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

Keith Kyzivat a ?crit :
> Something to look into perhaps is Trolltech's 'qmake' tool.
> It fills the role of something like autotools or now defunct imake.
I think TrollTech deserves a prize for their accomplishment in making
qmake even worse than autotools (I'm using it for something else and
wish I wasn't -- Qt itself is fine though). I've heard good things about
CMake though. I've no idea how it works, but if it's cross-platform like
the devs say it is, maybe it could be an option. Anyone with experience
with CMake? (or even better, willing to write makefiles for it)
> As far as I understand, you can indeed use it for projects that don't
do
> anything with the Qt libraries.
> Now, it may not have the support for multiple targets that it sounds like
> are needed for speex, and I know it doesn't have as comprehensive of
> platform-independent support as autoconf (i.e. it doesn't quite do
> feature-testing, IIRC),
> but it will generate project files, though it is unclear if it provides
> creation of all the different versions of projects we're looking for
(VC6,
> VS2003, VS2005, VS2008).
qmake is just insanely limited in terms of the structure of your code
(can't have an executable if you have a library, ...). On top of that,
I've had way too many cases where it just "forgot" to recompile
files
when a header file changed (causing strange segfaults) that I'm never
trusting it anymore.

	Jean-Marc

On 11/29/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:
> qmake is just insanely limited in terms of the structure of your code
> (can't have an executable if you have a library, ...). On top of that,
> I've had way too many cases where it just "forgot" to
recompile files
> when a header file changed (causing strange segfaults) that I'm never
> trusting it anymore.

Ahh good to know!
I'll steer clear of it from now on then.
I wasn't ever that fond of it to begin with, but from the experiences I have
had with it, it's more pleasant to use than dealing with MS project files
(granted, I was staying away from Windows for that project anyway).

-- 
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/20071129/6210bd61/attachment.htm

What's wrong with a plain old .bat file, or even an NMAKE .mak file?  Ship
two files, debug.bat and release.bat, and call it good.

It is best to leave project-file creation up to individual users, in my opinion.
MS changes their IDEs and project-file formats more often than most people
change their underwear.  The odds that any given open-source project will
actually compile without any tweaking are basically zero anyway, so you might as
well make the build steps as clear and obvious as possible.

Only half-joking...

-- john

  -----Original Message-----
  From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org]On Behalf
Of Keith Kyzivat
  Sent: Thursday, November 29, 2007 3:26 PM
  To: Jean-Marc Valin
  Cc: speex-dev@xiph.org
  Subject: Re: [Speex-dev] [PATCH] Add Visual Studio 2008 Prject files


  On 11/29/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:

    qmake is just insanely limited in terms of the structure of your code
    (can't have an executable if you have a library, ...). On top of that,
    I've had way too many cases where it just "forgot" to
recompile files
    when a header file changed (causing strange segfaults) that I'm never
    trusting it anymore.

  Ahh good to know!
  I'll steer clear of it from now on then.
  I wasn't ever that fond of it to begin with, but from the experiences I
have had with it, it's more pleasant to use than dealing with MS project
files (granted, I was staying away from Windows for that project anyway).
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/speex-dev/attachments/20071130/c9e2758f/attachment.html