-
When I install the MLX42 from a sub-module it's really conveniently installs glfw it it's not installed already. That means that I could to it in my Makefile so I don't depend on system install. My Problem is that it glfw is already installed somewhere, then it doesn't download it again, so my Makefile is already looking for a non existing directory. In our Campus (42Heilbronn) we don't have glfw installed by default, so we need to install it with brew and it's location is in non standard places depending on the install. So for me it would be really convenient if I could give CMake an option to always make glfw, so that in turn I don't need to hunt for it's specific location on other MAC-s. PS: I hope that this ramble makes sense and thanks for you're work on the library it's a pleasure to use and the CMake version is easier to set up than ever. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
You could try and compile it with My real suggestion would be to tell your sysadmin to install it. CMake and GLFW are useful for advanced (specialization projects) later on anyway so why not include it? |
Beta Was this translation helpful? Give feedback.
You could try and compile it with
cmake -B build -Dglfw_FOUND=0
if you want it to build and always download GLFW. Tho it might not work. You could create a fork and then modify theCMakeLists.txt
and remove the if statement andfind_package
statement. That way it will clone and build it.My real suggestion would be to tell your sysadmin to install it. CMake and GLFW are useful for advanced (specialization projects) later on anyway so why not include it?
If you're on MacOS he/she can ask for the Munki files I suppose.