如何看到g ++的命令行Boost.Build调用（1.33.1） [英] How to see what g++ command-lines Boost.Build invokes (1.33.1)

问题描述

我抓我的头，试图弄清楚为什么当我建立我的机器上的Boost库的导入库都不会产生。更具体地说，建设的DLL工作正常，但在那里我会pviously $ P $（即之前，我重新安装了机）正确生成导入库。

I'm scratching my head, trying to figure out why the import libraries are not generated when I build the Boost libraries on my machine. More specifically, building the DLLs works fine, but where I would previously (i.e. before I reinstalled my machine) generate the import libraries correctly.

一些规格：

• 升压1.33.1


• 先按g ++ 4.3.3 TDM-1版本的Windows


• 从MS-DOS命令行提示符 GCC 工具集建筑


• UnxUtils（14-04-03后）

命令行调用bjam.exe是这样的：

The command-line that invokes 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

这奇妙的使用之前的工作和生产所需的文件 boost_thread.lib ，但现在不是了。我真的不知道发生了什么事情和我想知道到底是什么连接器接收的命令行和它认为它应该用它来做

This used to work wonderfully before and produced the desired file boost_thread.lib, but not anymore. I really don't know what's going on and I would like to know exactly what the linker receives on the command-line and what it thinks it should do with it.

谢谢，

卡尔

推荐答案

的-D2 应该给你你正在寻找什么。我很惊讶，它已经没有工作。也许它隐藏在其他消息。尝试省略 - 调试配置和替换-D2 与 -d + 2 。后者将打印命令的bjam调用除了bjam的非调试消息。

The -d2 should give you exactly what you are looking for. I'm surprised it hasn't worked. Perhaps it is hidden in other messages. Try omitting the --debug-configuration and replacing -d2 with -d+2. The latter will print the commands bjam invokes in addition to bjam non-debug messages.

这篇关于如何看到g ++的命令行Boost.Build调用（1.33.1）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！