Subject: Re: [Boost-build] Python port development
From: Vladimir Prus (ghost_at_[hidden])
Date: 2010-07-09 01:48:28
On Thursday 08 July 2010 22:48:48 Michael Jackson wrote:
> On 7/8/10 2:35 PM, in article 4C361A5A.6050302_at_[hidden], "Stefan
> Seefeld" wrote:
> > Let me copy&paste some high-level bits (from the above link) her:
> > Why? ¶ <https://trac.lvk.cs.msu.su/boost.build/wiki/PythonPort#Why>
> > Boost.Build V2 is mostly implemented in the interpreted language of the
> > underlying build tool, and it has a number of problems:
> > * No user knows that language, making it hard to extend Boost.Build
> > or become new developer.
> > * The language is strange at times, and not very nicely documented.
> > * There's no standard libraries, so every new functionality should
> > be implemented from scratch
> > * The only data structure in the language is list of strings. This
> > makes many tests cumbersome, and leads to excessive memory
> > consumption and poor performance on some workloads.
> > Stefan
> And for all those reasons the CMake build system was implemented for the
> boost project. It is done, works and is proven.
... and unmaintained? And because it's unmaintained, it's not even possible
to prove that cmake gets the same test results on all targets. Yeah, proven ;-)
Also, most of the concerns about the language listed above equally applies
to CMake -- it has crazy language that has no use whatsoever outside cmake.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk