Go to file
Jussi Pakkanen a7bfcbd6b9 More keyword adding. 2013-02-10 13:15:33 +02:00
test cases More keyword adding. 2013-02-10 13:15:33 +02:00
.gitignore Start of project. 2012-12-23 16:35:35 +02:00
COPYING Start of project. 2012-12-23 16:35:35 +02:00
bparser.py Enforce keyword order. 2013-02-10 02:01:41 +02:00
build.py Can set global flags. 2013-01-26 01:44:56 +02:00
builder.py Use relative paths for file names. 2013-02-06 23:51:12 +02:00
builder_install.py Generate shared library symlinks with Ninja. 2013-02-08 23:49:25 +02:00
builder_test.py Beginning of an install script. 2013-02-08 20:22:47 +02:00
depfixer.py Fix dependency info. 2013-02-08 21:29:02 +02:00
environment.py A dummy dependency class. 2013-02-10 01:19:00 +02:00
generators.py Generate configure files in Ninja backend. Now it passes all unit tests. 2013-02-09 01:02:42 +02:00
interpreter.py More keyword adding. 2013-02-10 13:15:33 +02:00
nodes.py Enforce keyword order. 2013-02-10 02:01:41 +02:00
readme.txt Renamed generators file. 2013-02-06 19:37:19 +02:00
run_tests.py Run tests in numerical rather than ASCIIbetical order. 2013-02-09 01:07:12 +02:00

readme.txt

This is an experiment to examine what would be
the optimal syntax for a cross-platform build
system.

Dependencies: Python3 and Python-Ply

Running:

Builder requires that you have a source directory and a build directory
and that these two are different. In your source root must exist a file
called 'builder.txt'. To generate the build system run this command:

builder.py <source directory> <build directory>

You can omit either of the two directories, and Builder will substitute
the current directory and autodetect what you mean. This mean that you
can do things like this:

cd source_root; mkdir build; cd build; builder ..
cd source_root; mkdir build; builder build

For questions contact jpakkane@gmail.com.