caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Yaron Minsky <yminsky@cs.cornell.edu>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Windows, Godi, Findlib and all that
Date: Wed, 26 Oct 2005 22:53:32 +0200	[thread overview]
Message-ID: <1130360012.15589.66.camel@localhost.localdomain> (raw)
In-Reply-To: <891bd3390510260632l695672e0i927e23d1a460ef23@mail.gmail.com>

Am Mittwoch, den 26.10.2005, 09:32 -0400 schrieb Yaron Minsky:
> I've been trying to figure out what the state of OCaml on Windows is,
> and I'm wondering if anyone on the list can help me out.  I've been
> trying to get godi, findlib and integration with MS excel going at the
> same time.  The problem is that these approaches appear at first
> glance to be incompatible.  Here are the dependencies that I know
> about.
> 
> 1. Godi works only on cygwin, and isn't supported even with mingw.

Porting Godi to mingw has become quite important. It is now
top-priority, but apparently not simple. A lot of preliminary work has
already been done, especially getting rid of all the C helper programs
(this is not yet released, though), so the port has only to deal with
O'Caml programs and shell scripts.

However, there is no solution in the short term. I expect the release of
the mingw port in summer 2006.

> 2. Findlib works with cygwin -or- mingw, but doesn't work with the native build

This should be doable. Findlib is a pure O'Caml program, and the system
side is very simple. Although I don't know what is going wrong, I
suspect the calling conventions of external programs are different.
Findlib executes ocamlc as subprocess.

> 3. The real windows support (win32 libraries and ocamole, the latter
> of which provides Excel integration), only work with the native build.

I have actually no idea whether this can be ported to mingw, or whether
one can at least link mingw- and msvc-generated libraries together. The
mingw web site says this is possible.

Gerd

> Does anyone have a sense of whether any of these issues can be
> overcome?  How much work, for instance, would it take to get findlib
> working on the native win32 build?  How about Godi?  How about getting
> theings like ocamole working with the mingw build?
> 
> Thanks,
> Yaron Minsky
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
> 
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
Telefon: 06151/153855                  Telefax: 06151/997714
------------------------------------------------------------


      reply	other threads:[~2005-10-26 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 13:32 Yaron Minsky
2005-10-26 20:53 ` 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=1130360012.15589.66.camel@localhost.localdomain \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=yminsky@cs.cornell.edu \
    /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).