On *nix sytems, the build requires the libuuid library that is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net/ which is not always installed by default.
On Fedora/Red Hat/openSUSE, you should install the e2fsprogs and e2fsprogs-devel packages. On Debian/Ubuntu, you should install uuid and uuid-dev packages.
The package contains a complete set of CppUnit tests. In order for you to build an run the tests, you will need to download and install the CppUnit library. See http://cppunit.sourceforge.net/cppunit-wiki
On Fedora/Red Hat/openSUSE, you should install the cppunit and cppunit-devel packages. On Debian/Ubuntu, you should install the build-essential, libcppunit and libcppunit-dev packages.
Make sure that the paths to the installed CppUnit library and includes are visible in your current shell before you try building the tests.
Windows users will need to build the CppUnit library using the CppUnit MSVC project files. A discussion of the build process can be found on the CppUnit wiki under CppUnit build instructions this covers both MSVC along with many other platforms and tool suites.
With versions of ActiveMQ-CPP 2.2 and later, we have a dependency on the Apache Portable Runtime project. You'll need to install APR on your system before you'll be able to build ActiveMQ-CPP.
To Generate the ./configure script use to create the Makefiles, you need the following software installed:
You can also install the Doxygen and Graphviz packages if you want to generate the API documentation in HTML format.
This assumes you have all of the project dependencies installed. We're now ready to create the configure script. To do this, run:
This should be run the first time and anytime you change configure.ac or any of the Makefile.am files.
The configure script will customize the way the software is built and installed into your system along with detecting the available libraries that have been installed. To use the default configuration just run:
For more help on how to customize the build configuration, run:
Once the configure script has run successfully, you are ready to build. Run:
This will build all of the core ActiveMQ CPP source code. To build and install the code into the system directories, run:
You will have to become the superuser in order to be able to install the files.
To generate the doxygen documentation for the project, just run:
In order to build and run the suite of unit tests, run:
This will verify that the library is functioning correctly on the target platform. In addition, it will generate the integration tests binary.
The library also contains a set of tests that are run against a real AMQ broker. These allow you to validate this distribution of ActiveMQ CPP against your broker. Running these without a broker will result in failed tests. The tests currently hard-code the broker url to be tcp://localhost:61613 for stomp and tcp://localhost:61616 for openwire.
The integration tests are built via "make check". To run them, first start a broker and then
This will take quite some time to complete, so be patient.
There is an example application that ships with the distribution in src/examples. The example is compiled by default with the "make" command, but can easily be compiled manually using the command:
We support using the GNU compiler on Windows, using the Cygwin package. However we also support using the MSVC compiler on Windows.
There are a couple or things that you will need to setup to ensure that the MSVC compile succeeds.
The Project files reference the libraries described in the Dependencies section. To build successfully, you must either place these libraries in a directory listed in the project settings, or add a new location for your library directories.
If you're using MSVC >= 2008, it comes with the Windows SDK (so you don't need to download it separately).
For ActiveMQ-CPP >= 2.2, you will have to follow some special instructions for building APR, duscussed here.
If you are using Visual C++ < 2008, you need to download and install the Platform SDK if you don't have it installed already (the Platform SDK is called the "Windows SDK" since the release of Windows Vista). Once installed, do the following: