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.