[Adium-devl] Protocol plugins

[Evan Schoenberg]

There's a 'current' symlink which should be used rather than the  
versioned folder.

Cheers,
Evan

On Dec 31, 2007, at 4:39 PM, "Eion Robb" <eion at robbmob.com> wrote:

> Hi again,
>
> Yeah, I know I described it badly.  XCode isn't really my native  
> IDE :)
>
>> Frankly, I don't see a solution as being worth working towards.
>> Support 1.2+.  There's no reason for anyone to continue using 1.1.x.
> This is the problem though.  For every version of Adium 1.2 that comes
> out, if it has a different version of libpurple in it, then the plugin
> needs to be recompiled for that version, since it has a new version
> foldername that XCode is wanting to link to.
>
> I'll look at that "weak linking" you were talking about, see if I  
> can make
> XCode do it.
>
>> The packaging and construction of libpurple.framework has changed
>> between 1.1.x and 1.2.x and beyond. You may want to examine the
>> changes between 1.1.x and 1.2.x because you may have been depending  
>> on
>> the packaging and location of the framework when your originally  
>> setup
>> your project.
> That's the thing, I'm telling XCode to look in both places for  
> loading the
> frameworks.  I'm starting to think that maybe this is a compile-time  
> only
> thing, and isn't flexible to when the plugin gets loaded.
>
> Cheers,
> --Eion
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>