Installation is quite easy. Get MeVisLab from http://www.mevislab.de/download/. You can choose between the 32-bit and 64-bit version. After the download you must make the installer executable. Run the command 'chmod u+x' and execute it. Select an installation directory. We will refer to it as InstallDirectory from now.

	Note
	The installer is a 32-bit executable, even if MeVisLab is 64-bit. Thus you must ensure that you have installed the 32-bit compatibility libraries on a 64-bit system. For example, the Ubuntu package is called 'ia32-libs'.

	Note
	Users who want to run MeVisLab must have read and write permissions to all files in the MeVisLab installation directory. Keep this in mind when installing MeVisLab as the root user.

You can start MeVisLab from the applications menu entry. Alternatively, you can run InstallDirectory/bin/MeVisLab. InstallDirectory/bin/MeVisLab_d will start the debug version of MeVisLab.

MeVisLab offers "Module Wizards", which are accessible via the file menu. They create the skeleton of ML- and Inventor-modules. The sources are created in a folder named by your module in the "Source" subdirectory of a MeVisLab package.

Some environment variables are required to build C++ modules, for example MLAB_ROOT, MLAB_COMPILER_VERSION and LD_LIBRARY_PATH.

The next step is to create the makefiles. Therefore simply execute the bash script inside your modules source directory (it is named just like your module).Now you can type make -f Makefile."modulename" (or use mlmake) to compile and link your module. If everything works fine, the library will be copied to the lib directory of the package. If MeVisLab is running, then it will be copied to lib/updated instead. It will be moved to lib during the next MeVisLab restart.

	Note
	To avoid problems you should use the same compiler version that MeVisLab was built with. The required version is mentioned in the Linux readme file: InstallDirectory/Packages/MeVisLab/Resources/Documentation/Publish/SDK/LinuxReadme.txt. You can check your compiler version by running gcc -dumpversion.

	Tip
	If you have multiple cpus, then you can pass -j n to make for parallel execution, where n must be replaced by the number of parallel processes.

	Tip
	MeVisLab supports the Code::Blocks IDE (http://www.codeblocks.org/). A Code::Blocks project is created next to the makefiles. It is called "modulename".cbp.

	Tip
	You can use InstallDirectory/bin/mlmake and InstallDirectory/bin/mlcodeblocks to run make and codeblocks from outside the bash context created with InstallDirectory/bin/mlshell.

Use the gdb from the bash context created with InstallDirectory/bin/mlshell. The MeVisLab executable for debugging is InstallDirectory/Packages/MeVisLab/IDE/bin. You can also use the script InstallDirectory/bin/mlgdb from outside the bash context. If it is started without arguments, then it uses MeVisLab as debug target, otherwise all arguments are passed to the gdb.