From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: MinGW cross-compilation support
Date: Wed, 07 Dec 2016 10:36:22 +0100
Message-ID: <87wpfc9j3d.fsf_-_@gnu.org>
References: <20160818060851.2853-1-janneke@gnu.org>
	<20160818060851.2853-11-janneke@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54122)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cEYeW-0006r4-10
	for guix-devel@gnu.org; Wed, 07 Dec 2016 04:36:40 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cEYeV-0002zu-6k
	for guix-devel@gnu.org; Wed, 07 Dec 2016 04:36:40 -0500
In-Reply-To: <20160818060851.2853-11-janneke@gnu.org> (Jan Nieuwenhuizen's
	message of "Thu, 18 Aug 2016 08:08:49 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org

Hello Guix!

After all this time I=E2=80=99m happy to report that I=E2=80=99ve finally m=
erged MinGW
cross-compilation support, woohoo!

So we should now be able to do:

  guix build --target=3Di686-w64-mingw32 guile

to cross-compile Guile to MinGW.

Hydra will build the cross-compilation toolchain and some example
packages.

I didn=E2=80=99t merge the cross-libtool patch and this one:

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> * gnu/packages/ncurses.scm (ncurses)[MINGW]: Build with libtool, as
> recommended; enables dlopen'ing.

I=E2=80=99m not sure what this means (and the explanation should be as a co=
mment
in the code).  Could you explain a bit more?

The idea of Libtool is normally to bundle it in the package tarball.
That ncurses can optionally take an externally-provided Libtool is weird
and I=E2=80=99d rather avoid relying on that if possible.


Adding a new cross-compilation target is a commitment.  So I hope you
and others will make sure it remains functional and useful!

I also think that together with Manolis and everyone else who=E2=80=99s pla=
yed
with cross-compilation, we must clean up the mess that this has become.
;-)  Namely, we must more clearly separate target-specific things and
also separate build-side from host-side code (in cross-base.scm).

Suggestions and hacks welcome!

Thanks,
Ludo=E2=80=99.