| Summary: | MacOS - sdl2-config.cmake is missing and if you ./configure it got the wrong path | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Anders Nauman <anders.nauman> |
| Component: | build | Assignee: | Sam Lantinga <slouken> |
| Status: | NEW --- | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | CC: | foo.null, leonardo.guilherme |
| Version: | 2.0.8 | ||
| Hardware: | x86_64 | ||
| OS: | macOS 10.13 | ||
| See Also: | https://bugzilla.libsdl.org/show_bug.cgi?id=4597 | ||
|
Description
Anders Nauman
2018-08-11 13:12:43 UTC
Hey, I have created bug 5497 that tries to partially addresses your issue, it incorporate features of FindSDL2.cmake into sdl2-config.cmake. Would you mind trying replacing the current sdl2-config.cmake with it and reporting back if it works? As for the .dmg having the sdl2-config.cmake bundled in, I suppose this is not an CMake issue but how the dmg was created, which I don't know yet how to fix. cmake is probably doing the "right" thing by assuming SDL headers are where autoconf installed to. The dmg path ought to be treated as a different path. Also anyone familiar with macOS development ought to know that copying frameworks to /Library/ or other global path is bad advice, because frameworks have to be copied/bundled inside app bundles and having frameworks there may create false sense of working-ness. The dmg path should be "copy SDL.framework into your project", link it, bundle it in your app. Common workflow. |