Matthieu Dubuget a écrit :
Correction:
Matthieu Dubuget a écrit :
Thanks to Nicolas: the solution was:
- tag .oocamlfind files with dont_link_with
In fact, tagging .oocamlfind files is not needed.
The key point is to add dont_link_with when calling dep:
dep
Correction:
Matthieu Dubuget a écrit :
Thanks to Nicolas: the solution was:
- tag .oocamlfind files with dont_link_with
In fact, tagging .oocamlfind files is not needed.
The key point is to add dont_link_with when calling dep:
- and add dont_link_with in left part of dep:
dep
Excerpts from Matthieu Dubuget's message of Wed Feb 11 23:26:43 +0100 2009:
Hello,
I'm trying to manage internal camlfind packages. I use internal with
the same meanning than in ocamlbuild documentation when speaking about
libraries.
I want my camlfind packages to be re-installed if one
Matthieu Dubuget a écrit :
Nicolas Pouillard a écrit :
Excerpts from Matthieu Dubuget's message of Wed Feb 11 23:26:43 +0100 2009:
Hello,
I'm trying to manage internal camlfind packages. I use internal with
the same meanning than in ocamlbuild documentation when speaking about
Hello,
I'm trying to manage internal camlfind packages. I use internal with
the same meanning than in ocamlbuild documentation when speaking about
libraries.
I want my camlfind packages to be re-installed if one of their
dependency was modified. For this, I wrote a simple rule, based on
Hi everyone,
I'm trying to write a OCamlBuild plug-in to automatically generate
the .mli corresponding to a .mlpack (for documentation purposes).
I've written a [rule] which lets me depend a .mli on the
corresponding .mlpack . From this .mlpack, I can obtain the list of
modules involved
