Re: [Audacity-devel] documenting dependencies

[Leland <le...@au...>]

Richard Ash wrote:
> 
> This seems likely to cause problems for a release, so we are obviously
> going to have to do something. The options are basically:
> * Attack the file timestamps so that it doesn't try to run autoconf.
> Anyone who is going to run autoconf still needs to install the relevant
> macros. At the mercy of how CVS handles timestamps.
> * Attach the makefiles with the same ends. More robuts, but still
> requires external packages to run autoconf.
> * Import the macros into the audacity tree, so that you don't need the
> autoconf-archive macros installed to run autoconf. Increases the source
> tarball weight a bit, but is the most robust solution. Needs some
> architectural work on the build system so keeping them up to date isn't
> a chore.
> 
It's only 3 macros (6 if you do C++ versions to) that are needed...about 
20KB.

* Remove the -Wall and -pedantic checks from configure.ac script.

Just another possibility...

Leland