-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'package.cache' conflict with multiple haskell_library deps #7
Comments
I guess the problem is even simpler: having two haskell_library(
name = "a",
srcs = ["A.hs"],
)
haskell_library(
name = "b",
srcs = ["B.hs"],
) |
Interesting, I wonder if they share directories so it's counting it as same output… Thanks for reporting, it's very much WIP. |
Fuuzetsu
pushed a commit
that referenced
this issue
Nov 29, 2017
This no longer fails at analysis time but it fails at build-time: seems the two libraries are sharing build directory and it breaks things in a nasty way (bazel NPE).
Fuuzetsu
pushed a commit
that referenced
this issue
Nov 29, 2017
We suffix all the build directories and files that we make with a package name and version. As package name is a target name, there can only be a unique one in single project and we preserve some sanity in build environment, at least for the directories we declare and pass around. This allows multiple `haskell_library` and `haskell_binary` targets in a single package. Closes #7.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Take the following example BUILD file from https://github.com/jin/bazel_haskell_example:
This throws an error:
The text was updated successfully, but these errors were encountered: