...
The various projects that contain C++ source are offered with both Windows IDE project files and autoconf-based Unix packages using the standard configure/make/make install sequence. Detailed information on source builds is available from the OS-specific pages linked on the Installation topic.
To obtain the latest code ahead of a tagged release, you'll need to check out the code on the latest branches in the various repositories. Do not rely on the trunk as it will normally be out of date. After checking out the branches for each project, you'll need to manually generate the configure script using the "bootstrap" shell script in the root of each project. Running this will require that a current set of autotools are installed.
| Code Block | ||
|---|---|---|
| ||
$ svn co https://svn.shibboleth.net/cpp-xmltooling/branches/REL_1 cpp-xmltooling
$ cd cpp-xmltooling
$ autoreconf -if
$ ./configure
$ make dist
|
The Makefiles are known to break on relatively out of date versions of autotools. Errors related to "doxygen" are normally a sign that you need to generate the relevant files on a newer system. You can use the "make dist" command to generate a tarball and then transfer it to an older system for building.
Note that in most cases the snapshot from subversion will generate a newer version of the package than is generally available, once changes have been made to the branch. This is a signal that you're using unreleased/unsupported code at your own riskThere's also a page describing the overall C++ development process.