The outputted libboost.a, however, only consists of libboost_log.a.
Sometimes, this can be worked around by also providing the list of dependencies in --boost-libs, but libboost_log_setup.a is not a standalone library, so this won't work.
Why not just take all .a files in stage folder as target library files?
Currently, the script only combines libraries provided in
--boost-libs
, by iteratingfor NAME in $BOOTSTRAP_LIBS; do
.However, boost binary has dependencies, e.g, if I build
log
, then here is what are actually built (by default),log
library and all its dependencies.The outputted
libboost.a
, however, only consists oflibboost_log.a
.Sometimes, this can be worked around by also providing the list of dependencies in
--boost-libs
, butlibboost_log_setup.a
is not a standalone library, so this won't work.Why not just take all
.a
files instage
folder as target library files?