[VS Community 2017]：致命错误LNK1104：无法打开文件'boost_python3-vc141-mt-x64-1_66.lib' [英] [VS Community 2017]: fatal error LNK1104: cannot open file 'boost_python3-vc141-mt-x64-1_66.lib'

问题描述

正如标题所说......

As the title says ...

while：

while :

• 
  

  
  链接器 - >输入 - >其他依赖项：boost_python3-vc141-mt-x64-1_66.lib（拼写清晰）

• Linker -> Input -> Additional dependencies : boost_python3-vc141-mt-x64-1_66.lib (is well spelled)

链接器 - >平台 - >活动（x64）

Linker -> Platform -> Active (x64)

链接器 - >常规 - >其他库目录：C：\ boost_1_66_0 \stage \ lib>

Linker -> General -> Additional Library Directories : C:\boost_1_66_0\stage\lib

任何想法为什么？

Any idea why ?

非常感谢您的贡献

Thanks a lot for your contributions

推荐答案

没有猜测？你还没提供太多信息。

Without guessing? You haven't really provided much information.

如果你不介意猜测，那么最明显的可能性是：

If you don't mind guesses then the most obvious possibilities are:

1）即使你说事情拼写正确，你在某个地方犯了一个错误。

1) Even though you say things are spelt correctly, you made a mistake somewhere.

2）你没有把设置放到正确的配置中。属性的配置可能与为Visual Studio本身选择的配置不同。

2) You didn't put the settings into the correct configuration. The configuration for the properties can be different to the configuration selected for Visual Studio itself.

如果要测试，可以使用#pragma指令。
#pragma comment 指令允许您指定要链接的库而不将其添加到项目属性。您也可以指定库的完整路径。因此您可以使用它作为测试方法确保你的路径和名称
正确。

If you want to test, you can use the #pragma directive. The #pragma comment directive allows you to specify a library to link against without adding it to the project properties. You can also specify the full path to the library too. So you can use this as a way to test to make sure that you have the path and name correct.

#pragma c的语法omment指令是：

The syntax for the #pragma comment directive is:

#pragma comment(lib, "full path to library")

所以试试这个也是

这篇关于[VS Community 2017]：致命错误LNK1104：无法打开文件'boost_python3-vc141-mt-x64-1_66.lib'的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！