Re: [Boost-cmake] disabling particular external dependencies

Subject: Re: [Boost-cmake] disabling particular external dependencies
From: Sean Chittenden (sean_at_[hidden])
Date: 2009-11-04 18:39:38

>> Is there anyway to disable building the python related code in boost?
>
> Yup, docs here:
>
> http://sodium.resophonic.com/boost-cmake/current-docs/externals/index.html

-DWITH_PYTHON=OFF

EXCELLENT!

btw, the new cmake boost 1.41 imports look *very* good so far.  The  
INSTALL_VERSIONED=ON broke a few things on my first pass, but all due  
to path issues.

I'd ideally like to make use of BOOST_INSTALL_CMAKE_DRIVERS and  
INSTALL_VERSIONED.  Is the intention to just include lib/Boost.cmake  
and have it take care of all of the pathing and version information  
depending on the results of find_package(Boost 1.41...) or some such?   
If lib/Boost.cmake can support multiple versions of boost installed,  
it would be *ideal* if the effort required to use boost were as simple  
as:

set(Boost_USE_MULTITHREADED ON)
set(Boost_MIN_VERSION 1.41)
set(Boost_SET_INCLUDE ON)    # Should default to ON, same concept for  
linker flags
include("${CONTRIBOBJ}/lib/Boost.cmake")
find_package(Boost ${Boost_VERSION} COMPONENTS thread NO_MODULE)
# no need for include(${Boost_INCLUDE_DIR}) with Boost_SET_INCLUDE=ON

Food for thought.  -sc

--
Sean Chittenden
sean_at_[hidden]