From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjEWv-000128-Uf for qemu-devel@nongnu.org; Thu, 13 Dec 2012 14:33:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TjEWo-0004Ba-CO for qemu-devel@nongnu.org; Thu, 13 Dec 2012 14:33:13 -0500 Received: from ch1ehsobe002.messaging.microsoft.com ([216.32.181.182]:42495 helo=ch1outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjEWl-0004BI-2y for qemu-devel@nongnu.org; Thu, 13 Dec 2012 14:33:03 -0500 Date: Thu, 13 Dec 2012 13:32:43 -0600 From: Scott Wood In-Reply-To: <1355426208.14046.6@snotra> (from scottwood@freescale.com on Thu Dec 13 13:16:48 2012) Message-ID: <1355427163.14046.7@snotra> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Scott Wood Cc: Stefan Weil , Anthony Liguori , qemu-devel@nongnu.org, Gerd Hoffmann 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 =20 >> scenario) justs >> requires adding `dirname "${cross_prefix}"` to PATH and passing >> `basename "${cross_prefix%-}" to the pixman configure. >=20 > Right... I'm not thrilled at the idea of build scripts messing with =20 > $PATH -- normally I deal with autoconf builds by explicitly passing =20 > in CC and such (and am much happier when I encounter a project such =20 > as QEMU-until-recently that is fine with just a cross prefix rather =20 > than a host tuple) -- but the alternative is making the QEMU build =20 > scripts aware of every build tool than pixman requires. >=20 > What I don't want to do is put it in $PATH semi-permanently, in the =20 > interactive instance of the shell. >=20 >> 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 =20 >> longer >> use internal pixman for any of my cross compilations. >=20 > Yes, I could manually install it, though then I get to deal with =20 > telling the pixman build exactly where to install itself, and =20 > repeating the process for each toolchain and multilib-variant thereof. BTW, I use QEMU's --extra-cflags and --extra-ldflags options for =20 choosing the multilib variant I'm targeting. It looks like something =20 would need to be added to get those passed into pixman's build as well. -Scott=