[Scons-users] dry runs and Configure

Bill Deegan bill at baddogconsulting.com
Wed Aug 2 13:09:58 EDT 2017


What happens if you comment out the Exit()'s?
Do you see messages for each Check*?
Or does it bail out after one?

-Bill
p.s. Not suggesting as a resolution, just curious.

On Wed, Aug 2, 2017 at 4:28 AM, Mats Wichmann <mats at wichmann.us> wrote:

> On 08/01/2017 03:49 PM, Bill Deegan wrote:
> > Would scons -k -n work for you?
>
> well, no, because it still quits at that point (either because "continue
> as much as possible" left nothing possible, or just because it hits the
> Exit line)
>
> >
> > 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
> >>
> >
> >
> >
> > _______________________________________________
> > 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/20170802/4397d58b/attachment.html>


More information about the Scons-users mailing list