Aron Rosenberg
2007-Nov-28 20:29 UTC
[Speex-dev] [PATCH] Add Visual Studio 2008 Prject files
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
Keith Kyzivat
2007-Nov-28 21:06 UTC
[Speex-dev] [PATCH] Add Visual Studio 2008 Prject files
Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote:> > 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 >-- 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/f6936e7f/attachment.htm
Jean-Marc Valin
2007-Nov-29 09:09 UTC
[Speex-dev] [PATCH] Add Visual Studio 2008 Prject files
Keith Kyzivat wrote:> Ok! > If there are indeed cross-compiling targets defined, then vs2005 > projects probably should be maintained. > > In any case, this is all up to Jean-Marc, since he's the one that > actually has authority to change it :) > Jean-Marc -- what's your opinion?It's actually Alexander Chemeris who's "officially" in charge of the Windows crap^H^H^H^Hproject files. My opinion is that I don't want to have anything to do with it, but as long as people want it and someone volunteers to maintain it, I'm fine keeping that around. To give you an idea, I've never even compiled Speex on Windows (don't even have Windows on my machine, much less VS200x), so I'm the least qualified to comment on the project files themselves. Jean-Marc> > On 11/28/07, *Aron Rosenberg* <arosenberg@sightspeed.com > <mailto:arosenberg@sightspeed.com>> wrote: > > 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> > [mailto: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 <mailto: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 > <mailto: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 <mailto: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: Web Bug from chrome://skype_ff_toolbar_win/content/space.gif > Web Bug from chrome://skype_ff_toolbar_win/content/space.gifWeb Bug > from chrome://skype_ff_toolbar_win/content/space.gif Web Bug from > chrome://skype_ff_toolbar_win/content/space.gif+1 (617) 273-4000 > > > > > -- > Keith Kyzivat > > SIPez LLC. > SIP VoIP, IM and Presence Consulting > http://www.SIPez.com > tel: +1 (617) 273-4000 > > > ------------------------------------------------------------------------ > > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/speex-dev
Alexander Chemeris
2007-Nov-29 14:13 UTC
[Speex-dev] [PATCH] Add Visual Studio 2008 Prject files
On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote:> You could also remove the old Visual Studio 6 files, .dsw, .dsp since that > compiler is no longer supported by MS.Well, MS wants all to use their latest software (and pay for updates). Not all users want to upgrade, if existing software fulfil their requirements. E.g. we have customers who still use VS6. So it is still used, even if not supported. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000