|Anonymous | Login | Signup for a new account||2018-06-19 14:55 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007808||OCaml||toplevel||public||2018-06-14 11:41||2018-06-15 12:48|
|Target Version||Fixed in Version|
|Summary||0007808: Add an OCAML_TOPLEVEL_PATH variable to ocaml|
|Description||In the new world of opam and its system and non-system switches allowing both: |
# #use "topfind"
to work correctly has proven to be a dire source of hacks and workarounds (I can provide full details if one needs to be convinced).
It turns out that letting the `ocaml` binary be affected by an OCAML_TOPLEVEL_PATH variable, whose semantics would simply be to add the colon separated directories to the includes (#directory include) would allow us to get rid of all of these hacks.
Slightly related to 0007770
|Tags||No tags attached.|
Note that you can already do this today by using OCAMLPARAM, e.g.
will result in <dir1> and <dir2> to be added to the list of include directories.
|Sure but I'd rather not use OCAMLPARAM for that as it affects all the ocaml tools and may be used by switches for other purposes.|
|The request seems sensible to me, but I think that the current name is a bit misleading (to me it says where to find the toplevel binary), I would expect INCLUDE_PATH to be in the name.|
Agreed on the name, I just reused what opam devs initially used. Here are a few candidates
Logic would go for OCAML_INCLUDE_PATH but this could be mistaken as applying to the compilers or one might want to reserve it for that purpose to follow the example of C_INCLUDE_PATH.
Maybe OCAMLTOP_INCLUDE_PATH ?
|2018-06-14 11:41||dbuenzli||New Issue|
|2018-06-14 14:30||nojebar||Note Added: 0019189|
|2018-06-14 14:38||dbuenzli||Note Added: 0019190|
|2018-06-14 16:31||gasche||Note Added: 0019191|
|2018-06-14 16:52||dbuenzli||Note Added: 0019192|
|2018-06-15 12:48||nojebar||Note Added: 0019196|
|Copyright © 2000 - 2011 MantisBT Group|