From: whitequark <whitequark@whitequark.org>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: caml-list@inria.fr
Subject: RE: [Caml-list] [ANN] opam-cross-windows
Date: Tue, 15 Mar 2016 11:56:40 +0300 [thread overview]
Message-ID: <d910e5a64c1031eed49fbdfb09b39246@whitequark.org> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CEA7748@IRSMSX102.ger.corp.intel.com>
On 2016-03-15 11:53, Soegtrop, Michael wrote:
> Dear Whitequark,
>
>> Since Cygwin is striving to present a Unix-like environment, those
>> assumptions would not hold. So I don't think opam-cross-windows will
>> work
>> on Cygwin, sorry.
>
>> Note that opam-cross-windows uses a toolchain that targets plain Win32
>> API
>> without using any kind of POSIX emulation such as MSYS or Cygwin.
>
> I talked about cross compiling for MinGW under cygwin. This should be
> fairly similar to cross compiling for MinGW under Unix. The Ocaml
> compiler created by my scripts runs on plain windows (without cygwin
> installed) and also creates executables for such systems. I use cygwin
> just as a build environment.
>
> Ideally I would like to have an opam running on plain windows, but I
> think an Opam running on cygwin but creating plain windows tools might
> be a good compromise between usability and maintainability.
Ah. Yeah, that should just work. I don't see any reason why it wouldn't.
>
> 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, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
--
whitequark
next prev parent reply other threads:[~2016-03-15 8:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 9:02 whitequark
2016-03-14 19:55 ` Martin DeMello
2016-03-14 20:14 ` Adrien Nader
2016-03-14 20:26 ` Martin DeMello
2016-03-14 20:39 ` Adrien Nader
2016-03-14 21:10 ` Martin DeMello
2016-03-15 8:37 ` whitequark
2016-03-15 8:26 ` Soegtrop, Michael
2016-03-15 8:36 ` whitequark
2016-03-15 8:53 ` Soegtrop, Michael
2016-03-15 8:56 ` whitequark [this message]
2016-03-15 11:29 ` Soegtrop, Michael
2016-03-16 14:27 ` Andreas Hauptmann
2016-03-15 9:18 ` Adrien Nader
2016-03-15 9:12 ` David Allsopp
2016-05-20 18:38 ` Boutillier, Pierre
2016-05-20 18:45 ` whitequark
2016-05-23 8:24 ` Soegtrop, Michael
2016-05-24 6:57 ` whitequark
2016-05-24 12:35 ` Adrien Nader
2016-05-23 9:53 ` Mauricio Fernández
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=d910e5a64c1031eed49fbdfb09b39246@whitequark.org \
--to=whitequark@whitequark.org \
--cc=caml-list@inria.fr \
--cc=michael.soegtrop@intel.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;
as well as URLs for NNTP newsgroup(s).