Subject: Re: [Boost-build] How to set special generation requirements for generated files
From: Moritz Hassert (mhassert_at_[hidden])
Date: 2010-07-22 14:50:09
Thanks for your quick response.
Steven Watanabe wrote:
> Moritz Hassert wrote:
> > cpp bison1
> > : bison1.yy
> > : <bison.prefix>pre1 ;
> > cpp bison2
> > : bison2.yy
> > : <bison.prefix>pre2 ;
> > lib foo
> > : somefile.cpp
> > :
> > bison1
> > bison2
> > : <define>SOME_MACRO
> > <include>some/path ;
> This doesn't work? I would have expected it to. There should be a rule
> for every file type that Boost.Build handles.
Of course it does ... now I feel a bit like a fool :)
That "cpp" of mine was just an arbitrary example how I would call such a rule.
I never actually tried that piece of Jamfile because I found nothing like that
in the docs.
I think the fact that those rules exist and that they can be used for such
purposes should be included in the "common tasks" or "builtin rules" section.
My current problem is perfectly solved using the above code.
By the way: digging the boost-build sources, I found another undocumented rule
convert foo cpp : ... ;
seems to do exactly the same as
cpp foo : ... ;
Is there any difference?
Geschaeftsfuehrer: Dipl.-Inform. Christopher Asp
Amtsgericht Mannheim HRB 105845
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