That would be the correct file. I had to rewrite this file in Parts myself.. it 
was easier to just override the whole file, than trying to monkey patch it.

Just looking at the bug report. It looks more like a how the path was provided 
bug than a Scons bug. It might be easy to fix with a simple "#" added before 
the name of the file.
There is an open issue in scons that has to be addressed yet, in that Scons 
should not switch current working paths. Or should do it in a excepted way. 
Currently SCons will try to change the CWD to the variant directory in 
question. If it does not exist it used the source directory of the variant 
path. I had pointed out in some other bug that this causes certain use cases of 
pattern searching to fail as new files are not found correctly, since the file 
does not exist in the variant directory area. It looks like this is the root 
cause of this bug.

Jason 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Cristina Yenyxe González García
Sent: Monday, November 19, 2012 5:41 PM
To: SCons developer list
Subject: Re: [Scons-dev] SCons + Tup?

2012/11/15 Kenny, Jason L <[email protected]>:
>
> Honestly I believe given what I have in the works that some 
> refactoring of some logic in SCons to better use the stored 
> information and add a few of the methods in Parts will allow SCons to 
> start up much faster and scale much better with large builds.

That would be a good starting point, probably easier than the one I suggested.

Just in case I can help, I've downloaded the source code from the Bitbucket 
repository and generated everything with the bootstrap script. Maybe I could 
start working on a bug to get familiar with the code, then we could talk again 
about this topic? This bug doesn't seem very hard to fix: 
http://scons.tigris.org/issues/show_bug.cgi?id=816
I guess that Variables/__init__.py is the file that needs modifications, but if 
someone could give me a hint... :-) 
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev

Reply via email to