| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
Merge-request: !1782
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
Merge-request: !1770
|
| |/ |
|
|/
|
|
|
| |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
|
|
|
|
| |
Add section headers similar to the 3.10 release notes and move each
individual bullet into an appropriate section. Revise a few bullets.
|
|
|
|
|
| |
Run the `Utilities/Release/consolidate-relnotes.bash` script to move
notes from `Help/release/dev/*` into `Help/release/3.11.rst`.
|
|\
| |
| |
| |
| |
| |
| | |
b95eda9b Help: Fix code example in cmake_parse_arguments.rst
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1747
|
| | |
|
|/ |
|
|
|
|
|
| |
The current documentation doesn't clarify that compilers simulating
Visual C++ will also have these variables set.
|
|\
| |
| |
| |
| |
| |
| | |
7771657c Help: Better explain that foreach(RANGE ) is inclusive.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1716
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
99e473ca Help: Fix typo in CMAKE_INCLUDE_CURRENT_DIR docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1708
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
fc57afde Help: Fix typo in CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1709
|
| |/ |
|
|/ |
|
|
|
|
|
|
| |
Extend the maintainer guide with a reminder to self-review the
new ancestry of the `release` and `master` branches to ensure
that nothing unexpected was merged.
|
|\
| |
| |
| |
| |
| |
| |
| | |
239a3ef8 Server-mode: Document protocol version for optional handshake arguments
9b1a3d24 Server-mode: Rename functions to reflect what they do
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1693
|
| |
| |
| |
| |
| |
| |
| |
| | |
Document which Protocol version only needs the build directory to be passed
during a handshake.
This is available a bit earlier than that, but from all I can tell 1.2 is
the earliest version where that feature is reliably available.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
551bd0b3 Generators: adjust error message for the removed KDevelop3 generator
9198e6a2 Generators: remove KDevelop3 generator
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1688
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The last KDevelop3 release was many years ago, in 2008 I think.
I haven't seen or read about anybody using KDevelop 3 since a
long time, so I think it can safely be removed from CMake.
KDevelop 4 (first released in 2010) has its own proper CMake
support now, independent from this generator.
Alex
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
04483111 sourceFile properties: add property INCLUDE_DIRECTORIES
3073bd1f VisualStudio generators: refactoring
78b1c2e0 sourceFile properties: add property COMPILE_OPTIONS
3f935e69 LocalGenerator: refactoring
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1596
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| | |
Add the support of per-source property COMPILE_OPTIONS,
including generator expressions support.
Related: #17507
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
b1ae9aaf GenerateExportHeader: add release notes, tests for include guard changes
f4082b0e GenerateExportHeader: add INCLUDE_GUARD_NAME option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1643
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
93bc5848 CPack: accept --trace and --trace-expand
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1583
|
| |/ |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
4829ea23 add_jar: add option GENERATE_NATIVE_HEADERS
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1675
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
c89c87c9 Help: Fix heading level for CMAKE_AUTOMOC_MACRO_NAMES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1671
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
60febda4 Help: Explain meaning and limitations of CMAKE_CROSSCOMPILING
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1672
|
| |/
| |
| |
| | |
Fixes: #17653
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
f3e9bedd Help: CMAKE_<LANG>_COMPILER_EXTERNAL_TOOLCHAIN typo removal
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1679
|
| |/ |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
c42b377c cmCacheManager: Test and document newline truncation behavior
a9c48307 cmCacheManager: Truncate values containing newlines
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1652
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
60216e15 Help: Improved MAIN_DEPENDENCY documentation of add_custom_command()
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1665
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
506fda1c Genex: Enable COMPILE_LANGUAGE for INCLUDE_DIRECTORIES with VS and Xcode
c2f79c98 Genex: Enable COMPILE_LANGUAGE for COMPILE_DEFINITIONS with VS and Xcode
0795d25b cmVisualStudio10TargetGenerator: Factor out include dir computation
1ab4d186 cmLocalVisualStudio7Generator: Clarify variable name of compiled language
07e1a743 cmLocalVisualStudio7Generator: Clarify condition for target that compiles
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1657
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The set of compile flags used for a target's C and C++ sources is based
on the linker language. By default this is always the C++ flags if any
C++ sources appear in the target, and otherwise the C flags. Therefore
we can define the `COMPILE_LANGUAGE` generator expression in
`INCLUDE_DIRECTORIES` to match the selected language.
This is not exactly the same as for other generators, but is the best VS
and Xcode can do. It is also sufficient for many use cases since the
set of include directories for C and C++ is frequently similar but may
be distinct from those for other languages like CUDA.
Fixes: #17435
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The set of compile flags used for a target's C and C++ sources is based
on the linker language. By default this is always the C++ flags if any
C++ sources appear in the target, and otherwise the C flags. Therefore
we can define the `COMPILE_LANGUAGE` generator expression in
`COMPILE_DEFINITIONS` to match the selected language.
This is not exactly the same as for other generators, but is the best VS
and Xcode can do. It is also sufficient for many use cases since the
set of definitions for C and C++ is frequently similar but may be
distinct from those for other languages like CUDA.
Issue: #17435
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
f74c2580 CheckIncludeFiles: Honor CMAKE_REQUIRED_LIBRARIES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1620
|