Linking against libglib.framework

[Mike McMaster]

Thanks, Evan - you were exactly right. I've got it working now.

Mike


On Dec 6, 2009, at 12:52 PM, Evan Schoenberg, M.D. wrote:

> Mike,
> 
> Check your header and framework search path settings for your target; I believe you need to make changes so that #include <glib/glib.h> is sensical (refers to a glib framework in a location Xcode can find at compile tome). Remember that using the header for compilation and linking against the binary at link time are separate steps and can go wrong separatey.
> 
> Cheers,
> Evan
> 
> 
> 
> 
> On Dec 6, 2009, at 2:27 PM, Mike McMaster <mike at mikemcmaster.com> wrote:
> 
>> Hi all,
>> 
>> Long time Adium user, first time potential contributor. I'm attempting to make a plugin out of the patch submitted for RVP support in this support ticket: http://trac.adium.im/ticket/2993
>> 
>> The source code requires glib, and I see that Adium's Frameworks directory has libglib.framework which seems to contain the necessary headers. However, when I link to that framework in Xcode, it still doesn't see glib.h when I attempt to build the plugin.
>> 
>> Is there a trick to using this framework? I'm not a total Xcode noob - I've been doing iPhone development for the past year and a half, but this is my first foray into Mac development. I am able to build and link to (Adium, AIUtilities, FriBidi).framework successfully (I am using fernyb's plugin template). Everything builds fine there.
>> 
>> If Adium's libglib.framework is unusable for some reason, what are my options? Do I need to compile glib from source? If so, I'm not sure how to link to it in Xcode - is that pretty involved? My searches aren't turning up much, but I might not be using the right terms.
>> 
>> Thanks in advance - I appreciate any help.
>> 
>> Mike
>