| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
11768733 NSIS: Quote uninstaller path when executing it in a shell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Protect our `$0` reference in the shell as `"$0"`. Otherwise it works
with a space in the path only due to an insecure Windows feature.
Prior to this fix, any installer using the option added by commit
v2.8.9~234^2 (Added CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL,
2011-06-11) exposes a local privilege escalation vulnerability.
Reported-by: Amir Szekely <kichik@gmail.com>
Reported-by: Ug_0 Security
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add an explicit `<Natvis>` element in VS project files for `*.natvis`
files. These enable custom debug visualizers for project-specific
types.
Fixes #16043.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
8a98cf64 Honor CMAKE_*_LINKER_FLAGS[_<CONFIG>]_INIT set in toolchain files
37d15c39 MSVC: Set all CMAKE_*_LINKER_FLAGS_INIT directly
55c884ed Embarcadero: Set all CMAKE_*_LINKER_FLAGS_INIT directly
aec3c79a Strip CMAKE_*_LINKER_FLAGS[_<CONFIG>] initializer whitespace
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Document these variables.
Change our convention for setting these variables from:
set(CMAKE_EXE_LINKER_FLAGS_INIT "...")
to
string(APPEND CMAKE_EXE_LINKER_FLAGS_INIT " ...")
so that any value previously set by a toolchain file will be used.
|
|/ /
| |
| |
| |
| |
| | |
Port changes from VTK commit fda6a31cb9 (Added Improved FindOpenMP
module, 2015-04-23). Improve use of try_compile to avoid needing
to pass OpenMP flags as libraries.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
e3bff7b3 Help: Add notes for topic 'findicu'
4a63be15 FindICU: New module
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
9da725cb Windows: Honor WINDOWS_EXPORT_ALL_SYMBOLS for executables with exports
2005b960 Makefile: Factor out WINDOWS_EXPORT_ALL_SYMBOLS helper
|
| | |
| | |
| | |
| | |
| | | |
For executables with ENABLE_EXPORTS set, export all symbols when
instructed to do so by WINDOWS_EXPORT_ALL_SYMBOLS.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Document these variables.
Change our convention for setting these variables from:
set(CMAKE_C_FLAGS_INIT "...")
to
string(APPEND CMAKE_C_FLAGS_INIT " ...")
so that any value previously set by a toolchain file will be used.
Automate the conversion with:
sed -i 's/set *(\(CMAKE_\(C\|CXX\|Fortran\|RC\|ASM\|${[^}]\+}\)_FLAGS\(_[^_]\+\)\?_INIT \+"\)/string(APPEND \1 /' \
Modules/Compiler/*.cmake Modules/Platform/*.cmake
and follow up with some manual fixes (e.g. to cases that already
meant to append). Also revert the automated changes to contexts
that are not protected from running multiple times.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the `try_compile` source file signature we propagate the caller's
value of `CMAKE_<LANG>_FLAGS` into the test project. Extend this to
propagate `CMAKE_<LANG>_FLAGS_<CONFIG>` too instead of always using the
default value in the test project. This will be useful, for example, to
allow the MSVC runtime library to be changed (e.g. `-MDd` => `-MTd`).
However, some projects may currently depend on this not being done,
so we need to activate the behavior using a policy.
This change was originally made by commit v3.6.0-rc1~160^2 (try_compile:
Honor CMAKE_<LANG>_FLAGS_<CONFIG> changes, 2016-04-11) but without the
policy and so had to be reverted during the 3.6 release candidate cycle.
Fixes #16174.
|
|\ \
| | |
| | |
| | |
| | | |
843402b0 GenerateExportHeader: Add option to specify custom content
|
| | | |
|
|\ \ \
| |/ /
|/| /
| |/
| | |
943fe6e3 Revert "try_compile: Honor CMAKE_<LANG>_FLAGS_<CONFIG> changes"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Revert commit v3.6.0-rc1~160^2 (try_compile: Honor
CMAKE_<LANG>_FLAGS_<CONFIG> changes, 2016-04-11). The behavior it
introduced can break projects that depend on the lack of such behavior.
We will have to introduce a policy or other mechanism to enable the
behavior in a compatible way. Simply revert it for now.
See issue #16174.
|
|\ \
| | |
| | |
| | |
| | | |
ed05f11d VS: Add a VS_TOOL_OVERRIDE source file property
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This property allow to specify a specific Visual Studio tool for a
source file overriding the default tool behavior. For example, a
`.resw` file being processed as a `PriResource` file. This has the
advantage of being able to teach CMake to process new file types without
code modifications.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
35a6cac2 VS: Add VS_SDK_REFERENCES target property to reference external SDKs
|
| |/ /
| | |
| | |
| | |
| | | |
Allow one to specify external SDK references such as
`Microsoft.AdMediatorWindows81, Version=1.0`.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
5cc34162 AIX: Add support for Clang compiler
|
| | |
| | |
| | |
| | |
| | | |
The platform information module for GNU on AIX can be reused for Clang
on AIX because clang accepts almost all of the same options.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even in relatively small projects using `--trace` (and `--trace-expand`)
may produce a lot of output. When developing a custom module usually
one is interested in output of only a few particular modules.
Add a `--trace-source=<file>` option to enable tracing only a subset of
source files. The final output would be only from requested modules,
ignoring anything else not matched to given filename(s).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
8be00e44 Help: Add release note about XCODE_FILE_ATTRIBUTES source file property
27eb657d Xcode: Add support for mig files
811f6c82 Xcode: Add XCODE_FILE_ATTRIBUTES source file property
ef494edf Xcode: Don't emit empty settings blocks.
82ebbf68 Xcode: Add function to conditionally add Xcode Attributes
025edea0 Xcode: Add const qualifiers
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
a0902efa Help: Add notes for topic 'link_what_you_use'
96242f80 Add options to run `ldd -u -r` as a "link-what-you-use" tool
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
Add a ``FIND_LIBRARY_USE_LIB32_PATHS`` global property analogous to the
``FIND_LIBRARY_USE_LIB64_PATHS`` property. This helps find commands on
multilib systems that use ``lib32`` directories and either do not have
``lib`` symlinks or point ``lib`` to ``lib64``.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
0bd91ad4 UseJava: Fix race condition creating java class list
89df91b9 Help: Add notes for topic 'java-export-targets'
95d84369 Tests: Add test for exported JARs
5341c0d8 UseJava: Add infrastructure to export targets
d91ec044 Tests/Java: Clean up style of Java test code
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
adf4df28 Add FindVulkan.cmake.
|
| | |
| | |
| | |
| | | |
This adds FindVulkan with corresponding tests.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
63e5eb5f Help: Add notes for 'productbuild' topic
2e3c67d1 productbuild: Add new productbuild cpack generator.
50a3d340 PackageMaker: factor out common code for creating pkg files.
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
| |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
|
|
|
|
| |
Add section headers similar to the 3.5 release notes and move each
individual bullet into an appropriate section. Revise a few bullets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move all development release notes into a new version-specific document:
tail -q -n +3 Help/release/dev/* > Help/release/3.6.rst
git rm -- Help/release/dev/*
except the sample topic:
git checkout HEAD -- Help/release/dev/0-sample-topic.rst
Reference the new document from the release notes index document.
Add a title and intro sentence to the new document by hand.
|
|\
| |
| |
| |
| |
| | |
d256ba07 try_compile: Optionally forward custom platform variables to test project
fb4791b3 cmCoreTryCompile: Refactor forwarding of variables to test project
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a `CMAKE_TRY_COMPILE_PLATFORM_VARIABLES` variable to specify a list
of custom variables to be forwarded to a `try_compile` test project.
This will be useful for platform information modules or toolchain files
to forward some platform-specific set of variables from the host project
(perhaps set in its cache) to the test project so that it can build the
same way.
|
|\ \
| | |
| | |
| | |
| | | |
3acc29fc CPack/DragNDrop: Optionally disable `/Applications` symlink
|
| |/ |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
c1340827 Add a variable to specify language-wide system include directories
44199097 cmMakefile: Optimize AddSystemIncludeDirectories for empty set
a896043b GHS: Compute include directories consistently with other generators
|
| |
| |
| |
| |
| |
| |
| | |
Create a `CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES` variable to specify
system include directories for for `<LANG>` compiler command lines.
This plays a role for include directories as the existing
`CMAKE_<LANG>_STANDARD_LIBRARIES` variable does for link libraries.
|
|\ \
| |/
| |
| |
| | |
7807b3a9 Help: Document CMAKE_<LANG>_STANDARD_LIBRARIES variable
|
| |
| |
| |
| |
| | |
Also drop documentation of non-existent CMAKE_STANDARD_LIBRARIES
variable.
|
|\ \
| | |
| | |
| | |
| | | |
adbd3985 CPack/Deb possibility to change package name
|