For full installation and usage instructions, see the documentation.
Building IMP from source code
To build IMP source found in
path/to/imp-source and install it in
mkdir build && cd build
cmake path/to/imp-source -DCMAKE_INSTALL_PREFIX=path_to_install
See the installation instructions in the manual for more details (in particular this covers the necessary prerequisites you'll need before running cmake).
ccmake to see more variables that can be used to customize your build and
To run IMP without installing, build IMP and then use
set the required environment variables. For example, to run
./setup_environment.sh ligand_score arguments..., or
./setup_environment.sh $SHELL and then
ligand_score arguments... in the
Copyright and License information
IMP is Copyright 2007-2023 IMP Inventors. The IMP Inventors are Andrej Sali, Ben Webb, Daniel Russel, Keren Lasker, Dina Schneidman, Javier Velázquez-Muriel, Friedrich Förster, Elina Tjioe, Hao Fan, Seung Joong Kim, Yannick Spill, Riccardo Pellarin.
IMP is largely available under the GNU Lesser GPL; see the file COPYING.LGPL for the full text of this license. Some IMP modules are available under the GNU GPL (see the file COPYING.GPL). Please refer to the documentation for more detail.
Files and folders structure
When you build IMP, the
lib directory contains Python modules (both pure
Python, in the
IMP subdirectory, and C++ extensions, as
in the top-level directory) and the IMP C++ libraries (as
in the top-level directory). Rationale: Windows searches for C++ dynamic
libraries in the same directory as C++ Python extensions.
include directory contains all public header files under the
subdirectory. Modules are in named subdirectories under that.
swig directory contains all SWIG interface (
.i) files used to build
the Python interface.