From: Xavier ALLAMIGEON <xavier.allamigeon@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] static C library of wrappers: compilation issues
Date: Thu, 26 Apr 2012 12:08:08 +0200 [thread overview]
Message-ID: <4F991E88.5060402@inria.fr> (raw)
In-Reply-To: <4F990869.5050105@etorok.net>
Dear Edwin,
Le 26/04/12 10:33, Török Edwin a écrit :
>> Here's the way I'm compiling everything. It builds a libhello_world.a static library from ml_code.obj.o and c_code.o.
>> ocamlc -c ml_code.mli
>> ocamlopt -c ml_code.ml
>> ocamlopt -output-obj ml_code.cmx -o ml_code.obj.o
>> gcc -c c_code.c -I"`ocamlc -where`"
>> ar rcs libhello_world.a ml_code.obj.o c_code.o
>> gcc -o test -L. -L"`ocamlc -where`" test.c -lhello_world -lasmrun -lm -ldl
>
> You need -Wl,--whole-archive -Wl,--no-whole-archive around the link of your .a, like this:
> gcc -o test -L. -L"`ocamlc -where`" test.c -Wl,--whole-archive -lhello_world -Wl,--no-whole-archive -lasmrun -lm -ldl
Thanks a lot, it works now!
> Otherwise the functions from your .a are dropped because nothing else before it needs it (-lasmrun would, but its after your .a).
What do you mean exactly? I imagine that test.o needs some functions of
the libhello_world.a. But I don't see why libasmrun would need some
other functions of libhello_world...
What about the following alternative where libasmrun is directly
appended to the .a file?
cp "`ocamlc -where`"/libasmrun.a libhello_world.a
ar rcs libhello_world.a ml_code.obj.o c_code.o
gcc -o test -L. -L"`ocamlc -where`" test.c -lhello_world -lm -ldl
Best regards.
Xavier
next prev parent reply other threads:[~2012-04-26 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 7:58 Xavier ALLAMIGEON
2012-04-26 8:33 ` Török Edwin
2012-04-26 10:08 ` Xavier ALLAMIGEON [this message]
2012-04-26 12:23 ` Alain Frisch
2012-04-26 14:30 ` Xavier ALLAMIGEON
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=4F991E88.5060402@inria.fr \
--to=xavier.allamigeon@inria.fr \
--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