[Adium-devl] Libpurple Build Dependencies

[Evan Schoenberg]

Quoting Augie Fackler <lists at durin42.com>:

> We should be able to do this all using the native build system for
> each target and some clever linker options.
Excellent :)

> Should I make my goal a
> universal gstreamer binary and just do deps for that first? Or do you
> have libs that Libpurple.framework uses I should do first?
It sounds like Eric's trying to convince the new glib to compile...  
that's probably a dependency both for gstreamer and for libpurple.  So  
glib will happen either way :)

Let's start with going for the universal gstream binary along with its  
deps, since that's what doesn't work at all at present; we can  
transition working-but-hacky dependencies to working-and-elegant style  
after that (unless the hackery interferes with the rest, in which case  
you might have to fix it all at once).  Sound good?


>> The current process utilizes a static config.h for each dependency,
>> made using that library's configure script followed by manual changes
>> to allow for big/small endian appropriateness and other ppc vs. intel
>> #define differences.  An XCode target then includes each file to be
>> built into the library.  Static libraries are produced and linked
>> against as needed.
>
> aaand a kitten dies because of how nasty that is. Static config.h's
> for the lose. Ideally, upstream rearrangements of code shouldn't
> require project changes on our end.
Double true. (I described the current process not as a model of  
goodness but in order to make obvious how much of a kludge it is.)

-Evan

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.