Boost logo

Boost :

Subject: Re: [boost] [1.38] CMake support added to release branch?
From: troy d. straszheim (troy_at_[hidden])
Date: 2009-02-01 14:23:20


John Maddock wrote:
>
> So they'll see the CMake files and just go ahead and use them without
> realising that something experimental made it into the release.

Yeah, that clearly would happen, so the boost-cmake build won't let you
proceed until you confirm that you understand the system is
experimental. It looks like this:

% cmake ../src
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done

-- 
##########################################################################
--  This cmake-based build system is currently under development.  The
--  bjam-based system is the 'standard' way to build boost.  To try
--  try out the cmake build, invoke CMake with the argument
--         -DCMAKE_IS_EXPERIMENTAL=YES_I_KNOW
--  Or use the gui to set the variable CMAKE_IS_EXPERIMENTAL to some value.
--  This will only be necessary the first time.
--
--  For more information on boost-cmake see the wiki:
--      https://svn.boost.org/trac/boost/wiki/CMake
-- 
--  Subscribe to the mailing list:
--      http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
-- 
--  And/or check the archives:
--      http://news.gmane.org/gmane.comp.lib.boost.cmake
-- 
-- 
##########################################################################
CMake Error at CMakeLists.txt:54 (message):
   Magic variable CMAKE_IS_EXPERIMENTAL unset.
-- Configuring done
of course we can tweak the message as necessary.  Maybe it should 
mention specifically to keep cmake chatter off of the main boost list.
> Has the 
> CMake code merged to release been rigorously tested
Yeah, as rigorously as one could given our resources (small)
> or do we at least 
> have a means to test it prior to release - for example to test the 
> library build process?
Sure...  just build boost with it.
-t

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk