| Age | Commit message (Collapse) | Author |
|---|
|
.. and do the same for build-wolfssl.bat.
Because MS calls it VC14.1.
Closes https://github.com/curl/curl/pull/2189
|
|
Fixes #2430
Closes #2457
|
|
|
|
|
|
Whilst the compiler parameter is mandatory, platform is optional as it
is automatically calculated by the :configure section.
This partially reverts commit 6d62d2c55d.
|
|
...and not just the Community Edition.
|
|
|
|
Ref: https://github.com/curl/curl/issues/1002
|
|
Fixed inconsistency from commit 1eae114065 and 0ad6c72227 of the order
in which Perl was added to the PATH.
|
|
|
|
|
|
|
|
Allow the -help command line argument to be specified in any argument
and not just as the first.
|
|
|
|
|
|
Use LF not CRLF, throughout. msysgit will only convert a file to CRLF
on checkout if it's not mixed.
|
|
|
|
Prior to this change if x64 release was specified a failed attempt was
made to build x86 release instead.
|
|
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
|
|
|
|
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.
|
|
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.
|
|
|
