-
Notifications
You must be signed in to change notification settings - Fork 442
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
Figure out how to bundle 3rd party Find modules #436
Comments
Hi! Installing the extra FindGLFW, FindOpenAL, ... modules system-wide is problematic, because those could cause conflicts with Find modules of other libraries (to my knowledge there's at least five different mutually incompatible Hope this helps :) |
Thanks for the quick response. I thought I was just missing something obvious, thanks! |
Finally, as of mosra/corrade@1eec665, 282f95d, mosra/magnum-plugins@69fe099 and mosra/magnum-integration@73af607 the dependency Find modules get installed alongside Magnum and they're automatically used when finding dependencies. In other words, it's no longer needed for projects to bundle It's also done in a way that shouldn't cause them to clash with modules of the same supplied by other projects -- they get installed into a |
Trying to follow the documentation for when Magnum was externally built and installed and I can't get it to work. Magnum compiles just fine but then it doesn't copy all the FindXXX.cmake files to the install folder. That causes the FindMagnum.cmake to fail when it tries to
find_package(GLFW)
. I think the fix would be to add them to the install as well, but I might be doing something wrong.It warns that it can't find GLFW in this line => https://github.com/mosra/magnum/blob/master/modules/FindMagnum.cmake#L632
and then it fails later when it tries to find
GLFW::GLFW
I believe the fix would be to just add the rest of the find cmakes to https://github.com/mosra/magnum/blob/master/modules/CMakeLists.txt but given that file hasn't been changed for a long time it makes me think that I'm doing something wrong instead
The text was updated successfully, but these errors were encountered: