yano
2016-11-15 05:01:50 UTC
Hi all,
experimenting with the CMakeLists approach. It seems that the current CMakeLists.txt is designed to build/package/install SDL. Great, it seems to basically work, but the whole package config thing is a bit annoying on non-linux systems. I'm trying to build my project for Android, iOS, Mac, and Windows via CMake, and most libraries expose a normal library through their CMakeLists.txt, so for example, I can just do
Code:
target_link_libraries(MyAwesomeGame PUBLIC SDL2)
and that takes care of linking and headers, etc... However when I do this for SDL2, it tells me it can't find the include path, since its trying to reference the installed location rather than the build location, or maybe its not doing anything, hard to tell.
My question is, am I missing something? Or should I work on this functionality for a pull request?
Since we're on the topic, how do you do a pull request in mercurial? TIA
[/code]
experimenting with the CMakeLists approach. It seems that the current CMakeLists.txt is designed to build/package/install SDL. Great, it seems to basically work, but the whole package config thing is a bit annoying on non-linux systems. I'm trying to build my project for Android, iOS, Mac, and Windows via CMake, and most libraries expose a normal library through their CMakeLists.txt, so for example, I can just do
Code:
target_link_libraries(MyAwesomeGame PUBLIC SDL2)
and that takes care of linking and headers, etc... However when I do this for SDL2, it tells me it can't find the include path, since its trying to reference the installed location rather than the build location, or maybe its not doing anything, hard to tell.
My question is, am I missing something? Or should I work on this functionality for a pull request?
Since we're on the topic, how do you do a pull request in mercurial? TIA
[/code]