Prerequisites

In order to build IPOPT, some third party components are required:

• BLAS (Basic Linear Algebra Subroutines). Many vendors of compilers and operating systems provide precompiled and optimized libraries for these dense linear algebra subroutines. But you can also get the source code from www.netlib.org and have the IPOPT distribution compile it automatically.
• LAPACK (Linear Algebra PACKage). Also for LAPACK, some vendors offer precompiled and optimized libraries. But like with BLAS, you can get the source code from www.netlib.org and have the IPOPT distribution compile it automatically.

  Note that currently LAPACK is only required if you intend to use the quasi-Newton options in IPOPT. You can compile the code without LAPACK, but an error message will then occur if you try to run the code with an option that requires LAPACK. Currently, the LAPACK routines that are used by IPOPT are only DPOTRF, DPOTRS, and DSYEV.

• A sparse symmetric indefinite linear solver. The IPOPT needs to obtain the solution of sparse, symmetric, indefinite linear systems, and for this it relies on third-party code.

  Currently, the following linear solvers can be used:

  • MA27 from the Harwell Subroutine Library
    (see http://www.cse.clrc.ac.uk/nag/hsl/).
  • MA57 from the Harwell Subroutine Library
    (see http://www.cse.clrc.ac.uk/nag/hsl/).
  • MUMPS (MUltifrontal Massively Parallel sparse direct Solver)
    (see http://graal.ens-lyon.fr/MUMPS/)
  • The Parallel Sparse Direct Solver (PARDISO)
    (see http://www.computational.unibas.ch/cs/scicomp/software/pardiso/).
    Note: The Pardiso version in Intel's MKL library does not yet support the features necessary for IPOPT.
  • The Watson Sparse Matrix Package (WSMP)
    (see http://www-users.cs.umn.edu/~agupta/wsmp.html)
  We recommend to include at least one of the linear solvers above in order to run IPOPT, and if you want to be able to switch easily between different alternatives, you can compile IPOPT with all of them.

  The IPOPT library also has mechanisms to load the MA27, MA57, and Pardiso linear solvers from a shared library at runtime, if the library has not been compiled with them (see Section 2.2.6).

  NOTE: The solution of the linear systems is a central ingredient in IPOPT and the optimizer's performance and robustness depends on your choice. Please keep this in mind, particularly when you are comparing IPOPT with other optimization codes.

  Interfaces to other linear solvers might be added in the future; if you are interested in contributing such an interface please contact us! Note that IPOPT requires that the linear solver is able to provide the inertia (number of positive and negative eigenvalues) of the symmetric matrix that is factorized.

• Furthermore, IPOPT can also use the Harwell Subroutine MC19 for scaling of the linear systems before they are passed to the linear solver. This may be particularly useful if IPOPT is used with MA27 or MA57. However, it is not required to have MC19 to compile IPOPT; if this routine is missing, the scaling is never performed⁴.
• ASL (AMPL Solver Library). The source code is available at www.netlib.org, and the IPOPT makefiles will automatically compile it for you if you put the source code into a designated space. NOTE: This is only required if you want to use IPOPT from AMPL and want to compile the IPOPT AMPL solver executable.

For more information on third-party components and how to obtain them, see Section 2.2.

Since the IPOPT code is written in C++, you will need a C++ compiler to build the IPOPT library. We tried very hard to write the code as platform and compiler independent as possible.

In addition, the configuration script currently also searches for a Fortran, since some of the dependencies above are written in Fortran. If all third party dependencies are available as self-contained libraries, those compilers are in principle not necessary. Also, it is possible to use the Fortran-to-C compiler f2c from www.netlib.org/f2c to convert Fortran code to C, and compile the resulting C files with a C compiler and create a library containing the required third party dependencies. We have tested and used this in connection with the Microsoft Visual C++ compiler, and instructions on how to use it in this context are given below.