[Scons-dev] Likely bug - installing side effect files

[Kenny, Jason L]

Honestly I view sideeffect as a result ( ie a side effect) of not wanting to fix the builder up. PDB files are side effects file that might exists is some flags are set. Honestly it better to handle them as targets. 
Jason

-----Original Message-----
From: Scons-dev [mailto:scons-dev-bounces at scons.org] On Behalf Of Dirk Bächle
Sent: Monday, November 3, 2014 8:38 AM
To: scons-dev at scons.org
Subject: Re: [Scons-dev] Likely bug - installing side effect files

On 03.11.2014 14:44, Ben Golding wrote:
> Hi Dirk,
>
> Thanks for the clarification.
>
> Nevertheless, what effect does this "marking" of the side effect file actually have during the build? What can I usefully do with the object returned by SideEffect()?
Not very much, I'm afraid...and why would you want to anyway? I'm not a native speaker, so take it with a grain of salt please that it appears obvious to me, that declaring a file as "SideEffect" means that I don't really care about it.

> Does it have an effect during the parallel build? (like a mutex, 
> restricting that only one builder instance can run concurrently if 
> they share the same hard-coded filename)
Yes, it does exactly that.
>
> > Another thing that "SideEffect()" does, is to mark the file for 
> > getting removed on a "scons -c". In the past, this has misled many 
> > writers of builders/tools, to use SideEffect() in favour of the more correct Clean()...
>
> If you are correct, this behaviour is certainly in contradiction with the docs:
> http://scons.org/doc/latest/HTML/scons-user/apd.html#f-sideeffect
In the passage above I was referring to the "might be removed as part of cleaning the directory in which it lives" part...sorry, if this got you confused.

Regards,

Dirk

_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev