Difference between revisions of "Build requirements"

From mitk.org
Jump to navigation Jump to search
m
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
__NOTOC__
+
For the current build requirements please see our [http://docs.mitk.org/nightly/BuildInstructionsPage.html Build Instructions]. Besides, the [[Developer_Tutorial|Developer Tutorial]] could be helpful.
= Build Requirements =
 
 
 
 
 
<pre><nowiki>#!wiki tip
 
'''Automatically build all requirements'''
 
 
 
Note that with the ''MITK superbuild'', the only requirements on external packages are
 
 
 
* [[http://cmake.org|CMake]] 2.8.4 or later
 
* [[http://qt-project.org|Qt]] 4.6.2 or later (for application and widget support)
 
 
 
All other required software packages will be downloaded and build automatically, depending on your MITK configuration.
 
 
 
See the [[http://docs.mitk.org/nightly-qt4/BuildInstructionsPage.html|Build Instructions]] for more information.
 
</nowiki></pre>
 
 
 
 
 
For completeness, the sections below contain some hints how to build required external packages yourself.
 
 
 
== Supported Platforms ==
 
 
 
Please see http://docs.mitk.org/nightly-qt4/SupportedPlatformsPage.html
 
 
 
There have been some experiments compiling MITK with gcc 4.4.0 on Windows using MinGW (see [[MinGW Instructions]] for details). However, please note that MinGW is not one of the officially supported platforms.
 
 
 
=== MacOS ===
 
[[MacOSX|Building MITK for MacOS]] contains a detailed description.
 
 
 
== ITK Download ==
 
We recommend to use the latest stable ITK 3.x version. Usually MITK is compatible with the latest two versions of ITK. However, ITK 4 support is still not finished. BUILD_SHARED_LIBS must be turned ON.
 
 
 
* Since May 2011*: MITK needs at least [http://sourceforge.net/projects/gdcm/ GDCM 2.0.14]. If the ITK version you are using is not bundled with this version, you need to build it yourself (uses also CMake) and toggle ITK_USE_SYSTEM_GDCM while configuring ITK.
 
 
 
[http://itk.org/ITK/resources/software.html ITK-Download page]
 
 
 
== VTK Download ==
 
Currently, VTK version 5.6 or 5.8 is required. VTK_USE_PARALLEL, VTK_USE_HYBRID, and BUILD_SHARED_LIBS must be turned ON.
 
 
 
If you want to use Qt for application development, compile VTK_USE_GUISUPPORT (advanced CMake option), VTK_USE_QVTK and VTK_USE_QVTK_QTOPENGL turned ON.
 
 
 
[http://vtk.org/VTK/resources/software.html VTK-Download page]
 
 
 
== CMake Download ==
 
MITK requires the latest stable CMake release.
 
 
 
[http://www.cmake.org/HTML/Download.html CMake-Download page]
 
 
 
Windows installer packages can be built using the [http://nsis.sourceforge.net/Main_Page Nullsoft scriptable install system].
 
 
 
== GUI-Toolkits ==
 
The core MITK library is GUI-toolkit independent.
 
 
 
The main example application ExtApp is implemented using Qt 4.5. It is currently under heavy development, since we only recently switched to Qt 4.
 
 
 
Qt can be downloaded from Nokia [http://www.qtsoftware.com/downloads here].
 
 
 
== OpenCV (optional) ==
 
The Open Source Computer Vision library may be used for video playback/processing in MITK, but is completely optional! Currently, only OpenCV 2 is supported as it is built with CMake and therefore easily integrated in MITK. To use OpenCV in MITK, follow these steps:
 
 
 
* Download OpenCV from their [http://opencv.willowgarage.com/wiki/ Website] for your OS
 
* You may compile OpenCV from source or use an installer. When building from source, there are no special options you have to set in CMake, just two things to remind:
 
** On Windows: Turn off "ENABLE_OPENMP" when you have built MITK without OpenMP support. If you are unsure, turn it off
 
** On Linux: As there were issues with AVI playback, make sure to use OpenCV with FFMPEG on Linux. [http://opencv.willowgarage.com/wiki/FFMPEG Read here how to use FFMPEG with OpenCV]
 
* General installation instructions: http://opencv.willowgarage.com/wiki/InstallGuide
 
* (Re-)configure your MITK build: Open CMAKE and turn on MITK_USE_OPENCV. Next, let OpenCV_DIR point to the directory containing the OpenCVConfig.cmake file (should be found automatically if OpenCV was installed regularly)
 
* Have a look into the module "OpenCVVideoSupport"
 

Latest revision as of 16:23, 9 June 2016

For the current build requirements please see our Build Instructions. Besides, the Developer Tutorial could be helpful.