Kitware-CMake

Commit Graph

Author	SHA1	Message	Date
Clemens Wasser	59277bccd3	bzip: Precompile common expensive headers	2 years ago
Brad King	91e4d27765	bzip2: Suppress clang-analyzer warnings	2 years ago
Brad King	c7c3e39e4f	Utilities: Activate POSIX APIs even without compiler extensions Compile some third-party libraries with preprocessor definitions that activate POSIX APIs even when compiler extensions are not enabled. We already do this in libuv, inherited from the upstream buildsystem. This extends commit `f034b0f663` (CMake compilation: do not use compiler extensions, 2020-03-14, v3.18.0-rc1~494^2). Issue: #20454	3 years ago
Aaron Liu	24da80b70a	Utilities: Suppress warnings in third-party code with IBMClang	4 years ago
makise-homura	e5d9fce03f	LCC: Add dedicated support for MCST LCC compiler Divert LCC compiler as a new one, instead of treating it as GNU. Since old times, Elbrus C/C++/Fortran Compiler (LCC) by MCST has been passing checks for GNU compilers, so it has been identified as GNU. Now, with intent of seriously upstreaming its support, it has been added as a separate LCC compiler, and its version displays not a supported GCC version, but LCC version itself (e.g. LCC 1.25.19 instead of GNU 7.3.0). This commit adds its support for detection, and also converts basically every check like 'is this compiler GNU?' to 'is this compiler GNU or LCC?'. The only places where this check is untouched, is where it regards other platforms where LCC is unavailable (primarily non-Linux), and where it REALLY differs from GNU compiler. Note: this transition may break software that are already ported to Elbrus, but hardly relies that LCC will be detected as GNU; still such software is not known.	4 years ago
Brad King	408e6d6185	Utilities: Suppress warnings in third-party code with NVHPC	4 years ago
Brad King	87909f0600	Utilities: Suppress warnings in third-party code when using IntelLLVM	5 years ago
Brad King	db1447b2cf	bzip2: Disable MSVC warnings in 3rd party code In commit `35acaa90c5` (bzip2: Add compilation flags to disable warnings in third-party code, 2020-02-24) we forgot to disable warnings for MSVC.	5 years ago
Brad King	35acaa90c5	bzip2: Add compilation flags to disable warnings in third-party code	6 years ago
Brad King	2c40844891	bzip2: Remove all sources to make room for fresh import	6 years ago
Brad King	c69b4c8dfe	bzip2: Drop unused .dsp files	8 years ago
Sean McBride	af0051f48a	curl, bzip2: Suppress warnings by setting initial value Silence clang -Wsometimes-uninitialized warnings.	12 years ago
David Cole	7918998533	BZip2: Remove unnecessary .bz2 files from CMake source tree We had complaints that people couldn't install the CMake source tarball on some secure systems because there were "corrupt bz2 files" in it... We do not use these sample.bz2 files anyhow in the CMake build, so we'll just remove them.	13 years ago
Brad King	87fde60563	Suppress -Wcast-align in curl and bzip2 Trust upstream developers of third-party code.	15 years ago
Bill Hoffman	3e5d2bda4d	suppress another warning.	16 years ago
Bill Hoffman	74981c1afd	Remove a few more warnings	16 years ago
Bill Hoffman	2021832170	Remove makefile as it breaks in-source build testing	16 years ago
Brad King	08dc3d5170	bzip2: Restore fix for unused variables The commit "bzip2: Disable Borland warnings" accidentally reverted changes from commit "Fix warnings for unused variables". This restores them.	16 years ago
Brad King	60855f620b	bzip2: Disable Borland warnings We disable warnings to silence them while making minimal changes to third-party code.	16 years ago
Bill Hoffman	5f41fe03ca	Fix warnings for unused variables	16 years ago
Bill Hoffman	fb51d98562	Switch to using libarchive from libtar for cpack and cmake -E tar This allows for a built in bzip and zip capability, so external tools will not be needed for these packagers. The cmake -E tar xf should be able to handle all compression types now as well.	16 years ago

23 Commits (master)