On Fri, 26 Oct 2018 at 11:44, Edward Diener via Boost
There is no need to try and do that. Earlier releases for Windows were built targeting gcc, not vc++. It was only with later releases that the default build of clang for Windows targeted vc++.
You seem to continuously miss the point. I don't want to have anything to do with GCC!
But whatever the default build of clang for Windows targeted you could always use the compile/link -target switch to change it at runtime.
How does that work with C++-name-mangling? Aside from the use of different jam files for clang and clang-cl, Apart from this detail, it's exactly the same, WTF!
and the fact that clang-cl allows vc++ like options, clang-cl and clang targeting vc++ work exactly the same.
Yes, this is true, the above is the problem. I have experienced some linking issues when running Boost tests for
various libraries for nearly every release of clang. John Maddock also brought this up in a past thread. If you had a solution for the linking issues that worked I did not see it.
Until this "targeting gcc" get's clarified, it's all like spaghetti on the wall. I do not understand what "targeting gcc" even means in this context. GCC does not work [on Windows] outside MinGW as far as I know, but this implies everything should be compiled that way [inside MinGW].
way of proper correct working linking [it works for the rest of us]. I doubt clang-7.0 brings any relief in solving your problem, because the changes in clang are not at that [basic] level, it also always worked fine with clang-6, clang-5, clang-4, clang-3.9 and clang-3.8 [in respect of
Other than the above gcc-targeting I don't see what [for you] comes in the the
latter two, the number of ICE's were rather prohibitive for anything over "Hello world.", though].
Again this is your experience but not mine.,
Well, I am not 'targeting gcc' and as far as I know this is not something clang-cl is doing [whatever that means]. FYI, Microsoft is using clang-cl as a test case for their STL, they also use Boost as a test-case. If there were problems linking stuff, I'm sure somebody would have noticed at some point. In order to get forward at all, we need to: 1. Forget about GCC! It's got nothing to do with GCC. 2. Don't call clang++.exe in the config file, as this invokes the incorrect [linux] jam.file [as confirmed by Peter]. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*