jachris/cook

🛠️ An Extensible, Dynamic, Fast and Cross-Platform Build System (2017)

Hi there 👋 Here are some random links for you ...

🦀 Rust MIR Optimization (2022)

✨ Interactive WASM Raytracer (2019)

🛠️ Build System (2017)

cook's Issues

Automatically regenerate CLion project

The CLion CMake generator (currently examples/cpp/clion.py) should regenerate CMakeLists.txt when needed.

Investigate Java Rules

Name conflicts with Peter Miller's build tool "cook"

While his website is down after his death, the source is still on FTP sites, and it's available as Debian and Ubuntu packages.

Path handling

A rule must currently core.resolve() any files relative to the build script and core.build() any files relative to the build directory. The paths are returned relative to the current working directory.

This can lead to some unexpected resulsts since a path returned by build can be resolved to create a totally nonsensical path. This could be improved to reduce the likelihood of errors.

C++ feature detection / configuration

The results could be saved to a file from a separate task to avoid redoing it every build.

Git Bash on Windows - UI issues

Determine default environment to run commands within

Currently, core.call() uses an empty environment when not specifying anything else. This is a bad default behaviour because many applications rely on some enviroment variables like TMP. We should determine some useful defaults which will not impact reproducability.

Investigate Android Rules

decider option like scons

It would be nice to have something like Decider function ( http://scons.org/doc/HTML/scons-user.html#idm139933297217568 ) - so manage when input file has changed. As part of my build process is binary mesh builder file and I'd like to rebuild every time its checksum changed and not timestep.

Generic rule for arbitrary commands

Sometimes there is the need for just running a program with known outputs and inputs. There should be a user-friendly rule that provides such a functionality, maybe including inputs / outputs path substitution.

flake8: F821 undefined name 'primaries'

flake8 testing of https://github.com/jachris/cook on Python 3.6.2

$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics

./cook/core/graph.py:327:23: F821 undefined name 'primaries'
    return primary in primaries
                      ^

Cook name duplicates established work of art

There has been another "cook" build system that was first made available in the early 2000's by a notable software author, Peter Miller. Your system seems to share no relationship with it and that may be confusing for some users.

http://ibiblio.org/pub/Linux/devel/make/cook-2.25.tut.pdf
https://en.wikipedia.org/wiki/Peter_Miller_(software_engineer)
https://lists.auug.org.au/pipermail/cook-users/

I would recommend choosing another name, or including prominent footnotes indicating that there is no relationship in respect to that prior author's work.

immediate quit whole build if any job fails

cmdline switch at least would be fine. Especially on Windows (git bash console) it's annoying to stop failing build process.

Investigate C Rules

C++ shared and static library could be unified

Currently, there are two completly separate implementations for shared and static c++ libraries. Maybe the underlying rule implementation or even the API can be unified?

Improve IDE support

Integrate other build systems

It should be possible to let the system run other build systems. This could be useful to build subprojects not using Cook or for projects that want to change build systems.

Handle unknown output filenames

Some rules (e.g. Java) might output different filenames which are difficult to know before executing the rule. Currently all outputs must be known before execution – other build tools solve this by zipping all produced files to a well-defined path.

Improve website

Warnings are not restored

The mechanism seems to be broken. A test should be added to prevent this in the future.

Improve documentation

output build directory / tracking BUILD.py

Is it possible to setup output outside of build directory?

Option to choose debug / release

Investigate Rust Rules