From: Carsten Clasohm <clasohm@rivalnet.com>
To: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: AW: ocaml needs users: native code for windows?
Date: Tue, 13 May 1997 10:16:54 +0200 [thread overview]
Message-ID: <01BC5F86.F615A000@strato> (raw)
> You still can't ship a plain binary, can you?
I can. I use ocamlopt to compile the OCaml code and link the object files and some OCaml libraries to my Win32 executable. Linking is done by VisualC++. (In practice it's a bit more complicated, as e.g. you have to link the additional file "camlstartup.asm" that would be automatically added if you used ocamlopt for linking. And there seems to be a conflict between Microsoft's runtime string functions and the regexp package delivered with OCaml. So I replaced the C regexp functions in OCaml's libstr.)
> At least the source code to MFC is
> available to anybody who buys VC++, so it is just a simple (!) matter
> of trascribing it from C++ to OCaml, right ?
That's right. And it's indeed easy to port C++ code to OCaml.
But VisualC++ would still have the advantage of offering a simple way to design GUI resources and link them with your code in an easy way (via message maps).
reply other threads:[~1997-05-13 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01BC5F86.F615A000@strato \
--to=clasohm@rivalnet.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