Open guygastineau opened 2 years ago
The cabal file was originally created from a stack.yaml
, but I am migrating away from stack. Still, it is a small file, and I believe I understand most of it. I don't think my cabal file is setting the haste
flag in any way.
Well, I got it building. I had to pass --constraint "selda-sqlite -haste"
to cabal build all
to get it to build. I don't know why setting it universally didn't work, but anyway it seems somehow one of my other dependencies was setting the haste flag to true. I don't know how this would happen, and I expected cabal wouldn't let such a thing happen. I will comb my deps to try finding the offending package. Maybe I should open an issue with cabal if I can find the problem.
As the above indicates, I have at least a workaround for now, and the issue was never selda-sqlite
's fault. If the maintainers would like I don't mind leaving this up until I resolve how it happens (perhaps with patches to cabal) in case someone else encounters this anomaly, but I will take no offense at closing it now, since the issue is not with your code. thank you.
Same here with selda-postgresql
. I have to use
cabal build --constraint "selda-postgresql -haste"
I have used the sqlite backend with stack before, but know I am using cabal for a different project. It complains that the guarded packages are not available, but I am not using Haste.
I am using cabal version 3.6.0.0 Here is my cabal file:
Here is the error I get when compiling.
I have poked around messing with flags to try fixing this, but I feel pretty stumped. The default value of the
haste
flag is set tofalse
in theselda-sqlite.cabal
c file, so I really don't know why this is happening. For cmpleteness here are the contents of mycabal.project
packages: ./
I really appreciate any help.