[Scons-users] Failure when linking against the output of a SCons Install

[John Finlay]

Hi Bill

Thanks for getting back to me

1) I’m using Python 2.7.13
2) We’re seeing the issue when building on Windows 10 and Server 2012 R2
3) Yes, we’re using a parallel build
4) I think the output of --tree=prune is showing me what I’d expect. The following is a paraphrased version of what it shows.
  +-bin\binary.exe
    +-output\library.lib
      +-build\library.lib

Cheers,
John

From: Scons-users [mailto:scons-users-bounces at scons.org] On Behalf Of Bill Deegan
Sent: 16 May 2017 15:16
To: SCons users mailing list
Subject: Re: [Scons-users] Failure when linking against the output of a SCons Install

John,
A couple questions:
1) What version of Python
2) Which version of windows
3) Are you building in parallel
4) Does the build\library.lib show up where you'd expect in scons --tree=prune
-Bill

On Tue, May 16, 2017 at 1:33 AM, John Finlay <j.finlay at indigovision.com<mailto:j.finlay at indigovision.com>> wrote:
Hi All

We are currently trying to migrate from SCons 2.3.6 to SCons 2.5.1 but are experiencing an issue when linking against libraries created earlier in the build.

The portion of the build that is giving us an issue is structured as follows
1) Use Scons to compile a library 'build\library.lib'
2) Use Scons "Install" to copy the library from 'build\library.lib' to 'output\library.lib'
3) Use Scons to compile a exe, linking the library 'output\library.lib'

This sequence has worked fine with SCons 2.3.6 (and versions prior to that). However when using SCons 2.5.1 step 3 fails and the error given is
  fatal error LNK1104: cannot open file 'output\library.lib'

After the failure I can see that 'output\library.lib' exists and can be opened. Also if I re-run scons the incremental build re-runs step 3 and it succeeds.

My theory is that with SCons 2.5.1 step 3 is being started before step 2 has completed, so when the linker tries to open the library it fails as it's still being copied.

Does my theory sound like it could be true, and are we doing something fundamentally wrong by trying to linking against something that is the output of a SCons Install?

Thanks,
John


_______________________________________________
Scons-users mailing list
Scons-users at scons.org<mailto: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/20170516/20905a8d/attachment-0001.html>