summaryrefslogtreecommitdiffstats
path: root/Utilities
Commit message (Collapse)AuthorAgeFilesLines
* Help: Override pygments CMakeLexer to support <..> and [..]Joachim Wuttke (o)2018-10-183-6/+77
| | | | | | | | | | | | | | | | | | | | | | * The code snippets in the docs consist of CMake code mixed with syntax definition punctuation like < > [ ] ... Therefore a pure CMake lexer is inadequate. Here it is replaced by a CMake syntax definition parser. * Fixed syntax definition snippets in FindPkgConfig.cmake to make best use of syntax highlighting. This source file is the hardest to support because it contains comparison operators <= = >=, which need special attention to avoid confusion with the placeholder indicators <...>. * Fixed syntax in execute_process.rst (there were unbalanced brackets). * Disabled syntax highlighting for long string examples in cmake-language.7.rst. * No highlighting of removed syntax in CMP0049 * To inspect the outcome of this patch, see e.g. the pages * manual/cmake-buildsystem.7.html * module/ExternalProject.html * module/FindPkgConfig.html which are particularly rich in complex code snippets.
* Utilities/Release: Update to openssl-1.1.1Brad King2018-10-081-3/+3
| | | | | Update the prebuilt binary build configurations for machines where we build our own OpenSSL library to use a newer version.
* CMake 3.13.0-rc1 version updateBrad King2018-10-031-1/+1
|
* Merge topic 'libuv-gnu-hurd'Brad King2018-10-031-8/+39
|\ | | | | | | | | | | | | 3c0bfb596f libuv: do not require PATH_MAX to be defined Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2422
| * libuv: do not require PATH_MAX to be definedBrad King2018-10-011-8/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'upstream-LibArchive' into update-libarchiveBrad King2018-09-2652-203/+1002
| | | | | | | | | | * upstream-LibArchive: LibArchive 2018-09-03 (5fe69dd0)
* | libarchive: Update script to get 3.3.3Brad King2018-09-261-1/+1
| |
* | Merge branch 'libarchive-libressl-2.7' into update-libarchiveBrad King2018-09-261-1/+2
|\ \
| * | libarchive: Backport fix for build with LibreSSL 2.7Brad King2018-09-261-1/+2
| |/ | | | | | | | | | | | | | | 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 branch 'sphinx-info' into release-3.12v3.12.0-rc1Brad King2018-06-131-1/+28
| |\ | | | | | | | | | Merge-request: !2146
* | | Utilities/Release: Build with gcc 8.2 on LinuxBrad King2018-09-251-2/+5
| | | | | | | | | | | | | | | | | | 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.
* | | Merge topic 'rel-win-nightly'Brad King2018-09-202-2/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | bab868be13 Utilities/Release: Skip spurious ExternalData test for nightly binary Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2404
| * | | Utilities/Release: Skip spurious ExternalData test for nightly binaryBrad King2018-09-192-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | libuv: Add kFreeBSD platform-specific filesGregor Jasny2018-09-181-0/+16
|/ / / | | | | | | | | | Issue 18375
* | | cmake-gui: Update iconsT.J. Corona2018-08-163-0/+0
| | |
* | | librhash: Avoid incorrect int8_t definition with PGI on Linux ppc64leBrad King2018-08-091-0/+2
| | | | | | | | | | | | | | | `sys/types.h` defines `int8_t` incorrectly as `char` which is unsigned. Adjust ordering so `inttypes.h` defines it as `signed char` first.
* | | Merge topic 'update-liblzma'Brad King2018-08-09111-2187/+4205
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | liblzma: Suppress MSVC warning parameter difference warningBrad King2018-08-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | liblzma: Drop checks for inline and restrict keywordsBrad King2018-08-062-40/+0
| | | | | | | | | | | | | | | | | | | | We now require the compiler to support these, except for MSVC where upstream liblzma already has special cases (in `common/sysdefs.h`).
| * | | Merge branch 'upstream-liblzma' into update-liblzmaBrad King2018-08-0696-1047/+3477
| | | | | | | | | | | | | | | | | | | | * upstream-liblzma: liblzma 2018-04-29 (b5be61cc)
| * | | liblzma: Revise update script to get version 5.2.4Brad King2018-08-061-1/+3
| | | |
| * | | liblzma: Avoid importing upstream makefilesBrad King2018-08-061-1/+3
| | | |
| * | | liblzma: Name sizeof size_t macro consistently with upstreamBrad King2018-08-063-4/+4
| | | |
| * | | liblzma: Revert "Port from C99 to C89/90"Brad King2018-08-0661-1075/+700
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | liblzma: Revert "Avoid defining a 'restrict' macro"Brad King2018-08-0631-103/+101
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | IWYU: Fix workaround mapping for std::hashBrad King2018-08-071-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | IWYU: Add workaround mapping for std::hashBrad King2018-07-311-0/+3
| | | | | | | | | | | | | | | When using GCC 8's standard library IWYU thinks that `<system_error>` must be included to get `std::hash`. Add a mapping for `<utility>`.
* | | Utilities/Release: Explicitly enable ccmake on macOS and LinuxBrad King2018-07-022-0/+2
| | | | | | | | | | | | | | | | | | | | | 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.
* | | Help: Add new section for CPack generatorsKyle Edwards2018-06-212-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Merge topic 'sphinx-info'Brad King2018-06-131-1/+28
|\ \ \ | |/ / |/| / | |/ | | | | | | 276e369813 Utilities/Sphinx: Add option to build and install Info manual Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2146
| * Utilities/Sphinx: Add option to build and install Info manualOrivej Desh2018-06-121-1/+28
| | | | | | | | | | Add option `SPHINX_INFO` to enable the Sphinx 'texinfo' builder and use the `makeinfo` tool to convert it to a `.info` file.
* | CMake 3.12.0-rc1 version updateBrad King2018-06-051-1/+1
|/
* Fix misc. typosluz.paz2018-06-041-1/+1
| | | | Found via `codespell` and `grep`
* Revise C++ coding style using clang-format-6.0Kitware Robot2018-06-0113-30/+30
| | | | | | | | | | | | 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.
* clang-format.bash: update to clang-format-6.0Brad King2018-06-012-7/+7
| | | | | | | | | | | | 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.
* Utilities/Release: Update to openssl-1.1.0hBrad King2018-05-311-3/+3
| | | | | Update the prebuilt binary build configurations for machines where we build our own OpenSSL library to use a newer version.
* Merge topic 'update-curl'Brad King2018-05-21108-1761/+3630
|\ | | | | | | | | | | | | | | | | 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
| * Merge branch 'upstream-curl' into update-curlBrad King2018-05-18107-1760/+3629
| | | | | | | | | | * upstream-curl: curl 2018-05-15 (cb013830)
| * curl: Update script to get curl 7.60.0Brad King2018-05-181-1/+1
| |
* | clang-format: Explicitly require version 3.8 of the toolBrad King2018-05-181-1/+6
|/ | | | | | | | | 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.
* regenerate-parsers.bash: Add script to automate parser generationDaniel Franke2018-05-161-0/+37
| | | | | | | This depends on - a suitable flex version in PATH (currently 3.0.4) - a suitable version of 'sed' in PATH (e.g. GNU sed)
* regenerate-lexers.bash: Add option to check timestampsDaniel Franke2018-05-161-9/+22
|
* regenerate-lexers.bash: Factor file names into variablesDaniel Franke2018-05-161-8/+14
|
* Merge topic 'update-libuv'Brad King2018-05-0861-752/+991
|\ | | | | | | | | | | | | | | | | 0d389d175a libuv: Revert local linux/sparc64 fix now that we have upstream fix 42fbb28516 Merge branch 'upstream-libuv' into update-libuv c8b67ea119 libuv 2018-05-06 (bf605bd7) Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2049
| * libuv: Revert local linux/sparc64 fix now that we have upstream fixBrad King2018-05-071-1/+1
| |
| * Merge branch 'upstream-libuv' into update-libuvBrad King2018-05-0761-751/+990
| | | | | | | | | | * upstream-libuv: libuv 2018-05-06 (bf605bd7)
* | Merge topic 'doc-code-block-highlight'Brad King2018-05-081-0/+1
|\ \ | |/ |/| | | | | | | | | 8114b00b02 Utilities/Sphinx: Do not highlight unspecified code blocks as python Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2047
| * Utilities/Sphinx: Do not highlight unspecified code blocks as pythonBrad King2018-05-041-0/+1
| |
* | Utilities/Sphinx: Make HTML links in parsed-literal blocks more obviousBrad King2018-05-071-0/+10
|/ | | | | | | | Hyperlink text color does not stand out when used inside a literal block because such blocks typically get syntax highlighting. Update our CSS style to make the links more distinct. Suggested-by: Kyle Edwards <kyle.edwards@kitware.com>
* Merge topic 'ctest-libuv-linux-sparc64'Brad King2018-05-031-1/+1
|\ | | | | | | | | | | | | 1c22fdf360 libuv: linux/sparc64: use fcntl to set and clear O_NONBLOCK Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2029
generated by cgit v0.12 at 2025-01-17 06:52:00 (GMT)