All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix SDL configuration for mingw32 cross compilation.
Date: Tue, 16 Jun 2009 16:28:30 +0100	[thread overview]
Message-ID: <20090616152830.GJ29040@shareable.org> (raw)
In-Reply-To: <4A35AFD2.5060909@us.ibm.com>

Anthony Liguori wrote:
> Stefan Weil wrote:
> >Anthony Liguori schrieb:
> >  
> >>Stefan Weil wrote:
> >>    
> >>>When building QEMU for win32 on linux with mingw32,
> >>>configure must call ${cross_prefix}-sdl-config (not
> >>>sdl-config) to get the correct include and lib paths.
> >>>
> >>>The results of the native sdl-config are only valid
> >>>for native builds. They are useless for cross builds.
> >>>  
> >>>      
> >>No, when you cross compile sdl, you still end up with an sdl-config
> >>binary.  The solution is to install the binary to a different path and
> >>use PATH when building.
> >>
> >>Where did you get your cross build of SDL from?  I assume whoever
> >>packaged it renamed the binary but it's not what sdl actually does.
> >>
> >>    
> >
> >The PATH solution works (I used it, too), but it is bad:
> >you have to use a modified PATH for every cross build
> >(make calls configure when the configure script is updated).
> >  
> 
> Yes, this annoys me too.  One thing I thought about is that we could 
> record important environment variables for use when re-running make.
> It's not just PATH.  PKG_CONFIG_PATH is also important for running 
> configure.  To properly cross compile, you need to set both.

You can record PATH and other environment variables picked up at
configure time in the Makefile itself.  Makefile.in:

   export PATH = @PATH@

It's not pretty, but it works.

-- Jamie

  reply	other threads:[~2009-06-16 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  8:01 [Qemu-devel] [PATCH] Fix SDL configuration for mingw32 cross compilation Stefan Weil
2009-06-13 22:24 ` Anthony Liguori
2009-06-14 14:00   ` Stefan Weil
2009-06-15  2:20     ` Anthony Liguori
2009-06-16 15:28       ` Jamie Lokier [this message]
2009-06-16 16:31         ` Stefan Weil
2009-06-16 18:14           ` Jamie Lokier
2009-06-17 10:27             ` Daniel P. Berrange

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=20090616152830.GJ29040@shareable.org \
    --to=jamie@shareable.org \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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.