From: Adrien Nader <adrien@notk.org>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
"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 20:04:02 +0100 [thread overview]
Message-ID: <20151026190402.GA26641@notk.org> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CE335B7@IRSMSX102.ger.corp.intel.com>
On Mon, Oct 26, 2015, Soegtrop, Michael wrote:
> > The Makefile.nt system exists mainly for the MSVC build. I also think that the
> > mingw build would be better done with the Makefiles.
>
> I see. I guess an Ocaml build is very special, but did the Ocaml community ever consider cmake or bakefiles? The main advantage, besides supplying cross platform builds in a maintainable way, is that they also supply IDE project files, which makes it more comfortable to work on Ocaml itself, especially libraries.
There are several things to take into account here:
- history
- migration cost
- availability of something in either cmake or bmake that fits the needs
of OCaml and of the compiler (I am fairly sure there aren't any, at
least in cmake)
- cost of cleaning 20 years of growth (this applies to anything related
to this subject since it is often difficult to understand the
differences between .nt and non .nt files)
--
Adrien Nader
next prev parent reply other threads:[~2015-10-26 19:04 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
2015-10-24 11:16 ` Gerd Stolpmann
2015-10-26 8:42 ` Soegtrop, Michael
2015-10-26 19:04 ` Adrien Nader [this message]
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=20151026190402.GA26641@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--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).