From: fred@ontosys.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Yet Another Compilation Question: lablgtk for windows + cygwin-mingw
Date: Mon, 5 Aug 2002 12:05:31 -0500 [thread overview]
Message-ID: <20020805120530.A11782@ontosys.com> (raw)
In-Reply-To: <20020805164038.A21811@pauillac.inria.fr>; from xavier.leroy@inria.fr on Mon, Aug 05, 2002 at 04:40:38PM +0200
On Mon, Aug 05, 2002 at 04:40:38PM +0200, Xavier Leroy wrote:
> One last, general comment. (Climbing on my soapbox.) The GNU
> compilers, OCaml, GTK. lablgtk, etc, are all software projects that
> are developed primarily under Unix, and then ported to Windows. While
> each of these ports are done carefully and with considerable ingenuity,
> Windows is not Unix and minor differences or inconsistencies remain in
> each port. These minor issues are usually workable when you use only
> one port, but can become a real headache when you pile up port over
> port over port. What I am coming at is that unless you like to suffer
> and are ready to solve these issues yourself, it doesn't make much
> sense to develop an OCaml+lablgtk+GTK program under Windows.
I've been planning to build an interactive application with OCaml that
will be deployed primarily on Windows, so I'd like to understand your
warning better.
1. Is the risk just in developing (compiling, packaging) on Windows,
or also in deploying to Windows?
2. What do you mean by "piling port after port"? Do you mean
reworking the application to track changes as the various tools
(GNU+OCaml+labltk+GTK) evolve in successive releases? Has this
been a big problem in applications such as Unison? (Or any
other broadly deployed OCaml app? I don't know of others.)
3. Is there some other GUI framework that you expect will entail less
suffering than lablgtk+GTK?
4. As the porting problem applies to the GNU compilers and OCaml
itself, are you warning us against developing OCaml applications
for use on Windows?
--
Fred Yankowski fred@ontosys.com tel: +1.630.879.1312
OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370
www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-08-05 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 13:49 Kontra, Gergely
2002-08-05 14:40 ` Xavier Leroy
2002-08-05 17:05 ` fred [this message]
2002-08-06 8:59 ` Xavier Leroy
2002-08-06 9:52 ` Nicolas Cannasse
2002-08-08 14:07 ` Alan Schmitt
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=20020805120530.A11782@ontosys.com \
--to=fred@ontosys.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).