qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Stefan Weil <sw@weilnetz.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Thu, 13 Dec 2012 13:32:43 -0600	[thread overview]
Message-ID: <1355427163.14046.7@snotra> (raw)
In-Reply-To: <1355426208.14046.6@snotra> (from scottwood@freescale.com on Thu Dec 13 13:16:48 2012)

On 12/13/2012 01:16:48 PM, Scott Wood wrote:
> On 12/13/2012 12:58:19 PM, Stefan Weil wrote:
>> A cross prefix which starts with an absolute path (like in your  
>> scenario) justs
>> requires adding `dirname "${cross_prefix}"` to PATH and passing
>> `basename "${cross_prefix%-}" to the pixman configure.
> 
> Right...  I'm not thrilled at the idea of build scripts messing with  
> $PATH -- normally I deal with autoconf builds by explicitly passing  
> in CC and such (and am much happier when I encounter a project such  
> as QEMU-until-recently that is fine with just a cross prefix rather  
> than a host tuple) -- but the alternative is making the QEMU build  
> scripts aware of every build tool than pixman requires.
> 
> What I don't want to do is put it in $PATH semi-permanently, in the  
> interactive instance of the shell.
> 
>> These modifications could be added to QEMU's configure and Makefile
>> if we really want that. Installing pixman once manually also works
>> and saves compilation time for repeated builds. That's why I no  
>> longer
>> use internal pixman for any of my cross compilations.
> 
> Yes, I could manually install it, though then I get to deal with  
> telling the pixman build exactly where to install itself, and  
> repeating the process for each toolchain and multilib-variant thereof.

BTW, I use QEMU's --extra-cflags and --extra-ldflags options for  
choosing the multilib variant I'm targeting.  It looks like something  
would need to be added to get those passed into pixman's build as well.

-Scott

  reply	other threads:[~2012-12-13 19:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  3:18 [Qemu-devel] [RFC PATCH] Allow building without graphics support Scott Wood
2012-12-12  6:46 ` Stefan Weil
2012-12-13  0:48   ` Scott Wood
2012-12-13  6:31     ` Stefan Weil
2012-12-13 15:53       ` Scott Wood
2012-12-13 18:58         ` Stefan Weil
2012-12-13 19:16           ` Scott Wood
2012-12-13 19:32             ` Scott Wood [this message]
2012-12-14  8:13             ` Gerd Hoffmann
2012-12-14 18:51               ` Scott Wood
2012-12-19  9:02                 ` Gerd Hoffmann
2012-12-19 18:47                   ` Scott Wood
2012-12-14  8:07         ` Gerd Hoffmann
2012-12-14 18:48           ` Scott Wood
2012-12-19  9:13             ` Gerd Hoffmann
2012-12-19 18:57               ` Scott Wood
2012-12-20  6:59                 ` Gerd Hoffmann
2012-12-20 16:19                   ` Scott Wood
2012-12-21  8:56                     ` Gerd Hoffmann
2012-12-21 10:56                       ` Robert Schiele
2012-12-21 19:01                         ` Scott Wood
2012-12-12  7:52 ` Gerd Hoffmann
2012-12-13  0:57   ` Scott Wood
2012-12-13  7:16     ` Gerd Hoffmann
2012-12-13 14:44       ` Alexander Graf
2012-12-13 15:10         ` Peter Maydell
2012-12-13 15:16         ` Gerd Hoffmann
2012-12-13 15:30           ` Alexander Graf
2012-12-13 15:57           ` Scott Wood
2012-12-12 16:28 ` John Spencer
2012-12-12 16:54   ` Andreas Färber
2012-12-13  0:53     ` Scott Wood
2012-12-12 16:47 ` Peter Maydell
2012-12-12 17:09   ` Andreas Färber
2012-12-12 17:37     ` Peter Maydell
2012-12-12 17:42     ` Paolo Bonzini
2012-12-13  0:51   ` Scott Wood

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=1355427163.14046.7@snotra \
    --to=scottwood@freescale.com \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).