| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
We should not call `add_test` unless `BUILD_TESTING` is enabled.
Fixes: #18500
|
|\
| |
| |
| | |
Merge-request: !2509
|
| |
| |
| |
| |
| |
| |
| | |
The_CURL_STATICLIB option was replaced by BUILD_SHARED_LIBS.
Drop our own CURL_STATICLIB compile definition because it is now
provided by curl's usage requirements.
|
| |
| |
| |
| |
| |
| | |
Curl 7.61.1 requires CMake 3.4 to build from source and also exposes
a dependency on OpenSSL imported targets. Revert that part of the
changes imported from curl upstream.
|
| |
| |
| |
| |
| | |
* upstream-curl:
curl 2018-09-04 (432eb5f5)
|
| | |
|
|\ \
| | |
| | |
| | | |
Merge-request: !2513
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When generating `curl_config.h`, add size information for `long long`
and `__int64` types. These are needed as candidates for defining the
`ssize_t` type because on MSVC, `long` is not the same size as `size_t`.
This problem did not affect upstream curl because it computes the
`ssize_t` type in CMake code where all sizes are available. CMake's
port computes it in preprocessor logic because universal binaries on
macOS do not know type sizes until compile time.
Fixes: #18477
|
| |
| |
| |
| | |
Fixes: #18465
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
3c0bfb596f libuv: do not require PATH_MAX to be defined
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2422
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some platforms (e.g. GNU/Hurd) do not define PATH_MAX. Add a few other
variants and a fallback constant. Also use alternatives where possible:
* For readlink(), use lstat() to read the length of the link first.
If it is not a symlink, report EINVAL before trying to allocate.
If the size reports as zero, fall back one of the PATH_MAX variants.
* For realpath(), POSIX 2008 allows us to pass a NULL buffer
to tell it to malloc() internally.
This patch was inspired by downstream patches in Debian packaging
for issues 897061 and 909011.
Issue: #18337
|
| |
| |
| |
| |
| | |
* upstream-LibArchive:
LibArchive 2018-09-03 (5fe69dd0)
|
| | |
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Backport libarchive commit v3.3.3~16^2 (fix build with LibreSSL 2.7,
2018-04-01). LibreSSL 2.7 adds OpenSSL 1.1 API leading to conflicts on
method names.
Fixes: #18404
|
| |\
| | |
| | |
| | | |
Merge-request: !2146
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also add a binutils-2.31 to CMAKE_PREFIX_PATH in the environment so that
tests that look for them with `find_program` can find a newer version.
This is needed for the build id support in readelf.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bab868be13 Utilities/Release: Skip spurious ExternalData test for nightly binary
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2404
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This test fails spuriously too often and prevents the nightly binary
from finishing. Simply skip it for the nightly binary to allow it to
complete more regularly.
|
|/ / /
| | |
| | |
| | | |
Issue 18375
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
`sys/types.h` defines `int8_t` incorrectly as `char` which is unsigned.
Adjust ordering so `inttypes.h` defines it as `signed char` first.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
1e9c1d0c87 CTestCustom: Suppress scanbuild warning in liblzma
2461dd79e5 liblzma: Suppress MSVC warning parameter difference warning
9f77124ea8 liblzma: Drop checks for inline and restrict keywords
7a976ee742 Merge branch 'upstream-liblzma' into update-liblzma
352b8fa70d liblzma 2018-04-29 (b5be61cc)
021b54cab8 liblzma: Revise update script to get version 5.2.4
6b494f567a Merge branch 'upstream-liblzma' into update-liblzma
897b790d57 liblzma 2014-12-21 (265e5ffb)
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2264
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some `.c` sources add `restrict` to their pointer types to tell
the optimizer that there is no aliasing. These do not appear in
the corresponding `.h` declarations so MSVC warns.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We now require the compiler to support these, except for MSVC where
upstream liblzma already has special cases (in `common/sysdefs.h`).
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* upstream-liblzma:
liblzma 2018-04-29 (b5be61cc)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Revert commit v3.1.0-rc1~255^2~5 (liblzma: Port from C99 to C89/90,
2014-07-13). We now compile as C99 or above except on MSVC where
we will use another approach.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Revert commit v3.1.0-rc1~255^2~2 (liblzma: Avoid defining a 'restrict'
macro, 2014-07-24). We will use another approach to deal with the
'restrict' keyword.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is provided by `functional`, not `utility`. Fix the mapping added by
commit 276d3c7afe (IWYU: Add workaround mapping for std::hash,
2018-07-31). Also generalize the workaround from commit v3.12.0-rc1~39^2~1
(IWYU: Define a macro to tell code it is preprocessing for iwyu,
2018-05-25) to allow local builds to configure specific flags. This
is needed because iwyu behaves differently in different environments.
|
| | |
| | |
| | |
| | |
| | | |
When using GCC 8's standard library IWYU thinks that `<system_error>`
must be included to get `std::hash`. Add a mapping for `<utility>`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit v3.12.0-rc1~325^2 (ccmake: Check for curses more robustly
before enabling, 2018-03-21) we may not enable ccmake by default when
using a non-system curses (e.g. the static curses we build on Linux for
our binaries). Enable the option explicitly for our prebuilt binaries.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The documentation for CPack generators previously lived in their
respective internal CMake modules. This setup was misleading,
because it implied that you should include the modules in your own
code, which is not the case. Moving the documentation into a
separate section does a better job of hiding the internal modules,
which are just an implementation detail. The generator documentation
has also been modified to remove any references to the module name.
The CPackIFW module is a special exception: since it has user-facing
macros, the documentation for these macros has been kept in the module
page, while all other documentation related to the IFW generator has
been moved into the new section.
To make it easier to find the new documentation, the old help pages
for the CPack*.cmake modules have not been deleted, but have been
replaced with a link to their respective help page in the new
documentation section.
|
|\ \ \
| |/ /
|/| /
| |/
| |
| |
| | |
276e369813 Utilities/Sphinx: Add option to build and install Info manual
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2146
|
| |
| |
| |
| |
| | |
Add option `SPHINX_INFO` to enable the Sphinx 'texinfo' builder and use
the `makeinfo` tool to convert it to a `.info` file.
|
|/ |
|
|
|
|
| |
Found via `codespell` and `grep`
|
|
|
|
|
|
|
|
|
|
|
|
| |
Run the `clang-format.bash` script to update all our C and C++ code to a
new style defined by `.clang-format`. Use `clang-format` version 6.0.
* If you reached this commit for a line in `git blame`, re-run the blame
operation starting at the parent of this commit to see older history
for the content.
* See the parent commit for instructions to rebase a change across this
style transition commit.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update `.clang-format` with configuration to make the 6.0 format as
close as possible to what 3.8 produced before. Then revise the style:
* Indent preprocessor directives (a feature new since 3.8)
* Add a newline and indentation before inheritance `:` and `,`
Rename the Git attribute identifying the format to include the
clang-format version number: `format.clang-format-6.0`. This will aid
external infrastructure in knowing what version of the tool to run.
|
|
|
|
|
| |
Update the prebuilt binary build configurations for machines where
we build our own OpenSSL library to use a newer version.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
3e913b819d Merge branch 'upstream-curl' into update-curl
d431136e02 curl 2018-05-15 (cb013830)
f3c73b878c curl: Update script to get curl 7.60.0
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2091
|
| |
| |
| |
| |
| | |
* upstream-curl:
curl 2018-05-15 (cb013830)
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Versions of clang-format newer than 3.8 produce different output.
Our source code guide says that version 3.8 exactly must be used.
Update the comment in our `.clang-format` config file accordingly.
Add a check to our formatting script to verify the version.
Also update its tool search to look for the explicitly-named
3.8 variant first.
|
|
|
|
|
|
|
| |
This depends on
- a suitable flex version in PATH (currently 3.0.4)
- a suitable version of 'sed' in PATH (e.g. GNU sed)
|
| |
|