-
Notifications
You must be signed in to change notification settings - Fork 237
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
Build not picking up external libraries #674
Comments
You will need to open a PR like #669, I'm afraid I don't know which nix package provides the vulkan-headers. You'll essentially need to provide haskell.nix with a mapping of the library name to the corresponding nix pkg that provides the data. If the extra-libraries name matches the package name in nix, it will work automatically, if not, we need a mapping. |
The package name in nix is |
I think the problem is that http://hackage.haskell.org/package/VulkanMemoryAllocator-0.3.2/VulkanMemoryAllocator.cabal doesn't declare any dependency on a |
It's a little weird, In |
Cabal lets you state |
I tried forking it and adding that to the cabal file but it says no vulkan-headers found. Fork of vulkan: https://github.com/locallycompact/vulkan/blob/master/VulkanMemoryAllocator/VulkanMemoryAllocator.cabal#L62 |
Sorry, suggesting pkg-config was not the right thing to do, as vulkan-headers doesn't have any pkg-config information associated The important question to answer is: how are non-library build time dependencies supposed to be specified? |
I think the correct way is to use
Doing that cabal finds vulkan header. |
It surprises me that there is no equivalent of Strictly speaking: VulkanMemoryAllocator doesn't depend on Additionally I'm open to any change to the Haskell VMA package as long as it doesn't impact compilation on other OSs or with the nixpkgs Haskell infrastructure. In particular compilation with stack on Windows is quite fragile as the mingw vulkan-loader installed by stack doesn't work and mustn't be linked against. I'm not sure if a pkgconfig dependency would cause that to be linked instead of (or in addition to) the library installed by the SDK; of course this isn't haskell.nix's concern, but might be useful to anyone looking to change things on the package side. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, I'm trying to get the result of
stack-to-nix
to build the vulkan libraries but it does not seem to be able to pick it up. I have in package.yamlwhich seems to generate
but I still get a build error that is package not found.
Source: https://gitlab.com/shakebook-site/shakebook-site.gitlab.io/-/tree/staging/vulkan
Error: https://gitlab.com/shakebook-site/shakebook-site.gitlab.io/-/jobs/591709328
The text was updated successfully, but these errors were encountered: