Building Libpurple Statically

[Evan Schoenberg, M.D.]

Kevin,

On Jul 2, 2009, at 8:25 AM, Kevin Hughes wrote:

> Could you explain in more detail how you linked statically?

An xcode project was created, with a static library target for  
libpurple and one for each dependent library. All the .c and .h files  
were dragged in, associated with the appropriate targets. A config.h  
file was made by running ./configure and then modifying it to fit both  
architectures, for each target.  libpurple then had the libraries as  
dependencies and linked against them.

It was honestly a giant mess, though it worked.

> Or is there a way to check out old versions of adium and see the  
> libpurple build process?  Unless libpurple has always been released  
> precompiled with the Adium source...
>

libpurple has always been precompiled within the Adium source itself,  
but we used to have a separate subversion repository, 'libpurple',  
which housed the whole build process. svnserve is not currently  
running on our server, and I'm sure if it the repository's files even  
still exist, unfortunately.

-Evan