-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Build with VS2015 #773
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
Build with VS2015 #773
Conversation
----- Original Message ----- This sequence of commits allows git-for-windows to be built using VS2015. It DOES NOT attempt to generate SLN or VCPROJ files. I'd eventually like to merge this effort with: #256 Excellent work Philip You can view, comment on, or merge this pull request online at: Commit Summary |
Rebased onto v.2.9.0.windows.1. |
my $is_linking = 0; | ||
while (@ARGV) { | ||
my $arg = shift @ARGV; | ||
if ("$arg" =~ /^-[DIMGO]/) { | ||
if ("$arg" =~ /^-[DIMGOZ]/) { |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Looks quite good already! I am sure we can whip this into shape now. |
Hey @dscho big thanks for taking a look at this! I'll give it another spin shortly. |
Note to self: See also #49 WRT the environment conversion issue. I added code in my port to MSVC to change how that is handled at startup due to differences in the CRT. |
I rebased this branch (verifying that the OpenSSL SHA-1 patch is no longer necessary) and touched up the commit messages and pushed the result to the I will continue tomorrow, editing the commits as per my suggestions, and hope you may find time some time later this week to look over the branch and maybe rebase your branch? |
The file compat/msvc.c includes compat/mingw.c, which means that we have to recompile compat/msvc.o if compat/mingw.c changes. Signed-off-by: Johannes Schindelin <[email protected]>
Signed-off-by: Jeff Hostetler <[email protected]>
For the record, I've been continuing to work on this branch, and as of an hour ago, it passes the test suite. This required adding the libiconv dependency and a very ugly workaround for the NuPkg's Currently I am testing whether things work just fine without the ugly |
Excellent!!! Thanks for your help on this. |
I just built your branch and commented out the #ifdef's in dscho@ec7f740
For the record, you're right the commit message is suspect. I should have said that it was complaining about the memcpy() and the free() on the const pointer. |
Yep!
Right! I changed it.
I'd rather keep it. It would be nice to eliminate the warnings in the long run (real bugs tend to hide within such swaths of warnings; I remember e.g. an incorrect assignment of
Don't you have to override |
WRT VS "15", yes I had to update both SANE_TOOL_PATH and MSVC_VCDIR to get it to build with VS "15". I haven't pushed this yet, since it's just a pre-release -- and I suspect the lines in config.mak.uname containing "10.0.10240.0" will need a similar fix, but I won't know the build numbers until it is actually released. Long time, I'd like to have something that properly knows how to get the MSVC paths.... |
Build with VS2015
Build with VS2015
Build with VS2015
Build with VS2015 Signed-off-by: Johannes Schindelin <[email protected]>
Build with VS2015 Signed-off-by: Johannes Schindelin <[email protected]>
This sequence of commits allows git-for-windows to be built using VS2015.
This includes changes to build scripts and MSVC-specific versions of various OS and CRT wrappers.
It is sufficient to allow debugging and profiling using VS2015.
It DOES NOT attempt to generate SLN or VCPROJ files.
Most of my efforts here have been focused on porting to VC and the new UCRT in VS2015.
I'd eventually like to merge this effort with: #256
since Philip is concentrating on the SLN and VCPROJ issues.
This should be considered a WIP, since there are several cleanup steps (documented in one
of the READMEs) and I still need to get through the test suite (and add any additional tests we
think are necessary).