You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Require cabal.project packages and/or optional-packages field
Currently, if a cabal.project file is present and the `packages` and
`optional-packages` fields do not exist, a warning will be issued, and
cabal will fail with a different, potentially misleading error message:
"There is no <pkgname>.cabal package file or cabal.project file..."
This changes it so that the prior warning is now an error, hence will
cause cabal to fail before the misleading error is given. That at least
one of these fields is required is already specified in the docs, hence
this is not a specification change.
See #7401.
There is no <pkgname>.cabal package file or cabal.project file. To build packages locally you need at minimum a <pkgname>.cabal file. You can use 'cabal init' to create one.
4
+
5
+
For non-trivial projects you will also want a cabal.project file in the root directory of your project. This file lists the packages in your project and all other build configuration. See the Cabal user guide for full details.
6
+
7
+
# cabal v2-build
8
+
Error: [Cabal-7136]
9
+
There is no <pkgname>.cabal package file or cabal.project file. To build packages locally you need at minimum a <pkgname>.cabal file. You can use 'cabal init' to create one.
10
+
11
+
For non-trivial projects you will also want a cabal.project file in the root directory of your project. This file lists the packages in your project and all other build configuration. See the Cabal user guide for full details.
0 commit comments