-
-
Notifications
You must be signed in to change notification settings - Fork 856
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
Use Ninja on AppVeyor #310
Conversation
This brings up improved compilation speed and saner error messages.
How does this represent an improvement over the actual configuration? I don't get it to be honest. |
Ninja's primary use is significantly faster dependency tracking and job handling, it's often quite a bit faster on compiling larger projects than make/nmake/etc... So I think it's just to reduce the build times. In addition it's logs don't get mangled with errors from different threads if there is a failure to build like make/nmake do. |
Does it use VC under the hood? Because the compatibility with MSVC is the whole point of using appveyor. I develop on linux usually, so the CI is what I use for this purpose. |
Yes, ninja is just the build orchestrator, it still uses gcc/clang/visual-studio-tools/icc/whatever. |
As was already stated, ninja is just a tool to invoke compiler. That and (almost) just that, which makes it fast, much faster than msbuild. You can verify what ninja does under the hood by passing Before:
After:
|
Ninja is the best thing's that can happen in your life ;) |
This brings up improved compilation speed and saner error messages.