Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

C library for interaction with a Burrow server

branch: master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 config
Octocat-spinner-32 docs
Octocat-spinner-32 examples
Octocat-spinner-32 libburrow
Octocat-spinner-32 m4
Octocat-spinner-32 support
Octocat-spinner-32 tests
Octocat-spinner-32 .gitignore
Octocat-spinner-32 AUTHORS
Octocat-spinner-32 COPYING
Octocat-spinner-32 ChangeLog
Octocat-spinner-32 INSTALL
Octocat-spinner-32 NEWS
Octocat-spinner-32 README
Octocat-spinner-32 valgrind.suppressions

This project provides an asynchronous C library for interacting with a Burrow
message queue server. See:


This is an early-release version of the library. Major functionality is
in place, and functional, but there are doubtless bugs, quirks, kludges,
and goblins hiding in the code.

Use with caution.

Maintainer Setup

If you didn't download this as a tarball, you probably pulled it from
a souce-control repository. In that case, please run:

  # ./config/
That'll setup the autotools environment.


Now that your autotools environment is set up (or if you downloaded this
as a tarball), please run:

  # ./configure
  # ./make && ./make install

To install the library.


Tests are located in the tests/ subfolder. To run test applications, please run:

	$ make check

This will compile and run test files. (Note: new files must also be added to, by modifying check_PROGRAMS).

You may find yourself wanting to run a test in gdb. You may find yourself
wanting to run code coverage. Well, we can do all this and more!
Supported commands of further interest:

  $ make check-valgrind  # run tests thru valgrind
  $ make check-gdb       # run tests thru gdb
  $ make lcov            # run tests and calculate line coverage
                         # make sure you first ./configure --enable-coverage

Functional Tests

These haven't been implemented yet, but eventually will, under examples/
More notes to come in the future.
Something went wrong with that request. Please try again.