升级到VS2010：随机未解析的符号
我刚刚从 Visual Studio 2008 转到 2010，在解决所有问题后，我的项目运行得非常完美。
然而，有时项目会抱怨未解析的符号。当我重建导致问题的对象时，问题再次解决，至少直到我再次编辑和编译项目的一部分。
该解决方案包含Lua项目并将其编译为dll。游戏引擎项目使用Lua，游戏项目也这样做，这样它就可以注册必要的游戏功能。当然，游戏项目也链接到游戏引擎项目。
总是游戏项目无法解析Lua项目符号。
据我所知，引用和依赖项设置正确。
谢谢
I just went from visual studio 2008 to 2010, and after solving all issues my project runs perfectly.
However sometimes a project is complaining about unresolved symbols. When I rebuild the objects causing the issues the problem is solved again, at least until I edit and compile part of the project again.
The solution contains the Lua project and compiles it as dll. A game engine project uses Lua, and the game project also does this so it can register necessary game-functions. The game project also links to the game engine project of course.
It's always the game project being unable to resolve Lua project symbols.
References and dependencies are set correctly as far as I can see.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
只是预感：
您是否使用“最小重建”标志？这个对我来说很少起作用，因为它似乎取决于你的项目/包括以某种未知的、神秘的方式设置。 ;)
VS2010 中可能发生了一些变化，打破了这些假设。
Just a hunch:
Are you using the "minimal rebuild" flag? That one has seldom worked well for me, as it seems to depend on your project/includes being set up in some unknown, mysterious way. ;)
Something might've changed going into VS2010 that breaks these assumptions.
听起来你的系统上的某些东西正在破坏（可能截断）静态导入库。仔细检查您的防病毒软件。
另一种可能性是修改现有文件而不是创建新文件的构建步骤（例如，使用库管理器将对象添加到静态库）。在这种情况下，当重新编译 DLL 时，会在没有对象的情况下重新创建静态导入库，但具有较新的时间戳，并且不会触发重建。解决方案是对合并库使用与用于创建它的静态导入库不同的名称。
It sounds like something on your system is corrupting (perhaps truncating) the static import library. Take a good close look at your antivirus.
Another possibility is a build step that modifies an existing file instead of creating a new one (e.g. using the librarian to add objects to a static library). In this case when the DLL is recompiled, the static import library is recreated without the objects, but has a newer timestamp and doesn't trigger a rebuild. The solution is to use a different name for the merged library than the static import library used to create it.
不确定是否相关，但 VS2010 开始在其错误输出窗口中显示 C++ 的智能感知错误。特别是在 x64 构建中，我看到很多实际上来自系统头文件的内容。我的项目仍然可以完美地编译和运行。这些是智能感知错误还是构建错误？
Not sure if it's related, but VS2010 started showing intellisense errors for C++ in it's error output window. Especially in x64 builds, I have seen a lot of lot of these that are actually coming out of the system header files. My projects still compile and run flawlessly. Are these intellisense errors or build errors?