From: Martin DeMello <martindemello@gmail.com>
To: Adrien <camaradetux@gmail.com>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] include path problem: -I +site-lib/lib not working
Date: Sun, 15 Apr 2012 23:04:27 -0700 [thread overview]
Message-ID: <CAFrFfuEb6wWS19w644swUKEAsX0O6G6eLQWNWmKFoc2Ck2MFmg@mail.gmail.com> (raw)
In-Reply-To: <CAP5QFJkZzbTQfbTSKt7N=m3wT+aNmRMLTubJnKToSoUOnbzQ5Q@mail.gmail.com>
On Wed, Apr 11, 2012 at 12:41 AM, Adrien <camaradetux@gmail.com> wrote:
>
> Nothing is wrong with it. As far as I remember, the "-I +..." syntax is
> relative to the location of the compiler. On my godi install, I get:
> % ocamlc -where
> /opt/ocaml/lib/ocaml/std-lib
>
> As you can see, "std-lib" <> "site-lib" (and same for "pkg-lib"). By the
> way, if I'm not mistaken, on godi, std-lib is for the base ocaml,
> pkg-lib is for what has been installed through godi and site-lib is for
> user-installed packages (and godi has a cryptokit package ;-) ).
Thanks, I realise I hadn't properly understood what -I +... was doing.
I can't use the cryptokit from godi because opa depends on
cryptokit-1.5 and godi ships 1.3.
> The right way to do it is to compile with ocamlfind which will always
> know the right location.
> % ocamlfind query cryptokit
> /opt/ocaml/lib/ocaml/pkg-lib/cryptokit
>
> % ocamlfind ocamlopt -package cryptokit -c ...
Wish I could! It's a pretty big open source project that I'm merely
trying to get compiled so I can use it. I don't have the time to sit
and hack at their build system :( But thanks for the detailed
explanation of why ocamlfind is the way to go; I'll definitely be
using it for all my personal projects.
martin
prev parent reply other threads:[~2012-04-16 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 3:52 Martin DeMello
2012-04-11 7:41 ` Adrien
2012-04-16 6:04 ` Martin DeMello [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=CAFrFfuEb6wWS19w644swUKEAsX0O6G6eLQWNWmKFoc2Ck2MFmg@mail.gmail.com \
--to=martindemello@gmail.com \
--cc=camaradetux@gmail.com \
--cc=caml-list@yquem.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