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

Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: speex_vs2008.diff
Type: application/octet-stream
Size: 165590 bytes
Desc: speex_vs2008.diff
Url :
http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj

Aron Rosenberg a ?crit :
> Attached is a patch which adds the directory, project and solution files
> needed for Visual Studio 2008. They are an import of the 2005 files, but
> fixed and tested.
Thanks. Applied.

BTW, ran those just for fun:

% du -sk libspeex
988     libspeex

% du -sk win32
828     win32

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

On 11/27/07, Aron Rosenberg <arosenberg@sightspeed.com>
wrote:
> Attached is a patch which adds the directory, project and solution files
> needed for Visual Studio 2008. They are an import of the 2005 files, but
> fixed and tested.
You sure you imported VS2005 ones? VS2005 do not have projects for
tests yet, but VS2003 and your patch have them.

-- 
Regards,
Alexander Chemeris.

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

The VS2005 project files are known to not be up-to-date, so I can understand
that you'd need to fix some things.
Can you verify with an import of the VS2003 project files, that there is no
need for any fixes, and just works after importing?

Managing multiple project files should be minimized if at all possible.  If
a straight import of vs2003 project files can be done without any changes
post-import, then I'd recommend that vs2008 project files are *not* checked
in.  In fact, I think it'd probably be a good idea to remove the vs2005
project files, given they are not as up-to-date as the vs2003 ones, and
someone with VS2005 can easily import and use them.

The only time that I have found that VS2005 project files need to be
maintained over vs2003 ones is if multiple configurations for different
platforms need to be maintained (i.e. for wince).

On 11/27/07, Aron Rosenberg <arosenberg@sightspeed.com>
wrote:
>
>  Attached is a patch which adds the directory, project and solution files
> needed for Visual Studio 2008. They are an import of the 2005 files, but
> fixed and tested.
>
>
>
> -Aron
>
> Aron Rosenberg
>
> SightSpeed Inc.
>
>
>
> _______________________________________________
> Speex-dev mailing list
> Speex-dev@xiph.org
> http://lists.xiph.org/mailman/listinfo/speex-dev
>
>
>

-- 
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/20071128/667a4b9d/attachment.html

I pulled the test directory from 2003, but everything else from 2005. The 2005
files have more ?cross-compiling? targets than the 2003 ones. I fixed the
various missing files in the new 2008 projects (misc.c and one other other are
gone now).

 

The only thing you could do which would make them more compact would be to get
rid of the subdirectories under each vs-version. There is no real need for it
and it just makes things a little confusing.

 

Win32 ------ vs2003 -----All .sln, .vcproj

            |

            |------vs2005 -----All .sln, .vcproj

            |

            |------vs2008 -----All .sln,.bcproj

 

 

You could also remove the old Visual Studio 6 files, .dsw, .dsp since that
compiler is no longer supported by MS.

 

 

-Aron

 

From: kamaji@gmail.com [mailto:kamaji@gmail.com] On Behalf Of Keith Kyzivat
Sent: Wednesday, November 28, 2007 8:00 AM
To: Aron Rosenberg
Cc: speex-dev@xiph.org
Subject: Re: [Speex-dev] [PATCH] Add Visual Studio 2008 Prject files

 

The VS2005 project files are known to not be up-to-date, so I can understand
that you'd need to fix some things.
Can you verify with an import of the VS2003 project files, that there is no need
for any fixes, and just works after importing?

Managing multiple project files should be minimized if at all possible.  If a
straight import of vs2003 project files can be done without any changes
post-import, then I'd recommend that vs2008 project files are *not* checked
in.  In fact, I think it'd probably be a good idea to remove the vs2005
project files, given they are not as up-to-date as the vs2003 ones, and someone
with VS2005 can easily import and use them.

The only time that I have found that VS2005 project files need to be maintained
over vs2003 ones is if multiple configurations for different platforms need to
be maintained (i.e. for wince).

On 11/27/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote:

Attached is a patch which adds the directory, project and solution files needed
for Visual Studio 2008. They are an import of the 2005 files, but fixed and
tested.

 

-Aron

Aron Rosenberg

SightSpeed Inc.

 


_______________________________________________
Speex-dev mailing list
Speex-dev@xiph.org
http://lists.xiph.org/mailman/listinfo/speex-dev







-- 
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/20071128/7fbc2334/attachment-0001.html

On 11/28/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
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?
Well, you could use Mingw with the same autotools files. But then you
will not be able to link Speex statically with VS projects. Other variant
is to use some generator, which will use autotools-like files to
generate VS project files. But I do not know any such generator which
will support all required VS versions. If anybody know - let me know.

-- 
Regards,
Alexander Chemeris.

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

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

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?
Just delete the old versions.   VC6 especially is not worth the trouble 
maintaining the files, especially if you are trying to compile C++.  VC8 (2005) 
is free and works well, so maybe remove projects for versions older than that? 
   Also, write in the README what some of the required options are and what 
files to include and not include in a VS project and people can set up their own
project files if necessary for one of the older versions.

(I don't know anything about 2008 yet.)

Reed