blocks|key|2860621|text|好吧，你不喜欢我另外两个想法……所以就这样..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2860622|你发货给你的客户一个“存根EXE”。存根EXE不依赖于其他任何东西，只包含一个ZIP文件(或安装包或类似的)，作为存根EXE中的资源。嵌入在存根EXE中的zip文件只包含实际程序EXE及其所有依赖的DLL。当存根EXE运行时，它只是将ZIP文件解压缩到临时子目录并启动应用程序EXE。|2860623|您可以对其进行优化，如果应用程序已经安装在%25TEMP%25中，那么您可以跳过解压缩步骤，只需启动已经存在的应用程序EXE。|2860624|就我个人而言，我不会走这条路。如果EXE有依赖项，只需给用户一个安装程序。但你比我更了解你的用户和客户。|2860625|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Ok, you didn't like either of my other two ideas... so here goes...

You ship and give your customers a "stub EXE". The stub EXE doesn't depend on anything else and just contains a ZIP file (or setup package or similar) as a resource in your stub EXE. The zip file embedded in the stub EXE just contains the actual program EXE and all its dependent DLLs. When the stub EXE runs, it just unpacks the ZIP file to a TEMP sub-directory and launches the application EXE.

You could optimize it such that if the app has already been installed in %TEMP%, then you skip the unpacking step and just launch the application EXE already present.

Personally, I wouldn't go this route. Just give the user an installer if the EXE has dependencies. But you know your users and customers better than I do.

blocks|key|1304956|text|您可以静态地链接可执行文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1304957|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|$]]

You could statically link the executable.

blocks|key|2501427|text|另一种选择是在GAC中安装DLL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2501428|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|$]]

One alternative is to install the DLL's in the GAC.

blocks|key|2501485|text|您没有提到DLL依赖项是什么。直接使用存根库的DLL吗？通过LoadLibrary动态加载？COM?需要注册吗？这个.NET中有一个吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2501486|需要考虑的几种选择。|2501487|将所有必需的DLL放在与EXE相同的目录中(这样就不必使用PATH变量)。安装只是一个“拷贝*.*”，或者只允许从一个文件共享中运行。(如果有.NET代码，则为YMMV--因为这在从远程文件共享运行时具有安全性限制)。|ordered-list-item|2501488|静态地将EXE链接到C-Runtime而不是dynamic选项(因此您不必在尚未安装MSVCRT的机器上重新处理MSVCRT)。|2501489|我有一些更疯狂的想法，如果上面的两个项目不够。让我知道。|2501490|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

You didn't mention what the DLL dependencies are. Just straight up DLLs with a stub lib? Dynamically loaded via LoadLibrary? COM? Registration required? Is any of this .NET?

Several options to consider.

<ol>
<li>Put the all the required DLLs in the same directory as the EXE (so you don't have to muck with the PATH variable). Installation is just a "copy *.*" or just allowed to run from a file share. (YMMV if there is .NET code - as that has security restriction when run from a remote file share).</li>
<li>Statically link the EXE with the C-Runtime instead of the dynamic option (so you don't have to redist the MSVCRT on machines that don't already have it installed).</li>
</ol>

I have some crazier ideas if the above 2 items don't suffice. Let me know.

blocks|key|2860597|text|显然，存在可以将DLL转换为LIB的软件，这样您就可以静态地链接到它，但是在这种情况下，这可能是过分的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2860598|entityMap|0|LINK|mutability|MUTABLE|url|http://www.binary-soft.com/dll2lib/dll2lib.htm^0|I|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Apparently there exists <a href="http://www.binary-soft.com/dll2lib/dll2lib.htm" rel="nofollow">software</a> that can convert a DLL to a LIB, so that you can link against it statically, but that might be overkill in this case.

Often my exe's have dll dependencies that I package with an installer like <a href="http://nsis.sourceforge.net/" rel="nofollow">nsis</a> or <a href="http://www.jrsoftware.org/isinfo.php" rel="nofollow">inno</a>.
This makes sense for large programs but is overkill for small scripts.

Is there an alternative way to bundle dependencies, so that the user can just execute a single exe and not require a directory of dll's in the PATH? 

 

EDIT

I am hoping for a solution that won't depend on the type of dll's, and will work for other kinds of dependencies too.

Here are some potential options:

<ul>
<li><a href="http://www.adontec.com/index.htm?GO=/runtimepacker_e.htm" rel="nofollow">http://www.adontec.com/index.htm?GO=/runtimepacker_e.htm</a></li>
<li><a href="http://boxedapp.com/" rel="nofollow">http://boxedapp.com/</a></li>
<li><a href="http://www.filetransit.com/view.php?id=16640" rel="nofollow">http://www.filetransit.com/view.php?id=16640</a></li>
</ul>

Does anyone have experience with a tool like this?

how to bundle dependencies in exe

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

通常，我的exe有dll依赖项，我用像或这样的安装程序进行打包。对于大型程序来说，这是有意义的，但对于小型脚本来说，这是过分的。是否有另一种方法来捆绑依赖项，以便用户只需执行单个exe，而不需要路径中的dll目录？编辑我希望有一种解决方案，它不依赖于dll的类型，也适用于其他类型的依赖项。以下是一些潜在的选择：有人有这种工具的经验吗？

问如何在exe中绑定依赖项
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在exe中绑定依赖项EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在exe中绑定依赖项
EN