-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Teach our Azure Pipeline to build and test also using MSVC #2098
Comments
This has been sitting awhile in my todo/inbox. Finally got around to trying to get VS2017 installed and this checked (so I can do the #1848 et al 4Gb issue(s,s,s,s) looked at, hopefully with a bit of intellisense... 😉 However I got "invalid numeric argument '/Werror'" for fuzz-commit-graph.o, which I suspect is a new fault in the fuzz code..
I was hoping to get to try out the new VS stuff, but I'm not there yet. |
looks like this is a makefile error in that
where |
the FUZZ_OBJ are defined at https://github.com/git-for-windows/git/blob/master/Makefile#L703-L710 but are then included in the OBJECTS list at https://github.com/git-for-windows/git/blob/master/Makefile#L2314-L2319 so will still need to resolve the MSVC compiler flags problem (eventually). Eventually just went with
so still steps to go. |
Let's close this in favor of #2148 |
Yeah, I forgot to take care of
No, it needs to be compiled in...
I addressed that as part of the commit that adds support for |
We are very close to contributing Git for Windows' MSVC patches to the Git mailing list (gitgitgadget#149), and we should really have a test first, to make sure that we got it right, and also to keep it working once it is in core Git's
master
.To that end, I already added a job that builds the vcpkg dependencies and offers them as a build artifact (no sense trying to rebuild those dependencies every single time we want to build & test Git...): https://dev.azure.com/git/git/_build?definitionId=9
The text was updated successfully, but these errors were encountered: