From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] New version of the binary installer for Windows
Date: Wed, 28 Mar 2012 14:24:35 +0200 [thread overview]
Message-ID: <4F730303.8000802@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Hi,
I've spent the past few days improving the OCaml installer for windows.
This should solve all issues that have been mentioned previously. This
in preparation for the upcoming 4.0 release ; therefore, the "beta
installer" below will install a fairly recent trunk version of OCaml.
http://yquem.inria.fr/~protzenk/caml-installer/ocaml-4.01.0+dev0-i686-mingw64.exe
*Changelog:*
- The installer packages a working and well-configured findlib, out of
the box. This means you can open up cmd.exe, type ocaml, then type #use
"topfind";; in the top-level.
- The installer no longer blasts the PATH variable if it is too long.
Moreover, it is now able to deal with PATHs that are up to 8192 bytes long.
- The installer is now able to deal with multi-user privileges: in
particular, you can use this installer on a *limited account*: OCaml
will properly install into your local "Application Data" folder if you
don't have administrator rights on your machine. This should be
particularly useful for school computers that run Windows.
- Various fixes: better cleanups on exit, minor fixes for OCamlWinPlus,
properly warn the user if it was unable to download ActiveTCL from the
internet.
- The installer packages a newer version of flexlink, so you shouldn't
have any more issues with gcc not accepting the -mno-cygwin option.
However, the new, official toolchain uses the mingw64 32-bit compilers.
This means flexlink will look for a i686-w64-mingw32-gcc in your path
whenever you try to do native compilation. The official, recommended way
to work is to install cygwin and its mingw64 packages. While in theory
it should be possible to work within a MSys environment, some issues [1]
currently prevent you from doing so.
[1] http://caml.inria.fr/mantis/view.php?id=5465
Please let me know if anything doesn't work as expected. This will be
the official installer for the 4.0 release.
Cheers,
jonathan
[-- Attachment #2: Type: text/html, Size: 2549 bytes --]
next reply other threads:[~2012-03-28 12:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 12:24 Jonathan Protzenko [this message]
2012-03-28 14:55 ` Kakadu
2012-03-28 15:19 ` Jonathan Protzenko
2012-03-28 15:25 ` Wojciech Meyer
2012-03-28 15:38 ` Jonathan Protzenko
2012-03-28 15:54 ` David Allsopp
2012-03-28 16:04 ` Jonathan Protzenko
2012-03-28 17:36 ` Adrien
2012-03-28 20:42 ` Jonathan Protzenko
2012-03-29 11:55 ` Kakadu
2012-03-29 12:18 ` Gabriel Scherer
2012-03-29 12:19 ` Jonathan Protzenko
2012-03-29 12:27 ` Kakadu
2012-03-28 15:32 ` Jonathan Protzenko
2012-03-30 14:15 ` [Caml-list] " Jonathan Protzenko
2012-03-30 14:41 ` David Allsopp
2012-03-30 17:38 ` Kakadu
2012-04-03 12:32 ` Jonathan Protzenko
2012-03-31 9:34 ` Sylvain Le Gall
2012-04-02 8:03 ` Romain Bardou
2012-04-02 8:21 ` Alain Frisch
2012-04-02 8:23 ` David Allsopp
2012-04-02 11:14 ` Adrien
2012-04-02 11:39 ` Romain Bardou
2012-04-02 11:53 ` Jonathan Protzenko
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=4F730303.8000802@gmail.com \
--to=jonathan.protzenko@gmail.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).