<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 12:30 AM, Erik de Castro Lopo <span dir="ltr"><<a href="mailto:mle%2Bla@mega-nerd.com">mle+la@mega-nerd.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">Keith Kyzivat wrote:<br>
<br>
> And Alex has told me that visual studio-built projects cannot link with<br>
> mingw-win32-gcc produced DLLs...<br>
<br>
</div>This is only true when the DLL being called exports C++ name mangled<br>
symbols.</blockquote><div><br></div><div>Is there a way to get mingw to produce the same name mangling, to get around the issue?</div><div>I know this may not be the case for speex, but I'm curious for C++, because I would *love* to get rid of the VS project files for another project (which uses C++).</div>
<div><br></div><div>If not that, are there any tools that can alter a mingw-produced DLL (produced from C++ code) to make it linkable to VS produced executables?</div></div><br>-- <br>Keith Kyzivat<br><br>SIPez LLC.<br>SIP VoIP, IM and Presence Consulting<br>
<a href="http://www.SIPez.com">http://www.SIPez.com</a><br>tel: +1 (617) 273-4000<br>
</div>