From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: make wrapper relocatable
Date: Wed, 9 Mar 2016 10:51:52 -0300 [thread overview]
Message-ID: <56E02A78.1050701@zacarias.com.ar> (raw)
In-Reply-To: <87egbj228a.fsf@dell.be.48ers.dk>
On 09/03/16 10:46, Peter Korsgaard wrote:
>>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
>
> > Use shell ${STAGING_DIR} to expand at run time instead of build time
> > hence avoiding hardcoding the staging directory in it and making it
> > relocatable.
>
> > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
>
> Ehh, doesn't this break using pkg-config outside buildroot?
Hi.
Indeed it does, but you can't have the cake and eat it at once can you?
Arnout in the famous vala-wrapper thread pointed that we shouldn't
hardcode the staging directory in it and i've adjusted accordingly, so
which way is it? (same logic would apply to both cases). Re:
http://lists.busybox.net/pipermail/buildroot/2016-February/153671.html
Regards.
next prev parent reply other threads:[~2016-03-09 13:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 13:16 [Buildroot] [PATCH] pkgconf: make wrapper relocatable Gustavo Zacarias
2016-03-09 13:46 ` Peter Korsgaard
2016-03-09 13:51 ` Gustavo Zacarias [this message]
2016-03-09 14:00 ` Peter Korsgaard
2016-03-09 14:04 ` Gustavo Zacarias
2016-03-09 14:31 ` Peter Korsgaard
2016-03-09 14:37 ` Arnout Vandecappelle
2016-03-09 14:40 ` Gustavo Zacarias
2016-03-09 14:46 ` Peter Korsgaard
2016-03-09 14:52 ` Arnout Vandecappelle
2016-03-09 15:06 ` Peter Korsgaard
2016-03-09 14:03 ` Thomas Petazzoni
2016-03-09 14:28 ` Gustavo Zacarias
2016-03-09 14:40 ` Arnout Vandecappelle
2016-03-09 14:41 ` Gustavo Zacarias
2016-03-09 14:42 ` Arnout Vandecappelle
2016-03-09 14:30 ` Peter Korsgaard
2016-03-09 14:50 ` Thomas Petazzoni
2016-03-09 14:55 ` Peter Korsgaard
2016-03-09 15:22 ` Samuel Martin
2016-03-09 15:55 ` Peter Korsgaard
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=56E02A78.1050701@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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