From: codex653 (brandonbraun653_at_[hidden])
Date: 2019-06-04 17:42:57
Certainly! According to b2 -v, I'm on 2018.02, OS=LINUX. But my full boost
"package" version I'm compiling with is boost_1_70_0.
Ah yeah a minimal example will be difficult right off the bat. All my
targets currently are for STM32 chips and only support the embedded
environment, aka you would have to install the gcc_arm_none_eabi toolchain,
clone my repo, etc...If necessary I can come up with a variant that will do
this same behavior, but with the run of the mill gcc. I have plans to do
this anyways, so I wouldn't feel bad if you wanted it.
In lieu of that however, the latest variant of my project that I've been
working on can be found here on the master branch:
Try not to laugh too much at the jamfiles! I'm still learning!
I tried to build two variants of my executable target "valkyrie_stm32f4"
(Valkyrie/build.jam), one with the -Wl,--start-group flag and the other
without, and dumped the output at the -d2 level into
Valkyrie/normal_failing_link.txt and Valkyrie/start_group_failing_link.txt.
My gcc_arm_none_eabi.jam file can be found at:
I copy this into the actual boost-build toolchain src/tools directory on my
PC so that boost knows how to initialize it. That might not be the "best"
way of doing it, but it's working for now haha.
AHA! So I /did/ find the correct line that does the actual linking
command!!! I've been modifying the heck out of that in my
gcc_arm_none_eabi.jam file, even putting really stupid stuff that should
immediately break the linker, but yet somehow boost completely ignored every
change I made.
-- Sent from: http://boost.2283326.n4.nabble.com/Boost-Build-f2685023.html
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