From: Gerd Stolpmann <gerd@gerd-stolpmann.de>
To: "Vijay Chakravarthy" <vchakravarthy@verticalnet.com>,
"Vijay Chakravarthy" <vchakravarthy@verticalnet.com>,
<lionel.fourquaux@wanadoo.fr>, "'Chris Hecker'" <checker@d6.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: OCaml for Windows: a suggestion
Date: Tue, 13 Feb 2001 19:20:53 +0100 [thread overview]
Message-ID: <0102131953080C.02644@ice> (raw)
In-Reply-To: <003f01c0969b$5e11b550$d3d4fc9e@SFOWVCHAK1L7>
On Wed, 14 Feb 2001, Vijay Chakravarthy wrote:
>While we are on this topic, some observations (trying to coordinate my
>windows based Ocaml development with the rest
>of my team (they use Linux, I have a laptop and use Win2000)) that can be
>considered feedback:
>
>1. findlib etc dont work on windows, and there is enough of a difference
>between make and nmake that most make scripts break.
>That causes a bunch of packages to be difficult to build under windows
>(difficult enough to put off novice programmers that
>I'm trying to get hooked on Ocaml)
>2. I guess 1. stems from dbm not being available on windows. Would it be
>difficult to have an interface to Sleepycat's version on windows,
>and make that part of the standard distrib?
No, this is not the reason. The problem with findlib (and other packages) is
that there are no shell scripts under Windows. Findlib uses scripts for
configuration, and for the installation of new packages. It is possible to
replace these scripts by O'Caml programs; but it is not a simple task.
Of course, there is a second problem: I neither have a Windows system nor the
VC compiler. (Ok, there is now the cygwin port, but it should be compatible
enough such that findlib works (with little effort), so the cygwin port is not
the problem.)
>3. Since fork() doesnt work on windows, I cant use most of the web-server
>type stuff written in Ocaml. It would be nice to have
>a (medusa,thttpd,zeus) style single threaded web-server based on equeues. It
>would also rock -- performance wise (upto a certain
>number of users I guess)
I would appreciate such a server, too.
Gerd
--
----------------------------------------------------------------------------
Gerd Stolpmann Telefon: +49 6151 997705 (privat)
Viktoriastr. 100
64293 Darmstadt EMail: gerd@gerd-stolpmann.de
Germany
----------------------------------------------------------------------------
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-02-13 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 21:07 Lionel Fourquaux
2001-02-04 17:54 ` Jean Martos
2001-02-10 19:28 ` Lionel Fourquaux
2001-02-11 9:52 ` Xavier Leroy
2001-02-12 19:37 ` Chris Hecker
2001-02-12 21:27 ` Lionel Fourquaux
2001-02-14 15:32 ` [Caml-list] " Vijay Chakravarthy
2001-02-13 18:07 ` Mattias Waldau
2001-02-13 18:20 ` Gerd Stolpmann [this message]
2001-02-13 4:36 Hao-yang Wang
2001-02-13 16:25 ` [Caml-list] " Brian Rogoff
2001-02-14 17:50 [Caml-list] " Dave Berry
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=0102131953080C.02644@ice \
--to=gerd@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=info@gerd-stolpmann.de \
--cc=lionel.fourquaux@wanadoo.fr \
--cc=vchakravarthy@verticalnet.com \
/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).