From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Subject: Re: [ptxdist] Hardcoded path in pkg-config file
Date: Thu, 11 Dec 2014 11:46:47 +0100 [thread overview]
Message-ID: <201412111146.47136.jbe@pengutronix.de> (raw)
In-Reply-To: <CABDcavbkxDmsKJnM7TcBJr3LxhrmJgAVtP1UX1TWLibg8ifc8A@mail.gmail.com>
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?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-12-11 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 16:14 Guillermo Rodriguez Garcia
2014-12-11 10:46 ` Juergen Borleis [this message]
2014-12-11 11:12 ` Guillermo Rodriguez Garcia
2014-12-12 10:22 ` Michael Olbrich
2014-12-12 15:48 ` Guillermo Rodriguez Garcia
2015-01-09 11:32 ` Guillermo Rodriguez Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201412111146.47136.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox