From: Alain Frisch <alain@frisch.fr>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Pre-compiled ocaml binary for windows
Date: Tue, 07 Dec 2010 10:30:13 +0100 [thread overview]
Message-ID: <4CFDFEA5.3000900@frisch.fr> (raw)
In-Reply-To: <slrnifru2m.ut5.sylvain@gallu.homelinux.org>
On 12/07/2010 10:03 AM, Sylvain Le Gall wrote:
> We will provide ocamlopt (32/64 bits). But indeed, the toolchain can be
> an issue (esp. masm). I plan to use VS2008.
I don't think MASM is going to be an issue. FWIW, the Windows 7 SDK
(which has nothing to do with Windows 7) contains everything needed
(including the VS2008 C compiler, the assembler, the linker, the
libraries, etc).
> Maybe the native Lexifi's amd64/x86 backend is a better option. If we
> are able to use this backend, we still have to use a linker ?
This native backend removes the need for an external assembler for using
ocamlopt. Flexdll has a standalone mode to build DLLs which works fine
to build pure OCaml .cmxs plugins for ocamlopt (there might be some
issues when linking C libraries in the cmxs). But yes, to build the main
program, you still need an external linker (this could be addressed by
working more on flexdll) and also static runtime objects and libraries.
An option could be to ship a minimalistic main program, which simply
dynlinks .cmxs files given on its command line.
>> Not building labltk seems ok. As for the graphical toplevel, I think
>> there are some pending bugs (random crashes) with the current version
>> under recent versions of Windows, so it's probably better not to include
>> it. Some support for installing the emacs mode automatically and/or a
>> version of ledit would be useful replacements.
>>
>
> I didn't known this fact. This is another reason for not building
> labltk. Since I almost never use it, I don't think it will be a big
> loose.
The graphical toplevel does not depend on labltk, so the two issues are
really unrelated. For crashes with the OCamlWin.exe, I was thinking
about http://caml.inria.fr/mantis/view.php?id=4399 and
http://caml.inria.fr/mantis/view.php?id=3052, but this might be pure
FUD. The real problem is that nobody seems interested enough in this
graphical toplevel to put serious work on it.
> I will probably look for ledit (or lwt toplevel) which seems a better
> alternative to emacs (too heavy too install).
If your hope is to make OCaml accessible to beginner hobbyists under
Windows (I assume this is the primary audience for pre-compiled
binaries), you might still want to provide easy ways to use code
editors. Providing easy access only to the toplevel (be it graphical, or
with a line-editor) might be a turnoff for beginners.
-- Alain
next prev parent reply other threads:[~2010-12-07 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 20:06 José Romildo Malaquias
2010-12-06 15:28 ` [Caml-list] " Damien Doligez
2010-12-06 16:08 ` Sylvain Le Gall
2010-12-06 17:50 ` [Caml-list] " Matthieu Dubuget
2010-12-07 0:24 ` Sylvain Le Gall
2010-12-07 8:21 ` [Caml-list] " Alain Frisch
2010-12-07 9:03 ` Sylvain Le Gall
2010-12-07 9:30 ` Alain Frisch [this message]
2010-12-07 9:42 ` Sylvain Le Gall
2010-12-07 9:49 ` [Caml-list] " Alain Frisch
2010-12-09 11:54 ` Mauricio Fernandez
2010-12-09 13:12 ` Alain Frisch
2010-12-07 9:42 ` gasche
2010-12-07 9:52 ` Alain Frisch
2010-12-07 10:29 ` gasche
2010-12-07 15:57 ` [Caml-list] " ygrek
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=4CFDFEA5.3000900@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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