Sean Chittenden wrote:
-DCMAKE_IS_EXPERIMENTAL=YES_I_KNOW \ <<< Is this necessary any
more?
Heh. No, not necessary any more. What an embarrasement.
Troy, will try 1.40 now and let you know. git or tarball? URL? -sc
git clone git://gitorious.org/boost/cmake.git src
cd src
git c
${CMAKE_COMMAND}
-DCMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER} \
-DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS} \
-DCMAKE_IS_EXPERIMENTAL=YES_I_KNOW \ <<< Is this necessary
any more?
-DDCMAKE_VERBOSE_MAKEFILE=true \
[...]
Erm. I'm glad it's Friday.
Quoting CMAKE_CXX_FLAGS fixed this:
Sean Chittenden wrote:
And when I build boost: I'm not longer seeing either of those post
1.40.0. Starting with cmake2, it looks like CMAKE_CXX_FLAGS ceased
working but I don't know how or why. Is there a better way to pass
CXX_FLAGS to boost? -sc
I just backported a ton of stuff from
Here's what I've got. There are several options controlling how things
are built and installed, here are short descriptions:
INSTALL_VERSIONED: mangle boost version into installed dirnames
So with INSTALL_VERSIONED off:
% cmake .. -DCMAKE_INSTALL_PREFIX=/tmp/local
install layout:
Headers:
Adding the ${CMAKE_CXX_FLAGS} to ADD_DEFINITIONS() seems redundant.to
me because CMAKE_CXX_FLAGS already sets definitions passed to the c++
compiler. I think this flag is more useful for setting
config-dependent flags, e.g. CMAKE_CXX_FLAGS_DEBUG and
CMAKE_CXX_FLAGS_RELEASE, but maybe others on the
troy d. straszheim wrote:
> Brad King wrote:
>> Perhaps the boost CMake code is not setting SOVERSION.
>
> Hmm. It isn't setting it on purpose... If I set either VERSION or
> SOVERSION on a module on the mac, I get:
[snip]
> ../../../lib/libboost_python-mt.1.41.0.dylib -framework Python
> i686-a
troy d. straszheim wrote:
> Ingmar Vanhassel wrote:
>> Excerpts from troy d. straszheim's message of Thu Oct 29 23:18:12
>> +0100 2009:
>>> I haven't forgotten about LIB_SUFFIX. It is footnoted in the
>>> exported targets section of the docs:
>>
>> I meant the cmake/ subdirectory, to avoid clutter
