From: Florian Hars <florian@hars.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Linking camlidl stub code
Date: Mon, 19 Aug 2002 17:58:06 +0200 [thread overview]
Message-ID: <3D61158E.70001@hars.de> (raw)
In-Reply-To: <3D5CA644.4000801@hars.de>
Florian Hars wrote:
> My remainig problem is how to link my programs with the generated stub
> code.
To answer my own questions:
Don't trust OcamlMakefile (at lest not the version from march 2001) to handle
all the IDL stuff.
If I compile all my C stub code files (the libfoo library I want to interface
to has several related, but technically independent subsets of its API which I
want to put in different modules) and put them into a libfoostubs.a, I can then
compile the Ocaml side of then stub code with
-cclib foostubs -cclib foo -cclib camlidl
into a cm(x)a, and things work. Phew....
Yours, Florian.
-------------------
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-08-19 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 7:14 Florian Hars
2002-08-19 15:58 ` Florian Hars [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=3D61158E.70001@hars.de \
--to=florian@hars.de \
--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).