Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] host-pkgconf: install pkg-config-native
Date: Tue, 7 Oct 2014 14:12:24 +0200	[thread overview]
Message-ID: <20141007121217.GA4028@rmm-p1267483> (raw)
In-Reply-To: <87r3ylhtfe.fsf@dell.be.48ers.dk>

Hi!

On Mon, Oct 06, 2014 at 09:47:17PM +0200, Peter Korsgaard wrote:
> >>>>> "Eric" == Eric Le Bihan <eric.le.bihan.dev@free.fr> writes:
>
>  > The package host-pkgconf now provides `pkg-config-native`, which uses the
>  > host native sysroot. It is useful for packages which compile build-time
>  > helper tools (such as Gtk+ 3.0).
>
>  > Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
>  > ---
>  >  package/pkgconf/pkg-config-native.in | 3 +++
>  >  package/pkgconf/pkgconf.mk           | 8 ++++++++
>  >  2 files changed, 11 insertions(+)
>  >  create mode 100644 package/pkgconf/pkg-config-native.in
>
>  > diff --git a/package/pkgconf/pkg-config-native.in b/package/pkgconf/pkg-config-native.in
>  > new file mode 100644
>  > index 0000000..7e25cd2
>  > --- /dev/null
>  > +++ b/package/pkgconf/pkg-config-native.in
>  > @@ -0,0 +1,3 @@
>  > +#!/bin/sh
>  > +
>  > +PKG_CONFIG_LIBDIR=@HOST_DIR@/usr/lib/pkgconfig:@HOST_DIR@/usr/share/pkgconfig @HOST_DIR@/usr/bin/pkgconf $@
>
> Why is that needed? host-pkgconf is already built with
> --prefix=$HOST_DIR/usr, so it does the right thing:
>
> strace output/host/usr/bin/pkgconf --cflags blah 2>&1 |grep blah                      ~/source/buildroot
> execve("output/host/usr/bin/pkgconf", ["output/host/usr/bin/pkgconf", "--cflags", "blah"], [/* 50 vars */]) = 0
> open("/home/peko/source/buildroot/output/host/usr/lib/pkgconfig/blah-uninstalled.pc", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/home/peko/source/buildroot/output/host/usr/lib/pkgconfig/blah.pc", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/home/peko/source/buildroot/output/host/usr/share/pkgconfig/blah-uninstalled.pc", O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/home/peko/source/buildroot/output/host/usr/share/pkgconfig/blah.pc", O_RDONLY) = -1 ENOENT (No such file or directory)

Of course! No need to re-invent the wheel! Thanks for pointing it out. I will
remove this patch and update the one for libgtk3.

Best regards,
ELB

  reply	other threads:[~2014-10-07 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 16:21 [Buildroot] [PATCH 0/3] Re-introducing libgtk3 Eric Le Bihan
2014-09-23 16:21 ` [Buildroot] [PATCH 1/3] host-pkgconf: install pkg-config-native Eric Le Bihan
2014-10-06 19:47   ` Peter Korsgaard
2014-10-07 12:12     ` Eric Le Bihan [this message]
2014-09-23 16:21 ` [Buildroot] [PATCH 2/3] hicolor-icon-theme: new package Eric Le Bihan
2014-10-05 21:22   ` Thomas Petazzoni
2014-10-07 12:25     ` Eric Le Bihan
2014-10-07 12:28       ` Thomas Petazzoni
2014-10-07 12:50         ` Mike Zick
2014-10-07 12:55         ` Eric Le Bihan
2014-10-07 13:36           ` Thomas Petazzoni
2014-09-23 16:21 ` [Buildroot] [PATCH 3/3] libgtk3: " Eric Le Bihan
2014-09-23 16:23   ` Vicente Olivert Riera
2014-09-23 16:42     ` Gustavo Zacarias

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=20141007121217.GA4028@rmm-p1267483 \
    --to=eric.le.bihan.dev@free.fr \
    --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