From: whitequark <whitequark@whitequark.org>
To: "Boutillier, Pierre" <Pierre_Boutillier@hms.harvard.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] opam-cross-windows
Date: Fri, 20 May 2016 18:45:55 +0000 [thread overview]
Message-ID: <77d8e9183ed929e80464c70376561cd8@whitequark.org> (raw)
In-Reply-To: <9D53A509-55BC-4E89-A8CF-389EE20580DD@hms.harvard.edu>
On 2016-05-20 18:38, Boutillier, Pierre wrote:
> Hi list,
>
> Sorry to:
> - reactivate an old thread
> - maybe going into human-relation issue (hopefully not)
>
> On github live:
> https://github.com/whitequark/opam-cross-windows
> and
> https://github.com/vouillon/opam-windows-repository
>
> Both are active (9 days old commit vs 10 days old commit). One has
> yojson, the other (a bit old) lwt. I sit in the middle.
> Could you give me insight of technical design choice differences (i
> don't see) in order to allow me to decide in which direction I should
> put my energy toward helping a "merge"?
My repository uses MXE so that a wide range of native dependencies can
be easily compiled. Moreover, you get opam-cross-android and
opam-cross-ios
for free, with exact same conventions, largely similar package sets,
etc,
and it is easy to port packages between the three as well.
Also, Jerome has expressed a desire to merge the opam-cross-*
repositories
but that didn't go anywhere so far.
>
> All the best,
> Pierre B.
>
>
>> Le 13 mars 2016 à 05:02, whitequark <whitequark@whitequark.org> a
>> écrit :
>>
>> 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
--
whitequark
next prev parent reply other threads:[~2016-05-20 18:45 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
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 [this message]
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=77d8e9183ed929e80464c70376561cd8@whitequark.org \
--to=whitequark@whitequark.org \
--cc=Pierre_Boutillier@hms.harvard.edu \
--cc=caml-list@inria.fr \
/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