How to see which g ++ command lines Boost.Build calls (1.33.1)

I scratch my head, trying to understand why import libraries are not generated when creating Boost libraries on my machine. More specifically, creating DLL files works fine, but earlier I would (for example, before reinstalling my computer) correctly create import libraries.

Some specifications:

  • Boost 1.33.1
  • g ++ 4.3.3 TDM-1 for Windows
  • Creating using the gccMS Dos command-line toolbox
  • UnxUtils (after 14-04-03)

The command line that calls bjam.exe looks like this:

"C:\.../boost_1_33_1/tools/build/jam_src/bin.ntx86/bjam.exe" --debug-configuration -d2 -q --builddir=C:/.../trunk/XTemp/gcc.debug/boost_1_33_1 toolset=gcc threading=multi define=BOOST_WINDOWS define=_GLIBCXX__PTHREADS linkflags=-shared-libgcc runtime-link=shared variant=debug --v2  linkflags=-out-implib=boost_thread.lib

This used to work wonderfully and create the desired file boost_thread.lib, but no more. I really don’t know what is going on, and I would like to know exactly what the linker receives on the command line and what he thinks he should do with it .

Thanks,

Charles

+3
source share
1 answer

-d2should give you exactly what you are looking for. I am surprised that this did not work. It may be hidden in other posts. Try to exclude --debug-configurationand replace -d2with -d+2. The latter will be printed by bjam commands in addition to bjam debugging messages.

+3
source

Source: https://habr.com/ru/post/1720011/


All Articles