From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: Romain Bardou <romain.bardou@inria.fr>
Cc: caml-list@inria.fr, matthieu.dubuget@gmail.com
Subject: Re: [Caml-list] OCaml installer on Windows no longer installs MinGW?
Date: Mon, 15 Jul 2013 23:34:15 +0800 [thread overview]
Message-ID: <51E41677.2010008@gmail.com> (raw)
In-Reply-To: <51E4044D.5020303@inria.fr>
Hi,
The installer is indeed maintained, but it is slightly outdated. I
asked the people from Tcl/Tk to provide a "stable" URL, e.g.
installer-w32-threads-latest.exe, but they could not do it, and hosting
a copy of the installer myself would be a breach of license, so
unfortunately, the installer will keep breaking at regular intervals
because of that. (I guess I could get away with a php script on my
homepage that emits a Location: header, so that I just have to modify a
script and not regenerate the installer whenever the URL for the latest
stable version of tcl/tk changes, but that's more hackish than I was
hoping for.)
As to the flexdll issue, I'm currently away, but I plan to refresh the
installer just because of that when I get back.
For the "not all packages got installed by cygwin properly" error,
please submit a pull request on the install.nsi file, it's really
trivial to add a new package to the set of those that are installed by
default. I'm surprised it didn't work by itself, but well.
Finally, for the OASIS-related errors, that's outside the scope of my
responsibilities as a maintainer of the ocaml installer for windows :-).
Cheers,
jonathan
On Mon 15 Jul 2013 10:16:45 PM SGT, Romain Bardou wrote:
> Le 15/07/2013 14:39, Matthieu Dubuget a écrit :
>> Le 15/07/2013 14:22, Matthieu Dubuget a écrit :
>>> Le 15/07/2013 14:11, Romain Bardou a écrit :
>>>
>>>>
>>>> I have absolutely no clue what to do now. Is the installer from
>>>> protz.github deprecated?
>>> Well. I would say it is a little outdated. It should just be slightly
>>> adapted and recompiled.
>>>
>>
>> I must admit that using OCaml on windows with mingw flavour is not
>> actually a click and work experience…
>>
>> And most of the time, the packages are to be adapted in order to compile.
>>
>> I also hit another problem, that you should be aware of:
>>
>> on my installation, *i686-w64-mingw32-gcc -o toto ...* produces
>> *toto.exe* instead of *toto*.
>> But flexlink has asked for *toto*, and never sees *toto.exe*, which
>> leads to a compilation failure.
>
> Interesting. I managed to compile Cryptokit, LablGTK (this one took me a
> while…) and an application which uses both of them, without the error
> you describe.
>
> Thanks and cheers,
>
next prev parent reply other threads:[~2013-07-15 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 12:11 Romain Bardou
2013-07-15 12:21 ` David Allsopp
2013-07-15 12:22 ` Matthieu Dubuget
2013-07-15 12:37 ` Romain Bardou
2013-07-15 12:42 ` Matthieu Dubuget
[not found] ` <51E3E975.7020708@gmail.com>
2013-07-15 12:39 ` Matthieu Dubuget
2013-07-15 14:16 ` Romain Bardou
2013-07-15 15:34 ` Jonathan Protzenko [this message]
2013-07-15 15:59 ` Romain Bardou
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=51E41677.2010008@gmail.com \
--to=jonathan.protzenko@gmail.com \
--cc=caml-list@inria.fr \
--cc=matthieu.dubuget@gmail.com \
--cc=romain.bardou@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