Installation notes

You'll have to download a version of GraceTMPL, first. Follow the instructions in the Downloads section to do so.

Compilation

After downloading and unpacking the GraceTMPL source distribution or checking out the cvs version, change the working directory to the GraceTMPL sources.

Please note that you must have numarray installed to be able to compile the python wrap. Also note that it's really worth it!

If you have not yet done so, copy Makefile.defs.tmpl to Makefile.defs and edit it to contain your preferred installation path. Normally, the base path is /usr/local, so binaries will go to /usr/local/bin , libraries to /usr/local/lib and header files to /usr/local/include .

Now you can just type

  # make
  # make pythonwrap

If numarray is not installed on your system the pythonwrap will not be built.

After a cvs update it might happen that you are advised to edit Makefile.defs again. You can safely leave your settings, but it would be wise to compare Makefile.defs.tmpl with Makefile.defs to see if any important declarations are missing in the latter.

Installation

If all of the above went well you can now type

  # make install
  # make python_install

If the installation base directory is not writable for you, you have to do it as root.

Upon installation, the script gracetmpl-config will be installed in the binary destination directory. It can be taken by projects using GraceTMPL to identify the necessary CFLAGS and LIBS settings for compilation of the project. You can use 'gracetmpl-config --cflags' and 'gracetmpl-config --libs' for that.

Making the tests

There are several tests contained in the directory tests to check GraceTMPL's correct behavior and also put on a little show. The tests' output are included in the docs' section Examples and tests.

  # make test

should do. The results are .agr files you can open with xmgrace.

Building the docs

Normally you wouldn't have to build the docs since GraceTMPL is already shipped with complete docs. Only when starting from a CVS-version you might want to take this step. Note you must have Image Magick installed to be able to build the test output images for the section Examples and tests. Doxygen is an essential must-have to process the inline documentation.

If all prerequisites are met, just type

  # make doc

---