Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: hmf <hmf@inescporto.pt>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild missing links: using a bash script
Date: Wed, 21 Nov 2007 12:19:44 +0100	[thread overview]
Message-ID: <1195643622-sup-4152@port-ext2.ensta.fr> (raw)
In-Reply-To: <47440DEA.9060104@inescporto.pt>

Excerpts from hmf's message of Wed Nov 21 11:52:26 +0100 2007:
> Hello,
> 
> I have a very simple bash script that I use to
> build my project using ocamlbuild. The idea is
> to build modules successively and execute tests
> until compilation fails, a test fails or all
> modules are correctly compiled.
> 
> It goes something like this:
> .................................................
> #!/bin/bash
> 
> # Exit on error
> set -e
> 
> ocamlbuild src/comb/tests_comb.d.byte --
> 
> ocamlbuild -lib unix src/uf/bench.d.byte --
> .................................................
> 
> I have noticed however that the build (if
> successful) only retains the last symbolic
> link to the compiled artefacts.
> 
> My questions are:
> 
> 1. Is the above behaviour intended?

Yes, links made by ocamlbuild are made each time.

> 2. If so how can I keep all resulting links

If you ask for multiple programs you will get multiple links.

ocamlbuild -lib unix src/comb/tests_comb.d.byte src/uf/bench.d.byte

However it doesn't work in combination with running the given command (using '--').

The  second  option  is  to  forget about this (mis-)feature of links. And use
binaries from the _build dir.

-- 
Nicolas Pouillard aka Ertai


      reply	other threads:[~2007-11-21 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 10:52 Hugo Ferreira
2007-11-21 11:19 ` Nicolas Pouillard [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=1195643622-sup-4152@port-ext2.ensta.fr \
    --to=nicolas.pouillard@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=hmf@inescporto.pt \
    /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