From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Borleis Date: Thu, 11 Dec 2014 11:46:47 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201412111146.47136.jbe@pengutronix.de> Subject: Re: [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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Guillermo Rodriguez Garcia Hi Guillermo, On Wednesday 10 December 2014 17:14:06 Guillermo Rodriguez Garcia wrote: > 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=3D${pcfiledir}/../.. > exec_prefix=3D${prefix} > libdir=3D${exec_prefix}/lib > includedir=3D${prefix}/include > libincludedir=3D/usr/lib/libzip/include > ^^^^^^^^^^^ > [...] What is the difference between 'includedir' and 'libincludedir'? What kind of files does the install stage install to these locations? Regards, Juergen -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 | Industrial Linux Solutions =A0 =A0 =A0| http://www.pengutroni= x.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de