From: "Nicolas Cannasse" <warplayer@free.fr>
To: <fred@ontosys.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Yet Another Compilation Question: lablgtk for windows + cygwin-mingw
Date: Tue, 6 Aug 2002 11:52:57 +0200 [thread overview]
Message-ID: <000d01c23d2f$0b977df0$0700a8c0@warp> (raw)
In-Reply-To: <20020805120530.A11782@ontosys.com>
> 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.
As an windows ocaml user for some time now, I'll try to answer your
questions
> 1. Is the risk just in developing (compiling, packaging) on Windows,
> or also in deploying to Windows?
As Xavier answered, deploying under windows is easier than under Unix . You
can package binaries quite easily without even the need for the end-user to
install Ocaml ( DLL's since 3.04 simplified lots of things )
About developing, I'm currently compiling and running OCaml code from MSVC++
:)
It's quite confortable this way, even if an OCaml IDE would be better.
> 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?
I've been developping Osiris, an OCaml class-based GUI system which is built
on top of the Win32 API OCaml Port (still partial, but complete enough to
work with). If you're willing to develop GUIs for windows-only, Osiris may
be a good choice. If you're willing to develop cross-platform applications,
I have been thinking for few month now to write a GTK port of Osiris... when
I'll have some free time :)
> 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?
Don't worry, the ratio ( INRIA support ) / (number of window users) is quite
high :)
Nicolas Cannasse
-------------------
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-06 9:53 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
2002-08-06 8:59 ` Xavier Leroy
2002-08-06 9:52 ` Nicolas Cannasse [this message]
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='000d01c23d2f$0b977df0$0700a8c0@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=fred@ontosys.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