Re: Including bjam code based on the address_model
Rene Rivera via Boost-build <[email protected]> Thu, 11 Jul 2019 06:50:35 -0500
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <CAHEh_GiMqs1P6AgcEdYhLLDFo-mjWqZDA64dtXeKGKQUF9novg@mail.gmail.com> |
On Thu, Jul 11, 2019 at 12:46 AM Edward Diener via Boost-build < [email protected]> wrote: > I do understand that the logic for 32-bit versus 64-bit setup may > already be in a toolset's jamfile, but this is not guaranteed for every > toolset. Even when it is in the toolset's jamfile it is rarely documented. Let's reset a bit.. Since it's the intel-win toolset you're mucking with lets make it support the toolset requirements directly first. And then we can find a way to support that use case. Supporting the requirements is as easy as: * Adding the extra "requirement *" argument to the init. Ex: < https://github.com/boostorg/build/blob/develop/src/tools/gcc.jam#L151> * Passing that to "check-init-parameters". Ex: < https://github.com/boostorg/build/blob/develop/src/tools/gcc.jam#L278> From there one can optionally add custom handling of default requirements. For example a default target-os: < https://github.com/boostorg/build/blob/develop/src/tools/gcc.jam#L284> -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build