libsigc++ : The Typesafe Callback Framework for C++
Introduction
libsigc++ implements a typesafe callback system for standard C++. It allows you to define signals and to connect those signals to any callback function, either global or a member function, regardless of whether it is static or virtual.
libsigc++ is used by gtkmm to wrap the GTK+ signal system. It does not depend on GTK+ or gtkmm.
See the libsigc++ web site
License
Distribution of library and components is under the LGPL as listed in the file COPYING. Examples and tests are Public Domain.
Compatibility
Compatible compilers must support C++17, such as the decltype(auto) specifier (from C++14) and std::invoke().
Build
Whenever possible, you should use the official binary packages approved by the supplier of your operating system, such as your Linux distribution. For instance, Ubuntu Linux, Debian Linux and Fedora Linux have official libsigc++ packages.
Building from a release tarball
Building from the libsigc++ release tarball is easier than building from git.
It's easiest to build with Meson, if the tarball was made with Meson, and to build with Autotools, if the tarball was made with Autotools. Then you don't have to use maintainer-mode.
How do you know how the tarball was made? If it was made with Meson, it contains files in untracked/build_scripts/, untracked/docs/ and possibly other subdirectories of untracked/.
Building from a tarball with Meson
Don't call the builddir 'build'. There is a directory called 'build' with files used by Autotools.
For instance:
# If the tarball was made with Autotools, and you want to rebuild the reference
# documentation, you must enable maintainer-mode:
$ meson --prefix=/usr/local --libdir=lib -Dmaintainer-mode=true your_builddir .
# If the tarball was made with Meson, or you don't want to rebuild the docs:
$ meson --prefix=/usr/local --libdir=lib your_builddir .
# then:
$ cd your_builddir
$ ninja
$ ninja install
# You can run the tests like so:
$ ninja testBuilding from a tarball with Autotools
For instance:
# If the tarball was made with Autotools:
$ ./configure --prefix=/usr/local
# If the tarball was made with Meson, you must enable maintainer-mode:
$ ./autogen.sh --prefix=/usr/local
# then:
$ make
$ make install
# You can build the examples and tests, and run the tests, like so:
$ make checkBuilding from git
Building from git can be difficult so you should prefer building from a release tarball unless you need to work on the libsigc++ code itself.
jhbuild can be a good help. See the jhbuild repo and the jhbuild wiki.
Building from git with Meson
You must have Meson properly installed (meson, ninja, etc) and you will also need mm-common version 1.0.0 or higher.
Maintainer-mode is enabled by default when you build from a git clone.
Don't call the builddir 'build'. There is a directory called 'build' with files used by Autotools.
$ meson --prefix=/usr/local --libdir=lib your_builddir .
$ cd your_builddir
$ ninja
$ ninja install
# You can run the tests like so:
$ ninja test
# You can create a tarball like so:
$ ninja distBuilding from git with Autotools
You must have Autotools properly installed (autoconf, automake, etc) and you will also need mm-common.
$ ./autogen.sh --prefix=/usr/local
$ make
$ make install
# You can build the examples and tests, and run the tests, like so:
$ make check
# You can create a tarball like so:
$ make distcheck
# or
$ make distBuilding from git with CMake
The CMake build is not used very often by the libsigc++ developers, but it should work, and we would welcome improvements.
For instance:
$ mkdir libsigcplusplus_build
$ cd libsigcplusplus_build
$ cmake path/to/libsigcplusplus
$ makeBuilding with Microsoft Visual C++
See MSVC_NMake/README.txt.