Boost logo

Boost Interest :

Subject: Re: [Boost-cmake] 1.40.0.cmake5 (?) builds cleanly
From: Denis Arnaud (denis.arnaud_boost_at_[hidden])
Date: 2009-11-03 05:08:50

2009/11/2 troy d. straszheim <troy_at_[hidden]>

> Denis Arnaud wrote:
>> We could maybe tag that version to 1.40.0.cmake5, couldn't we?
> For reference, the head of that branch is now
> I'm willing to tag it up. Anybody else? There will probably be more build
> system back-ports though, I'm making good progress on some installation
> stuff that Brad has recently clarified.

I forgot to mention that I still have to apply two patches (provided in
attachment, but also available on my Fedora page: to alter the
configuration of CMake.
a) One is to uncomment the SOVERSION line (which, from my understanding, is
reported to fail on some platforms such as Mac), so that sonames can be
generated in the right way.
b) The other patch is to avoid building binaries (e.g., bcp, inspect). As I
have included all the possible combinations (BUILD_TESTS=NONE,
BUILD_BCP=OFF, etc), it should work for many versions of Boost-CMake.

Now, may I suggest a few enhancements, from a Fedora packaging perspective?

1. To enable the installation of the Boost libraries into the /usr/lib64
directory on 64bit Linux platforms, I currently use the

On Fedora, the RPM cmake-macro uses the "-DLIB_SUFFIX=64" directive (, though some
suggest ( to replace it
by the "-DLIB_INSTALL_DIR:PATH=%{_libdir}" directive (where %{_libdir} is
equal to either /usr/lib or /usr/lib64, depending on the platform).

So, I'd suggest that Boost-CMake supports one of those, as apparently KDE4
does (

2. To instruct CMake about the installation directory, I currently use ( the
"-DCMAKE_INSTALL_PREFIX=$RPM_BUILD_ROOT%{_prefix}" directive (where
%{_prefix} is equal to /usr). However, it has rpmlint (the RPM packaging
checker utility) to complain/warn about it:
$ rpmlint -i SPECS/boost.spec
SPECS/boost.spec:257: W: rpm-buildroot-usage %build %cmake
$RPM_BUILD_ROOT should not be touched during %build or %prep stage, as it
break short circuit builds."

Also, the "standard Fedora way" (used by KDE4: ?) is to
instruct make (not cmake), like for VERBOSE=1, where to install everything,
with "make install DESTDIR=$RPM_BUILD_ROOT".

So, if possible, I'd suggest that the installation directory may be
instructed at the installation stage, understood by make (and not only by


Boost-cmake list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at