Re: [doc] b2 headers
Robert Ramey via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <[email protected]> |
On 4/9/18 10:27 AM, Steven Watanabe via Boost-build wrote: > AMDG > `b2 headers` is not really intended for end users. > It's only relevant when working from git as the > packaged releases have all the headers moved into > boost/ to begin with. As a result, the obvious > places to put this documentation (the getting started > guide and `b2 --help` from $BOOST_ROOT) are not really > correct. LOL - THIS end user uses github from my machine. I invoke b2 headers as needed. OK - you're going to argue that I'm not a typical end user. I don't kno about that. But this is a great way of working. We should encourage users to connect to github directly. The idea of downloading a huge monolithic boost distribution on from time to so last century. > Also, most of the time, you don't need to care > about `b2 headers`. Running b2 in $BOOST_ROOT > will build the headers in addition to putting > the libraries in stage/lib. For internal use > such as Boost tests and examples, the necessary > headers will be created automatically. Hmmm - I never trusted that, but if you say so ... > >> But, as long-time Boost.Build users, I dare to judge this is an >> excellent example of why peole hate this awesome build system :) Right - unfortunately you're not alone. I think the build system lacks clarity regarding whom it is trying to serve, what it's proper scope is and what it is supposed to do. Robert Ramey _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build