Re: PKG_CONFIG_PATH gets clobbered ?

[guenther <guenther rudersport de>]

On Wed, 2005-09-14 at 10:02 -0400, John Affleck wrote:
> So I'm trying garnome-2.12.0 on a system I've had luck building
> garnome on in the past.  It's an interesting experience, since it's a
> RH 7.1 based box that I don't have root access to.  This means I end
> up building a lot of support packages that aren't in bootstrap (Mesa,
> libpng, for example) and sticking them somewhere.
                                         ^^^^^^^^^
Huh, somewhere? ;)

What about your GARNOME main_prefix? If you do this, the pkgconfig files
should be magically available.

Besides, if you need or want to build extra dependencies, rather than
installing them from packages (which you obviously can't), you could
easily hack a simple garball [1] for any extra dep, thus kind of
ensuring a sane "somewhere" and eliminating a lot of manually
building...


> This requires that
> pkg-config can see this area, and I naively thought that just setting
> PKG_CONFIG_PATH would be sufficient.  Turns out that gar.conf.mk
> clobbers PKG_CONFIG_PATH, which means that I'm not building against
> what I thought I was..
> 
> Is there a reason to reset PKG_CONFIG_PATH, or was it just an
> oversight ?

...guenther


[1] The directory of a package with it's contents, like "evolution" in
"desktop". Simply create a new meta-garball dir like bootstrap or re-use
one of them. Create a new dir for the extra dep, hack up the Makefile
and run 'make makesum' to create the md5sums automatically. I already
posted more info about this in the past...


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}