Re: Smokin' Fast Builds...

> How does the builder know the necessary command lines? Is there a
> script file?

Yeah. But it's quite simple (keeping it declarative instead of imperative)

A configuration consists of a directory, for example:

    ps2_debug/
    pc_vc_7_1_release/

The builder can be pointed to that directory to build that configuration.
The directory needs to contain the following five files to be a valid
config:

include.sfb
    list of all include paths, both relative or absolute, in search order

src.sfb
    list of files that contain lists of source files. So for example,
src.sfb will contain ps2.file_list and common.file_list. Those *.file_list
files will then contain lists of cpp files.

libs.sfb
    list of static libraries this project depends on. If it points to a .lib
file it's a prebuilt library, if it points to a configuration directory, it
will consider building that project as part of the whole build

compile.sfb
    contains the command line to turn cpp files into obj files. For CL this
currently contains: