
29 Jun
2006
29 Jun
'06
9:18 a.m.
Walter Landry wrote:
I feel like a borken record, but this would be solved if there was always an explicit configuration step before the actual build. That way, it is only during the one configuration step that you find out that python and ICU will not be available, rather than every single time you build. Many other libraries with lots of optional features operate this way.
I agree up to a point: but for bbv2 as a build system that claims to operate independently of Boost, it should not be "configuring" Boost lib's unless you're actually going to be building them. Currently every Boost lib that has a Jamfile gets parsed regardless of what you're building! Also sounding like a broken record yours, John.