Installation Instructions
=========================
   Since you are reading this I assume you already obtained one of the release
tarballs and successfully extracted it. The latest version of LEMON is
available at our web page (http://lemon.cs.elte.hu/).
   In order to install LEMON from the extracted source tarball you have to
issue the following commands:
      This command changes to the directory which was created when you
      extracted the sources. The x.y.z part is a version number.
      This command runs the configure shell script, which does some checks and
      This command compiles the non-template part of LEMON into libemon.a
      file. It also compiles the programs in the tools, benchmark and demo
      subdirectories when enabled.
      This step is optional, but recommended. It runs the test programs that
      we developed for LEMON to check whether the library works properly on
      This command installs LEMON under /usr/local (you will need root
      privileges to be able to do that). If you want to install it to some
      other location, then pass the --prefix=DIRECTORY flag to configure in
      step 2. For example: `./configure --prefix=/home/username/lemon'.
      This command installs the documentation under share/doc/lemon/docs. The
      generated documentation is included in the tarball. If you want to
      generate it yourself, then run `make html'. Note that for this you need
      to have the following programs installed: Doxygen, Graphviz, Ghostscript,
Configure Options and Variables
===============================
   In step 2 you can customize the actions of configure by setting variables
and passing options to it. This can be done like this:
`./configure [OPTION]... [VARIABLE=VALUE]...'
   Below you will find some useful variables and options (see
`./configure --help' for more):
  Change the C++ compiler to 'comp'.
  Pass the 'flags' to the compiler. For example CXXFLAGS='-O3 -march=pentium-m'
  turns on generation of aggressively optimized Pentium-M specific code.
  Set the installation prefix to PREFIX. By default it is /usr/local.
   Build the examples in the demo subdirectory.
   Do not build the examples in the demo subdirectory (default).
   Build the programs in the benchmark subdirectory.
   Do not build the programs in the benchmark subdirectory (default).
   Build the programs in the tools subdirectory (default).
   Do not build the programs in the tools subdirectory.
   Enable GLPK support (default). You should specify the prefix too if
   you installed GLPK to some non-standard location (e.g. your home
   directory). If it is not found, GLPK support will be disabled.
--with-glpk-includedir=DIR
   The directory where the GLPK header files are located. This is only
   useful when the GLPK headers and libraries are not under the same
   prefix (which is unlikely).
   The directory where the GLPK libraries are located. This is only
   useful when the GLPK headers and libraries are not under the same
   prefix (which is unlikely).
   Enable CPLEX support (default). You should specify the prefix too
   if you installed CPLEX to some non-standard location
   (e.g. /opt/ilog/cplex75). If it is not found, CPLEX support will be
--with-cplex-includedir=DIR
   The directory where the CPLEX header files are located. This is
   only useful when the CPLEX headers and libraries are not under the
   same prefix (e.g.  /usr/local/cplex/cplex75/include).
   The directory where the CPLEX libraries are located. This is only
   useful when the CPLEX headers and libraries are not under the same
   /usr/local/cplex/cplex75/lib/i86_linux2_glibc2.2_gcc3.0/static_pic_mt).
   Enable SoPlex support (default). You should specify the prefix too if
   you installed SoPlex to some non-standard location (e.g. your home
   directory). If it is not found, SoPlex support will be disabled.
--with-soplex-includedir=DIR
   The directory where the SoPlex header files are located. This is only
   useful when the SoPlex headers and libraries are not under the same
   prefix (which is unlikely).
   The directory where the SoPlex libraries are located. This is only
   useful when the SoPlex headers and libraries are not under the same
   prefix (which is unlikely).