Re: [Audacity-devel] Need help on building Audacity using VC++ 6.0 using the latest WxWindows 2_4_BRANCH

[Markus M. <me...@me...>]

Vaughan,

I now tested compiling Audacity-Pre4 (the tarball) under Win2000 /
MSVC++ 6.0 SP5. In short, it doesn't compile out of the box at all.

First regarding our original problem: I removed the
/NODEFAULTLIB:msvcrtd before doing anything. This alone didn't cause any
problems, specifically I had no lib conflicts when linking the final
audacity.exe file. I also double-checked the settings and found nothing
suspicious. Maybe some other lib on your system still uses a
"Multithreaded DLL" setting? (Think external vorbis lib / libid3tag or
something). I propose to remove the /NODEFAULTLIB clause, because we
should be able to do without it, and providing it just prevents the user
to detect a misconfiguration of her system.

Now to some other things:

Libnyquist complained it couldn't find "xlisp\xlextstart.c" and
"tran/quant.c.c". I removed these from the project file (locally), after
that compilation did continue. I don't know exactly what's wrong here,
but these files are apparently not needed when building Audacity on
Windows, so they can just be left out.

Also, the linker wanted to link with libid3tag, madd.lib and the
ogg/vorbis libs, although they are switched off per default in
'configwin.h'. I removed them manually from the list of linked files.
They could be included via a '#pragma lib' instead being in the main
config.

Let me know if I should try to correct any of these problems, for now
I'll just try to get some sleep.


Markus


Am Don, den 19.02.2004 schrieb Markus Meyer um 10:12:
> Vaughan,
> 
> I'll make a note of this and look at it in the afternoon (GMT+1). I
> remember that last time I compiled Audacity I had to tweak some
> settings, but my Windows build environment is such a mess due to
> different installations of wxWindows etc., so I really didn't think it
> could be a general problem.
> 
> 
> Markus
> 
> Am Mit, den 18.02.2004 schrieb Vaughan Johnson um 22:33:
> > I don't know much about this stuff, but currently, in the MSVC++ 
> > Project: Settings: Link tab for Audacity, the debug version won't link 
> > without /nodefaultlib:"msvcrtd.lib" in the Project Options. The release 
> > version has no such /nodefaultlib. If I understand Markus's reply, then 
> > apparently we've got a lib to link in whose debug version is built with 
> > msvcrtd.lib but the release version is built with libcmt.lib. Is that 
> > right?
> > 
> > If so, I guess we need to go through all the included libs' settings and 
> > correct that, right?
> > 
> > -Vaughan
> > 
> > 
> > Markus Meyer wrote:
> > 
> > >As I understand this, ignoring libraries can be done as a last
> > >workaround, e.g. if you have a pre-compiled (binary-only) library which
> > >you can't recompile. Obviously, you then don't have any option other
> > >than trying to get it working by tweaking linker settings, but the
> > >caveats regarding memory allocators and single/multithreaded
> > >environments do apply nevertheless.
> > >
> > >Anyway, with Audacity this should never be required, because everything
> > >can be recompiled to use the same runtime library.
> > >
> > >
> > >Markus
> > >
> > >Am Mit, den 18.02.2004 schrieb Dave Fancella um 01:02:
> > >  
> > >
> > >>On Wednesday 18 February 2004 07:52 am, Markus Meyer wrote:
> > >>    
> > >>
> > >>>Am Die, den 17.02.2004 schrieb Dave Fancella um 18:42:
> > >>>      
> > >>>
> > >>>>You must use one or the other of msvcrt or libcmt, but *not* both.  So
> > >>>>ignore one and I bet it'll link.  I would ignore msvcrtd.lib, because
> > >>>>that will dynamically link to the msvc runtime dll and require that you
> > >>>>have that dll present when you run audacity.  If you link to libcmtd
> > >>>>instead, it'll statically link the msvc runtime and you won't need the
> > >>>>dll present.
> > >>>>        
> > >>>>
> > >>>Never ignore libraries. These warning / errors do have a purpose. For
> > >>>example when libraries use different memory allocators this can lead to
> > >>>program crashes and memory corruption.
> > >>>      
> > >>>
> > >>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/HTML/lnk4098.asp
> > >>
> > >>The way I read this page, you're supposed to ignore libraries.  :)  Sorry.  
> > >>Maybe I'm reading it wrong?  In the past, when I've tried to use the 
> > >>particular setting you're referring to to solve this problem, it's failed and 
> > >>I had to resort to using the 'ignore libraries' settings in the linker tab to 
> > >>correct it.  There's always the possibility I'm smoking crack, of course.  
> > >>I've also never tried to compile audacity with msvc++, so I'm not referring 
> > >>to any actual experience with audacity, here.  ;)
> > >>
> > >>Dave
> > >>
> > >>    
> > >>
> > >>>The problems mentioned should go away by simply choosing the correct
> > >>>runtime library ("Multithreaded" in this case for release builds) for
> > >>>every project which is linked to. Especially wxWindows must use the same
> > >>>setting as Audacity (which it doesn't by default). This is described in
> > >>>"win/compile.txt".
> > >>>
> > >>>
> > >>>Markus
> > >>>
> > >  
> > >
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Audacity-devel mailing list
> > Aud...@li...
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel