[Scons-dev] please try latest default branch

[roberto de vecchi]

Gary,

 

I think that the problem I’m seeing is generated by the modification in
FS.py around line 3052:

 

  def built(self):

        """Called just after this File node is successfully built.

        

         Just like for 'release_target_info' we try to release

         some more target node attributes in order to minimize the

         overall memory consumption.

         

         @see: release_target_info

        """

 

        SCons.Node.Node.built(self)

 

        if not hasattr(self.attributes, 'keep_targetinfo'):

            # Ensure that the build infos get computed and cached...        

            self.store_info()

            # ... then release some more variables.

            self._specific_sources = False

            self.labspath = None

            self._save_str()

            self.cwd = None   ß-

 

removing the reset of self.cwd things look much better and I can build
correctly with interactive mode. Just for your info we are running
exclusively with variantdir enabled and no source duplication.

 

If you can confirm the small change makes sense, I’ll let some of our
developer test more in detail this configuration.

 

Regards,

roberto

 

 

From: scons-dev-bounces at scons.org [mailto:scons-dev-bounces at scons.org] On
Behalf Of Gary Oberbrunner
Sent: mercoledì 8 gennaio 2014 19:52
To: SCons developer list
Subject: Re: [Scons-dev] please try latest default branch

 

 

On Wed, Jan 8, 2014 at 12:35 PM, roberto de vecchi
<roberto.devecchi at vi-grade.com> wrote:

I tried upgrading our company build engine including the latest default
branch and for std build it seems to work properly: the memory consumption
is reduced compared to the standard version. Unfortunately we are getting
many troubles with the interactive mode we use quite heavily. On the first
build the interactive execution works fine but triggering a new build, the
process is stopped due to missing input libraries during the linking stage.

 

Thanks Roberto -- just to confirm, interactive mode was working OK for you
in 2.3.0 but not on default?  Perhaps you can bisect to see which change
caused it.  Current tests pass, but they could easily be missing some cases
for interactive use.

 

-- 
Gary 

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140108/c6b91ff2/attachment.html>