(linux) build breaking: 'wxLocale' does not name a type

[Edgar]

@Lightning

well, this ain’t a slackware-specific problem. i also found similar problems for gentoo or arch people e.g… we all have in common, that we’re rolling release distris with bleeding edge (but stable) software. so of course we use latest gcc, latest glibc and so on. changing the compiler is definitely no option at all; no one would even think about that.

i guess the wx-lists AND the audacity-lists are the right place for this problem (unless somebody has a tip in here ). wx because these guys potentially didn’t manage to write correct/compliant code (which is absolutely their job) and audacity because the autoconf-scripts of audacity should detect the “quirks” (let’s call it that way, although it’s just the right behavoir) and set additional compiletime-flags for gcc OR because audacity code needs some additional ifdefines for recent libs and compilers.

i’ll write to the lists next week.
i’ll also try to compile audacity against wxwidgets’ unstable branch; maybe the code has already been corrected (last wx-stable release is 3/4 year old). (did anyone already try wx 2.9 with audacity?)
i have only a little time atm, but maybe i’ll find a minute during holidays to do some code-analysis and write some patches for wx and/or audacity.

Team Audacity is especially resistant to “bleeding-edge”! You think you have it bad? They will not even support the two most recent releases of Microsoft’s Visual Studio (2010 and the new version 11–probably will be called 2012) insisting that only MS VC++ 2008 is supported. I understand this as the “bugs” in Audacity code which are exposed by the newer compilers are a hassle to fix, see:

Success compiling Audacity with VS2010

In your Audacity directory, convert win/audacity.sln by opening it in MS VS2010 (this needs to be an up-to-date version–use Windows Update service and make sure you are set to “update other products from Microsoft”). DO NOT attempt to build it yet! After the conversion, in the /win/ folder you will find the newly-created-during-conversion file: ny.props Open this file with a text editor and replace it with the following: <?xml version="1.0" encoding="utf-8"?> <Project xmlns="http://schemas.m…

As for moving Audacity from 2.8 to 2.9, the many API changes between the two make this a chore, but it is do-able:

moving to wxWidgets 3.0

Currently Audacity will not build with any wxWidgets release beyond the 2.8 series; wx29 has many bug fixes which might benefit Audacity but the Audacity code needs some massaging to make it wx29+ compliant. The included patch is stale and will need to be applied manually, it was current as of when I created it but changes will have been made since then! I can only test this on Windows 7 so other OSes will have minor differences which are not explored here. On Windows one must change all the so…

For a look at a discussion about moving an app from wx28 to wx29/30 read this thread:
http://groups.google.com/group/wx-dev/browse_thread/thread/dfca1c6bd6deffb8/38804e0a75b077a0?show_docid=38804e0a75b077a0

and for some info on Linux distros:
http://groups.google.com/group/wx-dev/browse_thread/thread/58c444b73e08a9a9/73853ddc0c08a716?show_docid=73853ddc0c08a716