On Thu, Sep 30, 2010 at 9:43 AM, Dongsheng Song <[email protected]> wrote: > Maybe there have another solution: > > S1: the intersection of XP and 2k3 symbols in msvcrt.dll > S2: the intersection of VISTA and 2k8 symbols in msvcrt.dll > S3: the Windows 7 symbols in msvcrt.dll > > libmsvcrt: S1 > libvista: (S2 - S1) > libwin7: (S3 - S1) or (S3 - S2) > > If user want to use symbols in VISTA/2K8, they should put libvista in > additional library list. > Then the generated files only valid on vista/2k8 or later is acceptable for > these users. > > If user want to use symbols in Windows 7, they should put libwin7 in > additional library list. > Then the generated files only valid on Windows 7 or later is acceptable for > these users.
I tend to think this is not related to Windows versions. As mentioned msvcrt.dll does not have this, no matter it is Windows 7 or Windows Vista. They are in the run time for VS2003/2005/2008/2010 which can be installed in XP/Vista/7. These runtime dlls are not named msvcrt.dll. But I agree with your subject "please get rid of symbols from mingw-w64-crt\lib32\msvcrt.def which belong to msvcr70.dll and msvcr80.dll". Since they are after all not belong to msvcrt.dll but rather msvcr70.dll, msvcr80.dll or later. -- Xiaofan ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
