[Scons-users] does use of Configure (e.g. CheckLib) scupper dry run mode?

[Bill Deegan]

Is this a project where you can share the scons logic?
(open source?)

-Bill

On Fri, May 26, 2017 at 8:23 AM, Mats Wichmann <mats at wichmann.us> wrote:

>
> I've had a hunt around for this without finding anything yet, maybe it
> just has obvious answers.
>
> I'm playing with a project which is fairly large... there are some 200
> scons scripts in the tree, and they're, ummm, not that well crafted.
>
> In debugging possible changes I thought it might be useful to run "scons
> -n" to see what I'm breaking without actually doing builds, but that
> dies with messages something like (this one is from a particular
> CheckLib call):
>
> scons: *** Cannot update configure test ".sconf_temp/conftest_0.cpp"
> within a dry-run.
>
> It's a fatal error, can't skip it by adding --ignore-errors, etc.
>
> If the project uses configure tests that would attempt compilation, does
> that mean dry-runs cannot work?  Or is there a way around this?
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170526/fb29c78e/attachment.html>