From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Anthony Tavener <anthony.tavener@gmail.com>
Cc: "Gabriel Scherer" <gabriel.scherer@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] A way to avoid "WARNING: myocamlbuild.cmi occurs in several directories"?
Date: Fri, 13 Dec 2013 01:12:58 +0100 [thread overview]
Message-ID: <3029652948434D5A8C48531553154776@erratique.ch> (raw)
In-Reply-To: <CAN=ouMR_zwszt-Sg8WFC=_g=_onykpfGLUVSt7xYQLfmg707uw@mail.gmail.com>
Le vendredi, 13 décembre 2013 à 00:57, Anthony Tavener a écrit :
> I regularly develop libraries in parallel with application code.
Since you seem to be using ocamlbuild, at a certain point I was using (and still use sometimes) a workflow that I described here:
http://brion.inria.fr/gallium/index.php/Working_on_dependent_projects_with_ocamlbuild
If you work with version control you could also make local git package for the libs. That way you can update your all your libraries after new commits with a single `opam update && opam upgrade`.
Best,
Daniel
next prev parent reply other threads:[~2013-12-13 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 21:47 Anthony Tavener
2013-12-12 22:33 ` Gabriel Scherer
2013-12-12 23:57 ` Anthony Tavener
2013-12-13 0:12 ` Daniel Bünzli [this message]
2013-12-13 3:34 ` Stephen Magill
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=3029652948434D5A8C48531553154776@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=anthony.tavener@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
/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).