Re: pkg-config

On Tue, Apr 29, 2003 at 12:03:31PM +0300, Tor Lillqvist wrote:
> Richard Atterer wrote
> > A nicer solution would be to allow relative paths in .pc files (relative to
> > the directory which contains the .pc file), then just setting
> > PKG_CONFIG_PATH would be enough.
> 
> In my opinion, it's not necessarily that useful to make pkg-config
> support end-user-choosable installation location on Unix, as the
> libraries that said .pc files describe aren't freely locatable
> anyway. On Unix, for instance both the GTK and Pango libraries
> (regardless whether built shared or static) contain hardcoded paths to
> the installation path decided at configure time. (Used to look up
> dynamically loaded modules, rc files, message catalogs.)

As said, after having installed the gtkwin32 stuff into
/home/luther/download/gtkwin32, i was able to cross build, and also run
under wine, the hello-gtk program :

$ export PKG_CONFIG_PATH=/home/luther/download/gtkwin32/lib/pkgconfig
$ i586-mingw32msvc-gcc -mno-cygwin -mms-bitfields -o lib/hello-gtk `pkg-config --define-variable=prefix=/home/luther/download/gtkwin32 --cflags gtk+-2.0` hello-gtk.c `pkg-config --define-variable=prefix=/home/luther/download/gtkwin32 --libs gtk+-2.0`

With the stock debian/sid pkg-config 0.15.0-2.

Friendly,

Sven Luther