The reason, at least as far as I understand it, is that the libpurple build is incredibly cumbersome. It requires a multitude of source tarball downloads (plus yet another DVCS tool fir pidgin's repository) and a significant amount of compile time.
It is possible to accomplish this with a script in a build step, but keeping the binaries up to date when the source updates (Xcode will not track source file mod times for this) and the amount of time it takes to compile libpurple+dependencies are the key drawbacks, in my recollection. We know its ugly, and id love to see this situation improve. But for now, versioned binaries of libpurple+dependencies seems the most pragmatic path for us. -- Steve Holt Sent from my iPhone On Dec 23, 2010, at 8:50 PM, Ryan Govostes <r...@adium.im> wrote: > I note that /Frameworks is full of binaries. Why is this so? > > http://hg.adium.im/adium/file/5b2e819a13f8/Frameworks > > -- Ryan >
