From: "Ashish Agarwal" <agarwal1975@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlbuild's symlink behavior
Date: Mon, 3 Mar 2008 20:26:33 -0500 [thread overview]
Message-ID: <d8be5ae20803031726s4602c446la02a8e2eebc7c4e2@mail.gmail.com> (raw)
In-Reply-To: <20080303180449.GA16119@stratocaster.home>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
It is probably better to refer to the executables under _build in external
scripts.
On Mon, Mar 3, 2008 at 1:04 PM, Eric Cooper <ecc@cmu.edu> wrote:
> Ocamlbuild seems to create a symbolic link into the _build directory
> when you build a single target. But it removes that symlink if you
> build a different target, and it doesn't produce any symlinks if you
> build a *.otarget.
>
> Is there any rationale for this? It makes it difficult to use the
> resulting symlinks in any kind of build script.
>
> --
> Eric Cooper e c c @ c m u . e d u
>
[-- Attachment #2: Type: text/html, Size: 693 bytes --]
next prev parent reply other threads:[~2008-03-04 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 18:04 Eric Cooper
2008-03-04 1:26 ` Ashish Agarwal [this message]
2008-03-04 9:00 ` [Caml-list] " Nicolas Pouillard
2008-03-04 9:36 ` Berke Durak
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=d8be5ae20803031726s4602c446la02a8e2eebc7c4e2@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).