Philip Oakley <philipoakley@xxxxxxx> writes: > Hopefully it's not too late in the cycle for a review of this contrib/compat > item. Has this been discussed in the Windows land and folks are all happy with this change? If so the only thing we would need review on the main list is the top-level change outside compat/ and contrib/, so it may be possible to sneak it in before -rc1. Otherwise, no, but we can still polish it during the prerelease freeze and aim to merge it in the first batch after the upcoming release. > Philip Oakley (17): > .gitignore: improve MSVC ignore patterns > .gitignore: ignore library directories created by MSVC VS2008 > buildsystem > (msvc-build) Vcproj.pm: remove duplicate GUID > Makefile: a dry-run can error out if no perl. Document the issue > engine.pl: fix error message (lib->link) > engine.pl: Avoid complications with perl support > engine.pl: Properly accept quoted spaces in filenames > engine.pl: Fix i18n -o option in msvc buildsystem generator > engine.pl: ignore invalidcontinue.obj which is known to MSVC > engine.pl: name the msvc buildsystem's makedry error file > engine.pl: delete the captured stderr file if empty > engine.pl: add debug line to capture the dry-run > engine.pl: provide more debug print statements > Vcproj.pm: list git.exe first to be startup project > vcbuild/readme: Improve layout and reference msvc-build script > msvc-build: add complete Microsoft Visual C compilation script > config.mak.uname: add MSVC No_SafeExeceptionHandler option > > .gitignore | 8 ++- > Makefile | 3 ++ > compat/vcbuild/README | 27 +++++++--- > compat/vcbuild/scripts/msvc-build | 89 +++++++++++++++++++++++++++++++ > config.mak.uname | 9 ++++ > contrib/buildsystems/Generators/Vcproj.pm | 34 ++++++------ > contrib/buildsystems/engine.pl | 37 ++++++++++--- > 7 files changed, 174 insertions(+), 33 deletions(-) > create mode 100644 compat/vcbuild/scripts/msvc-build > mode change 100755 => 100644 contrib/buildsystems/engine.pl Why? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html