WSL-4.0 and __MSVCRT_VERSION__
Keith Marshall <[email protected]> Fri, 23 Aug 2013 21:34:59 +0100
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Organization | MinGW Project |
| Message-ID | <[email protected]> |
Earnie,
Reading your NEWS items for the WSL-4.0 release, I see a possible issue
concerning the change in usage of __MSVCRT_VERSION__. In mingwrt-3.x
and w32api-3.x, this macro could be used to convey the user's intent to
link with MSVCRxx.DLL *other* than plain old MSVCRT.DLL. However,
simply defining __MSVCRT_VERSION__ alone was never enough; the user also
had to tweak the GCC specs, to *remove* the automatic reference to
-lmsvcrt, and to *substitute* -lmsvcrxx.dll; (see my comments on
http://mingw.org/wiki/SpecsFileHOWTO
for further details).
As written up in your NEWS item for WSL-4.0, you suggest that it is now
only necessary to *add* -lmsvcrxx; surely this is not the case, for the
automatic reference to -lmsvcrt.dll will still be added by GCC specs.
It may be true that the definition of __MSVCRT_VERSION__ can become
redundant, but isn't the specs file tweak to *substitute* -lmsvcrxx.dll
for -lmsvcrt.dll? Without that, surely the user ends up linking with
two mutually incompatible runtime DLLs?
--
Regards,
Keith.
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk