mirror of
https://salsa.debian.org/ha-team/libqb
synced 2026-02-01 17:50:12 +00:00
It also means the missing key specification is now a hard error when ASCII armored files are to be created (directly or by other rules). Leveraging the previous commit, it is now unnecessary to guard against release mode not being requested, so this guard is dropped completely in the transition, allowing for the full-fledged (incl. GPG signing) release delivery testing without mangling with in-tree tags. To allow "sign" target to (possibly eventually) become the implicit goal even if "gpgsignkey" variable is explicitly unspecified, make it depend on "tarballs". Signed-off-by: Jan Pokorný <jpokorny@redhat.com> |
||
|---|---|---|
| .tito | ||
| build-aux | ||
| docs | ||
| examples | ||
| include | ||
| lib | ||
| m4 | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .tito.spec.tmpl | ||
| .travis.yml | ||
| autogen.sh | ||
| check | ||
| coding_style.txt | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| libqb.spec.in | ||
| Lindent | ||
| Makefile.am | ||
| README.markdown | ||
libqb
What is libqb?
libqb is a library with the primary purpose of providing high-performance, reusable features for client-server architecture, such as logging, tracing, inter-process communication (IPC), and polling.
libqb is not intended to be an all-encompassing library, but instead provide focused APIs that are highly tuned for maximum performance for client-server applications.
For more information, see:
-
You can build it yourself with the following commands:
$ make doxygen $ firefox ./doc/html/index.html
Dependencies
- glib-2.0-devel (If you want to build the glib example code)
- check-devel (If you want to run the tests)
- doxygen and graphviz (If you want to build the doxygen man pages or html manual)
Source Control (GIT)
git clone git://github.com/ClusterLabs/libqb.git
Installing from source
$ ./autogen.sh
$ ./configure
$ make
$ sudo make install
How you can help
If you find this project useful, you may want to consider supporting its future development. There are a number of ways to support the project.
- Test and report issues.
- Help others on the developers@clusterlabs.org mailing list.
- Contribute documentation, examples and test cases.
- Contribute patches.
- Spread the word.

