You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to look for plugin or tag files outside the source directory. This is a valid need when those files have been auto-generated (for example by oasis) and the user wants to keep auto-generated files outside the source diretory. This comes from the following caml-list discussion by Magnus Therning:
A slightly more general question is whether the other ocamlbuild-specific files (.mllib, .odocl etc.) could also be located somewhere else. People have been asking for the option to put these in a config file (often in the _tags file, but that does not fit _tags' semantic model) instead of as separate files, and this approach would easily allow to have that config file outside the source directory.
The text was updated successfully, but these errors were encountered:
Original bug ID: 6997
Reporter: @gasche
Status: resolved (set by @damiendoligez on 2017-03-01T10:34:04Z)
Resolution: suspended
Priority: normal
Severity: feature
Target version: later
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Monitored by: @hcarty
Bug description
We should have the command-line options
-config-dir $DIR
-plugin-path /path/to/foo.ml
-tags-file /path/to/_tags
to look for plugin or tag files outside the source directory. This is a valid need when those files have been auto-generated (for example by oasis) and the user wants to keep auto-generated files outside the source diretory. This comes from the following caml-list discussion by Magnus Therning:
https://sympa.inria.fr/sympa/arc/caml-list/2015-09/msg00152.html
Additional information
A slightly more general question is whether the other ocamlbuild-specific files (.mllib, .odocl etc.) could also be located somewhere else. People have been asking for the option to put these in a config file (often in the _tags file, but that does not fit _tags' semantic model) instead of as separate files, and this approach would easily allow to have that config file outside the source directory.
The text was updated successfully, but these errors were encountered: