I don't think that would be a problem. You can always configure Merlin to read the directory that you want it to read, right?
On Monday, February 29, 2016, Anton Bachin <antronbachin@gmail.com> wrote:
Thanks Arto, Ivan.The question about Merlin is a good one. I better start using Merlinmyself, because I don’t know the answer. I suppose if Merlin readsthings from src/ (or lib/, or whatever) in a project, then it shouldn’twork. But if Merlin reads from _build/, as I would think it does, thenit “should" work. But I don’t know either way at the moment. It willprobably take some time for me to set Merlin up, but I will look intoit.Best,AntonOn Feb 29, 2016, at 12:37, Ivan Gotovchits <ivg@ieee.org> wrote:Hi Anton!It is a great project!But nowadays I always want to know, does it work with merlin?Regards,IvanOn Mon, Feb 29, 2016 at 11:40 AM, Anton Bachin <antronbachin@gmail.com> wrote:Hello,I would like to announce the release of Namespaces, an Ocamlbuild plugin thatgives your project logical nested modules based on its directory layout, as iscommon in the build systems of many other languages.Client.Foo. There is no conflict between the two foo.ml files, and thus no needto call them server_foo.ml and client_foo.ml.The project page and documentation can be found here:Namespaces works, but it abuses Ocamlbuild heavily, so there may be many cornercases that are not yet addressed well. Bug reports are very much welcome. Ifsomething can’t be fixed by changing Namespaces, perhaps Namespaces will be agood point of discussion for updating Ocamlbuild itself, or other OCaml tooling.Regards and enjoy,AntonP.S. How is Ocamlbuild spelled? I have seen it as Ocamlbuild, OCamlbuild (whichstands to reason), and ocamlbuild in monospace font, in the original manual.