Re: Meaning of gcc-mingw toolset
Edward Diener via Boost-build <[email protected]> Thu, 16 Apr 2020 09:35:52 -0400
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <[email protected]> |
On 4/16/2020 7:03 AM, Steven Watanabe via Boost-build wrote: > AMDG > > On 4/15/20 4:45 AM, Edward Diener via Boost-build wrote: >> In the multiprecision testing jamfile there is a line which has the >> requirement: >> >> <toolset>gcc-mingw:<cxxflags>-Wa,-mbig-obj >> >> I do not see a toolset called gcc-mingw nor do I see a subfeature of the >> gcc toolset called mingw. > > The subfeature is called flavor. > >> I do realize that the gcc toolset has support >> for mingw gcc on Windows, which I use myself in my user-config.jam with >> the plain designation of: >> >> using gcc : nnn : etc ; >> >> but the nnn is always a version number, like 9.3. The gcc.jam picks up >> that this is mingw-w64/gcc implementation internally and works fine with >> it. But whatever '<toolset>gcc-mingw' is supposed to mean it does not >> applu to my "toolset=gcc-nnn' when I run the test. > > What is the path component for the toolset? It should be > gcc-mingw-nnn. Otherwise the detection for mingw isn't working. > Also, I recall that there used to be problems if you have both > mingw and non-mingw versions of gcc. I don't remember whether > that was ever fixed. What do you mean by "the path component of the toolset" ? _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build