Re: [Boost-build] Integrating source control in boost.build

From: Olivier Smeesters (olivier.smeesters_at_[hidden])
Date: 2006-10-04 03:05:56

Hi Phillip,

It was indeed inspired from that example and from the notfile rule. My 
problem is that the itrace example does not show how it invokes the 
tool, how it gets the file names.

If you can help me there, I would be very interested.

Thanks,

Olivier

> Date: Tue, 03 Oct 2006 11:00:43 -0400
> From: Phillip Seaver <phil_at_[hidden]>
> Subject: Re: [Boost-build] Integrating source control in boost.build
> To: "Boost.Build developer's and user's list"
> 	<boost-build_at_[hidden]>
> Message-ID: <45227B1B.1000503_at_[hidden]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>   

> It looks like you might want something more like the itrace example:  
> http://www.boost.org/doc/html/bbv2/extending/tools.html#id2859013
>
> Phillip
>
>
> Olivier Smeesters wrote, on 9/26/2006 7:22 AM:
>   
>> > Hi All,
>> >
>> > I'm trying to convert a previous build system, based on Ant, to 
>> > Boost.Build. One nice feature of this previous system was that it 
>> > could run cvs commands on the sources (eg. to find out if all files 
>> > are up-to-date or to tag all files that make a release). I'm trying to 
>> > reproduce this functionality.
>> >
>> > The ultimate goal would be to create rule where items to be managed 
>> > under version control would be declared and, automatically, several 
>> > main targets would be created like "cvs-check", "cvs-update", 
>> > "cvs-commit", "cvs-tag".
>> >
>> > As a first try, I wanted to create a generator which would allow me to 
>> > do something like this:
>> >
>> > | exe foo : foo.c ;
>> > | cvs commit : foo : <cvs-action>commit ;
>> >
>> > And calling "bjam commit" would commit all the files used to build foo.
>> >
>> > So I wrote the attached generator (derived from notfile).
>> >
>> > But currently, I don't get any source file name although I checked 
>> > with an echo that $(leaves) is full of file-target objects in the run 
>> > rule of the generator. Nevertheless, I only get something like:
>> >
>> > | cvs.run <l./gcc/debug/cvs-action-commit>commit
>> > | Action: commit
>> > | Sources: <l./gcc/debug/cvs-action-commit>commit
>> >
>> > Any idea how I can get the file names in the cvs.run action ? or how I 
>> > should do that CVS thingy ?
>> >
>> > Thanks in advance,
>> >
>> >
>> > Olivier
>>     
>
>
>   

-- 
Olivier Smeesters
Embedded Software Engineer
Newtec (LLN Office)
Avenue Einstein, 2A
B-1348 Louvain-la-Neuve
Tel: [phone]
Fax: [phone]