From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: David Allsopp <dra-news@metastack.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Effect of Windows LLP64 architecture on 64 bit MingW OCaml
Date: Mon, 26 Oct 2015 08:25:00 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE33594@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E9FB63D3@Remus.metastack.local>
Dear David,
> FWIW, this might be pulling itself into my native Windows OPAM port - we're
> interested in Windows/Cygwin cross-compilers (i.e. ocamlopt being a Cygwin
> executable which outputs native Windows executables using mingw64/msvc
> and vice versa) and it makes sense to unify the build process at the same
> time as trying to do that.
I fully agree. But I think full native windows Ocaml compilers are also required. E.g. recent Coq requires an Ocaml compiler at run time and one doesn't want to require Cygwin for this. That's the reason why I started to think what it would take to get to a gcc like configure with separate build, host and target configure parameters. In the end one might want to have 3 different build variants:
-build=x86_64-pc-cygwin
-host= x86_64-pc-cygwin
-target=x86_64-pc-cygwin
As far as I can tell this variant works fine and also opam works in this configuration out of the box. Useful for people working on GPL projects or can afford a lawyer to figure out the licensing details or a want to buy a cygwin commercial license.
-build=x86_64-pc-cygwin
-host= x86_64-pc-cygwin
-target=x86_64-w64-mingw32
This is what you mentioned above and, assuming opam works, would be a good work for environment for everybody who is mostly working on Linux and just wants to supply Windows binaries of his application with minimal effort.
-build=x86_64-pc-cygwin
-host=x86_64-w64-mingw32
-target=x86_64-w64-mingw32
This works by using the supplied separate makefiles and is required for those who mainly work on Windows and for applications which need an Ocaml compiler at run time (like Coq 8.5).
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2015-10-26 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 13:57 Soegtrop, Michael
2015-10-23 16:13 ` Xavier Leroy
2015-10-24 9:29 ` Soegtrop, Michael
2015-10-24 10:05 ` Adrien Nader
2015-10-24 10:09 ` Gabriel Scherer
2015-10-24 10:54 ` Soegtrop, Michael
2015-10-24 10:59 ` David Allsopp
2015-10-26 8:25 ` Soegtrop, Michael [this message]
2015-10-24 11:16 ` Gerd Stolpmann
2015-10-26 8:42 ` Soegtrop, Michael
2015-10-26 19:04 ` Adrien Nader
2015-10-24 10:49 Soegtrop, Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F7D3B1B3C4B894D824F5B822E3E5A172CE33594@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox