caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Cross-compiling OCaml
Date: Wed, 1 Sep 2004 14:16:39 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDKEJBHHAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <200409011445.05355.jgoerzen@complete.org>

John Goerzen wrote:
> > Brandon Van Every wrote:
> >
> > how satisfied they are.  I encountered a similar phenom on
>
> You also encountered it on freeciv-dev.

Goodness, the C crowd.  If OCaml people were to consider the codebase
and my reactions to it, do you want to take bets on where their
sympathies would lie?  Let's just say my offers to Pythonize stuff met
with crickets chirping.  I did make a VS 2003 build that apparently
nobody but myself actually wanted because they're too UNIX / mingw
oriented.  Did the same thing for XConq, got the same reactions.
Freeciv and XConq were the painful mingw projects I referred to when
this thread started.  Well, and all their support libraries too.  Well,
kicking zlib into VS 2003 buildable shape wasn't so hard, but it was
futzy.  Like ripping off a <dirent.h> implementation and that sort of
thing.  I'm sooooo uninterested in mingw now.

It feels like I've been at "heavy duty e-mail" for a week.  Checking
dates, it's only been 3 days for this thread, but that's way more than
enough.  Even I have my limits, amazingly enough.  As of this post, I'm
bowing out of this thread.

I made the point I wanted to make in my 1st post.  Linux-to-Windows
cross-compilation is a Windows avoidance strategy, not a Windows support
strategy.  As such, Linux guys may want it, but Windows guys don't.
We'd like VS 2003 support, or nothing, thanks much.  Makefiles with MSVC
as the backend are ok, just please don't assume a Cygwin / mingw build
and header file environment.

I'll be looking at cross-platform build tools, but that's like OCaml
project priority #5 right now.  It seems there are several competing
OCaml build tools out there  For instance, ocalibs has its own tool
called ocalibsmake.  Plus non-OCaml build tools to consider.  A lot of
tools to chug through.  I don't have time right now.

Oh, and if you're wondering where to get the free MSVC compiler sans
Visual Studio IDE, it's at:
http://msdn.microsoft.com/visualc/vctoolkit2003/  So don't say Microsoft
never gave ya nuthin'.  :-) They're reeeel generous, they just love you
all over.

> But that's like complaining about going to a Perl meeting and hearing
> about parsing or going to an Emacs meeting and hearing about Lisp.

Indeed, part of why I dropped Python is there's nothing worthwhile in
that community for 3D graphics.  I did a lot of looking and digging.
Nothing is past the "Hey, we've got an OpenGL wrapper!" stage.  Well,
neither is OCaml, but OCaml has performance and Python doesn't.

> Frankly, through all your talk on all these forums, I have never yet
> seen even one single substantive thing come out of it.  I
> think you are all talk and no do.  In other words, a troll.
>
> [...]
>
> Or /dev/null, preferably.  Since the set of your projects is
> pretty much the same as the contents of that file.

You're welcome to come over to ocamlgames, ocaml-biz, or the COCAN wiki
at any time.  I haven't seen you at any of those venues, so perhaps
you're just prone to the Law Of Selective Observation.  If you have
serious work to discuss, we can do so.


Cheers,                     www.indiegamedesign.com
Brand*n Van Every           S*attle, WA

"Troll" - (n.) Anything you don't like.
Usage: "He's just a troll."

-------------------
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


  reply	other threads:[~2004-09-01 21:06 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AA48BAF0-FC3A-11D8-8C25-000A958FF2FE@wetware.com>
2004-09-01 18:37 ` Brandon J. Van Every
2004-09-01 19:45   ` John Goerzen
2004-09-01 21:16     ` Brandon J. Van Every [this message]
     [not found] <Pine.LNX.4.44.0408312302560.3196-100000@localhost>
2004-08-31 20:04 ` Brandon J. Van Every
2004-08-30 21:02 Ken Rose
2004-08-30 21:30 ` Erik de Castro Lopo
2004-08-31  6:09 ` Sven Luther
2004-08-31  6:50   ` Brandon J. Van Every
2004-08-31  7:14     ` james woodyatt
2004-08-31  9:05       ` Brandon J. Van Every
2004-08-31 13:41         ` John Goerzen
2004-08-31 15:56           ` Ken Rose
2004-08-31 19:30           ` Brandon J. Van Every
2004-09-01  0:05           ` Christopher A. Watford
2004-09-01  7:53             ` Sven Luther
2004-09-01  7:32         ` james woodyatt
2004-09-01 16:38           ` Brandon J. Van Every
2004-09-01 17:17             ` Brandon J. Van Every
2004-09-01 22:56               ` Sven Luther
2004-09-01 17:32             ` John Goerzen
2004-09-02 21:24             ` I R T
2004-08-31  7:16     ` Sven Luther
2004-08-31  9:05       ` Brandon J. Van Every
2004-08-31  9:18         ` Sven Luther
2004-08-31  9:41           ` Brandon J. Van Every
2004-08-31 15:17           ` skaller
2004-08-31 16:49             ` Sven Luther
2004-08-31 13:48         ` John Goerzen
2004-09-01 13:22         ` I R T
2004-08-31 13:56           ` Erik de Castro Lopo
2004-08-31 13:29     ` John Goerzen
2004-08-31 14:06       ` Erik de Castro Lopo
2004-08-31 15:48         ` skaller
2004-08-31 15:54         ` John Goerzen
2004-08-31 22:49           ` Jon Harrop
2004-08-31 23:36             ` Benjamin Geer
2004-09-01  8:08             ` Erik de Castro Lopo
2004-09-02 11:30               ` Richard Jones
2004-09-09  1:46               ` Jon Harrop
2004-09-01  4:05           ` skaller
2004-09-01  8:45             ` Erik de Castro Lopo
2004-09-01  7:40           ` Erik de Castro Lopo
2004-08-31 19:11       ` Brandon J. Van Every
2004-09-01 21:18         ` I R T
2004-08-31 18:34     ` brogoff

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=OOEALCJCKEBJBIJHCNJDKEJBHHAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.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).