From: Adrien Nader <adrien@notk.org>
To: whitequark <whitequark@whitequark.org>
Cc: "Soegtrop, Michael" <michael.soegtrop@intel.com>, caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] opam-cross-windows
Date: Tue, 24 May 2016 14:35:15 +0200 [thread overview]
Message-ID: <20160524123515.GA23998@notk.org> (raw)
In-Reply-To: <523de93ae2fdfcafd18686809b09d84e@whitequark.org>
On Tue, May 24, 2016, whitequark wrote:
> On 2016-05-23 08:24, Soegtrop, Michael wrote:
> >Dear whitequark,
> >
> >>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.
> >
> >Thanks for the pointer to MXE (http://mxe.cc/). A very interesting
> >project! It might help to put MinGW cross opam for cygwin on a solid
> >foundation.
> >
> >One question: how happy are you with the make file approach of MXE? I
> >worked an something similar as MXE, but based on shell scripts, since
> >I thought "meta makefiles" might be hard to maintain and to debug and
> >shell scripts might be more appropriate for this task. But it was a
> >difficult decision and I still see some advantages in using make for
> >this.
>
> I have absolutely none in-depth understanding of how MXE functions,
> but I
> can say that I never needed one, or wanted it, so I'd say it is a
> success :)
> Of course, this is only valid from the perspective of a user.
I make win-builds.org and there's a really large update coming amost any
time soon. Currently it has C and C++ things.
The goal is to make a distribution roughly in the Linux sense and it's
very "standard". MXE on the other hand only does static linking.
Different goals and approaches.
--
Adrien Nader
next prev parent reply other threads:[~2016-05-24 12:35 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
2016-05-23 8:24 ` Soegtrop, Michael
2016-05-24 6:57 ` whitequark
2016-05-24 12:35 ` Adrien Nader [this message]
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=20160524123515.GA23998@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=michael.soegtrop@intel.com \
--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