Re: [doc] b2 headers
Mateusz Loskot via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <CABUeae83Bw2XZoij+Qe102Q-oRZxjQn7LO77FgaTGqBDxCfneQ@mail.gmail.com> |
On 9 April 2018 at 18:49, Mateusz Loskot <[email protected]> wrote: > On 9 April 2018 at 16:09, Rene Rivera <[email protected]> wrote: >> On Mon, Apr 9, 2018 at 8:35 AM, Mateusz Loskot <[email protected]> wrote: >>> >>> The magic of https://www.google.com/search?q="b2+headers" >>> brought this page to my attention: >>> https://www.boost.org/doc/libs/master/tools/boostdep/doc/html/ >>> where, to my surprise, I find one of best intro to the concept >>> of modular Boost including very helpful explanation of the virtual >>> /boost directory and role of b2 headers command. >>> >>> Why this kind of information is presented in docs for somewhat >>> exotic to Boost (end)users command, I have no idea. >>> But, as long-time Boost.Build users, I dare to judge this is an >>> excellent example of why people hate this awesome build system :) >> >> >> "b2 headers" is an entirely Boost C++ Libraries specific construct and other >> than using b2 has nothing to do with b2 itself. > > Fair. > > The b2doc makes sense > > " > target > All tokens that are neither options nor properties specify what > targets to build. > " b2 --toolset=gcc-5 This works as expected, of course, and does it work due to this rule? " properties (...) Syntactically, all command line tokens with an equal sign in them are considered to specify properties. " IOW, equal sign has higher priority, and -- is discarded, so it is a property, not an option. Correct? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build