1
- # libsigc++ : The Typesafe Callback Framework for C++
1
+ # libsigc++
2
+ Typesafe Callback Framework for C++
2
3
3
- ## Introduction
4
+ # Introduction
4
5
5
- libsigc++ implements a typesafe callback system for standard C++. It
6
- allows you to define signals and to connect those signals to any
7
- callback function, either global or a member function, regardless of
6
+ libsigc++ (a.k.a. libsigcplusplus) implements a typesafe callback system for
7
+ standard C++. It allows you to define signals and to connect those signals
8
+ to any callback function, either global or a member function, regardless of
8
9
whether it is static or virtual.
9
10
10
11
libsigc++ is used by gtkmm to wrap the GTK signal system. It does not
@@ -13,8 +14,6 @@ depend on GTK or gtkmm.
13
14
sigc++-2.0 and sigc++-3.0 are different parallel-installable ABIs.
14
15
This file describes sigc++-3.0.
15
16
16
- See the [ libsigc++ web site] ( https://libsigcplusplus.github.io/libsigcplusplus/ )
17
-
18
17
## License
19
18
20
19
Distribution of library and components is under the LGPL as listed in the
@@ -25,7 +24,35 @@ file COPYING. Examples and tests are Public Domain.
25
24
Compatible compilers must support C++17, such as the decltype(auto) specifier
26
25
(from C++14) and std::invoke().
27
26
28
- ## Build
27
+ # General information
28
+
29
+ Web site
30
+ - https://libsigcplusplus.github.io/libsigcplusplus/
31
+
32
+ Download location
33
+ - https://download.gnome.org/sources/libsigc++/
34
+ - https://github.com/libsigcplusplus/libsigcplusplus/releases/
35
+
36
+ Reference documentation
37
+ - https://libsigcplusplus.github.io/libsigcplusplus/reference/html/
38
+
39
+ Tarballs contain reference documentation. In tarballs generated with Meson,
40
+ see the untracked/docs/docs/reference/html directory.
41
+
42
+ Discussion on GNOME's discourse forum
43
+ - https://discourse.gnome.org/tag/cplusplus
44
+ - https://discourse.gnome.org/c/platform
45
+
46
+ Git repository
47
+ - https://github.com/libsigcplusplus/libsigcplusplus
48
+
49
+ Bugs can be reported to
50
+ - https://github.com/libsigcplusplus/libsigcplusplus/issues
51
+
52
+ Patches can be submitted to
53
+ - https://github.com/libsigcplusplus/libsigcplusplus/pulls
54
+
55
+ # Building
29
56
30
57
Whenever possible, you should use the official binary packages approved by the
31
58
supplier of your operating system, such as your Linux distribution. For
@@ -34,8 +61,7 @@ packages.
34
61
35
62
## Building from a release tarball
36
63
37
- Building from the [ libsigc++ release tarball] ( https://github.com/libsigcplusplus/libsigcplusplus/releases )
38
- is easier than building from git.
64
+ Building from a release tarball is easier than building from git.
39
65
40
66
It's easiest to build with Meson, if the tarball was made with Meson,
41
67
and to build with Autotools, if the tarball was made with Autotools.
@@ -148,4 +174,4 @@ $ make
148
174
149
175
## Building with Microsoft Visual C++
150
176
151
- See MSVC_NMake/MSVC-Builds.md.
177
+ See [ MSVC-Builds.md ] ( MSVC_NMake/MSVC-Builds.md )
0 commit comments