A C library version of the GAP kernel.
GAP (http://www.gap-system.org) is a system fo computational group
theory. This repo contains a shared library version of the GAP kernel,
allowing you to directly talk to GAP from your own C/C++ code.
Much of the group theory in Sage (http://www.sagemath.org) is
implemented using LibGAP.
* the GAP library (scripts in the GAP language)
* GMP/MPIR shared library
* GMP/MPIR headers
Packaging (to run "make dist"):
* The Python PLY module (http://www.dabeaz.com/ply)
The current tarball can be found at
* Always use the libgap-x.y.z.tar.gz tarball (the output of "make
dist"), and not the files in the repository. Only the former has
its symbols transforrmed with the "libGAP_" prefix.
* For the testsuite, you need to have the gap library installed
somewhere. Configure/make libGAP with
-DSYS_DEFAULT_PATHS=<gap_root> cflags tests, where the path has be
quoted such that it ends up with quotation marks in C sources:
$ ./configure CFLAGS='-DSYS_DEFAULT_PATHS=\"/path/to/gap\"'
$ export CFLAGS='-DSYS_DEFAULT_PATHS=\"/home/vbraun/Sage/git/local/gap/latest\"'
$ make check
For example, using the Gap installation in Sage:
$ ./configure CFLAGS='-DSYS_DEFAULT_PATHS=\"$SAGE_ROOT/local/gap/latest\"'
LibGAP aims to track the upstream GAP development as close as
possible. To update LibGAP-x.y.z to a new GAP-x.y.(z+1) release, use
the following steps:
1. Copy the previous and new GAP src directory to upstream-gap-x.y.z
and upstream-gap-x.y.(z+1), respectively.
2. Run scripts/generate_patch.sh, which will generate
3. Replace the C sources in LibGAP's src with the new
cp upstream/src/*.[c,h] src/
4. Apply patches/gap-x.y.z.patch to the new src
directory. Hopefully, there are no conflicts. Good luck!
$ cd src && patch -p1 < ../patches/gap-x.y.z.patch
5. Update src/Makefile.am if C sources have been added/removed.
6. Update the version in configure.ac and run
$ autoreconf -fiv
7. Run "make distcheck" (the testsuite will fail because it does not
pass CFLAGS, ignore).
The tests use unescaped GAP symbols since its easier to develop. The
test/Makefile.am dist-hook rewrites them with the libGAP_ prefix. If
you change tests make sure to update the dist-hook in with any new GAP
symbols that you use.
For debugging you should probably build gap
$ ./configure CFLAGS='-O0 -g3' # standalone gap
$ SAGE_DEBUG=yes ./sage -f gap # inside of Sage
libgap with debug symbols:
$ ./configure CFLAGS='-DSYS_DEFAULT_PATHS=\"/path/to/gap\" -O0 -g3 -DDEBUG_MASTERPOINTERS -DDEBUG_GLOBAL_BAGS -DDEBUG_FUNCTIONS_BAGS'
See Sage, and in particular $SAGE_ROOT/sage/libs/gap/, for real-world
usage of LibGAP. Sage contains a Cython interface to LibGAP if you are
Talk about LibGAP:
* Slides: https://bitbucket.org/vbraun/libgap/downloads/libGAP.pdf
* Video: https://www.youtube.com/watch?v=0gOL0QRHkmA