boost build lacks <library>/boost//log, <library>/boost//log_setup

[Trey Van Riper <vanriper.trey@…>]

If you create a Jamfile.jam file such as the following:

import boost ;
boost.use-project ;
exe test : [ glob src/*.cpp ] : <library>/boost//system <library>/boost//thread <library>/boost//log <library>/boost//log_setup

Boost build cannot find the library (presume I've configured Jamroot.jam to point to boost).

I was able to fix this by going to the boost build's src/contrib/boost.jam file, jump to line 216 (within rule boost_std), and add the following two lines:

boost_lib_std log        : BOOST_LOG_DYN_LINK ;
boost_lib_std log_setup  : BOOST_LOG_SETUP_DYN_LINK ;

[Trey Van Riper <vanriper.trey@…>]

Looks like I should have used BOOST_LOG_DYN_LINK instead of BOOST_LOG_SETUP_DYN_LINK, if I'm reading documentation correctly. It worked for me because I am statically linking, I assume.

[Andrey Semashev]

tools/build/src/contrib/boost.jam is part of Boost.Build, so I'm reassigning the ticket. I'm not sure what that file contains.

BOOST_LOG_DYN_LINK and BOOST_LOG_SETUP_DYN_LINK control how Boost.Log (the two built libraries it consists of) is linked. If the macro is defined, the corresponding library is linked as a shared object (.so or .dll), otherwise as a static library. If you're linking statically, you should not define either of these macros.

[anonymous]

An interesting question comes to mind... how does a new boost library add its lib to this file?

[Andrey Semashev]

BTW, I can see those boost_lib_std lines are already present in the file in lines 217-218 in 1.64, current master and develop. So maybe this ticket should be closed.

[vanriper.trey@…]

Hrm, perhaps I picked up a different branch or something. I've found other problems, so perhaps I need to pull again.

[Andrey Semashev]

I'm closing the ticket as the requested lines are already present.