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
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
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
I've been running with the following snippet in my boost build
directory for a while.
IF(CMAKE_COMPILER_IS_GNUCXX)
IF(APPLE)
ADD_DEFINITIONS(${CMAKE_CXX_FLAGS} "-gdwarf-2")
ENDIF(APPLE)
# At some point in the future, this won't be requied to silence an
# error message for boost, b
