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
Original bug ID: 5869 Reporter: meyer Status: resolved (set by @damiendoligez on 2017-03-03T10:39:26Z) Resolution: suspended Priority: normal Severity: feature Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues Monitored by: meyer Camarade_Tux @hcarty
Bug description
Currently ocamlbuild relies on a file system, and is purely a command line tool.
Some tools like Oasis rely on generating a lot of intermediate files for ocamlbuild -- that could be avoided all together if the client tool just called ocamlbuild to give it the same information as in _tags, mllib, mlpack etc. and myocamlbuild plugins.
The client thus would behave like an interpreter not a compiler anymore. This would make the building process less fragile and eliminate many errors originating from file system state.
The text was updated successfully, but these errors were encountered:
Original bug ID: 5869
Reporter: meyer
Status: resolved (set by @damiendoligez on 2017-03-03T10:39:26Z)
Resolution: suspended
Priority: normal
Severity: feature
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Monitored by: meyer Camarade_Tux @hcarty
Bug description
Currently ocamlbuild relies on a file system, and is purely a command line tool.
Some tools like Oasis rely on generating a lot of intermediate files for ocamlbuild -- that could be avoided all together if the client tool just called ocamlbuild to give it the same information as in _tags, mllib, mlpack etc. and myocamlbuild plugins.
The client thus would behave like an interpreter not a compiler anymore. This would make the building process less fragile and eliminate many errors originating from file system state.
The text was updated successfully, but these errors were encountered: