blocks|key|3152480|text|对此的简单解释是，您只是忘记了导出任何内容。如果没有导出，链接器将不会创建.lib/.exp文件。您可以通过在DLL上运行dumpbin.exe+/exports来验证这一点。带着你什么也看不见的期望。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3152481|使用__declspec(dllexport)从DLL中导出符号。或.def文件。|3152482|entityMap^0|1P|K|0|2|L|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

The simple explanation for that is that you just forgot to export anything. The linker won't create a .lib/.exp file if there are no exports. You can verify this by running <code>dumpbin.exe /exports</code> on the DLL. With the expectation that you see nothing.

Use <code>__declspec(dllexport)</code> to export symbols from the DLL. Or a .def file.

blocks|key|2320225|text|问题是DLL2只有.h文件，在任何相关的.cpp文件中都没有内容。所以集成开发环境并没有意识到创建.lib文件的必要性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2320226|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The problem was that DLL2 had only .h files and no content in any of the associated .cpp files. So the IDE didn't see the neccesity of creating the .lib file.

blocks|key|413217|text|我刚刚发现了另一种方法来导致同样的事情发生。我将一些在另一个DLL中作为服务例程开发和测试的例程移到了它们自己的DLL中。由于在我编写第一行代码之前就计划好了这一步，它们没有被标记为导出，因此使用了该项目的默认调用约定__cdecl。当我构建这个库时，构建环境并没有创建.LIB文件。经过一些调查，并受到本主题中提到的__declspec(dllimport)的启发，我意识到，尽管我将声明移动到了由新建项目向导生成的模板头文件中，但我忘记将生成的调用约定宏的名称插入到原型中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|413218|通过在包含实现的头文件和CPP文件中指定调用约定，我得到了预期的.LIB文件。|413219|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just discovered another way to cause the same thing to happen. I moved some routines that I developed and tested as service routines in another DLL into a DLL of their own. Since this move was planned before I wrote the first line of code, they weren't marked for export, and were, hence, using that project's default calling convention, __cdecl. When I built the library, the build environment didn't create a .LIB file. After some investigation, and inspired by the mention of __declspec(dllimport) in this topic, I realized that, although I moved the declarations into the template header file generated by the New Project Wizard, I forgot to insert the name of the generated calling convention macro into the prototypes.

With the calling convention specified, both in the header and the CPP files that hold the implementations, I got the expected .LIB file.

So, I have a c++ solution which contains 3 project ( 2 DLL, and 1 .exe).

here's the basic dependencies representation:

Application --> DLL2

Application --> DLL1

DLL2 --> DLL1

The problem I have is that DLL2 (when building it) does generate the .dll but doesn't generate the .lib and .exp I need to reference properly DLL2 in the Application project. However, DLL1 does generate these files and I've compared DLL1's settings to DLL2's, and I can't find what the difference could be.

DLL Project doesn't generate .exp and .lib file

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

因此，我有一个包含3个项目(2dll和1个.exe)的c++解决方案。下面是基本的依赖关系表示：应用程序--> DLL2应用程序--> DLL1DLL2 --> DLL1我遇到的问题是，DLL2 (在构建它时)确实会生成.dll，但不会生成我需要在应用程序项目中正确引用DLL2的.lib和.exp。然而，DLL1确实生...

问DLL项目不生成.exp和.lib文件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问DLL项目不生成.exp和.lib文件EN