blocks|key|213991|text|我使用了SCons，这个构建系统给我留下了深刻的印象。python和python本身都是可扩展的--这很棒，因为SCons拥有你需要的一切，只需编写逻辑代码，所有的低级功能都已经在SCons和Python中实现，并且是跨平台的。如果你有很好的编程技巧，那么你的构建脚本就会看起来完美而简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|213992|Make、CMake和类似的构建系统看起来像是宏的垃圾。晶片是SCons模拟的。我正在尝试网站管家，但SCons会更友好，所以我留在了SCons。|213993|大众认为SCons太慢了，但是在项目的中间，我看不出make和SCons在构建速度上有什么不同。相反，SCons已经很好地处理了并行构建，而make则遇到了很大的麻烦。|213994|此外，SCons允许你从模板中获取-配置，构建，部署，生成配置，运行测试和完成任何其他可以用python和SCons编码的任务-所有这些都可以在一起完成。这是一个非常大的优势。|213995|对于一个简单的项目，CMake也是一个不错的选择。|213996|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I used SCons and am impressed by this build system. SCons is extensible by python and python itself - it's great, because Python has all that you need, just code the logic, all the low-level functionality is already implemented in SCons and Python and is crossplatform. If have good programming skills then your build scripts will be looking perfect and easy.

Make, CMake and similar build systems seems as trash of macroses. 
Waf is SCons analog. I'm trying Waf but SCons will be more friendly and so I stayed with SCons. 

By crowd opinion SCons is too slow, but in the middle of a project I didn't see any difference between make and SCons by build speed. Instead, SCons has well worked with parallel builds, while make has big troubles with it. 

Also, SCons allows you to get - configure, build, deploy, generate configuration from templates, run tests and do any other task that can be done can coding with python and SCons - all in one. That is a very big advantage.

For a simple project CMake is also a good choice.

blocks|key|2863424|text|%2B1代表，“太多了，它们太可怕了。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2863425|但是，“最丰富的”和“最具伸缩性的”可能是CMake，它是一个Makefile生成器(也生成原生的MSVC%2B%2B+*.proj/*.sln)。奇怪的语法，但是一旦你学会了它，你就可以很好地为不同的平台生成构建。如果我是“started+fresh”，我可能会使用CMake。它应该处理您的列表，尽管您的“代码生成”可能会在构建系统之外呈现“自己的生命”，这取决于您想要做什么。(请参见下文。)|offset|length|style|CODE|2863426|对于简单的项目，可以使用QMake生成器(使用QMake不需要使用Qt库)。但是，您没有描述“简单”--代码生成和“额外阶段”意味着您可能需要CMake或具有丰富应用编程接口的扩展，如Scons+(或Waf)。|2863427|我们在工作中使用Scons。它产生了“防弹构建”，但它真的很慢。没有其他系统会像Scons一样防弹。但是，它很慢。它是用Python语言编写的，我们已经为我们的“工作空间组织”(我们只指定模块依赖项)扩展了接口，这是Scons设计意图的一部分(通过Python进行的这种类型的扩展)。很方便，但是构建速度很慢。你得到了无懈可击的构建(任何开发人员盒都可以完成最终版本)，但速度很慢。而且，它很慢。但是，不要忘记，如果您使用Scons，它的速度会很慢。而且，它很慢。|2863428|想到2000年后的十年，我们仍然没有会飞的汽车，这让我很不舒服。我们可能还要等上一百年才能拿到它们。然后，我们可能都会开着我们的会飞的汽车到处飞来飞去，这些汽车仍然是用糟糕的建造系统建造的。|2863429|是的，它们都很糟糕。|2863430|关于代码生成|2863431|Scons在“阶段”上工作，它们是“有些静态的”。它可以构建作为构建的一部分生成的代码(人们用几种不同的方式来做这件事)，但这被描述为“非常不像Scons的东西”。|2863432|如果只是简单的“预处理一些文件并生成源文件”，那么就没什么大不了的(您有很多选择，这就是为什么编写qmake+--用于*.hpp/*.cpp文件的moc预处理)。|2863433|然而，如果你是以一种“繁重的方式”来做这件事，你将需要编写自己的脚本。例如，我们有作为构建的一部分的脚本，它查询数据库并生成C%2B%2B类来在“层”之间进行接口(在传统的3层应用程序开发中)。类似地，我们通过IDL生成服务器/客户端源代码，并嵌入版本信息，以允许多个客户端/服务器同时运行不同的版本(对于相同的“客户端”或“服务器”)。大量生成的源代码。我们可以“假装”这是“构建系统”，但实际上，它是一个用于“配置管理”的非平凡的基础设施，其中一部分是“构建系统”。例如，此系统必须将“关闭”和“启动”服务器作为此过程的一部分。类似地，回归测试是作为这个过程的一部分执行的，版本之间有大量的“报告”和“差异测试”--所有这些都是我们“构建脚本”的一部分。|2863434|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cmake.org/|1|http://en.wikipedia.org/wiki/Qmake|2|http://www.scons.org/^0|0|1K|6|1R|5|3M|5|L|5|0|0|1Z|5|2K|5|2S|3|C|5|1|0|14|5|30|5|5V|5|8|5|2|0|0|0|0|0|5|0|1D|5|1N|B|21|3|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]]|9|@$D|1H|E|1I|1|1J]]|A|$]]|$1|H|3|I|5|6|7|1K|8|@$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]|$D|1P|E|1Q|F|G]]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|J|3|K|5|6|7|1U|8|@$D|1V|E|1W|F|G]|$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|G]]|9|@$D|21|E|22|1|23]]|A|$]]|$1|L|3|M|5|6|7|24|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|25|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|26|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|2A|8|@$D|2B|E|2C|F|G]|$D|2D|E|2E|F|G]|$D|2F|E|2G|F|G]]|9|@]|A|$]]|$1|V|3|W|5|6|7|2H|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|16]]|17|$5|10|11|12|A|$13|18]]]]

+1 for, "Many, and they're awful."

But, the "richest" and "most-scalable" is probably <a href="http://www.cmake.org/" rel="noreferrer">CMake</a>, which is a Makefile-generator (also generates native MSVC++ <code>*.proj</code>/<code>*.sln</code>). Weird syntax, but once you learn it, it can allow you to nicely generate builds for different platforms. If I "started-fresh", I'd probably use <code>CMake</code>. It should handle your list, although your "code-generation" could take on "a-life-of-its-own" beyond the build system depending on what you want to do. (See below.)

For simple projects, the <a href="http://en.wikipedia.org/wiki/Qmake" rel="noreferrer">QMake</a> generator is ok (you don't need to use the Qt libraries to use QMake). But, you're not describing "simple" -- code generation and "extra-phases" means you probably want <code>CMake</code> or something with a rich API for your own extensions, like <code>Scons</code> (or <code>Waf</code>).

We use <a href="http://www.scons.org/" rel="noreferrer">Scons</a> at work. It produces "bullet-proof-builds", but it's really slow. No other system will be as bullet-proof as <code>Scons</code>. But, it's slow. It is written in Python and we've extended the interface for our "workspace-organization" (where we merely specify module dependencies), and that is part of the <code>Scons</code> design intent (this type of extension through Python). Convenient, but builds are slow. You get bullet-proof builds (any developer box can make the final release), but it's slow. And, it's slow. Don't forget that if you use <code>Scons</code>, though, that it's slow. And, it's slow.

It makes me ill to think that a decade after the Year 2000, we still don't have flying cars. We'll probably have to wait another hundred years or something to get them. And, we will then all probably be flying around in our flying cars that are still being constructed with crappy build systems.

Yes, they are all awful.

[ABOUT CODE GENERATION]

<code>Scons</code> works on "phases", and they are "somewhat-static". It can build code that is generated as part of the build (people are doing this in a couple of different ways), but this has been described as, "something very un-Scons-like".

If it's simple "preprocess some files and generate source files", then no biggie (you have lots of options, and this is why <code>qmake</code> was written -- for the <code>moc</code> preprocessing of <code>*.hpp/*.cpp</code> files).

However, if you are doing this in a "heavy-manner", you're going to need to script your own. For example, we had as-a-part-of-the-build scripts that queried the databases and generated C++ classes to interface between the "layers" (in traditional 3-tier application development). Similarly, we generated server/client source code through IDLs, and embedded version information to permit multiple clients/servers to run simultaneously with different versions (for the same "client" or "server"). Lots of generated source code. We could "pretend" that is "the-build-system", but really, it's a non-trivial-infrastructure for "configuration management", of which part of it is the "build-system". For example, this system had to, "take-down" and "start-up" servers as a part of this process. Similarly, the regression-tests were executed as a part of this process, with heavy "reporting" and "difference-testing" between versions -- all as a part of our "build-scripts".

blocks|key|217308|text|补充一下我的观点:+premake|type|unstyled|depth|inlineStyleRanges|entityRanges|data|217309|http://industriousone.com/premake|offset|length|217310|在维基上也有一个dedicated+webpage。|217311|entityMap|0|LINK|mutability|MUTABLE|url|1|http://en.wikipedia.org/wiki/Premake^0|0|0|X|0|0|8|H|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|P]]]]

just to add my cents: premake

<a href="http://industriousone.com/premake" rel="nofollow">http://industriousone.com/premake</a>

there is also a <a href="http://en.wikipedia.org/wiki/Premake" rel="nofollow">dedicated webpage</a> on the wiki.

blocks|key|216983|text|Scons是一个非常友好和灵活的系统，但是你说得对，Lothar，它真的很慢。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|216984|但是有一种方法可以提高用Python编写的程序的性能。JIT的这种用法。在所有已知的项目中，PyPy是一个非常强大、快速增长和有动力的JIT支持的Python2.7实现。PyPy与Python2.7的兼容性简直令人惊叹。但是，Scons在PyPy+compatibility+wiki上声明为不受支持的项目。另一方面，python被建模为基于python的autotools+sucessor，完全受PyPy基础设施的支持。在我的项目中，在过渡到PyPy的过程中，汇编的速度提高了5-7倍。You+can+see+the+performance+reports+from+PyPy。|offset|length|216985|对于现代和相对快速的构建系统，Waf是一个很好的选择。|216986|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/pypy/compatibility/wiki/Home|1|http://code.google.com/p/waf/^0|0|3B|N|0|6T|19|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]|$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Scons is very friendly and flexible system, but you right, Lothar, it really slow.

But there is a way to increase the performance of programs written in Python. This use of the JIT. Of all known projects, PyPy is a very powerful, fast-growing and motivated JIT-backed - Python 2.7 implementation. PyPy compatibility with Python 2.7 is simply amazing. However, Scons declared as unsupported project on the <a href="https://bitbucket.org/pypy/compatibility/wiki/Home" rel="noreferrer">PyPy compatibility wiki</a>.
Waf, on the other hand, modeled as python-based autotools sucessor, is fully supported by PyPy infrastructure. In my projects the speed of the assembly has increased 5-7 times in the transition to PyPy. <a href="http://code.google.com/p/waf/" rel="noreferrer">You can see the performance reports from PyPy</a>.

For modern and relatively fast build system Waf is good choice.

blocks|key|2863501|text|您可以使用Ceedling。请注意，它目前只支持C语言，并且与作者的Unity和CMock测试框架紧密耦合。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2863502|可以对其进行派生和修改，以便与C%2B%2B编译器和单元测试/模拟框架一起工作。|2863503|此外，Tup也值得一提。它非常快，但它对测试框架等一无所知，这意味着你必须使用Tup编写自己的构建系统。如果你打算做TDD，Tup可能是个不错的选择。|2863504|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ThrowTheSwitch/Ceedling|1|http://gittup.org/tup/^0|5|8|0|0|0|3|3|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

You can use <a href="https://github.com/ThrowTheSwitch/Ceedling" rel="nofollow">Ceedling</a>. Note, however it only supports C at the moment and it is tightly coupled to the author's Unity and CMock testing frameworks.

It can be forked and modified to work with a C++ compiler and unit testing / mocking framework fairly easily.

Also <a href="http://gittup.org/tup/" rel="nofollow">Tup</a> is a worthy mention. It is extremely fast but it knows nothing about testing frameworks etc. which means you'll have to write your own build system using Tup. If you plan on doing TDD, Tup is probably the way to go.

blocks|key|214125|text|现在可以使用Gradle了：https://docs.gradle.org/current/userguide/native_software.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|214126|自从我最初发布这篇文章以来，这似乎已经相当成熟了。说这个项目正在“孵化”的页面已经消失了，但我找不到任何官方声明删除这个状态。|214127|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gradle.org/current/userguide/native_software.html^0|E|1Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You can use Gradle now: <a href="https://docs.gradle.org/current/userguide/native_software.html" rel="noreferrer">https://docs.gradle.org/current/userguide/native_software.html</a>

This seems to have matured quite a bit in the years since I originally posted this. The page saying that the project is "incubating" has disappeared, but I can't find any official announcement removing this status.

blocks|key|217397|text|我找到了这些，我还没有亲自使用过：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|217398|Ninja，一个专注于速度的小型构建系统。谷歌现在使用忍者来构建Android，而不是Make：link。|offset|length|217399|Shake，一个强大而快速的构建系统。|217400|Tup，一个高性能的构建系统。基于Algorithmic的设计。Analysis+of+Tup。|217401|所有这些现在都是跨平台的，并且都支持Windows。我还不确定您的其他需求，因为我还没有亲自测试它们。他们正在被用于商业开发，CIG拿起了忍者。我已经使用并喜欢忍者的轻松和快速的项目生成器。前两个类似于Scons、Ant等。|217402|entityMap|0|LINK|mutability|MUTABLE|url|https://ninja-build.org/|1|https://groups.google.com/forum/#!topic/android-platform/Hhl_4hfOONg/discussion|2|https://github.com/ndmitchell/shake|3|http://gittup.org/tup/|4|http://gittup.org/tup/build_system_rules_and_algorithms.pdf|5|http://chadaustin.me/2010/06/scalable-build-systems-an-analysis-of-tup/|6|https://www.cloudimperiumgames.com/^0|0|0|5|0|1C|4|1|0|0|5|2|0|0|3|3|H|B|4|W|F|5|0|1R|3|6|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]|$D|1A|E|1B|1|1C]]|A|$]]|$1|F|3|G|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|H|3|I|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]|$D|1L|E|1M|1|1N]|$D|1O|E|1P|1|1Q]]|A|$]]|$1|J|3|K|5|6|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|L|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]|X|$5|O|P|Q|A|$R|Y]]|Z|$5|O|P|Q|A|$R|10]]|11|$5|O|P|Q|A|$R|12]]|13|$5|O|P|Q|A|$R|14]]]]

I found these, I have not personally used all of them yet:
<a href="https://ninja-build.org/" rel="nofollow noreferrer">Ninja</a>, a small build system focused on speed. Google now uses Ninja to build Android instead of Make: <a href="https://groups.google.com/forum/#!topic/android-platform/Hhl_4hfOONg/discussion" rel="nofollow noreferrer">link</a>.
<a href="https://github.com/ndmitchell/shake" rel="nofollow noreferrer">Shake</a>, a powerful and fast build system.
<a href="http://gittup.org/tup/" rel="nofollow noreferrer">Tup</a>, a high performance build system. <a href="http://gittup.org/tup/build_system_rules_and_algorithms.pdf" rel="nofollow noreferrer">Algorithmic</a> based design. <a href="http://chadaustin.me/2010/06/scalable-build-systems-an-analysis-of-tup/" rel="nofollow noreferrer">Analysis of Tup</a>.
All are now cross-platform and support Windows. I'm not yet sure about the rest of your requirements as, again, I have yet to test them myself. They are being used in commercial development, <a href="https://www.cloudimperiumgames.com/" rel="nofollow noreferrer">CIG</a> picked Ninja up. I've used and love ease and speed of Ninja with a project generator. First two are akin to Scons, Ant, etc.

blocks|key|3076947|text|谷歌构建系统是一个很好的选择：http://bazel.io/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3076948|entityMap|0|LINK|mutability|MUTABLE|url|http://bazel.io/^0|F|G|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]]]]

Google build system is a good alternative: <a href="http://bazel.io/">http://bazel.io/</a>

I'm looking at starting a new project in C++ - just in my own time initially - and I'm investigating the build systems that are available. It would appear that the answer is "Many, and they're all awful". 

The features that I specifically need for this are:

<ol>
<li>C++11 support</li>
<li>Cross platform (Linux as main target, but able to build on at least Windows as well)</li>
<li>Decent unit testing support</li>
<li>Support for multiple modules for separating code out</li>
<li>Support for code generation (Using asn1c or protobuf - not 100% sure yet)</li>
<li>Easy to maintain</li>
</ol>

Now, I know I can do 1-4 of those using CMake and Autotools easily enough. Probably also with SCons and Waf and the couple of others too. The problem is that I've never worked out how to correctly do code generation using them - that is source files that do not exist until the build process is first run, so source files that the build system must be able to convert into executable code but doesn't actually know about until the build starts... (ASN1C in particular generates dozens of header and source files that must be able to work together, and the actual set of files generates depends on the contents of your asn file) There's also the fact that none of these are especially easy to maintain - CMake and Autotools have their own huge set of scripts that you need to manage for them to work, and Waf and Scons require that anybody working with them has decent knowledge of python (I don't) to work with them...

So - what build systems are recommended for something like this? Or will I be stuck with make files and shell scripts for now?

C++ Build Systems - What to use?

单元测试

回归测试

数据库

服务器

编译器

Android

Windows

Python

Linux

我正在考虑在C++中开始一个新项目-最初只是在我的业余时间-我正在研究可用的构建系统。答案似乎是“很多，而且它们都很糟糕”。为此，我特别需要的特性是：C++11支持跨平台(以Linux为主要目标，但至少也能在Windows上构建)针对多个模块的得体单元测试用于分离代码的多个模块支持代码生成(使用asn1c或protob...

问C++构建系统-使用什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C++构建系统-使用什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C++构建系统-使用什么？
EN