Difference between revisions of "Build Systems"

From bootstrapping
Jump to navigation Jump to search
Line 25: Line 25:
* http://mesonbuild.com/Use-of-Python.html
* http://mesonbuild.com/Use-of-Python.html
* https://ninja-build.org/
* https://ninja-build.org/
* https://github.com/michaelforney/samurai
== fac ==
== fac ==

Revision as of 20:02, 15 August 2017

GNU Make

GNU Make is usually built with make, but it actually provides a shell script that breaks the loop!

> If you need to build GNU Make and have no other `make' program to use, > you can use the shell script `build.sh' instead. To do this, first run > `configure' as described in INSTALL. Then, instead of typing `make' to > build the program, type `sh build.sh'. This should compile the program > in the current directory. Then you will have a Make program that you can > use for `./make install', or whatever else.

> As you see, you are not in the vicious circle.

Meson and Ninja

Meson is a build system intended to replace ./configure and Make.

It depends on Ninja (another more primitive build system) and is implemented in Python. Python may switch to Meson in the future. In that case there would be a bootstrapping loop, but maybe it's a non issue if ninja files are provided.

> Ninja is used to build Google Chrome, parts of Android, LLVM, and can be used in many other projects due to CMake's Ninja backend.


> Fac uses the ptrace system call to track all system calls that a build rule uses. It recognizes those calls that read or write to files or directories.

Could a tool like fac be used in general to break build system bootstrap loops?