[build2] Binaries of build2 0.8.0 toolchain for OS X and Linux

Boris Kolpackov boris at codesynthesis.com
Sat Sep 22 22:11:13 UTC 2018

Dane Springmeyer <dane at mapbox.com> writes:
> In my experience I only choose bash when I want to avoid any need for
> external dependencies. So if I'm depending on build2 I'm unsure if I
> would need to write bash.

Yes, that's a valid point. Though bash can still be more effective than,
say C++, if all you need is to string together a bunch of commands with
some basic logic in between.

In our case, we use this in brep (repository web interface) where we have
C++ core plus a bunch of "handler scripts" for things like CI, package
submissions, etc.

> What are the use cases you have for preprocessing bash?

Preprocessing is predominantly used for module imports. In a nutshell, the
idea is to be able to factor common functionality into modules (.bash files)
that can then be imported by multiple scripts with build2 making sure these
modules are found regardless of the situation (development build, installed,
etc). You can also use cross-project imports and even package your bash
modules into build2 packages. Here is one example:


More information about the users mailing list