Re: Passing defines to b2 ?
Ken Moffat via Boost-build <[email protected]> Fri, 31 May 2019 18:50:31 +0100
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <CANVEwpY8Db4T6QJb6m7CaStNrNAHA5MZKHU1QH5u496NvHPv4Q@mail.gmail.com> |
On Fri, 31 May 2019 at 10:48, Mateusz Loskot via Boost-build <[email protected]> wrote: > > On Fri, 31 May 2019 at 11:44, Ken Moffat via Boost-build > <[email protected]> wrote: > > > > Now I'm looking at the first of the cheap hardening options (on gcc) : > > -D_FORTIFY_SOURCE=2 but b2 has a strong dislike of -D. > > b2 app optimization=full define=USE_ASM > > see that example (and explanation) in this section > https://boostorg.github.io/build/manual/develop/index.html#bbv2.tutorial.libs > > Best regards, > Thanks. For building boost itself, a quick partial build with a bit more than the things I'm currently testing: ./b2 stage cxxflags="-march=native -fstack-protector-strong" \ define=_FORTIFY_SOURCE=2 define=_GLIBCXX_ASSERTIONS threading=multi \ link=shared -d+2 showed the process works (all get added to the existing -O3). I've spelled that out in the hope google can find it - unfortunately most of my searching for b2 boost fortify came up with stuff about vitamins. And I've made a note of where the manual is. _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build