From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: exn-source - exception backtraces with source code printing
Date: Mon, 20 Oct 2014 21:28:32 +0300 [thread overview]
Message-ID: <54455450.7080508@etorok.net> (raw)
In-Reply-To: <5444FCD9.2090704@inria.fr>
On 10/20/2014 03:15 PM, Francois Berenger wrote:
> On 10/20/2014 02:06 PM, Peter Zotov wrote:
>> On 2014-10-20 15:52, John Whitington wrote:
>>> Noted. I'd like to add functionality like this. The first thing I'm
>>> going to add is automatic finding of the stdlib, since this just
>>> requires parsing the output of "ocamlc -config".
>>
>> I would take this directly from OCaml configuration (module Config,
>> -package compiler-libs.common). No shelling out needed.
>>
>>> Unfortunately, I don't believe most OPAM packages install their
>>> source, just the .mli files. I wonder how much extra space installing
>>> source would take on average, and if people think it's worth it, for
>>> this or other reasons.
Other reasons for wanting things from the build directory are 'cmt/cmti' files for merlin/ocamlspot/ocp-index (or their equivalent file that only stores documentation used by opam-doc).
Do these require the original source files to extract&format the documentation strings?
>>
>> I think it's mainly due to lack of infrastructure that could install
>> sources (eg OASIS couldn't easily be coerced into doing that). You could
>> probably make opam do the grunt work for you; no need to have the sources
>> installed in the same places as mli or binaries!
>
> Isn't opam -b or --keep-build-dir supposed to keep the sources?
>
It does, but it also requires more disk space by keeping all the binaries and intermediate files around.
Perhaps this tool could be extended to install the source files too, or something equivalent provided at the opam level:
https://bitbucket.org/camlspotter/spotinstall
Then you wouldn't need to modify the build system of every package to install its sources / its documentation /its annotation files.
Best regards,
--Edwin
next prev parent reply other threads:[~2014-10-20 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:03 John Whitington
2014-10-19 18:26 ` Gabriel Scherer
2014-10-19 18:55 ` John Whitington
2014-10-19 19:05 ` Gabriel Scherer
[not found] ` <54441347.904@coherentgraphics.co.uk>
2014-10-19 19:50 ` Gabriel Scherer
2014-10-20 9:15 ` Nicolas Boulay
2014-10-20 9:35 ` Peter Zotov
2014-10-20 11:52 ` John Whitington
2014-10-20 12:06 ` Peter Zotov
2014-10-20 12:15 ` Francois Berenger
2014-10-20 18:28 ` Török Edwin [this message]
2014-10-23 8:32 ` John Whitington
2014-10-23 11:48 ` Sébastien Hinderer
2014-10-23 16:43 ` Gabriel Scherer
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=54455450.7080508@etorok.net \
--to=edwin+ml-ocaml@etorok.net \
--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