Subject: Re: [Boost-build] custom generator problems
From: Alexander Sack (pisymbol_at_[hidden])
Date: 2009-03-09 16:34:17
On Mon, Mar 9, 2009 at 2:57 PM, Alexander Sack <pisymbol_at_[hidden]> wrote:
> So here I had to register new file-targets as well as an action using
> the virtual-target class which allowed me to register what I wanted
> Boost.Build to do when foo.proto is listed as a dependency.
One more note, I *think* one could glob over the target directory
where your generated files are and then register new
virtual-file-targets so they become managed files?? This is very
similar to the PYTHON Example in the doc on generators (what I did for
my protobuf example). I'm going to have look at this later today.
Btw do you REALLY not know the name of them at all or could you
actually right rules like obj <targetname> : <type that generates it>
style lines then have your binary depend on them potentially? (I'm
I'm looking at the virtual-target.jam class to better understand how
one should handle multiple target translation units from a single
source file to create a good example since I'm finally not the only
one that has run across this and has gotten a little confused. It
would be nice if there was a "new file-targetS" that took a list of
generated source files (CPP/H etc. plus I was deriving the name off of
the original source file which may not be applicable in your build env
so I should consider that too).
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