caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christophe Troestler <Christophe.Troestler@umons.ac.be>
To: Olaf Hering <olaf@aepfle.de>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] OASIS help: link stublib to system lib and another caml lib
Date: Sat, 28 May 2016 01:22:02 +0200	[thread overview]
Message-ID: <87h9djf5np.fsf@poincare3.umons.ac.be> (raw)
In-Reply-To: <20160527081429.GA18793@gmail.com>


On 2016-05-27, Olaf Hering wrote:
> 
> On Thu, May 26, Christophe Troestler wrote:
> 
> > "-lfuse" is needed because it is the library you bind to but
> > "-L/usr/lib64/ocaml -lcamlidl" should be handled by "camlidl" 
> > (specifically
> > by `ocamlfind query camlidl`/com.cma).
> 
> Are you saying that something should automatically generate and pass 
> the
> -L option to the compiler with the provided _oasis file? For me 
> nothing
> like that happens if I add just '-lfuse -lcamlidl' to CcOpt:
> execve("/usr/bin/gcc", ["gcc", "-shared", "-o", 
> "lib/dllFuse_stubs.so",
> "lib/Fuse_util.o", "lib/Unix_util_stubs.o", 
> "lib/Fuse_bindings_stubs.o",
> "-lfuse", "-lcamlidl"]
> 
> For the time being my workaround is to use '-L/usr/lib64/ocaml 
> -L/usr/lib/ocaml' which appearently fixes 32 and 64bit builds.
> 
> To me it looks like "OCamlbuild additional flags:" needs to be set. 
> Is there a way to pass this via 'ocaml setup.ml -configure'?

You wan only pass static options via _oasis.  If you can get the path to 
camlidl — which the camlidl library should provide, try "ocamlfind query 
camlidl" — then you can use the trick below to pass it to ocamlbuild and 
set appropriate flags.

> > https://github.com/Chris00/ocaml-odepack/blob/master/setup.ml#L68
> 
> I think thats a very bad advice. Are you suggesting to ignore the 'DO 
> NOT EDIT' of each generated setup.ml? Being able to regenerate the 
> files required for building from scratch is essential.

The edits are *outside* the OASIS section so are preserved upon 
regeneration — this is the purpose of the delimiters, this not bad 
advice at all! :-)

Best,
C.

  reply	other threads:[~2016-05-27 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 20:11 Olaf Hering
2016-05-26 20:58 ` Christophe Troestler
2016-05-27  8:14   ` Olaf Hering
2016-05-27 23:22     ` Christophe Troestler [this message]
2016-06-01 16:25       ` Olaf Hering

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=87h9djf5np.fsf@poincare3.umons.ac.be \
    --to=christophe.troestler@umons.ac.be \
    --cc=caml-list@inria.fr \
    --cc=olaf@aepfle.de \
    /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).