[Top][All Lists]

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

Re: cl.exe and system types

From: Keith Marshall
Subject: Re: cl.exe and system types
Date: Thu, 23 Aug 2018 20:00:40 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0

On 23/08/18 18:08, Earnie wrote:
> If you're using MSVC, there is no crosstool chain of software so you
> specify a fictitious --host and --build to be the same such as
> {i686,x86_64}-pc-msvc and point the environment variables to the
> binaries.

But the OP seems to want to use AC_CANONICAL_*.  IIRC, these demand that
the --build and --host, (and --target, if applicable), must be known to
config.sub; that kind of precludes just inventing an arbitrary name.

For --build, the output from config.guess should always be suitable; for
--host, it may be okay to affix an arbitrary suffix to mingw32, such as
(untested [*]) --host=mingw32cl CC=cl.exe, (and any other explicit tool
identification assignments which may be required).

You could possibly also use AS_IF, or AS_CASE, in or a user
written macro included by, to test $host_alias for your
specific modified host identifier, and make a conditional assignment of
CC=cl.exe and so on, within the generated configure script itself.

[*] Note that I've explicitly avoided "mingw32msvc" as a host identifier
in this example, because some GNU/Linux distributors have adopted that,
(inappropriately, IMO), to designate their mingw32 cross-compiler tool


Public key available from
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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