NightStrike wrote: > On Tue, Mar 3, 2009 at 2:16 PM, Jackie <kjac...@gmail.com> wrote: >> Hello, >> >> I got some problems when I tried to use the library compiled by >> mingw-w64 in VS2008, then I search the issue on the web. It says >> mingw-64 and msvc use different function name decoration, and it seems >> can be solved by using "-fno-leading-underscore" to compile CRT and >> other base libraries. However, all of the binaries (for Linux) >> distributed on SF.net still have this problem. Both Win64 and MSVC are >> created by M$, and mingw-w64 is intent to create things for Win64, isn't >> it? Why not make things compatible with MSVC? >> >> Best regards, >> >> Kai-Chieh Ku. > > I see your point. Since we are emulating MS, you are saying we should > emulate them as default, and provide alternates via options. > Currently, we are using the alternate as the default and emulating MS > as an option. > > I don't personally know which is best.
Does this have to do with exported __stdcall functions not having an underscore prefix on their symbol name? gg ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
