aboutsummaryrefslogtreecommitdiff
path: root/winbuild/gen_resp_file.bat
AgeCommit message (Collapse)Author
2019-05-23winbuild: Use two space indentationSteve Holme
Closes #3930
2019-05-09gen_resp_file.bat: Removed unnecessary @ from all but the first commandSteve Holme
There is need to use @ on every command once echo has been turned off. Closes #3854
2019-05-05winbuild: Add our standard copyright header to the winbuild batch filesSteve Holme
2018-05-27winbuild: only delete OUTFILE if it existsrichardthe3rd
This removes the slightly annoying "Could not file LIBCURL_OBJS.inc" and "Could not find CURL_OBJS.inc.inc" message when building into a clean folder. closes #2602
2014-09-12newlines: fix mixed newlines to LF-onlyRay Satiro
I use the curl repo mainly on Windows with the typical Windows git checkout which converts the LF line endings in the curl repo to CRLF automatically on checkout. The automatic conversion is not done on files in the repo with mixed line endings. I recently noticed some weird output with projects/build-openssl.bat that I traced back to mixed line endings, so I scanned the repo and there are files (excluding the test data) that have mixed line endings. I used this command below to do the scan. Unfortunately it's not as easy as git grep, at least not on Windows. This gets the names of all the files in the repo's HEAD, gets each of those files raw from HEAD, checks for mixed line endings of both LF and CRLF, and prints the name if mixed. I excluded path tests/data/test* because those can have mixed line endings if I understand correctly. for f in `git ls-tree --name-only --full-tree -r HEAD`; do if [ -n "${f##tests/data/test*}" ]; then git show "HEAD:$f" | \ perl -0777 -ne 'exit 1 if /([^\r]\n.*\r\n)|(\r\n.*[^\r]\n)/'; if [ $? -ne 0 ]; then echo "$f"; fi; fi; done
2012-11-01Architecture selection for winbuild and minor makefiles refactoringSapien2
2012-04-13Set batch mode to 755 to make Cygwin git pulls work.Guenter Knauf
2011-01-28Windows build: alternative makefilePierre Joye
This is a separate makefile for MSVC builds. It is deliberately put in another dir than src/ and lib/ to allow a different build experience than the previous - at least during a period. Eventually we should unify.