aboutsummaryrefslogtreecommitdiff
path: root/projects/build-openssl.bat
AgeCommit message (Collapse)Author
2015-07-26build-openssl.bat: Added support for VC14Steve Holme
2015-07-25build-openssl.bat: Show syntax if required args are missingJay Satiro
2015-04-02build-openssl.bat: Fix mixed line endingsJay Satiro
Use LF not CRLF, throughout. msysgit will only convert a file to CRLF on checkout if it's not mixed.
2015-01-16build-openssl.bat: Added check for Perl installationSteve Holme
2014-11-02build-openssl.bat: Fix x64 release buildJay Satiro
Prior to this change if x64 release was specified a failed attempt was made to build x86 release instead.
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
2014-05-20build-openssl.bat: Added check for OpenSSL source directorySteve Holme
2014-05-20build-openssl.bat: Added default source directory when not specifiedSteve Holme
Added a default source directory so the user doesn't have to specify one - the same as that, which the Visual Studio project files expect the OpenSSL dependencies to be in.
2014-05-06build-openssl.bat: Corrected use of angled brackets in help outputIvo Bellin Salarin
Angled brackets were used in the help output to indicate that the compiler and platform arguments are mandatory. Unfortunately this caused a "< was unexpected at this time" error as the characters are interpreted as re-direction characters when not escaped.
2014-05-01build: Added OpenSSL VC build helper for side-by-side compilationsSteve Holme