From: Peter Dimov (pdimov_at_[hidden])
Date: 2023-09-28 13:03:32
Tom Kent wrote:
> On Wed, Sep 27, 2023 at 7:12 PM Peter Dimov <pdimov_at_[hidden]
> <mailto:pdimov_at_[hidden]> > wrote:
>
>
> Tom Kent wrote:
> > Any ideas on how I can convince that build to use msvc-14.3 while
> keeping
> > msvc-10.0 in my user-config.jam? I'm guessing there is some auto-
> picking
> > logic at play that I might be able to control? I'd like to keep still testing
> with
> > that version of visual studio a bit longer, thus I don't want to
> completely get rid
> > of it.
>
> Easiest is probably just to put 14.3 first (in user-config).
>
>
>
> That did make msvc-14.3 the build tool (b2 documentation on user-config.jam
> could be improved to say order matters), however it didn't solve the problem.
>
> New output here:
> https://gist.github.com/teeks99/4b0bf5fea31c972be8f3d79fd71bf774
>
> The end:
>
> [3] msvc-14.3/release/build-no/link-static/python-2.7/threadapi-
> win32/threading-multi/visibility-hidden
> ...found 1 target...
That's odd. Even the "has BCrypt API" check fails, and it should succeed.
What does config.log in the binary directory contain?