Subject: Re: [Boost-build] Custom clean target
From: Alexander Sack (pisymbol_at_[hidden])
Date: 2008-10-17 12:58:26
On Wed, Oct 15, 2008 at 3:00 PM, Alexander Sack <pisymbol_at_[hidden]> wrote:
> On Wed, Oct 15, 2008 at 2:44 PM, Vladimir Prus
> <vladimir_at_[hidden]> wrote:
>> Alexander Sack wrote:
>>> On Wed, Oct 15, 2008 at 12:30 PM, Vladimir Prus
>>> <vladimir_at_[hidden]> wrote:
>>>> Alexander Sack wrote:
>>>>> Hello (again):
>>>>> Is there a way to extend the clean rule for various targets? I need
>>>>> added cleanup when I do "bjam --clean" etc. Do I have to make a
>>>>> separate target to do the dirty work or is there a way to extend the
>>>>> built-in clean target?
>>>> Can you tell what extra actions you have to do in clean?
>>> Clean generated side files from a special tool I invoked via a make or
>>> notfile target or even a custom generator class.
>> A custom generator class should accurately report what files it has produced.
>> And if it does, those files will be cleaned just fine.
>>> But regardless
>>> Vladimir, don't you think this is a reasonable request? :D
>> Well, "I need added cleanup" is not actually a request, because I don't know
>> what exactly you mean.
>> 1. Do you want --clean to remove some files, that are known to be located
>> as specific directories, or:
>> 2. You want to specify that a certain target (like make), may produce additional
>> files, in the same directory as main result, and those files, if present, must
>> be cleaned, or:
>> 3. You want arbitrary code to be executed on --clean?
> So all of the above that's why its a generic question. I guess my
> first though was the third question which is how to extend clean to
> execute my own clean rule that can do whatever. I think that seems
> reasonable no?
I'm gong to assume the answer is no on all fronts? So the work around
would be to create a custom target to do the dirty work? (that's fine,
I'm just asking).
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