Repository files navigation

For full installation and usage instructions, see thedocumentation.

To build IMP source found inpath/to/imp-source and install it inpath_to_install do:

1. mkdir build && cd build
2. cmake path/to/imp-source -DCMAKE_INSTALL_PREFIX=path_to_install
3. make -j4
4. make install

See theinstallation instructions in the manualfor more details (in particular this covers the necessary prerequisites you'llneed before running cmake).

Runccmake to see more variables that can be used to customize your build andinstall.

To run IMP without installing, build IMP and then usesetup_environment.sh toset the required environment variables. For example, to runligand_score, do./setup_environment.sh ligand_score arguments..., or./setup_environment.sh $SHELL and thenligand_score arguments... in thenew shell.

IMP is Copyright 2007-2025 IMP Inventors. The IMP Inventors areAndrej 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.LGPLfor the full text of this license. Some IMP modules are available under theGNU GPL (see the file COPYING.GPL). Please refer to thedocumentationfor more detail.

When you build IMP, thelib directory contains Python modules (both purePython, in theIMP subdirectory, and C++ extensions, as_IMP_foo.soin the top-level directory) and the IMP C++ libraries (aslibimp_foo.soin the top-level directory). Rationale: Windows searches for C++ dynamiclibraries in the same directory as C++ Python extensions.

Theinclude directory contains all public header files under theIMPsubdirectory. Modules are in named subdirectories under that.

Theswig directory contains all SWIG interface (.i) files used to buildthe Python interface.