summaryrefslogtreecommitdiffstats
path: root/Help/variable
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'add-execute_process-command-echo'Brad King2019-04-301-0/+6
|\ | | | | | | | | | | | | | | 044dcf9f8d execute_process: Add option to echo command lines d350fb6889 execute_process: Manage KWSys Process lifetime with unique_ptr Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3165
| * execute_process: Add option to echo command linesBill Hoffman2019-04-191-0/+6
| | | | | | | | | | | | | | | | | | | | Add COMMAND_ECHO option to the execute_process command. This will allow execute_process to show the command it will run. Also add a cmake variable CMAKE_EXECUTE_PROCESS_COMMAND_ECHO. Both the option and the variable can be set to one of the following: STDERR|STDOUT|NONE. The command will be printed to stderr or stdout or not at all. Fixes: #18933
* | Merge topic 'vs-default-platform'Brad King2019-04-222-1/+12
|\ \ | | | | | | | | | | | | | | | | | | db02be85a0 VS: Provide the default platform name to project code Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3246
| * | VS: Provide the default platform name to project codeBrad King2019-04-192-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio generators based on `CMAKE_GENERATOR_PLATFORM` or some default. Prior to the VS 2019 generator, the default was always `Win32`. However, for the `Visual Studio 16 2019` generator, the default is based on the host platform. Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for use by project code. This is particularly useful in toolchain files because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so `CMAKE_VS_PLATFORM_NAME` is not yet known. Of course the toolchain file author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that will be used. Fixes: #19177
| * | Merge branch 'docs-xcode-schemes' into release-3.14Brad King2019-03-061-15/+10
| |\ \ | | | | | | | | | | | | Merge-request: !3066
| * \ \ Merge branch 'ios-docs' into release-3.14Brad King2019-03-051-0/+3
| |\ \ \ | | | | | | | | | | | | | | | Merge-request: !3047
* | | | | MSVC: Add abstraction for runtime library selectionBrad King2019-04-171-0/+27
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace our hard-coded defaults for `/MD` and `/MDd` with a first-class abstraction to select the runtime library from an enumeration of logical names. We've long hesitated to do this because the idea of "runtime library selection" touches on related concepts on several platforms. Avoid that scope creep by simply defining an abstraction that applies only when targeting the MSVC ABI on Windows. Removing the old default flags requires a policy because existing projects may rely on string processing to edit them and choose a runtime library under the old behavior. Add policy CMP0091 to provide compatibility. Fixes: #19108
* | | | Modules: Update documentation formattingBartosz Kosiorek2019-04-082-2/+2
| | | |
* | | | Help: Improve formatting of Help documentationBartosz Kosiorek2019-04-089-17/+17
| | | |
* | | | Merge topic 'improve-documentation'Brad King2019-04-043-5/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 456e0fb64f Help: Improve documentation formating Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3174
| * | | | Help: Improve documentation formatingBartosz Kosiorek2019-04-043-5/+6
| | | | |
* | | | | project: Add variable CMAKE_PROJECT_INCLUDE_BEFORERuslan Baratov2019-04-011-0/+6
| | | | |
* | | | | project: Add variable CMAKE_PROJECT_INCLUDERuslan Baratov2019-03-271-0/+6
|/ / / /
* | | | Merge topic 'ghs-linux'Brad King2019-03-221-1/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2c43fb5be3 FindThreads: Fix pthread library check in GHS Multi Generator 0404efe786 GHS: Add support for GHS Multi Generator in Linux 2060a1445c Tests: Fix file name case in GHS object library test ddad70c8a4 Tests: Run GHS tests in a separate ctest process f7dca1fc97 GHS: Fix include-what-you-use and clang-tidy diagnostics Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3006
| * | | | GHS: Add support for GHS Multi Generator in LinuxNaren Manimohan2019-03-211-1/+2
| | | | |
* | | | | Xcode: Create Xcode schemes per targetHarry Mallon2019-03-2116-43/+18
| | | | |
* | | | | Merge topic 'export-package-default-off'Brad King2019-03-152-2/+22
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9bede5c4ce export: Disable PACKAGE mode user package registry by default Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Lukas Mosimann <lumosimann@gmail.com> Merge-request: !3041
| * | | | export: Disable PACKAGE mode user package registry by defaultRobert Maynard2019-03-152-2/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The user package registry populated by the `export()` command causes side effects outside the build and source directories. Such effects should be opt-in rather than op-out. Introduce a policy to change default behavior of `export(PACKAGE)` to do nothing.
* | | | | XCode: Add scheme option XCODE_SCHEME_DEBUG_AS_ROOTHarry Mallon2019-03-111-0/+1
| | | | |
* | | | | Merge topic 'docs-xcode-schemes'Brad King2019-03-061-15/+10
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d0cb912a28 Help: Remove note that Xcode scheme generator is experimental de850fe385 Help: Trivial typo fix for CMAKE_XCODE_GENERATE_SCHEME d61a5a20ef Help: Sort lists of (CMAKE_)XCODE_SCHEME_... variables and properties Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3066
| * | | | Help: Remove note that Xcode scheme generator is experimentalCraig Scott2019-03-061-5/+0
| | | | |
| * | | | Help: Trivial typo fix for CMAKE_XCODE_GENERATE_SCHEMECraig Scott2019-03-061-1/+1
| | | | |
| * | | | Help: Sort lists of (CMAKE_)XCODE_SCHEME_... variables and propertiesCraig Scott2019-03-061-9/+9
| | | | |
* | | | | Merge topic 'ios-docs'Brad King2019-03-061-0/+3
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 376138fe0c Help: CMAKE_MACOSX_BUNDLE is ON for iOS/tvOS/watchOS f7d602b572 Help: Example of tweaking iOS/tvOS/watchOS build 4a9e2e4f35 Help: find_package with fat iOS libraries Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3047
| * | | | Help: CMAKE_MACOSX_BUNDLE is ON for iOS/tvOS/watchOSRuslan Baratov2019-03-051-0/+3
| |/ / /
* | | | Merge topic 'ios-variable'Brad King2019-03-061-0/+4
|\ \ \ \ | |_|/ / |/| | / | | |/ | |/| | | | | | | e427c7c1d8 iOS: Add IOS variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3051
| * | iOS: Add IOS variableRuslan Baratov2019-03-051-0/+4
| |/ | | | | | | | | | | | | Since commit 11da882a12 (Apple: Introduce separate system name for iOS, tvOS, and watchOS, 2018-01-15, v3.14.0-rc1~14^2~1) we support setting `CMAKE_SYSTEM_NAME` to `iOS`. Existing iOS toolchain files already set `IOS` as a short-hand variable, so do the same here.
| * Merge branch 'fix-implicit-includes-fortran' into release-3.14Brad King2019-02-201-1/+6
| |\ | | | | | | | | | Merge-request: !2994
* | | XLClang: Add policy CMP0089 to present as XL for compatibilityBrad King2019-02-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | We now identify IBM's Clang-based XL compilers, which define `__ibmxl__`, as `XLClang` rather than `XL`. In order to support existing project code that checks for `XL`, add a policy whose OLD behavior is to present the compiler id as `XL` and whose NEW behavior is to present the compiler id as `XLClang` as we really detect it.
* | | Merge topic 'drop-MIPSpro'Brad King2019-02-251-1/+0
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 214fcefa52 Remove now-unused code once used for MIPSpro on IRIX Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3004
| * | | Remove now-unused code once used for MIPSpro on IRIXBrad King2019-02-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | In commit beb991110d (Remove now-unused code once used on IRIX, 2019-01-11, v3.14.0-rc1~167^2) we removed remnants of IRIX support. Also remove remnants of MIPSpro compiler support.
* | | | Merge topic 'fix-implicit-includes-fortran'Brad King2019-02-251-1/+6
|\ \ \ \ | |/ / / |/| | / | | |/ | |/| | | | | | | | | | 3dc81a48ff Fortran: Do not suppress explicit use of implicit include directories Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Michael Hirsch, Ph.D. <michael@scivision.co> Merge-request: !2994
| * | Fortran: Do not suppress explicit use of implicit include directoriesBrad King2019-02-201-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 2e91627dea (ParseImplicitIncludeInfo: add Fortran implicit include handling, 2019-01-25, v3.14.0-rc1~73^2) we actually populate `CMAKE_Fortran_IMPLICIT_INCLUDE_DIRECTORIES` for the first time. This value may be useful to project code to pass to other tooling that wants to preprocess the way Fortran does, so we should compute the value. However, compilers like `gfortran` do not actually search their own implicit include directories for `.mod` files. The directories must be passed via `-I` in order for `.mod` files in them to be found. Since Fortran has no standard library header files that we need to avoid overriding, it is safe to *not* filter out implicit include directories from those passed explicitly via `-I` options. Skip this filtering so that include directories specified by project code to find `.mod` files will be searched by the compiler even if they happen to be implicitly searched by the preprocessor. Fixes: #18914
* | | Xcode: Require at least Xcode 5Gregor Jasny2019-02-161-6/+2
| |/ |/|
* | GHS: Document usage of GHS_NO_SOURCE_GROUP_FILEFred Baksik2019-02-081-0/+6
|/ | | | -- Also change variable name to CMAKE_GHS_NO_SOURCE_GROUP_FILE
* Xcode: Update default Swift language version for Xcode 10.2Brad King2019-02-041-2/+6
| | | | | | Xcode 10.2 no longer supports Swift language versions before 4.0. Fixes: #18871
* Help: improve details on `CMAKE_LANG_CREATE_SHARED_*`Saleem Abdulrasool2019-01-312-2/+4
| | | | | Add a note that the `CMAKE_<LANG>_CREATE_SHARED_*` rule variables are semicolon delimited lists that can run multiple commands.
* Merge topic 'variables1'Brad King2019-01-311-2/+5
|\ | | | | | | | | | | | | | | | | 9d20fe014f Help: moved 7 variables to "internal" section dfb2d6178e Help: "internal variables" instead of "obsolete", with some explanatory prose 9c4cdc43f6 Help: declare CMAKE_HOME_DIRECTORY obsolete Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2881
| * Help: declare CMAKE_HOME_DIRECTORY obsoleteJoachim Wuttke (o)2019-01-301-2/+5
| |
* | Merge topic 'msys_docs'Brad King2019-01-311-0/+4
|\ \ | | | | | | | | | | | | | | | | | | ec027aa64a Help: Add documentation for MSYS variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2882
| * | Help: Add documentation for MSYS variableHarry Mallon2019-01-301-0/+4
| |/
* | DOCS: put Flang in alphabetical orderMichael Hirsch, Ph.D2019-01-291-1/+1
|/
* VS: Add support for explicit 32-bit toolset selection via host=x86Brad King2019-01-282-7/+7
| | | | | Generalize the ``host=x64`` option in `CMAKE_GENERATOR_TOOLSET` to also support ``host=x86``.
* cmMakefile: Impose maximum recursion limitKyle Edwards2019-01-231-0/+33
| | | | | | | | | In order to keep infinitely-recursive scripts from causing a stack overflow in the CMake executable, CMake now imposes a maximum recursion limit before issuing an error message. The limit can be adjusted at runtime with CMAKE_MAXIMUM_RECURSION_DEPTH. Fixes: #18694
* Merge topic 'find-package-resolve-symlinks'Brad King2019-01-211-0/+10
|\ | | | | | | | | | | | | | | b773e58099 find_package: add test coverage for CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS a5e948a36f find_package: optionally resolve symlinks when discovering packages Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2798
| * find_package: optionally resolve symlinks when discovering packagesDavid Aguilar2019-01-161-0/+10
| | | | | | | | | | | | | | | | | | Teach find_package() to resolve symlinks when constructing relocatable prefix paths from discovered cmake config files. The `CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS` variable enables this behavior when set to `TRUE`. Fixes: #18704
* | Merge topic 'submit-url'Brad King2019-01-211-0/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2915a75615 CTest: Add documentation and release notes for SubmitURL d6475daa79 Modules/CTest: Set SubmitURL 938f06fda6 ctest_submit: Add parameter SUBMIT_URL 65e725c957 CTest: Add option SubmitURL 65f1fc9d63 CTest: Add function GetSubmitURL 2bedd5fb7c ctest_submit: Remove submit method from log output Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2719
| * | CTest: Add documentation and release notes for SubmitURLRegina Pfeifer2019-01-161-0/+5
| |/
* | GHS: Add Compiler ID detectionFred Baksik2019-01-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | -- Detect GHS compiler and version Detect ARCHITECTURE_ID for PPC / ARM / 86 targets Detect PLATFORM_ID for Integrity and Integrity178 platforms Using defines specified in the documents for the compilers: 201416 PPC / 201754 ARM / 201714 86 -- Fallback C/CXX compiler ID to GHS if not otherwise detected and using GHS MULTI generator Works around issue with some GHS compilers not setting __ghs__ compiler define -- Tweak Compiler ID checking so major id of 002017 is not replaced with 217 -- Prefer try_compile() library targets when testing for working GHS compilers -- Avoid CMake errors if reading past end of file for checking if file is PE executable
* | GHS: Integrity Application updatesFred Baksik2019-01-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -- Check the property "ghs_integrity_app" on executables to set [INTEGRITY Application] If the property is not set then check if an integrate file is one of the source files (.int file). Dynamic Downloads that do not have an integrate file can use this property along with setting the compiler flag "-dynamic". -- Remove parsing for -dynamic flag; it is only used to print a comment The MULTI GUI will show if it is a Monolith or Dynamic Download application -- Use project references to specify which executables are part of the Integrity Application Usually Implicit Dependency Analysis will ensure that executable targets become part of the application. This does not work for Dynamic Download without integrate files. Use `add_dependencies(dd vas)` to mark that the vas target is part of dd target. -- Update file locations in the Integrate files.