A developers' log is provided (and should be updated) under the <a href="http://sourceforge.net/projects/quantity/develop> wiki facilities of project.
Each of the source code directories includes a subdirectory test
which contains test programs. Documentation sources are located in subdirectory documentation
. Supporting macros for the build system are located in subdirectory m4
.
After installation, the following directories are generated and populated:
<_install_directory_>/include/Quantities-<versionnumber>/Quantities
: the header files in the respective subdirectories<_install_directory_>/lib/Quantities-<versionnumber><libtag>
: the (possibly static and shared) libraries; libraries with different libtags are thus installed into different directories. If the libtag is different from an empty string, this encodes the fact whether the library contains debugging information (-d) or is optimized (-o). Selection of a library with particular properties defined by the libtag is easily done by selecting the respective directory.<_install_directory_>/share/Quantities-<versionnumber>
: the documentation files, including the doxygen tag file, and the html as well as the latex subdirectories.Thus, the installed file layout looks like this:
<_install_directory_>
+- include
| +- Quantities-<versionnumber>
| | +- Quantities
| | +- Quantity
| | +- PhysicalQuantities
| | +- GeneralQuantities
| | +- MathematicalQuantities
+- lib
| +- Quantities-<versionnumber>
| +- Quantities-<versionnumber>-o
| +- Quantities-<versionnumber>-d
| +- Quantities-<versionnumber>-o-d
+- share
| +- Quantities-<versionnumber>
Additional functionality is imported through the boost.m4 macros, which have been adapted slightly (boost_BS.m4).
With the recent autotools (see above), it is no longer necessary to use the bootstrap skript after downloading the cvs code. Rather,
autoreconf --install
After this, the common
./configure <options> make make install make check make doc make doc-install
As also mentioned above, libraries compiled and linked according to various configure
options may be installed in the respective subdirectories in the <_install_directory_>/lib
tree. It is important to purge the object files generated by the compilation step, before it is attempted to compile code with different options with
make clean
Note that for linking versions of Quantities with debug information or optimization enabled, the respective versions of the BSUtilities libraries must be available.
The following suggestions are provided for testing:
make distcheck
for testing<_source_directory>/*/test
make doc
.You should also set the recommended version number of BSutilities to be used in
back to Quantities start page