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 configure.ac or a user
written macro included by configure.ac, 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
chains.
--
Regards,
Keith.
Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
