From: Martin DeMello <martindemello@gmail.com>
To: whitequark <whitequark@whitequark.org>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] opam-cross-windows
Date: Mon, 14 Mar 2016 12:55:59 -0700 [thread overview]
Message-ID: <CAFrFfuGz6WA7X19c7R1oVuKN0n86+0aNw0xOz-bgaVbD8z4dew@mail.gmail.com> (raw)
In-Reply-To: <bf0131483b16f5ca8877a614c22197b5@whitequark.org>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
If anyone has gotten this working on ubuntu, please share the mingw
packages you had to install for it. (If not I'll report back once I do.)
martin
On Sun, Mar 13, 2016 at 1:02 AM, whitequark <whitequark@whitequark.org>
wrote:
> Hi all,
>
> I've released opam-cross-windows[1], a 4.02.3 OCaml toolchain
> in the spirit of opam-cross-android[2] (ex opam-android).
> It provides easy cross-compilation of the OCaml compiler
> and select packages from any *nix environment to 32-bit
> and 64-bit x86 Windows.
>
> There aren't many packages yet but you're encouraged to submit
> your own. Personally, I find the porting process that uses
> the opam-cross-* conventions so simple and robust that it
> can be done nearly mindlessly.
>
> The cross-compiled package definitions themselves are
> identical to the ones from opam-cross-android (except for
> s/android/windows) so I think cross-compilation should gain
> at least minimal OPAM support; I've described my proposal
> at [3].
>
> [1]: https://github.com/whitequark/opam-cross-windows
> [2]: https://github.com/whitequark/opam-cross-android
> [3]: https://github.com/ocaml/opam/issues/2476
>
> --
> whitequark
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2448 bytes --]
next prev parent reply other threads:[~2016-03-14 19: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 [this message]
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
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=CAFrFfuGz6WA7X19c7R1oVuKN0n86+0aNw0xOz-bgaVbD8z4dew@mail.gmail.com \
--to=martindemello@gmail.com \
--cc=caml-list@inria.fr \
--cc=whitequark@whitequark.org \
/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).