在 WDK 构建中链接 boost lib 时发出警告(“LNK4217:本地定义的符号 _ 已在函数 _ 中导入”)

发布于 2024-08-08 00:54:08 字数 2503 浏览 8 评论 0原文

我正在使用 WDK 构建以下示例 boost 消耗用户模式应用程序,但在从同一终端窗口链接到我之前使用 bootstrap 和 .\bjam 构建的 boost 库时,出现以下错误。

IIUC,MSDN 说这是因为(可怕的是manged) 函数 - 它似乎是一个 C++ std lib 函数 - 被标记为 DLL 导入,但我有一个本地定义。这是怎么发生的?有办法解决这个问题吗?

另请参阅:松散相关的问题

C:\exp>more exp.cpp
#pragma warning(disable: 4512)
#include <boost/program_options.hpp>
int __cdecl main() {
  boost::program_options::options_description desc("Allowed options");
  return 0;
}

C:\exp>more sources
TARGETNAME=exp
TARGETTYPE=PROGRAM

USE_MSVCRT=1
USE_STL=1
USE_NATIVE_EH=1

MSC_WARNING_LEVEL=/W4 /WX

_NT_TARGET_VERSION= $(_NT_TARGET_VERSION_WINXP)

INCLUDES=..\boost_1_40_0

SOURCES=exp.cpp

UMTYPE=console
UMBASE=0x400000

TARGETLIBS = $(SDK_LIB_PATH)\ws2_32.lib ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt.lib

C:\exp>build
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\7600.16385.0\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Start time: Wed Oct 14 17:34:23 2009
BUILD: Examining c:\exp directory for files to compile.
   c:\exp
Invalidating OACR warning log for 'root:x86chk'
BUILD: Saving c:\winddk\7600.16385.0\build.dat...
BUILD: Compiling and Linking c:\exp directory
Configuring OACR for 'root:x86chk' - <OACR on>
_NT_TARGET_VERSION SET TO WINXP
Linking Executable - objchk_win7_x86\i386\exp.exe
1>errors in directory c:\exp
1>link : error LNK1218: warning treated as error; no output file generated
BUILD: Finish time: Wed Oct 14 17:34:44 2009
BUILD: Done

   1 executable built - 1 Warning - 1 Error

C:\exp>more *wrn
1>warnings in directory c:\exp
1>c:\exp\libboost_program_options-vc100-mt.lib(options_description.obj): warning LNK4217: locally defined symbol ??1?$basic_streambuf@DU?$char_traits@D@std@@@std@@UAE@XZ (public: virtual __thiscall std::basic_streambuf<char,struct std::char_traits<char> >::~basic_streambuf<char,struct std::char_traits<char> >(void)) imported in function "public: virtual __thiscall std::basic_stringbuf<char,struct std::char_traits<char>,class std::allocator<char> >::~basic_stringbuf<char,struct std::char_traits<char>,class std::allocator<char> >(void)" (??1?$basic_stringbuf@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@UAE@XZ)

I'm building the below example boost-consuming user-mode app with the WDK, but I'm getting the following errors when linking with the boost libraries that I built earlier using bootstrap and .\bjam, from the same terminal window.

IIUC, MSDN says it's because the (hideously mangled) function - which appears to be a C++ std lib function - is marked as a DLL import, yet I have a local definition. How did this happen? Is there a way to work around this?

See also: a loosely related question.

C:\exp>more exp.cpp
#pragma warning(disable: 4512)
#include <boost/program_options.hpp>
int __cdecl main() {
  boost::program_options::options_description desc("Allowed options");
  return 0;
}

C:\exp>more sources
TARGETNAME=exp
TARGETTYPE=PROGRAM

USE_MSVCRT=1
USE_STL=1
USE_NATIVE_EH=1

MSC_WARNING_LEVEL=/W4 /WX

_NT_TARGET_VERSION= $(_NT_TARGET_VERSION_WINXP)

INCLUDES=..\boost_1_40_0

SOURCES=exp.cpp

UMTYPE=console
UMBASE=0x400000

TARGETLIBS = $(SDK_LIB_PATH)\ws2_32.lib ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt.lib

C:\exp>build
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\7600.16385.0\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Start time: Wed Oct 14 17:34:23 2009
BUILD: Examining c:\exp directory for files to compile.
   c:\exp
Invalidating OACR warning log for 'root:x86chk'
BUILD: Saving c:\winddk\7600.16385.0\build.dat...
BUILD: Compiling and Linking c:\exp directory
Configuring OACR for 'root:x86chk' - <OACR on>
_NT_TARGET_VERSION SET TO WINXP
Linking Executable - objchk_win7_x86\i386\exp.exe
1>errors in directory c:\exp
1>link : error LNK1218: warning treated as error; no output file generated
BUILD: Finish time: Wed Oct 14 17:34:44 2009
BUILD: Done

   1 executable built - 1 Warning - 1 Error

C:\exp>more *wrn
1>warnings in directory c:\exp
1>c:\exp\libboost_program_options-vc100-mt.lib(options_description.obj): warning LNK4217: locally defined symbol ??1?$basic_streambuf@DU?$char_traits@D@std@@@std@@UAE@XZ (public: virtual __thiscall std::basic_streambuf<char,struct std::char_traits<char> >::~basic_streambuf<char,struct std::char_traits<char> >(void)) imported in function "public: virtual __thiscall std::basic_stringbuf<char,struct std::char_traits<char>,class std::allocator<char> >::~basic_stringbuf<char,struct std::char_traits<char>,class std::allocator<char> >(void)" (??1?$basic_stringbuf@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@UAE@XZ)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

忘年祭陌 2024-08-15 00:54:08

您在链接中明确包含 ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt.lib。

您应该让 boost auto_link 的内容配置执行正确的 #pragma comment(lib, ...) 内容,确保您引入正确的库并正确设置链接器搜索路径。最有可能的情况是 boost 库和您的代码链接到不同的运行时库。

You are explicitly including ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt.lib in the link.

You should let the boost auto_link stuff configure do the correct #pragma comment(lib, ...) stuff ensure you bring in the right library and set the linker search path correctly. The most likely thing is that the boost library and your code are linking against different runtime libraries.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文