Speex dev - Dec 2007 - [PATCH] Add Visual Studio 2008 Prject files

Jean-Marc Valin wrote:
...
> I think the amount of Windows crap is getting a bit ridiculous. Does
> anyone know of a solution to keep things manageable? I mean, the same
> autotools files manage the build for Linux PCs, Blackfins and MacOS (and
> others). Yet, we need one set of files for each MS compiler version
> (good thing they don't practice "release early, release
often"). There
> has to be some simpler solution. Anyone?
> 
> 	Jean-Marc
The autotools files can also be used to build Win32 libraries using 
mingw32 (preferably cross-compiling on GNU/Linux). It's currently 
possible to build static libs. To be able to build DLLs you need to add 
AC_LIBTOOL_WIN32_DLL to configure.ac.

--- speex-1.2beta2/configure.ac 2007-05-17 16:14:35.000000000 +0200
+++ speex-1.2beta2.my/configure.ac      2007-11-29 23:33:37.000000000 +0100
@@ -30,6 +30,7 @@
  AM_MAINTAINER_MODE

  AC_CANONICAL_HOST
+AC_LIBTOOL_WIN32_DLL
  AM_PROG_LIBTOOL

  AC_C_BIGENDIAN

Mikael

On 11/30/07, Mikael Magnusson <mikma264@gmail.com>
wrote:
> The autotools files can also be used to build Win32 libraries using
> mingw32 (preferably cross-compiling on GNU/Linux).
Why "preferably"? I thought they are building fine from under Win with
MinGW.
> It's currently possible to build static libs. To be able to build DLLs
you
> need to add AC_LIBTOOL_WIN32_DLL to configure.ac.
Yeah, but this static libs are not compatible with VS, afaik?

-- 
Regards,
Alexander Chemeris.

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000

On 11/29/07, Mikael Magnusson <mikma264@gmail.com>
wrote:
>
> Jean-Marc Valin wrote:
> ...
> > I think the amount of Windows crap is getting a bit ridiculous. Does
> > anyone know of a solution to keep things manageable? I mean, the same
> > autotools files manage the build for Linux PCs, Blackfins and MacOS
(and
> > others). Yet, we need one set of files for each MS compiler version
> > (good thing they don't practice "release early, release
often"). There
> > has to be some simpler solution. Anyone?
> >
> >       Jean-Marc
>
> The autotools files can also be used to build Win32 libraries using
> mingw32 (preferably cross-compiling on GNU/Linux). It's currently
> possible to build static libs. To be able to build DLLs you need to add
> AC_LIBTOOL_WIN32_DLL to configure.ac.

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)?

-- 
Keith Kyzivat

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/speex-dev/attachments/20071130/81fe0925/attachment.html

Alexander Chemeris wrote:
> On 11/30/07, Mikael Magnusson <mikma264@gmail.com> wrote:
>> The autotools files can also be used to build Win32 libraries using
>> mingw32 (preferably cross-compiling on GNU/Linux).
> 
> Why "preferably"? I thought they are building fine from under Win
with
> MinGW.
> 
It should work on Windows with MinGW+MSYS, but it's building faster on 
GNU/Linux at least if you include the time it takes to run configure. 
Because especially configure creates a lot of processes, and process 
creation is slower on Windows compared to GNU/Linux.
>> It's currently possible to build static libs. To be able to build
DLLs you
>> need to add AC_LIBTOOL_WIN32_DLL to configure.ac.
> 
> Yeah, but this static libs are not compatible with VS, afaik?
> 
No, not the static libs, but DLLs should work.

http://www.mingw.org/mingwfaq.shtml#faq-msvcdll

Mikael

Mikael Magnusson wrote:
> Jean-Marc Valin wrote:
> ...
> > I think the amount of Windows crap is getting a bit ridiculous.
It always was. I'm just surprised you took so long to realise it :-).
> The autotools files can also be used to build Win32 libraries using 
> mingw32 (preferably cross-compiling on GNU/Linux). It's currently 
> possible to build static libs. To be able to build DLLs you need to add 
> AC_LIBTOOL_WIN32_DLL to configure.ac.
For libsndfile, my solution has been :

  - Use MinGW on windows.
  - Release pre-compiled binaries.

I provide basic instructions for compling using MinGW:

    http://www.mega-nerd.com/libsndfile/win32.html

And if anyone asks why I don't just ship project files, I point them
to the FAQ which explains why:

    http://www.mega-nerd.com/libsndfile/FAQ.html#Q019

The main problem with the above is that I need to have a windows
machine that I actually don't use for anything else.

The other problem is that MinGW currently does not support compiling
for 64 bit windows. From what I hear, that is coming.

This may be an option for you to consider.

Erik
-- 
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"I ran it on my DeathStation 9000 and demons flew out of my nose."
--Kaz

>>> I think the amount of Windows crap is getting a bit ridiculous.
> 
> It always was. I'm just surprised you took so long to realise it :-).
Well, it's actually getting worse as MS releases new compiler
versions... I really haven't been paying attention because I've never
compiled it on windows.
> For libsndfile, my solution has been :
> 
>   - Use MinGW on windows.
Does MinGW require any change to the autoconf files or does it work out
of the box.
>   - Release pre-compiled binaries.
Well, I'd still have to rely on 3rd parties, since I don't have a
windows box.
> I provide basic instructions for compling using MinGW:
> 
>     http://www.mega-nerd.com/libsndfile/win32.html
> 
> And if anyone asks why I don't just ship project files, I point them
> to the FAQ which explains why:
> 
>     http://www.mega-nerd.com/libsndfile/FAQ.html#Q019
What you're saying here sounds pretty much like my experience, except
that I'm still including these project files even though they are
sometimes broken.
> This may be an option for you to consider.
Well, I'll see how things to...

BTW, Windows is not quite the only "special" platform, there's the
TI
C55x DSP as well. At least that one has the excuse of not being a
general purpose computing platform.

	Jean-Marc