From: Dmitry Bely <dbely@mail.ru>
To: caml-list@inria.fr
Subject: Re: [Caml-list] camlidl - problems under windows NT
Date: 21 Mar 2002 15:19:42 +0300 [thread overview]
Message-ID: <y9gmglk1.fsf@mail.ru> (raw)
In-Reply-To: <Pine.LNX.4.21.0203201028490.27664-100000@gig-0.cs.unm.edu>
"William D. Neumann" <wneumann@cs.unm.edu> writes:
> I'm having some problems getting camlidl to work for me under windows NT
> (well, not camlidl, but its output). I created a very simple C routine,
> bf.c and its associated .idl file, dumb.idl, which I processed with
> camlidl...all went well here. I then compiled bf.c, dumb.c, dumb.mli, and
> dumb.ml without problems. The problem comes when I try to use the results
> of the above in a new program. Here's what happens:
>
> $ ocamlc -o bftest -custom bf.obj dumb.obj dumb.cmo bft.ml -cclib -lcamlidl
> camlprim0.c
> libcamlidl.lib(idlalloc.obj) : error LNK2001: unresolved external symbol
> __imp__CoTaskMemAlloc@4
> libcamlidl.lib(idlalloc.obj) : error LNK2001: unresolved external symbol
> __imp__CoTaskMemFree@4
> bftest.exe : fatal error LNK1120: 2 unresolved externals
> Error while building custom runtime system
You need to link ole32.lib and oleaut32.lib into resulting executable.
> This happens both at a DOS prompt and under Cygwin (using the
> Native Win32 port, not one compiled from source under Cygwin). When I
> perform the same steps under my OS X installation, everything works
> fine.
Yes, camlild runtime library uses COM only under Windows.
Hope to hear from you soon,
Dmitry
-------------------
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
prev parent reply other threads:[~2002-03-21 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 21:05 William D. Neumann
2002-03-21 12:19 ` Dmitry Bely [this message]
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=y9gmglk1.fsf@mail.ru \
--to=dbely@mail.ru \
--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