Age | Commit message (Collapse) | Author |
|
The maketgz script now makes sure the generated hugehelp.c file in the
tarball is newer than the generated curl.1 man page, so that it doesn't
have to get unnecessarily rebuilt first thing in a typical build. It
thus also removes the need for perl to build off a plain release
tarball.
Fixes #1565
|
|
... and support and additional "security patched" date for those who
enhance older versions that way. Pass on the define CURL_PATCHSTAMP with
a date for that.
Building with non-release headers shows the date as [unreleased].
Also: this changes the date format generated in the curlver.h file to be
"YYYY-MM-DD" (no name of the day or month, no time, no time zone) to
make it easier on the eye and easier to parse. Example (new) date
string: 2017-05-09
Suggested-by: Brian Childs
Closes #1474
|
|
maketgz now runs scripts/updatemanpages.pl to update the man pages .TH
section to use the current date and curl/libcurl version.
(TODO Section 3.1)
Closes #1058
|
|
The winbuild/ build files is now the single MSVC makefile build choice.
Closes #1215
|
|
... to allow you to update the local repository with the given version
number data.
|
|
|
|
... makes it a lot faster
|
|
|
|
bug: http://curl.haxx.se/mail/lib-2016-01/0123.html
|
|
VC7, VC11, VC12 and VC14 makefiles were missing from the release
tarball.
|
|
|
|
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
|
|
grrr, missed them in my previous fix
|
|
|
|
To get the VC project files generated before packaging!
|
|
Apparently the previous usage didn't work with that implementation,
while this updated version works with at least both Parallel BZIP2
v1.1.8 and regular bzip "Version 1.0.6, 6-Sept-2010".
|
|
Configuration files such as curl_config.h and all config-*.h no longer exist
nor are generated/copied into 'src' directory, now these only exist in 'lib'
directory from where curl tool sources uses them.
Additionally old src/setup.h has been refactored into src/tool_setup.h which
now pulls lib/setup.h
The possibility of a makefile needing an include path adjustment exists.
|
|
|
|
maketgz and buildconf.bat updated to reflect this.
|
|
Adam Light posted this patch to the list which enables builds from
git with VC versions other than vc6; also he added a vc10 target.
|
|
It passes the git log output through 'log2changes.pl' to produce
the lot.
|
|
|
|
|
|
|
|
|
|
libcurl is used with other projects which also have a config.h.
|
|
files
|
|
in the release archive - by using our .dist suffix trick.
|
|
now use the actual makefile targets to do the VC8 and VC9 makefiles.
|
|
building with VC8 to get the "manifest" embedded to make fine stand-alone
binaries. The maketgz and the src/Makefile.vc6 files were adjusted
accordingly.
|
|
|
|
|
|
machine type too.
|
|
makefiles that are included in the source release archives, generated from
the Makefile.vc6 files by the maketgz script. I also modified the root
Makefile to have a VC variable that defaults to vc6 but can be overridden to
allow it to be used for vc8 as well. Like this:
nmake VC=vc8 vc
|
|
This is meant
to primarily be used for the autobuilds to know from what point in time a particular tarball
is, and thus what changes it contains (or not).
|
|
|
|
reported, the define is used by the configure script and is assumed to use
the 0xYYXXZZ format. This made "curl-config --vernum" fail in the 7.15.0
release version.
|
|
|
|
--vernum output wasn't zero prefixed properly (as claimed in documentation).
This is fixed in maketgz now.
|
|
|
|
|
|
|
|
patch number zero.
|
|
|
|
well. Removed the depedency on perl.
|
|
|
|
2. make the libcurl and curl version the same
|
|
|
|
|
|
|