Version française
Home     About     Download     Resources     Contact us    
Browse thread
compiling a clib from further away
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Nicolas Pouillard <nicolas.pouillard@g...>
Subject: Re: [Caml-list] compiling a clib from further away
On 6/27/07, Andrew Warshaver <awarshaver@janestcapital.com> wrote:
>
>
> Andrew Warshaver wrote:
> > I am trying to compile a clib (with the eventual hope of it making its
> > way into a compiled ocaml lib).  It is working fine if I am in the
> > specific directory; but if I move too far out it fails.  My directories
> > are like /../janebase/lib/cephes/  The c files live in cephes.
> >
> > $ cat lib/cephes/libjane_stubs.clib
> > bdtr.o
> > btdtr.o
> > chbevl.o
> > ...
> > $ cat _tags
> > <sexp> or <lib>: include
> >
> > $ cat myocamlbuild.ml
> > open Ocamlbuild_plugin
> > open Command
> >
> > let headers = ["lib/cephes/mconf.h"; "lib/cephes/protos.h"];;
> >
> > dispatch begin function
> >   | After_rules ->
> >       dep ["compile"; "c"] headers;
> >   | _ -> ()
> > end
> >
> > $ ocamlbuild lib/cephes/libjane_stubs.a
> > + /usr/local/home/godi310/godi/bin/ocamlmklib -o /cephes/libjane_stubs
>
> by the way, obviously the culprit is in this -o, it should have lib/, is
> this a ocamlbuild bug?
>

Indeed, it seems to be a bug. In order to give the library name
without the "lib" prefix, ocamlbuild cuts the given pathname on the
substring "lib". The bad news is that it's not dummy programming bug,
it's more abou the expressiveness of ocamlbuild rules.

Indeed there are roughly two rules for libs.

... ~prods:["lib%(libname).a"; "dll%(libname).so"] ...

... ~prods:["%(path)/lib%(libname).a"; "%(path)/dll%(libname).so"] ...

And for now I can specify more precise rules. So with your lib/
directory you fall in the first one.

An safe workaround is to rename your lib/ dir.

-- 
Nicolas Pouillard