Boost Interest :
From: troy d. straszheim (troy_at_[hidden])
Date: 2008-06-17 11:36:25
> I can see how these CMake specifics can be very confusing to someone that is
> not used to CMake. It seems like it would be easier to have a testing
> configuration file that specifies the necessary configuration options. For
> example, we could have "BoostTestingSlave.cmake" with the following contents:
> # BoostTestingSlave.cmake
> set(BOOST_BUILD_SLAVE ON CACHE BOOL "Documentation ..." FORCE)
> set(BOOST_BUILD_TESTING ON CACHE BOOL "Documentation ..." FORCE)
> With a config file, the user would not be required to manually edit cache
> variables (and reconfigure, etc). The process would look something like
> 1) Checkout sources:
> svn co https://somerepo somerepo
> 2) Create build directory:
> mkdir build
> 3) Configure build directory:
> cd build
> cmake -C BoostTestingSlave.cmake ../somerepo
> 4) Everything is ready to build!
Yeah, that could be a good way to go. The two-step configuration is a hassle.
Let me give it a shot.