$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
Subject: [Boost-build] prototyping alternative Boost.Build syntax
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-28 09:12:38
Hi,
I'm trying to wrap my head around the distinction between b2 ('the
engine ?') and boost.build. I assume somewhere base concepts such as
"rule", "target", "action", and "feature" are defined. Then, a parser
reads in all the Jamfiles, constructs a DAG of targets, and passes that
down to b2 to process. Is that approximately right ?
Is that parser part of b2 ? What are b2's internal representations of
the above concepts ? (I'd like to prototype a bit with a new (Python)
syntax, and therefore need to hook up my own parser to feed b2 the
objects it expects.
Am I on the right track ?
Thanks,
Stefan
-- ...ich hab' noch einen Koffer in Berlin...