Subject: Re: [Boost-build] prototyping alternative Boost.Build syntax
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-28 12:55:24
On 28.10.2016 12:48, Vladimir Prus wrote:
> On 28-Oct-16 7:44 PM, Stefan Seefeld wrote:
>>> A target is just represented as a string in Jam and
>>> Python. The internal structures used by the back end
>>> are created on demand.
>> That doesn't help me much. If I want to define a new target I surely
>> need to invoke some `bjam` function (from the bjam module Vladimir just
>> mentioned) to declare that.
> Are you sure you want to define a new target? That would bypass all of
> logic for creating a target that Boost.Build has?
> I though that what you're after is to prototype how do use Python do
> define a metatarget, affectively how to replace
> exe a : a.cpp ;
> with equivalent Python code. In order to do that, you only need to know
> Python interface for declaring metatargets, not b2 interface for
> declaring targets. Am I missing something?
I'm not sure. I have yet to figure out what the right boundary is to
interface with the build engine.
So let's assume I want to try both:
* I want to prototype how to write metatargets in Python
* I want to prototype how to write targets (to eventually replace all of
the above Boost.Build logic by suitable Python code).
How would I do the above ?
-- ...ich hab' noch einen Koffer in Berlin...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk