Re: Choosing vc++ setup for 14.1
Steven Watanabe via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Organization | Providere Consulting, Inc. |
| Message-ID | <[email protected]> |
AMDG On 10/22/2018 11:53 AM, Edward Diener via Boost-build wrote: > On 10/22/2018 1:24 PM, Steven Watanabe via Boost-build wrote: >> On 10/22/2018 10:55 AM, Edward Diener via Boost-build wrote: >> <snip> >> msvc depends on the version to find the location >> of the compiler. Mangling the version prevents >> this from working correctly. Just pass cxxstd=14 >> or cxxstd=17 to b2 when building. > > There are more flags I would like to pass than just cxxstd for different > invocations and you are saying I need to pass them manually all the time > using a single 'using' declaration for a particular version of msvc. Your other thread is on the right track. > That is also a bit of a pain since I must also pass any flags, which > contain the colon character, in quotes since b2 treats the colon in some > special way. ':' is used to separate arguments. > Could not Boost Build logic parse the version number from > any cruft that comes after it by looking for a non-numeric non-dot as > the end of the version number, and just use that version number to > determine the msvc-setup ? In other words, for example, Boost Build > parses 14.1 as release 14.1 but parses 14.1c14 as release 14 for the > purpose of creating the correct msvc-setup.bat. How hard would it really > be to correct the latter to release 14.1 ? > Actually, you're probably hitting the final fallback of searching PATH. All the code for finding the path based on the version number requires an exact match. In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build