"John Maddock" <john@johnmaddock.co.uk> wrote:
David Abrahams wrote:
Jody Hagins <jody-boost-011304@atdesk.com> writes: In BBv1 there was
"pass --without-python to suppress this message in the future"
in the message. If that's been dropped for v2 it should probably be reinstated.
OK, but none of this addresses the basic issue: why is BBv2 scanning these Jamfiles in the first place, when it manifestly is not building these lib's or anything dependent upon them?
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. Cheers, Walter Landry wlandry@ucsd.edu