HLS fails on complex project

[k355l3r-5yndr0m3]

I have a project that I am working on that is quite complex. The build-type is custom, and Setup.hs uses the autoconfUserhooks so it also generate a .buildinfo file.
The configure build-type could not be used because I uses Setup.hs to generate the project's autogen modules.
There are two issues. The auto generated modules are not created and must be manually copied from dist-newstyle to the corresponding directory in hie-bios, and the buildinfo file appears to be ignored.
The project builds fine, but hls cannot be used.

[fendor]

Hi, thank you for your bug report!

Does cabal repl succeed in your project?

Can you reduce your project to a minimal reproducer and post it, so we can have a look at it?

[k355l3r-5yndr0m3]

minimal.zip
The configure script generate a buildinfo file with the buildable flag set to false, yet hls is not aware of this. Adding buildable: False to the .cabal file produces the correct behavior. This apply to other flags too.
The Setup script create a module called Autogen, which hls cannot locate.

[fendor]

I am not sure if we can help with the configure script, I don't know enough about Cabal to know what's going on here.

What behaviour would you expect?

Re the Setup.hs, iirc, preBuildHook is only run if you execute cabal build. However, HLS calls cabal repl to find the compilation options. If you manage to generate the module also on cabal repl, perhaps via the preReplHook, that could work.

[k355l3r-5yndr0m3]

Generating the modules at preRepl does solve the autogenerated module issue.
As for the configure script issue, I use it to resolve the include paths and library paths. My project deals with a lot of C code. I've been adding the paths specific to my system to the cabal file as a workaround.
cabal build run without error, but cabal repl fails because it could not find the header files.

[michaelpj]

As Fendor says, we rely on cabal repl to find the build flags. If cabal repl doesn't work, HLS won't work. I'm not sure how to make cabal repl work for your project, but that's more of a cabal issue than a HLS issue.

[michaelpj]

Meta-issue: ideally if someone gets a cradle failure it would be very clear that we ran cabal repl and that we need to do that in order to get the build flags, and they should try and fix it if it's broken.

[AleXoundOS]

cabal build run without error, but cabal repl fails

This seems to be a cabal issue. I face the same issue with cabal 3.10.1.0.

1. `build-type: Configure`
2. `configure` script generates `PROJ.buildinfo` file with `cpp-options: -DMYDEF=1` contents
3. haskell code uses `CPP` extension to access `MYDEF`
4. `cabal build` successfully builds the project
5. `cabal repl` fails with `Data constructor not in scope` for `MYDEF`

[michaelpj]

Closing as mostly-expected