[Scons-users] dry runs and Configure

[Bill Deegan]

Would scons -k -n work for you?

On Tue, Aug 1, 2017 at 2:13 PM, Mats Wichmann <mats at wichmann.us> wrote:

>
> _still_ trying to figure out how some things are messed up in this
> build. Here's one question. Some code does this... (seems broken anyway
> in a cross-compile environment, where CheckLib ought to check against a
> target lib, but that's not the topic here, that's a different problem to
> solve).
>
>         conf = Configure(lib_env.Clone(LIBS=[]))
>
>         if not conf.CheckLib('boost_thread', language='C++'):
>             Exit('Did not find boost_thread, exiting!')
>
>         if not conf.CheckLib('boost_system', language='C++'):
>             Exit('Did not find boost_system, exiting!')
>
>
> Running "scons -n" dies with:
>
> scons: *** Cannot update configure test ".sconf_temp/conftest_0.cpp"
> within a dry-run.
>
> and then quits, kind of defeating the purpose of using a dry run.
>
> (the error line is the one of the first CheckLib)
>
> is there a best-practices approach to this? namely, to include
> configure-style tests, but not to not break dry-run in doing so?
> _______________________________________________
> 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/20170801/0683d681/attachment.html>