Re: [Audacity-devel] 1.2 branch configure script
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Richard A. <ri...@au...> - 2006-08-02 19:11:07
|
Right, I've fixed and committed the 1.2 branch script with these changes, so it should work with either 2.4 or 2.6 wx-config scripts first in the path. I'm happy to release at this point, so unless anyone has big objections I'll start on the maketarball script and check the readme.txt etc. Richard On Wed, 2006-07-19 at 23:19 +0100, Richard Ash wrote: > On Tue, 2006-07-18 at 02:22 -0700, Dominic Mazzoni wrote: > > On Jul 17, 2006, at 12:44 PM, Richard Ash wrote: > > > Is there any reason why the ./configure script for 1.2 branch has the > > > argument "--version=2.4" added to all the WX-CONFIG calls? This > > > utterly > > > breaks the configure process for me - wx-config for wxGTK 2.4.2 > > > doesn't > > > accept a --version= argument at all. > > > > > > There is also an attempt to look for installed versions using --list, > > > which similarly doesn't work if you have wx 2.4 > > > > > > I've changed these, and tweaked the failure message a little so it > > > works > > > under Linux. Unless anyone complains I'll check them in (configure.in > > > and configure)? > > > > Ohhh....I added these because on all of my machines I have both wx > > 2.4 wx 2.6 installed, and Audacity 1.2 was trying to configure itself > > with wx 2.6. > > > > I guess it'd be preferable if it could run "wx-config --version" and > > if the answer is "2.4" it should set WX_CONFIG to wx-config and > > stop. For anything else it should try the options I gave it. > > > > Alternatively we can require the user to set the WX_CONFIG > > environment variable. We could have the configure script stop and > > suggest a WX_CONFIG setting if it detects wx 2.6. > > I see. Under Gentoo /usr/bin/wx-config is a symlink to (one of) the > wxgtk 2.4 binary, so that get's found by default. When something needs > 2.6 I set WX_CONFIG when running configure to find the right version. > Portage builds do the same thing via some utility functions to get the > desired version. |