From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: Pre-compiled ocaml binary for windows
Date: Tue, 7 Dec 2010 09:03:18 +0000 (UTC) [thread overview]
Message-ID: <slrnifru2m.ut5.sylvain@gallu.homelinux.org> (raw)
In-Reply-To: <4CFDEE7E.8030000@frisch.fr>
Hello,
On 07-12-2010, Alain Frisch <alain@frisch.fr> wrote:
> On 12/07/2010 01:24 AM, Sylvain Le Gall wrote:
>> Here is the list so far:
>> 1. no build system setup : Martin who first did the packaging, didn't
>> have included how to build ocaml/findlib neither the binaries itself.
>> So basically you need to build by hand to generate the .msi. This is
>> not a big issue but for a collective effort it is better to have a
>> common way to build the binaries
>> 2. some environment variables are not set and make ocaml crash (AFAIR, we
>> doesn't set OCAMLIB)
>> 3. we don't ship the graphical toplevel
>> 4. I am still not sure how to deal with ActiveTCL + OCaml (because of the
>> ActiveTCL license)
>> 5. Total lack of documentation
>
> Do you plan to support ocamlopt? If yes, the users will have to install
> a toolchain (at least, an assembler+linker). Mingw has the advantage of
> producing binaries that depend only on msvcrt.dll (available on any
> fresh Windows installation), not on a specific version of
> msvcr80.dll/msvcr90.dll. But Windows users might prefer to install a
> version of VS Express or a Windows SDK.
We will provide ocamlopt (32/64 bits). But indeed, the toolchain can be
an issue (esp. masm). I plan to use VS2008.
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 ?
>
> 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.
I will probably look for ledit (or lwt toplevel) which seems a better
alternative to emacs (too heavy too install).
Regards,
Sylvain Le Gall
next prev parent reply other threads:[~2010-12-07 9:03 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 [this message]
2010-12-07 9:30 ` Alain Frisch
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=slrnifru2m.ut5.sylvain@gallu.homelinux.org \
--to=sylvain@le-gall.net \
--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