-
Notifications
You must be signed in to change notification settings - Fork 53
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
Ninja build on Windows #934
Comments
I cannot speak of the https://cmake.org/cmake/help/latest/variable/CMAKE_GENERATOR.html |
Are you sure it’s the build system is the problem and not the compiler? MSVC is very slow. But yes, you can set |
Actually the problem that I have is that I can set the generator to Ninja, but it doesn't find the correct compiler in GitHub actions. Honestly I'd like to use anything other than MSVC because of its many shortcomings, but I guess it is the only way to ensure compatibility with Windows users. I know the Numpy devs are considering using clang-cl instead, but AFAIK they haven't moved over yet for much the same reason. |
You need to setup msvc to get ninja to find it. Something like https://github.com/ilammy/msvc-dev-cmd should work. |
OK that's great, I'll take a look! |
Are there any plans to allow for Ninja builds on Windows? MSBuild is dreadfully slow - A simple package I build takes ~ 100 seconds to build a single wheel on Windows, whilst MacOS finishes all 6 of its builds in 125 seconds.
MSVC does have support for Ninja, and if I remember correctly SciKit-Build did once support Ninja builds on Windows, which as much faster.
What are the obstacles for supporting Ninja with MSVC builds? Can they be added in a vendored scikit-build-core for my larger complex builds?
The text was updated successfully, but these errors were encountered: