The binary distribution is nothing else as a full source distribution with precompiled client programs. Run

    make install

and choose the installation location when asked for.

If you are going to develop new client programs, you should add `install-devel` to the `make` arguments. You must also meet all the requirements concerning the C++ compiler. If your standard C++ compiler does not fit, you will need an explicit configuration step

    make configure

The GMP library is included in source form only. It will be compiled if make configure fails to find a working installation of it on your system. It usually takes not that long than the compilation of the entire polymake sources, and can profit enormously from the processor-specific tuning procedures implemented in the GMP configuration script.

### Notes

- Not every MacOS X system seems to have GMP library installed by default. In this case `polymake` clients will try to use the own copy of the library. But you must tell the run-time dynamic loader where it resides. The most usual way is to include

      export DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH:+"$DYLD_LIBRARY_PATH":}/usr/local/polymake/lib

  in `~/.bashrc` (if you are using `bash`), or

      if $?DYLD_LIBRARY_PATH; then
         setenv DYLD_LIBRARY_PATH "$DYLD_LIBRARY_PATH":/usr/local/polymake/lib
      else
         setenv DYLD_LIBRARY_PATH /usr/local/polymake/lib
      endif

  in `~/.cshrc` (for `tcsh`).
  Be sure to replace `/usr/local/polymake` in the examples above by appropriate installation path.
- The installation procedure copies all program binaries to the final destination; after it has completed, you can safely delete the whole unpacked tree.