atom feed3 messages in org.freebsd.freebsd-portsRe: How to force port respecting PKGC...
FromSent OnAttachments
O. HartmannNov 18, 2010 5:29 am 
Greg LarkinNov 18, 2010 5:51 am 
Christian WeisgerberNov 18, 2010 6:37 am 
Subject:Re: How to force port respecting PKGCONFIGDIR?
From:Greg Larkin (glar@FreeBSD.org)
Date:Nov 18, 2010 5:51:30 am
List:org.freebsd.freebsd-ports

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

O. Hartmann wrote:

Hello. As I realized while trying to port xerces-c version 3.1.1 in an test environment as suggested in the porters handbook, the software, which is capable of using the GNU autotoll environment, installs its xerces-c.pc file into ${PREFIX}/lib/pkgconfig/ and not according the FreeBSD paradigm into ${PREFIX}/libdata/pkgconfig/. I see three ports having already installed their obviously mislead *.pc file into ${PREFIX}/lib/pkgconfig/ in real-world-installations (libvlc.pc, lapackpp.pc and vlc-plugin.pc) on all of my FreeBSD boxes where these packages are installed - every other package using pkg-config seems to have their config files installed at the proper place and therefor ${PREFIX}/libdata/pkgconfig/ is well populated.

The question is: how can I trim my port's Makefile to accept and respect FreeBSD's path? I tried to figure out what directive has to be set and passed to any kind of environemnt, but the handbook silence this out. I have a faint clue that all directives tagged *_PC_* has to do something with this, but in ports I examined which install their pkg-config files in the proper way I did not find any hint.

Please set me CC if responding due to I'm not subscriber of the list.

Thanks.

Hi Oliver,

Have a look at this patch file for an example of how to do that:

http://www.freebsd.org/cgi/cvsweb.cgi/ports/graphics/GraphicsMagick13/files/patch-Makefile.in?rev=1.7;content-type=text%2Fplain

Hope that helps, Greg - -- Greg Larkin

http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFM5S950sRouByUApARAljzAJ9CCNOc5RF0abkE673mkcZ+uXHuogCfYoU5 XiKFBhwCDLd/NorLv/bvUM0= =w5OP -----END PGP SIGNATURE-----