Footnotes

(1)

The configure script is itself generated from the file ‘configure.ac’. It is only distributed in packaged releases of GiNaC. If you got the naked sources, e.g. from git, you must generate configure along with the various ‘Makefile.in’ by using the autoreconf utility. This will require a fair amount of support from your local toolchain, though.

(2)

Uninstallation does not work after you have called make distclean since the ‘Makefile’ is itself generated by the configuration from ‘Makefile.in’ and hence deleted by make distclean. There are two obvious ways out of this dilemma. First, you can run the configuration again with the same PREFIX thus creating a ‘Makefile’ with a working ‘uninstall’ target. Second, you can do it by hand since you now know where all the files went during installation.

(3)

The self-contained source for this example is included in GiNaC, see the ‘doc/examples/mystring.cpp’ file.

(4)

Each GiNaC class has a static member called tinfo_static. This member is declared by the GINAC_DECLARE_REGISTERED_CLASS macros and defined by the GINAC_IMPLEMENT_REGISTERED_CLASS macros.

(5)

This is because CLN uses PROVIDE/REQUIRE like macros to let the compiler gather all static initializations, which works for GNU C++ only. Feel free to contact the authors in case you really believe that you need to use a different compiler. We have occasionally used other compilers and may be able to give you advice.

(6)

If GiNaC is installed into some non-standard directory prefix one should set the PKG_CONFIG_PATH environment variable to prefix/lib/pkgconfig for this to work.