[Scons-users] caching build parameters

[Jason Kenny]

Hi,

Sorry I did not read it as well as I thought. So I am sorry, my reply was a
bit off.

I have a similar issue with Parts as well ( my extension to SCons). I am
trying to fix this with staled work on an Setting object based on a proposal
called IAPAT ( Information about tools and platforms) that you might be able
to find in the wiki.

1) The only way I understand how you can do this at the moment is to map the
--option to a Variable value. This can be a bit of work to maintain...
Ideally the Setting object I was working on solves this for you, but it not
100% "ready". However that code might be useful for solving your issue as it
does most of what is needed, but would need some clean up to decouple a few
Parts "things" related to the environment generation.

2) I don't know of a way to do this. In fact in Parts I patch up the
Variable object to help me do better merging of data from different sources,
and I disable the help generation. In the case of Parts the dump of
Variables I define is overwhelming to dump on the console. Currently I don't
believe there is a way to day I want show this variable in the help but not
that one.

Sorry this is not so helpful. I believe you hit on a known issue that keeps
slipping through the cracks in SCons


Jason

-----Original Message-----
From: Scons-users [mailto:scons-users-bounces at scons.org] On Behalf Of Stefan
Seefeld
Sent: Friday, June 10, 2016 9:49 AM
To: scons-users at scons.org
Subject: Re: [Scons-users] caching build parameters

Hi Jason,

thanks for your reply.

On 10.06.2016 10:34, Jason Kenny wrote:
> Hi,
>
> You should look at the Variables object in SCons. There is an ability 
> to have it write out options to a file that you can then read back in 
> on the next run.

Have you actually read what I wrote ? I'm using that technique already, but
find it insufficient. Please see my two questions *at the end* of my mail.

On the need for a separate 'config' step: Perhaps you are right and I don't
need that. I simply haven't found a clear way to distinguish an ordinary
build that would reuse any cached values from an invocation that would flush
any caches and recompute the values by running the configure checks.


Thanks,
        Stefan


-- 

      ...ich hab' noch einen Koffer in Berlin...

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