3 # Building and installing basics # {#installation}
7 IMP is available in a variety of different ways. If you are just planning on
using
8 existing IMP code and run on a standard platform, you may be able to install
9 a pre-built binary. See the [download](http:
11 If you are planning on contributing to IMP, you should download and build the source.
12 See the next section
for more information.
16 Building IMP from source is straightforward
if the [prerequisites](#prereqs)
17 are already installed.
24 cmake ../imp -DCMAKE_BUILD_TYPE=Release
27 See [Building IMP with CMake](https:
31 # Prerequisites # {#installation_prereqs}
32 In order to obtain and compile IMP, you will need:
34 - cmake (2.8 or later)
35 - Boost (1.40 or later)
37 - Developers will also need a git client to access the repository
39 If you wish to build the Python interfaces, you will also need:
41 - Python (2.4 or later)
42 - SWIG (1.3.40 or later)
44 ## Getting prerequisites on a Mac ## {#installation_prereqs_mac}
46 Mac users must first install Xcode (previously known as Developer Tools)
47 which is not installed by
default with OS X, but is available from the App store
48 (or from the Mac OS install DVD
for old versions of Mac OS). They will also
49 need the Xcode command line tools (install by going to Xcode Preferences, then
50 Downloads, then Components, and select
"Command Line Tools").
52 Then Mac users should use one of the available collections of Unix tools,
57 `brew tap homebrew/science`
59 `brew install boost gmp google-perftools cgal graphviz gsl cmake doxygen hdf5 swig eigen fftw mpfr`
61 to install everything IMP finds useful (or that you will want
for installing various useful python libs that IMP finds useful). On older Macs, you may also need to `brew install git`
if you want to use git (newer Macs include git).
63 config file or by making an `environment.plist` file) and then
do
65 `sudo port install boost cmake swig-python`
67 to install the needed libraries and tools. When installing HDF5 with MacPorts, be sure to install `hdf5-18`
68 (version 1.8), rather than the older `hdf5` (version 1.6.9).
71 ### Mac OS X 10.5 and 10.6
72 These versions of mac os include a
'swig' binary, but it is too old to use
73 with IMP. You need to make sure that the newer version of `swig` is found first
77 ## Getting prerequisites on Windows ## {#installation_prereqs_windows}
79 We recommend Linux or Mac
for developing with IMP, as obtaining the
80 prerequisites on Windows is much more involved. However, we
do test IMP on
81 Windows, built with the Microsoft Visual Studio compilers (we use Visual Studio
82 Express 2010 SP1). One complication is that different packages are compiled
83 with different versions of Visual Studio, and mixing the different runtimes
84 (msvc*.dll) can cause odd behavior; therefore, we recommend building most
85 of the dependencies from source code
using the same version of Visual Studio
86 that you
're going to use to build IMP. The basic procedure is as follows:
88 - Install Microsoft Visual Studio Express (it is free, but registration with
89 Microsoft is required).
90 - Get and install [cmake](http://www.cmake.org).
91 - Get [Python 2](http://www.python.org) (not Python 3)
92 (make sure you get the
93 32-bit version if you're going to build IMP
for 32-bit Windows).
96 (both the
"complete package, except sources" and the
"sources" installers).
97 - The
package without sources can be installed anywhere; we chose the
98 default location of `C:\Program Files\GnuWin32`. The sources, however,
99 must be installed in a path that doesn
't contain spaces (otherwise the
100 Boost build will fail). We chose `C:\zlib`.
101 - We found that the zconf.h header included with zlib erroneously includes
102 unistd.h, which doesn't exist on Windows, so we commented out that line
104 - Download the [Boost source code](http:
105 (we extracted it into `C:\Program Files\boost_1_53_0`), then
106 - Open a Visual Studio Command Prompt, and cd into the directory where
109 - You may need to help the compiler find the zlib header file with
110 `set INCLUDE=C:\Program Files\GnuWin32\include`
111 - Run `bjam link=shared runtime-link=shared -sNO_ZLIB=0 -sZLIB_SOURCE=C:\zlib\1.2.3\zlib-1.2.3`
112 - Get and install [SWIG
for Windows](http:
113 - Get the [HDF5 source code](http:
114 - Edit the H5pubconf.h file in the `windows\src` subdirectory to
115 disable szip (or first install szip
if you want to include szip support).
116 Copy
this file into the top-level src directory.
117 - Open the h5libsettings project (in `windows\misc\typegen\h5libsettings`)
118 in Visual Studio, and build it in Release configuration. (Note that
if
119 you don
't have the x64 SDK installed, you'll first need to edit the
120 project file in a text editor and
remove any mention of the x64 platform,
121 since otherwise the upgrade of
this solution to 2010 format will fail.)
122 - Build the
'h5tinit' project (in `windows\misc\typegen\h5tinit`) in
123 Release configuration.
124 - Build the
'hdf5dll' project (in `windows\proj\hdf5dll`) in
125 Release configuration.
126 - In order
for Visual Studio to find zlib, we first opened the project
127 settings, and under C/C++, Additional Include Directories, added
128 `C:\Program Files\GnuWin32\include`, and under Linker, Input,
129 Additional Dependencies, added
130 `C:\Program Files\GnuWin32\lib\zlib.lib`.
131 - Copy proj\hdf5dll\Release\hdf5dll.lib to hdf5.lib to help cmake
133 - (Optional) [Build CGAL from source code](http:
134 - (Optional) [Get and install Eigen](http:
135 - (Optional) Download the
137 instructions at that website to make .lib
import libraries needed
for
139 - Copy `libfftw3-3.lib` to `fftw3.lib` to help cmake find it
141 [GSL source code](http:
143 - Open the libgsl project file in the `src\gsl\1.8\gsl-1.8\VC8`
145 - Build in Release-DLL configuration
146 - Copy the generated `libgsl.dll` and `libgslcblas.dll` to a suitable
147 location (we used `C:\Program Files\gsl-1.8\lib`)
148 - Copy the corresponding .lib files, libgsl_dll.lib and libgslcblas_dll.lib
149 (we recommend removing the _dll suffix and the lib prefix when you
do
150 this so that cmake has an easier time finding them, i.e. call them
151 gsl.lib and gslcblas.lib).
152 - (Optional) Get [numpy and scipy](http:
154 - (Optional) Get and install
156 - Copy `libTAU.lib` to `TAU.lib` to help cmake find it.
157 - (Optional) Get the [OpenCV source code](http:
158 and build it by following the instructions at that website.
159 - Copy each `opencv_*.lib` to a similar file without the version extension
160 (e.g. copy `opencv_ml244.lib` to `opencv_ml.lib`) to help cmake find it
161 - Set PATH, INCLUDE, and/or LIB environment variables so that the compiler
162 can find all of the dependencies. (We wrote a little batch file.)
163 - Set up IMP by running something similar to
165 `cmake <imp_source_directory> -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS=
"/DBOOST_ALL_DYN_LINK /EHsc /D_HDF5USEDLL_ /DWIN32 /DGSL_DLL" -G
"NMake Makefiles"`
167 - Then use simply
'nmake' (instead of
'make', as on Linux or Mac) to
168 build IMP. (cmake can also generate Visual Studio project files, but
170 - To use IMP or run tests, first run the setup_environment.bat file to set
171 up the environment so all the programs and Python modules can be found.
172 (This batch file needs to be run only once, not
for each test.)
174 ## Getting prerequisites on Linux
175 All of the prerequisites should be available as pre-built packages
for
176 your Linux distribution of choice.
178 # Optional prerequisites # {#installation_preqs_optional}
180 IMP can make use of a variety of external tools to provide more or
181 better functionality.
184 part of most Unix tool sets (HomeBrew, all Linux distributions etc.).
185 - [Modeller](\ref modeller)
187 - [Google perf tools](\ref perf)
190 - [OpenCV](\ref OpenCV)
193 # Where to go next # {#installation_next}
195 You are now ready to use IMP within Python and C++.
197 Everyone should read the [introduction](\ref introduction) and developers should
198 then move on to the [Developer Guide](\ref devguide).