From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wi0-x233.google.com ([2a00:1450:400c:c05::233]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1Xyju2-0006xW-1j for ptxdist@pengutronix.de; Wed, 10 Dec 2014 17:14:14 +0100 Received: by mail-wi0-f179.google.com with SMTP id ex7so5725821wid.0 for ; Wed, 10 Dec 2014 08:14:08 -0800 (PST) MIME-Version: 1.0 Date: Wed, 10 Dec 2014 17:14:06 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: [ptxdist] Hardcoded path in pkg-config file Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" Hello all, I am trying to port a package to ptxdist (libzip). This package creates a pkg-config .pc file that contains some hardcoded paths. During the install stage, it looks like ptxdist already does some magic to "fix" the hardcoded paths (where is this done?), however not all paths are fixed. Here's the .pc file that gets copied to sysroot-target: prefix=${pcfiledir}/../.. exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include libincludedir=/usr/lib/libzip/include ^^^^^^^^^^^ [...] Can someone help? Thank you, Guillermo Rodriguez Garcia guille.rodriguez@gmail.com -- ptxdist mailing list ptxdist@pengutronix.de