Hi Joshua, good to hear from you.
I just tried to build libmad on Linux last night and "configure"
complained that a file was missing. If you have a chance, please take a
look and see if you forgot to check in a file. Otherwise I'll probably
figure it out soon.
> Alright, I built a debian package for 0.97 and uploaded it, it should be
> in unstable by tomorrow or the next day. A few notes:
> * A bug was filed on the debian package since its config.guess and
> config.sub were out of date (these are scripts that ./configure uses
> to determine the arch and os when it is run). The newer versions can
> correctly detect newer architectures like ia64, but in actuality this
> didn't have any adverse effect on Audacity, since all we depend on it
> to do is correctly detect if i386 and Linux are present. However, I
> replaced these files with the newer ones both in the Debian package and
> in CVS
> * Nice improvements to the makefile. It's nice to finally have an
> "install" target :-)
It looks like I should have added some mkdirs to "make install" - one
person complained that it fails if the directory we try to install to
doesn't exist. This should only affect the help files on Linux.
If it's not too late, do you want to fix that in the .deb?
> * There is a bug in the 0.97 sources that will prevent Audacity from
> finding its help file on Windows. on line 114 of Help.cpp:
> paths.Add("C:\Program Files\Audacity\audacity-help.htb");
> Notice you didn't escape the backslashes. But on second thought, it
> will probably find it anyway since it's in the same directory it's run
Oops. I guess I never tested it in a setup where it couldn't find the
help file. Note that I also added a "Locate Help File" menu option -
that at least gives the user a way out if they have two versions
installed at once, and it's going to an old help file.
> I think that's it, but my thoughts are scattered. Nice job getting 0.97
> out the door -- the installer on Windows is really nice too.
I agree - thanks, Logan.
I'm partway done integrating libsndfile and so far it works like a
charm. I'll try to have the trunk building again on all three platforms
soon - right now the lib-src libraries are not set up properly.
Thought question: How should we handle building the sublibraries?
1. Use one configure script which builds all of the libraries. This
would involve merging their scripts into ours, which is probably
impossible for all but the simplest of libraries.
2. Our configure script recursively calls the sublibraries' configure
3. Our configure script just configures Audacity, and then "make" calls
configure on each sublibrary if necessary. (This is what I did for 0.97