| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| | |
3333e2791b Help: Add release note about 'copy_directory' behavior change
24367563d7 Merge branch 'upstream-KWSys' into update-kwsys
1e0a2e9377 KWSys 2018-05-15 (5f757898)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2080
|
| |
| |
| |
| | |
Issue: #16001
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
c9349cc1b9 target_link_libraries: Allow use with targets in other directories
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2040
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Previously the command did not allow naming targets on the LHS that
were not created in the calling directory. Lift this restriction to
enable more flexible use by projects.
Fixes: #17943
|
|\ \
| |/
|/|
| |
| |
| |
| | |
71a033616a added CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2032
|
| |
| |
| |
| | |
Fixes: #17955
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
9672d81ca3 Qt4Macros: Don't AUTOMOC or AUTOUIC qt4-generated files
800b2fcf80 Qt4Macros: Use get_property/set_property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2066
|
| |
| |
| |
| |
| |
| |
| | |
Suppress AUTOMOC and AUTOUIC on files generated by Qt4 wrapping macros;
particularly, those generated by `qt4_wrap_cpp`, `qt4_wrap_ui`, and
`qt4_add_resources`. None of these should need AUTOMOC or AUTOUIC
treatment, and CMP0071 makes it important to mark this explicitly.
|
| |\
| | |
| | |
| | | |
Merge-request: !2058
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
92ac721a44 FindPkgConfig: export the list of found libraries also as variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2068
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f739752ad6 CPack: Add NuGet support
dd43e6fe89 Tests: Format `RunCPackVerifyResult.cmake` more consistently
43582cda57 Tests: Fix comment for finding dpkg tool
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1972
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create a CPack generator that uses `nuget.exe` to create packages:
https://docs.microsoft.com/en-us/nuget/what-is-nuget
NuGet packages could be easily produced from a `*.nuspec` file (running
`nuget pack` in the directory w/ the spec file). The spec filename does
not affect the result `*.nupkg` name -- only `id` and `version` elements
of the spec are used (by NuGet).
Some implementation details:
* Minimize C++ code -- use CMake script do to the job. It just let the
base class (`cmCPackGenerator`) to preinstall everything to a temp
directory, render the spec file and run `nuget pack` in it, harvesting
`*.nupkg` files...;
* Ignore package name (and use default paths) prepared by the base class
(only `CPACK_TEMPORARY_DIRECTORY` is important) -- final package
filename is a responsibility of NuGet, so after generation just scan the
temp directory for the result `*.nupkg` file(s) and update
`packageFileNames` data-member of the generator;
* The generator supports _all-in-one_ (default), _one-group-per-package_
and _one-component-per-package_ modes.
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
e567d7eb63 add_library: Restore error on alias of non-global imported target
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2058
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In commit v3.11.0-rc1~433^2~1 (Add support for IMPORTED GLOBAL targets
to be aliased, 2017-09-14) we accidentally dropped the error on calling
`add_library` to alias an imported target that is not globally visible.
The `add_executable` command's equivalent check was properly updated.
Restore the check in `add_library` with the same update. Also fix the
test case accordingly.
Fixes: #17982
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
This change reworks ctest_start() so that simply calling
ctest_start(APPEND) will read all the information from the TAG file.
On top of that, it relaxes the argument parsing for ctest_start() to
allow greater flexibility in the argument ordering, and the documentation
for ctest_start() has been cleaned up.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
e15adbfed3 Help: Specify COMPILE_OPTIONS and COMPILE_FLAGS source properties usage
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2043
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
Add a synopsis section at the top summarizing all signatures.
Issue: #17948
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Summarize the command signatures in one block at the top of the
documentation as is typical in Unix command-line tool manuals.
Make the mode keywords links to the corresponding full signature
and documentation.
Issue: #17948
|
| |
| |
| |
| |
| | |
The LENGTH, GET, JOIN, and SUBLIST operations all read the list without
modifying it. Name their section appropriately.
|
| |
| |
| |
| | |
Prepare for the addition of section headers for grouping commands.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
af1c48871c CPack: Use project version as default for `CPACK_PACKAGE_VERSION`
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Harry Mallon <hjmallon@gmail.com>
Merge-request: !2020
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Introduce `CMAKE_PROJECT_VERSION` and the corresponsing components:
`CMAKE_PROJECT_VERSION_MAJOR`, `CMAKE_PROJECT_VERSION_MINOR`,
`CMAKE_PROJECT_VERSION_PATCH` and `CMAKE_PROJECT_VERSION_TWEAK`.
* `CPack` module use `CMAKE_PROJECT_VERSION_MAJOR`,
`CMAKE_PROJECT_VERSION_MINOR` and `CMAKE_PROJECT_VERSION_PATCH`
to initialize corresponsing CPack variables.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
7e8046e20b Help: add release notes for NAMELINK_COMPONENT
c02eeb0853 Help: clarify "undefined behavior" in install(EXPORT) command
edcb545a24 install: add test for new NAMELINK_COMPONENT parameter
0212d7c762 install: add NAMELINK_COMPONENT argument
cbb609072f Help: clean up install(TARGETS) documentation
b81280ba1f Help: add list of command signatures to top of INSTALL page
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex Turbov <i.zaufi@gmail.com>
Merge-request: !1982
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The "undefined behavior" that the install(EXPORT) command warned about
was simply the possibility of build errors (or other errors) if the
referenced targets aren't installed. As long as the referenced targets
are installed, this won't be an issue.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For shared libraries, this allows you to specify separate components
for the shared library and for the namelink.
Suggested in https://cmake.org/pipermail/cmake-developers/2014-December/024032.html.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The documentation for install(TARGETS) has been rearranged so that
the options are presented as a list, for better readability and
maintenance.
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
6dd11ffbde Help: Clarify add_custom_command build event execution order
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2030
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #17949
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Document the `=` in the option name. Clarify the term "named pipe" as
an abstraction of local domain sockets on Unix and named pipes on
Windows.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
9a8687121f Help: Improve accuracy, readability and cross-referencing of cpack docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2013
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
This is primarily a cleanup of the cpack(1) page. The cpack.cxx file
and CPack module were also updated to make the docs relating to
the generator specification and option names consistent in all
three places.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
83ed65cdde Add generator expressions for VS_SHADER_ source file properties.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2000
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
8d1ccbc693 VS: Add VS_SHADER_OBJECT_FILE_NAME source file property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1997
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ae09bc774b Help: Add example to CMAKE_<LANG>_CLANG_TIDY
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2002
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #16869
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4d15046edd Genex: Add $<TARGET_GENEX_EVAL:...> and $<GENEX_EVAL:...>
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1984
|
| | |/ /
| |/| |
| | | |
| | | | |
Fixes: #17884
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
76ad2ecb50 Order SYSTEM include directories after non-system directories
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1968
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
An effect of the `-isystem` flag is to search the directory after those
specified via `-I` flags. Make behavior more consistent on compilers
that do not have any `-isystem` flag by explicitly moving system include
directories to the end.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
b1f95e5b14 Fortran: Extend submodule test with great-grandchild
402735314e Fortran: Add support for submodule dependencies
62538b2c4c Fortran: Refactor to treat .mod extension as part of module name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Izaak Beekman <contact@izaakbeekman.com>
Merge-request: !1989
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit v3.7.0-rc1~73^2~1 (Fortran: Add support for submodule
syntax in dependency scanning, 2016-09-05) we support parsing Fortran
sources that use submodule syntax, but it left addition of `.smod`
dependencies to future work. Add it now.
The syntax
submodule (module_name) submodule_name
means the current source requires `module_name.mod` and provides
`module_name@submodule_name.smod`. The syntax
submodule (module_name:submodule_name) nested_submodule_name
means the current source requires `module_name@submodule_name.smod`
provides `module_name@nested_submodule_name.smod`.
Fixes: #17017
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
8e841a473f Cleanup: Fix typos and grammar in docs and code
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1996
|