Re: [Audacity-devel] wx linking problem
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
|
From: Gale (A. Team) <ga...@au...> - 2008-10-16 20:02:04
|
Vaughan Johnson wrote: > > > Gale (Audacity Team) wrote: >> >> Martyn Shaw-2 wrote: >> >>> I just logged into my windows XP machine, did a CVS update on >>> Audacity, Cleaned and Rebuilt. It compiled fine but when I tried to >>> run it I got: >>> >>> 'The procedure entry point ?SetLabel@wxChoice@@UAEXABVwxString@@@Z >>> could not be located in the dynamic link library >>> wxmsw28ud_core_vc_custom.dll.' >>> >> >> Has anyone built on Windows with wx 2.8.9 yet, or is this still an issue? >> >> I've compiled Unicode Release Audacity with 2.8.9 fine but get a similar >> problem >> when launching Audacity: >> >> "The procedure entry point ?GetLo@wxLongLongNative@@QBEKXZ could not be >> located in the dynamic link library wxbase28u_vc_custom.dll" >> >> I could not find where the outcome of this thread went, sorry. > > > Yes, per my update of compile.txt and email to Rupinder, I've built on > Windows with 2.8.9 and it works fine. I'm pretty sure the problem is > that you haven't copied the new wxWidgets DLLs to your Audacity > executable directory (or updated your PATH if that's the way you > prefer). I made the same mistake at first, and that's why I added the > step in compile.txt. (I didn't give instructions about PATH because the > installer script expects them in the exe directory.) Thanks. Hmm. I was particularly careful to see that I had copied the five newly built wxWidgets dlls to the folder containing the Audacity executable. Maybe it's some kind of caching problem/picking up the old dll's somehow? I'll have to reboot/maybe do a fresh Audacity checkout and let you know. In fact I wonder, where we added the step in compile.txt about copying over the five Widgets dll's, if we are duplicating it, and perhaps confusing things because of that? We have it at MSVC++ STEP 2: point 4: "4. Copy the DLL's from "C:\wxWidgets-2.8.9\lib\vc_dll" to the corresponding build directory, so the Audacity executable can access them" which seems it might refer to the Widgets build directory (we don't mean that do we?), and then again correctly I think at MSVC++ STEP 5: "You'll need to provide each Audacity executable access to the wxWidgets DLLs that you built in "MSVC++ STEP 2: Build wxWidgets" above. You can put them in your Windows PATH, or simply put them in the same directory as the executable..." And do we need a note that if you are building for distribution to others you need to include msvcr80.dll and msvcp80.dll in case the users do not have those? Gale -- View this message in context: http://n2.nabble.com/wx-linking-problem-tp834845p1342498.html Sent from the audacity-devel mailing list archive at Nabble.com. |