-
Notifications
You must be signed in to change notification settings - Fork 208
Error loading a project with build-type: custom
(f.e. cabal-install)
#1638
Comments
Maybe project failed to load? Are hover requests working? |
I restarted vs code (the editor that i'm using) seems that this issue is first stuck on another issue
Or maybe it's the same issue but another manifestation of it. |
there should be a diagnostic in the first line with more infos |
First line where ? |
In the file you load, there should be a diagnostic in the first line. In the logs, you see the full error message, too.
Calling the command |
Error:
Looks that somewhere windows paths are not properly handled |
interesting, could be a cabal bug. Needs more investigating. |
Do you think it's worth to report upstream ? |
Probably, if you can provide a nice way to reproduce the issue. |
I think i launched that command from a mingw shell. When i launch from
|
I will try to load |
build-type: custom
(f.e. cabal-install)
I've just adding:
to a simple, working cabal project and i've got the same error so i am afraid that the error is generic. @fendor could you comfirm that it is reproduced in linux, please? |
workarounds:
|
Can reproduce on linux as well. Adds a component
|
@jneira with which package is the root cause of this? Is it cabal-helper? Would reporting upstream be helpful? I can not use the workaround to drop the custom setup because the project is cabal itself (cloned from github) and i'm sure the cabal developers have their good reasons to do a custom setup. What should go into |
It seems to be an issue with cradle:
cabal:
- path: ./cabal-install
component: "exe:cabal"
- path: ./Cabal
component: "lib:Cabal" |
well, examining the
just @fendor has confimed me that cabal-helper is choosing the targets so it is the appropiate thing to do |
https://github.com/haskell/cabal/blob/ac84fa2f25505ed604769d6fc3f00ecf3933b248/cabal-install/Distribution/Client/ProjectPlanning.hs#L1417
The text was updated successfully, but these errors were encountered: