fendor

No, you can not add entries for both build tools, since hie would then not know what to use! In this repo, we have `hie.yaml.cbl` and `hie.yaml.stack` which you rename...

> Hmm... According to this, HIE should by default (if none of these files is present) use Stack (no ambiguity, no confusion, nothing points at Cabal - therefore use Stack),...

> Is it likely that it would remain so? I dont see a reason why it should, it is an implementation detail. > What would be the impact of this?...

@drewboardman With messages such as `"can't load .so/.DLL for: libgmp.so (libgmp.so: cannot open shared object file: No such file or directory)"`, your problem is probably not related to `hie.yaml`, rather...

@mouse07410 It is currently not supported to open the `Setup.hs` file which is special to the Cabal (not cabal-install, nor stack) build system. That's why it exists in both cabal-install...

You made me look... The error is in the hie.yaml, it should be: ```yaml cradle: multi: - path: ./Setup.hs config: cradle: direct: arguments: - "-package Cabal" - "-package base" -...

Can not reproduce, I did `stack new example`, followed by creating this `hie.yaml`: ```yaml cradle: stack: - path: ./src component: "example:lib" - path: ./test component: "example:test:example-test" ``` and then `hie...

@expipiplus1 Does it happen when you set an explicit component, too? E.g. ```yaml cradle: cabal: component: "lib:hie-reload-example" ```

Probably part of the problem is shown in line: ``` 2020-03-11 10:37:23.385812562 [ThreadId 48] - setTargets: [("/home/j/projects/bugs/reload/src/Foo.hs","/run/user/1000/haskell-lsp17296/Foo.hs-00000--4428135201160501691.hs")] ``` The targets should contain `Bar.hs` EDIT: flags obtained with `hie-bios` look fine:...

Looks like the problem that #1526 aimed to solve.