caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: paul.lachat@edu.univ-fcomte.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [Question] Compile a custom toplevel on Windows
Date: Wed, 19 Apr 2017 08:31:55 +0200	[thread overview]
Message-ID: <20170419063155.GA21673@notk.org> (raw)
In-Reply-To: <36405058.13728179.1492500074563.JavaMail.zimbra@edu.univ-fcomte.fr>

Hi,

On Tue, Apr 18, 2017, paul.lachat@edu.univ-fcomte.fr wrote:
> I want to compile the toplevel to have a .exe, so I could avoid using Cygwin to launch the application. 

"Using Cygwin" can be quite broad, does it mean that you want to avoid
the whole cygwin setup (through its setup.exe and everything) or also
avoid the cygwin1.dll dependency?

Usually, distributing an application built with Cygwin doesn't require
distributing more than the cygwin1.dll file. For the ocaml binaries, I
think that Cygwin adds no dependency other than this file.

If it were already merely cygwin1.dll that you're trying to avoid, I
invite you to think more about it and to compare the difficulties of
doing this build with the gains of avoiding it. It's a single file,
apparently only the ocaml compiler/toplevel will be linked against it,
and chances are that you already have an infrastructure able to provide
several files (e.g. all the .cm* files).

In both cases however, the filesystem interactions will reflect the
Cygwin lineage but if you are not doing such operations, the negative
impact of Cygwin should be minimal.

-- 
Adrien Nader

      parent reply	other threads:[~2017-04-19  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  7:21 paul.lachat
2017-04-18 18:11 ` Evgeny Roubinchtein
2017-04-19  6:31 ` Adrien Nader [this message]

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=20170419063155.GA21673@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=paul.lachat@edu.univ-fcomte.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;
as well as URLs for NNTP newsgroup(s).