未加星标

Why Not Make?

字体大小 | |
[系统(linux) 所属分类 系统(linux) | 发布者 店小二05 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

Make is a conceptually simple build-system, and it is packaged with major linux distributions. However, Make should rarely be your build-system of choice when starting a new C++ project.

That’s a bold claim, so here’s why…

Writing a Large, Correct Makefile is ReallyHard

The dependency graph of a C++ library is actually quite complex. It must be rebuilt every time a linked object-file changes… But an object-file should be rebuilt every time its translation-unit changes, or the compilation flags change, or if any of its included headers change, or if the compiler changes…

You can query this information using the compiler and encode all of this in a Makefile, but it’s going to get really verbose.

There’s a high chance that you will miss a dependency. If this happens, then you might have stale artefacts after a change. Cue a clean build!

No Sandboxing

The lack of sandboxing is the root problem. Make has a dependency graph, but it does not actually enforce it. What this means is that a build-rule can read a file even if it is not declared as a dependency in Make!

Caches are NotPortable

Make does not allow you to share build artefacts across a network, so everyone on your development team will be performing the same build-steps over and over!

Yes, you can use CCache, but that is not general (only compiler calls are cached) and it isn’t provided out-of-the-box.

No Language Abstractions areProvided

Make’s simplicity is a big strength, but it is also a major weakness. Make doesn’t provide any language-specific abstractions, so you have to write them yourself. This can get very tedious, and the odds of making a mistake are high.

This also goes for tests, deployments and so on. You need to build everything yourelf.

Timestamps, NotHashes

In determining when to rebuild, Make uses the timestamps of build inputs rather than their hashes. This results in many unnecessary rebuilds when a file has been touched, but has not actually changed. If this happens deep in the dependency tree, then the rebuild will take a long time!

So When Should You UseMake?

It’s not all bad; Make still has its place as a bootstrapping tool. If you have extreme dependency requirements (for example you are building Linux from source), then you need something simple and self-contained. But for most developers this just isn’t the case. We already fetch Clang, GCC and Visual Studio as prebuilt binaries, so why not download a prebuilt build-system?

Since You’reHere…

We recently announced BuildInfer , a new tool to optimize your C/C++ build scripts. Take a look !


Why Not Make?

本文系统(linux)相关术语:linux系统 鸟哥的linux私房菜 linux命令大全 linux操作系统

代码区博客精选文章
分页:12
转载请注明
本文标题:Why Not Make?
本站链接:https://www.codesec.net/view/611139.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(linux) | 评论(0) | 阅读(66)