Chapter 17. Operating Systems Details

Table of Contents

17.1. Windows Guide
17.1.1. Installation on Windows
17.1.2. Module Development on Windows
17.2. Mac OS X Guide
17.3. Linux Guide
17.3.1. MeVisLab on Linux

The following chapter gives detailed information on some operating system (OS) specific settings and things to keep in mind, especially when working on module development. Read the respective OS sections in case of compilation and compiler problems and when in need of troubleshooting.

17.1. Windows Guide

17.1.1. Installation on Windows

For Windows, a typical installation of the SDK results in the following programs being installed:

  • MeVisLab in release and debug version. This versions will scan the installed packages at start-up to update the internal module database.

  • QuickStart MeVisLab in release and debug version. This will start MeVisLab without scanning the installed packages; while being much faster, new or removed modules will not cause a change of the internal database. However, if no modules are being developed, this programs are what you want to start.

  • MeVisLab MATE, this is an integrated text editor.

  • MeVisLab ToolRunner, this is a meta-tool.

Figure 17.1. MeVisLab Icons

MeVisLab Icons


Debug versions can only be started if a development environment (Visual Studio) is installed on the computer.

17.1.2. Module Development on Windows

For C++ module development, the Visual Studio installation and its Visual C++ version has to fit to the installed MeVisLab version. For example, for MeVisLab 64bit, Visual Studio 2017 X64 with VC15 or Visual Studio 2019 X64 with VC17 needs to be installed.

There may also be differences between Visual Studio Express versions and the full Visual Studio versions (standard or professional). Make sure that the compiler version that you intend to use is supported by your Visual Studio installation.

A helpful tool for development is the ToolRunner, which is delivered with the MeVisLab SDK. It looks for a variety of tools (Python, Subversion, DependencyWalker etc.), helping you to check their availability and versions. If a tool is definitely installed but cannot be found by ToolRunner, you might check the PATH variable on Windows and also check whether more than one software version is installed. Only certain versions may work with MeVisLab; in that case, upgrade or downgrade accordingly. See the ToolRunner Manual for further information.

For compilation, qmake is used. See the qmake Manual for further information.

The environment variables MEVIS_DEBUGGING_COMMAND_RELEASE and MEVIS_DEBUGGING_COMMAND_DEBUG can be set to control which executable is used for debugging in Visual Studio. Use either absolute file paths or paths relative to MLAB_ROOT. Arguments can be passed via MEVIS_DEBUGGING_COMMAND_ARGUMENTS to the executable. You will have to recompile the *.pro file after changing these variables.