Re: [Audacity-devel] Fatal Errors with my Build

[Vaughan J. <va...@au...>]

On 3/16/2010 1:57 PM, Al Dimond wrote:
> On Tuesday 16 March 2010 13:24:41 Vaughan Johnson wrote:
>    
>> On 3/15/2010 5:59 PM, Al Dimond wrote:
>>      
>>> On Monday 15 March 2010 15:56:08 Vaughan Johnson wrote:
>>>        
>>>> On 3/14/2010 11:55 PM, Al Dimond wrote:
>>>>          
>>>>> On Sunday 14 March 2010 23:55:13 Simon Peter Muwanga wrote:
>>>>>            
>>>>>> Hi,
>>>>>>
>>>>>> my audacity checkout from
>>>>>> http://audacity.googlecode.com/svn/audacity-src/trunk/
>>>>>> is not building successfully. I get the following on the
>>>>>>     error-list. Am using wxWidget 2.8.10 . I tried out this
>>>>>> link( http://forums.adobe.com/thread/497546?tstart=1 ) for
>>>>>> help, but the errors are still there. Thats, the files cannot
>>>>>> be opened, yet I can see them in the $WXWIN\lib\vc_lib\ .
>>>>>> I added $WXWIN\lib\vc_lib\  to (Configuration-->Linker-->
>>>>>> Input and
>>>>>> Additional Dependencies) and
>>>>>> had to add the path (<wxWidgetsHome>\lib\vc_lib\) to the file
>>>>>> in the includes in the the project properties
>>>>>>     (Configuration-->C/C++--
>>>>>>              
>>>>> I don't think I've ever had to add anything to project
>>>>> dependencies to get Audacity to build. Instead I added
>>>>> $WXWIN\lib\vc_lib to the PATH environment variable.
>>>>>            
>>>> Really?! Totally unnecessary. I don't even have a
>>>> $WXWIN\lib\vc_lib on my system because I didn't bother to build
>>>> static libraries that we don't use.
>>>>          
>>> Whoa, I misread his post. I was thinking of $WXWIN\lib\vc_dll.
>>>        
>> That's good. But you still shouldn't need to put it in your path,
>>   unless you're not doing the copy into local dirs where the exes
>>   are built. Copying them is a better idea if you're building
>>   installers because the installer scripts look for the wxWindows
>>   dll's in the build dirs, e.g., "audacity\win\Unicode Release", not
>>   in the $WXWIN\lib\vc_dll.
>>
>>      
> I copy into local directories when it's appropriate. But for most of
> my dev work it's more convenient to just put it in PATH. I've had to
> mess with wxWidgets from time to time, and this saves me from doing a
> manual copy of a bunch of files with weird names that are hard to pick
> out from each other every time I rebuild wxWidgets, change versions
> (I've tested things against 2.8-trunk and a couple 2.8.11 RCs), or
> nuke my Audacity tree.
>    
You know what's going on.


>    
>>>> Have you changed your copy of Audacity to link statically to
>>>>    wxWindows? We agreed not to change  back to static linking at
>>>> this time.
>>>>          
>>> Nah, still linking dynamically. Sorry for the panic.
>>>        
>> My hair was on fire. (Well, maybe not.) :-)
>>
>>      
> I once saw a guy light his hair on fire shooting off fireworks in his
> backyard. Didn't look very pleasant.
>
>    
Yikes! Surely not.

- V