From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
MIME-Version: 1.0
In-Reply-To: <201412111146.47136.jbe@pengutronix.de>
References: <CABDcavbkxDmsKJnM7TcBJr3LxhrmJgAVtP1UX1TWLibg8ifc8A@mail.gmail.com>
	<201412111146.47136.jbe@pengutronix.de>
Date: Thu, 11 Dec 2014 12:12:40 +0100
Message-ID: <CABDcavYpf6NtKus+Z9-+RRpmTfVzvCk=FZ6RUa_Mx-VyGe4b6A@mail.gmail.com>
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Subject: Re: [ptxdist] Hardcoded path in pkg-config file
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: Juergen Borleis <jbe@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>

Hi Juergen,

Thank you for your answer.

2014-12-11 11:46 GMT+01:00 Juergen Borleis <jbe@pengutronix.de>:
> 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=${pcfiledir}/../..
>> exec_prefix=${prefix}
>> libdir=${exec_prefix}/lib
>> includedir=${prefix}/include
>> libincludedir=/usr/lib/libzip/include
>> ^^^^^^^^^^^
>> [...]
>
> What is the difference between 'includedir' and 'libincludedir'?
> What kind of files does the install stage install to these locations?

Apparently these are just two locations for header files. Here's the
complete .pc.in file:

===
prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@
libincludedir=@libdir@/@PACKAGE@/include

zipcmp=@prefix@/bin/zipcmp

Name: libzip
Description: library for handling zip archives
Version: @VERSION@
Libs: -L${libdir} -lzip @LIBS@
Cflags: -I${includedir} -I${libincludedir}
===

This is probably not very common (they could have just used includedir
for all paths) but as far as I can see it is valid syntax.

After some digging (the post-install processing does not seem to be
documented anywhere) I already found where ptxdist is patching these
files (ptxd_make_world_install_mangle_pc.awk), which was my original
question. Now the question is, should this awk script handle all paths
in the .pc file? Or only the "common cases" prefix / exec_prefix /
libdir / includedir?

Thank you,

Guillermo

-- 
ptxdist mailing list
ptxdist@pengutronix.de