We already install a raylib.pc file for pkg-config, but we probably should also install a raylib-config.cmake, so dependent CMake projects can use it.
Documentation: https://cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-packages
Could it be raylibConfig.cmake for library naming consistency? Or the requirement for that kind of file is starting with capital letter?
It's a convention, but CMake also accepts raylib-config.cmake.
ok, I prefer this option, I always name files in lower-case convention...
The CMakeLists.txt in examples/ and games/ have the build/ directory hardcoded, which kinda defeats the purpose of doing out-of-tree builds. That should probably be fixed too...
The link_libraries_to_executable function in cmake/utils.cmake is a hack that should be got rid off as well.
@a3f what's the state of this issue? could it be closed?
We don't yet provide a raylib-config.cmake. I would leave this issue open till someone implements it...
On Fri, Jul 13, 2018 at 1:05 PM, Ray notifications@github.com wrote:
@a3f https://github.com/a3f what's the state of this issue? could it be
closed?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/raysan5/raylib/issues/471#issuecomment-404801859, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE9pkLOWYmnxc5o1OSsACdNQG8NEtwiTks5uGH8HgaJpZM4SI4_4
.
Most helpful comment
The
CMakeLists.txtinexamples/andgames/have thebuild/directory hardcoded, which kinda defeats the purpose of doing out-of-tree builds. That should probably be fixed too...The
link_libraries_to_executablefunction incmake/utils.cmakeis a hack that should be got rid off as well.