On 11/29/07, <b class="gmail_sendername">Mikael Magnusson</b> <<a href="mailto:mikma264@gmail.com">mikma264@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jean-Marc Valin wrote:<br>...<br>> I think the amount of Windows crap is getting a bit ridiculous. Does<br>> anyone know of a solution to keep things manageable? I mean, the same<br>> autotools files manage the build for Linux PCs, Blackfins and MacOS (and
<br>> others). Yet, we need one set of files for each MS compiler version<br>> (good thing they don't practice "release early, release often"). There<br>> has to be some simpler solution. Anyone?<br>
><br>> Jean-Marc<br><br>The autotools files can also be used to build Win32 libraries using<br>mingw32 (preferably cross-compiling on GNU/Linux). It's currently<br>possible to build static libs. To be able to build DLLs you need to add
<br>AC_LIBTOOL_WIN32_DLL to <a href="http://configure.ac">configure.ac</a>.</blockquote><div><br>Ok, but are those resultant static libs that mingw32 able to be used within other Visual Studio projects? (i.e. can you get mingw to generate MS compatible static libs)?
<br></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