Building
FUSE Message Broker C++ Client uses the Autotools as its build tool for unix based operating systems, and includes Visual Studio 2005 project files for Windows users. The latest trunk code even has experimental support for building directly from Maven although its still not quite ready for prime time.
Prequisites
Required:
On Both Windows an Unix OS’s you need the following:
- A build of the Apache APR libraries, both APR and APR-Util, each of which must be version 1.3 or higher.
- A build of CPPUnit v1.10.2 or higher if you want to run the Unit Tests.
On Windows you will also need:
- Visual Studio 2005 or higher.
- The Platform SDK if using an Express version of Visual Studio.
On a Unix type OS you will also need:
- Autoconf v2.61 or higher.
- Automake v1.10 or higher.
- libtool v1.5.24 or higher.
- libuuid.
Once you have have all the build requirements: * Get the latest Source.
Building on a Unix type OS
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:
./configure
For more help on how to customize the build configuration, run:
./configure --help
Once the configure script has run successfully, you are ready to build. Run:
make
This will build all of the core FUSE Message Broker C++ Client source code. To build and install the code into the system directories, run:
make install
You will have to become the superuser in order to be able to install the files. If you’d first like to build and run the provided unit tests then you can run:
make check
Building in Visual Studio:
Before you can build with Visual Studio there are three environment variable that you must set in order for the build to succeed. These environment variables tell the solution where to find the dependancies needed by the FUSE Message Broker C++ Client library. The environment variable are:
- APR_DIST - This tells us where your build of APR and APR-Util are located.
- CPPUNIT_DIST - This tells us where your CPPUnit build is located.
- PLATFORM_SDK - If you are using an express version of Visual Studio this points to your install of the Platform SDK.
Once you have set these values you can open the included Visual Studion solution file and build the project. There are builds defined in the solution for debug and release version of the library in both static and DLL form. Also you may choose the platform type 32bit or 64 bit.