Go to file
2012-05-09 18:56:08 +10:00
build-aux Fix errors found by api-sanity-autotest 2011-11-25 17:16:19 +11:00
docs examples: add ipc client/server 2011-10-23 22:40:26 +11:00
examples Add some special commands into the ipc example 2012-04-30 15:49:42 +10:00
include Add the event queue length to the connection stats. 2012-05-01 13:22:16 +10:00
lib Test for log facility names 2012-05-09 18:56:08 +10:00
tests IPC: fix retrying of partial recv's and sends. 2012-05-03 21:24:02 +10:00
.gitignore check: add abi checking script 2011-11-22 17:11:02 +11:00
autogen.sh libtool and code re-structure 2010-04-15 23:25:29 +10:00
check Fix typo in ./check 2012-05-01 12:15:15 +10:00
coding_style.txt Add the coding style definition file. 2010-07-06 12:45:46 +10:00
configure.ac Get the example socket includes right. 2012-04-04 09:51:28 +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 Make "make (s)rpm" work more reliably 2012-04-30 15:09:55 +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.