I agree with David. Can we have one script to maintain instead of... how many was that again, and what are their names, and where are they?

Regards,
Mike

-----Original Message-----
>From: David Akbari 
>Sent: May 6, 2008 2:43 PM
>To: Developer discussions 
>Subject: Re: [Cs-dev] cleanup.sh
>
>At a glance this looks really great!
>
>My question is however, how is this different from the command `scons
>-c` from the root of the Csound source tree ?
>
>Would it be possible to add your additional functionality to a new
>"clean" target in SConstruct so that the end user could feasibly run
>`scons clean` for a more thorough cleanup ?
>
>
>Thank you for your time and consideration,
>
>
>David Akbari
>
>On Mon, May 5, 2008 at 11:17 PM, Felipe Sateler  wrote:
>> Hi there. Since I usually do lots of compile-clean-compile runs, I was very
>>  annoyed with cleanup.sh taking too long to compile. I have thus enhanced it a
>>  bit to traverse the source tree less times, and to call file on less files.
>>  The result is several times faster (from 25-27 to 3-4 seconds on my
>>  computer). However my find-fu is not that good, so I'm wary of commiting it
>>  directly to CVS. I haven't found any problems, though.
>>
>>  Attached is the modified cleanup.sh so you can take a look at it, and
>>  eventually it ends up at the CVS (25 seconds to clean up is just too much!).
>>
>>  --
>>  Felipe Sateler
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
>Don't miss this year's exciting event. There's still time to save $100. 
>Use priority code J8TL2D2. 
>http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Why not move to out-of-source build? Then the source dirs are guaranteed
to be unpoluted, and cleanup is just a matter of doing an

  rm -rf build

Felipe Sateler wrote:
> The scons -c option has 2 problems. One, you need to remember which options you
> used to build in the first place, or else stuff won't get cleaned up.
> 2, scons doesn't track
> very well what it is that it built. For example, the swig builders
> leave lots of stuff around.
> Also, making SConstruct aware of every file it needs to cleanup is
> apparently not
> straightforward. For example, SConstruct2 has code to remove symlinks
> (libcsound.so,
> libcsnd.so) when cleaning up, but for some reason it doesn't pick them
> up (perhaps
> because by the time they are cleaned up they are dangling).
> 
> I think it is easier to maintain a number of patterns to remove. I
> tried to make scons aware
> of all the cruft it leaves behind but I was not very successful.
> 
> On Tue, May 6, 2008 at 3:38 PM, Michael Gogins  wrote:
>> I agree with David. Can we have one script to maintain instead of... how many was that again, and what are their names, and where are they?
>>
>>  Regards,
>>  Mike
>>
>>
>>
>>  -----Original Message-----
>>  >From: David Akbari 
>>  >Sent: May 6, 2008 2:43 PM
>>  >To: Developer discussions 
>>  >Subject: Re: [Cs-dev] cleanup.sh
>>  >
>>  >At a glance this looks really great!
>>  >
>>  >My question is however, how is this different from the command `scons
>>  >-c` from the root of the Csound source tree ?
>>  >
>>  >Would it be possible to add your additional functionality to a new
>>  >"clean" target in SConstruct so that the end user could feasibly run
>>  >`scons clean` for a more thorough cleanup ?
>>  >
>>  >
>>  >Thank you for your time and consideration,
>>  >
>>  >
>>  >David Akbari
>>  >
>>  >On Mon, May 5, 2008 at 11:17 PM, Felipe Sateler  wrote:
>>  >> Hi there. Since I usually do lots of compile-clean-compile runs, I was very
>>  >>  annoyed with cleanup.sh taking too long to compile. I have thus enhanced it a
>>  >>  bit to traverse the source tree less times, and to call file on less files.
>>  >>  The result is several times faster (from 25-27 to 3-4 seconds on my
>>  >>  computer). However my find-fu is not that good, so I'm wary of commiting it
>>  >>  directly to CVS. I haven't found any problems, though.
>>  >>
>>  >>  Attached is the modified cleanup.sh so you can take a look at it, and
>>  >>  eventually it ends up at the CVS (25 seconds to clean up is just too much!).
>>  >>
>>  >>  --
>>  >>  Felipe Sateler


-- 
/Jonatan         [ http://kymatica.com ]

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net