 |
OpenMS
2.7.0
|
This document addresses OpenMS users and explains the installation procedure for building OpenMS from its sources. If you only want to use the OpenMS Proteomics Pipeline (TOPP), you are strongly encouraged to download the windows binary installer (see here), instead of building OpenMS from sources. For more information read the install instructions for the TOPP binaries.
This document especially considers the installation of several libraries which are required by OpenMS. Most of these libraries are made available in our "contrib-package" (see below).
If you encounter errors during configuring/compiling our software, have a look at our "Known Issues" section here, maybe the error is already known. If not, please write to the mailing list.
Notation of this tutorial
Pre-Requisites (Software)
7-Zip (see http://www.7-zip.org/) OpenMS depends on several other libraries. On a Windows system, these are usually not present.
In order to make the installation of the remaining required libraries easier, we composed a "contrib-package" containing the libraries Boost, Eigen, sqlite3, CoinMP, WildMagic, libSVM, libHDF5, glpk, zlib, libbz2 and Xerces-C. This contrib package has several advantages over manual installation
Download:
If you plan to use the development version of OpenMS, clone OpenMS and checkout the optional contrib submodule with
to obtain the latest potentially unstable version. If you want to use a release version of OpenMS, use the corresponding Release-tagged version on GitHub (https://github.com/OpenMS/contrib/releases) or download the contrib source from a .tar.gz for older releases.
Installation:
After you got the source code for the contrib package follow these steps:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 to get one! "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat". (Same goes for VS2019) mkdir contrib_win64_build Call CMake to build the contrib
Be aware that you can build 64bit apps even if your operating system is only 32bit (cross-compiling), but you will not be able to run 64bit apps in this case.
The <generator> you use must be one of the Visual Studio Generators. This is because some contrib libs require Visual Studio to build. Use the -A x64 flag to build 64-bit libraries for the contrib (32-bit does not really make any sense for LC-MS data processing)! Type cmake -help to see a list of available generators.
Example:
Qt comes in two flavors: commercial or non-commercial - choose whatever is applicable to you: read more on the Qt website For several recent QT5 versions, there are binary development versions available for the most recent compilers. Go to https://www.qt.io/download and click on "Go open source" at the end of the right column to download the installer. Follow steps, download, save and run the installer. Create a Qt account. Choose a folder like "c:\dev\QT". From the components choose a matching version, e.g. QT 5.10.0 and the MSVC component that fits your Visual Studio version and architecture (most likely only 64bit is supported anymore). You can deselect QTCreator under Tools. Accept the license, choose startmenu entries if wanted and install. Resulting files appear under "c:\dev\QT\$VERSION".
To build Qt from sources, download Qt5 from their git repository ad follow the steps below:
Follow this procedure if you want to compile Qt yourself:
-platform param for the next configure command (e.g., -platform win32-msvc2012) -prefix switch to install only the required parts of Qt to a new directory of your choice (called <path-to-qt>, e.g. c:/dev/Qt/5.9/). Check more options and supported compilers here: http://doc.qt.io/qt-5/configure-options.html (especially for developers). Note that part of Qt requires Python to compile, so its a good idea to add the Python executable to your path <path-to-qt> and sub-directories. <path-to-qt>/bin (!) directory to your PATH Environment Variable, so the dlls are found during runtime. <path-to-qt>/plugins/platforms, otherwise you might get an error "This application failed to start because it could not find or load the Qt platform plugin "windows". Alternatively, you can copy the entire platforms-folder into the folder where your OpenMS executables will be created (but they will depend on the build-type, i.e. release|debug|...). This section is optional. If you can live with the online documentation, you do not need to build your own.
In order to build the class documentation (doc & doc_internal targets), TOPP tutorials (doc_tutorials target) and more, you will need to install three programs:
dot. You should install the above apps prior to installing OpenMS (see below), because otherwise during the configuration step the documentation targets will be disabled. If you already have a working installation of OpenMS (without documentation), you can simply install the above programs and reconfigure OpenMS by calling cmake . in your build tree. No need to recompile the library!
For development and cutting edge functionalities we recommend using the Git version from GitHub
Certain stable releases can found on the GitHub release page https://github.com/OpenMS/OpenMS/releases.
If you have not installed the libraries which OpenMS requires, please refer to the section Contrib installation above (and skip the clone step).
Now, we create the build system:
mkdir OpenMS_Win64 Call CMake to create the build system
The CMAKE_PREFIX_PATH should hold the path to your Qt5 build directory (see example below). Note that it is NOT the main Qt5 directory, but the subfolder which is named after the toolchain it was build with (e.g. "5.6/msvc2015_64").
<path_to_qt>\mkspecs. Here you will need to choose the matching directory for your architecture and Visual Studio version. C:\dev\qt-5.9\mkspecs\winrt-x64-msvc2017The choice of <generator> depends on your system. Type cmake –help to see a list of available generators.
MSBuild also on VS solution files! Use the -A x64 flag to build a 64-bit OpenMS library and TOPP executables (32-bit does not really make any sense for LC-MS data processing)! The -T host=x64 flag instructs Visual Studio to use a 64bit compiler and linker toolchain to avoid linker errors (LNK1210: exceeded internal ILK size limit; link with /INCREMNTAL:NO) during development (if the flag is omitted the 32bit toolchain is used to generate 64bit binaries). Example: You can set more CMake variables adding -DVARIABLE=VALUE options when calling CMake.The most important CMake variables are:
OPENMS_CONTRIB_LIBS | Separate search path for the contrib libraries from github.com/OpenMS/contrib that is internally considered before CMAKE_PREFIX_PATH for searching, linking and adding include directories. |
CMAKE_PREFIX_PATH | Additional search path for the contrib libraries. [MacOSX only] If you want to use libraries installed via Homebrew or MacPorts you might need to provide the corresponding paths
Please keep in mind that both Homebrew and MacPorts do not provide all libraries so you also need to specify the path to your self-build contrib via -DOPENMS_CONTRIB_LIBS |
Qt5_DIR | Additional search path for the Qt5 CMake files. Use /PATH/TO/QT_INSTALLATION/lib/cmake/Qt5 as value. |
HAS_XSERVER=On/Off | [Linux/MacOS only] Defines if a running X Server is available when building OpenMS. As building parts of the documentation and running certain tests requires a running X Server, this flag can be used to disable those parts of the documentation and the tests that need an X Server. (Default: On) |
ADDRESS_SANITIZER=On/Off | [g++/clang only] Enables/Disables Address Sanitizer (ASAN) to find access violations and other bugs. |
WITH_GUI=On/Off | Defines if the OpenMS GUI tools (TOPPView, TOPPAS) should be built or not. If you plan to use OpenMS without a GUI, set this flag to "Off" (Default: On) |
ENABLE_TUTORIALS=On/Off | Enables targets to build and install the pdf tutorials (needs LaTeX). (Default: On) |
ENABLE_DOCS=On/Off | Enables documentation targets, allowing to build the OpenMS documentation. (Default: On) |
GIT_TRACKING=On/Off | Embed Git checksum into the library. (Default: On) |
ENABLE_UPDATE_CHECK=On/Off | Check online for OpenMS Updates upon invocation of any TOPP/UTIL. (Default: On) |
CMAKE_BUILD_TYPE | [makefiles only; does not apply for XCode or VS] Should be either 'Release' (optimization enabled) or 'Debug' (debug info and precondition/postcondition checks enabled). The default is 'Release'. |
CMAKE_CXX_COMPILER | Defines the C++ compiler to use. |
MY_CXX_FLAGS | Additional custom C++ compile options you would like to add (must fit your chosen compiler). This might be useful, for example, for adding debug symbols to a Release build, or for performance analysis (e.g. for '... -DMY_CXX_FLAGS="-Og;-ggdb;-g3;-fno-omit-frame-pointer" ...') |
CMAKE_C_COMPILER | Defines the C compiler to use. This should match the C++ compiler. Mixing compilers (e.g., clang++ for C++ and gcc for C) can lead to undefined behaviour as some internal settings (e.g., OpenMP support) are determined using the C compiler and are assumed to be the same for the C++ compiler. |
SEARCH_ENGINES_DIRECTORY (optional) | The location where thirdparty search engines (X!Tandem, OMSSA, MyriMatch, MSGF+, Fido) are located. This directory should have the same structure as the example in the search engine repository at https://github.com/OpenMS/THIRDPARTY after flattening for your platform. /. This directory is only needed to include thirdparty tools in the installer for OpenMS. |
PYOPENMS=Off/On | Create Python bindings, see also pyOpenMS (Python bindings) (Default: Off) |
CMAKE_INSTALL_PREFIX | the path where the bin/ and lib/ directories should be installed to (when sudo make install is wished for a system-wide install: e.g. -DCMAKE_INSTALL_PREFIX=/usr/local/) For development, install prefixes are not supported. In this case OpenMS must be built in place! |
Now there should be a OpenMS_host.sln file in your build directory, which you can open using Visual Studio. If you want to work on only a subset of OpenMS (e.g., OpenMS_GUI) you can open the specific solution that you will find in the src/ folder of your build folder and below (e.g., src/openms_gui/OpenMS_GUI.sln).
In Visual Studio execute the 'targets' project, which will show you the most prominent targets.
Try to build the OpenMS library - the target is called 'OpenMS'. This will create the OpenMS.dll library. If you used the debug configuration it will be called OpenMSd.dll, in release mode its called OpenMS.dll.
As a last step you should add the location of the OpenMS.dll to your PATH environment. This makes calling TOPPView and TOPP tools more convenient if you are working the command line. Also, external projects (see External Code using OpenMS) require the OpenMS dll (OpenMS.dll or OpenMSd.dll) to be in the PATH. Depending on the generator and configuration used you will find the dll in [OpenMS_build]/bin/Release or [OpenMS_build]/bin/Debug (for VS) or just [OpenMS_build]/bin (nmake). In the same folder the TOPP tools will reside once build (see next section). Be aware that the order of directories in the PATH variable determines which dll or executable is used, if no absolute path was given when the executable was called. So the PATH might need to be updated (add/delete/reorder entries) if you are working with multiple installations or configurations of OpenMS.
TOPP is a toolset for the analysis of HPLC-MS data. It consists of several small applications that can be chained to create analysis pipelines tailored for a specific problem.
After you have built OpenMS, you can build the TOPP tools by building the "TOPP" project in the IDE.
Each class in OpenMS and each TOPP tool has a unit test. The tests will be build with the complete solution. To specifically build and execute the tests, go to your OpenMS build_tree and further into ./src/tests/class_tests. There you'll find an OpenMS_class_tests.sln file, which you can open. For other generators an equivalent file with another suffix will be present. Now, build the 'ALL_BUILD' target and the 'RUN_TESTS' target. You can also run the tests in a command prompt in <OpenMS_build_tree> using ctest. Single tests can be run with ctest -R <testnameregex>, e.g. ctest -R Base64_test. For more syntax on CTest look at the online documentation at http://cmake.org/.
The Visual Studio solution files can contain many targets, which makes the IDE a bit sluggish especially when starting up the first time. The OpenMS class tests are by far the largest.
If you just want to compile the library or executables, it's usually faster to use the commandline. Visual Studio solution files can be used here as well, as arguments to MSBuild.exe, e.g.
Example:
OpenMS/tools/build.bat and in the root of your build tree (copied there by cmake for convenience), which allows to build the most important targets (TOPP, UTILS, Gui, Tests, Doc) in Release or Debug using very short notation. Call it without arguments to see its usage help text. For example to build only the OpenMS library in release mode, callDownload NSIS (we tested nsis-3.06.1 successfully) and extract it somewhere
Install the large-string-build NSIS installer on top (just extract into the same directory as NSIS; and use a matching version!). This is required for PATH manipulation of up to 8k length; the default NSIS handles up to 1k strings, which might be too short and potentially leads to a broken PATH environment variable.
Install the UltraModernUI-plugin on top (just extract into the same directory as NSIS). We tested version 2.0b6 successfully.
Add the NSIS folder (which contains 'makensis.exe') to your PATH, so CMake can find it.
Checkout the THIRDPARTY GitHub Repository and flatten the structure for the target platform, e.g. copy all subdirectories in ./all/ to ./Windows/64bit/.
Configure OpenMS as usual with additional flags SEARCH_ENGINES_DIRECTORY (for the flattened THIRDPARTY directory) and PACKAGE_TYPE="nsis", e.g.
Build all targets (incl. 'doc' and 'doc_tutorials') in Release mode (copy the Qt5 plugin to the [OpenMS_build]\bin\Release and [OpenMS_build]/doc/doxygen/parameters/Release/ directories first)
1.9.1