From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-06-14 20:50:45
> Hmm, this post is larger than I thought, so I'll leave this
> here for now except to quicky say I've posted this here since
> I believe it is a build question, although underneath it all,
> it may apply to the design of Boost, etc. Lastly, if I'm
> really off base in any or all of the above, then it's
> probably so that a lot of the above is non-questions
> or totally off-base statements and so probably won't
> warrant a detailed answer. Either way, thanks in advance
> for any insights.
Nothing wrong with your concerns, but I don't think this is really a
question having to do with the build tools so much as with the
philosophy behind various libraries' use of platform features.
Actually, multiple philosophies, since the libraries differ in that
respect. As such, I think it would be more appropriately posted to
the main Boost list.
(FWIW, the Boost.Python library always ends up with a superset of the
dependencies induced by <Python.h>. Furthermore like most of the
other Boost libraries, it builds as a DLL, which, on Windows, means
the use of non-standard extensions for all practical purposes).
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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