Re: [Audacity-devel] Recent LV2 updates

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

Leland wrote:
> Lars Luthman wrote:
>   
>> Another way could be to leave it as it is, compile it using the MinGW
>> version of GCC, put the compiled library in CVS and just link it into
>> Audacity in the normal build process. If there are no difficulties
>> linking that probably is the method that requires the least work.
>>
>>     
> I've been playing around with this for the last hour or so and have 
> found that MinGW may very well be the way to go.
>
> Building SLV2 as C++ gets past a lot of the errors from before, but 
> there's a lot of typing issues with return values and argument passing 
> that VC++ doesn't like.
>
> And I just ran into the whole file handling issue...it's very Unix 
> specific...no accounting for backslashes, colons...uses functions like 
> opendir/readdir...
>
> Sure, all of that is fixable and I started to do it, but it was just 
> getting out of hand and I seriously doubt if the author would accept the 
> changes.  Mind you, if someone want so ask him and he says yes, I will 
> continue and make it as clean as possible.
>
>   

Since it's GPL, we could keep a lib-src version even if he doesn't want 
the changes... If it's worth the effort.

- V