Building Libpurple Statically

[Evan Schoenberg, M.D.]

On Jul 1, 2009, at 11:00 PM, Nicholas Peshek wrote:

> I'm assuming he's making an iPhone app.

If that's true, I'd check out the source for ApolloIM, if it's  
available; it was a legitimately OSS iPhone libpurple-based IM client  
in the pre-SDK days.  Dunno if it's still around as such, though.

-Evan

>
> On Jul 1, 2009, at 9:14 PM, "Evan Schoenberg, M.D." <evan at adium.im>  
> wrote:
>
>>
>> On Jul 1, 2009, at 8:52 PM, Kevin Hughes wrote:
>>
>>> I am trying to build libpurple statically for use in a programming  
>>> project of mine, and have run into some complications.  I know  
>>> Adium used to build libpurple statically, but moved away from that  
>>> to building dynamically.  What was the reason for this change?   
>>> What sort of issues were you having with building statically?
>>>
>>> I only need the yahoo protocol and the ssl plugins for my project;  
>>> would this simplify the issues you had?
>>
>> We built statically by creating an xcode project with all the files  
>> needed, along with all the dependencies as targets linked  
>> statically.  The config.h file for each target was generated once,  
>> copied in, and then modified to have appropriate platform-specific  
>> #ifdef sections (PPC vs. Intel).
>>
>> We moved away from this because while it worked fine once it  
>> worked, it fell like a house of wet cards when trying to upgrade  
>> any dependency or libpurple itself, as libraries expect their  
>> autoconfigure to work, and we were literally short-circuiting it.
>>
>> There might be a better way than building statically - what are you  
>> trying to accomplish?
>>
>> Cheers,
>> Evan
>>
>