-
Notifications
You must be signed in to change notification settings - Fork 701
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
Q:
how does cabal build
choose/ find the package nodes
#8481
Comments
Thank you very much, as you suggested, I will also include my reproducer, in this case, of course, only the cabal files are interesting. |
One thing to note is that from an outside perspective, the respective |
You need to provide more details with the reproducer. What is the command given, the actual, and the expected behavior? |
Hi @gbaz, in the reproducer, the |
@MangoIV: I'm afraid, the question you ask very few living persons know the answer to or are able to code-dive and fish out. If you'd live to code-dive on your own, however, and diary the attempt here, I hope we'd be able to help and we'd all learn from the experience. |
@MangoIV I'm pretty sure this is #6039 (comment) (see #5660 for the general status of multiple public libraries). You can confirm by trying to build with bare Cabal, that should work. |
I was wondering what exactly cabal looks at to decide which packages to include when trying to build a packages dependencies. (In particular I'm trying to find out what configuration could cabal cause to not include a sublib into a build although its
*.conf
file and the actual package is provided to the environment)The text was updated successfully, but these errors were encountered: