Hi Michael,

2014-12-12 11:22 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> Hi,
>
> On Thu, Dec 11, 2014 at 12:12:40PM +0100, Guillermo Rodriguez Garcia wrote:
>> 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:
>
> Yes, some packages have (generated) headers that are platform specific.
> Those are installed separately to handle multiarch correctly.
>
>> ===
>> prefix=@prefix@
>> exec_prefix=@exec_prefix@
>> libdir=@libdir@
>> includedir=@includedir@
>> libincludedir=@libdir@/@PACKAGE@/include
>
> Patch this to change this to:
>
> libincludedir=${libdir}/@PACKAGE@/include

Yes, thank you. At the end I followed a similar approach. But instead
of patching the sources, I am patching the generated .pc file in the
install.pack stage. I'll be submitting a patch for this in minutes, so
you can hopefully have a look and let me know if this is OK.

Thanks,

Guillermo