[Mingw-w64-public] -fno-leading-underscore should be default?
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. -- 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
Re: [Mingw-w64-public] -fno-leading-underscore should be default?
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
Re: [Mingw-w64-public] -fno-leading-underscore should be default?
Graham Greene graham.gre...@charter.net wrote on 04.03.2009 07:17:05: 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 On Win64 there is just __fastcall convention. Any other calling convention is treated, but makes no differences on calling convention, nor on name decoration. At the moment we decorate C symbols by an underscore, this have to be changed in future release. The reason why I did this was, that first the world within our toolchain has to proven as valid. While 4.5 gcc is running, I plan to change the default behaviour of x64. Cheers, Kai | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | ()_() world domination. -- 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
