-
Notifications
You must be signed in to change notification settings - Fork 68
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
Using CMake or some other build system generator #407
Comments
JayFoxRox has (had?) a branch dedicated to accomplishing this goal. Might be a good starting point if you decide to pursue this. As for reasons for not using cmake already, it seems to mostly boil down to personal preference and ease of maintenance. |
This should have been resolved by #518 Closed. |
Hi @JayFoxRox, not sure if you're aware but CMake toolchain in nxdk upstream is nonfunctional. Should be at least fully resolve in #631 |
Okay, however, current state (+ your branch) should be enough to resolve this issue. Users can also check JayFoxRox#84 and JayFoxRox#74 for more options if upstream isn't good enough yet. |
This example helped me use cmake instead of make: https://github.com/Ryzee119/Xenium-Tools/blob/master/CMakeLists.txt Take note of the extra commands needed in the ci workflow: https://github.com/Ryzee119/Xenium-Tools/blob/857464712cbee504098c590c09743edb44dae398/.github/workflows/build.yml#L19-L29 |
Is there a particular reason that CMake (or some other build system generator) was not used for the nxdk? It seems to me that CMake would be a nicer option than make as it would make it easier to use nxdk with an IDE (Visual Studio has support for CMake out of the box) and it allows for integration with CTest which could be nice for some projects. I would be more than willing to try and convert the nxdk to CMake myself, but I don't want to go through the effort if it wouldn't be accepted because there is some reason that make was chosen over CMake.
The text was updated successfully, but these errors were encountered: