HACKING

All you need to know when hacking (modifying) GNU libsigsegv or when building
it off the Git repository.


Requirements
============

You will need reasonably recent versions of the build tools:

  * A C compiler. Such as GNU GCC.
    + Homepage:
      https://gcc.gnu.org/

  * GNU automake
    + Homepage:
      https://www.gnu.org/software/automake/

  * GNU autoconf
    + Homepage:
      https://www.gnu.org/software/autoconf/

  * GNU m4
    + Homepage:
      https://www.gnu.org/software/m4/

  * Perl
    + Homepage:
      https://www.perl.org/

  * Either an internet connection or a recent copy of GNU gnulib.
    + Homepage:
      https://www.gnu.org/software/gnulib/

And, of course, the packages listed in the DEPENDENCIES file.


Building off the Git repository
===============================

Access to the Git repository is described at
https://savannah.gnu.org/git/?group=libsigsegv .

After fetching the sources from the Git repository, peek at the comments in
autogen.sh, then run
  ./autopull.sh
  ./autogen.sh
Then you can proceed with "./configure" as usual.

Each time you want to update the source, do not only "git pull".  Instead do
  git pull && ./autopull.sh
  ./autogen.sh


Continuous integration
======================

There are two continuous integrations that regularly build and test
libsigsegv:
* On a Linux/glibc system only:
  https://gitlab.com/gnu-libsigsegv/ci-distcheck/pipelines
  https://gitlab.com/gnu-libsigsegv/ci-distcheck/-/jobs?scope=finished
  This one will catch only the most blatant mistakes.
* On many platforms:
  https://github.com/gnu-libsigsegv/ci-check/actions
  This one catches platform-specific bugs.