From: "William D. Neumann" <wneumann@cs.unm.edu>
To: Shivkumar Chandrasekaran <shiv@ece.ucsb.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlbuild and C stubs
Date: Wed, 7 Mar 2007 15:03:23 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.62.0703071445510.23302@io.cs.unm.edu> (raw)
In-Reply-To: <C0EA3AF9-8F12-4182-99E8-856488E931AA@ece.ucsb.edu>
On Wed, 7 Mar 2007, Shivkumar Chandrasekaran wrote:
> Is there any (easy) way to use ocamlbuild to handle the automatic
> (re)-compilation of the C stub files to external libraries? Thanks,
Well, I don't know if it's the best way (I wait for Nicolas to chime in),
but while playing around with it I tried to get cryptokit to build with
ocamlbuild. What I ended up with that worked was a myocamlbuild.ml that
looks like:
open Ocamlbuild_plugin
open Command
open Arch
let static = false
let zlib = "-DHAVE_ZLIB"
let zlib_lib="-lz"
let zlib_libdir="/usr/lib"
(* let zlib_libdir=/usr/lib64 (* for x86-64 Linux *) *)
let zlib_include="/usr/include"
let libname = "cryptokit"
let cc_map lst = List.fold_right (fun v b -> A"-ccopt"::(A v)::b) lst []
let l_ x = "-L"^x
let _a = "%.a"
let c_files =
[ "rijndael-alg-fst"; "stubs-aes"
; "d3des"; "stubs-des"
; "arcfour"; "stubs-arcfour"
; "sha1"; "stubs-sha1"
; "sha2"; "stubs-sha2"
; "sha256"; "stubs-sha256"
; "ripemd160"; "stubs-ripemd160"
; "pool"; "stubs-pool"
; "stubs-md5" ; "stubs-zlib"; "stubs-misc"; "stubs-rng"
]
let c_objs = List.map (fun f -> f-.-"o") c_files
let _ = dispatch begin function
| Before_rules ->
rule "create C library rule"
~prod:_a
~deps:c_objs
begin fun env build ->
let a = env _a in
let tags = tags_of_pathname a++"library"++"object"++"archive" in
Cmd(S([ !Options.ocamlmklib; A"-o"; A libname ]
@ (List.map (fun o -> A o) c_objs) @
[ A(l_ zlib_libdir); A zlib_lib; T tags ]
)
)
end;
flag [ "c"; "compile"; ] (S(A"-I"::P".."::(cc_map [("-I"^zlib_include); zlib])));
flag [ "library"; "ocaml" ] (S[A"-ccopt"; A(l_ zlib_libdir); A"-cclib"; A zlib_lib]);
flag [ "ocaml"; "program" ] (S[A"-ccopt"; A"-L."]);
if static then flag [ "byte"; "link" ] (A"-custom");
flag [ "byte"; "library"; "link" ] (S[A"-dllib"; A"-lcryptokit"; A"-cclib"; A"-lcryptokit"]);
flag [ "native"; "library"; "link" ] (S[A"-cclib"; A"-lcryptokit"]);
| _ -> ()
end
The main thing here being the rule to build the C library. I then use an
itarget file to build the library. This contains
libcryptokit.a
cryptokit.cma
cryptokit.cmxa
Now, to build the library, I just issue the command
ocamlbuild libcryptokit.otarget
And then to build, for example, the test program I use something like
ocamlbuild test.native -libs nums,unix,cryptokit
I'm sure there's a bunch of cruft in there that could be better handled,
but it seems to work well for now.
William D. Neumann
---
"There's just so many extra children, we could just feed the
children to these tigers. We don't need them, we're not doing
anything with them.
Tigers are noble and sleek; children are loud and messy."
-- Neko Case
Life is unfair. Kill yourself or get over it.
-- Black Box Recorder
next prev parent reply other threads:[~2007-03-07 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 21:07 Shivkumar Chandrasekaran
2007-03-07 22:03 ` William D. Neumann [this message]
2007-03-08 12:22 ` [Caml-list] " Nicolas Pouillard
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=Pine.LNX.4.62.0703071445510.23302@io.cs.unm.edu \
--to=wneumann@cs.unm.edu \
--cc=caml-list@inria.fr \
--cc=shiv@ece.ucsb.edu \
/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