[Adium-devl] libglib.framework

[Devraj Mukherjee]

Hi Elliott,

Thanks for the detailed response. Will try that out rtool. Managed to
fetch libpurple via svn and build it using the command line tools.

Also, how well does libpurple support of the Jabber protocol? The
application we are looking at developing will use Jabber to
communicate and libpurple may infact be suitable for what we are
doing.

Thanks a lot.

On Jan 2, 2008 9:15 AM, Elliott Harris <excitebike at mac.com> wrote:
> Hiya,
>
> I doubt you'll find anything specifically for Linux->OS X, but Apple does
> offer some documentation for UNIX developers here:
>
> http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/intro/chapter_1_section_1.html
>
> libglib.framework is actually generated by a tool written by Augie, one of
> our developers, with some small help from myself. It leverages rtool to
> create frameworks out of every Linux-styled dependency we need
> automatically.  The entire thing is python script that checkouts the version
> we need (from a file listing the location of the version on the web),
> untars/rars/gzips it, and uses the native build process (make, etc.) to
> create a native installation, then we use rtool to relocate that
> installation into a framework. It certainly isn't very pretty or mac-like at
> all, but the end result is wonderful. Unfortunately, not everything works
> perfectly. We've run into situations where we've had to patch things for
> them to work correctly, and even situations where we've had to get really
> hacky to get universal binaries to work correctly.
>
> If you want to know more about the process you can checkout Adium 1.2 from
> svn. Inside, you'll find the entire project, but the
> ./Utilities/dep-build-scripts/ folder would be worth looking at. You can
> then use these as a stepping point to building your own libraries. One
> tricky thing about this entire process is how dependencies work. Since we
> are rewriting the headers for the installed library, we also have to rewrite
> the location of the dependencies. In this case, that means all the
> dependencies must be turned into frameworks (frameworkized as we say) and
> referenced correctly. This should all be handled by our scripts, but it's
> important to keep in mind going forward. This means that not only do you
> need libglib, but also all of its dependencies frameworkized.
>
> As far as GPL goes, I'm pretty sure if you are GPL it's completely kosher,
> but then again I'm no license buff, and someone else can field that
> question.
>
> Good luck!
>
> Cheers,
> Elliott
>
>
>
> On Jan 1, 2008, at 4:01 PM, Devraj Mukherjee wrote:
>
>
> Hi everyone,
>
> I have been trying to port some software to OS X, they were originally
> written for Linux and depend on glib. I noticed that Adium does it in
> a really neat way and provides libglib.framework (I am assuming to end
> up using things like libpurple) and everything then compiles as a
> project in XCode.
>
> Can anyone please point me to some doco that talks about porting
> applications properly from the Linux world to OSX? Also assuming that
> our code will be released under the GPL as well are we able to use the
> libglib.framework provided by Adium?
>
> Thanks a lot.
>
> --
> "I never look back darling, it distracts from the now", Edna Mode (The
> Incredibles)
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>



-- 
"I never look back darling, it distracts from the now", Edna Mode (The
Incredibles)