[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 2/9] configure: cross-compiling without cross_prefix

From: Paolo Bonzini
Subject: Re: [PATCH v2 2/9] configure: cross-compiling without cross_prefix
Date: Tue, 20 Oct 2020 10:34:59 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1

On 20/10/20 07:15, Thomas Huth wrote:
>>>>>> +  ;;
>>>>>> +  --enable-cross-compile) cross_compile="yes"
>>>>>> +  ;;
>>>>>> +  --disable-cross-compile) cross_compile="no"
>>>>> Can't you simply use --cros-prefix="" instead?
>>>> I mean, still introduce the "cross_compile=yes" variable, just omit the new
>>>> options.
>>> That seems less intuitive for people trying to find this option. If --help
>>> lists --enable-cross-compile I can guess what that means but there's no
>>> way I could guess --cros-prefix="" unless I've been told or searched and
>>> stumbled upon it. So unless it's a big problem I like the explicit options
>>> better. Or is that a convention in other projects to use empty prefix to
>>> enable cross compile that I don't know about?
> I don't think that --cross-prefix is a "standard" option... Most other
> (GNU-tools related) projects use "--build" and "--host" instead... so I
> guess we're free to chose here. Let's see whether other people here have an
> opionion on this...

Yeah, the way GNU tools do it is that you specify --build and --host,
and --host triggers cross compilation.  I'm not sure how they'd handle
the situation where the cross prefix is empty.

For QEMU, I agree with Thomas that --cross-prefix="" is enough.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]