如何构建源代码以签入需要很长时间构建的二进制文件
我想检查一些预编译的二进制文件以获取第三方依赖项。 构建 /trunk 文件夹的好方法是什么？
我的项目中有大约十个第三方库。我的项目也是跨平台的。仅一个目标就需要大约 1 小时来构建所有内容。我们现在规模越来越大，我想更频繁地编译它。
所以我想检查二进制文件中的依赖项。 您认为这个想法怎么样？
/trunk
/pre-compiled-binaries
/win32
/debug
/file1.dll, filex.lib, filex.h
/release
/file1.dll, filex.lib, filex.h
/iOS
/debug
/libFile, libFilex.h
/relase
/libFile, libFilex.h
/bin
/stuff that is being compiled right now
在我构建的脚本中，我将有两个脚本用于两个不同的目的。
- 这是什么平台？现在将预编译的二进制文件复制到 /trunk/bin
- 构建所有依赖项。现在将它们复制到 /trunk/bin
由于依赖关系不会改变，所以我不必做这么多。
我的目录结构合适吗？
I'd like to check in some pre-compiled binaries for 3rd party dependencies. What is a good way to structure my /trunk folder?
My project is has around ten 3rd party libraries in it. My project is also cross-platform. It takes around 1 hour to build everything for just one target. We are getting bigger now and I'd like to compile it all more frequently.
So I'd like to check in the binaries for the dependencies. What do you think of this idea?
/trunk
/pre-compiled-binaries
/win32
/debug
/file1.dll, filex.lib, filex.h
/release
/file1.dll, filex.lib, filex.h
/iOS
/debug
/libFile, libFilex.h
/relase
/libFile, libFilex.h
/bin
/stuff that is being compiled right now
In my built scripts, I would have two for two different purposes.
- What platform is this? Now copy Pre-Compiled Binaries to /trunk/bin
- Built all the dependencies. Now copy them into /trunk/bin
Since the depencies won't change, I won't have to do this much.
Is my directory structure appropriate?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我已经用类似的方式做过很多次了。只要您预编译二进制文件，然后将它们签入专门用于它们的目录中，无论将其放在哪里都可以。我个人倾向于使用“外部”而不是“预编译的二进制文件”，但是YMMV。
I have done this in a similar way many times. As long as you pre-compile the binaries then check them in to a directory just for them, you're fine no matter where you put it. I personally tend to use "external" rather than "pre-compiled-binaries", but YMMV.