All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files
Date: Mon, 04 Feb 2013 23:51:50 +0100	[thread overview]
Message-ID: <87sj5b1ym1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1359550000-10585-1-git-send-email-stefan.froberg@petroprogram.com> ("Stefan Fröberg"'s message of "Wed, 30 Jan 2013 14:46:40 +0200")

>>>>> "Stefan" == Stefan Fr?berg <stefan.froberg@petroprogram.com> writes:

 Stefan> This patch will add <pkg>_CONFIG_FIXUP variable to buildroot infra.
 Stefan> It's purpose is to inform buildroot that the package in question
 Stefan> contains some $(STAGING_DIR)/usr/bin/*-config files and that we
 Stefan> want to automatically fix prefixes of such files.

 Stefan> It is often the case that many packages call these
 Stefan> files during their configuration step to determine 3rd party
 Stefan> library package locations and any flags needed to link against them.

 Stefan> For example:
 Stefan> Some package might try to check the existense and linking flags
 Stefan> of NSPR package by calling $(STAGING_DIR)/usr/bin/nspr-config --prefix.
 Stefan> Without this fix. NSPR would return /usr/ as it's prefix which is
 Stefan> wrong when cross-compiling.
 Stefan> Correct would be $(STAGING_DIR)/usr.

 Stefan> All packages that have <pkg>_INSTALL_STAGING = YES defined and
 Stefan> also install some config file(s) into $(STAGING_DIR)/usr/bin must
 Stefan> hereafter also define <pkg>_CONFIG_FIXUP with the correspondig
 Stefan> filename(s).

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-02-04 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 12:46 [Buildroot] [PATCH v4] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files Stefan Fröberg
2013-02-04 22:51 ` Peter Korsgaard [this message]
2013-02-05 10:28   ` Stefan Fröberg

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=87sj5b1ym1.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.