caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: William Smith <bills@emu-bark.com>
Cc: Caml-list <caml-list@inria.fr>
Subject: AW: [Caml-list] Re: OCaml on Windows
Date: Thu, 27 Jun 2013 16:51:20 +0200	[thread overview]
Message-ID: <1372344680.3769.3@samsung> (raw)
In-Reply-To: <51CC43B1.4050809@emu-bark.com> (from bills@emu-bark.com on Thu Jun 27 15:52:49 2013)

Am 27.06.2013 15:52:49 schrieb(en) William Smith:
> Hi,
> 
> One major concern with using cygwin to compile ocamlc etc. is that  
> the resulting executables are subject to copy-left since it uses a  
> DLL that is distributed under GPL.

Thanks for the clarification (although I don't think anybody messed  
this up so far). There is in deed a difference between being dependent  
on the Cygwin DLL and on the Cygwin utilities. The first means that you  
get "infected" by the GPL, and there are also other potential technical  
problems from the emulation layer. So most professional developers try  
to avoid that. The other issue - and I think most of the discussion  
refers to that - are dependencies on command-line utilities from Cygwin  
(like bash). This is just a build-time matter.

> To quote from README.win32 in the top folder of the source:
> 
> (*) Cygwin-generated .exe files refer to a DLL that is distributed  
> under
> the GPL.  Thus, these .exe files can only be distributed under a  
> license
> that is compatible with the GPL.  Executables generated by MSVC or by
> MinGW have no such restrictions.
> 
> There's a difference between using cygwin to build the system (in  
> other words, compile everything with gcc)

Not quite exact: MinGW is also gcc-based. The point is whether you  
produce executables linking with the Cygwin DLL or not. (There used to  
be a switch -mno-cygwin for not linking with this DLL, but since quite  
a while there are separate gcc frontends for this purpose.)

> vs. using cygwin to compile the tools (in other words, use a cygwin  
> shell to execute all of the Makefile/Makefile.nt files and msvc or  
> MinGW as the compiler).

Right. The essential point is which C compiler is configured for use  
with ocaml (configure -cc the-cc-to-use).

> I have been building ocaml with the MSVC compiler for quite a while.   
> I use cygwin to run the shell and Makefiles in the build process.   I  
> don't use cygwin compilers or utilities (other than make) in my  
> production code.   I don't have any experience with the MinGW port.
> 
> I haven't done a thorough testing of all of the tools in OCaml-4.00.1  
> but I believe they all work.   [The only problem I have had is that I  
> have to manually block making the library otherlibs/labltk/browser.]
> 
> also, r.3@libertyserf.fr said:
> > Is anyone using omake on windows? Does it have a dependency on  
> Cygwin like ocamlbuild?
> 
> I believe that is false that ocamlbuild depends on cygwin.

ocamlbuild appears to call bash internally, and that's usually a Cygwin  
utility. In that sense, the statement is correct. There is no  
dependency on the Cygwin DLL.

Gerd


> Bill
> 
>> Hi,
> 
>> I am looking to use ocaml to implement a project for my employer.  
>> However, the
>> environment is Windows OS. I am using cygwin and so far it seems to  
>> work but
>> curious on experiences others have on using ocaml on windows - both  
>> as a
>> development and deployment platform. Also has anyone tried using  
>> opam on
>> windows? Does it work?
> 
>> Bikal
> 
> 
>-- 
> 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


-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------

      reply	other threads:[~2013-06-27 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 13:52 William Smith
2013-06-27 14:51 ` Gerd Stolpmann [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=1372344680.3769.3@samsung \
    --to=info@gerd-stolpmann.de \
    --cc=bills@emu-bark.com \
    --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;
as well as URLs for NNTP newsgroup(s).