Re: [Boost-cmake] [PATCH] building Boost.Python fails

Subject: Re: [Boost-cmake] [PATCH] building Boost.Python fails
From: Bill Hoffman (bill.hoffman_at_[hidden])
Date: 2009-09-17 09:05:28

troy d. straszheim wrote:

> Well, there was some discussion about this over on the -dev list.  I 
> would like to have cmake removed completely from boost svn to avoid 
> confusion.   Vladimir Prus has pointed out that the locations of the 
> cmakefiles violate some code-organization standards.
> 
> Due to the way boost does its releases, the trunk version would have to 
> be actively maintained by somebody.  Apparently one can't just commit to 
> release without committing to trunk, as it confuses a crucial 
> merge-tracking tool that the release managers use, and then the cmake 
> effort holds up the release process and inflicts pain on people who 
> neither know nor care about cmake.   This is bad.  It is also clear that 
> it wouldn't be productive to further discuss version control, testing, 
> buildsystems, modularization etc. on the -dev list... I'm not about to 
> publish a "manifesto" (if you don't get the reference, don't worry) and 
> be a troll.
> 
> OTOH if somebody wants to take maintainership of the cmakefiles in the 
> boost SVN tree, great.  I'll continue to push tweaks to the git repo 
> where you can click-click-download patchfiles at will;  if the tweaks 
> make it to SVN first, no problem, git doesn't care.
> 
> To me, what makes most sense is, with the help of those on this list, to 
> just tune up the cmakefiles shortly after the release is frozen, and 
> release under separate cover.
> 

So, at boost con we talked about setting up CDash for Boost.   I think 
it would be much easier to maintain the CMake files for Boost if such a 
testing system were in place.

-Bill