Re: [Gtk-osx-devs] pkg-config and _exec_prefix

[John Ralls <jralls ceridwen fremont ca us>]

On Jan 17, 2011, at 11:55 PM, Anders F Björklund wrote:

> John Ralls wrote:
> 
>>> I *am* building pkg-config as part of gtk-osx, but it is in
>>> _exec_prefix (~/Source/bootstrap) and not prefix (/opt/gtk)
> 
>>> I thought the setup of pkg-config should go next to the
>>> other setup, just to make sure that it finds it alright ?
> 
>> That would be because you've created a separate exec_prefix in your .jhbuild-custom, so it's your job to adjust the path the same way.
>> 
>> I don't have any problem with you doing things your way, but I'm not going to change things for everybody else to suit you.
> 
> Maybe I was just reading too much into the config comments...
> 
> # In addition, you can override _exec_prefix (used to set $M4 and
> # $LIBTOOLIZE); by default it's set to prefix. You might want to reset
> # it if you want to bootstrap to one directory and build in another
> # (or more likely, several others). Similarly, you can override
> # tarballdir so that you need download tarballs only once for multiple
> # builds.
> # _exec_prefix = os.path.join(os.path.expanduser("~"), "Source", "bootstrap")
> # tarballdir = os.path.join(os.path.expanduser("~"), "Source", "Download")
> 
> I thought it was a supported configuration, guess I was wrong ?
> Easy enough to put those two lines in .jhbuildrc-custom instead.
> 
> It seemed to apply, since I was doing two builds for Universal...
> 
>> Oh, I forgot to ask: What's the Gtk bug number? 
> 
> It is now https://bugzilla.gnome.org/show_bug.cgi?id=639820
> 
> Another minor problem is when using a SDK, since there are no
> PC files in the /Developer/SDKs (and none at all for 10.4u.sdk)
> 
> But that's a completely different story, only affecting system. :-)

Yes, I think that you read too much into it, or maybe I didn't write enough into it, since I didn't include a line adding _exec_prefix to the path.

Bug 639820: I see that Mattias has applied your patch to master, so I'll add it as a backport to gtk-osx.

Setup_sdk() sets the compile flags for you. No pkgconfig files needed. For Apple's frameworks, just do it their way (#include <Cocoa/Cocoa.h> in the source file and -framework Cocoa in the CFLAGS and LDFLAGS) and there's no need for pkgconfig.

Regards,
John Ralls


------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Gtk-osx-devs mailing list
Gtk-osx-devs lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtk-osx-devs