From: Xavier Clerc <xavier.clerc@inria.fr>
To: Francois Berenger <berenger@riken.jp>, caml-list <caml-list@inria.fr>
Cc: xavier clerc <xavier.clerc@inria.fr>
Subject: Re: [Caml-list] ocamlbuild generates .annot files in _build
Date: Tue, 17 Jul 2012 09:31:30 +0200 (CEST) [thread overview]
Message-ID: <1354601606.12118372.1342510290266.JavaMail.root@inria.fr> (raw)
In-Reply-To: <50051320.4020303@riken.jp>
----- Mail original -----
> On 07/17/2012 03:55 PM, Xavier Clerc wrote:
> >
> >
> > ----- Mail original -----
> >> Hello,
> >>
> >> Shouldn't it generate theses files where the source files
> >> are?
> >>
> >> The emacs plugin can no more find the types in case
> >> the .annot files are not where the source file is.
> >
> > For the record, we already have a PR related to this problem:
> > http://caml.inria.fr/mantis/view.php?id=5226
> >
> >
> > As you can see there, we have not reached consensus about
> > what to do. However, following the ocamlbuild philosophy
> > of leaving the source directories untouched
>
> ocamlbuild already creates symbolic links to the created executables.
> Maybe links to the .annot files could be created as well.
Yes, this is perfectly right, and also already discussed
in the aforementioned PR. However, such links are scarce
while links to annot files (or annot files themselves, for
the matter) would really clutter the source directories.
At least, it is how I see things, but I am very interested
to gather input on the subject in order to reach consensus
on how to settle the issue.
Regards,
Xavier
next prev parent reply other threads:[~2012-07-17 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 5:12 Francois Berenger
2012-07-17 5:25 ` Francois Berenger
2012-07-17 7:00 ` Xavier Clerc
2012-07-17 7:35 ` Francois Berenger
2012-07-17 14:46 ` Romain Bardou
2012-07-17 6:55 ` Xavier Clerc
2012-07-17 7:24 ` Francois Berenger
2012-07-17 7:27 ` Francois Berenger
2012-07-17 7:31 ` Xavier Clerc [this message]
2012-07-17 14:28 ` Romain Bardou
2012-07-17 8:49 ` Anil Madhavapeddy
2012-07-17 11:05 ` Daniel Bünzli
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=1354601606.12118372.1342510290266.JavaMail.root@inria.fr \
--to=xavier.clerc@inria.fr \
--cc=berenger@riken.jp \
--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).