qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Stuart yoder <stuart.yoder@freescale.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] remove cross prefix from pkg-config command
Date: Tue, 02 Aug 2011 23:01:16 +0200	[thread overview]
Message-ID: <4E38659C.7080008@mail.berlios.de> (raw)
In-Reply-To: <1312316473-22591-1-git-send-email-stuart.yoder@freescale.com>

Am 02.08.2011 22:21, schrieb Stuart yoder:
> From: Stuart Yoder <stuart.yoder@freescale.com>
>
> the host pkg-config tool should be used with the location to
> pkg-config *.pc files being specified via the PKG_CONFIG_PATH
>
> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
> ---
>
> The Freescale cross build environment is multilib which
> means there are special library paths for different
> cpu types. pkg-config installed along with the
> other cross tools does not work...it has no clue how
> to find the right libraries. So using cross-prefix
> does no good. Only thing I can get to work is
> explicitly setting PKG_CONFIG_PATH before running
> configure.
>
> Not sure how other cross build envionments work, but
> it seems like the above method should be sufficiently
> general.
>
> configure | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)

I run cross builds for arm, mips, powerpc and mingw.
All of them use the cross prefix. When running make,
I neither want to specify a special PATH nor a
PKG_CONFIG_PATH. All I need is something like
"make -C bin/arm" (each cross target has its own
directory with the binaries).

The general idea of your patch is ok, but maybe you
can modify it so the cross prefix is used if there
is no PKG_CONFIG_PATH set?

Regards,
Stefan Weil

  reply	other threads:[~2011-08-02 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 20:21 [Qemu-devel] [PATCH] remove cross prefix from pkg-config command Stuart yoder
2011-08-02 21:01 ` Stefan Weil [this message]
2011-08-03  6:41   ` Paolo Bonzini
2011-08-03 14:03     ` Yoder Stuart-B08248

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=4E38659C.7080008@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stuart.yoder@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).