DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=SQSe
	MabBSobHkHCtdxacdTwRIcxniC/Wcm8DSitCtx4kXmdN1ctqardvK/urT3c72vPU
	3xnG2WiA/sW+f+hPgsVRnFZ06pCNYBDd8cwxBLTBvAS+AsfKp16SL9etTmB1uKCr
	0gp9Q9pXOn/I1NU0PokXPtBqLV1POogFlLkcjz8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 25EF0C050907
Subject: Re: How to use CMake with cygwin/mingw toolchain?
To: cygwin@cygwin.com
References: <CA+3dX1xvZZLXy9ax5MHeu80N6V8SCORx6wcJGMoUkAvy5pKAkg@mail.gmail.com>
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
Message-ID: <aaae0288-a012-f49b-dcbb-2b1952622ed5@cygwin.com>
Date: Fri, 20 Oct 2017 16:11:03 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CA+3dX1xvZZLXy9ax5MHeu80N6V8SCORx6wcJGMoUkAvy5pKAkg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AnONDva0b0sdM903vJ4BAbPQrgQ5R19HV"

--AnONDva0b0sdM903vJ4BAbPQrgQ5R19HV
Content-Type: multipart/mixed; boundary="JKwLbMiQFklTedOTaUdTfqhi4AJ5eoDhn";
 protected-headers="v1"
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Message-ID: <aaae0288-a012-f49b-dcbb-2b1952622ed5@cygwin.com>
Subject: Re: How to use CMake with cygwin/mingw toolchain?
References: <CA+3dX1xvZZLXy9ax5MHeu80N6V8SCORx6wcJGMoUkAvy5pKAkg@mail.gmail.com>
In-Reply-To: <CA+3dX1xvZZLXy9ax5MHeu80N6V8SCORx6wcJGMoUkAvy5pKAkg@mail.gmail.com>


--JKwLbMiQFklTedOTaUdTfqhi4AJ5eoDhn
Content-Type: text/plain; charset=utf-8
Content-Language: en-CA
Content-Transfer-Encoding: quoted-printable

On 2017-10-20 07:50, Peter Quiring wrote:
> What is the current process to use the mingw toolchain that is
> included with cygwin?

Treat it like any other cross-compiling scenario.

> There use to be a -mno-cygwin option used with gcc.

That was an ugly hack which never really worked correctly and which we
happily rid ourselves years ago.

> The mingw versions have x86_64-w64-mingw32- or i686-w64-mingw32- added
> to their exe names. Currently I just use these directly but I want to
> use cmake.
>=20
> Cygwin also includes cmake. How would I configure it to use the mingw
> toolset that is included with cygwin?

You need to provide a number of options, see:

https://github.com/cygwinports/cygport/blob/master/cygclass/cmake.cygclass#=
L137

> I also see some Qt5 *.cmake modules included in the Qt5 libraries for min=
gw.

Those, like all my packages, are built with cygport.

> Would it be possible to include a version of cmake built for mingw?

No, but you can create a CMake toolchain file with all the options so
that you don't have to specify them each time:

https://cmake.org/Wiki/CMake_Cross_Compiling

--=20
Yaakov


--JKwLbMiQFklTedOTaUdTfqhi4AJ5eoDhn--

--AnONDva0b0sdM903vJ4BAbPQrgQ5R19HV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHQEARECADQWIQRFYAu5jKh4qpenARn/IK+aZu4flAUCWepmZxYceXNlbGtvd2l0
ekBjeWd3aW4uY29tAAoJEP8gr5pm7h+URBMAmweYcqrP65TFgs4boTxmFRrExPkh
AKCFAfmiXElQzqKhnEiJpCv3kAD87Q==
=T+50
-----END PGP SIGNATURE-----

--AnONDva0b0sdM903vJ4BAbPQrgQ5R19HV--