Go to file
Angus Salkeld d48ed76dfd TEST: fix the map load test.
Signed-off-by: Angus Salkeld <asalkeld@redhat.com>
2011-10-23 13:36:07 +11:00
build-aux use latest git-version-gen from gnulib 2011-05-24 09:31:46 +10:00
docs Initial map using either a skiplist or a hashtable 2011-08-22 14:11:43 +10:00
include LOG: add stdarg to qblog.h 2011-10-23 13:36:07 +11:00
lib LOG: check for SCHED_IDLE 2011-10-23 13:36:07 +11:00
tests TEST: fix the map load test. 2011-10-23 13:36:07 +11:00
.gitignore adjust .gitignore so "git status" ignores all build artifacts 2011-05-24 09:44:56 +10:00
autogen.sh libtool and code re-structure 2010-04-15 23:25:29 +10:00
check Add a ./check mock 2011-10-23 13:35:45 +11:00
coding_style.txt Add the coding style definition file. 2010-07-06 12:45:46 +10:00
configure.ac LOG: serialize the va_list, don't snprintf 2011-08-22 10:29:48 +10:00
COPYING Re-license to LGPL 2.1 2010-05-25 06:11:59 +10:00
INSTALL Initial Commit. 2010-03-11 14:19:39 +11:00
libqb.spec.in Fix references to README 2011-06-23 14:46:36 +10:00
Lindent Change Lindent options to break the procedure type. 2011-06-22 14:19:14 +10:00
Makefile.am Remove TODO from dist_doc_DATA 2011-07-14 10:40:43 +10:00
README.markdown Add some more content to the README 2011-07-13 11:34:03 +10:00

libqb

What is libqb?

libqb is a library with the primary purpose of providing high performance client server reusable features. It provides high performance logging, tracing, ipc, and poll.

We don't intend be an all encompassing library, but instead provide very specially focused APIs that are highly tuned for maximum performance for client/server applications.

For more information look at:

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/asalkeld/libqb.git

See Github

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 mailing list.
  • Contribute documentation, examples and test cases.
  • Contribute patches.
  • Spread the word.