Update Darwin CMake prebuilt to 3.22.1 Fusion2: http://fusion2/610fb8e3-5633-41a6-b50b-ed5819f55cd6 GCS path: gs://ndk-kokoro-release-artifacts/prod/ndk/cmake/darwin_release/3/20211215-131219 Prebuilt updated using: ndk/scripts/update_kokoro_prebuilts.py Test: Treehugger, Kokoro presubmit Bug: http://b/213946898 Change-Id: Icbb6d90cad49dbe67f168075508872b1704d9f61
diff --git a/bin/ccmake b/bin/ccmake index a05fde2..3ec5e8e 100755 --- a/bin/ccmake +++ b/bin/ccmake Binary files differ
diff --git a/bin/cmake b/bin/cmake index 5434528..67fbd69 100755 --- a/bin/cmake +++ b/bin/cmake Binary files differ
diff --git a/bin/cpack b/bin/cpack index 37aefe4..adca012 100755 --- a/bin/cpack +++ b/bin/cpack Binary files differ
diff --git a/bin/ctest b/bin/ctest index f5f6d6a..fe2db5b 100755 --- a/bin/ctest +++ b/bin/ctest Binary files differ
diff --git a/doc/cmake-3.18/Copyright.txt b/doc/cmake-3.18/Copyright.txt deleted file mode 100644 index b867d01..0000000 --- a/doc/cmake-3.18/Copyright.txt +++ /dev/null
@@ -1,132 +0,0 @@ -CMake - Cross Platform Makefile Generator -Copyright 2000-2020 Kitware, Inc. and Contributors -All rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: - -* Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - -* Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in the - documentation and/or other materials provided with the distribution. - -* Neither the name of Kitware, Inc. nor the names of Contributors - may be used to endorse or promote products derived from this - software without specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS -"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT -LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT -HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT -LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, -DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY -THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT -(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE -OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - ------------------------------------------------------------------------------- - -The following individuals and institutions are among the Contributors: - -* Aaron C. Meadows <cmake@shadowguarddev.com> -* Adriaan de Groot <groot@kde.org> -* Aleksey Avdeev <solo@altlinux.ru> -* Alexander Neundorf <neundorf@kde.org> -* Alexander Smorkalov <alexander.smorkalov@itseez.com> -* Alexey Sokolov <sokolov@google.com> -* Alex Merry <alex.merry@kde.org> -* Alex Turbov <i.zaufi@gmail.com> -* Andreas Pakulat <apaku@gmx.de> -* Andreas Schneider <asn@cryptomilk.org> -* André Rigland Brodtkorb <Andre.Brodtkorb@ifi.uio.no> -* Axel Huebl, Helmholtz-Zentrum Dresden - Rossendorf -* Benjamin Eikel -* Bjoern Ricks <bjoern.ricks@gmail.com> -* Brad Hards <bradh@kde.org> -* Christopher Harvey -* Christoph Grüninger <foss@grueninger.de> -* Clement Creusot <creusot@cs.york.ac.uk> -* Daniel Blezek <blezek@gmail.com> -* Daniel Pfeifer <daniel@pfeifer-mail.de> -* Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> -* Eran Ifrah <eran.ifrah@gmail.com> -* Esben Mose Hansen, Ange Optimization ApS -* Geoffrey Viola <geoffrey.viola@asirobots.com> -* Google Inc -* Gregor Jasny -* Helio Chissini de Castro <helio@kde.org> -* Ilya Lavrenov <ilya.lavrenov@itseez.com> -* Insight Software Consortium <insightsoftwareconsortium.org> -* Jan Woetzel -* Julien Schueller -* Kelly Thompson <kgt@lanl.gov> -* Laurent Montel <montel@kde.org> -* Konstantin Podsvirov <konstantin@podsvirov.pro> -* Mario Bensi <mbensi@ipsquad.net> -* Martin Gräßlin <mgraesslin@kde.org> -* Mathieu Malaterre <mathieu.malaterre@gmail.com> -* Matthaeus G. Chajdas -* Matthias Kretz <kretz@kde.org> -* Matthias Maennich <matthias@maennich.net> -* Michael Hirsch, Ph.D. <www.scivision.co> -* Michael Stürmer -* Miguel A. Figueroa-Villanueva -* Mike Jackson -* Mike McQuaid <mike@mikemcquaid.com> -* Nicolas Bock <nicolasbock@gmail.com> -* Nicolas Despres <nicolas.despres@gmail.com> -* Nikita Krupen'ko <krnekit@gmail.com> -* NVIDIA Corporation <www.nvidia.com> -* OpenGamma Ltd. <opengamma.com> -* Patrick Stotko <stotko@cs.uni-bonn.de> -* Per Øyvind Karlsen <peroyvind@mandriva.org> -* Peter Collingbourne <peter@pcc.me.uk> -* Petr Gotthard <gotthard@honeywell.com> -* Philip Lowman <philip@yhbt.com> -* Philippe Proulx <pproulx@efficios.com> -* Raffi Enficiaud, Max Planck Society -* Raumfeld <raumfeld.com> -* Roger Leigh <rleigh@codelibre.net> -* Rolf Eike Beer <eike@sf-mail.de> -* Roman Donchenko <roman.donchenko@itseez.com> -* Roman Kharitonov <roman.kharitonov@itseez.com> -* Ruslan Baratov -* Sebastian Holtermann <sebholt@xwmw.org> -* Stephen Kelly <steveire@gmail.com> -* Sylvain Joubert <joubert.sy@gmail.com> -* The Qt Company Ltd. -* Thomas Sondergaard <ts@medical-insight.com> -* Tobias Hunger <tobias.hunger@qt.io> -* Todd Gamblin <tgamblin@llnl.gov> -* Tristan Carel -* University of Dundee -* Vadim Zhukov -* Will Dicharry <wdicharry@stellarscience.com> - -See version control history for details of individual contributions. - -The above copyright and license notice applies to distributions of -CMake in source and binary form. Third-party software packages supplied -with CMake under compatible licenses provide their own copyright notices -documented in corresponding subdirectories or source files. - ------------------------------------------------------------------------------- - -CMake was initially developed by Kitware with the following sponsorship: - - * National Library of Medicine at the National Institutes of Health - as part of the Insight Segmentation and Registration Toolkit (ITK). - - * US National Labs (Los Alamos, Livermore, Sandia) ASC Parallel - Visualization Initiative. - - * National Alliance for Medical Image Computing (NAMIC) is funded by the - National Institutes of Health through the NIH Roadmap for Medical Research, - Grant U54 EB005149. - - * Kitware, Inc.
diff --git a/doc/cmake-3.18/cmcurl/COPYING b/doc/cmake-3.18/cmcurl/COPYING deleted file mode 100644 index 9d9e4af..0000000 --- a/doc/cmake-3.18/cmcurl/COPYING +++ /dev/null
@@ -1,22 +0,0 @@ -COPYRIGHT AND PERMISSION NOTICE - -Copyright (c) 1996 - 2020, Daniel Stenberg, <daniel@haxx.se>, and many -contributors, see the THANKS file. - -All rights reserved. - -Permission to use, copy, modify, and distribute this software for any purpose -with or without fee is hereby granted, provided that the above copyright -notice and this permission notice appear in all copies. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN -NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, -DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR -OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE -OR OTHER DEALINGS IN THE SOFTWARE. - -Except as contained in this notice, the name of a copyright holder shall not -be used in advertising or otherwise to promote the sale, use or other dealings -in this Software without prior written authorization of the copyright holder.
diff --git a/doc/cmake-3.18/cmlibarchive/COPYING b/doc/cmake-3.18/cmlibarchive/COPYING deleted file mode 100644 index 14bbefa..0000000 --- a/doc/cmake-3.18/cmlibarchive/COPYING +++ /dev/null
@@ -1,66 +0,0 @@ -The libarchive distribution as a whole is Copyright by Tim Kientzle -and is subject to the copyright notice reproduced at the bottom of -this file. - -Each individual file in this distribution should have a clear -copyright/licensing statement at the beginning of the file. If any do -not, please let me know and I will rectify it. The following is -intended to summarize the copyright status of the individual files; -the actual statements in the files are controlling. - -* Except as listed below, all C sources (including .c and .h files) - and documentation files are subject to the copyright notice reproduced - at the bottom of this file. - -* The following source files are also subject in whole or in part to - a 3-clause UC Regents copyright; please read the individual source - files for details: - libarchive/archive_entry.c - libarchive/archive_read_support_filter_compress.c - libarchive/archive_write_add_filter_compress.c - libarchive/mtree.5 - -* The following source files are in the public domain: - libarchive/archive_getdate.c - -* The following source files are triple-licensed with the ability to choose - from CC0 1.0 Universal, OpenSSL or Apache 2.0 licenses: - libarchive/archive_blake2.h - libarchive/archive_blake2_impl.h - libarchive/archive_blake2s_ref.c - libarchive/archive_blake2sp_ref.c - -* The build files---including Makefiles, configure scripts, - and auxiliary scripts used as part of the compile process---have - widely varying licensing terms. Please check individual files before - distributing them to see if those restrictions apply to you. - -I intend for all new source code to use the license below and hope over -time to replace code with other licenses with new implementations that -do use the license below. The varying licensing of the build scripts -seems to be an unavoidable mess. - - -Copyright (c) 2003-2018 <author(s)> -All rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions -are met: -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer - in this position and unchanged. -2. Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in the - documentation and/or other materials provided with the distribution. - -THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY EXPRESS OR -IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES -OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. -IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, -INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT -NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, -DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY -THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT -(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF -THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/doc/cmake-3.22/Copyright.txt b/doc/cmake-3.22/Copyright.txt new file mode 100644 index 0000000..7f51293 --- /dev/null +++ b/doc/cmake-3.22/Copyright.txt
@@ -0,0 +1,132 @@ +CMake - Cross Platform Makefile Generator +Copyright 2000-2021 Kitware, Inc. and Contributors +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + +* Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + +* Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +* Neither the name of Kitware, Inc. nor the names of Contributors + may be used to endorse or promote products derived from this + software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR +A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT +HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +------------------------------------------------------------------------------ + +The following individuals and institutions are among the Contributors: + +* Aaron C. Meadows <cmake@shadowguarddev.com> +* Adriaan de Groot <groot@kde.org> +* Aleksey Avdeev <solo@altlinux.ru> +* Alexander Neundorf <neundorf@kde.org> +* Alexander Smorkalov <alexander.smorkalov@itseez.com> +* Alexey Sokolov <sokolov@google.com> +* Alex Merry <alex.merry@kde.org> +* Alex Turbov <i.zaufi@gmail.com> +* Andreas Pakulat <apaku@gmx.de> +* Andreas Schneider <asn@cryptomilk.org> +* André Rigland Brodtkorb <Andre.Brodtkorb@ifi.uio.no> +* Axel Huebl, Helmholtz-Zentrum Dresden - Rossendorf +* Benjamin Eikel +* Bjoern Ricks <bjoern.ricks@gmail.com> +* Brad Hards <bradh@kde.org> +* Christopher Harvey +* Christoph Grüninger <foss@grueninger.de> +* Clement Creusot <creusot@cs.york.ac.uk> +* Daniel Blezek <blezek@gmail.com> +* Daniel Pfeifer <daniel@pfeifer-mail.de> +* Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> +* Eran Ifrah <eran.ifrah@gmail.com> +* Esben Mose Hansen, Ange Optimization ApS +* Geoffrey Viola <geoffrey.viola@asirobots.com> +* Google Inc +* Gregor Jasny +* Helio Chissini de Castro <helio@kde.org> +* Ilya Lavrenov <ilya.lavrenov@itseez.com> +* Insight Software Consortium <insightsoftwareconsortium.org> +* Jan Woetzel +* Julien Schueller +* Kelly Thompson <kgt@lanl.gov> +* Konstantin Podsvirov <konstantin@podsvirov.pro> +* Laurent Montel <montel@kde.org> +* Mario Bensi <mbensi@ipsquad.net> +* Martin Gräßlin <mgraesslin@kde.org> +* Mathieu Malaterre <mathieu.malaterre@gmail.com> +* Matthaeus G. Chajdas +* Matthias Kretz <kretz@kde.org> +* Matthias Maennich <matthias@maennich.net> +* Michael Hirsch, Ph.D. <www.scivision.co> +* Michael Stürmer +* Miguel A. Figueroa-Villanueva +* Mike Jackson +* Mike McQuaid <mike@mikemcquaid.com> +* Nicolas Bock <nicolasbock@gmail.com> +* Nicolas Despres <nicolas.despres@gmail.com> +* Nikita Krupen'ko <krnekit@gmail.com> +* NVIDIA Corporation <www.nvidia.com> +* OpenGamma Ltd. <opengamma.com> +* Patrick Stotko <stotko@cs.uni-bonn.de> +* Per Øyvind Karlsen <peroyvind@mandriva.org> +* Peter Collingbourne <peter@pcc.me.uk> +* Petr Gotthard <gotthard@honeywell.com> +* Philip Lowman <philip@yhbt.com> +* Philippe Proulx <pproulx@efficios.com> +* Raffi Enficiaud, Max Planck Society +* Raumfeld <raumfeld.com> +* Roger Leigh <rleigh@codelibre.net> +* Rolf Eike Beer <eike@sf-mail.de> +* Roman Donchenko <roman.donchenko@itseez.com> +* Roman Kharitonov <roman.kharitonov@itseez.com> +* Ruslan Baratov +* Sebastian Holtermann <sebholt@xwmw.org> +* Stephen Kelly <steveire@gmail.com> +* Sylvain Joubert <joubert.sy@gmail.com> +* The Qt Company Ltd. +* Thomas Sondergaard <ts@medical-insight.com> +* Tobias Hunger <tobias.hunger@qt.io> +* Todd Gamblin <tgamblin@llnl.gov> +* Tristan Carel +* University of Dundee +* Vadim Zhukov +* Will Dicharry <wdicharry@stellarscience.com> + +See version control history for details of individual contributions. + +The above copyright and license notice applies to distributions of +CMake in source and binary form. Third-party software packages supplied +with CMake under compatible licenses provide their own copyright notices +documented in corresponding subdirectories or source files. + +------------------------------------------------------------------------------ + +CMake was initially developed by Kitware with the following sponsorship: + + * National Library of Medicine at the National Institutes of Health + as part of the Insight Segmentation and Registration Toolkit (ITK). + + * US National Labs (Los Alamos, Livermore, Sandia) ASC Parallel + Visualization Initiative. + + * National Alliance for Medical Image Computing (NAMIC) is funded by the + National Institutes of Health through the NIH Roadmap for Medical Research, + Grant U54 EB005149. + + * Kitware, Inc.
diff --git a/doc/cmake-3.22/cmcurl/COPYING b/doc/cmake-3.22/cmcurl/COPYING new file mode 100644 index 0000000..48f1447 --- /dev/null +++ b/doc/cmake-3.22/cmcurl/COPYING
@@ -0,0 +1,22 @@ +COPYRIGHT AND PERMISSION NOTICE + +Copyright (c) 1996 - 2021, Daniel Stenberg, <daniel@haxx.se>, and many +contributors, see the THANKS file. + +All rights reserved. + +Permission to use, copy, modify, and distribute this software for any purpose +with or without fee is hereby granted, provided that the above copyright +notice and this permission notice appear in all copies. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN +NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR +OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE +OR OTHER DEALINGS IN THE SOFTWARE. + +Except as contained in this notice, the name of a copyright holder shall not +be used in advertising or otherwise to promote the sale, use or other dealings +in this Software without prior written authorization of the copyright holder.
diff --git a/doc/cmake-3.22/cmlibarchive/COPYING b/doc/cmake-3.22/cmlibarchive/COPYING new file mode 100644 index 0000000..1b97235 --- /dev/null +++ b/doc/cmake-3.22/cmlibarchive/COPYING
@@ -0,0 +1,65 @@ +The libarchive distribution as a whole is Copyright by Tim Kientzle +and is subject to the copyright notice reproduced at the bottom of +this file. + +Each individual file in this distribution should have a clear +copyright/licensing statement at the beginning of the file. If any do +not, please let me know and I will rectify it. The following is +intended to summarize the copyright status of the individual files; +the actual statements in the files are controlling. + +* Except as listed below, all C sources (including .c and .h files) + and documentation files are subject to the copyright notice reproduced + at the bottom of this file. + +* The following source files are also subject in whole or in part to + a 3-clause UC Regents copyright; please read the individual source + files for details: + libarchive/archive_read_support_filter_compress.c + libarchive/archive_write_add_filter_compress.c + libarchive/mtree.5 + +* The following source files are in the public domain: + libarchive/archive_getdate.c + +* The following source files are triple-licensed with the ability to choose + from CC0 1.0 Universal, OpenSSL or Apache 2.0 licenses: + libarchive/archive_blake2.h + libarchive/archive_blake2_impl.h + libarchive/archive_blake2s_ref.c + libarchive/archive_blake2sp_ref.c + +* The build files---including Makefiles, configure scripts, + and auxiliary scripts used as part of the compile process---have + widely varying licensing terms. Please check individual files before + distributing them to see if those restrictions apply to you. + +I intend for all new source code to use the license below and hope over +time to replace code with other licenses with new implementations that +do use the license below. The varying licensing of the build scripts +seems to be an unavoidable mess. + + +Copyright (c) 2003-2018 <author(s)> +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: +1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer + in this position and unchanged. +2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/doc/cmake-3.18/cmliblzma/COPYING b/doc/cmake-3.22/cmliblzma/COPYING similarity index 100% rename from doc/cmake-3.18/cmliblzma/COPYING rename to doc/cmake-3.22/cmliblzma/COPYING
diff --git a/doc/cmake-3.18/cmlibrhash/COPYING b/doc/cmake-3.22/cmlibrhash/COPYING similarity index 100% rename from doc/cmake-3.18/cmlibrhash/COPYING rename to doc/cmake-3.22/cmlibrhash/COPYING
diff --git a/doc/cmake-3.18/cmlibuv/LICENSE b/doc/cmake-3.22/cmlibuv/LICENSE similarity index 100% rename from doc/cmake-3.18/cmlibuv/LICENSE rename to doc/cmake-3.22/cmlibuv/LICENSE
diff --git a/doc/cmake-3.18/cmnghttp2/COPYING b/doc/cmake-3.22/cmnghttp2/COPYING similarity index 100% rename from doc/cmake-3.18/cmnghttp2/COPYING rename to doc/cmake-3.22/cmnghttp2/COPYING
diff --git a/doc/cmake-3.18/cmsys/Copyright.txt b/doc/cmake-3.22/cmsys/Copyright.txt similarity index 100% rename from doc/cmake-3.18/cmsys/Copyright.txt rename to doc/cmake-3.22/cmsys/Copyright.txt
diff --git a/doc/cmake-3.18/cmzlib/Copyright.txt b/doc/cmake-3.22/cmzlib/Copyright.txt similarity index 100% rename from doc/cmake-3.18/cmzlib/Copyright.txt rename to doc/cmake-3.22/cmzlib/Copyright.txt
diff --git a/doc/cmake-3.18/cmzstd/LICENSE b/doc/cmake-3.22/cmzstd/LICENSE similarity index 100% rename from doc/cmake-3.18/cmzstd/LICENSE rename to doc/cmake-3.22/cmzstd/LICENSE
diff --git a/share/cmake-3.18/Help/command/DEVICE_LINK_OPTIONS.txt b/share/cmake-3.18/Help/command/DEVICE_LINK_OPTIONS.txt deleted file mode 100644 index 3f0226f..0000000 --- a/share/cmake-3.18/Help/command/DEVICE_LINK_OPTIONS.txt +++ /dev/null
@@ -1,11 +0,0 @@ - -When a device link step is involved, which is controlled by -:prop_tgt:`CUDA_SEPARABLE_COMPILATION` and -:prop_tgt:`CUDA_RESOLVE_DEVICE_SYMBOLS` properties and policy :policy:`CMP0105`, -the raw options will be delivered to the host and device link steps (wrapped in -``-Xcompiler`` or equivalent for device link). Options wrapped with -``$<DEVICE_LINK:...>`` -:manual:`generator expression <cmake-generator-expressions(7)>` will be used -only for the device link step. Options wrapped with ``$<HOST_LINK:...>`` -:manual:`generator expression <cmake-generator-expressions(7)>` will be used -only for the host link step.
diff --git a/share/cmake-3.18/Help/command/FIND_XXX.txt b/share/cmake-3.18/Help/command/FIND_XXX.txt deleted file mode 100644 index 4a62c5b..0000000 --- a/share/cmake-3.18/Help/command/FIND_XXX.txt +++ /dev/null
@@ -1,161 +0,0 @@ -A short-hand signature is: - -.. parsed-literal:: - - |FIND_XXX| (<VAR> name1 [path1 path2 ...]) - -The general signature is: - -.. parsed-literal:: - - |FIND_XXX| ( - <VAR> - name | |NAMES| - [HINTS path1 [path2 ... ENV var]] - [PATHS path1 [path2 ... ENV var]] - [PATH_SUFFIXES suffix1 [suffix2 ...]] - [DOC "cache documentation string"] - [REQUIRED] - [NO_DEFAULT_PATH] - [NO_PACKAGE_ROOT_PATH] - [NO_CMAKE_PATH] - [NO_CMAKE_ENVIRONMENT_PATH] - [NO_SYSTEM_ENVIRONMENT_PATH] - [NO_CMAKE_SYSTEM_PATH] - [CMAKE_FIND_ROOT_PATH_BOTH | - ONLY_CMAKE_FIND_ROOT_PATH | - NO_CMAKE_FIND_ROOT_PATH] - ) - -This command is used to find a |SEARCH_XXX_DESC|. -A cache entry named by ``<VAR>`` is created to store the result -of this command. -If the |SEARCH_XXX| is found the result is stored in the variable -and the search will not be repeated unless the variable is cleared. -If nothing is found, the result will be ``<VAR>-NOTFOUND``. -The ``REQUIRED`` option stops processing with an error message if nothing -is found, otherwise the search will be attempted again the -next time |FIND_XXX| is invoked with the same variable. - -Options include: - -``NAMES`` - Specify one or more possible names for the |SEARCH_XXX|. - - When using this to specify names with and without a version - suffix, we recommend specifying the unversioned name first - so that locally-built packages can be found before those - provided by distributions. - -``HINTS``, ``PATHS`` - Specify directories to search in addition to the default locations. - The ``ENV var`` sub-option reads paths from a system environment - variable. - -``PATH_SUFFIXES`` - Specify additional subdirectories to check below each directory - location otherwise considered. - -``DOC`` - Specify the documentation string for the ``<VAR>`` cache entry. - -``REQUIRED`` - Stop processing with an error message if nothing is found. - -If ``NO_DEFAULT_PATH`` is specified, then no additional paths are -added to the search. -If ``NO_DEFAULT_PATH`` is not specified, the search process is as follows: - -.. |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX_SUBDIR| replace:: - |prefix_XXX_SUBDIR| for each ``<prefix>`` in the - :variable:`<PackageName>_ROOT` CMake variable and the - :envvar:`<PackageName>_ROOT` environment variable if - called from within a find module loaded by - :command:`find_package(<PackageName>)` - -.. |CMAKE_PREFIX_PATH_XXX_SUBDIR| replace:: - |prefix_XXX_SUBDIR| for each ``<prefix>`` in :variable:`CMAKE_PREFIX_PATH` - -.. |SYSTEM_ENVIRONMENT_PREFIX_PATH_XXX_SUBDIR| replace:: - |prefix_XXX_SUBDIR| for each ``<prefix>/[s]bin`` in ``PATH``, and - |entry_XXX_SUBDIR| for other entries in ``PATH`` - -.. |CMAKE_SYSTEM_PREFIX_PATH_XXX_SUBDIR| replace:: - |prefix_XXX_SUBDIR| for each ``<prefix>`` in - :variable:`CMAKE_SYSTEM_PREFIX_PATH` - -1. If called from within a find module or any other script loaded by a call to - :command:`find_package(<PackageName>)`, search prefixes unique to the - current package being found. Specifically, look in the - :variable:`<PackageName>_ROOT` CMake variable and the - :envvar:`<PackageName>_ROOT` environment variable. - The package root variables are maintained as a stack, so if called from - nested find modules or config packages, root paths from the parent's find - module or config package will be searched after paths from the current - module or package. In other words, the search order would be - ``<CurrentPackage>_ROOT``, ``ENV{<CurrentPackage>_ROOT}``, - ``<ParentPackage>_ROOT``, ``ENV{<ParentPackage>_ROOT}``, etc. - This can be skipped if ``NO_PACKAGE_ROOT_PATH`` is passed or by setting - the :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` to ``FALSE``. - See policy :policy:`CMP0074`. - - * |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX| - -2. Search paths specified in cmake-specific cache variables. - These are intended to be used on the command line with a ``-DVAR=value``. - The values are interpreted as :ref:`semicolon-separated lists <CMake Language Lists>`. - This can be skipped if ``NO_CMAKE_PATH`` is passed or by setting the - :variable:`CMAKE_FIND_USE_CMAKE_PATH` to ``FALSE``. - - * |CMAKE_PREFIX_PATH_XXX| - * |CMAKE_XXX_PATH| - * |CMAKE_XXX_MAC_PATH| - -3. Search paths specified in cmake-specific environment variables. - These are intended to be set in the user's shell configuration, - and therefore use the host's native path separator - (``;`` on Windows and ``:`` on UNIX). - This can be skipped if ``NO_CMAKE_ENVIRONMENT_PATH`` is passed or - by setting the :variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH` to ``FALSE``. - - * |CMAKE_PREFIX_PATH_XXX| - * |CMAKE_XXX_PATH| - * |CMAKE_XXX_MAC_PATH| - -4. Search the paths specified by the ``HINTS`` option. - These should be paths computed by system introspection, such as a - hint provided by the location of another item already found. - Hard-coded guesses should be specified with the ``PATHS`` option. - -5. Search the standard system environment variables. - This can be skipped if ``NO_SYSTEM_ENVIRONMENT_PATH`` is passed or by - setting the :variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH` to ``FALSE``. - - * |SYSTEM_ENVIRONMENT_PATH_XXX| - * |SYSTEM_ENVIRONMENT_PATH_WINDOWS_XXX| - -6. Search cmake variables defined in the Platform files - for the current system. This can be skipped if ``NO_CMAKE_SYSTEM_PATH`` - is passed or by setting the :variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH` - to ``FALSE``. - - * |CMAKE_SYSTEM_PREFIX_PATH_XXX| - * |CMAKE_SYSTEM_XXX_PATH| - * |CMAKE_SYSTEM_XXX_MAC_PATH| - - The platform paths that these variables contain are locations that - typically include installed software. An example being ``/usr/local`` for - UNIX based platforms. - -7. Search the paths specified by the PATHS option - or in the short-hand version of the command. - These are typically hard-coded guesses. - -.. |FIND_ARGS_XXX| replace:: <VAR> NAMES name - -On macOS the :variable:`CMAKE_FIND_FRAMEWORK` and -:variable:`CMAKE_FIND_APPBUNDLE` variables determine the order of -preference between Apple-style and unix-style package components. - -.. include:: FIND_XXX_ROOT.txt -.. include:: FIND_XXX_ORDER.txt
diff --git a/share/cmake-3.18/Help/command/LINK_OPTIONS_LINKER.txt b/share/cmake-3.18/Help/command/LINK_OPTIONS_LINKER.txt deleted file mode 100644 index 3f66181..0000000 --- a/share/cmake-3.18/Help/command/LINK_OPTIONS_LINKER.txt +++ /dev/null
@@ -1,22 +0,0 @@ -To pass options to the linker tool, each compiler driver has its own syntax. -The ``LINKER:`` prefix and ``,`` separator can be used to specify, in a portable -way, options to pass to the linker tool. ``LINKER:`` is replaced by the -appropriate driver option and ``,`` by the appropriate driver separator. -The driver prefix and driver separator are given by the values of the -:variable:`CMAKE_<LANG>_LINKER_WRAPPER_FLAG` and -:variable:`CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP` variables. - -For example, ``"LINKER:-z,defs"`` becomes ``-Xlinker -z -Xlinker defs`` for -``Clang`` and ``-Wl,-z,defs`` for ``GNU GCC``. - -The ``LINKER:`` prefix can be specified as part of a ``SHELL:`` prefix -expression. - -The ``LINKER:`` prefix supports, as an alternative syntax, specification of -arguments using the ``SHELL:`` prefix and space as separator. The previous -example then becomes ``"LINKER:SHELL:-z defs"``. - -.. note:: - - Specifying the ``SHELL:`` prefix anywhere other than at the beginning of the - ``LINKER:`` prefix is not supported.
diff --git a/share/cmake-3.18/Help/command/OPTIONS_SHELL.txt b/share/cmake-3.18/Help/command/OPTIONS_SHELL.txt deleted file mode 100644 index 0f8ec32..0000000 --- a/share/cmake-3.18/Help/command/OPTIONS_SHELL.txt +++ /dev/null
@@ -1,9 +0,0 @@ -The final set of compile or link options used for a target is constructed by -accumulating options from the current target and the usage requirements of -its dependencies. The set of options is de-duplicated to avoid repetition. -While beneficial for individual options, the de-duplication step can break -up option groups. For example, ``-D A -D B`` becomes ``-D A B``. One may -specify a group of options using shell-like quoting along with a ``SHELL:`` -prefix. The ``SHELL:`` prefix is dropped, and the rest of the option string -is parsed using the :command:`separate_arguments` ``UNIX_COMMAND`` mode. -For example, ``"SHELL:-D A" "SHELL:-D B"`` becomes ``-D A -D B``.
diff --git a/share/cmake-3.18/Help/command/add_compile_definitions.rst b/share/cmake-3.18/Help/command/add_compile_definitions.rst deleted file mode 100644 index e10aba0..0000000 --- a/share/cmake-3.18/Help/command/add_compile_definitions.rst +++ /dev/null
@@ -1,25 +0,0 @@ -add_compile_definitions ------------------------ - -Add preprocessor definitions to the compilation of source files. - -.. code-block:: cmake - - add_compile_definitions(<definition> ...) - -Adds preprocessor definitions to the compiler command line. - -The preprocessor definitions are added to the :prop_dir:`COMPILE_DEFINITIONS` -directory property for the current ``CMakeLists`` file. They are also added to -the :prop_tgt:`COMPILE_DEFINITIONS` target property for each target in the -current ``CMakeLists`` file. - -Definitions are specified using the syntax ``VAR`` or ``VAR=value``. -Function-style definitions are not supported. CMake will automatically -escape the value correctly for the native build system (note that CMake -language syntax may require escapes to specify some values). - -Arguments to ``add_compile_definitions`` may use "generator expressions" with -the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/command/add_custom_command.rst b/share/cmake-3.18/Help/command/add_custom_command.rst deleted file mode 100644 index 9279748..0000000 --- a/share/cmake-3.18/Help/command/add_custom_command.rst +++ /dev/null
@@ -1,281 +0,0 @@ -add_custom_command ------------------- - -Add a custom build rule to the generated build system. - -There are two main signatures for ``add_custom_command``. - -Generating Files -^^^^^^^^^^^^^^^^ - -The first signature is for adding a custom command to produce an output: - -.. code-block:: cmake - - add_custom_command(OUTPUT output1 [output2 ...] - COMMAND command1 [ARGS] [args1...] - [COMMAND command2 [ARGS] [args2...] ...] - [MAIN_DEPENDENCY depend] - [DEPENDS [depends...]] - [BYPRODUCTS [files...]] - [IMPLICIT_DEPENDS <lang1> depend1 - [<lang2> depend2] ...] - [WORKING_DIRECTORY dir] - [COMMENT comment] - [DEPFILE depfile] - [JOB_POOL job_pool] - [VERBATIM] [APPEND] [USES_TERMINAL] - [COMMAND_EXPAND_LISTS]) - -This defines a command to generate specified ``OUTPUT`` file(s). -A target created in the same directory (``CMakeLists.txt`` file) -that specifies any output of the custom command as a source file -is given a rule to generate the file using the command at build time. -Do not list the output in more than one independent target that -may build in parallel or the two instances of the rule may conflict -(instead use the :command:`add_custom_target` command to drive the -command and make the other targets depend on that one). -In makefile terms this creates a new target in the following form:: - - OUTPUT: MAIN_DEPENDENCY DEPENDS - COMMAND - -The options are: - -``APPEND`` - Append the ``COMMAND`` and ``DEPENDS`` option values to the custom - command for the first output specified. There must have already - been a previous call to this command with the same output. - The ``COMMENT``, ``MAIN_DEPENDENCY``, and ``WORKING_DIRECTORY`` - options are currently ignored when APPEND is given, but may be - used in the future. - -``BYPRODUCTS`` - Specify the files the command is expected to produce but whose - modification time may or may not be newer than the dependencies. - If a byproduct name is a relative path it will be interpreted - relative to the build tree directory corresponding to the - current source directory. - Each byproduct file will be marked with the :prop_sf:`GENERATED` - source file property automatically. - - Explicit specification of byproducts is supported by the - :generator:`Ninja` generator to tell the ``ninja`` build tool - how to regenerate byproducts when they are missing. It is - also useful when other build rules (e.g. custom commands) - depend on the byproducts. Ninja requires a build rule for any - generated file on which another rule depends even if there are - order-only dependencies to ensure the byproducts will be - available before their dependents build. - - The :ref:`Makefile Generators` will remove ``BYPRODUCTS`` and other - :prop_sf:`GENERATED` files during ``make clean``. - -``COMMAND`` - Specify the command-line(s) to execute at build time. - If more than one ``COMMAND`` is specified they will be executed in order, - but *not* necessarily composed into a stateful shell or batch script. - (To run a full script, use the :command:`configure_file` command or the - :command:`file(GENERATE)` command to create it, and then specify - a ``COMMAND`` to launch it.) - The optional ``ARGS`` argument is for backward compatibility and - will be ignored. - - If ``COMMAND`` specifies an executable target name (created by the - :command:`add_executable` command), it will automatically be replaced - by the location of the executable created at build time if either of - the following is true: - - * The target is not being cross-compiled (i.e. the - :variable:`CMAKE_CROSSCOMPILING` variable is not set to true). - * The target is being cross-compiled and an emulator is provided (i.e. - its :prop_tgt:`CROSSCOMPILING_EMULATOR` target property is set). - In this case, the contents of :prop_tgt:`CROSSCOMPILING_EMULATOR` will be - prepended to the command before the location of the target executable. - - If neither of the above conditions are met, it is assumed that the - command name is a program to be found on the ``PATH`` at build time. - - Arguments to ``COMMAND`` may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - Use the ``TARGET_FILE`` generator expression to refer to the location of - a target later in the command line (i.e. as a command argument rather - than as the command to execute). - - Whenever a target is used as a command to execute or is mentioned in a - generator expression as a command argument, a target-level dependency - will be added automatically so that the mentioned target will be built - before any target using this custom command. However this does NOT add - a file-level dependency that would cause the custom command to re-run - whenever the executable is recompiled. List target names with - the ``DEPENDS`` option to add such file-level dependencies. - -``COMMENT`` - Display the given message before the commands are executed at - build time. - -``DEPENDS`` - Specify files on which the command depends. Each argument is converted - to a dependency as follows: - - 1. If the argument is the name of a target (created by the - :command:`add_custom_target`, :command:`add_executable`, or - :command:`add_library` command) a target-level dependency is - created to make sure the target is built before any target - using this custom command. Additionally, if the target is an - executable or library, a file-level dependency is created to - cause the custom command to re-run whenever the target is - recompiled. - - 2. If the argument is an absolute path, a file-level dependency - is created on that path. - - 3. If the argument is the name of a source file that has been - added to a target or on which a source file property has been set, - a file-level dependency is created on that source file. - - 4. If the argument is a relative path and it exists in the current - source directory, a file-level dependency is created on that - file in the current source directory. - - 5. Otherwise, a file-level dependency is created on that path relative - to the current binary directory. - - If any dependency is an ``OUTPUT`` of another custom command in the same - directory (``CMakeLists.txt`` file), CMake automatically brings the other - custom command into the target in which this command is built. - A target-level dependency is added if any dependency is listed as - ``BYPRODUCTS`` of a target or any of its build events in the same - directory to ensure the byproducts will be available. - - If ``DEPENDS`` is not specified, the command will run whenever - the ``OUTPUT`` is missing; if the command does not actually - create the ``OUTPUT``, the rule will always run. - - Arguments to ``DEPENDS`` may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - -``COMMAND_EXPAND_LISTS`` - Lists in ``COMMAND`` arguments will be expanded, including those - created with - :manual:`generator expressions <cmake-generator-expressions(7)>`, - allowing ``COMMAND`` arguments such as - ``${CC} "-I$<JOIN:$<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>,;-I>" foo.cc`` - to be properly expanded. - -``IMPLICIT_DEPENDS`` - Request scanning of implicit dependencies of an input file. - The language given specifies the programming language whose - corresponding dependency scanner should be used. - Currently only ``C`` and ``CXX`` language scanners are supported. - The language has to be specified for every file in the - ``IMPLICIT_DEPENDS`` list. Dependencies discovered from the - scanning are added to those of the custom command at build time. - Note that the ``IMPLICIT_DEPENDS`` option is currently supported - only for Makefile generators and will be ignored by other generators. - -``JOB_POOL`` - Specify a :prop_gbl:`pool <JOB_POOLS>` for the :generator:`Ninja` - generator. Incompatible with ``USES_TERMINAL``, which implies - the ``console`` pool. - Using a pool that is not defined by :prop_gbl:`JOB_POOLS` causes - an error by ninja at build time. - -``MAIN_DEPENDENCY`` - Specify the primary input source file to the command. This is - treated just like any value given to the ``DEPENDS`` option - but also suggests to Visual Studio generators where to hang - the custom command. Each source file may have at most one command - specifying it as its main dependency. A compile command (i.e. for a - library or an executable) counts as an implicit main dependency which - gets silently overwritten by a custom command specification. - -``OUTPUT`` - Specify the output files the command is expected to produce. - If an output name is a relative path it will be interpreted - relative to the build tree directory corresponding to the - current source directory. - Each output file will be marked with the :prop_sf:`GENERATED` - source file property automatically. - If the output of the custom command is not actually created - as a file on disk it should be marked with the :prop_sf:`SYMBOLIC` - source file property. - -``USES_TERMINAL`` - The command will be given direct access to the terminal if possible. - With the :generator:`Ninja` generator, this places the command in - the ``console`` :prop_gbl:`pool <JOB_POOLS>`. - -``VERBATIM`` - All arguments to the commands will be escaped properly for the - build tool so that the invoked command receives each argument - unchanged. Note that one level of escapes is still used by the - CMake language processor before add_custom_command even sees the - arguments. Use of ``VERBATIM`` is recommended as it enables - correct behavior. When ``VERBATIM`` is not given the behavior - is platform specific because there is no protection of - tool-specific special characters. - -``WORKING_DIRECTORY`` - Execute the command with the given current working directory. - If it is a relative path it will be interpreted relative to the - build tree directory corresponding to the current source directory. - - Arguments to ``WORKING_DIRECTORY`` may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - -``DEPFILE`` - Specify a ``.d`` depfile for the :generator:`Ninja` generator. - A ``.d`` file holds dependencies usually emitted by the custom - command itself. - Using ``DEPFILE`` with other generators than Ninja is an error. - -Build Events -^^^^^^^^^^^^ - -The second signature adds a custom command to a target such as a -library or executable. This is useful for performing an operation -before or after building the target. The command becomes part of the -target and will only execute when the target itself is built. If the -target is already built, the command will not execute. - -.. code-block:: cmake - - add_custom_command(TARGET <target> - PRE_BUILD | PRE_LINK | POST_BUILD - COMMAND command1 [ARGS] [args1...] - [COMMAND command2 [ARGS] [args2...] ...] - [BYPRODUCTS [files...]] - [WORKING_DIRECTORY dir] - [COMMENT comment] - [VERBATIM] [USES_TERMINAL] - [COMMAND_EXPAND_LISTS]) - -This defines a new command that will be associated with building the -specified ``<target>``. The ``<target>`` must be defined in the current -directory; targets defined in other directories may not be specified. - -When the command will happen is determined by which -of the following is specified: - -``PRE_BUILD`` - On :ref:`Visual Studio Generators`, run before any other rules are - executed within the target. - On other generators, run just before ``PRE_LINK`` commands. -``PRE_LINK`` - Run after sources have been compiled but before linking the binary - or running the librarian or archiver tool of a static library. - This is not defined for targets created by the - :command:`add_custom_target` command. -``POST_BUILD`` - Run after all other rules within the target have been executed. - -.. note:: - Because generator expressions can be used in custom commands, - it is possible to define ``COMMAND`` lines or whole custom commands - which evaluate to empty strings for certain configurations. - For **Visual Studio 2010 (and newer)** generators these command - lines or custom commands will be omitted for the specific - configuration and no "empty-string-command" will be added. - - This allows to add individual build events for every configuration.
diff --git a/share/cmake-3.18/Help/command/add_custom_target.rst b/share/cmake-3.18/Help/command/add_custom_target.rst deleted file mode 100644 index 56ab414..0000000 --- a/share/cmake-3.18/Help/command/add_custom_target.rst +++ /dev/null
@@ -1,149 +0,0 @@ -add_custom_target ------------------ - -Add a target with no output so it will always be built. - -.. code-block:: cmake - - add_custom_target(Name [ALL] [command1 [args1...]] - [COMMAND command2 [args2...] ...] - [DEPENDS depend depend depend ... ] - [BYPRODUCTS [files...]] - [WORKING_DIRECTORY dir] - [COMMENT comment] - [JOB_POOL job_pool] - [VERBATIM] [USES_TERMINAL] - [COMMAND_EXPAND_LISTS] - [SOURCES src1 [src2...]]) - -Adds a target with the given name that executes the given commands. -The target has no output file and is *always considered out of date* -even if the commands try to create a file with the name of the target. -Use the :command:`add_custom_command` command to generate a file with -dependencies. By default nothing depends on the custom target. Use -the :command:`add_dependencies` command to add dependencies to or -from other targets. - -The options are: - -``ALL`` - Indicate that this target should be added to the default build - target so that it will be run every time (the command cannot be - called ``ALL``). - -``BYPRODUCTS`` - Specify the files the command is expected to produce but whose - modification time may or may not be updated on subsequent builds. - If a byproduct name is a relative path it will be interpreted - relative to the build tree directory corresponding to the - current source directory. - Each byproduct file will be marked with the :prop_sf:`GENERATED` - source file property automatically. - - Explicit specification of byproducts is supported by the - :generator:`Ninja` generator to tell the ``ninja`` build tool - how to regenerate byproducts when they are missing. It is - also useful when other build rules (e.g. custom commands) - depend on the byproducts. Ninja requires a build rule for any - generated file on which another rule depends even if there are - order-only dependencies to ensure the byproducts will be - available before their dependents build. - - The :ref:`Makefile Generators` will remove ``BYPRODUCTS`` and other - :prop_sf:`GENERATED` files during ``make clean``. - -``COMMAND`` - Specify the command-line(s) to execute at build time. - If more than one ``COMMAND`` is specified they will be executed in order, - but *not* necessarily composed into a stateful shell or batch script. - (To run a full script, use the :command:`configure_file` command or the - :command:`file(GENERATE)` command to create it, and then specify - a ``COMMAND`` to launch it.) - - If ``COMMAND`` specifies an executable target name (created by the - :command:`add_executable` command), it will automatically be replaced - by the location of the executable created at build time if either of - the following is true: - - * The target is not being cross-compiled (i.e. the - :variable:`CMAKE_CROSSCOMPILING` variable is not set to true). - * The target is being cross-compiled and an emulator is provided (i.e. - its :prop_tgt:`CROSSCOMPILING_EMULATOR` target property is set). - In this case, the contents of :prop_tgt:`CROSSCOMPILING_EMULATOR` will be - prepended to the command before the location of the target executable. - - If neither of the above conditions are met, it is assumed that the - command name is a program to be found on the ``PATH`` at build time. - - Arguments to ``COMMAND`` may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - Use the ``TARGET_FILE`` generator expression to refer to the location of - a target later in the command line (i.e. as a command argument rather - than as the command to execute). - - Whenever a target is used as a command to execute or is mentioned in a - generator expression as a command argument, a target-level dependency - will be added automatically so that the mentioned target will be built - before this custom target. - - The command and arguments are optional and if not specified an empty - target will be created. - -``COMMENT`` - Display the given message before the commands are executed at - build time. - -``DEPENDS`` - Reference files and outputs of custom commands created with - :command:`add_custom_command` command calls in the same directory - (``CMakeLists.txt`` file). They will be brought up to date when - the target is built. - A target-level dependency is added if any dependency is a byproduct - of a target or any of its build events in the same directory to ensure - the byproducts will be available before this target is built. - - Use the :command:`add_dependencies` command to add dependencies - on other targets. - -``COMMAND_EXPAND_LISTS`` - Lists in ``COMMAND`` arguments will be expanded, including those - created with - :manual:`generator expressions <cmake-generator-expressions(7)>`, - allowing ``COMMAND`` arguments such as - ``${CC} "-I$<JOIN:$<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>,;-I>" foo.cc`` - to be properly expanded. - -``JOB_POOL`` - Specify a :prop_gbl:`pool <JOB_POOLS>` for the :generator:`Ninja` - generator. Incompatible with ``USES_TERMINAL``, which implies - the ``console`` pool. - Using a pool that is not defined by :prop_gbl:`JOB_POOLS` causes - an error by ninja at build time. - -``SOURCES`` - Specify additional source files to be included in the custom target. - Specified source files will be added to IDE project files for - convenience in editing even if they have no build rules. - -``VERBATIM`` - All arguments to the commands will be escaped properly for the - build tool so that the invoked command receives each argument - unchanged. Note that one level of escapes is still used by the - CMake language processor before ``add_custom_target`` even sees - the arguments. Use of ``VERBATIM`` is recommended as it enables - correct behavior. When ``VERBATIM`` is not given the behavior - is platform specific because there is no protection of - tool-specific special characters. - -``USES_TERMINAL`` - The command will be given direct access to the terminal if possible. - With the :generator:`Ninja` generator, this places the command in - the ``console`` :prop_gbl:`pool <JOB_POOLS>`. - -``WORKING_DIRECTORY`` - Execute the command with the given current working directory. - If it is a relative path it will be interpreted relative to the - build tree directory corresponding to the current source directory. - - Arguments to ``WORKING_DIRECTORY`` may use - :manual:`generator expressions <cmake-generator-expressions(7)>`.
diff --git a/share/cmake-3.18/Help/command/add_dependencies.rst b/share/cmake-3.18/Help/command/add_dependencies.rst deleted file mode 100644 index de219a5..0000000 --- a/share/cmake-3.18/Help/command/add_dependencies.rst +++ /dev/null
@@ -1,23 +0,0 @@ -add_dependencies ----------------- - -Add a dependency between top-level targets. - -.. code-block:: cmake - - add_dependencies(<target> [<target-dependency>]...) - -Makes a top-level ``<target>`` depend on other top-level targets to -ensure that they build before ``<target>`` does. A top-level target -is one created by one of the :command:`add_executable`, -:command:`add_library`, or :command:`add_custom_target` commands -(but not targets generated by CMake like ``install``). - -Dependencies added to an :ref:`imported target <Imported Targets>` -or an :ref:`interface library <Interface Libraries>` are followed -transitively in its place since the target itself does not build. - -See the ``DEPENDS`` option of :command:`add_custom_target` and -:command:`add_custom_command` commands for adding file-level -dependencies in custom rules. See the :prop_sf:`OBJECT_DEPENDS` -source file property to add file-level dependencies to object files.
diff --git a/share/cmake-3.18/Help/command/add_executable.rst b/share/cmake-3.18/Help/command/add_executable.rst deleted file mode 100644 index e073228..0000000 --- a/share/cmake-3.18/Help/command/add_executable.rst +++ /dev/null
@@ -1,99 +0,0 @@ -add_executable --------------- - -.. only:: html - - .. contents:: - -Add an executable to the project using the specified source files. - -Normal Executables -^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_executable(<name> [WIN32] [MACOSX_BUNDLE] - [EXCLUDE_FROM_ALL] - [source1] [source2 ...]) - -Adds an executable target called ``<name>`` to be built from the source -files listed in the command invocation. (The source files can be omitted -here if they are added later using :command:`target_sources`.) The -``<name>`` corresponds to the logical target name and must be globally -unique within a project. The actual file name of the executable built is -constructed based on conventions of the native platform (such as -``<name>.exe`` or just ``<name>``). - -By default the executable file will be created in the build tree -directory corresponding to the source tree directory in which the -command was invoked. See documentation of the -:prop_tgt:`RUNTIME_OUTPUT_DIRECTORY` target property to change this -location. See documentation of the :prop_tgt:`OUTPUT_NAME` target property -to change the ``<name>`` part of the final file name. - -If ``WIN32`` is given the property :prop_tgt:`WIN32_EXECUTABLE` will be -set on the target created. See documentation of that target property for -details. - -If ``MACOSX_BUNDLE`` is given the corresponding property will be set on -the created target. See documentation of the :prop_tgt:`MACOSX_BUNDLE` -target property for details. - -If ``EXCLUDE_FROM_ALL`` is given the corresponding property will be set on -the created target. See documentation of the :prop_tgt:`EXCLUDE_FROM_ALL` -target property for details. - -Source arguments to ``add_executable`` may use "generator expressions" with -the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -See also :prop_sf:`HEADER_FILE_ONLY` on what to do if some sources are -pre-processed, and you want to have the original sources reachable from -within IDE. - -Imported Executables -^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_executable(<name> IMPORTED [GLOBAL]) - -An :ref:`IMPORTED executable target <Imported Targets>` references an -executable file located outside the project. No rules are generated to -build it, and the :prop_tgt:`IMPORTED` target property is ``True``. The -target name has scope in the directory in which it is created and below, but -the ``GLOBAL`` option extends visibility. It may be referenced like any -target built within the project. ``IMPORTED`` executables are useful -for convenient reference from commands like :command:`add_custom_command`. -Details about the imported executable are specified by setting properties -whose names begin in ``IMPORTED_``. The most important such property is -:prop_tgt:`IMPORTED_LOCATION` (and its per-configuration version -:prop_tgt:`IMPORTED_LOCATION_<CONFIG>`) which specifies the location of -the main executable file on disk. See documentation of the ``IMPORTED_*`` -properties for more information. - -Alias Executables -^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_executable(<name> ALIAS <target>) - -Creates an :ref:`Alias Target <Alias Targets>`, such that ``<name>`` can -be used to refer to ``<target>`` in subsequent commands. The ``<name>`` -does not appear in the generated buildsystem as a make target. The -``<target>`` may not be an ``ALIAS``. - -An ``ALIAS`` to a non-``GLOBAL`` :ref:`Imported Target <Imported Targets>` -has scope in the directory in which the alias is created and below. -The :prop_tgt:`ALIAS_GLOBAL` target property can be used to check if the -alias is global or not. - -``ALIAS`` targets can be used as targets to read properties -from, executables for custom commands and custom targets. They can also be -tested for existence with the regular :command:`if(TARGET)` subcommand. -The ``<name>`` may not be used to modify properties of ``<target>``, that -is, it may not be used as the operand of :command:`set_property`, -:command:`set_target_properties`, :command:`target_link_libraries` etc. -An ``ALIAS`` target may not be installed or exported.
diff --git a/share/cmake-3.18/Help/command/add_library.rst b/share/cmake-3.18/Help/command/add_library.rst deleted file mode 100644 index 01c415a..0000000 --- a/share/cmake-3.18/Help/command/add_library.rst +++ /dev/null
@@ -1,187 +0,0 @@ -add_library ------------ - -.. only:: html - - .. contents:: - -Add a library to the project using the specified source files. - -Normal Libraries -^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_library(<name> [STATIC | SHARED | MODULE] - [EXCLUDE_FROM_ALL] - [source1] [source2 ...]) - -Adds a library target called ``<name>`` to be built from the source files -listed in the command invocation. (The source files can be omitted here -if they are added later using :command:`target_sources`.) The ``<name>`` -corresponds to the logical target name and must be globally unique within -a project. The actual file name of the library built is constructed based -on conventions of the native platform (such as ``lib<name>.a`` or -``<name>.lib``). - -``STATIC``, ``SHARED``, or ``MODULE`` may be given to specify the type of -library to be created. ``STATIC`` libraries are archives of object files -for use when linking other targets. ``SHARED`` libraries are linked -dynamically and loaded at runtime. ``MODULE`` libraries are plugins that -are not linked into other targets but may be loaded dynamically at runtime -using dlopen-like functionality. If no type is given explicitly the -type is ``STATIC`` or ``SHARED`` based on whether the current value of the -variable :variable:`BUILD_SHARED_LIBS` is ``ON``. For ``SHARED`` and -``MODULE`` libraries the :prop_tgt:`POSITION_INDEPENDENT_CODE` target -property is set to ``ON`` automatically. -A ``SHARED`` or ``STATIC`` library may be marked with the :prop_tgt:`FRAMEWORK` -target property to create an macOS Framework. - -If a library does not export any symbols, it must not be declared as a -``SHARED`` library. For example, a Windows resource DLL or a managed C++/CLI -DLL that exports no unmanaged symbols would need to be a ``MODULE`` library. -This is because CMake expects a ``SHARED`` library to always have an -associated import library on Windows. - -By default the library file will be created in the build tree directory -corresponding to the source tree directory in which the command was -invoked. See documentation of the :prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY`, -:prop_tgt:`LIBRARY_OUTPUT_DIRECTORY`, and -:prop_tgt:`RUNTIME_OUTPUT_DIRECTORY` target properties to change this -location. See documentation of the :prop_tgt:`OUTPUT_NAME` target -property to change the ``<name>`` part of the final file name. - -If ``EXCLUDE_FROM_ALL`` is given the corresponding property will be set on -the created target. See documentation of the :prop_tgt:`EXCLUDE_FROM_ALL` -target property for details. - -Source arguments to ``add_library`` may use "generator expressions" with -the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -See also :prop_sf:`HEADER_FILE_ONLY` on what to do if some sources are -pre-processed, and you want to have the original sources reachable from -within IDE. - -Imported Libraries -^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_library(<name> <SHARED|STATIC|MODULE|OBJECT|UNKNOWN> IMPORTED - [GLOBAL]) - -An :ref:`IMPORTED library target <Imported Targets>` references a library -file located outside the project. No rules are generated to build it, and -the :prop_tgt:`IMPORTED` target property is ``True``. The target name has -scope in the directory in which it is created and below, but the ``GLOBAL`` -option extends visibility. It may be referenced like any target built -within the project. ``IMPORTED`` libraries are useful for convenient -reference from commands like :command:`target_link_libraries`. Details -about the imported library are specified by setting properties whose names -begin in ``IMPORTED_`` and ``INTERFACE_``. - -The most important properties are: - -* :prop_tgt:`IMPORTED_LOCATION` (and its per-configuration - variant :prop_tgt:`IMPORTED_LOCATION_<CONFIG>`) which specifies the - location of the main library file on disk. -* :prop_tgt:`IMPORTED_OBJECTS` (and :prop_tgt:`IMPORTED_OBJECTS_<CONFIG>`) - for object libraries, specifies the locations of object files on disk. -* :prop_tgt:`PUBLIC_HEADER` files to be installed during :command:`install` invocation - -See documentation of the ``IMPORTED_*`` and ``INTERFACE_*`` properties -for more information. - -An ``UNKNOWN`` library type is typically only used in the implementation of -:ref:`Find Modules`. It allows the path to an imported library (often found -using the :command:`find_library` command) to be used without having to know -what type of library it is. This is especially useful on Windows where a -static library and a DLL's import library both have the same file extension. - -Object Libraries -^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_library(<name> OBJECT <src>...) - -Creates an :ref:`Object Library <Object Libraries>`. An object library -compiles source files but does not archive or link their object files into a -library. Instead other targets created by :command:`add_library` or -:command:`add_executable` may reference the objects using an expression of the -form ``$<TARGET_OBJECTS:objlib>`` as a source, where ``objlib`` is the -object library name. For example: - -.. code-block:: cmake - - add_library(... $<TARGET_OBJECTS:objlib> ...) - add_executable(... $<TARGET_OBJECTS:objlib> ...) - -will include objlib's object files in a library and an executable -along with those compiled from their own sources. Object libraries -may contain only sources that compile, header files, and other files -that would not affect linking of a normal library (e.g. ``.txt``). -They may contain custom commands generating such sources, but not -``PRE_BUILD``, ``PRE_LINK``, or ``POST_BUILD`` commands. Some native build -systems (such as Xcode) may not like targets that have only object files, so -consider adding at least one real source file to any target that references -``$<TARGET_OBJECTS:objlib>``. - -Alias Libraries -^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_library(<name> ALIAS <target>) - -Creates an :ref:`Alias Target <Alias Targets>`, such that ``<name>`` can be -used to refer to ``<target>`` in subsequent commands. The ``<name>`` does -not appear in the generated buildsystem as a make target. The ``<target>`` -may not be an ``ALIAS``. - -An ``ALIAS`` to a non-``GLOBAL`` :ref:`Imported Target <Imported Targets>` -has scope in the directory in which the alias is created and below. -The :prop_tgt:`ALIAS_GLOBAL` target property can be used to check if the -alias is global or not. - -``ALIAS`` targets can be used as linkable targets and as targets to -read properties from. They can also be tested for existence with the -regular :command:`if(TARGET)` subcommand. The ``<name>`` may not be used -to modify properties of ``<target>``, that is, it may not be used as the -operand of :command:`set_property`, :command:`set_target_properties`, -:command:`target_link_libraries` etc. An ``ALIAS`` target may not be -installed or exported. - -Interface Libraries -^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - add_library(<name> INTERFACE [IMPORTED [GLOBAL]]) - -Creates an :ref:`Interface Library <Interface Libraries>`. An ``INTERFACE`` -library target does not directly create build output, though it may -have properties set on it and it may be installed, exported and -imported. Typically the ``INTERFACE_*`` properties are populated on -the interface target using the commands: - -* :command:`set_property`, -* :command:`target_link_libraries(INTERFACE)`, -* :command:`target_link_options(INTERFACE)`, -* :command:`target_include_directories(INTERFACE)`, -* :command:`target_compile_options(INTERFACE)`, -* :command:`target_compile_definitions(INTERFACE)`, and -* :command:`target_sources(INTERFACE)`, - -and then it is used as an argument to :command:`target_link_libraries` -like any other target. - -An ``INTERFACE`` :ref:`Imported Target <Imported Targets>` may also be -created with this signature. An ``IMPORTED`` library target references a -library defined outside the project. The target name has scope in the -directory in which it is created and below, but the ``GLOBAL`` option -extends visibility. It may be referenced like any target built within -the project. ``IMPORTED`` libraries are useful for convenient reference -from commands like :command:`target_link_libraries`.
diff --git a/share/cmake-3.18/Help/command/add_link_options.rst b/share/cmake-3.18/Help/command/add_link_options.rst deleted file mode 100644 index faa4afb..0000000 --- a/share/cmake-3.18/Help/command/add_link_options.rst +++ /dev/null
@@ -1,33 +0,0 @@ -add_link_options ----------------- - -Add options to the link step for executable, shared library or module -library targets in the current directory and below that are added after -this command is invoked. - -.. code-block:: cmake - - add_link_options(<option> ...) - -This command can be used to add any link options, but alternative commands -exist to add libraries (:command:`target_link_libraries` or -:command:`link_libraries`). See documentation of the -:prop_dir:`directory <LINK_OPTIONS>` and -:prop_tgt:`target <LINK_OPTIONS>` ``LINK_OPTIONS`` properties. - -.. note:: - - This command cannot be used to add options for static library targets, - since they do not use a linker. To add archiver or MSVC librarian flags, - see the :prop_tgt:`STATIC_LIBRARY_OPTIONS` target property. - -Arguments to ``add_link_options`` may use "generator expressions" with -the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -.. include:: DEVICE_LINK_OPTIONS.txt - -.. include:: OPTIONS_SHELL.txt - -.. include:: LINK_OPTIONS_LINKER.txt
diff --git a/share/cmake-3.18/Help/command/add_test.rst b/share/cmake-3.18/Help/command/add_test.rst deleted file mode 100644 index a77ba37..0000000 --- a/share/cmake-3.18/Help/command/add_test.rst +++ /dev/null
@@ -1,76 +0,0 @@ -add_test --------- - -Add a test to the project to be run by :manual:`ctest(1)`. - -.. code-block:: cmake - - add_test(NAME <name> COMMAND <command> [<arg>...] - [CONFIGURATIONS <config>...] - [WORKING_DIRECTORY <dir>] - [COMMAND_EXPAND_LISTS]) - -Adds a test called ``<name>``. The test name may not contain spaces, -quotes, or other characters special in CMake syntax. The options are: - -``COMMAND`` - Specify the test command-line. If ``<command>`` specifies an - executable target (created by :command:`add_executable`) it will - automatically be replaced by the location of the executable created - at build time. - -``CONFIGURATIONS`` - Restrict execution of the test only to the named configurations. - -``WORKING_DIRECTORY`` - Set the :prop_test:`WORKING_DIRECTORY` test property to - specify the working directory in which to execute the test. - If not specified the test will be run with the current working - directory set to the build directory corresponding to the - current source directory. - -``COMMAND_EXPAND_LISTS`` - Lists in ``COMMAND`` arguments will be expanded, including those - created with - :manual:`generator expressions <cmake-generator-expressions(7)>`. - -The given test command is expected to exit with code ``0`` to pass and -non-zero to fail, or vice-versa if the :prop_test:`WILL_FAIL` test -property is set. Any output written to stdout or stderr will be -captured by :manual:`ctest(1)` but does not affect the pass/fail status -unless the :prop_test:`PASS_REGULAR_EXPRESSION`, -:prop_test:`FAIL_REGULAR_EXPRESSION` or -:prop_test:`SKIP_REGULAR_EXPRESSION` test property is used. - -The ``COMMAND`` and ``WORKING_DIRECTORY`` options may use "generator -expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available expressions. - -Example usage: - -.. code-block:: cmake - - add_test(NAME mytest - COMMAND testDriver --config $<CONFIGURATION> - --exe $<TARGET_FILE:myexe>) - -This creates a test ``mytest`` whose command runs a ``testDriver`` tool -passing the configuration name and the full path to the executable -file produced by target ``myexe``. - -.. note:: - - CMake will generate tests only if the :command:`enable_testing` - command has been invoked. The :module:`CTest` module invokes the - command automatically unless the ``BUILD_TESTING`` option is turned - ``OFF``. - ---------------------------------------------------------------------- - -.. code-block:: cmake - - add_test(<name> <command> [<arg>...]) - -Add a test called ``<name>`` with the given command-line. Unlike -the above ``NAME`` signature no transformation is performed on the -command-line to support target names or generator expressions.
diff --git a/share/cmake-3.18/Help/command/build_command.rst b/share/cmake-3.18/Help/command/build_command.rst deleted file mode 100644 index 6659005..0000000 --- a/share/cmake-3.18/Help/command/build_command.rst +++ /dev/null
@@ -1,45 +0,0 @@ -build_command -------------- - -Get a command line to build the current project. -This is mainly intended for internal use by the :module:`CTest` module. - -.. code-block:: cmake - - build_command(<variable> - [CONFIGURATION <config>] - [TARGET <target>] - [PROJECT_NAME <projname>] # legacy, causes warning - ) - -Sets the given ``<variable>`` to a command-line string of the form:: - - <cmake> --build . [--config <config>] [--target <target>...] [-- -i] - -where ``<cmake>`` is the location of the :manual:`cmake(1)` command-line -tool, and ``<config>`` and ``<target>`` are the values provided to the -``CONFIGURATION`` and ``TARGET`` options, if any. The trailing ``-- -i`` -option is added for :ref:`Makefile Generators` if policy :policy:`CMP0061` -is not set to ``NEW``. - -When invoked, this ``cmake --build`` command line will launch the -underlying build system tool. - -.. code-block:: cmake - - build_command(<cachevariable> <makecommand>) - -This second signature is deprecated, but still available for backwards -compatibility. Use the first signature instead. - -It sets the given ``<cachevariable>`` to a command-line string as -above but without the ``--target`` option. -The ``<makecommand>`` is ignored but should be the full path to -devenv, nmake, make or one of the end user build tools -for legacy invocations. - -.. note:: - In CMake versions prior to 3.0 this command returned a command - line that directly invokes the native build tool for the current - generator. Their implementation of the ``PROJECT_NAME`` option - had no useful effects, so CMake now warns on use of the option.
diff --git a/share/cmake-3.18/Help/command/cmake_host_system_information.rst b/share/cmake-3.18/Help/command/cmake_host_system_information.rst deleted file mode 100644 index 2e9563a..0000000 --- a/share/cmake-3.18/Help/command/cmake_host_system_information.rst +++ /dev/null
@@ -1,50 +0,0 @@ -cmake_host_system_information ------------------------------ - -Query host system specific information. - -.. code-block:: cmake - - cmake_host_system_information(RESULT <variable> QUERY <key> ...) - -Queries system information of the host system on which cmake runs. -One or more ``<key>`` can be provided to select the information to be -queried. The list of queried values is stored in ``<variable>``. - -``<key>`` can be one of the following values: - -============================= ================================================ -Key Description -============================= ================================================ -``NUMBER_OF_LOGICAL_CORES`` Number of logical cores -``NUMBER_OF_PHYSICAL_CORES`` Number of physical cores -``HOSTNAME`` Hostname -``FQDN`` Fully qualified domain name -``TOTAL_VIRTUAL_MEMORY`` Total virtual memory in MiB [#mebibytes]_ -``AVAILABLE_VIRTUAL_MEMORY`` Available virtual memory in MiB [#mebibytes]_ -``TOTAL_PHYSICAL_MEMORY`` Total physical memory in MiB [#mebibytes]_ -``AVAILABLE_PHYSICAL_MEMORY`` Available physical memory in MiB [#mebibytes]_ -``IS_64BIT`` One if processor is 64Bit -``HAS_FPU`` One if processor has floating point unit -``HAS_MMX`` One if processor supports MMX instructions -``HAS_MMX_PLUS`` One if processor supports Ext. MMX instructions -``HAS_SSE`` One if processor supports SSE instructions -``HAS_SSE2`` One if processor supports SSE2 instructions -``HAS_SSE_FP`` One if processor supports SSE FP instructions -``HAS_SSE_MMX`` One if processor supports SSE MMX instructions -``HAS_AMD_3DNOW`` One if processor supports 3DNow instructions -``HAS_AMD_3DNOW_PLUS`` One if processor supports 3DNow+ instructions -``HAS_IA64`` One if IA64 processor emulating x86 -``HAS_SERIAL_NUMBER`` One if processor has serial number -``PROCESSOR_SERIAL_NUMBER`` Processor serial number -``PROCESSOR_NAME`` Human readable processor name -``PROCESSOR_DESCRIPTION`` Human readable full processor description -``OS_NAME`` See :variable:`CMAKE_HOST_SYSTEM_NAME` -``OS_RELEASE`` The OS sub-type e.g. on Windows ``Professional`` -``OS_VERSION`` The OS build ID -``OS_PLATFORM`` See :variable:`CMAKE_HOST_SYSTEM_PROCESSOR` -============================= ================================================ - -.. rubric:: Footnotes - -.. [#mebibytes] One MiB (mebibyte) is equal to 1024x1024 bytes.
diff --git a/share/cmake-3.18/Help/command/cmake_language.rst b/share/cmake-3.18/Help/command/cmake_language.rst deleted file mode 100644 index 0988097..0000000 --- a/share/cmake-3.18/Help/command/cmake_language.rst +++ /dev/null
@@ -1,99 +0,0 @@ -cmake_language --------------- - -Call meta-operations on CMake commands. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - cmake_language(`CALL`_ <command> [<args>...]) - cmake_language(`EVAL`_ CODE <code>...) - -Introduction -^^^^^^^^^^^^ - -This command will call meta-operations on built-in CMake commands or -those created via the :command:`macro` or :command:`function` commands. - -``cmake_language`` does not introduce a new variable or policy scope. - -Calling Commands -^^^^^^^^^^^^^^^^ - -.. _CALL: - -.. code-block:: cmake - - cmake_language(CALL <command> [<args>...]) - -Calls the named ``<command>`` with the given arguments (if any). -For example, the code: - -.. code-block:: cmake - - set(message_command "message") - cmake_language(CALL ${message_command} STATUS "Hello World!") - -is equivalent to - -.. code-block:: cmake - - message(STATUS "Hello World!") - -.. note:: - To ensure consistency of the code, the following commands are not allowed: - - * ``if`` / ``elseif`` / ``else`` / ``endif`` - * ``while`` / ``endwhile`` - * ``foreach`` / ``endforeach`` - * ``function`` / ``endfunction`` - * ``macro`` / ``endmacro`` - -Evaluating Code -^^^^^^^^^^^^^^^ - -.. _EVAL: - -.. code-block:: cmake - - cmake_language(EVAL CODE <code>...) - -Evaluates the ``<code>...`` as CMake code. - -For example, the code: - -.. code-block:: cmake - - set(A TRUE) - set(B TRUE) - set(C TRUE) - set(condition "(A AND B) OR C") - - cmake_language(EVAL CODE " - if (${condition}) - message(STATUS TRUE) - else() - message(STATUS FALSE) - endif()" - ) - -is equivalent to - -.. code-block:: cmake - - set(A TRUE) - set(B TRUE) - set(C TRUE) - set(condition "(A AND B) OR C") - - file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/eval.cmake " - if (${condition}) - message(STATUS TRUE) - else() - message(STATUS FALSE) - endif()" - ) - - include(${CMAKE_CURRENT_BINARY_DIR}/eval.cmake)
diff --git a/share/cmake-3.18/Help/command/cmake_minimum_required.rst b/share/cmake-3.18/Help/command/cmake_minimum_required.rst deleted file mode 100644 index e6ebcf0..0000000 --- a/share/cmake-3.18/Help/command/cmake_minimum_required.rst +++ /dev/null
@@ -1,68 +0,0 @@ -cmake_minimum_required ----------------------- - -Require a minimum version of cmake. - -.. code-block:: cmake - - cmake_minimum_required(VERSION <min>[...<max>] [FATAL_ERROR]) - -Sets the minimum required version of cmake for a project. -Also updates the policy settings as explained below. - -``<min>`` and the optional ``<max>`` are each CMake versions of the form -``major.minor[.patch[.tweak]]``, and the ``...`` is literal. - -If the running version of CMake is lower than the ``<min>`` required -version it will stop processing the project and report an error. -The optional ``<max>`` version, if specified, must be at least the -``<min>`` version and affects policy settings as described below. -If the running version of CMake is older than 3.12, the extra ``...`` -dots will be seen as version component separators, resulting in the -``...<max>`` part being ignored and preserving the pre-3.12 behavior -of basing policies on ``<min>``. - -The ``FATAL_ERROR`` option is accepted but ignored by CMake 2.6 and -higher. It should be specified so CMake versions 2.4 and lower fail -with an error instead of just a warning. - -.. note:: - Call the ``cmake_minimum_required()`` command at the beginning of - the top-level ``CMakeLists.txt`` file even before calling the - :command:`project` command. It is important to establish version - and policy settings before invoking other commands whose behavior - they may affect. See also policy :policy:`CMP0000`. - - Calling ``cmake_minimum_required()`` inside a :command:`function` - limits some effects to the function scope when invoked. Such calls - should not be made with the intention of having global effects. - -Policy Settings -^^^^^^^^^^^^^^^ - -The ``cmake_minimum_required(VERSION)`` command implicitly invokes the -:command:`cmake_policy(VERSION)` command to specify that the current -project code is written for the given range of CMake versions. -All policies known to the running version of CMake and introduced -in the ``<min>`` (or ``<max>``, if specified) version or earlier will -be set to use ``NEW`` behavior. All policies introduced in later -versions will be unset. This effectively requests behavior preferred -as of a given CMake version and tells newer CMake versions to warn -about their new policies. - -When a ``<min>`` version higher than 2.4 is specified the command -implicitly invokes - -.. code-block:: cmake - - cmake_policy(VERSION <min>[...<max>]) - -which sets CMake policies based on the range of versions specified. -When a ``<min>`` version 2.4 or lower is given the command implicitly -invokes - -.. code-block:: cmake - - cmake_policy(VERSION 2.4[...<max>]) - -which enables compatibility features for CMake 2.4 and lower.
diff --git a/share/cmake-3.18/Help/command/cmake_parse_arguments.rst b/share/cmake-3.18/Help/command/cmake_parse_arguments.rst deleted file mode 100644 index fcd36d0..0000000 --- a/share/cmake-3.18/Help/command/cmake_parse_arguments.rst +++ /dev/null
@@ -1,109 +0,0 @@ -cmake_parse_arguments ---------------------- - -Parse function or macro arguments. - -.. code-block:: cmake - - cmake_parse_arguments(<prefix> <options> <one_value_keywords> - <multi_value_keywords> <args>...) - - cmake_parse_arguments(PARSE_ARGV <N> <prefix> <options> - <one_value_keywords> <multi_value_keywords>) - -This command is for use in macros or functions. -It processes the arguments given to that macro or function, -and defines a set of variables which hold the values of the -respective options. - -The first signature reads processes arguments passed in the ``<args>...``. -This may be used in either a :command:`macro` or a :command:`function`. - -The ``PARSE_ARGV`` signature is only for use in a :command:`function` -body. In this case the arguments that are parsed come from the -``ARGV#`` variables of the calling function. The parsing starts with -the ``<N>``-th argument, where ``<N>`` is an unsigned integer. This allows for -the values to have special characters like ``;`` in them. - -The ``<options>`` argument contains all options for the respective macro, -i.e. keywords which can be used when calling the macro without any value -following, like e.g. the ``OPTIONAL`` keyword of the :command:`install` -command. - -The ``<one_value_keywords>`` argument contains all keywords for this macro -which are followed by one value, like e.g. ``DESTINATION`` keyword of the -:command:`install` command. - -The ``<multi_value_keywords>`` argument contains all keywords for this -macro which can be followed by more than one value, like e.g. the -``TARGETS`` or ``FILES`` keywords of the :command:`install` command. - -.. note:: - - All keywords shall be unique. I.e. every keyword shall only be specified - once in either ``<options>``, ``<one_value_keywords>`` or - ``<multi_value_keywords>``. A warning will be emitted if uniqueness is - violated. - -When done, ``cmake_parse_arguments`` will consider for each of the -keywords listed in ``<options>``, ``<one_value_keywords>`` and -``<multi_value_keywords>`` a variable composed of the given ``<prefix>`` -followed by ``"_"`` and the name of the respective keyword. These -variables will then hold the respective value from the argument list -or be undefined if the associated option could not be found. -For the ``<options>`` keywords, these will always be defined, -to ``TRUE`` or ``FALSE``, whether the option is in the argument list or not. - -All remaining arguments are collected in a variable -``<prefix>_UNPARSED_ARGUMENTS`` that will be undefined if all arguments -were recognized. This can be checked afterwards to see -whether your macro was called with unrecognized parameters. - -``<one_value_keywords>`` and ``<multi_value_keywords>`` that were given no -values at all are collected in a variable ``<prefix>_KEYWORDS_MISSING_VALUES`` -that will be undefined if all keywords received values. This can be checked -to see if there were keywords without any values given. - -Consider the following example macro, ``my_install()``, which takes similar -arguments to the real :command:`install` command: - -.. code-block:: cmake - - macro(my_install) - set(options OPTIONAL FAST) - set(oneValueArgs DESTINATION RENAME) - set(multiValueArgs TARGETS CONFIGURATIONS) - cmake_parse_arguments(MY_INSTALL "${options}" "${oneValueArgs}" - "${multiValueArgs}" ${ARGN} ) - - # ... - -Assume ``my_install()`` has been called like this: - -.. code-block:: cmake - - my_install(TARGETS foo bar DESTINATION bin OPTIONAL blub CONFIGURATIONS) - -After the ``cmake_parse_arguments`` call the macro will have set or undefined -the following variables:: - - MY_INSTALL_OPTIONAL = TRUE - MY_INSTALL_FAST = FALSE # was not used in call to my_install - MY_INSTALL_DESTINATION = "bin" - MY_INSTALL_RENAME <UNDEFINED> # was not used - MY_INSTALL_TARGETS = "foo;bar" - MY_INSTALL_CONFIGURATIONS <UNDEFINED> # was not used - MY_INSTALL_UNPARSED_ARGUMENTS = "blub" # nothing expected after "OPTIONAL" - MY_INSTALL_KEYWORDS_MISSING_VALUES = "CONFIGURATIONS" - # No value for "CONFIGURATIONS" given - -You can then continue and process these variables. - -Keywords terminate lists of values, e.g. if directly after a -``one_value_keyword`` another recognized keyword follows, this is -interpreted as the beginning of the new option. E.g. -``my_install(TARGETS foo DESTINATION OPTIONAL)`` would result in -``MY_INSTALL_DESTINATION`` set to ``"OPTIONAL"``, but as ``OPTIONAL`` -is a keyword itself ``MY_INSTALL_DESTINATION`` will be empty (but added -to ``MY_INSTALL_KEYWORDS_MISSING_VALUES``) and ``MY_INSTALL_OPTIONAL`` will -therefore be set to ``TRUE``.
diff --git a/share/cmake-3.18/Help/command/cmake_policy.rst b/share/cmake-3.18/Help/command/cmake_policy.rst deleted file mode 100644 index 4bc7807..0000000 --- a/share/cmake-3.18/Help/command/cmake_policy.rst +++ /dev/null
@@ -1,108 +0,0 @@ -cmake_policy ------------- - -Manage CMake Policy settings. See the :manual:`cmake-policies(7)` -manual for defined policies. - -As CMake evolves it is sometimes necessary to change existing behavior -in order to fix bugs or improve implementations of existing features. -The CMake Policy mechanism is designed to help keep existing projects -building as new versions of CMake introduce changes in behavior. Each -new policy (behavioral change) is given an identifier of the form -``CMP<NNNN>`` where ``<NNNN>`` is an integer index. Documentation -associated with each policy describes the ``OLD`` and ``NEW`` behavior -and the reason the policy was introduced. Projects may set each policy -to select the desired behavior. When CMake needs to know which behavior -to use it checks for a setting specified by the project. If no -setting is available the ``OLD`` behavior is assumed and a warning is -produced requesting that the policy be set. - -Setting Policies by CMake Version -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The ``cmake_policy`` command is used to set policies to ``OLD`` or ``NEW`` -behavior. While setting policies individually is supported, we -encourage projects to set policies based on CMake versions: - -.. code-block:: cmake - - cmake_policy(VERSION <min>[...<max>]) - -``<min>`` and the optional ``<max>`` are each CMake versions of the form -``major.minor[.patch[.tweak]]``, and the ``...`` is literal. The ``<min>`` -version must be at least ``2.4`` and at most the running version of CMake. -The ``<max>`` version, if specified, must be at least the ``<min>`` version -but may exceed the running version of CMake. If the running version of -CMake is older than 3.12, the extra ``...`` dots will be seen as version -component separators, resulting in the ``...<max>`` part being ignored and -preserving the pre-3.12 behavior of basing policies on ``<min>``. - -This specifies that the current CMake code is written for the given -range of CMake versions. All policies known to the running version of CMake -and introduced in the ``<min>`` (or ``<max>``, if specified) version -or earlier will be set to use ``NEW`` behavior. All policies -introduced in later versions will be unset (unless the -:variable:`CMAKE_POLICY_DEFAULT_CMP<NNNN>` variable sets a default). -This effectively requests behavior preferred as of a given CMake -version and tells newer CMake versions to warn about their new policies. - -Note that the :command:`cmake_minimum_required(VERSION)` -command implicitly calls ``cmake_policy(VERSION)`` too. - -Setting Policies Explicitly -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - cmake_policy(SET CMP<NNNN> NEW) - cmake_policy(SET CMP<NNNN> OLD) - -Tell CMake to use the ``OLD`` or ``NEW`` behavior for a given policy. -Projects depending on the old behavior of a given policy may silence a -policy warning by setting the policy state to ``OLD``. Alternatively -one may fix the project to work with the new behavior and set the -policy state to ``NEW``. - -.. include:: ../policy/DEPRECATED.txt - -Checking Policy Settings -^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - cmake_policy(GET CMP<NNNN> <variable>) - -Check whether a given policy is set to ``OLD`` or ``NEW`` behavior. -The output ``<variable>`` value will be ``OLD`` or ``NEW`` if the -policy is set, and empty otherwise. - -CMake Policy Stack -^^^^^^^^^^^^^^^^^^ - -CMake keeps policy settings on a stack, so changes made by the -``cmake_policy`` command affect only the top of the stack. A new entry on -the policy stack is managed automatically for each subdirectory to -protect its parents and siblings. CMake also manages a new entry for -scripts loaded by :command:`include` and :command:`find_package` commands -except when invoked with the ``NO_POLICY_SCOPE`` option -(see also policy :policy:`CMP0011`). -The ``cmake_policy`` command provides an interface to manage custom -entries on the policy stack: - -.. code-block:: cmake - - cmake_policy(PUSH) - cmake_policy(POP) - -Each ``PUSH`` must have a matching ``POP`` to erase any changes. -This is useful to make temporary changes to policy settings. -Calls to the :command:`cmake_minimum_required(VERSION)`, -``cmake_policy(VERSION)``, or ``cmake_policy(SET)`` commands -influence only the current top of the policy stack. - -Commands created by the :command:`function` and :command:`macro` -commands record policy settings when they are created and -use the pre-record policies when they are invoked. If the function or -macro implementation sets policies, the changes automatically -propagate up through callers until they reach the closest nested -policy stack entry.
diff --git a/share/cmake-3.18/Help/command/configure_file.rst b/share/cmake-3.18/Help/command/configure_file.rst deleted file mode 100644 index 29e85bd..0000000 --- a/share/cmake-3.18/Help/command/configure_file.rst +++ /dev/null
@@ -1,135 +0,0 @@ -configure_file --------------- - -Copy a file to another location and modify its contents. - -.. code-block:: cmake - - configure_file(<input> <output> - [COPYONLY] [ESCAPE_QUOTES] [@ONLY] - [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ]) - -Copies an ``<input>`` file to an ``<output>`` file and substitutes -variable values referenced as ``@VAR@`` or ``${VAR}`` in the input -file content. Each variable reference will be replaced with the -current value of the variable, or the empty string if the variable -is not defined. Furthermore, input lines of the form - -.. code-block:: c - - #cmakedefine VAR ... - -will be replaced with either - -.. code-block:: c - - #define VAR ... - -or - -.. code-block:: c - - /* #undef VAR */ - -depending on whether ``VAR`` is set in CMake to any value not considered -a false constant by the :command:`if` command. The "..." content on the -line after the variable name, if any, is processed as above. -Input file lines of the form ``#cmakedefine01 VAR`` will be replaced with -either ``#define VAR 1`` or ``#define VAR 0`` similarly. -The result lines (with the exception of the ``#undef`` comments) can be -indented using spaces and/or tabs between the ``#`` character -and the ``cmakedefine`` or ``cmakedefine01`` words. This whitespace -indentation will be preserved in the output lines: - -.. code-block:: c - - # cmakedefine VAR - # cmakedefine01 VAR - -will be replaced, if ``VAR`` is defined, with - -.. code-block:: c - - # define VAR - # define VAR 1 - -If the input file is modified the build system will re-run CMake to -re-configure the file and generate the build system again. -The generated file is modified and its timestamp updated on subsequent -cmake runs only if its content is changed. - -The arguments are: - -``<input>`` - Path to the input file. A relative path is treated with respect to - the value of :variable:`CMAKE_CURRENT_SOURCE_DIR`. The input path - must be a file, not a directory. - -``<output>`` - Path to the output file or directory. A relative path is treated - with respect to the value of :variable:`CMAKE_CURRENT_BINARY_DIR`. - If the path names an existing directory the output file is placed - in that directory with the same file name as the input file. - -``COPYONLY`` - Copy the file without replacing any variable references or other - content. This option may not be used with ``NEWLINE_STYLE``. - -``ESCAPE_QUOTES`` - Escape any substituted quotes with backslashes (C-style). - -``@ONLY`` - Restrict variable replacement to references of the form ``@VAR@``. - This is useful for configuring scripts that use ``${VAR}`` syntax. - -``NEWLINE_STYLE <style>`` - Specify the newline style for the output file. Specify - ``UNIX`` or ``LF`` for ``\n`` newlines, or specify - ``DOS``, ``WIN32``, or ``CRLF`` for ``\r\n`` newlines. - This option may not be used with ``COPYONLY``. - -Example -^^^^^^^ - -Consider a source tree containing a ``foo.h.in`` file: - -.. code-block:: c - - #cmakedefine FOO_ENABLE - #cmakedefine FOO_STRING "@FOO_STRING@" - -An adjacent ``CMakeLists.txt`` may use ``configure_file`` to -configure the header: - -.. code-block:: cmake - - option(FOO_ENABLE "Enable Foo" ON) - if(FOO_ENABLE) - set(FOO_STRING "foo") - endif() - configure_file(foo.h.in foo.h @ONLY) - -This creates a ``foo.h`` in the build directory corresponding to -this source directory. If the ``FOO_ENABLE`` option is on, the -configured file will contain: - -.. code-block:: c - - #define FOO_ENABLE - #define FOO_STRING "foo" - -Otherwise it will contain: - -.. code-block:: c - - /* #undef FOO_ENABLE */ - /* #undef FOO_STRING */ - -One may then use the :command:`include_directories` command to -specify the output directory as an include directory: - -.. code-block:: cmake - - include_directories(${CMAKE_CURRENT_BINARY_DIR}) - -so that sources may include the header as ``#include <foo.h>``.
diff --git a/share/cmake-3.18/Help/command/continue.rst b/share/cmake-3.18/Help/command/continue.rst deleted file mode 100644 index 31c7089..0000000 --- a/share/cmake-3.18/Help/command/continue.rst +++ /dev/null
@@ -1,14 +0,0 @@ -continue --------- - -Continue to the top of enclosing foreach or while loop. - -.. code-block:: cmake - - continue() - -The ``continue`` command allows a cmake script to abort the rest of a block -in a :command:`foreach` or :command:`while` loop, and start at the top of -the next iteration. - -See also the :command:`break` command.
diff --git a/share/cmake-3.18/Help/command/ctest_build.rst b/share/cmake-3.18/Help/command/ctest_build.rst deleted file mode 100644 index 66e1844..0000000 --- a/share/cmake-3.18/Help/command/ctest_build.rst +++ /dev/null
@@ -1,78 +0,0 @@ -ctest_build ------------ - -Perform the :ref:`CTest Build Step` as a :ref:`Dashboard Client`. - -:: - - ctest_build([BUILD <build-dir>] [APPEND] - [CONFIGURATION <config>] - [FLAGS <flags>] - [PROJECT_NAME <project-name>] - [TARGET <target-name>] - [NUMBER_ERRORS <num-err-var>] - [NUMBER_WARNINGS <num-warn-var>] - [RETURN_VALUE <result-var>] - [CAPTURE_CMAKE_ERROR <result-var>] - ) - -Build the project and store results in ``Build.xml`` -for submission with the :command:`ctest_submit` command. - -The :variable:`CTEST_BUILD_COMMAND` variable may be set to explicitly -specify the build command line. Otherwise the build command line is -computed automatically based on the options given. - -The options are: - -``BUILD <build-dir>`` - Specify the top-level build directory. If not given, the - :variable:`CTEST_BINARY_DIRECTORY` variable is used. - -``APPEND`` - Mark ``Build.xml`` for append to results previously submitted to a - dashboard server since the last :command:`ctest_start` call. - Append semantics are defined by the dashboard server in use. - This does *not* cause results to be appended to a ``.xml`` file - produced by a previous call to this command. - -``CONFIGURATION <config>`` - Specify the build configuration (e.g. ``Debug``). If not - specified the ``CTEST_BUILD_CONFIGURATION`` variable will be checked. - Otherwise the ``-C <cfg>`` option given to the :manual:`ctest(1)` - command will be used, if any. - -``FLAGS <flags>`` - Pass additional arguments to the underlying build command. - If not specified the ``CTEST_BUILD_FLAGS`` variable will be checked. - This can, e.g., be used to trigger a parallel build using the - ``-j`` option of make. See the :module:`ProcessorCount` module - for an example. - -``PROJECT_NAME <project-name>`` - Ignored. This was once used but is no longer needed. - -``TARGET <target-name>`` - Specify the name of a target to build. If not specified the - ``CTEST_BUILD_TARGET`` variable will be checked. Otherwise the - default target will be built. This is the "all" target - (called ``ALL_BUILD`` in :ref:`Visual Studio Generators`). - -``NUMBER_ERRORS <num-err-var>`` - Store the number of build errors detected in the given variable. - -``NUMBER_WARNINGS <num-warn-var>`` - Store the number of build warnings detected in the given variable. - -``RETURN_VALUE <result-var>`` - Store the return value of the native build tool in the given variable. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Suppress any CTest-specific non-error output that would have been - printed to the console otherwise. The summary of warnings / errors, - as well as the output from the native build tool is unaffected by - this option.
diff --git a/share/cmake-3.18/Help/command/ctest_configure.rst b/share/cmake-3.18/Help/command/ctest_configure.rst deleted file mode 100644 index 2dea07b..0000000 --- a/share/cmake-3.18/Help/command/ctest_configure.rst +++ /dev/null
@@ -1,46 +0,0 @@ -ctest_configure ---------------- - -Perform the :ref:`CTest Configure Step` as a :ref:`Dashboard Client`. - -:: - - ctest_configure([BUILD <build-dir>] [SOURCE <source-dir>] [APPEND] - [OPTIONS <options>] [RETURN_VALUE <result-var>] [QUIET] - [CAPTURE_CMAKE_ERROR <result-var>]) - -Configure the project build tree and record results in ``Configure.xml`` -for submission with the :command:`ctest_submit` command. - -The options are: - -``BUILD <build-dir>`` - Specify the top-level build directory. If not given, the - :variable:`CTEST_BINARY_DIRECTORY` variable is used. - -``SOURCE <source-dir>`` - Specify the source directory. If not given, the - :variable:`CTEST_SOURCE_DIRECTORY` variable is used. - -``APPEND`` - Mark ``Configure.xml`` for append to results previously submitted to a - dashboard server since the last :command:`ctest_start` call. - Append semantics are defined by the dashboard server in use. - This does *not* cause results to be appended to a ``.xml`` file - produced by a previous call to this command. - -``OPTIONS <options>`` - Specify command-line arguments to pass to the configuration tool. - -``RETURN_VALUE <result-var>`` - Store in the ``<result-var>`` variable the return value of the native - configuration tool. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Suppress any CTest-specific non-error messages that would have - otherwise been printed to the console. Output from the underlying - configure command is not affected.
diff --git a/share/cmake-3.18/Help/command/ctest_coverage.rst b/share/cmake-3.18/Help/command/ctest_coverage.rst deleted file mode 100644 index d50f634..0000000 --- a/share/cmake-3.18/Help/command/ctest_coverage.rst +++ /dev/null
@@ -1,46 +0,0 @@ -ctest_coverage --------------- - -Perform the :ref:`CTest Coverage Step` as a :ref:`Dashboard Client`. - -:: - - ctest_coverage([BUILD <build-dir>] [APPEND] - [LABELS <label>...] - [RETURN_VALUE <result-var>] - [CAPTURE_CMAKE_ERROR <result-var>] - [QUIET] - ) - -Collect coverage tool results and stores them in ``Coverage.xml`` -for submission with the :command:`ctest_submit` command. - -The options are: - -``BUILD <build-dir>`` - Specify the top-level build directory. If not given, the - :variable:`CTEST_BINARY_DIRECTORY` variable is used. - -``APPEND`` - Mark ``Coverage.xml`` for append to results previously submitted to a - dashboard server since the last :command:`ctest_start` call. - Append semantics are defined by the dashboard server in use. - This does *not* cause results to be appended to a ``.xml`` file - produced by a previous call to this command. - -``LABELS`` - Filter the coverage report to include only source files labeled - with at least one of the labels specified. - -``RETURN_VALUE <result-var>`` - Store in the ``<result-var>`` variable ``0`` if coverage tools - ran without error and non-zero otherwise. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Suppress any CTest-specific non-error output that would have been - printed to the console otherwise. The summary indicating how many - lines of code were covered is unaffected by this option.
diff --git a/share/cmake-3.18/Help/command/ctest_memcheck.rst b/share/cmake-3.18/Help/command/ctest_memcheck.rst deleted file mode 100644 index 288b65a..0000000 --- a/share/cmake-3.18/Help/command/ctest_memcheck.rst +++ /dev/null
@@ -1,38 +0,0 @@ -ctest_memcheck --------------- - -Perform the :ref:`CTest MemCheck Step` as a :ref:`Dashboard Client`. - -:: - - ctest_memcheck([BUILD <build-dir>] [APPEND] - [START <start-number>] - [END <end-number>] - [STRIDE <stride-number>] - [EXCLUDE <exclude-regex>] - [INCLUDE <include-regex>] - [EXCLUDE_LABEL <label-exclude-regex>] - [INCLUDE_LABEL <label-include-regex>] - [EXCLUDE_FIXTURE <regex>] - [EXCLUDE_FIXTURE_SETUP <regex>] - [EXCLUDE_FIXTURE_CLEANUP <regex>] - [PARALLEL_LEVEL <level>] - [TEST_LOAD <threshold>] - [SCHEDULE_RANDOM <ON|OFF>] - [STOP_TIME <time-of-day>] - [RETURN_VALUE <result-var>] - [DEFECT_COUNT <defect-count-var>] - [QUIET] - ) - - -Run tests with a dynamic analysis tool and store results in -``MemCheck.xml`` for submission with the :command:`ctest_submit` -command. - -Most options are the same as those for the :command:`ctest_test` command. - -The options unique to this command are: - -``DEFECT_COUNT <defect-count-var>`` - Store in the ``<defect-count-var>`` the number of defects found.
diff --git a/share/cmake-3.18/Help/command/ctest_start.rst b/share/cmake-3.18/Help/command/ctest_start.rst deleted file mode 100644 index f0704ac..0000000 --- a/share/cmake-3.18/Help/command/ctest_start.rst +++ /dev/null
@@ -1,83 +0,0 @@ -ctest_start ------------ - -Starts the testing for a given model - -:: - - ctest_start(<model> [<source> [<binary>]] [GROUP <group>] [QUIET]) - - ctest_start([<model> [<source> [<binary>]]] [GROUP <group>] APPEND [QUIET]) - -Starts the testing for a given model. The command should be called -after the binary directory is initialized. - -The parameters are as follows: - -``<model>`` - Set the dashboard model. Must be one of ``Experimental``, ``Continuous``, or - ``Nightly``. This parameter is required unless ``APPEND`` is specified. - -``<source>`` - Set the source directory. If not specified, the value of - :variable:`CTEST_SOURCE_DIRECTORY` is used instead. - -``<binary>`` - Set the binary directory. If not specified, the value of - :variable:`CTEST_BINARY_DIRECTORY` is used instead. - -``GROUP <group>`` - If ``GROUP`` is used, the submissions will go to the specified group on the - CDash server. If no ``GROUP`` is specified, the name of the model is used by - default. This replaces the deprecated option ``TRACK``. Despite the name - change its behavior is unchanged. - -``APPEND`` - If ``APPEND`` is used, the existing ``TAG`` is used rather than creating a new - one based on the current time stamp. If you use ``APPEND``, you can omit the - ``<model>`` and ``GROUP <group>`` parameters, because they will be read from - the generated ``TAG`` file. For example: - - .. code-block:: cmake - - ctest_start(Experimental GROUP GroupExperimental) - - Later, in another ``ctest -S`` script: - - .. code-block:: cmake - - ctest_start(APPEND) - - When the second script runs ``ctest_start(APPEND)``, it will read the - ``Experimental`` model and ``GroupExperimental`` group from the ``TAG`` file - generated by the first ``ctest_start()`` command. Please note that if you - call ``ctest_start(APPEND)`` and specify a different model or group than - in the first ``ctest_start()`` command, a warning will be issued, and the - new model and group will be used. - -``QUIET`` - If ``QUIET`` is used, CTest will suppress any non-error messages that it - otherwise would have printed to the console. - -The parameters for ``ctest_start()`` can be issued in any order, with the -exception that ``<model>``, ``<source>``, and ``<binary>`` have to appear -in that order with respect to each other. The following are all valid and -equivalent: - -.. code-block:: cmake - - ctest_start(Experimental path/to/source path/to/binary GROUP SomeGroup QUIET APPEND) - - ctest_start(GROUP SomeGroup Experimental QUIET path/to/source APPEND path/to/binary) - - ctest_start(APPEND QUIET Experimental path/to/source GROUP SomeGroup path/to/binary) - -However, for the sake of readability, it is recommended that you order your -parameters in the order listed at the top of this page. - -If the :variable:`CTEST_CHECKOUT_COMMAND` variable (or the -:variable:`CTEST_CVS_CHECKOUT` variable) is set, its content is treated as -command-line. The command is invoked with the current working directory set -to the parent of the source directory, even if the source directory already -exists. This can be used to create the source tree from a version control -repository.
diff --git a/share/cmake-3.18/Help/command/ctest_submit.rst b/share/cmake-3.18/Help/command/ctest_submit.rst deleted file mode 100644 index 983fc20..0000000 --- a/share/cmake-3.18/Help/command/ctest_submit.rst +++ /dev/null
@@ -1,104 +0,0 @@ -ctest_submit ------------- - -Perform the :ref:`CTest Submit Step` as a :ref:`Dashboard Client`. - -:: - - ctest_submit([PARTS <part>...] [FILES <file>...] - [SUBMIT_URL <url>] - [BUILD_ID <result-var>] - [HTTPHEADER <header>] - [RETRY_COUNT <count>] - [RETRY_DELAY <delay>] - [RETURN_VALUE <result-var>] - [CAPTURE_CMAKE_ERROR <result-var>] - [QUIET] - ) - -Submit results to a dashboard server. -By default all available parts are submitted. - -The options are: - -``PARTS <part>...`` - Specify a subset of parts to submit. Valid part names are:: - - Start = nothing - Update = ctest_update results, in Update.xml - Configure = ctest_configure results, in Configure.xml - Build = ctest_build results, in Build.xml - Test = ctest_test results, in Test.xml - Coverage = ctest_coverage results, in Coverage.xml - MemCheck = ctest_memcheck results, in DynamicAnalysis.xml - Notes = Files listed by CTEST_NOTES_FILES, in Notes.xml - ExtraFiles = Files listed by CTEST_EXTRA_SUBMIT_FILES - Upload = Files prepared for upload by ctest_upload(), in Upload.xml - Submit = nothing - Done = Build is complete, in Done.xml - -``FILES <file>...`` - Specify an explicit list of specific files to be submitted. - Each individual file must exist at the time of the call. - -``SUBMIT_URL <url>`` - The ``http`` or ``https`` URL of the dashboard server to send the submission - to. If not given, the :variable:`CTEST_SUBMIT_URL` variable is used. - -``BUILD_ID <result-var>`` - Store in the ``<result-var>`` variable the ID assigned to this build by - CDash. - -``HTTPHEADER <HTTP-header>`` - Specify HTTP header to be included in the request to CDash during submission. - For example, CDash can be configured to only accept submissions from - authenticated clients. In this case, you should provide a bearer token in your - header: - - .. code-block:: cmake - - ctest_submit(HTTPHEADER "Authorization: Bearer <auth-token>") - - This suboption can be repeated several times for multiple headers. - -``RETRY_COUNT <count>`` - Specify how many times to retry a timed-out submission. - -``RETRY_DELAY <delay>`` - Specify how long (in seconds) to wait after a timed-out submission - before attempting to re-submit. - -``RETURN_VALUE <result-var>`` - Store in the ``<result-var>`` variable ``0`` for success and - non-zero on failure. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Suppress all non-error messages that would have otherwise been - printed to the console. - -Submit to CDash Upload API -^^^^^^^^^^^^^^^^^^^^^^^^^^ - -:: - - ctest_submit(CDASH_UPLOAD <file> [CDASH_UPLOAD_TYPE <type>] - [SUBMIT_URL <url>] - [HTTPHEADER <header>] - [RETRY_COUNT <count>] - [RETRY_DELAY <delay>] - [RETURN_VALUE <result-var>] - [QUIET]) - -This second signature is used to upload files to CDash via the CDash -file upload API. The API first sends a request to upload to CDash along -with a content hash of the file. If CDash does not already have the file, -then it is uploaded. Along with the file, a CDash type string is specified -to tell CDash which handler to use to process the data. - -This signature accepts the ``SUBMIT_URL``, ``BUILD_ID``, ``HTTPHEADER``, -``RETRY_COUNT``, ``RETRY_DELAY``, ``RETURN_VALUE`` and ``QUIET`` options -as described above.
diff --git a/share/cmake-3.18/Help/command/ctest_test.rst b/share/cmake-3.18/Help/command/ctest_test.rst deleted file mode 100644 index 3589296..0000000 --- a/share/cmake-3.18/Help/command/ctest_test.rst +++ /dev/null
@@ -1,144 +0,0 @@ -ctest_test ----------- - -Perform the :ref:`CTest Test Step` as a :ref:`Dashboard Client`. - -:: - - ctest_test([BUILD <build-dir>] [APPEND] - [START <start-number>] - [END <end-number>] - [STRIDE <stride-number>] - [EXCLUDE <exclude-regex>] - [INCLUDE <include-regex>] - [EXCLUDE_LABEL <label-exclude-regex>] - [INCLUDE_LABEL <label-include-regex>] - [EXCLUDE_FIXTURE <regex>] - [EXCLUDE_FIXTURE_SETUP <regex>] - [EXCLUDE_FIXTURE_CLEANUP <regex>] - [PARALLEL_LEVEL <level>] - [RESOURCE_SPEC_FILE <file>] - [TEST_LOAD <threshold>] - [SCHEDULE_RANDOM <ON|OFF>] - [STOP_ON_FAILURE] - [STOP_TIME <time-of-day>] - [RETURN_VALUE <result-var>] - [CAPTURE_CMAKE_ERROR <result-var>] - [REPEAT <mode>:<n>] - [QUIET] - ) - -Run tests in the project build tree and store results in -``Test.xml`` for submission with the :command:`ctest_submit` command. - -The options are: - -``BUILD <build-dir>`` - Specify the top-level build directory. If not given, the - :variable:`CTEST_BINARY_DIRECTORY` variable is used. - -``APPEND`` - Mark ``Test.xml`` for append to results previously submitted to a - dashboard server since the last :command:`ctest_start` call. - Append semantics are defined by the dashboard server in use. - This does *not* cause results to be appended to a ``.xml`` file - produced by a previous call to this command. - -``START <start-number>`` - Specify the beginning of a range of test numbers. - -``END <end-number>`` - Specify the end of a range of test numbers. - -``STRIDE <stride-number>`` - Specify the stride by which to step across a range of test numbers. - -``EXCLUDE <exclude-regex>`` - Specify a regular expression matching test names to exclude. - -``INCLUDE <include-regex>`` - Specify a regular expression matching test names to include. - Tests not matching this expression are excluded. - -``EXCLUDE_LABEL <label-exclude-regex>`` - Specify a regular expression matching test labels to exclude. - -``INCLUDE_LABEL <label-include-regex>`` - Specify a regular expression matching test labels to include. - Tests not matching this expression are excluded. - -``EXCLUDE_FIXTURE <regex>`` - If a test in the set of tests to be executed requires a particular fixture, - that fixture's setup and cleanup tests would normally be added to the test - set automatically. This option prevents adding setup or cleanup tests for - fixtures matching the ``<regex>``. Note that all other fixture behavior is - retained, including test dependencies and skipping tests that have fixture - setup tests that fail. - -``EXCLUDE_FIXTURE_SETUP <regex>`` - Same as ``EXCLUDE_FIXTURE`` except only matching setup tests are excluded. - -``EXCLUDE_FIXTURE_CLEANUP <regex>`` - Same as ``EXCLUDE_FIXTURE`` except only matching cleanup tests are excluded. - -``PARALLEL_LEVEL <level>`` - Specify a positive number representing the number of tests to - be run in parallel. - -``RESOURCE_SPEC_FILE <file>`` - Specify a - :ref:`resource specification file <ctest-resource-specification-file>`. See - :ref:`ctest-resource-allocation` for more information. - -``TEST_LOAD <threshold>`` - While running tests in parallel, try not to start tests when they - may cause the CPU load to pass above a given threshold. If not - specified the :variable:`CTEST_TEST_LOAD` variable will be checked, - and then the ``--test-load`` command-line argument to :manual:`ctest(1)`. - See also the ``TestLoad`` setting in the :ref:`CTest Test Step`. - -``REPEAT <mode>:<n>`` - Run tests repeatedly based on the given ``<mode>`` up to ``<n>`` times. - The modes are: - - ``UNTIL_FAIL`` - Require each test to run ``<n>`` times without failing in order to pass. - This is useful in finding sporadic failures in test cases. - - ``UNTIL_PASS`` - Allow each test to run up to ``<n>`` times in order to pass. - Repeats tests if they fail for any reason. - This is useful in tolerating sporadic failures in test cases. - - ``AFTER_TIMEOUT`` - Allow each test to run up to ``<n>`` times in order to pass. - Repeats tests only if they timeout. - This is useful in tolerating sporadic timeouts in test cases - on busy machines. - -``SCHEDULE_RANDOM <ON|OFF>`` - Launch tests in a random order. This may be useful for detecting - implicit test dependencies. - -``STOP_ON_FAILURE`` - Stop the execution of the tests once one has failed. - -``STOP_TIME <time-of-day>`` - Specify a time of day at which the tests should all stop running. - -``RETURN_VALUE <result-var>`` - Store in the ``<result-var>`` variable ``0`` if all tests passed. - Store non-zero if anything went wrong. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Suppress any CTest-specific non-error messages that would have otherwise - been printed to the console. Output from the underlying test command is not - affected. Summary info detailing the percentage of passing tests is also - unaffected by the ``QUIET`` option. - -See also the :variable:`CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE` -and :variable:`CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE` variables.
diff --git a/share/cmake-3.18/Help/command/ctest_update.rst b/share/cmake-3.18/Help/command/ctest_update.rst deleted file mode 100644 index 96a11c9..0000000 --- a/share/cmake-3.18/Help/command/ctest_update.rst +++ /dev/null
@@ -1,39 +0,0 @@ -ctest_update ------------- - -Perform the :ref:`CTest Update Step` as a :ref:`Dashboard Client`. - -:: - - ctest_update([SOURCE <source-dir>] - [RETURN_VALUE <result-var>] - [CAPTURE_CMAKE_ERROR <result-var>] - [QUIET]) - -Update the source tree from version control and record results in -``Update.xml`` for submission with the :command:`ctest_submit` command. - -The options are: - -``SOURCE <source-dir>`` - Specify the source directory. If not given, the - :variable:`CTEST_SOURCE_DIRECTORY` variable is used. - -``RETURN_VALUE <result-var>`` - Store in the ``<result-var>`` variable the number of files - updated or ``-1`` on error. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs. - -``QUIET`` - Tell CTest to suppress most non-error messages that it would - have otherwise printed to the console. CTest will still report - the new revision of the repository and any conflicting files - that were found. - -The update always follows the version control branch currently checked -out in the source directory. See the :ref:`CTest Update Step` -documentation for information about variables that change the behavior -of ``ctest_update()``.
diff --git a/share/cmake-3.18/Help/command/ctest_upload.rst b/share/cmake-3.18/Help/command/ctest_upload.rst deleted file mode 100644 index 39d9de1..0000000 --- a/share/cmake-3.18/Help/command/ctest_upload.rst +++ /dev/null
@@ -1,22 +0,0 @@ -ctest_upload ------------- - -Upload files to a dashboard server as a :ref:`Dashboard Client`. - -:: - - ctest_upload(FILES <file>... [QUIET] [CAPTURE_CMAKE_ERROR <result-var>]) - -The options are: - -``FILES <file>...`` - Specify a list of files to be sent along with the build results to the - dashboard server. - -``QUIET`` - Suppress any CTest-specific non-error output that would have been - printed to the console otherwise. - -``CAPTURE_CMAKE_ERROR <result-var>`` - Store in the ``<result-var>`` variable -1 if there are any errors running - the command and prevent ctest from returning non-zero if an error occurs.
diff --git a/share/cmake-3.18/Help/command/enable_language.rst b/share/cmake-3.18/Help/command/enable_language.rst deleted file mode 100644 index fdc44f2..0000000 --- a/share/cmake-3.18/Help/command/enable_language.rst +++ /dev/null
@@ -1,25 +0,0 @@ -enable_language ---------------- -Enable a language (CXX/C/OBJC/OBJCXX/Fortran/etc) - -.. code-block:: cmake - - enable_language(<lang> [OPTIONAL] ) - -Enables support for the named language in CMake. This is -the same as the :command:`project` command but does not create any of the extra -variables that are created by the project command. Example languages -are ``CXX``, ``C``, ``CUDA``, ``OBJC``, ``OBJCXX``, ``Fortran``, and ``ASM``. - -If enabling ``ASM``, enable it last so that CMake can check whether -compilers for other languages like ``C`` work for assembly too. - -This command must be called in file scope, not in a function call. -Furthermore, it must be called in the highest directory common to all -targets using the named language directly for compiling sources or -indirectly through link dependencies. It is simplest to enable all -needed languages in the top-level directory of a project. - -The ``OPTIONAL`` keyword is a placeholder for future implementation and -does not currently work. Instead you can use the :module:`CheckLanguage` -module to verify support before enabling.
diff --git a/share/cmake-3.18/Help/command/execute_process.rst b/share/cmake-3.18/Help/command/execute_process.rst deleted file mode 100644 index b32025f..0000000 --- a/share/cmake-3.18/Help/command/execute_process.rst +++ /dev/null
@@ -1,129 +0,0 @@ -execute_process ---------------- - -Execute one or more child processes. - -.. code-block:: cmake - - execute_process(COMMAND <cmd1> [<arguments>] - [COMMAND <cmd2> [<arguments>]]... - [WORKING_DIRECTORY <directory>] - [TIMEOUT <seconds>] - [RESULT_VARIABLE <variable>] - [RESULTS_VARIABLE <variable>] - [OUTPUT_VARIABLE <variable>] - [ERROR_VARIABLE <variable>] - [INPUT_FILE <file>] - [OUTPUT_FILE <file>] - [ERROR_FILE <file>] - [OUTPUT_QUIET] - [ERROR_QUIET] - [COMMAND_ECHO <where>] - [OUTPUT_STRIP_TRAILING_WHITESPACE] - [ERROR_STRIP_TRAILING_WHITESPACE] - [ENCODING <name>] - [ECHO_OUTPUT_VARIABLE] - [ECHO_ERROR_VARIABLE]) - -Runs the given sequence of one or more commands. - -Commands are executed concurrently as a pipeline, with the standard -output of each process piped to the standard input of the next. -A single standard error pipe is used for all processes. - -Options: - -``COMMAND`` - A child process command line. - - CMake executes the child process using operating system APIs directly. - All arguments are passed VERBATIM to the child process. - No intermediate shell is used, so shell operators such as ``>`` - are treated as normal arguments. - (Use the ``INPUT_*``, ``OUTPUT_*``, and ``ERROR_*`` options to - redirect stdin, stdout, and stderr.) - - If a sequential execution of multiple commands is required, use multiple - :command:`execute_process` calls with a single ``COMMAND`` argument. - -``WORKING_DIRECTORY`` - The named directory will be set as the current working directory of - the child processes. - -``TIMEOUT`` - After the specified number of seconds (fractions allowed), all unfinished - child processes will be terminated, and the ``RESULT_VARIABLE`` will be - set to a string mentioning the "timeout". - -``RESULT_VARIABLE`` - The variable will be set to contain the result of last child process. - This will be an integer return code from the last child or a string - describing an error condition. - -``RESULTS_VARIABLE <variable>`` - The variable will be set to contain the result of all processes as a - :ref:`semicolon-separated list <CMake Language Lists>`, in order of the - given ``COMMAND`` arguments. Each entry will be an integer return code - from the corresponding child or a string describing an error condition. - -``OUTPUT_VARIABLE``, ``ERROR_VARIABLE`` - The variable named will be set with the contents of the standard output - and standard error pipes, respectively. If the same variable is named - for both pipes their output will be merged in the order produced. - -``INPUT_FILE, OUTPUT_FILE``, ``ERROR_FILE`` - The file named will be attached to the standard input of the first - process, standard output of the last process, or standard error of - all processes, respectively. If the same file is named for both - output and error then it will be used for both. - -``OUTPUT_QUIET``, ``ERROR_QUIET`` - The standard output or standard error results will be quietly ignored. - -``COMMAND_ECHO <where>`` - The command being run will be echo'ed to ``<where>`` with ``<where>`` - being set to one of ``STDERR``, ``STDOUT`` or ``NONE``. - See the :variable:`CMAKE_EXECUTE_PROCESS_COMMAND_ECHO` variable for a way - to control the default behavior when this option is not present. - -``ENCODING <name>`` - On Windows, the encoding that is used to decode output from the process. - Ignored on other platforms. - Valid encoding names are: - - ``NONE`` - Perform no decoding. This assumes that the process output is encoded - in the same way as CMake's internal encoding (UTF-8). - This is the default. - ``AUTO`` - Use the current active console's codepage or if that isn't - available then use ANSI. - ``ANSI`` - Use the ANSI codepage. - ``OEM`` - Use the original equipment manufacturer (OEM) code page. - ``UTF8`` or ``UTF-8`` - Use the UTF-8 codepage. Prior to CMake 3.11.0, only ``UTF8`` was accepted - for this encoding. In CMake 3.11.0, ``UTF-8`` was added for consistency with - the `UTF-8 RFC <https://www.ietf.org/rfc/rfc3629>`_ naming convention. - -``ECHO_OUTPUT_VARIABLE``, ``ECHO_ERROR_VARIABLE`` - The standard output or standard error will not be exclusively redirected to - the configured variables. - - The output will be duplicated, it will be sent into the configured variables - and also on standard output or standard error. - - This is analogous to the ``tee`` Unix command. - -If more than one ``OUTPUT_*`` or ``ERROR_*`` option is given for the -same pipe the precedence is not specified. -If no ``OUTPUT_*`` or ``ERROR_*`` options are given the output will -be shared with the corresponding pipes of the CMake process itself. - -The :command:`execute_process` command is a newer more powerful version of -:command:`exec_program`, but the old command has been kept for compatibility. -Both commands run while CMake is processing the project prior to build -system generation. Use :command:`add_custom_target` and -:command:`add_custom_command` to create custom commands that run at -build time.
diff --git a/share/cmake-3.18/Help/command/export.rst b/share/cmake-3.18/Help/command/export.rst deleted file mode 100644 index 2ca7056..0000000 --- a/share/cmake-3.18/Help/command/export.rst +++ /dev/null
@@ -1,86 +0,0 @@ -export ------- - -Export targets from the build tree for use by outside projects. - -.. code-block:: cmake - - export(EXPORT <export-name> [NAMESPACE <namespace>] [FILE <filename>]) - -Creates a file ``<filename>`` that may be included by outside projects to -import targets from the current project's build tree. This is useful -during cross-compiling to build utility executables that can run on -the host platform in one project and then import them into another -project being compiled for the target platform. If the ``NAMESPACE`` -option is given the ``<namespace>`` string will be prepended to all target -names written to the file. - -Target installations are associated with the export ``<export-name>`` -using the ``EXPORT`` option of the :command:`install(TARGETS)` command. - -The file created by this command is specific to the build tree and -should never be installed. See the :command:`install(EXPORT)` command to -export targets from an installation tree. - -The properties set on the generated IMPORTED targets will have the -same values as the final values of the input TARGETS. - -.. code-block:: cmake - - export(TARGETS [target1 [target2 [...]]] [NAMESPACE <namespace>] - [APPEND] FILE <filename> [EXPORT_LINK_INTERFACE_LIBRARIES]) - -This signature is similar to the ``EXPORT`` signature, but targets are listed -explicitly rather than specified as an export-name. If the APPEND option is -given the generated code will be appended to the file instead of overwriting it. -The EXPORT_LINK_INTERFACE_LIBRARIES keyword, if present, causes the -contents of the properties matching -``(IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)?`` to be exported, when -policy CMP0022 is NEW. If a library target is included in the export -but a target to which it links is not included the behavior is -unspecified. - -.. note:: - - :ref:`Object Libraries` under :generator:`Xcode` have special handling if - multiple architectures are listed in :variable:`CMAKE_OSX_ARCHITECTURES`. - In this case they will be exported as :ref:`Interface Libraries` with - no object files available to clients. This is sufficient to satisfy - transitive usage requirements of other targets that link to the - object libraries in their implementation. - -.. code-block:: cmake - - export(PACKAGE <PackageName>) - -Store the current build directory in the CMake user package registry -for package ``<PackageName>``. The :command:`find_package` command may consider the -directory while searching for package ``<PackageName>``. This helps dependent -projects find and use a package from the current project's build tree -without help from the user. Note that the entry in the package -registry that this command creates works only in conjunction with a -package configuration file (``<PackageName>Config.cmake``) that works with the -build tree. In some cases, for example for packaging and for system -wide installations, it is not desirable to write the user package -registry. - -By default the ``export(PACKAGE)`` command does nothing (see policy -:policy:`CMP0090`) because populating the user package registry has effects -outside the source and build trees. Set the -:variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` variable to add build directories to -the CMake user package registry. - -.. code-block:: cmake - - export(TARGETS [target1 [target2 [...]]] [ANDROID_MK <filename>]) - -This signature exports cmake built targets to the android ndk build system -by creating an Android.mk file that references the prebuilt targets. The -Android NDK supports the use of prebuilt libraries, both static and shared. -This allows cmake to build the libraries of a project and make them available -to an ndk build system complete with transitive dependencies, include flags -and defines required to use the libraries. The signature takes a list of -targets and puts them in the Android.mk file specified by the ``<filename>`` -given. This signature can only be used if policy CMP0022 is NEW for all -targets given. A error will be issued if that policy is set to OLD for one -of the targets.
diff --git a/share/cmake-3.18/Help/command/file.rst b/share/cmake-3.18/Help/command/file.rst deleted file mode 100644 index 693c059..0000000 --- a/share/cmake-3.18/Help/command/file.rst +++ /dev/null
@@ -1,955 +0,0 @@ -file ----- - -File manipulation command. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - `Reading`_ - file(`READ`_ <filename> <out-var> [...]) - file(`STRINGS`_ <filename> <out-var> [...]) - file(`\<HASH\> <HASH_>`_ <filename> <out-var>) - file(`TIMESTAMP`_ <filename> <out-var> [...]) - file(`GET_RUNTIME_DEPENDENCIES`_ [...]) - - `Writing`_ - file({`WRITE`_ | `APPEND`_} <filename> <content>...) - file({`TOUCH`_ | `TOUCH_NOCREATE`_} [<file>...]) - file(`GENERATE`_ OUTPUT <output-file> [...]) - file(`CONFIGURE`_ OUTPUT <output-file> CONTENT <content> [...]) - - `Filesystem`_ - file({`GLOB`_ | `GLOB_RECURSE`_} <out-var> [...] [<globbing-expr>...]) - file(`RENAME`_ <oldname> <newname>) - file({`REMOVE`_ | `REMOVE_RECURSE`_ } [<files>...]) - file(`MAKE_DIRECTORY`_ [<dir>...]) - file({`COPY`_ | `INSTALL`_} <file>... DESTINATION <dir> [...]) - file(`SIZE`_ <filename> <out-var>) - file(`READ_SYMLINK`_ <linkname> <out-var>) - file(`CREATE_LINK`_ <original> <linkname> [...]) - - `Path Conversion`_ - file(`RELATIVE_PATH`_ <out-var> <directory> <file>) - file({`TO_CMAKE_PATH`_ | `TO_NATIVE_PATH`_} <path> <out-var>) - - `Transfer`_ - file(`DOWNLOAD`_ <url> <file> [...]) - file(`UPLOAD`_ <file> <url> [...]) - - `Locking`_ - file(`LOCK`_ <path> [...]) - - `Archiving`_ - file(`ARCHIVE_CREATE`_ OUTPUT <archive> PATHS <paths>... [...]) - file(`ARCHIVE_EXTRACT`_ INPUT <archive> [...]) - -Reading -^^^^^^^ - -.. _READ: - -.. code-block:: cmake - - file(READ <filename> <variable> - [OFFSET <offset>] [LIMIT <max-in>] [HEX]) - -Read content from a file called ``<filename>`` and store it in a -``<variable>``. Optionally start from the given ``<offset>`` and -read at most ``<max-in>`` bytes. The ``HEX`` option causes data to -be converted to a hexadecimal representation (useful for binary data). If the -``HEX`` option is specified, letters in the output (``a`` through ``f``) are in -lowercase. - -.. _STRINGS: - -.. code-block:: cmake - - file(STRINGS <filename> <variable> [<options>...]) - -Parse a list of ASCII strings from ``<filename>`` and store it in -``<variable>``. Binary data in the file are ignored. Carriage return -(``\r``, CR) characters are ignored. The options are: - -``LENGTH_MAXIMUM <max-len>`` - Consider only strings of at most a given length. - -``LENGTH_MINIMUM <min-len>`` - Consider only strings of at least a given length. - -``LIMIT_COUNT <max-num>`` - Limit the number of distinct strings to be extracted. - -``LIMIT_INPUT <max-in>`` - Limit the number of input bytes to read from the file. - -``LIMIT_OUTPUT <max-out>`` - Limit the number of total bytes to store in the ``<variable>``. - -``NEWLINE_CONSUME`` - Treat newline characters (``\n``, LF) as part of string content - instead of terminating at them. - -``NO_HEX_CONVERSION`` - Intel Hex and Motorola S-record files are automatically converted to - binary while reading unless this option is given. - -``REGEX <regex>`` - Consider only strings that match the given regular expression. - -``ENCODING <encoding-type>`` - Consider strings of a given encoding. Currently supported encodings are: - UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE. If the ENCODING option - is not provided and the file has a Byte Order Mark, the ENCODING option - will be defaulted to respect the Byte Order Mark. - -For example, the code - -.. code-block:: cmake - - file(STRINGS myfile.txt myfile) - -stores a list in the variable ``myfile`` in which each item is a line -from the input file. - -.. _HASH: - -.. code-block:: cmake - - file(<HASH> <filename> <variable>) - -Compute a cryptographic hash of the content of ``<filename>`` and -store it in a ``<variable>``. The supported ``<HASH>`` algorithm names -are those listed by the :ref:`string(\<HASH\>) <Supported Hash Algorithms>` -command. - -.. _TIMESTAMP: - -.. code-block:: cmake - - file(TIMESTAMP <filename> <variable> [<format>] [UTC]) - -Compute a string representation of the modification time of ``<filename>`` -and store it in ``<variable>``. Should the command be unable to obtain a -timestamp variable will be set to the empty string (""). - -See the :command:`string(TIMESTAMP)` command for documentation of -the ``<format>`` and ``UTC`` options. - -.. _GET_RUNTIME_DEPENDENCIES: - -.. code-block:: cmake - - file(GET_RUNTIME_DEPENDENCIES - [RESOLVED_DEPENDENCIES_VAR <deps_var>] - [UNRESOLVED_DEPENDENCIES_VAR <unresolved_deps_var>] - [CONFLICTING_DEPENDENCIES_PREFIX <conflicting_deps_prefix>] - [EXECUTABLES [<executable_files>...]] - [LIBRARIES [<library_files>...]] - [MODULES [<module_files>...]] - [DIRECTORIES [<directories>...]] - [BUNDLE_EXECUTABLE <bundle_executable_file>] - [PRE_INCLUDE_REGEXES [<regexes>...]] - [PRE_EXCLUDE_REGEXES [<regexes>...]] - [POST_INCLUDE_REGEXES [<regexes>...]] - [POST_EXCLUDE_REGEXES [<regexes>...]] - ) - -Recursively get the list of libraries depended on by the given files. - -Please note that this sub-command is not intended to be used in project mode. -Instead, use it in an :command:`install(CODE)` or :command:`install(SCRIPT)` -block. For example: - -.. code-block:: cmake - - install(CODE [[ - file(GET_RUNTIME_DEPENDENCIES - # ... - ) - ]]) - -The arguments are as follows: - -``RESOLVED_DEPENDENCIES_VAR <deps_var>`` - Name of the variable in which to store the list of resolved dependencies. - -``UNRESOLVED_DEPENDENCIES_VAR <unresolved_deps_var>`` - Name of the variable in which to store the list of unresolved dependencies. - If this variable is not specified, and there are any unresolved dependencies, - an error is issued. - -``CONFLICTING_DEPENDENCIES_PREFIX <conflicting_deps_prefix>`` - Variable prefix in which to store conflicting dependency information. - Dependencies are conflicting if two files with the same name are found in - two different directories. The list of filenames that conflict are stored in - ``<conflicting_deps_prefix>_FILENAMES``. For each filename, the list of paths - that were found for that filename are stored in - ``<conflicting_deps_prefix>_<filename>``. - -``EXECUTABLES <executable_files>`` - List of executable files to read for dependencies. These are executables that - are typically created with :command:`add_executable`, but they do not have to - be created by CMake. On Apple platforms, the paths to these files determine - the value of ``@executable_path`` when recursively resolving the libraries. - Specifying any kind of library (``STATIC``, ``MODULE``, or ``SHARED``) here - will result in undefined behavior. - -``LIBRARIES <library_files>`` - List of library files to read for dependencies. These are libraries that are - typically created with :command:`add_library(SHARED)`, but they do not have - to be created by CMake. Specifying ``STATIC`` libraries, ``MODULE`` - libraries, or executables here will result in undefined behavior. - -``MODULES <module_files>`` - List of loadable module files to read for dependencies. These are modules - that are typically created with :command:`add_library(MODULE)`, but they do - not have to be created by CMake. They are typically used by calling - ``dlopen()`` at runtime rather than linked at link time with ``ld -l``. - Specifying ``STATIC`` libraries, ``SHARED`` libraries, or executables here - will result in undefined behavior. - -``DIRECTORIES <directories>`` - List of additional directories to search for dependencies. On Linux - platforms, these directories are searched if the dependency is not found in - any of the other usual paths. If it is found in such a directory, a warning - is issued, because it means that the file is incomplete (it does not list all - of the directories that contain its dependencies). On Windows platforms, - these directories are searched if the dependency is not found in any of the - other search paths, but no warning is issued, because searching other paths - is a normal part of Windows dependency resolution. On Apple platforms, this - argument has no effect. - -``BUNDLE_EXECUTABLE <bundle_executable_file>`` - Executable to treat as the "bundle executable" when resolving libraries. On - Apple platforms, this argument determines the value of ``@executable_path`` - when recursively resolving libraries for ``LIBRARIES`` and ``MODULES`` files. - It has no effect on ``EXECUTABLES`` files. On other platforms, it has no - effect. This is typically (but not always) one of the executables in the - ``EXECUTABLES`` argument which designates the "main" executable of the - package. - -The following arguments specify filters for including or excluding libraries to -be resolved. See below for a full description of how they work. - -``PRE_INCLUDE_REGEXES <regexes>`` - List of pre-include regexes through which to filter the names of - not-yet-resolved dependencies. - -``PRE_EXCLUDE_REGEXES <regexes>`` - List of pre-exclude regexes through which to filter the names of - not-yet-resolved dependencies. - -``POST_INCLUDE_REGEXES <regexes>`` - List of post-include regexes through which to filter the names of resolved - dependencies. - -``POST_EXCLUDE_REGEXES <regexes>`` - List of post-exclude regexes through which to filter the names of resolved - dependencies. - -These arguments can be used to exclude unwanted system libraries when -resolving the dependencies, or to include libraries from a specific -directory. The filtering works as follows: - -1. If the not-yet-resolved dependency matches any of the - ``PRE_INCLUDE_REGEXES``, steps 2 and 3 are skipped, and the dependency - resolution proceeds to step 4. -2. If the not-yet-resolved dependency matches any of the - ``PRE_EXCLUDE_REGEXES``, dependency resolution stops for that dependency. -3. Otherwise, dependency resolution proceeds. -4. ``file(GET_RUNTIME_DEPENDENCIES)`` searches for the dependency according to - the linking rules of the platform (see below). -5. If the dependency is found, and its full path matches one of the - ``POST_INCLUDE_REGEXES``, the full path is added to the resolved - dependencies, and ``file(GET_RUNTIME_DEPENDENCIES)`` recursively resolves - that library's own dependencies. Otherwise, resolution proceeds to step 6. -6. If the dependency is found, but its full path matches one of the - ``POST_EXCLUDE_REGEXES``, it is not added to the resolved dependencies, and - dependency resolution stops for that dependency. -7. If the dependency is found, and its full path does not match either - ``POST_INCLUDE_REGEXES`` or ``POST_EXCLUDE_REGEXES``, the full path is added - to the resolved dependencies, and ``file(GET_RUNTIME_DEPENDENCIES)`` - recursively resolves that library's own dependencies. - -Different platforms have different rules for how dependencies are resolved. -These specifics are described here. - -On Linux platforms, library resolution works as follows: - -1. If the depending file does not have any ``RUNPATH`` entries, and the library - exists in one of the depending file's ``RPATH`` entries, or its parents', in - that order, the dependency is resolved to that file. -2. Otherwise, if the depending file has any ``RUNPATH`` entries, and the - library exists in one of those entries, the dependency is resolved to that - file. -3. Otherwise, if the library exists in one of the directories listed by - ``ldconfig``, the dependency is resolved to that file. -4. Otherwise, if the library exists in one of the ``DIRECTORIES`` entries, the - dependency is resolved to that file. In this case, a warning is issued, - because finding a file in one of the ``DIRECTORIES`` means that the - depending file is not complete (it does not list all the directories from - which it pulls dependencies). -5. Otherwise, the dependency is unresolved. - -On Windows platforms, library resolution works as follows: - -1. The dependent DLL name is converted to lowercase. Windows DLL names are - case-insensitive, and some linkers mangle the case of the DLL dependency - names. However, this makes it more difficult for ``PRE_INCLUDE_REGEXES``, - ``PRE_EXCLUDE_REGEXES``, ``POST_INCLUDE_REGEXES``, and - ``POST_EXCLUDE_REGEXES`` to properly filter DLL names - every regex would - have to check for both uppercase and lowercase letters. For example: - - .. code-block:: cmake - - file(GET_RUNTIME_DEPENDENCIES - # ... - PRE_INCLUDE_REGEXES "^[Mm][Yy][Ll][Ii][Bb][Rr][Aa][Rr][Yy]\\.[Dd][Ll][Ll]$" - ) - - Converting the DLL name to lowercase allows the regexes to only match - lowercase names, thus simplifying the regex. For example: - - .. code-block:: cmake - - file(GET_RUNTIME_DEPENDENCIES - # ... - PRE_INCLUDE_REGEXES "^mylibrary\\.dll$" - ) - - This regex will match ``mylibrary.dll`` regardless of how it is cased, - either on disk or in the depending file. (For example, it will match - ``mylibrary.dll``, ``MyLibrary.dll``, and ``MYLIBRARY.DLL``.) - - Please note that the directory portion of any resolved DLLs retains its - casing and is not converted to lowercase. Only the filename portion is - converted. - -2. (**Not yet implemented**) If the depending file is a Windows Store app, and - the dependency is listed as a dependency in the application's package - manifest, the dependency is resolved to that file. -3. Otherwise, if the library exists in the same directory as the depending - file, the dependency is resolved to that file. -4. Otherwise, if the library exists in either the operating system's - ``system32`` directory or the ``Windows`` directory, in that order, the - dependency is resolved to that file. -5. Otherwise, if the library exists in one of the directories specified by - ``DIRECTORIES``, in the order they are listed, the dependency is resolved to - that file. In this case, a warning is not issued, because searching other - directories is a normal part of Windows library resolution. -6. Otherwise, the dependency is unresolved. - -On Apple platforms, library resolution works as follows: - -1. If the dependency starts with ``@executable_path/``, and an ``EXECUTABLES`` - argument is in the process of being resolved, and replacing - ``@executable_path/`` with the directory of the executable yields an - existing file, the dependency is resolved to that file. -2. Otherwise, if the dependency starts with ``@executable_path/``, and there is - a ``BUNDLE_EXECUTABLE`` argument, and replacing ``@executable_path/`` with - the directory of the bundle executable yields an existing file, the - dependency is resolved to that file. -3. Otherwise, if the dependency starts with ``@loader_path/``, and replacing - ``@loader_path/`` with the directory of the depending file yields an - existing file, the dependency is resolved to that file. -4. Otherwise, if the dependency starts with ``@rpath/``, and replacing - ``@rpath/`` with one of the ``RPATH`` entries of the depending file yields - an existing file, the dependency is resolved to that file. Note that - ``RPATH`` entries that start with ``@executable_path/`` or ``@loader_path/`` - also have these items replaced with the appropriate path. -5. Otherwise, if the dependency is an absolute file that exists, the dependency - is resolved to that file. -6. Otherwise, the dependency is unresolved. - -This function accepts several variables that determine which tool is used for -dependency resolution: - -.. variable:: CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM - - Determines which operating system and executable format the files are built - for. This could be one of several values: - - * ``linux+elf`` - * ``windows+pe`` - * ``macos+macho`` - - If this variable is not specified, it is determined automatically by system - introspection. - -.. variable:: CMAKE_GET_RUNTIME_DEPENDENCIES_TOOL - - Determines the tool to use for dependency resolution. It could be one of - several values, depending on the value of - :variable:`CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM`: - - ================================================= ============================================= - ``CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM`` ``CMAKE_GET_RUNTIME_DEPENDENCIES_TOOL`` - ================================================= ============================================= - ``linux+elf`` ``objdump`` - ``windows+pe`` ``dumpbin`` - ``windows+pe`` ``objdump`` - ``macos+macho`` ``otool`` - ================================================= ============================================= - - If this variable is not specified, it is determined automatically by system - introspection. - -.. variable:: CMAKE_GET_RUNTIME_DEPENDENCIES_COMMAND - - Determines the path to the tool to use for dependency resolution. This is the - actual path to ``objdump``, ``dumpbin``, or ``otool``. - - If this variable is not specified, it is determined by the value of - ``CMAKE_OBJDUMP`` if set, else by system introspection. - -Writing -^^^^^^^ - -.. _WRITE: -.. _APPEND: - -.. code-block:: cmake - - file(WRITE <filename> <content>...) - file(APPEND <filename> <content>...) - -Write ``<content>`` into a file called ``<filename>``. If the file does -not exist, it will be created. If the file already exists, ``WRITE`` -mode will overwrite it and ``APPEND`` mode will append to the end. -Any directories in the path specified by ``<filename>`` that do not -exist will be created. - -If the file is a build input, use the :command:`configure_file` command -to update the file only when its content changes. - -.. _TOUCH: -.. _TOUCH_NOCREATE: - -.. code-block:: cmake - - file(TOUCH [<files>...]) - file(TOUCH_NOCREATE [<files>...]) - -Create a file with no content if it does not yet exist. If the file already -exists, its access and/or modification will be updated to the time when the -function call is executed. - -Use TOUCH_NOCREATE to touch a file if it exists but not create it. If a file -does not exist it will be silently ignored. - -With TOUCH and TOUCH_NOCREATE the contents of an existing file will not be -modified. - -.. _GENERATE: - -.. code-block:: cmake - - file(GENERATE OUTPUT output-file - <INPUT input-file|CONTENT content> - [CONDITION expression]) - -Generate an output file for each build configuration supported by the current -:manual:`CMake Generator <cmake-generators(7)>`. Evaluate -:manual:`generator expressions <cmake-generator-expressions(7)>` -from the input content to produce the output content. The options are: - -``CONDITION <condition>`` - Generate the output file for a particular configuration only if - the condition is true. The condition must be either ``0`` or ``1`` - after evaluating generator expressions. - -``CONTENT <content>`` - Use the content given explicitly as input. - -``INPUT <input-file>`` - Use the content from a given file as input. - A relative path is treated with respect to the value of - :variable:`CMAKE_CURRENT_SOURCE_DIR`. See policy :policy:`CMP0070`. - -``OUTPUT <output-file>`` - Specify the output file name to generate. Use generator expressions - such as ``$<CONFIG>`` to specify a configuration-specific output file - name. Multiple configurations may generate the same output file only - if the generated content is identical. Otherwise, the ``<output-file>`` - must evaluate to an unique name for each configuration. - A relative path (after evaluating generator expressions) is treated - with respect to the value of :variable:`CMAKE_CURRENT_BINARY_DIR`. - See policy :policy:`CMP0070`. - -Exactly one ``CONTENT`` or ``INPUT`` option must be given. A specific -``OUTPUT`` file may be named by at most one invocation of ``file(GENERATE)``. -Generated files are modified and their timestamp updated on subsequent cmake -runs only if their content is changed. - -Note also that ``file(GENERATE)`` does not create the output file until the -generation phase. The output file will not yet have been written when the -``file(GENERATE)`` command returns, it is written only after processing all -of a project's ``CMakeLists.txt`` files. - -.. _CONFIGURE: - -.. code-block:: cmake - - file(CONFIGURE OUTPUT output-file - CONTENT content - [ESCAPE_QUOTES] [@ONLY] - [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ]) - -Generate an output file using the input given by ``CONTENT`` and substitute -variable values referenced as ``@VAR@`` or ``${VAR}`` contained therein. The -substitution rules behave the same as the :command:`configure_file` command. -In order to match :command:`configure_file`'s behavior, generator expressions -are not supported for both ``OUTPUT`` and ``CONTENT``. - -The arguments are: - -``OUTPUT <output-file>`` - Specify the output file name to generate. A relative path is treated with - respect to the value of :variable:`CMAKE_CURRENT_BINARY_DIR`. - ``<output-file>`` does not support generator expressions. - -``CONTENT <content>`` - Use the content given explicitly as input. - ``<content>`` does not support generator expressions. - -``ESCAPE_QUOTES`` - Escape any substituted quotes with backslashes (C-style). - -``@ONLY`` - Restrict variable replacement to references of the form ``@VAR@``. - This is useful for configuring scripts that use ``${VAR}`` syntax. - -``NEWLINE_STYLE <style>`` - Specify the newline style for the output file. Specify - ``UNIX`` or ``LF`` for ``\n`` newlines, or specify - ``DOS``, ``WIN32``, or ``CRLF`` for ``\r\n`` newlines. - -Filesystem -^^^^^^^^^^ - -.. _GLOB: -.. _GLOB_RECURSE: - -.. code-block:: cmake - - file(GLOB <variable> - [LIST_DIRECTORIES true|false] [RELATIVE <path>] [CONFIGURE_DEPENDS] - [<globbing-expressions>...]) - file(GLOB_RECURSE <variable> [FOLLOW_SYMLINKS] - [LIST_DIRECTORIES true|false] [RELATIVE <path>] [CONFIGURE_DEPENDS] - [<globbing-expressions>...]) - -Generate a list of files that match the ``<globbing-expressions>`` and -store it into the ``<variable>``. Globbing expressions are similar to -regular expressions, but much simpler. If ``RELATIVE`` flag is -specified, the results will be returned as relative paths to the given -path. The results will be ordered lexicographically. - -On Windows and macOS, globbing is case-insensitive even if the underlying -filesystem is case-sensitive (both filenames and globbing expressions are -converted to lowercase before matching). On other platforms, globbing is -case-sensitive. - -If the ``CONFIGURE_DEPENDS`` flag is specified, CMake will add logic -to the main build system check target to rerun the flagged ``GLOB`` commands -at build time. If any of the outputs change, CMake will regenerate the build -system. - -By default ``GLOB`` lists directories - directories are omitted in result if -``LIST_DIRECTORIES`` is set to false. - -.. note:: - We do not recommend using GLOB to collect a list of source files from - your source tree. If no CMakeLists.txt file changes when a source is - added or removed then the generated build system cannot know when to - ask CMake to regenerate. - The ``CONFIGURE_DEPENDS`` flag may not work reliably on all generators, or if - a new generator is added in the future that cannot support it, projects using - it will be stuck. Even if ``CONFIGURE_DEPENDS`` works reliably, there is - still a cost to perform the check on every rebuild. - -Examples of globbing expressions include:: - - *.cxx - match all files with extension cxx - *.vt? - match all files with extension vta,...,vtz - f[3-5].txt - match files f3.txt, f4.txt, f5.txt - -The ``GLOB_RECURSE`` mode will traverse all the subdirectories of the -matched directory and match the files. Subdirectories that are symlinks -are only traversed if ``FOLLOW_SYMLINKS`` is given or policy -:policy:`CMP0009` is not set to ``NEW``. - -By default ``GLOB_RECURSE`` omits directories from result list - setting -``LIST_DIRECTORIES`` to true adds directories to result list. -If ``FOLLOW_SYMLINKS`` is given or policy :policy:`CMP0009` is not set to -``NEW`` then ``LIST_DIRECTORIES`` treats symlinks as directories. - -Examples of recursive globbing include:: - - /dir/*.py - match all python files in /dir and subdirectories - -.. _RENAME: - -.. code-block:: cmake - - file(RENAME <oldname> <newname>) - -Move a file or directory within a filesystem from ``<oldname>`` to -``<newname>``, replacing the destination atomically. - -.. _REMOVE: -.. _REMOVE_RECURSE: - -.. code-block:: cmake - - file(REMOVE [<files>...]) - file(REMOVE_RECURSE [<files>...]) - -Remove the given files. The ``REMOVE_RECURSE`` mode will remove the given -files and directories, also non-empty directories. No error is emitted if a -given file does not exist. Relative input paths are evaluated with respect -to the current source directory. Empty input paths are ignored with a warning. - -.. _MAKE_DIRECTORY: - -.. code-block:: cmake - - file(MAKE_DIRECTORY [<directories>...]) - -Create the given directories and their parents as needed. - -.. _COPY: -.. _INSTALL: - -.. code-block:: cmake - - file(<COPY|INSTALL> <files>... DESTINATION <dir> - [FILE_PERMISSIONS <permissions>...] - [DIRECTORY_PERMISSIONS <permissions>...] - [NO_SOURCE_PERMISSIONS] [USE_SOURCE_PERMISSIONS] - [FOLLOW_SYMLINK_CHAIN] - [FILES_MATCHING] - [[PATTERN <pattern> | REGEX <regex>] - [EXCLUDE] [PERMISSIONS <permissions>...]] [...]) - -The ``COPY`` signature copies files, directories, and symlinks to a -destination folder. Relative input paths are evaluated with respect -to the current source directory, and a relative destination is -evaluated with respect to the current build directory. Copying -preserves input file timestamps, and optimizes out a file if it exists -at the destination with the same timestamp. Copying preserves input -permissions unless explicit permissions or ``NO_SOURCE_PERMISSIONS`` -are given (default is ``USE_SOURCE_PERMISSIONS``). - -If ``FOLLOW_SYMLINK_CHAIN`` is specified, ``COPY`` will recursively resolve -the symlinks at the paths given until a real file is found, and install -a corresponding symlink in the destination for each symlink encountered. For -each symlink that is installed, the resolution is stripped of the directory, -leaving only the filename, meaning that the new symlink points to a file in -the same directory as the symlink. This feature is useful on some Unix systems, -where libraries are installed as a chain of symlinks with version numbers, with -less specific versions pointing to more specific versions. -``FOLLOW_SYMLINK_CHAIN`` will install all of these symlinks and the library -itself into the destination directory. For example, if you have the following -directory structure: - -* ``/opt/foo/lib/libfoo.so.1.2.3`` -* ``/opt/foo/lib/libfoo.so.1.2 -> libfoo.so.1.2.3`` -* ``/opt/foo/lib/libfoo.so.1 -> libfoo.so.1.2`` -* ``/opt/foo/lib/libfoo.so -> libfoo.so.1`` - -and you do: - -.. code-block:: cmake - - file(COPY /opt/foo/lib/libfoo.so DESTINATION lib FOLLOW_SYMLINK_CHAIN) - -This will install all of the symlinks and ``libfoo.so.1.2.3`` itself into -``lib``. - -See the :command:`install(DIRECTORY)` command for documentation of -permissions, ``FILES_MATCHING``, ``PATTERN``, ``REGEX``, and -``EXCLUDE`` options. Copying directories preserves the structure -of their content even if options are used to select a subset of -files. - -The ``INSTALL`` signature differs slightly from ``COPY``: it prints -status messages (subject to the :variable:`CMAKE_INSTALL_MESSAGE` variable), -and ``NO_SOURCE_PERMISSIONS`` is default. -Installation scripts generated by the :command:`install` command -use this signature (with some undocumented options for internal use). - -.. _SIZE: - -.. code-block:: cmake - - file(SIZE <filename> <variable>) - -Determine the file size of the ``<filename>`` and put the result in -``<variable>`` variable. Requires that ``<filename>`` is a valid path -pointing to a file and is readable. - -.. _READ_SYMLINK: - -.. code-block:: cmake - - file(READ_SYMLINK <linkname> <variable>) - -This subcommand queries the symlink ``<linkname>`` and stores the path it -points to in the result ``<variable>``. If ``<linkname>`` does not exist or -is not a symlink, CMake issues a fatal error. - -Note that this command returns the raw symlink path and does not resolve -a relative path. The following is an example of how to ensure that an -absolute path is obtained: - -.. code-block:: cmake - - set(linkname "/path/to/foo.sym") - file(READ_SYMLINK "${linkname}" result) - if(NOT IS_ABSOLUTE "${result}") - get_filename_component(dir "${linkname}" DIRECTORY) - set(result "${dir}/${result}") - endif() - -.. _CREATE_LINK: - -.. code-block:: cmake - - file(CREATE_LINK <original> <linkname> - [RESULT <result>] [COPY_ON_ERROR] [SYMBOLIC]) - -Create a link ``<linkname>`` that points to ``<original>``. -It will be a hard link by default, but providing the ``SYMBOLIC`` option -results in a symbolic link instead. Hard links require that ``original`` -exists and is a file, not a directory. If ``<linkname>`` already exists, -it will be overwritten. - -The ``<result>`` variable, if specified, receives the status of the operation. -It is set to ``0`` upon success or an error message otherwise. If ``RESULT`` -is not specified and the operation fails, a fatal error is emitted. - -Specifying ``COPY_ON_ERROR`` enables copying the file as a fallback if -creating the link fails. It can be useful for handling situations such as -``<original>`` and ``<linkname>`` being on different drives or mount points, -which would make them unable to support a hard link. - -Path Conversion -^^^^^^^^^^^^^^^ - -.. _RELATIVE_PATH: - -.. code-block:: cmake - - file(RELATIVE_PATH <variable> <directory> <file>) - -Compute the relative path from a ``<directory>`` to a ``<file>`` and -store it in the ``<variable>``. - -.. _TO_CMAKE_PATH: -.. _TO_NATIVE_PATH: - -.. code-block:: cmake - - file(TO_CMAKE_PATH "<path>" <variable>) - file(TO_NATIVE_PATH "<path>" <variable>) - -The ``TO_CMAKE_PATH`` mode converts a native ``<path>`` into a cmake-style -path with forward-slashes (``/``). The input can be a single path or a -system search path like ``$ENV{PATH}``. A search path will be converted -to a cmake-style list separated by ``;`` characters. - -The ``TO_NATIVE_PATH`` mode converts a cmake-style ``<path>`` into a native -path with platform-specific slashes (``\`` on Windows and ``/`` elsewhere). - -Always use double quotes around the ``<path>`` to be sure it is treated -as a single argument to this command. - -Transfer -^^^^^^^^ - -.. _DOWNLOAD: -.. _UPLOAD: - -.. code-block:: cmake - - file(DOWNLOAD <url> <file> [<options>...]) - file(UPLOAD <file> <url> [<options>...]) - -The ``DOWNLOAD`` mode downloads the given ``<url>`` to a local ``<file>``. -The ``UPLOAD`` mode uploads a local ``<file>`` to a given ``<url>``. - -Options to both ``DOWNLOAD`` and ``UPLOAD`` are: - -``INACTIVITY_TIMEOUT <seconds>`` - Terminate the operation after a period of inactivity. - -``LOG <variable>`` - Store a human-readable log of the operation in a variable. - -``SHOW_PROGRESS`` - Print progress information as status messages until the operation is - complete. - -``STATUS <variable>`` - Store the resulting status of the operation in a variable. - The status is a ``;`` separated list of length 2. - The first element is the numeric return value for the operation, - and the second element is a string value for the error. - A ``0`` numeric error means no error in the operation. - -``TIMEOUT <seconds>`` - Terminate the operation after a given total time has elapsed. - -``USERPWD <username>:<password>`` - Set username and password for operation. - -``HTTPHEADER <HTTP-header>`` - HTTP header for operation. Suboption can be repeated several times. - -``NETRC <level>`` - Specify whether the .netrc file is to be used for operation. If this - option is not specified, the value of the ``CMAKE_NETRC`` variable - will be used instead. - Valid levels are: - - ``IGNORED`` - The .netrc file is ignored. - This is the default. - ``OPTIONAL`` - The .netrc file is optional, and information in the URL is preferred. - The file will be scanned to find which ever information is not specified - in the URL. - ``REQUIRED`` - The .netrc file is required, and information in the URL is ignored. - -``NETRC_FILE <file>`` - Specify an alternative .netrc file to the one in your home directory, - if the ``NETRC`` level is ``OPTIONAL`` or ``REQUIRED``. If this option - is not specified, the value of the ``CMAKE_NETRC_FILE`` variable will - be used instead. - -If neither ``NETRC`` option is given CMake will check variables -``CMAKE_NETRC`` and ``CMAKE_NETRC_FILE``, respectively. - -``TLS_VERIFY <ON|OFF>`` - Specify whether to verify the server certificate for ``https://`` URLs. - The default is to *not* verify. - -``TLS_CAINFO <file>`` - Specify a custom Certificate Authority file for ``https://`` URLs. - -For ``https://`` URLs CMake must be built with OpenSSL support. ``TLS/SSL`` -certificates are not checked by default. Set ``TLS_VERIFY`` to ``ON`` to -check certificates. If neither ``TLS`` option is given CMake will check -variables ``CMAKE_TLS_VERIFY`` and ``CMAKE_TLS_CAINFO``, respectively. - -Additional options to ``DOWNLOAD`` are: - -``EXPECTED_HASH ALGO=<value>`` - - Verify that the downloaded content hash matches the expected value, where - ``ALGO`` is one of the algorithms supported by ``file(<HASH>)``. - If it does not match, the operation fails with an error. - -``EXPECTED_MD5 <value>`` - Historical short-hand for ``EXPECTED_HASH MD5=<value>``. - -Locking -^^^^^^^ - -.. _LOCK: - -.. code-block:: cmake - - file(LOCK <path> [DIRECTORY] [RELEASE] - [GUARD <FUNCTION|FILE|PROCESS>] - [RESULT_VARIABLE <variable>] - [TIMEOUT <seconds>]) - -Lock a file specified by ``<path>`` if no ``DIRECTORY`` option present and file -``<path>/cmake.lock`` otherwise. File will be locked for scope defined by -``GUARD`` option (default value is ``PROCESS``). ``RELEASE`` option can be used -to unlock file explicitly. If option ``TIMEOUT`` is not specified CMake will -wait until lock succeed or until fatal error occurs. If ``TIMEOUT`` is set to -``0`` lock will be tried once and result will be reported immediately. If -``TIMEOUT`` is not ``0`` CMake will try to lock file for the period specified -by ``<seconds>`` value. Any errors will be interpreted as fatal if there is no -``RESULT_VARIABLE`` option. Otherwise result will be stored in ``<variable>`` -and will be ``0`` on success or error message on failure. - -Note that lock is advisory - there is no guarantee that other processes will -respect this lock, i.e. lock synchronize two or more CMake instances sharing -some modifiable resources. Similar logic applied to ``DIRECTORY`` option - -locking parent directory doesn't prevent other ``LOCK`` commands to lock any -child directory or file. - -Trying to lock file twice is not allowed. Any intermediate directories and -file itself will be created if they not exist. ``GUARD`` and ``TIMEOUT`` -options ignored on ``RELEASE`` operation. - -Archiving -^^^^^^^^^ - -.. _ARCHIVE_CREATE: - -.. code-block:: cmake - - file(ARCHIVE_CREATE OUTPUT <archive> - PATHS <paths>... - [FORMAT <format>] - [COMPRESSION <compression>] - [MTIME <mtime>] - [VERBOSE]) - -Creates the specified ``<archive>`` file with the files and directories -listed in ``<paths>``. Note that ``<paths>`` must list actual files or -directories, wildcards are not supported. - -Use the ``FORMAT`` option to specify the archive format. Supported values -for ``<format>`` are ``7zip``, ``gnutar``, ``pax``, ``paxr``, ``raw`` and -``zip``. If ``FORMAT`` is not given, the default format is ``paxr``. - -Some archive formats allow the type of compression to be specified. -The ``7zip`` and ``zip`` archive formats already imply a specific type of -compression. The other formats use no compression by default, but can be -directed to do so with the ``COMPRESSION`` option. Valid values for -``<compression>`` are ``None``, ``BZip2``, ``GZip``, ``XZ``, and ``Zstd``. - -.. note:: - With ``FORMAT`` set to ``raw`` only one file will be compressed with the - compression type specified by ``COMPRESSION``. - -The ``VERBOSE`` option enables verbose output for the archive operation. - -To specify the modification time recorded in tarball entries, use -the ``MTIME`` option. - -.. _ARCHIVE_EXTRACT: - -.. code-block:: cmake - - file(ARCHIVE_EXTRACT INPUT <archive> - [DESTINATION <dir>] - [PATTERNS <patterns>...] - [LIST_ONLY] - [VERBOSE]) - -Extracts or lists the content of the specified ``<archive>``. - -The directory where the content of the archive will be extracted to can -be specified using the ``DESTINATION`` option. If the directory does not -exist, it will be created. If ``DESTINATION`` is not given, the current -binary directory will be used. - -If required, you may select which files and directories to list or extract -from the archive using the specified ``<patterns>``. Wildcards are supported. -If the ``PATTERNS`` option is not given, the entire archive will be listed or -extracted. - -``LIST_ONLY`` will list the files in the archive rather than extract them. - -With ``VERBOSE``, the command will produce verbose output.
diff --git a/share/cmake-3.18/Help/command/find_file.rst b/share/cmake-3.18/Help/command/find_file.rst deleted file mode 100644 index 3f03f37..0000000 --- a/share/cmake-3.18/Help/command/find_file.rst +++ /dev/null
@@ -1,36 +0,0 @@ -find_file ---------- - -.. |FIND_XXX| replace:: find_file -.. |NAMES| replace:: NAMES name1 [name2 ...] -.. |SEARCH_XXX| replace:: full path to a file -.. |SEARCH_XXX_DESC| replace:: full path to named file -.. |prefix_XXX_SUBDIR| replace:: ``<prefix>/include`` -.. |entry_XXX_SUBDIR| replace:: ``<entry>/include`` - -.. |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |CMAKE_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_XXX_PATH| replace:: :variable:`CMAKE_INCLUDE_PATH` -.. |CMAKE_XXX_MAC_PATH| replace:: :variable:`CMAKE_FRAMEWORK_PATH` - -.. |SYSTEM_ENVIRONMENT_PATH_XXX| replace:: The directories in ``PATH`` and ``INCLUDE``. -.. |SYSTEM_ENVIRONMENT_PATH_WINDOWS_XXX| replace:: On Windows hosts: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |SYSTEM_ENVIRONMENT_PREFIX_PATH_XXX_SUBDIR|. - -.. |CMAKE_SYSTEM_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |CMAKE_SYSTEM_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_SYSTEM_XXX_PATH| replace:: - :variable:`CMAKE_SYSTEM_INCLUDE_PATH` -.. |CMAKE_SYSTEM_XXX_MAC_PATH| replace:: - :variable:`CMAKE_SYSTEM_FRAMEWORK_PATH` - -.. |CMAKE_FIND_ROOT_PATH_MODE_XXX| replace:: - :variable:`CMAKE_FIND_ROOT_PATH_MODE_INCLUDE` - -.. include:: FIND_XXX.txt
diff --git a/share/cmake-3.18/Help/command/find_library.rst b/share/cmake-3.18/Help/command/find_library.rst deleted file mode 100644 index 8a55aca..0000000 --- a/share/cmake-3.18/Help/command/find_library.rst +++ /dev/null
@@ -1,81 +0,0 @@ -find_library ------------- - -.. |FIND_XXX| replace:: find_library -.. |NAMES| replace:: NAMES name1 [name2 ...] [NAMES_PER_DIR] -.. |SEARCH_XXX| replace:: library -.. |SEARCH_XXX_DESC| replace:: library -.. |prefix_XXX_SUBDIR| replace:: ``<prefix>/lib`` -.. |entry_XXX_SUBDIR| replace:: ``<entry>/lib`` - -.. |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX| replace:: - ``<prefix>/lib/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` is set, - and |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_PREFIX_PATH_XXX| replace:: - ``<prefix>/lib/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` is set, - and |CMAKE_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_XXX_PATH| replace:: :variable:`CMAKE_LIBRARY_PATH` -.. |CMAKE_XXX_MAC_PATH| replace:: :variable:`CMAKE_FRAMEWORK_PATH` - -.. |SYSTEM_ENVIRONMENT_PATH_XXX| replace:: The directories in ``PATH`` and ``INCLUDE``. -.. |SYSTEM_ENVIRONMENT_PATH_WINDOWS_XXX| replace:: On Windows hosts: - ``<prefix>/lib/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |SYSTEM_ENVIRONMENT_PREFIX_PATH_XXX_SUBDIR|. - -.. |CMAKE_SYSTEM_PREFIX_PATH_XXX| replace:: - ``<prefix>/lib/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` is set, - and |CMAKE_SYSTEM_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_SYSTEM_XXX_PATH| replace:: - :variable:`CMAKE_SYSTEM_LIBRARY_PATH` -.. |CMAKE_SYSTEM_XXX_MAC_PATH| replace:: - :variable:`CMAKE_SYSTEM_FRAMEWORK_PATH` - -.. |CMAKE_FIND_ROOT_PATH_MODE_XXX| replace:: - :variable:`CMAKE_FIND_ROOT_PATH_MODE_LIBRARY` - -.. include:: FIND_XXX.txt - -When more than one value is given to the ``NAMES`` option this command by -default will consider one name at a time and search every directory -for it. The ``NAMES_PER_DIR`` option tells this command to consider one -directory at a time and search for all names in it. - -Each library name given to the ``NAMES`` option is first considered -as a library file name and then considered with platform-specific -prefixes (e.g. ``lib``) and suffixes (e.g. ``.so``). Therefore one -may specify library file names such as ``libfoo.a`` directly. -This can be used to locate static libraries on UNIX-like systems. - -If the library found is a framework, then ``<VAR>`` will be set to the full -path to the framework ``<fullPath>/A.framework``. When a full path to a -framework is used as a library, CMake will use a ``-framework A``, and a -``-F<fullPath>`` to link the framework to the target. - -If the :variable:`CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX` variable is set all -search paths will be tested as normal, with the suffix appended, and with -all matches of ``lib/`` replaced with -``lib${CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX}/``. This variable overrides -the :prop_gbl:`FIND_LIBRARY_USE_LIB32_PATHS`, -:prop_gbl:`FIND_LIBRARY_USE_LIBX32_PATHS`, -and :prop_gbl:`FIND_LIBRARY_USE_LIB64_PATHS` global properties. - -If the :prop_gbl:`FIND_LIBRARY_USE_LIB32_PATHS` global property is set -all search paths will be tested as normal, with ``32/`` appended, and -with all matches of ``lib/`` replaced with ``lib32/``. This property is -automatically set for the platforms that are known to need it if at -least one of the languages supported by the :command:`project` command -is enabled. - -If the :prop_gbl:`FIND_LIBRARY_USE_LIBX32_PATHS` global property is set -all search paths will be tested as normal, with ``x32/`` appended, and -with all matches of ``lib/`` replaced with ``libx32/``. This property is -automatically set for the platforms that are known to need it if at -least one of the languages supported by the :command:`project` command -is enabled. - -If the :prop_gbl:`FIND_LIBRARY_USE_LIB64_PATHS` global property is set -all search paths will be tested as normal, with ``64/`` appended, and -with all matches of ``lib/`` replaced with ``lib64/``. This property is -automatically set for the platforms that are known to need it if at -least one of the languages supported by the :command:`project` command -is enabled.
diff --git a/share/cmake-3.18/Help/command/find_package.rst b/share/cmake-3.18/Help/command/find_package.rst deleted file mode 100644 index 857de78..0000000 --- a/share/cmake-3.18/Help/command/find_package.rst +++ /dev/null
@@ -1,426 +0,0 @@ -find_package ------------- - -.. only:: html - - .. contents:: - -Find an external project, and load its settings. - -.. _`basic signature`: - -Basic Signature and Module Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - find_package(<PackageName> [version] [EXACT] [QUIET] [MODULE] - [REQUIRED] [[COMPONENTS] [components...]] - [OPTIONAL_COMPONENTS components...] - [NO_POLICY_SCOPE]) - -Finds and loads settings from an external project. ``<PackageName>_FOUND`` -will be set to indicate whether the package was found. When the -package is found package-specific information is provided through -variables and :ref:`Imported Targets` documented by the package itself. The -``QUIET`` option disables informational messages, including those indicating -that the package cannot be found if it is not ``REQUIRED``. The ``REQUIRED`` -option stops processing with an error message if the package cannot be found. - -A package-specific list of required components may be listed after the -``COMPONENTS`` option (or after the ``REQUIRED`` option if present). -Additional optional components may be listed after -``OPTIONAL_COMPONENTS``. Available components and their influence on -whether a package is considered to be found are defined by the target -package. - -The ``[version]`` argument requests a version with which the package found -should be compatible (format is ``major[.minor[.patch[.tweak]]]``). The -``EXACT`` option requests that the version be matched exactly. If no -``[version]`` and/or component list is given to a recursive invocation -inside a find-module, the corresponding arguments are forwarded -automatically from the outer call (including the ``EXACT`` flag for -``[version]``). Version support is currently provided only on a -package-by-package basis (see the `Version Selection`_ section below). - -See the :command:`cmake_policy` command documentation for discussion -of the ``NO_POLICY_SCOPE`` option. - -The command has two modes by which it searches for packages: "Module" -mode and "Config" mode. The above signature selects Module mode. -If no module is found the command falls back to Config mode, described -below. This fall back is disabled if the ``MODULE`` option is given. - -In Module mode, CMake searches for a file called ``Find<PackageName>.cmake``. -The file is first searched in the :variable:`CMAKE_MODULE_PATH`, -then among the :ref:`Find Modules` provided by the CMake installation. -If the file is found, it is read and processed by CMake. It is responsible -for finding the package, checking the version, and producing any needed -messages. Some find-modules provide limited or no support for versioning; -check the module documentation. - -If the ``MODULE`` option is not specified in the above signature, -CMake first searches for the package using Module mode. Then, if the -package is not found, it searches again using Config mode. A user -may set the variable :variable:`CMAKE_FIND_PACKAGE_PREFER_CONFIG` to -``TRUE`` to direct CMake first search using Config mode before falling -back to Module mode. - -Full Signature and Config Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -User code should generally look for packages using the above `basic -signature`_. The remainder of this command documentation specifies the -full command signature and details of the search process. Project -maintainers wishing to provide a package to be found by this command -are encouraged to read on. - -The complete Config mode command signature is - -.. code-block:: cmake - - find_package(<PackageName> [version] [EXACT] [QUIET] - [REQUIRED] [[COMPONENTS] [components...]] - [OPTIONAL_COMPONENTS components...] - [CONFIG|NO_MODULE] - [NO_POLICY_SCOPE] - [NAMES name1 [name2 ...]] - [CONFIGS config1 [config2 ...]] - [HINTS path1 [path2 ... ]] - [PATHS path1 [path2 ... ]] - [PATH_SUFFIXES suffix1 [suffix2 ...]] - [NO_DEFAULT_PATH] - [NO_PACKAGE_ROOT_PATH] - [NO_CMAKE_PATH] - [NO_CMAKE_ENVIRONMENT_PATH] - [NO_SYSTEM_ENVIRONMENT_PATH] - [NO_CMAKE_PACKAGE_REGISTRY] - [NO_CMAKE_BUILDS_PATH] # Deprecated; does nothing. - [NO_CMAKE_SYSTEM_PATH] - [NO_CMAKE_SYSTEM_PACKAGE_REGISTRY] - [CMAKE_FIND_ROOT_PATH_BOTH | - ONLY_CMAKE_FIND_ROOT_PATH | - NO_CMAKE_FIND_ROOT_PATH]) - -The ``CONFIG`` option, the synonymous ``NO_MODULE`` option, or the use -of options not specified in the `basic signature`_ all enforce pure Config -mode. In pure Config mode, the command skips Module mode search and -proceeds at once with Config mode search. - -Config mode search attempts to locate a configuration file provided by the -package to be found. A cache entry called ``<PackageName>_DIR`` is created to -hold the directory containing the file. By default the command -searches for a package with the name ``<PackageName>``. If the ``NAMES`` option -is given the names following it are used instead of ``<PackageName>``. -The command searches for a file called ``<PackageName>Config.cmake`` or -``<lower-case-package-name>-config.cmake`` for each name specified. -A replacement set of possible configuration file names may be given -using the ``CONFIGS`` option. The search procedure is specified below. -Once found, the configuration file is read and processed by CMake. -Since the file is provided by the package it already knows the -location of package contents. The full path to the configuration file -is stored in the cmake variable ``<PackageName>_CONFIG``. - -All configuration files which have been considered by CMake while -searching for an installation of the package with an appropriate -version are stored in the cmake variable ``<PackageName>_CONSIDERED_CONFIGS``, -the associated versions in ``<PackageName>_CONSIDERED_VERSIONS``. - -If the package configuration file cannot be found CMake will generate -an error describing the problem unless the ``QUIET`` argument is -specified. If ``REQUIRED`` is specified and the package is not found a -fatal error is generated and the configure step stops executing. If -``<PackageName>_DIR`` has been set to a directory not containing a -configuration file CMake will ignore it and search from scratch. - -Package maintainers providing CMake package configuration files are -encouraged to name and install them such that the `Search Procedure`_ -outlined below will find them without requiring use of additional options. - -Version Selection -^^^^^^^^^^^^^^^^^ - -When the ``[version]`` argument is given Config mode will only find a -version of the package that claims compatibility with the requested -version (format is ``major[.minor[.patch[.tweak]]]``). If the ``EXACT`` -option is given only a version of the package claiming an exact match -of the requested version may be found. CMake does not establish any -convention for the meaning of version numbers. Package version -numbers are checked by "version" files provided by the packages -themselves. For a candidate package configuration file -``<config-file>.cmake`` the corresponding version file is located next -to it and named either ``<config-file>-version.cmake`` or -``<config-file>Version.cmake``. If no such version file is available -then the configuration file is assumed to not be compatible with any -requested version. A basic version file containing generic version -matching code can be created using the -:module:`CMakePackageConfigHelpers` module. When a version file -is found it is loaded to check the requested version number. The -version file is loaded in a nested scope in which the following -variables have been defined: - -``PACKAGE_FIND_NAME`` - the ``<PackageName>`` -``PACKAGE_FIND_VERSION`` - full requested version string -``PACKAGE_FIND_VERSION_MAJOR`` - major version if requested, else 0 -``PACKAGE_FIND_VERSION_MINOR`` - minor version if requested, else 0 -``PACKAGE_FIND_VERSION_PATCH`` - patch version if requested, else 0 -``PACKAGE_FIND_VERSION_TWEAK`` - tweak version if requested, else 0 -``PACKAGE_FIND_VERSION_COUNT`` - number of version components, 0 to 4 - -The version file checks whether it satisfies the requested version and -sets these variables: - -``PACKAGE_VERSION`` - full provided version string -``PACKAGE_VERSION_EXACT`` - true if version is exact match -``PACKAGE_VERSION_COMPATIBLE`` - true if version is compatible -``PACKAGE_VERSION_UNSUITABLE`` - true if unsuitable as any version - -These variables are checked by the ``find_package`` command to determine -whether the configuration file provides an acceptable version. They -are not available after the ``find_package`` call returns. If the version -is acceptable the following variables are set: - -``<PackageName>_VERSION`` - full provided version string -``<PackageName>_VERSION_MAJOR`` - major version if provided, else 0 -``<PackageName>_VERSION_MINOR`` - minor version if provided, else 0 -``<PackageName>_VERSION_PATCH`` - patch version if provided, else 0 -``<PackageName>_VERSION_TWEAK`` - tweak version if provided, else 0 -``<PackageName>_VERSION_COUNT`` - number of version components, 0 to 4 - -and the corresponding package configuration file is loaded. -When multiple package configuration files are available whose version files -claim compatibility with the version requested it is unspecified which -one is chosen: unless the variable :variable:`CMAKE_FIND_PACKAGE_SORT_ORDER` -is set no attempt is made to choose a highest or closest version number. - -To control the order in which ``find_package`` checks for compatibility use -the two variables :variable:`CMAKE_FIND_PACKAGE_SORT_ORDER` and -:variable:`CMAKE_FIND_PACKAGE_SORT_DIRECTION`. -For instance in order to select the highest version one can set - -.. code-block:: cmake - - SET(CMAKE_FIND_PACKAGE_SORT_ORDER NATURAL) - SET(CMAKE_FIND_PACKAGE_SORT_DIRECTION DEC) - -before calling ``find_package``. - -Search Procedure -^^^^^^^^^^^^^^^^ - -CMake constructs a set of possible installation prefixes for the -package. Under each prefix several directories are searched for a -configuration file. The tables below show the directories searched. -Each entry is meant for installation trees following Windows (``W``), UNIX -(``U``), or Apple (``A``) conventions:: - - <prefix>/ (W) - <prefix>/(cmake|CMake)/ (W) - <prefix>/<name>*/ (W) - <prefix>/<name>*/(cmake|CMake)/ (W) - <prefix>/(lib/<arch>|lib*|share)/cmake/<name>*/ (U) - <prefix>/(lib/<arch>|lib*|share)/<name>*/ (U) - <prefix>/(lib/<arch>|lib*|share)/<name>*/(cmake|CMake)/ (U) - <prefix>/<name>*/(lib/<arch>|lib*|share)/cmake/<name>*/ (W/U) - <prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/ (W/U) - <prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/(cmake|CMake)/ (W/U) - -On systems supporting macOS :prop_tgt:`FRAMEWORK` and :prop_tgt:`BUNDLE`, the -following directories are searched for Frameworks or Application Bundles -containing a configuration file:: - - <prefix>/<name>.framework/Resources/ (A) - <prefix>/<name>.framework/Resources/CMake/ (A) - <prefix>/<name>.framework/Versions/*/Resources/ (A) - <prefix>/<name>.framework/Versions/*/Resources/CMake/ (A) - <prefix>/<name>.app/Contents/Resources/ (A) - <prefix>/<name>.app/Contents/Resources/CMake/ (A) - -In all cases the ``<name>`` is treated as case-insensitive and corresponds -to any of the names specified (``<PackageName>`` or names given by ``NAMES``). - -Paths with ``lib/<arch>`` are enabled if the -:variable:`CMAKE_LIBRARY_ARCHITECTURE` variable is set. ``lib*`` includes one -or more of the values ``lib64``, ``lib32``, ``libx32`` or ``lib`` (searched in -that order). - -* Paths with ``lib64`` are searched on 64 bit platforms if the - :prop_gbl:`FIND_LIBRARY_USE_LIB64_PATHS` property is set to ``TRUE``. -* Paths with ``lib32`` are searched on 32 bit platforms if the - :prop_gbl:`FIND_LIBRARY_USE_LIB32_PATHS` property is set to ``TRUE``. -* Paths with ``libx32`` are searched on platforms using the x32 ABI - if the :prop_gbl:`FIND_LIBRARY_USE_LIBX32_PATHS` property is set to ``TRUE``. -* The ``lib`` path is always searched. - -If ``PATH_SUFFIXES`` is specified, the suffixes are appended to each -(``W``) or (``U``) directory entry one-by-one. - -This set of directories is intended to work in cooperation with -projects that provide configuration files in their installation trees. -Directories above marked with (``W``) are intended for installations on -Windows where the prefix may point at the top of an application's -installation directory. Those marked with (``U``) are intended for -installations on UNIX platforms where the prefix is shared by multiple -packages. This is merely a convention, so all (``W``) and (``U``) directories -are still searched on all platforms. Directories marked with (``A``) are -intended for installations on Apple platforms. The -:variable:`CMAKE_FIND_FRAMEWORK` and :variable:`CMAKE_FIND_APPBUNDLE` -variables determine the order of preference. - -The set of installation prefixes is constructed using the following -steps. If ``NO_DEFAULT_PATH`` is specified all ``NO_*`` options are -enabled. - -1. Search paths specified in the :variable:`<PackageName>_ROOT` CMake - variable and the :envvar:`<PackageName>_ROOT` environment variable, - where ``<PackageName>`` is the package to be found. - The package root variables are maintained as a stack so if - called from within a find module, root paths from the parent's find - module will also be searched after paths for the current package. - This can be skipped if ``NO_PACKAGE_ROOT_PATH`` is passed or by setting - the :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` to ``FALSE``. - See policy :policy:`CMP0074`. - -2. Search paths specified in cmake-specific cache variables. These - are intended to be used on the command line with a ``-DVAR=value``. - The values are interpreted as :ref:`semicolon-separated lists <CMake Language Lists>`. - This can be skipped if ``NO_CMAKE_PATH`` is passed or by setting the - :variable:`CMAKE_FIND_USE_CMAKE_PATH` to ``FALSE``: - - * :variable:`CMAKE_PREFIX_PATH` - * :variable:`CMAKE_FRAMEWORK_PATH` - * :variable:`CMAKE_APPBUNDLE_PATH` - -3. Search paths specified in cmake-specific environment variables. - These are intended to be set in the user's shell configuration, - and therefore use the host's native path separator - (``;`` on Windows and ``:`` on UNIX). - This can be skipped if ``NO_CMAKE_ENVIRONMENT_PATH`` is passed or by setting - the :variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH` to ``FALSE``: - - * ``<PackageName>_DIR`` - * :envvar:`CMAKE_PREFIX_PATH` - * ``CMAKE_FRAMEWORK_PATH`` - * ``CMAKE_APPBUNDLE_PATH`` - -4. Search paths specified by the ``HINTS`` option. These should be paths - computed by system introspection, such as a hint provided by the - location of another item already found. Hard-coded guesses should - be specified with the ``PATHS`` option. - -5. Search the standard system environment variables. This can be - skipped if ``NO_SYSTEM_ENVIRONMENT_PATH`` is passed or by setting the - :variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH` to ``FALSE``. Path entries - ending in ``/bin`` or ``/sbin`` are automatically converted to their - parent directories: - - * ``PATH`` - -6. Search paths stored in the CMake :ref:`User Package Registry`. - This can be skipped if ``NO_CMAKE_PACKAGE_REGISTRY`` is passed or by - setting the variable :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` - to ``FALSE`` or the deprecated variable - :variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` to ``TRUE``. - - See the :manual:`cmake-packages(7)` manual for details on the user - package registry. - -7. Search cmake variables defined in the Platform files for the - current system. This can be skipped if ``NO_CMAKE_SYSTEM_PATH`` is - passed or by setting the :variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH` - to ``FALSE``: - - * :variable:`CMAKE_SYSTEM_PREFIX_PATH` - * :variable:`CMAKE_SYSTEM_FRAMEWORK_PATH` - * :variable:`CMAKE_SYSTEM_APPBUNDLE_PATH` - - The platform paths that these variables contain are locations that - typically include installed software. An example being ``/usr/local`` for - UNIX based platforms. - -8. Search paths stored in the CMake :ref:`System Package Registry`. - This can be skipped if ``NO_CMAKE_SYSTEM_PACKAGE_REGISTRY`` is passed - or by setting the :variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` - variable to ``FALSE`` or the deprecated variable - :variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` to ``TRUE``. - - See the :manual:`cmake-packages(7)` manual for details on the system - package registry. - -9. Search paths specified by the ``PATHS`` option. These are typically - hard-coded guesses. - -.. |FIND_XXX| replace:: find_package -.. |FIND_ARGS_XXX| replace:: <PackageName> -.. |CMAKE_FIND_ROOT_PATH_MODE_XXX| replace:: - :variable:`CMAKE_FIND_ROOT_PATH_MODE_PACKAGE` - -.. include:: FIND_XXX_ROOT.txt -.. include:: FIND_XXX_ORDER.txt - -By default the value stored in the result variable will be the path at -which the file is found. The :variable:`CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS` -variable may be set to ``TRUE`` before calling ``find_package`` in order -to resolve symbolic links and store the real path to the file. - -Every non-REQUIRED ``find_package`` call can be disabled by setting the -:variable:`CMAKE_DISABLE_FIND_PACKAGE_<PackageName>` variable to ``TRUE``. - -Package File Interface Variables -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -When loading a find module or package configuration file ``find_package`` -defines variables to provide information about the call arguments (and -restores their original state before returning): - -``CMAKE_FIND_PACKAGE_NAME`` - the ``<PackageName>`` which is searched for -``<PackageName>_FIND_REQUIRED`` - true if ``REQUIRED`` option was given -``<PackageName>_FIND_QUIETLY`` - true if ``QUIET`` option was given -``<PackageName>_FIND_VERSION`` - full requested version string -``<PackageName>_FIND_VERSION_MAJOR`` - major version if requested, else 0 -``<PackageName>_FIND_VERSION_MINOR`` - minor version if requested, else 0 -``<PackageName>_FIND_VERSION_PATCH`` - patch version if requested, else 0 -``<PackageName>_FIND_VERSION_TWEAK`` - tweak version if requested, else 0 -``<PackageName>_FIND_VERSION_COUNT`` - number of version components, 0 to 4 -``<PackageName>_FIND_VERSION_EXACT`` - true if ``EXACT`` option was given -``<PackageName>_FIND_COMPONENTS`` - list of requested components -``<PackageName>_FIND_REQUIRED_<c>`` - true if component ``<c>`` is required, - false if component ``<c>`` is optional - -In Module mode the loaded find module is responsible to honor the -request detailed by these variables; see the find module for details. -In Config mode ``find_package`` handles ``REQUIRED``, ``QUIET``, and -``[version]`` options automatically but leaves it to the package -configuration file to handle components in a way that makes sense -for the package. The package configuration file may set -``<PackageName>_FOUND`` to false to tell ``find_package`` that component -requirements are not satisfied.
diff --git a/share/cmake-3.18/Help/command/find_path.rst b/share/cmake-3.18/Help/command/find_path.rst deleted file mode 100644 index 52ffe3c..0000000 --- a/share/cmake-3.18/Help/command/find_path.rst +++ /dev/null
@@ -1,41 +0,0 @@ -find_path ---------- - -.. |FIND_XXX| replace:: find_path -.. |NAMES| replace:: NAMES name1 [name2 ...] -.. |SEARCH_XXX| replace:: file in a directory -.. |SEARCH_XXX_DESC| replace:: directory containing the named file -.. |prefix_XXX_SUBDIR| replace:: ``<prefix>/include`` -.. |entry_XXX_SUBDIR| replace:: ``<entry>/include`` - -.. |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |FIND_PACKAGE_ROOT_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |CMAKE_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_XXX_PATH| replace:: :variable:`CMAKE_INCLUDE_PATH` -.. |CMAKE_XXX_MAC_PATH| replace:: :variable:`CMAKE_FRAMEWORK_PATH` - -.. |SYSTEM_ENVIRONMENT_PATH_XXX| replace:: The directories in ``PATH`` and ``INCLUDE``. -.. |SYSTEM_ENVIRONMENT_PATH_WINDOWS_XXX| replace:: On Windows hosts: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |SYSTEM_ENVIRONMENT_PREFIX_PATH_XXX_SUBDIR|. - -.. |CMAKE_SYSTEM_PREFIX_PATH_XXX| replace:: - ``<prefix>/include/<arch>`` if :variable:`CMAKE_LIBRARY_ARCHITECTURE` - is set, and |CMAKE_SYSTEM_PREFIX_PATH_XXX_SUBDIR| -.. |CMAKE_SYSTEM_XXX_PATH| replace:: - :variable:`CMAKE_SYSTEM_INCLUDE_PATH` -.. |CMAKE_SYSTEM_XXX_MAC_PATH| replace:: - :variable:`CMAKE_SYSTEM_FRAMEWORK_PATH` - -.. |CMAKE_FIND_ROOT_PATH_MODE_XXX| replace:: - :variable:`CMAKE_FIND_ROOT_PATH_MODE_INCLUDE` - -.. include:: FIND_XXX.txt - -When searching for frameworks, if the file is specified as ``A/b.h``, then -the framework search will look for ``A.framework/Headers/b.h``. If that -is found the path will be set to the path to the framework. CMake -will convert this to the correct ``-F`` option to include the file.
diff --git a/share/cmake-3.18/Help/command/foreach.rst b/share/cmake-3.18/Help/command/foreach.rst deleted file mode 100644 index a01a104..0000000 --- a/share/cmake-3.18/Help/command/foreach.rst +++ /dev/null
@@ -1,127 +0,0 @@ -foreach -------- - -Evaluate a group of commands for each value in a list. - -.. code-block:: cmake - - foreach(<loop_var> <items>) - <commands> - endforeach() - -where ``<items>`` is a list of items that are separated by -semicolon or whitespace. -All commands between ``foreach`` and the matching ``endforeach`` are recorded -without being invoked. Once the ``endforeach`` is evaluated, the recorded -list of commands is invoked once for each item in ``<items>``. -At the beginning of each iteration the variable ``loop_var`` will be set -to the value of the current item. - -The commands :command:`break` and :command:`continue` provide means to -escape from the normal control flow. - -Per legacy, the :command:`endforeach` command admits -an optional ``<loop_var>`` argument. -If used, it must be a verbatim -repeat of the argument of the opening -``foreach`` command. - -.. code-block:: cmake - - foreach(<loop_var> RANGE <stop>) - -In this variant, ``foreach`` iterates over the numbers -0, 1, ... up to (and including) the nonnegative integer ``<stop>``. - -.. code-block:: cmake - - foreach(<loop_var> RANGE <start> <stop> [<step>]) - -In this variant, ``foreach`` iterates over the numbers from -``<start>`` up to at most ``<stop>`` in steps of ``<step>``. -If ``<step>`` is not specified, then the step size is 1. -The three arguments ``<start>`` ``<stop>`` ``<step>`` must -all be nonnegative integers, and ``<stop>`` must not be -smaller than ``<start>``; otherwise you enter the danger zone -of undocumented behavior that may change in future releases. - -.. code-block:: cmake - - foreach(<loop_var> IN [LISTS [<lists>]] [ITEMS [<items>]]) - -In this variant, ``<lists>`` is a whitespace or semicolon -separated list of list-valued variables. The ``foreach`` -command iterates over each item in each given list. -The ``<items>`` following the ``ITEMS`` keyword are processed -as in the first variant of the ``foreach`` command. -The forms ``LISTS A`` and ``ITEMS ${A}`` are -equivalent. - -The following example shows how the ``LISTS`` option is -processed: - -.. code-block:: cmake - - set(A 0;1) - set(B 2 3) - set(C "4 5") - set(D 6;7 8) - set(E "") - foreach(X IN LISTS A B C D E) - message(STATUS "X=${X}") - endforeach() - -yields -:: - - -- X=0 - -- X=1 - -- X=2 - -- X=3 - -- X=4 5 - -- X=6 - -- X=7 - -- X=8 - - -.. code-block:: cmake - - foreach(<loop_var>... IN ZIP_LISTS <lists>) - -In this variant, ``<lists>`` is a whitespace or semicolon -separated list of list-valued variables. The ``foreach`` -command iterates over each list simultaneously setting the -iteration variables as follows: - -- if the only ``loop_var`` given, then it sets a series of - ``loop_var_N`` variables to the current item from the - corresponding list; -- if multiple variable names passed, their count should match - the lists variables count; -- if any of the lists are shorter, the corresponding iteration - variable is not defined for the current iteration. - -.. code-block:: cmake - - list(APPEND English one two three four) - list(APPEND Bahasa satu dua tiga) - - foreach(num IN ZIP_LISTS English Bahasa) - message(STATUS "num_0=${num_0}, num_1=${num_1}") - endforeach() - - foreach(en ba IN ZIP_LISTS English Bahasa) - message(STATUS "en=${en}, ba=${ba}") - endforeach() - -yields -:: - - -- num_0=one, num_1=satu - -- num_0=two, num_1=dua - -- num_0=three, num_1=tiga - -- num_0=four, num_1= - -- en=one, ba=satu - -- en=two, ba=dua - -- en=three, ba=tiga - -- en=four, ba=
diff --git a/share/cmake-3.18/Help/command/function.rst b/share/cmake-3.18/Help/command/function.rst deleted file mode 100644 index 7a9b907..0000000 --- a/share/cmake-3.18/Help/command/function.rst +++ /dev/null
@@ -1,74 +0,0 @@ -function --------- - -Start recording a function for later invocation as a command. - -.. code-block:: cmake - - function(<name> [<arg1> ...]) - <commands> - endfunction() - -Defines a function named ``<name>`` that takes arguments named -``<arg1>``, ... The ``<commands>`` in the function definition -are recorded; they are not executed until the function is invoked. - -Per legacy, the :command:`endfunction` command admits an optional -``<name>`` argument. If used, it must be a verbatim repeat of the -argument of the opening ``function`` command. - -A function opens a new scope: see :command:`set(var PARENT_SCOPE)` for -details. - -See the :command:`cmake_policy()` command documentation for the behavior -of policies inside functions. - -See the :command:`macro()` command documentation for differences -between CMake functions and macros. - -Invocation -^^^^^^^^^^ - -The function invocation is case-insensitive. A function defined as - -.. code-block:: cmake - - function(foo) - <commands> - endfunction() - -can be invoked through any of - -.. code-block:: cmake - - foo() - Foo() - FOO() - cmake_language(CALL foo) - -and so on. However, it is strongly recommended to stay with the -case chosen in the function definition. Typically functions use -all-lowercase names. - -The :command:`cmake_language(CALL ...)` command can also be used to -invoke the function. - -Arguments -^^^^^^^^^ - -When the function is invoked, the recorded ``<commands>`` are first -modified by replacing formal parameters (``${arg1}``, ...) with the -arguments passed, and then invoked as normal commands. - -In addition to referencing the formal parameters you can reference the -``ARGC`` variable which will be set to the number of arguments passed -into the function as well as ``ARGV0``, ``ARGV1``, ``ARGV2``, ... which -will have the actual values of the arguments passed in. This facilitates -creating functions with optional arguments. - -Furthermore, ``ARGV`` holds the list of all arguments given to the -function and ``ARGN`` holds the list of arguments past the last expected -argument. Referencing to ``ARGV#`` arguments beyond ``ARGC`` have -undefined behavior. Checking that ``ARGC`` is greater than ``#`` is -the only way to ensure that ``ARGV#`` was passed to the function as an -extra argument.
diff --git a/share/cmake-3.18/Help/command/get_directory_property.rst b/share/cmake-3.18/Help/command/get_directory_property.rst deleted file mode 100644 index 218efa9..0000000 --- a/share/cmake-3.18/Help/command/get_directory_property.rst +++ /dev/null
@@ -1,29 +0,0 @@ -get_directory_property ----------------------- - -Get a property of ``DIRECTORY`` scope. - -.. code-block:: cmake - - get_directory_property(<variable> [DIRECTORY <dir>] <prop-name>) - -Stores a property of directory scope in the named ``<variable>``. -The ``DIRECTORY`` argument specifies another directory from which -to retrieve the property value instead of the current directory. -The specified directory must have already been traversed by CMake. - -If the property is not defined for the nominated directory scope, -an empty string is returned. In the case of ``INHERITED`` properties, -if the property is not found for the nominated directory scope, -the search will chain to a parent scope as described for the -:command:`define_property` command. - -.. code-block:: cmake - - get_directory_property(<variable> [DIRECTORY <dir>] - DEFINITION <var-name>) - -Get a variable definition from a directory. This form is useful to -get a variable definition from another directory. - -See also the more general :command:`get_property` command.
diff --git a/share/cmake-3.18/Help/command/get_filename_component.rst b/share/cmake-3.18/Help/command/get_filename_component.rst deleted file mode 100644 index 9bbf877..0000000 --- a/share/cmake-3.18/Help/command/get_filename_component.rst +++ /dev/null
@@ -1,55 +0,0 @@ -get_filename_component ----------------------- - -Get a specific component of a full filename. - -.. code-block:: cmake - - get_filename_component(<var> <FileName> <mode> [CACHE]) - -Sets ``<var>`` to a component of ``<FileName>``, where ``<mode>`` is one of: - -:: - - DIRECTORY = Directory without file name - NAME = File name without directory - EXT = File name longest extension (.b.c from d/a.b.c) - NAME_WE = File name without directory or longest extension - LAST_EXT = File name last extension (.c from d/a.b.c) - NAME_WLE = File name without directory or last extension - PATH = Legacy alias for DIRECTORY (use for CMake <= 2.8.11) - -Paths are returned with forward slashes and have no trailing slashes. -If the optional ``CACHE`` argument is specified, the result variable is -added to the cache. - -.. code-block:: cmake - - get_filename_component(<var> <FileName> <mode> [BASE_DIR <dir>] [CACHE]) - -Sets ``<var>`` to the absolute path of ``<FileName>``, where ``<mode>`` is one -of: - -:: - - ABSOLUTE = Full path to file - REALPATH = Full path to existing file with symlinks resolved - -If the provided ``<FileName>`` is a relative path, it is evaluated relative -to the given base directory ``<dir>``. If no base directory is -provided, the default base directory will be -:variable:`CMAKE_CURRENT_SOURCE_DIR`. - -Paths are returned with forward slashes and have no trailing slashes. If the -optional ``CACHE`` argument is specified, the result variable is added to the -cache. - -.. code-block:: cmake - - get_filename_component(<var> <FileName> PROGRAM [PROGRAM_ARGS <arg_var>] [CACHE]) - -The program in ``<FileName>`` will be found in the system search path or -left as a full path. If ``PROGRAM_ARGS`` is present with ``PROGRAM``, then -any command-line arguments present in the ``<FileName>`` string are split -from the program name and stored in ``<arg_var>``. This is used to -separate a program name from its arguments in a command line string.
diff --git a/share/cmake-3.18/Help/command/get_property.rst b/share/cmake-3.18/Help/command/get_property.rst deleted file mode 100644 index 0602518..0000000 --- a/share/cmake-3.18/Help/command/get_property.rst +++ /dev/null
@@ -1,85 +0,0 @@ -get_property ------------- - -Get a property. - -.. code-block:: cmake - - get_property(<variable> - <GLOBAL | - DIRECTORY [<dir>] | - TARGET <target> | - SOURCE <source> | - [DIRECTORY <dir> | TARGET_DIRECTORY <target>] | - INSTALL <file> | - TEST <test> | - CACHE <entry> | - VARIABLE > - PROPERTY <name> - [SET | DEFINED | BRIEF_DOCS | FULL_DOCS]) - -Gets one property from one object in a scope. - -The first argument specifies the variable in which to store the result. -The second argument determines the scope from which to get the property. -It must be one of the following: - -``GLOBAL`` - Scope is unique and does not accept a name. - -``DIRECTORY`` - Scope defaults to the current directory but another - directory (already processed by CMake) may be named by the - full or relative path ``<dir>``. - See also the :command:`get_directory_property` command. - -``TARGET`` - Scope must name one existing target. - See also the :command:`get_target_property` command. - -``SOURCE`` - Scope must name one source file. By default, the source file's property - will be read from the current source directory's scope, but this can be - overridden with one of the following sub-options: - - ``DIRECTORY <dir>`` - The source file property will be read from the ``<dir>`` directory's - scope. CMake must already know about that source directory, either by - having added it through a call to :command:`add_subdirectory` or ``<dir>`` - being the top level source directory. Relative paths are treated as - relative to the current source directory. - - ``TARGET_DIRECTORY <target>`` - The source file property will be read from the directory scope in which - ``<target>`` was created (``<target>`` must therefore already exist). - - See also the :command:`get_source_file_property` command. - -``INSTALL`` - Scope must name one installed file path. - -``TEST`` - Scope must name one existing test. - See also the :command:`get_test_property` command. - -``CACHE`` - Scope must name one cache entry. - -``VARIABLE`` - Scope is unique and does not accept a name. - -The required ``PROPERTY`` option is immediately followed by the name of -the property to get. If the property is not set an empty value is -returned, although some properties support inheriting from a parent scope -if defined to behave that way (see :command:`define_property`). - -If the ``SET`` option is given the variable is set to a boolean -value indicating whether the property has been set. If the ``DEFINED`` -option is given the variable is set to a boolean value indicating -whether the property has been defined such as with the -:command:`define_property` command. - -If ``BRIEF_DOCS`` or ``FULL_DOCS`` is given then the variable is set to a -string containing documentation for the requested property. If -documentation is requested for a property that has not been defined -``NOTFOUND`` is returned.
diff --git a/share/cmake-3.18/Help/command/get_source_file_property.rst b/share/cmake-3.18/Help/command/get_source_file_property.rst deleted file mode 100644 index 76ed776..0000000 --- a/share/cmake-3.18/Help/command/get_source_file_property.rst +++ /dev/null
@@ -1,40 +0,0 @@ -get_source_file_property ------------------------- - -Get a property for a source file. - -.. code-block:: cmake - - get_source_file_property(<variable> <file> - [DIRECTORY <dir> | TARGET_DIRECTORY <target>] - <property>) - -Gets a property from a source file. The value of the property is -stored in the specified ``<variable>``. If the source property is not found, -the behavior depends on whether it has been defined to be an ``INHERITED`` -property or not (see :command:`define_property`). Non-inherited properties -will set ``variable`` to ``NOTFOUND``, whereas inherited properties will search -the relevant parent scope as described for the :command:`define_property` -command and if still unable to find the property, ``variable`` will be set to -an empty string. - -By default, the source file's property will be read from the current source -directory's scope, but this can be overridden with one of the following -sub-options: - -``DIRECTORY <dir>`` - The source file property will be read from the ``<dir>`` directory's - scope. CMake must already know about that source directory, either by - having added it through a call to :command:`add_subdirectory` or ``<dir>`` - being the top level source directory. Relative paths are treated as - relative to the current source directory. - -``TARGET_DIRECTORY <target>`` - The source file property will be read from the directory scope in which - ``<target>`` was created (``<target>`` must therefore already exist). - -Use :command:`set_source_files_properties` to set property values. Source -file properties usually control how the file is built. One property that is -always there is :prop_sf:`LOCATION`. - -See also the more general :command:`get_property` command.
diff --git a/share/cmake-3.18/Help/command/if.rst b/share/cmake-3.18/Help/command/if.rst deleted file mode 100644 index be992df..0000000 --- a/share/cmake-3.18/Help/command/if.rst +++ /dev/null
@@ -1,280 +0,0 @@ -if --- - -Conditionally execute a group of commands. - -Synopsis -^^^^^^^^ - -.. code-block:: cmake - - if(<condition>) - <commands> - elseif(<condition>) # optional block, can be repeated - <commands> - else() # optional block - <commands> - endif() - -Evaluates the ``condition`` argument of the ``if`` clause according to the -`Condition syntax`_ described below. If the result is true, then the -``commands`` in the ``if`` block are executed. -Otherwise, optional ``elseif`` blocks are processed in the same way. -Finally, if no ``condition`` is true, ``commands`` in the optional ``else`` -block are executed. - -Per legacy, the :command:`else` and :command:`endif` commands admit -an optional ``<condition>`` argument. -If used, it must be a verbatim -repeat of the argument of the opening -``if`` command. - -.. _`Condition Syntax`: - -Condition Syntax -^^^^^^^^^^^^^^^^ - -The following syntax applies to the ``condition`` argument of -the ``if``, ``elseif`` and :command:`while` clauses. - -Compound conditions are evaluated in the following order of precedence: -Innermost parentheses are evaluated first. Next come unary tests such -as ``EXISTS``, ``COMMAND``, and ``DEFINED``. Then binary tests such as -``EQUAL``, ``LESS``, ``LESS_EQUAL``, ``GREATER``, ``GREATER_EQUAL``, -``STREQUAL``, ``STRLESS``, ``STRLESS_EQUAL``, ``STRGREATER``, -``STRGREATER_EQUAL``, ``VERSION_EQUAL``, ``VERSION_LESS``, -``VERSION_LESS_EQUAL``, ``VERSION_GREATER``, ``VERSION_GREATER_EQUAL``, -and ``MATCHES``. Then the boolean operators in the order ``NOT``, ``AND``, -and finally ``OR``. - -Possible conditions are: - -``if(<constant>)`` - True if the constant is ``1``, ``ON``, ``YES``, ``TRUE``, ``Y``, - or a non-zero number. False if the constant is ``0``, ``OFF``, - ``NO``, ``FALSE``, ``N``, ``IGNORE``, ``NOTFOUND``, the empty string, - or ends in the suffix ``-NOTFOUND``. Named boolean constants are - case-insensitive. If the argument is not one of these specific - constants, it is treated as a variable or string and the following - signature is used. - -``if(<variable|string>)`` - True if given a variable that is defined to a value that is not a false - constant. False otherwise. (Note macro arguments are not variables.) - -``if(NOT <condition>)`` - True if the condition is not true. - -``if(<cond1> AND <cond2>)`` - True if both conditions would be considered true individually. - -``if(<cond1> OR <cond2>)`` - True if either condition would be considered true individually. - -``if(COMMAND command-name)`` - True if the given name is a command, macro or function that can be - invoked. - -``if(POLICY policy-id)`` - True if the given name is an existing policy (of the form ``CMP<NNNN>``). - -``if(TARGET target-name)`` - True if the given name is an existing logical target name created - by a call to the :command:`add_executable`, :command:`add_library`, - or :command:`add_custom_target` command that has already been invoked - (in any directory). - -``if(TEST test-name)`` - True if the given name is an existing test name created by the - :command:`add_test` command. - -``if(EXISTS path-to-file-or-directory)`` - True if the named file or directory exists. Behavior is well-defined - only for full paths. Resolves symbolic links, i.e. if the named file or - directory is a symbolic link, returns true if the target of the - symbolic link exists. - -``if(file1 IS_NEWER_THAN file2)`` - True if ``file1`` is newer than ``file2`` or if one of the two files doesn't - exist. Behavior is well-defined only for full paths. If the file - time stamps are exactly the same, an ``IS_NEWER_THAN`` comparison returns - true, so that any dependent build operations will occur in the event - of a tie. This includes the case of passing the same file name for - both file1 and file2. - -``if(IS_DIRECTORY path-to-directory)`` - True if the given name is a directory. Behavior is well-defined only - for full paths. - -``if(IS_SYMLINK file-name)`` - True if the given name is a symbolic link. Behavior is well-defined - only for full paths. - -``if(IS_ABSOLUTE path)`` - True if the given path is an absolute path. - -``if(<variable|string> MATCHES regex)`` - True if the given string or variable's value matches the given regular - condition. See :ref:`Regex Specification` for regex format. - ``()`` groups are captured in :variable:`CMAKE_MATCH_<n>` variables. - -``if(<variable|string> LESS <variable|string>)`` - True if the given string or variable's value is a valid number and less - than that on the right. - -``if(<variable|string> GREATER <variable|string>)`` - True if the given string or variable's value is a valid number and greater - than that on the right. - -``if(<variable|string> EQUAL <variable|string>)`` - True if the given string or variable's value is a valid number and equal - to that on the right. - -``if(<variable|string> LESS_EQUAL <variable|string>)`` - True if the given string or variable's value is a valid number and less - than or equal to that on the right. - -``if(<variable|string> GREATER_EQUAL <variable|string>)`` - True if the given string or variable's value is a valid number and greater - than or equal to that on the right. - -``if(<variable|string> STRLESS <variable|string>)`` - True if the given string or variable's value is lexicographically less - than the string or variable on the right. - -``if(<variable|string> STRGREATER <variable|string>)`` - True if the given string or variable's value is lexicographically greater - than the string or variable on the right. - -``if(<variable|string> STREQUAL <variable|string>)`` - True if the given string or variable's value is lexicographically equal - to the string or variable on the right. - -``if(<variable|string> STRLESS_EQUAL <variable|string>)`` - True if the given string or variable's value is lexicographically less - than or equal to the string or variable on the right. - -``if(<variable|string> STRGREATER_EQUAL <variable|string>)`` - True if the given string or variable's value is lexicographically greater - than or equal to the string or variable on the right. - -``if(<variable|string> VERSION_LESS <variable|string>)`` - Component-wise integer version number comparison (version format is - ``major[.minor[.patch[.tweak]]]``, omitted components are treated as zero). - Any non-integer version component or non-integer trailing part of a version - component effectively truncates the string at that point. - -``if(<variable|string> VERSION_GREATER <variable|string>)`` - Component-wise integer version number comparison (version format is - ``major[.minor[.patch[.tweak]]]``, omitted components are treated as zero). - Any non-integer version component or non-integer trailing part of a version - component effectively truncates the string at that point. - -``if(<variable|string> VERSION_EQUAL <variable|string>)`` - Component-wise integer version number comparison (version format is - ``major[.minor[.patch[.tweak]]]``, omitted components are treated as zero). - Any non-integer version component or non-integer trailing part of a version - component effectively truncates the string at that point. - -``if(<variable|string> VERSION_LESS_EQUAL <variable|string>)`` - Component-wise integer version number comparison (version format is - ``major[.minor[.patch[.tweak]]]``, omitted components are treated as zero). - Any non-integer version component or non-integer trailing part of a version - component effectively truncates the string at that point. - -``if(<variable|string> VERSION_GREATER_EQUAL <variable|string>)`` - Component-wise integer version number comparison (version format is - ``major[.minor[.patch[.tweak]]]``, omitted components are treated as zero). - Any non-integer version component or non-integer trailing part of a version - component effectively truncates the string at that point. - -``if(<variable|string> IN_LIST <variable>)`` - True if the given element is contained in the named list variable. - -``if(DEFINED <name>|CACHE{<name>}|ENV{<name>})`` - True if a variable, cache variable or environment variable - with given ``<name>`` is defined. The value of the variable - does not matter. Note that macro arguments are not variables. - -``if((condition) AND (condition OR (condition)))`` - The conditions inside the parenthesis are evaluated first and then - the remaining condition is evaluated as in the previous examples. - Where there are nested parenthesis the innermost are evaluated as part - of evaluating the condition that contains them. - -Variable Expansion -^^^^^^^^^^^^^^^^^^ - -The if command was written very early in CMake's history, predating -the ``${}`` variable evaluation syntax, and for convenience evaluates -variables named by its arguments as shown in the above signatures. -Note that normal variable evaluation with ``${}`` applies before the if -command even receives the arguments. Therefore code like - -.. code-block:: cmake - - set(var1 OFF) - set(var2 "var1") - if(${var2}) - -appears to the if command as - -.. code-block:: cmake - - if(var1) - -and is evaluated according to the ``if(<variable>)`` case documented -above. The result is ``OFF`` which is false. However, if we remove the -``${}`` from the example then the command sees - -.. code-block:: cmake - - if(var2) - -which is true because ``var2`` is defined to ``var1`` which is not a false -constant. - -Automatic evaluation applies in the other cases whenever the -above-documented condition syntax accepts ``<variable|string>``: - -* The left hand argument to ``MATCHES`` is first checked to see if it is - a defined variable, if so the variable's value is used, otherwise the - original value is used. - -* If the left hand argument to ``MATCHES`` is missing it returns false - without error - -* Both left and right hand arguments to ``LESS``, ``GREATER``, ``EQUAL``, - ``LESS_EQUAL``, and ``GREATER_EQUAL``, are independently tested to see if - they are defined variables, if so their defined values are used otherwise - the original value is used. - -* Both left and right hand arguments to ``STRLESS``, ``STRGREATER``, - ``STREQUAL``, ``STRLESS_EQUAL``, and ``STRGREATER_EQUAL`` are independently - tested to see if they are defined variables, if so their defined values are - used otherwise the original value is used. - -* Both left and right hand arguments to ``VERSION_LESS``, - ``VERSION_GREATER``, ``VERSION_EQUAL``, ``VERSION_LESS_EQUAL``, and - ``VERSION_GREATER_EQUAL`` are independently tested to see if they are defined - variables, if so their defined values are used otherwise the original value - is used. - -* The right hand argument to ``NOT`` is tested to see if it is a boolean - constant, if so the value is used, otherwise it is assumed to be a - variable and it is dereferenced. - -* The left and right hand arguments to ``AND`` and ``OR`` are independently - tested to see if they are boolean constants, if so they are used as - such, otherwise they are assumed to be variables and are dereferenced. - -To prevent ambiguity, potential variable or keyword names can be -specified in a :ref:`Quoted Argument` or a :ref:`Bracket Argument`. -A quoted or bracketed variable or keyword will be interpreted as a -string and not dereferenced or interpreted. -See policy :policy:`CMP0054`. - -There is no automatic evaluation for environment or cache -:ref:`Variable References`. Their values must be referenced as -``$ENV{<name>}`` or ``$CACHE{<name>}`` wherever the above-documented -condition syntax accepts ``<variable|string>``.
diff --git a/share/cmake-3.18/Help/command/include_external_msproject.rst b/share/cmake-3.18/Help/command/include_external_msproject.rst deleted file mode 100644 index 540a13a..0000000 --- a/share/cmake-3.18/Help/command/include_external_msproject.rst +++ /dev/null
@@ -1,26 +0,0 @@ -include_external_msproject --------------------------- - -Include an external Microsoft project file in a workspace. - -.. code-block:: cmake - - include_external_msproject(projectname location - [TYPE projectTypeGUID] - [GUID projectGUID] - [PLATFORM platformName] - dep1 dep2 ...) - -Includes an external Microsoft project in the generated workspace -file. Currently does nothing on UNIX. This will create a target -named ``[projectname]``. This can be used in the :command:`add_dependencies` -command to make things depend on the external project. - -``TYPE``, ``GUID`` and ``PLATFORM`` are optional parameters that allow one to -specify the type of project, id (``GUID``) of the project and the name of -the target platform. This is useful for projects requiring values -other than the default (e.g. WIX projects). - -If the imported project has different configuration names than the -current project, set the :prop_tgt:`MAP_IMPORTED_CONFIG_<CONFIG>` -target property to specify the mapping.
diff --git a/share/cmake-3.18/Help/command/include_guard.rst b/share/cmake-3.18/Help/command/include_guard.rst deleted file mode 100644 index 877aa86..0000000 --- a/share/cmake-3.18/Help/command/include_guard.rst +++ /dev/null
@@ -1,46 +0,0 @@ -include_guard -------------- - -Provides an include guard for the file currently being processed by CMake. - -.. code-block:: cmake - - include_guard([DIRECTORY|GLOBAL]) - -Sets up an include guard for the current CMake file (see the -:variable:`CMAKE_CURRENT_LIST_FILE` variable documentation). - -CMake will end its processing of the current file at the location of the -:command:`include_guard` command if the current file has already been -processed for the applicable scope (see below). This provides functionality -similar to the include guards commonly used in source headers or to the -``#pragma once`` directive. If the current file has been processed previously -for the applicable scope, the effect is as though :command:`return` had been -called. Do not call this command from inside a function being defined within -the current file. - -An optional argument specifying the scope of the guard may be provided. -Possible values for the option are: - -``DIRECTORY`` - The include guard applies within the current directory and below. The file - will only be included once within this directory scope, but may be included - again by other files outside of this directory (i.e. a parent directory or - another directory not pulled in by :command:`add_subdirectory` or - :command:`include` from the current file or its children). - -``GLOBAL`` - The include guard applies globally to the whole build. The current file - will only be included once regardless of the scope. - -If no arguments given, ``include_guard`` has the same scope as a variable, -meaning that the include guard effect is isolated by the most recent -function scope or current directory if no inner function scopes exist. -In this case the command behavior is the same as: - -.. code-block:: cmake - - if(__CURRENT_FILE_VAR__) - return() - endif() - set(__CURRENT_FILE_VAR__ TRUE)
diff --git a/share/cmake-3.18/Help/command/install.rst b/share/cmake-3.18/Help/command/install.rst deleted file mode 100644 index c8df7d9..0000000 --- a/share/cmake-3.18/Help/command/install.rst +++ /dev/null
@@ -1,733 +0,0 @@ -install -------- - -Specify rules to run at install time. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - install(`TARGETS`_ <target>... [...]) - install({`FILES`_ | `PROGRAMS`_} <file>... [...]) - install(`DIRECTORY`_ <dir>... [...]) - install(`SCRIPT`_ <file> [...]) - install(`CODE`_ <code> [...]) - install(`EXPORT`_ <export-name> [...]) - -Introduction -^^^^^^^^^^^^ - -This command generates installation rules for a project. Install rules -specified by calls to the ``install()`` command within a source directory -are executed in order during installation. Install rules in subdirectories -added by calls to the :command:`add_subdirectory` command are interleaved -with those in the parent directory to run in the order declared (see -policy :policy:`CMP0082`). - -There are multiple signatures for this command. Some of them define -installation options for files and targets. Options common to -multiple signatures are covered here but they are valid only for -signatures that specify them. The common options are: - -``DESTINATION`` - Specify the directory on disk to which a file will be installed. - Arguments can be relative or absolute paths. - - If a relative path is given it is interpreted relative to the value - of the :variable:`CMAKE_INSTALL_PREFIX` variable. - The prefix can be relocated at install time using the ``DESTDIR`` - mechanism explained in the :variable:`CMAKE_INSTALL_PREFIX` variable - documentation. - - If an absolute path (with a leading slash or drive letter) is given - it is used verbatim. - - As absolute paths are not supported by :manual:`cpack <cpack(1)>` installer - generators, it is preferable to use relative paths throughout. - -``PERMISSIONS`` - Specify permissions for installed files. Valid permissions are - ``OWNER_READ``, ``OWNER_WRITE``, ``OWNER_EXECUTE``, ``GROUP_READ``, - ``GROUP_WRITE``, ``GROUP_EXECUTE``, ``WORLD_READ``, ``WORLD_WRITE``, - ``WORLD_EXECUTE``, ``SETUID``, and ``SETGID``. Permissions that do - not make sense on certain platforms are ignored on those platforms. - -``CONFIGURATIONS`` - Specify a list of build configurations for which the install rule - applies (Debug, Release, etc.). Note that the values specified for - this option only apply to options listed AFTER the ``CONFIGURATIONS`` - option. For example, to set separate install paths for the Debug and - Release configurations, do the following: - - .. code-block:: cmake - - install(TARGETS target - CONFIGURATIONS Debug - RUNTIME DESTINATION Debug/bin) - install(TARGETS target - CONFIGURATIONS Release - RUNTIME DESTINATION Release/bin) - - Note that ``CONFIGURATIONS`` appears BEFORE ``RUNTIME DESTINATION``. - -``COMPONENT`` - Specify an installation component name with which the install rule - is associated, such as "runtime" or "development". During - component-specific installation only install rules associated with - the given component name will be executed. During a full installation - all components are installed unless marked with ``EXCLUDE_FROM_ALL``. - If ``COMPONENT`` is not provided a default component "Unspecified" is - created. The default component name may be controlled with the - :variable:`CMAKE_INSTALL_DEFAULT_COMPONENT_NAME` variable. - -``EXCLUDE_FROM_ALL`` - Specify that the file is excluded from a full installation and only - installed as part of a component-specific installation - -``RENAME`` - Specify a name for an installed file that may be different from the - original file. Renaming is allowed only when a single file is - installed by the command. - -``OPTIONAL`` - Specify that it is not an error if the file to be installed does - not exist. - -Command signatures that install files may print messages during -installation. Use the :variable:`CMAKE_INSTALL_MESSAGE` variable -to control which messages are printed. - -Many of the ``install()`` variants implicitly create the directories -containing the installed files. If -:variable:`CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS` is set, these -directories will be created with the permissions specified. Otherwise, -they will be created according to the uname rules on Unix-like platforms. -Windows platforms are unaffected. - -Installing Targets -^^^^^^^^^^^^^^^^^^ - -.. _`install(TARGETS)`: -.. _TARGETS: - -.. code-block:: cmake - - install(TARGETS targets... [EXPORT <export-name>] - [[ARCHIVE|LIBRARY|RUNTIME|OBJECTS|FRAMEWORK|BUNDLE| - PRIVATE_HEADER|PUBLIC_HEADER|RESOURCE] - [DESTINATION <dir>] - [PERMISSIONS permissions...] - [CONFIGURATIONS [Debug|Release|...]] - [COMPONENT <component>] - [NAMELINK_COMPONENT <component>] - [OPTIONAL] [EXCLUDE_FROM_ALL] - [NAMELINK_ONLY|NAMELINK_SKIP] - ] [...] - [INCLUDES DESTINATION [<dir> ...]] - ) - -The ``TARGETS`` form specifies rules for installing targets from a -project. There are several kinds of target :ref:`Output Artifacts` -that may be installed: - -``ARCHIVE`` - Target artifacts of this kind include: - - * *Static libraries* - (except on macOS when marked as ``FRAMEWORK``, see below); - * *DLL import libraries* - (on all Windows-based systems including Cygwin; they have extension - ``.lib``, in contrast to the ``.dll`` libraries that go to ``RUNTIME``); - * On AIX, the *linker import file* created for executables with - :prop_tgt:`ENABLE_EXPORTS` enabled. - -``LIBRARY`` - Target artifacts of this kind include: - - * *Shared libraries*, except - - - DLLs (these go to ``RUNTIME``, see below), - - on macOS when marked as ``FRAMEWORK`` (see below). - -``RUNTIME`` - Target artifacts of this kind include: - - * *Executables* - (except on macOS when marked as ``MACOSX_BUNDLE``, see ``BUNDLE`` below); - * DLLs (on all Windows-based systems including Cygwin; note that the - accompanying import libraries are of kind ``ARCHIVE``). - -``OBJECTS`` - Object files associated with *object libraries*. - -``FRAMEWORK`` - Both static and shared libraries marked with the ``FRAMEWORK`` - property are treated as ``FRAMEWORK`` targets on macOS. - -``BUNDLE`` - Executables marked with the :prop_tgt:`MACOSX_BUNDLE` property are treated as - ``BUNDLE`` targets on macOS. - -``PUBLIC_HEADER`` - Any :prop_tgt:`PUBLIC_HEADER` files associated with a library are installed in - the destination specified by the ``PUBLIC_HEADER`` argument on non-Apple - platforms. Rules defined by this argument are ignored for :prop_tgt:`FRAMEWORK` - libraries on Apple platforms because the associated files are installed - into the appropriate locations inside the framework folder. See - :prop_tgt:`PUBLIC_HEADER` for details. - -``PRIVATE_HEADER`` - Similar to ``PUBLIC_HEADER``, but for ``PRIVATE_HEADER`` files. See - :prop_tgt:`PRIVATE_HEADER` for details. - -``RESOURCE`` - Similar to ``PUBLIC_HEADER`` and ``PRIVATE_HEADER``, but for - ``RESOURCE`` files. See :prop_tgt:`RESOURCE` for details. - -For each of these arguments given, the arguments following them only apply -to the target or file type specified in the argument. If none is given, the -installation properties apply to all target types. If only one is given then -only targets of that type will be installed (which can be used to install -just a DLL or just an import library.) - -For regular executables, static libraries and shared libraries, the -``DESTINATION`` argument is not required. For these target types, when -``DESTINATION`` is omitted, a default destination will be taken from the -appropriate variable from :module:`GNUInstallDirs`, or set to a built-in -default value if that variable is not defined. The same is true for the -public and private headers associated with the installed targets through the -:prop_tgt:`PUBLIC_HEADER` and :prop_tgt:`PRIVATE_HEADER` target properties. -A destination must always be provided for module libraries, Apple bundles and -frameworks. A destination can be omitted for interface and object libraries, -but they are handled differently (see the discussion of this topic toward the -end of this section). - -The following table shows the target types with their associated variables and -built-in defaults that apply when no destination is given: - -================== =============================== ====================== - Target Type GNUInstallDirs Variable Built-In Default -================== =============================== ====================== -``RUNTIME`` ``${CMAKE_INSTALL_BINDIR}`` ``bin`` -``LIBRARY`` ``${CMAKE_INSTALL_LIBDIR}`` ``lib`` -``ARCHIVE`` ``${CMAKE_INSTALL_LIBDIR}`` ``lib`` -``PRIVATE_HEADER`` ``${CMAKE_INSTALL_INCLUDEDIR}`` ``include`` -``PUBLIC_HEADER`` ``${CMAKE_INSTALL_INCLUDEDIR}`` ``include`` -================== =============================== ====================== - -Projects wishing to follow the common practice of installing headers into a -project-specific subdirectory will need to provide a destination rather than -rely on the above. - -To make packages compliant with distribution filesystem layout policies, if -projects must specify a ``DESTINATION``, it is recommended that they use a -path that begins with the appropriate :module:`GNUInstallDirs` variable. -This allows package maintainers to control the install destination by setting -the appropriate cache variables. The following example shows a static library -being installed to the default destination provided by -:module:`GNUInstallDirs`, but with its headers installed to a project-specific -subdirectory that follows the above recommendation: - -.. code-block:: cmake - - add_library(mylib STATIC ...) - set_target_properties(mylib PROPERTIES PUBLIC_HEADER mylib.h) - include(GNUInstallDirs) - install(TARGETS mylib - PUBLIC_HEADER - DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/myproj - ) - -In addition to the common options listed above, each target can accept -the following additional arguments: - -``NAMELINK_COMPONENT`` - On some platforms a versioned shared library has a symbolic link such - as:: - - lib<name>.so -> lib<name>.so.1 - - where ``lib<name>.so.1`` is the soname of the library and ``lib<name>.so`` - is a "namelink" allowing linkers to find the library when given - ``-l<name>``. The ``NAMELINK_COMPONENT`` option is similar to the - ``COMPONENT`` option, but it changes the installation component of a shared - library namelink if one is generated. If not specified, this defaults to the - value of ``COMPONENT``. It is an error to use this parameter outside of a - ``LIBRARY`` block. - - Consider the following example: - - .. code-block:: cmake - - install(TARGETS mylib - LIBRARY - COMPONENT Libraries - NAMELINK_COMPONENT Development - PUBLIC_HEADER - COMPONENT Development - ) - - In this scenario, if you choose to install only the ``Development`` - component, both the headers and namelink will be installed without the - library. (If you don't also install the ``Libraries`` component, the - namelink will be a dangling symlink, and projects that link to the library - will have build errors.) If you install only the ``Libraries`` component, - only the library will be installed, without the headers and namelink. - - This option is typically used for package managers that have separate - runtime and development packages. For example, on Debian systems, the - library is expected to be in the runtime package, and the headers and - namelink are expected to be in the development package. - - See the :prop_tgt:`VERSION` and :prop_tgt:`SOVERSION` target properties for - details on creating versioned shared libraries. - -``NAMELINK_ONLY`` - This option causes the installation of only the namelink when a library - target is installed. On platforms where versioned shared libraries do not - have namelinks or when a library is not versioned, the ``NAMELINK_ONLY`` - option installs nothing. It is an error to use this parameter outside of a - ``LIBRARY`` block. - - When ``NAMELINK_ONLY`` is given, either ``NAMELINK_COMPONENT`` or - ``COMPONENT`` may be used to specify the installation component of the - namelink, but ``COMPONENT`` should generally be preferred. - -``NAMELINK_SKIP`` - Similar to ``NAMELINK_ONLY``, but it has the opposite effect: it causes the - installation of library files other than the namelink when a library target - is installed. When neither ``NAMELINK_ONLY`` or ``NAMELINK_SKIP`` are given, - both portions are installed. On platforms where versioned shared libraries - do not have symlinks or when a library is not versioned, ``NAMELINK_SKIP`` - installs the library. It is an error to use this parameter outside of a - ``LIBRARY`` block. - - If ``NAMELINK_SKIP`` is specified, ``NAMELINK_COMPONENT`` has no effect. It - is not recommended to use ``NAMELINK_SKIP`` in conjunction with - ``NAMELINK_COMPONENT``. - -The `install(TARGETS)`_ command can also accept the following options at the -top level: - -``EXPORT`` - This option associates the installed target files with an export called - ``<export-name>``. It must appear before any target options. To actually - install the export file itself, call `install(EXPORT)`_, documented below. - See documentation of the :prop_tgt:`EXPORT_NAME` target property to change - the name of the exported target. - -``INCLUDES DESTINATION`` - This option specifies a list of directories which will be added to the - :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` target property of the - ``<targets>`` when exported by the `install(EXPORT)`_ command. If a - relative path is specified, it is treated as relative to the - ``$<INSTALL_PREFIX>``. - -One or more groups of properties may be specified in a single call to -the ``TARGETS`` form of this command. A target may be installed more than -once to different locations. Consider hypothetical targets ``myExe``, -``mySharedLib``, and ``myStaticLib``. The code: - -.. code-block:: cmake - - install(TARGETS myExe mySharedLib myStaticLib - RUNTIME DESTINATION bin - LIBRARY DESTINATION lib - ARCHIVE DESTINATION lib/static) - install(TARGETS mySharedLib DESTINATION /some/full/path) - -will install ``myExe`` to ``<prefix>/bin`` and ``myStaticLib`` to -``<prefix>/lib/static``. On non-DLL platforms ``mySharedLib`` will be -installed to ``<prefix>/lib`` and ``/some/full/path``. On DLL platforms -the ``mySharedLib`` DLL will be installed to ``<prefix>/bin`` and -``/some/full/path`` and its import library will be installed to -``<prefix>/lib/static`` and ``/some/full/path``. - -:ref:`Interface Libraries` may be listed among the targets to install. -They install no artifacts but will be included in an associated ``EXPORT``. -If :ref:`Object Libraries` are listed but given no destination for their -object files, they will be exported as :ref:`Interface Libraries`. -This is sufficient to satisfy transitive usage requirements of other -targets that link to the object libraries in their implementation. - -Installing a target with the :prop_tgt:`EXCLUDE_FROM_ALL` target property -set to ``TRUE`` has undefined behavior. - -`install(TARGETS)`_ can install targets that were created in -other directories. When using such cross-directory install rules, running -``make install`` (or similar) from a subdirectory will not guarantee that -targets from other directories are up-to-date. You can use -:command:`target_link_libraries` or :command:`add_dependencies` -to ensure that such out-of-directory targets are built before the -subdirectory-specific install rules are run. - -An install destination given as a ``DESTINATION`` argument may -use "generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available expressions. - -Installing Files -^^^^^^^^^^^^^^^^ - -.. _`install(FILES)`: -.. _`install(PROGRAMS)`: -.. _FILES: -.. _PROGRAMS: - -.. code-block:: cmake - - install(<FILES|PROGRAMS> files... - TYPE <type> | DESTINATION <dir> - [PERMISSIONS permissions...] - [CONFIGURATIONS [Debug|Release|...]] - [COMPONENT <component>] - [RENAME <name>] [OPTIONAL] [EXCLUDE_FROM_ALL]) - -The ``FILES`` form specifies rules for installing files for a project. -File names given as relative paths are interpreted with respect to the -current source directory. Files installed by this form are by default -given permissions ``OWNER_WRITE``, ``OWNER_READ``, ``GROUP_READ``, and -``WORLD_READ`` if no ``PERMISSIONS`` argument is given. - -The ``PROGRAMS`` form is identical to the ``FILES`` form except that the -default permissions for the installed file also include ``OWNER_EXECUTE``, -``GROUP_EXECUTE``, and ``WORLD_EXECUTE``. This form is intended to install -programs that are not targets, such as shell scripts. Use the ``TARGETS`` -form to install targets built within the project. - -The list of ``files...`` given to ``FILES`` or ``PROGRAMS`` may use -"generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available expressions. -However, if any item begins in a generator expression it must evaluate -to a full path. - -Either a ``TYPE`` or a ``DESTINATION`` must be provided, but not both. -A ``TYPE`` argument specifies the generic file type of the files being -installed. A destination will then be set automatically by taking the -corresponding variable from :module:`GNUInstallDirs`, or by using a -built-in default if that variable is not defined. See the table below for -the supported file types and their corresponding variables and built-in -defaults. Projects can provide a ``DESTINATION`` argument instead of a -file type if they wish to explicitly define the install destination. - -======================= ================================== ========================= - ``TYPE`` Argument GNUInstallDirs Variable Built-In Default -======================= ================================== ========================= -``BIN`` ``${CMAKE_INSTALL_BINDIR}`` ``bin`` -``SBIN`` ``${CMAKE_INSTALL_SBINDIR}`` ``sbin`` -``LIB`` ``${CMAKE_INSTALL_LIBDIR}`` ``lib`` -``INCLUDE`` ``${CMAKE_INSTALL_INCLUDEDIR}`` ``include`` -``SYSCONF`` ``${CMAKE_INSTALL_SYSCONFDIR}`` ``etc`` -``SHAREDSTATE`` ``${CMAKE_INSTALL_SHARESTATEDIR}`` ``com`` -``LOCALSTATE`` ``${CMAKE_INSTALL_LOCALSTATEDIR}`` ``var`` -``RUNSTATE`` ``${CMAKE_INSTALL_RUNSTATEDIR}`` ``<LOCALSTATE dir>/run`` -``DATA`` ``${CMAKE_INSTALL_DATADIR}`` ``<DATAROOT dir>`` -``INFO`` ``${CMAKE_INSTALL_INFODIR}`` ``<DATAROOT dir>/info`` -``LOCALE`` ``${CMAKE_INSTALL_LOCALEDIR}`` ``<DATAROOT dir>/locale`` -``MAN`` ``${CMAKE_INSTALL_MANDIR}`` ``<DATAROOT dir>/man`` -``DOC`` ``${CMAKE_INSTALL_DOCDIR}`` ``<DATAROOT dir>/doc`` -======================= ================================== ========================= - -Projects wishing to follow the common practice of installing headers into a -project-specific subdirectory will need to provide a destination rather than -rely on the above. - -Note that some of the types' built-in defaults use the ``DATAROOT`` directory as -a prefix. The ``DATAROOT`` prefix is calculated similarly to the types, with -``CMAKE_INSTALL_DATAROOTDIR`` as the variable and ``share`` as the built-in -default. You cannot use ``DATAROOT`` as a ``TYPE`` parameter; please use -``DATA`` instead. - -To make packages compliant with distribution filesystem layout policies, if -projects must specify a ``DESTINATION``, it is recommended that they use a -path that begins with the appropriate :module:`GNUInstallDirs` variable. -This allows package maintainers to control the install destination by setting -the appropriate cache variables. The following example shows how to follow -this advice while installing headers to a project-specific subdirectory: - -.. code-block:: cmake - - include(GNUInstallDirs) - install(FILES mylib.h - DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/myproj - ) - -An install destination given as a ``DESTINATION`` argument may -use "generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available expressions. - -Installing Directories -^^^^^^^^^^^^^^^^^^^^^^ - -.. _`install(DIRECTORY)`: -.. _DIRECTORY: - -.. code-block:: cmake - - install(DIRECTORY dirs... - TYPE <type> | DESTINATION <dir> - [FILE_PERMISSIONS permissions...] - [DIRECTORY_PERMISSIONS permissions...] - [USE_SOURCE_PERMISSIONS] [OPTIONAL] [MESSAGE_NEVER] - [CONFIGURATIONS [Debug|Release|...]] - [COMPONENT <component>] [EXCLUDE_FROM_ALL] - [FILES_MATCHING] - [[PATTERN <pattern> | REGEX <regex>] - [EXCLUDE] [PERMISSIONS permissions...]] [...]) - -The ``DIRECTORY`` form installs contents of one or more directories to a -given destination. The directory structure is copied verbatim to the -destination. The last component of each directory name is appended to -the destination directory but a trailing slash may be used to avoid -this because it leaves the last component empty. Directory names -given as relative paths are interpreted with respect to the current -source directory. If no input directory names are given the -destination directory will be created but nothing will be installed -into it. The ``FILE_PERMISSIONS`` and ``DIRECTORY_PERMISSIONS`` options -specify permissions given to files and directories in the destination. -If ``USE_SOURCE_PERMISSIONS`` is specified and ``FILE_PERMISSIONS`` is not, -file permissions will be copied from the source directory structure. -If no permissions are specified files will be given the default -permissions specified in the ``FILES`` form of the command, and the -directories will be given the default permissions specified in the -``PROGRAMS`` form of the command. - -The ``MESSAGE_NEVER`` option disables file installation status output. - -Installation of directories may be controlled with fine granularity -using the ``PATTERN`` or ``REGEX`` options. These "match" options specify a -globbing pattern or regular expression to match directories or files -encountered within input directories. They may be used to apply -certain options (see below) to a subset of the files and directories -encountered. The full path to each input file or directory (with -forward slashes) is matched against the expression. A ``PATTERN`` will -match only complete file names: the portion of the full path matching -the pattern must occur at the end of the file name and be preceded by -a slash. A ``REGEX`` will match any portion of the full path but it may -use ``/`` and ``$`` to simulate the ``PATTERN`` behavior. By default all -files and directories are installed whether or not they are matched. -The ``FILES_MATCHING`` option may be given before the first match option -to disable installation of files (but not directories) not matched by -any expression. For example, the code - -.. code-block:: cmake - - install(DIRECTORY src/ DESTINATION include/myproj - FILES_MATCHING PATTERN "*.h") - -will extract and install header files from a source tree. - -Some options may follow a ``PATTERN`` or ``REGEX`` expression and are applied -only to files or directories matching them. The ``EXCLUDE`` option will -skip the matched file or directory. The ``PERMISSIONS`` option overrides -the permissions setting for the matched file or directory. For -example the code - -.. code-block:: cmake - - install(DIRECTORY icons scripts/ DESTINATION share/myproj - PATTERN "CVS" EXCLUDE - PATTERN "scripts/*" - PERMISSIONS OWNER_EXECUTE OWNER_WRITE OWNER_READ - GROUP_EXECUTE GROUP_READ) - -will install the ``icons`` directory to ``share/myproj/icons`` and the -``scripts`` directory to ``share/myproj``. The icons will get default -file permissions, the scripts will be given specific permissions, and any -``CVS`` directories will be excluded. - -Either a ``TYPE`` or a ``DESTINATION`` must be provided, but not both. -A ``TYPE`` argument specifies the generic file type of the files within the -listed directories being installed. A destination will then be set -automatically by taking the corresponding variable from -:module:`GNUInstallDirs`, or by using a built-in default if that variable -is not defined. See the table below for the supported file types and their -corresponding variables and built-in defaults. Projects can provide a -``DESTINATION`` argument instead of a file type if they wish to explicitly -define the install destination. - -======================= ================================== ========================= - ``TYPE`` Argument GNUInstallDirs Variable Built-In Default -======================= ================================== ========================= -``BIN`` ``${CMAKE_INSTALL_BINDIR}`` ``bin`` -``SBIN`` ``${CMAKE_INSTALL_SBINDIR}`` ``sbin`` -``LIB`` ``${CMAKE_INSTALL_LIBDIR}`` ``lib`` -``INCLUDE`` ``${CMAKE_INSTALL_INCLUDEDIR}`` ``include`` -``SYSCONF`` ``${CMAKE_INSTALL_SYSCONFDIR}`` ``etc`` -``SHAREDSTATE`` ``${CMAKE_INSTALL_SHARESTATEDIR}`` ``com`` -``LOCALSTATE`` ``${CMAKE_INSTALL_LOCALSTATEDIR}`` ``var`` -``RUNSTATE`` ``${CMAKE_INSTALL_RUNSTATEDIR}`` ``<LOCALSTATE dir>/run`` -``DATA`` ``${CMAKE_INSTALL_DATADIR}`` ``<DATAROOT dir>`` -``INFO`` ``${CMAKE_INSTALL_INFODIR}`` ``<DATAROOT dir>/info`` -``LOCALE`` ``${CMAKE_INSTALL_LOCALEDIR}`` ``<DATAROOT dir>/locale`` -``MAN`` ``${CMAKE_INSTALL_MANDIR}`` ``<DATAROOT dir>/man`` -``DOC`` ``${CMAKE_INSTALL_DOCDIR}`` ``<DATAROOT dir>/doc`` -======================= ================================== ========================= - -Note that some of the types' built-in defaults use the ``DATAROOT`` directory as -a prefix. The ``DATAROOT`` prefix is calculated similarly to the types, with -``CMAKE_INSTALL_DATAROOTDIR`` as the variable and ``share`` as the built-in -default. You cannot use ``DATAROOT`` as a ``TYPE`` parameter; please use -``DATA`` instead. - -To make packages compliant with distribution filesystem layout policies, if -projects must specify a ``DESTINATION``, it is recommended that they use a -path that begins with the appropriate :module:`GNUInstallDirs` variable. -This allows package maintainers to control the install destination by setting -the appropriate cache variables. - -The list of ``dirs...`` given to ``DIRECTORY`` and an install destination -given as a ``DESTINATION`` argument may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. - -Custom Installation Logic -^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. _`install(CODE)`: -.. _`install(SCRIPT)`: -.. _CODE: -.. _SCRIPT: - -.. code-block:: cmake - - install([[SCRIPT <file>] [CODE <code>]] - [COMPONENT <component>] [EXCLUDE_FROM_ALL] [...]) - -The ``SCRIPT`` form will invoke the given CMake script files during -installation. If the script file name is a relative path it will be -interpreted with respect to the current source directory. The ``CODE`` -form will invoke the given CMake code during installation. Code is -specified as a single argument inside a double-quoted string. For -example, the code - -.. code-block:: cmake - - install(CODE "MESSAGE(\"Sample install message.\")") - -will print a message during installation. - -``<file>`` or ``<code>`` may use "generator expressions" with the syntax -``$<...>`` (in the case of ``<file>``, this refers to their use in the file -name, not the file's contents). See the -:manual:`cmake-generator-expressions(7)` manual for available expressions. - -Installing Exports -^^^^^^^^^^^^^^^^^^ - -.. _`install(EXPORT)`: -.. _EXPORT: - -.. code-block:: cmake - - install(EXPORT <export-name> DESTINATION <dir> - [NAMESPACE <namespace>] [[FILE <name>.cmake]| - [PERMISSIONS permissions...] - [CONFIGURATIONS [Debug|Release|...]] - [EXPORT_LINK_INTERFACE_LIBRARIES] - [COMPONENT <component>] - [EXCLUDE_FROM_ALL]) - install(EXPORT_ANDROID_MK <export-name> DESTINATION <dir> [...]) - -The ``EXPORT`` form generates and installs a CMake file containing code to -import targets from the installation tree into another project. -Target installations are associated with the export ``<export-name>`` -using the ``EXPORT`` option of the `install(TARGETS)`_ signature -documented above. The ``NAMESPACE`` option will prepend ``<namespace>`` to -the target names as they are written to the import file. By default -the generated file will be called ``<export-name>.cmake`` but the ``FILE`` -option may be used to specify a different name. The value given to -the ``FILE`` option must be a file name with the ``.cmake`` extension. -If a ``CONFIGURATIONS`` option is given then the file will only be installed -when one of the named configurations is installed. Additionally, the -generated import file will reference only the matching target -configurations. The ``EXPORT_LINK_INTERFACE_LIBRARIES`` keyword, if -present, causes the contents of the properties matching -``(IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)?`` to be exported, when -policy :policy:`CMP0022` is ``NEW``. - -.. note:: - The installed ``<export-name>.cmake`` file may come with additional - per-configuration ``<export-name>-*.cmake`` files to be loaded by - globbing. Do not use an export name that is the same as the package - name in combination with installing a ``<package-name>-config.cmake`` - file or the latter may be incorrectly matched by the glob and loaded. - -When a ``COMPONENT`` option is given, the listed ``<component>`` implicitly -depends on all components mentioned in the export set. The exported -``<name>.cmake`` file will require each of the exported components to be -present in order for dependent projects to build properly. For example, a -project may define components ``Runtime`` and ``Development``, with shared -libraries going into the ``Runtime`` component and static libraries and -headers going into the ``Development`` component. The export set would also -typically be part of the ``Development`` component, but it would export -targets from both the ``Runtime`` and ``Development`` components. Therefore, -the ``Runtime`` component would need to be installed if the ``Development`` -component was installed, but not vice versa. If the ``Development`` component -was installed without the ``Runtime`` component, dependent projects that try -to link against it would have build errors. Package managers, such as APT and -RPM, typically handle this by listing the ``Runtime`` component as a dependency -of the ``Development`` component in the package metadata, ensuring that the -library is always installed if the headers and CMake export file are present. - -In addition to cmake language files, the ``EXPORT_ANDROID_MK`` mode maybe -used to specify an export to the android ndk build system. This mode -accepts the same options as the normal export mode. The Android -NDK supports the use of prebuilt libraries, both static and shared. This -allows cmake to build the libraries of a project and make them available -to an ndk build system complete with transitive dependencies, include flags -and defines required to use the libraries. - -The ``EXPORT`` form is useful to help outside projects use targets built -and installed by the current project. For example, the code - -.. code-block:: cmake - - install(TARGETS myexe EXPORT myproj DESTINATION bin) - install(EXPORT myproj NAMESPACE mp_ DESTINATION lib/myproj) - install(EXPORT_ANDROID_MK myproj DESTINATION share/ndk-modules) - -will install the executable ``myexe`` to ``<prefix>/bin`` and code to import -it in the file ``<prefix>/lib/myproj/myproj.cmake`` and -``<prefix>/share/ndk-modules/Android.mk``. An outside project -may load this file with the include command and reference the ``myexe`` -executable from the installation tree using the imported target name -``mp_myexe`` as if the target were built in its own tree. - -.. note:: - This command supercedes the :command:`install_targets` command and - the :prop_tgt:`PRE_INSTALL_SCRIPT` and :prop_tgt:`POST_INSTALL_SCRIPT` - target properties. It also replaces the ``FILES`` forms of the - :command:`install_files` and :command:`install_programs` commands. - The processing order of these install rules relative to - those generated by :command:`install_targets`, - :command:`install_files`, and :command:`install_programs` commands - is not defined. - -Generated Installation Script -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. note:: - - Use of this feature is not recommended. Please consider using the - ``--install`` argument of :manual:`cmake(1)` instead. - -The ``install()`` command generates a file, ``cmake_install.cmake``, inside -the build directory, which is used internally by the generated install target -and by CPack. You can also invoke this script manually with ``cmake -P``. This -script accepts several variables: - -``COMPONENT`` - Set this variable to install only a single CPack component as opposed to all - of them. For example, if you only want to install the ``Development`` - component, run ``cmake -DCOMPONENT=Development -P cmake_install.cmake``. - -``BUILD_TYPE`` - Set this variable to change the build type if you are using a multi-config - generator. For example, to install with the ``Debug`` configuration, run - ``cmake -DBUILD_TYPE=Debug -P cmake_install.cmake``. - -``DESTDIR`` - This is an environment variable rather than a CMake variable. It allows you - to change the installation prefix on UNIX systems. See :envvar:`DESTDIR` for - details.
diff --git a/share/cmake-3.18/Help/command/install_files.rst b/share/cmake-3.18/Help/command/install_files.rst deleted file mode 100644 index ff074a8..0000000 --- a/share/cmake-3.18/Help/command/install_files.rst +++ /dev/null
@@ -1,41 +0,0 @@ -install_files -------------- - -.. deprecated:: 3.0 - - Use the :command:`install(FILES)` command instead. - -This command has been superceded by the :command:`install` command. It is -provided for compatibility with older CMake code. The ``FILES`` form is -directly replaced by the ``FILES`` form of the :command:`install` -command. The regexp form can be expressed more clearly using the ``GLOB`` -form of the :command:`file` command. - -:: - - install_files(<dir> extension file file ...) - -Create rules to install the listed files with the given extension into -the given directory. Only files existing in the current source tree -or its corresponding location in the binary tree may be listed. If a -file specified already has an extension, that extension will be -removed first. This is useful for providing lists of source files -such as foo.cxx when you want the corresponding foo.h to be installed. -A typical extension is ``.h``. - -:: - - install_files(<dir> regexp) - -Any files in the current source directory that match the regular -expression will be installed. - -:: - - install_files(<dir> FILES file file ...) - -Any files listed after the ``FILES`` keyword will be installed explicitly -from the names given. Full paths are allowed in this form. - -The directory ``<dir>`` is relative to the installation prefix, which is -stored in the variable :variable:`CMAKE_INSTALL_PREFIX`.
diff --git a/share/cmake-3.18/Help/command/install_programs.rst b/share/cmake-3.18/Help/command/install_programs.rst deleted file mode 100644 index fab6482..0000000 --- a/share/cmake-3.18/Help/command/install_programs.rst +++ /dev/null
@@ -1,36 +0,0 @@ -install_programs ----------------- - -.. deprecated:: 3.0 - - Use the :command:`install(PROGRAMS)` command instead. - -This command has been superceded by the :command:`install` command. It is -provided for compatibility with older CMake code. The ``FILES`` form is -directly replaced by the ``PROGRAMS`` form of the :command:`install` -command. The regexp form can be expressed more clearly using the ``GLOB`` -form of the :command:`file` command. - -:: - - install_programs(<dir> file1 file2 [file3 ...]) - install_programs(<dir> FILES file1 [file2 ...]) - -Create rules to install the listed programs into the given directory. -Use the ``FILES`` argument to guarantee that the file list version of the -command will be used even when there is only one argument. - -:: - - install_programs(<dir> regexp) - -In the second form any program in the current source directory that -matches the regular expression will be installed. - -This command is intended to install programs that are not built by -cmake, such as shell scripts. See the ``TARGETS`` form of the -:command:`install` command to create installation rules for targets built -by cmake. - -The directory ``<dir>`` is relative to the installation prefix, which is -stored in the variable :variable:`CMAKE_INSTALL_PREFIX`.
diff --git a/share/cmake-3.18/Help/command/install_targets.rst b/share/cmake-3.18/Help/command/install_targets.rst deleted file mode 100644 index c9efdce..0000000 --- a/share/cmake-3.18/Help/command/install_targets.rst +++ /dev/null
@@ -1,19 +0,0 @@ -install_targets ---------------- - -.. deprecated:: 3.0 - - Use the :command:`install(TARGETS)` command instead. - -This command has been superceded by the :command:`install` command. It is -provided for compatibility with older CMake code. - -:: - - install_targets(<dir> [RUNTIME_DIRECTORY dir] target target) - -Create rules to install the listed targets into the given directory. -The directory ``<dir>`` is relative to the installation prefix, which is -stored in the variable :variable:`CMAKE_INSTALL_PREFIX`. If -``RUNTIME_DIRECTORY`` is specified, then on systems with special runtime -files (Windows DLL), the files will be copied to that directory.
diff --git a/share/cmake-3.18/Help/command/link_directories.rst b/share/cmake-3.18/Help/command/link_directories.rst deleted file mode 100644 index 9cb8faa..0000000 --- a/share/cmake-3.18/Help/command/link_directories.rst +++ /dev/null
@@ -1,51 +0,0 @@ -link_directories ----------------- - -Add directories in which the linker will look for libraries. - -.. code-block:: cmake - - link_directories([AFTER|BEFORE] directory1 [directory2 ...]) - -Adds the paths in which the linker should search for libraries. -Relative paths given to this command are interpreted as relative to -the current source directory, see :policy:`CMP0015`. - -The directories are added to the :prop_dir:`LINK_DIRECTORIES` directory -property for the current ``CMakeLists.txt`` file, converting relative -paths to absolute as needed. -The command will apply only to targets created after it is called. - -By default the directories specified are appended onto the current list of -directories. This default behavior can be changed by setting -:variable:`CMAKE_LINK_DIRECTORIES_BEFORE` to ``ON``. By using -``AFTER`` or ``BEFORE`` explicitly, you can select between appending and -prepending, independent of the default. - -Arguments to ``link_directories`` may use "generator expressions" with -the syntax "$<...>". See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -.. note:: - - This command is rarely necessary and should be avoided where there are - other choices. Prefer to pass full absolute paths to libraries where - possible, since this ensures the correct library will always be linked. - The :command:`find_library` command provides the full path, which can - generally be used directly in calls to :command:`target_link_libraries`. - Situations where a library search path may be needed include: - - - Project generators like Xcode where the user can switch target - architecture at build time, but a full path to a library cannot - be used because it only provides one architecture (i.e. it is not - a universal binary). - - Libraries may themselves have other private library dependencies - that expect to be found via ``RPATH`` mechanisms, but some linkers - are not able to fully decode those paths (e.g. due to the presence - of things like ``$ORIGIN``). - - If a library search path must be provided, prefer to localize the effect - where possible by using the :command:`target_link_directories` command - rather than ``link_directories()``. The target-specific command can also - control how the search directories propagate to other dependent targets.
diff --git a/share/cmake-3.18/Help/command/list.rst b/share/cmake-3.18/Help/command/list.rst deleted file mode 100644 index 4d339a0..0000000 --- a/share/cmake-3.18/Help/command/list.rst +++ /dev/null
@@ -1,332 +0,0 @@ -list ----- - -List operations. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - `Reading`_ - list(`LENGTH`_ <list> <out-var>) - list(`GET`_ <list> <element index> [<index> ...] <out-var>) - list(`JOIN`_ <list> <glue> <out-var>) - list(`SUBLIST`_ <list> <begin> <length> <out-var>) - - `Search`_ - list(`FIND`_ <list> <value> <out-var>) - - `Modification`_ - list(`APPEND`_ <list> [<element>...]) - list(`FILTER`_ <list> {INCLUDE | EXCLUDE} REGEX <regex>) - list(`INSERT`_ <list> <index> [<element>...]) - list(`POP_BACK`_ <list> [<out-var>...]) - list(`POP_FRONT`_ <list> [<out-var>...]) - list(`PREPEND`_ <list> [<element>...]) - list(`REMOVE_ITEM`_ <list> <value>...) - list(`REMOVE_AT`_ <list> <index>...) - list(`REMOVE_DUPLICATES`_ <list>) - list(`TRANSFORM`_ <list> <ACTION> [...]) - - `Ordering`_ - list(`REVERSE`_ <list>) - list(`SORT`_ <list> [...]) - -Introduction -^^^^^^^^^^^^ - -The list subcommands ``APPEND``, ``INSERT``, ``FILTER``, ``PREPEND``, -``POP_BACK``, ``POP_FRONT``, ``REMOVE_AT``, ``REMOVE_ITEM``, -``REMOVE_DUPLICATES``, ``REVERSE`` and ``SORT`` may create -new values for the list within the current CMake variable scope. Similar to -the :command:`set` command, the LIST command creates new variable values in -the current scope, even if the list itself is actually defined in a parent -scope. To propagate the results of these operations upwards, use -:command:`set` with ``PARENT_SCOPE``, :command:`set` with -``CACHE INTERNAL``, or some other means of value propagation. - -.. note:: - - A list in cmake is a ``;`` separated group of strings. To create a - list the set command can be used. For example, ``set(var a b c d e)`` - creates a list with ``a;b;c;d;e``, and ``set(var "a b c d e")`` creates a - string or a list with one item in it. (Note macro arguments are not - variables, and therefore cannot be used in LIST commands.) - -.. note:: - - When specifying index values, if ``<element index>`` is 0 or greater, it - is indexed from the beginning of the list, with 0 representing the - first list element. If ``<element index>`` is -1 or lesser, it is indexed - from the end of the list, with -1 representing the last list element. - Be careful when counting with negative indices: they do not start from - 0. -0 is equivalent to 0, the first list element. - -Reading -^^^^^^^ - -.. _LENGTH: - -.. code-block:: cmake - - list(LENGTH <list> <output variable>) - -Returns the list's length. - -.. _GET: - -.. code-block:: cmake - - list(GET <list> <element index> [<element index> ...] <output variable>) - -Returns the list of elements specified by indices from the list. - -.. _JOIN: - -.. code-block:: cmake - - list(JOIN <list> <glue> <output variable>) - -Returns a string joining all list's elements using the glue string. -To join multiple strings, which are not part of a list, use ``JOIN`` operator -from :command:`string` command. - -.. _SUBLIST: - -.. code-block:: cmake - - list(SUBLIST <list> <begin> <length> <output variable>) - -Returns a sublist of the given list. -If ``<length>`` is 0, an empty list will be returned. -If ``<length>`` is -1 or the list is smaller than ``<begin>+<length>`` then -the remaining elements of the list starting at ``<begin>`` will be returned. - -Search -^^^^^^ - -.. _FIND: - -.. code-block:: cmake - - list(FIND <list> <value> <output variable>) - -Returns the index of the element specified in the list or -1 -if it wasn't found. - -Modification -^^^^^^^^^^^^ - -.. _APPEND: - -.. code-block:: cmake - - list(APPEND <list> [<element> ...]) - -Appends elements to the list. - -.. _FILTER: - -.. code-block:: cmake - - list(FILTER <list> <INCLUDE|EXCLUDE> REGEX <regular_expression>) - -Includes or removes items from the list that match the mode's pattern. -In ``REGEX`` mode, items will be matched against the given regular expression. - -For more information on regular expressions see also the -:command:`string` command. - -.. _INSERT: - -.. code-block:: cmake - - list(INSERT <list> <element_index> <element> [<element> ...]) - -Inserts elements to the list to the specified location. - -.. _POP_BACK: - -.. code-block:: cmake - - list(POP_BACK <list> [<out-var>...]) - -If no variable name is given, removes exactly one element. Otherwise, -assign the last element's value to the given variable and removes it, -up to the last variable name given. - -.. _POP_FRONT: - -.. code-block:: cmake - - list(POP_FRONT <list> [<out-var>...]) - -If no variable name is given, removes exactly one element. Otherwise, -assign the first element's value to the given variable and removes it, -up to the last variable name given. - -.. _PREPEND: - -.. code-block:: cmake - - list(PREPEND <list> [<element> ...]) - -Insert elements to the 0th position in the list. - -.. _REMOVE_ITEM: - -.. code-block:: cmake - - list(REMOVE_ITEM <list> <value> [<value> ...]) - -Removes all instances of the given items from the list. - -.. _REMOVE_AT: - -.. code-block:: cmake - - list(REMOVE_AT <list> <index> [<index> ...]) - -Removes items at given indices from the list. - -.. _REMOVE_DUPLICATES: - -.. code-block:: cmake - - list(REMOVE_DUPLICATES <list>) - -Removes duplicated items in the list. The relative order of items is preserved, -but if duplicates are encountered, only the first instance is preserved. - -.. _TRANSFORM: - -.. code-block:: cmake - - list(TRANSFORM <list> <ACTION> [<SELECTOR>] - [OUTPUT_VARIABLE <output variable>]) - -Transforms the list by applying an action to all or, by specifying a -``<SELECTOR>``, to the selected elements of the list, storing the result -in-place or in the specified output variable. - -.. note:: - - The ``TRANSFORM`` sub-command does not change the number of elements in the - list. If a ``<SELECTOR>`` is specified, only some elements will be changed, - the other ones will remain the same as before the transformation. - -``<ACTION>`` specifies the action to apply to the elements of the list. -The actions have exactly the same semantics as sub-commands of the -:command:`string` command. ``<ACTION>`` must be one of the following: - -``APPEND``, ``PREPEND``: Append, prepend specified value to each element of -the list. - - .. code-block:: cmake - - list(TRANSFORM <list> <APPEND|PREPEND> <value> ...) - -``TOUPPER``, ``TOLOWER``: Convert each element of the list to upper, lower -characters. - - .. code-block:: cmake - - list(TRANSFORM <list> <TOLOWER|TOUPPER> ...) - -``STRIP``: Remove leading and trailing spaces from each element of the -list. - - .. code-block:: cmake - - list(TRANSFORM <list> STRIP ...) - -``GENEX_STRIP``: Strip any -:manual:`generator expressions <cmake-generator-expressions(7)>` from each -element of the list. - - .. code-block:: cmake - - list(TRANSFORM <list> GENEX_STRIP ...) - -``REPLACE``: Match the regular expression as many times as possible and -substitute the replacement expression for the match for each element -of the list -(Same semantic as ``REGEX REPLACE`` from :command:`string` command). - - .. code-block:: cmake - - list(TRANSFORM <list> REPLACE <regular_expression> - <replace_expression> ...) - -``<SELECTOR>`` determines which elements of the list will be transformed. -Only one type of selector can be specified at a time. When given, -``<SELECTOR>`` must be one of the following: - -``AT``: Specify a list of indexes. - - .. code-block:: cmake - - list(TRANSFORM <list> <ACTION> AT <index> [<index> ...] ...) - -``FOR``: Specify a range with, optionally, an increment used to iterate over -the range. - - .. code-block:: cmake - - list(TRANSFORM <list> <ACTION> FOR <start> <stop> [<step>] ...) - -``REGEX``: Specify a regular expression. Only elements matching the regular -expression will be transformed. - - .. code-block:: cmake - - list(TRANSFORM <list> <ACTION> REGEX <regular_expression> ...) - - -Ordering -^^^^^^^^ - -.. _REVERSE: - -.. code-block:: cmake - - list(REVERSE <list>) - -Reverses the contents of the list in-place. - -.. _SORT: - -.. code-block:: cmake - - list(SORT <list> [COMPARE <compare>] [CASE <case>] [ORDER <order>]) - -Sorts the list in-place alphabetically. -Use the ``COMPARE`` keyword to select the comparison method for sorting. -The ``<compare>`` option should be one of: - -* ``STRING``: Sorts a list of strings alphabetically. This is the - default behavior if the ``COMPARE`` option is not given. -* ``FILE_BASENAME``: Sorts a list of pathnames of files by their basenames. -* ``NATURAL``: Sorts a list of strings using natural order - (see ``strverscmp(3)`` manual), i.e. such that contiguous digits - are compared as whole numbers. - For example: the following list `10.0 1.1 2.1 8.0 2.0 3.1` - will be sorted as `1.1 2.0 2.1 3.1 8.0 10.0` if the ``NATURAL`` - comparison is selected where it will be sorted as - `1.1 10.0 2.0 2.1 3.1 8.0` with the ``STRING`` comparison. - -Use the ``CASE`` keyword to select a case sensitive or case insensitive -sort mode. The ``<case>`` option should be one of: - -* ``SENSITIVE``: List items are sorted in a case-sensitive manner. This is - the default behavior if the ``CASE`` option is not given. -* ``INSENSITIVE``: List items are sorted case insensitively. The order of - items which differ only by upper/lowercase is not specified. - -To control the sort order, the ``ORDER`` keyword can be given. -The ``<order>`` option should be one of: - -* ``ASCENDING``: Sorts the list in ascending order. This is the default - behavior when the ``ORDER`` option is not given. -* ``DESCENDING``: Sorts the list in descending order.
diff --git a/share/cmake-3.18/Help/command/macro.rst b/share/cmake-3.18/Help/command/macro.rst deleted file mode 100644 index 797a90d..0000000 --- a/share/cmake-3.18/Help/command/macro.rst +++ /dev/null
@@ -1,150 +0,0 @@ -macro ------ - -Start recording a macro for later invocation as a command - -.. code-block:: cmake - - macro(<name> [<arg1> ...]) - <commands> - endmacro() - -Defines a macro named ``<name>`` that takes arguments named -``<arg1>``, ... Commands listed after macro, but before the -matching :command:`endmacro()`, are not executed until the macro -is invoked. - -Per legacy, the :command:`endmacro` command admits an optional -``<name>`` argument. If used, it must be a verbatim repeat of the -argument of the opening ``macro`` command. - -See the :command:`cmake_policy()` command documentation for the behavior -of policies inside macros. - -See the :ref:`Macro vs Function` section below for differences -between CMake macros and :command:`functions <function>`. - -Invocation -^^^^^^^^^^ - -The macro invocation is case-insensitive. A macro defined as - -.. code-block:: cmake - - macro(foo) - <commands> - endmacro() - -can be invoked through any of - -.. code-block:: cmake - - foo() - Foo() - FOO() - cmake_language(CALL foo) - -and so on. However, it is strongly recommended to stay with the -case chosen in the macro definition. Typically macros use -all-lowercase names. - -The :command:`cmake_language(CALL ...)` command can also be used to -invoke the macro. - -Arguments -^^^^^^^^^ - -When a macro is invoked, the commands recorded in the macro are -first modified by replacing formal parameters (``${arg1}``, ...) -with the arguments passed, and then invoked as normal commands. - -In addition to referencing the formal parameters you can reference the -values ``${ARGC}`` which will be set to the number of arguments passed -into the function as well as ``${ARGV0}``, ``${ARGV1}``, ``${ARGV2}``, -... which will have the actual values of the arguments passed in. -This facilitates creating macros with optional arguments. - -Furthermore, ``${ARGV}`` holds the list of all arguments given to the -macro and ``${ARGN}`` holds the list of arguments past the last expected -argument. -Referencing to ``${ARGV#}`` arguments beyond ``${ARGC}`` have undefined -behavior. Checking that ``${ARGC}`` is greater than ``#`` is the only -way to ensure that ``${ARGV#}`` was passed to the function as an extra -argument. - -.. _`Macro vs Function`: - -Macro vs Function -^^^^^^^^^^^^^^^^^ - -The ``macro`` command is very similar to the :command:`function` command. -Nonetheless, there are a few important differences. - -In a function, ``ARGN``, ``ARGC``, ``ARGV`` and ``ARGV0``, ``ARGV1``, ... -are true variables in the usual CMake sense. In a macro, they are not, -they are string replacements much like the C preprocessor would do -with a macro. This has a number of consequences, as explained in -the :ref:`Argument Caveats` section below. - -Another difference between macros and functions is the control flow. -A function is executed by transferring control from the calling -statement to the function body. A macro is executed as if the macro -body were pasted in place of the calling statement. This has the -consequence that a :command:`return()` in a macro body does not -just terminate execution of the macro; rather, control is returned -from the scope of the macro call. To avoid confusion, it is recommended -to avoid :command:`return()` in macros altogether. - -Unlike a function, the :variable:`CMAKE_CURRENT_FUNCTION`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE` variables are not -set for a macro. - -.. _`Argument Caveats`: - -Argument Caveats -^^^^^^^^^^^^^^^^ - -Since ``ARGN``, ``ARGC``, ``ARGV``, ``ARGV0`` etc. are not variables, -you will NOT be able to use commands like - -.. code-block:: cmake - - if(ARGV1) # ARGV1 is not a variable - if(DEFINED ARGV2) # ARGV2 is not a variable - if(ARGC GREATER 2) # ARGC is not a variable - foreach(loop_var IN LISTS ARGN) # ARGN is not a variable - -In the first case, you can use ``if(${ARGV1})``. In the second and -third case, the proper way to check if an optional variable was -passed to the macro is to use ``if(${ARGC} GREATER 2)``. In the -last case, you can use ``foreach(loop_var ${ARGN})`` but this will -skip empty arguments. If you need to include them, you can use - -.. code-block:: cmake - - set(list_var "${ARGN}") - foreach(loop_var IN LISTS list_var) - -Note that if you have a variable with the same name in the scope from -which the macro is called, using unreferenced names will use the -existing variable instead of the arguments. For example: - -.. code-block:: cmake - - macro(bar) - foreach(arg IN LISTS ARGN) - <commands> - endforeach() - endmacro() - - function(foo) - bar(x y z) - endfunction() - - foo(a b c) - -Will loop over ``a;b;c`` and not over ``x;y;z`` as one might have expected. -If you want true CMake variables and/or better CMake scope control you -should look at the function command.
diff --git a/share/cmake-3.18/Help/command/mark_as_advanced.rst b/share/cmake-3.18/Help/command/mark_as_advanced.rst deleted file mode 100644 index e52e623..0000000 --- a/share/cmake-3.18/Help/command/mark_as_advanced.rst +++ /dev/null
@@ -1,30 +0,0 @@ -mark_as_advanced ----------------- - -Mark cmake cached variables as advanced. - -.. code-block:: cmake - - mark_as_advanced([CLEAR|FORCE] <var1> ...) - -Sets the advanced/non-advanced state of the named -cached variables. - -An advanced variable will not be displayed in any -of the cmake GUIs unless the ``show advanced`` option is on. -In script mode, the advanced/non-advanced state has no effect. - -If the keyword ``CLEAR`` is given -then advanced variables are changed back to unadvanced. -If the keyword ``FORCE`` is given -then the variables are made advanced. -If neither ``FORCE`` nor ``CLEAR`` is specified, -new values will be marked as advanced, but if a -variable already has an advanced/non-advanced state, -it will not be changed. - -.. note:: - - Policy :policy:`CMP0102` affects the behavior of the ``mark_as_advanced`` - call. When set to ``NEW``, variables passed to this command which are not - already in the cache are ignored. See policy :policy:`CMP0102`.
diff --git a/share/cmake-3.18/Help/command/math.rst b/share/cmake-3.18/Help/command/math.rst deleted file mode 100644 index ddb1ec6..0000000 --- a/share/cmake-3.18/Help/command/math.rst +++ /dev/null
@@ -1,37 +0,0 @@ -math ----- - -Evaluate a mathematical expression. - -.. code-block:: cmake - - math(EXPR <variable> "<expression>" [OUTPUT_FORMAT <format>]) - -Evaluates a mathematical ``<expression>`` and sets ``<variable>`` to the -resulting value. The result of the expression must be representable as a -64-bit signed integer. - -The mathematical expression must be given as a string (i.e. enclosed in -double quotation marks). An example is ``"5 * (10 + 13)"``. -Supported operators are ``+``, ``-``, ``*``, ``/``, ``%``, ``|``, ``&``, -``^``, ``~``, ``<<``, ``>>``, and ``(...)``; they have the same meaning -as in C code. - -Hexadecimal numbers are recognized when prefixed with ``0x``, as in C code. - -The result is formatted according to the option ``OUTPUT_FORMAT``, -where ``<format>`` is one of - -``HEXADECIMAL`` - Hexadecimal notation as in C code, i. e. starting with "0x". -``DECIMAL`` - Decimal notation. Which is also used if no ``OUTPUT_FORMAT`` option - is specified. - - -For example - -.. code-block:: cmake - - math(EXPR value "100 * 0xA" OUTPUT_FORMAT DECIMAL) # value is set to "1000" - math(EXPR value "100 * 0xA" OUTPUT_FORMAT HEXADECIMAL) # value is set to "0x3e8"
diff --git a/share/cmake-3.18/Help/command/message.rst b/share/cmake-3.18/Help/command/message.rst deleted file mode 100644 index 6bc0e4c..0000000 --- a/share/cmake-3.18/Help/command/message.rst +++ /dev/null
@@ -1,182 +0,0 @@ -message -------- - -Log a message. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - `General messages`_ - message([<mode>] "message text" ...) - - `Reporting checks`_ - message(<checkState> "message text" ...) - - -General messages -^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - message([<mode>] "message text" ...) - -Record the specified message text in the log. If more than one message -string is given, they are concatenated into a single message with no -separator between the strings. - -The optional ``<mode>`` keyword determines the type of message, which -influences the way the message is handled: - -``FATAL_ERROR`` - CMake Error, stop processing and generation. - -``SEND_ERROR`` - CMake Error, continue processing, but skip generation. - -``WARNING`` - CMake Warning, continue processing. - -``AUTHOR_WARNING`` - CMake Warning (dev), continue processing. - -``DEPRECATION`` - CMake Deprecation Error or Warning if variable - :variable:`CMAKE_ERROR_DEPRECATED` or :variable:`CMAKE_WARN_DEPRECATED` - is enabled, respectively, else no message. - -(none) or ``NOTICE`` - Important message printed to stderr to attract user's attention. - -``STATUS`` - The main interesting messages that project users might be interested in. - Ideally these should be concise, no more than a single line, but still - informative. - -``VERBOSE`` - Detailed informational messages intended for project users. These messages - should provide additional details that won't be of interest in most cases, - but which may be useful to those building the project when they want deeper - insight into what's happening. - -``DEBUG`` - Detailed informational messages intended for developers working on the - project itself as opposed to users who just want to build it. These messages - will not typically be of interest to other users building the project and - will often be closely related to internal implementation details. - -``TRACE`` - Fine-grained messages with very low-level implementation details. Messages - using this log level would normally only be temporary and would expect to be - removed before releasing the project, packaging up the files, etc. - -The CMake command-line tool displays ``STATUS`` to ``TRACE`` messages on stdout -with the message preceded by two hyphens and a space. All other message types -are sent to stderr and are not prefixed with hyphens. The -:manual:`CMake GUI <cmake-gui(1)>` displays all messages in its log area. -The :manual:`curses interface <ccmake(1)>` shows ``STATUS`` to ``TRACE`` -messages one at a time on a status line and other messages in an -interactive pop-up box. The ``--log-level`` command-line option to each of -these tools can be used to control which messages will be shown. -To make a log level persist between CMake runs, the -:variable:`CMAKE_MESSAGE_LOG_LEVEL` variable can be set instead. -Note that the command line option takes precedence over the cache variable. - -Messages of log levels ``NOTICE`` and below will have each line preceded -by the content of the :variable:`CMAKE_MESSAGE_INDENT` variable (converted to -a single string by concatenating its list items). For ``STATUS`` to ``TRACE`` -messages, this indenting content will be inserted after the hyphens. - -Messages of log levels ``NOTICE`` and below can also have each line preceded -with context of the form ``[some.context.example]``. The content between the -square brackets is obtained by converting the :variable:`CMAKE_MESSAGE_CONTEXT` -list variable to a dot-separated string. The message context will always -appear before any indenting content but after any automatically added leading -hyphens. By default, message context is not shown, it has to be explicitly -enabled by giving the :manual:`cmake <cmake(1)>` ``--log-context`` -command-line option or by setting the :variable:`CMAKE_MESSAGE_CONTEXT_SHOW` -variable to true. See the :variable:`CMAKE_MESSAGE_CONTEXT` documentation for -usage examples. - -CMake Warning and Error message text displays using a simple markup -language. Non-indented text is formatted in line-wrapped paragraphs -delimited by newlines. Indented text is considered pre-formatted. - - -Reporting checks -^^^^^^^^^^^^^^^^ - -A common pattern in CMake output is a message indicating the start of some -sort of check, followed by another message reporting the result of that check. -For example: - -.. code-block:: cmake - - message(STATUS "Looking for someheader.h") - #... do the checks, set checkSuccess with the result - if(checkSuccess) - message(STATUS "Looking for someheader.h - found") - else() - message(STATUS "Looking for someheader.h - not found") - endif() - -This can be more robustly and conveniently expressed using the ``CHECK_...`` -keyword form of the ``message()`` command: - -.. code-block:: cmake - - message(<checkState> "message" ...) - -where ``<checkState>`` must be one of the following: - - ``CHECK_START`` - Record a concise message about the check about to be performed. - - ``CHECK_PASS`` - Record a successful result for a check. - - ``CHECK_FAIL`` - Record an unsuccessful result for a check. - -When recording a check result, the command repeats the message from the most -recently started check for which no result has yet been reported, then some -separator characters and then the message text provided after the -``CHECK_PASS`` or ``CHECK_FAIL`` keyword. Check messages are always reported -at ``STATUS`` log level. - -Checks may be nested and every ``CHECK_START`` should have exactly one -matching ``CHECK_PASS`` or ``CHECK_FAIL``. -The :variable:`CMAKE_MESSAGE_INDENT` variable can also be used to add -indenting to nested checks if desired. For example: - -.. code-block:: cmake - - message(CHECK_START "Finding my things") - list(APPEND CMAKE_MESSAGE_INDENT " ") - unset(missingComponents) - - message(CHECK_START "Finding partA") - # ... do check, assume we find A - message(CHECK_PASS "found") - - message(CHECK_START "Finding partB") - # ... do check, assume we don't find B - list(APPEND missingComponents B) - message(CHECK_FAIL "not found") - - list(POP_BACK CMAKE_MESSAGE_INDENT) - if(missingComponents) - message(CHECK_FAIL "missing components: ${missingComponents}") - else() - message(CHECK_PASS "all components found") - endif() - -Output from the above would appear something like the following:: - - -- Finding my things - -- Finding partA - -- Finding partA - found - -- Finding partB - -- Finding partB - not found - -- Finding my things - missing components: B
diff --git a/share/cmake-3.18/Help/command/project.rst b/share/cmake-3.18/Help/command/project.rst deleted file mode 100644 index b6093d3..0000000 --- a/share/cmake-3.18/Help/command/project.rst +++ /dev/null
@@ -1,133 +0,0 @@ -project -------- - -Set the name of the project. - -Synopsis -^^^^^^^^ - -.. code-block:: cmake - - project(<PROJECT-NAME> [<language-name>...]) - project(<PROJECT-NAME> - [VERSION <major>[.<minor>[.<patch>[.<tweak>]]]] - [DESCRIPTION <project-description-string>] - [HOMEPAGE_URL <url-string>] - [LANGUAGES <language-name>...]) - -Sets the name of the project, and stores it in the variable -:variable:`PROJECT_NAME`. When called from the top-level -``CMakeLists.txt`` also stores the project name in the -variable :variable:`CMAKE_PROJECT_NAME`. - -Also sets the variables - -* :variable:`PROJECT_SOURCE_DIR`, - :variable:`<PROJECT-NAME>_SOURCE_DIR` -* :variable:`PROJECT_BINARY_DIR`, - :variable:`<PROJECT-NAME>_BINARY_DIR` - -Further variables are set by the optional arguments described in the following. -If any of these arguments is not used, then the corresponding variables are -set to the empty string. - -Options -^^^^^^^ - -The options are: - -``VERSION <version>`` - Optional; may not be used unless policy :policy:`CMP0048` is - set to ``NEW``. - - Takes a ``<version>`` argument composed of non-negative integer components, - i.e. ``<major>[.<minor>[.<patch>[.<tweak>]]]``, - and sets the variables - - * :variable:`PROJECT_VERSION`, - :variable:`<PROJECT-NAME>_VERSION` - * :variable:`PROJECT_VERSION_MAJOR`, - :variable:`<PROJECT-NAME>_VERSION_MAJOR` - * :variable:`PROJECT_VERSION_MINOR`, - :variable:`<PROJECT-NAME>_VERSION_MINOR` - * :variable:`PROJECT_VERSION_PATCH`, - :variable:`<PROJECT-NAME>_VERSION_PATCH` - * :variable:`PROJECT_VERSION_TWEAK`, - :variable:`<PROJECT-NAME>_VERSION_TWEAK`. - - When the ``project()`` command is called from the top-level ``CMakeLists.txt``, - then the version is also stored in the variable :variable:`CMAKE_PROJECT_VERSION`. - -``DESCRIPTION <project-description-string>`` - Optional. - Sets the variables - - * :variable:`PROJECT_DESCRIPTION`, :variable:`<PROJECT-NAME>_DESCRIPTION` - - to ``<project-description-string>``. - It is recommended that this description is a relatively short string, - usually no more than a few words. - - When the ``project()`` command is called from the top-level ``CMakeLists.txt``, - then the description is also stored in the variable :variable:`CMAKE_PROJECT_DESCRIPTION`. - -``HOMEPAGE_URL <url-string>`` - Optional. - Sets the variables - - * :variable:`PROJECT_HOMEPAGE_URL`, :variable:`<PROJECT-NAME>_HOMEPAGE_URL` - - to ``<url-string>``, which should be the canonical home URL for the project. - - When the ``project()`` command is called from the top-level ``CMakeLists.txt``, - then the URL also is stored in the variable :variable:`CMAKE_PROJECT_HOMEPAGE_URL`. - -``LANGUAGES <language-name>...`` - Optional. - Can also be specified without ``LANGUAGES`` keyword per the first, short signature. - - Selects which programming languages are needed to build the project. - Supported languages include ``C``, ``CXX`` (i.e. C++), ``CUDA``, - ``OBJC`` (i.e. Objective-C), ``OBJCXX``, ``Fortran``, and ``ASM``. - By default ``C`` and ``CXX`` are enabled if no language options are given. - Specify language ``NONE``, or use the ``LANGUAGES`` keyword and list no languages, - to skip enabling any languages. - - If enabling ``ASM``, list it last so that CMake can check whether - compilers for other languages like ``C`` work for assembly too. - -The variables set through the ``VERSION``, ``DESCRIPTION`` and ``HOMEPAGE_URL`` -options are intended for use as default values in package metadata and documentation. - -Code Injection -^^^^^^^^^^^^^^ - -If the :variable:`CMAKE_PROJECT_INCLUDE_BEFORE` or -:variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE` variables are set, -the files they point to will be included as the first step of the -``project()`` command. -If both are set, then :variable:`CMAKE_PROJECT_INCLUDE_BEFORE` will be -included before :variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE`. - -If the :variable:`CMAKE_PROJECT_INCLUDE` or -:variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE` variables are set, the files -they point to will be included as the last step of the ``project()`` command. -If both are set, then :variable:`CMAKE_PROJECT_INCLUDE` will be included before -:variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE`. - -Usage -^^^^^ - -The top-level ``CMakeLists.txt`` file for a project must contain a -literal, direct call to the ``project()`` command; loading one -through the :command:`include` command is not sufficient. If no such -call exists, CMake will issue a warning and pretend there is a -``project(Project)`` at the top to enable the default languages -(``C`` and ``CXX``). - -.. note:: - Call the ``project()`` command near the top of the top-level - ``CMakeLists.txt``, but *after* calling :command:`cmake_minimum_required`. - It is important to establish version and policy settings before invoking - other commands whose behavior they may affect. - See also policy :policy:`CMP0000`.
diff --git a/share/cmake-3.18/Help/command/return.rst b/share/cmake-3.18/Help/command/return.rst deleted file mode 100644 index 830992c..0000000 --- a/share/cmake-3.18/Help/command/return.rst +++ /dev/null
@@ -1,19 +0,0 @@ -return ------- - -Return from a file, directory or function. - -.. code-block:: cmake - - return() - -Returns from a file, directory or function. When this command is -encountered in an included file (via :command:`include` or -:command:`find_package`), it causes processing of the current file to stop -and control is returned to the including file. If it is encountered in a -file which is not included by another file, e.g. a ``CMakeLists.txt``, -control is returned to the parent directory if there is one. If return is -called in a function, control is returned to the caller of the function. - -Note that a :command:`macro <macro>`, unlike a :command:`function <function>`, -is expanded in place and therefore cannot handle ``return()``.
diff --git a/share/cmake-3.18/Help/command/separate_arguments.rst b/share/cmake-3.18/Help/command/separate_arguments.rst deleted file mode 100644 index ab3d5c1..0000000 --- a/share/cmake-3.18/Help/command/separate_arguments.rst +++ /dev/null
@@ -1,46 +0,0 @@ -separate_arguments ------------------- - -Parse command-line arguments into a semicolon-separated list. - -.. code-block:: cmake - - separate_arguments(<variable> <mode> <args>) - -Parses a space-separated string ``<args>`` into a list of items, -and stores this list in semicolon-separated standard form in ``<variable>``. - -This function is intended for parsing command-line arguments. -The entire command line must be passed as one string in the -argument ``<args>``. - -The exact parsing rules depend on the operating system. -They are specified by the ``<mode>`` argument which must -be one of the following keywords: - -``UNIX_COMMAND`` - Arguments are separated by unquoted whitespace. - Both single-quote and double-quote pairs are respected. - A backslash escapes the next literal character (``\"`` is ``"``); - there are no special escapes (``\n`` is just ``n``). - -``WINDOWS_COMMAND`` - A Windows command-line is parsed using the same - syntax the runtime library uses to construct argv at startup. It - separates arguments by whitespace that is not double-quoted. - Backslashes are literal unless they precede double-quotes. See the - MSDN article `Parsing C Command-Line Arguments`_ for details. - -``NATIVE_COMMAND`` - Proceeds as in ``WINDOWS_COMMAND`` mode if the host system is Windows. - Otherwise proceeds as in ``UNIX_COMMAND`` mode. - -.. _`Parsing C Command-Line Arguments`: https://msdn.microsoft.com/library/a1y7w461.aspx - -.. code-block:: cmake - - separate_arguments(<var>) - -Convert the value of ``<var>`` to a semi-colon separated list. All -spaces are replaced with ';'. This helps with generating command -lines.
diff --git a/share/cmake-3.18/Help/command/set.rst b/share/cmake-3.18/Help/command/set.rst deleted file mode 100644 index c0e02e2..0000000 --- a/share/cmake-3.18/Help/command/set.rst +++ /dev/null
@@ -1,104 +0,0 @@ -set ---- - -Set a normal, cache, or environment variable to a given value. -See the :ref:`cmake-language(7) variables <CMake Language Variables>` -documentation for the scopes and interaction of normal variables -and cache entries. - -Signatures of this command that specify a ``<value>...`` placeholder -expect zero or more arguments. Multiple arguments will be joined as -a :ref:`semicolon-separated list <CMake Language Lists>` to form the actual variable -value to be set. Zero arguments will cause normal variables to be -unset. See the :command:`unset` command to unset variables explicitly. - -Set Normal Variable -^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - set(<variable> <value>... [PARENT_SCOPE]) - -Sets the given ``<variable>`` in the current function or directory scope. - -If the ``PARENT_SCOPE`` option is given the variable will be set in -the scope above the current scope. Each new directory or function -creates a new scope. This command will set the value of a variable -into the parent directory or calling function (whichever is applicable -to the case at hand). The previous state of the variable's value stays the -same in the current scope (e.g., if it was undefined before, it is still -undefined and if it had a value, it is still that value). - -Set Cache Entry -^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - set(<variable> <value>... CACHE <type> <docstring> [FORCE]) - -Sets the given cache ``<variable>`` (cache entry). Since cache entries -are meant to provide user-settable values this does not overwrite -existing cache entries by default. Use the ``FORCE`` option to -overwrite existing entries. - -The ``<type>`` must be specified as one of: - -``BOOL`` - Boolean ``ON/OFF`` value. :manual:`cmake-gui(1)` offers a checkbox. - -``FILEPATH`` - Path to a file on disk. :manual:`cmake-gui(1)` offers a file dialog. - -``PATH`` - Path to a directory on disk. :manual:`cmake-gui(1)` offers a file dialog. - -``STRING`` - A line of text. :manual:`cmake-gui(1)` offers a text field or a - drop-down selection if the :prop_cache:`STRINGS` cache entry - property is set. - -``INTERNAL`` - A line of text. :manual:`cmake-gui(1)` does not show internal entries. - They may be used to store variables persistently across runs. - Use of this type implies ``FORCE``. - -The ``<docstring>`` must be specified as a line of text providing -a quick summary of the option for presentation to :manual:`cmake-gui(1)` -users. - -If the cache entry does not exist prior to the call or the ``FORCE`` -option is given then the cache entry will be set to the given value. -Furthermore, any normal variable binding in the current scope will -be removed to expose the newly cached value to any immediately -following evaluation. - -It is possible for the cache entry to exist prior to the call but -have no type set if it was created on the :manual:`cmake(1)` command -line by a user through the ``-D<var>=<value>`` option without -specifying a type. In this case the ``set`` command will add the -type. Furthermore, if the ``<type>`` is ``PATH`` or ``FILEPATH`` -and the ``<value>`` provided on the command line is a relative path, -then the ``set`` command will treat the path as relative to the -current working directory and convert it to an absolute path. - -Set Environment Variable -^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - set(ENV{<variable>} [<value>]) - -Sets an :manual:`Environment Variable <cmake-env-variables(7)>` -to the given value. -Subsequent calls of ``$ENV{<variable>}`` will return this new value. - -This command affects only the current CMake process, not the process -from which CMake was called, nor the system environment at large, -nor the environment of subsequent build or test processes. - -If no argument is given after ``ENV{<variable>}`` or if ``<value>`` is -an empty string, then this command will clear any existing value of the -environment variable. - -Arguments after ``<value>`` are ignored. If extra arguments are found, -then an author warning is issued.
diff --git a/share/cmake-3.18/Help/command/set_property.rst b/share/cmake-3.18/Help/command/set_property.rst deleted file mode 100644 index 93c2d9c..0000000 --- a/share/cmake-3.18/Help/command/set_property.rst +++ /dev/null
@@ -1,96 +0,0 @@ -set_property ------------- - -Set a named property in a given scope. - -.. code-block:: cmake - - set_property(<GLOBAL | - DIRECTORY [<dir>] | - TARGET [<target1> ...] | - SOURCE [<src1> ...] - [DIRECTORY <dirs> ...] | - [TARGET_DIRECTORY <targets> ...] - INSTALL [<file1> ...] | - TEST [<test1> ...] | - CACHE [<entry1> ...] > - [APPEND] [APPEND_STRING] - PROPERTY <name> [<value1> ...]) - -Sets one property on zero or more objects of a scope. - -The first argument determines the scope in which the property is set. -It must be one of the following: - -``GLOBAL`` - Scope is unique and does not accept a name. - -``DIRECTORY`` - Scope defaults to the current directory but another directory - (already processed by CMake) may be named by full or relative path. - See also the :command:`set_directory_properties` command. - -``TARGET`` - Scope may name zero or more existing targets. - See also the :command:`set_target_properties` command. - -``SOURCE`` - Scope may name zero or more source files. By default, source file properties - are only visible to targets added in the same directory (``CMakeLists.txt``). - Visibility can be set in other directory scopes using one or both of the - following sub-options: - - ``DIRECTORY <dirs>...`` - The source file property will be set in each of the ``<dirs>`` - directories' scopes. CMake must already know about each of these - source directories, either by having added them through a call to - :command:`add_subdirectory` or it being the top level source directory. - Relative paths are treated as relative to the current source directory. - - ``TARGET_DIRECTORY <targets>...`` - The source file property will be set in each of the directory scopes - where any of the specified ``<targets>`` were created (the ``<targets>`` - must therefore already exist). - - See also the :command:`set_source_files_properties` command. - -``INSTALL`` - Scope may name zero or more installed file paths. - These are made available to CPack to influence deployment. - - Both the property key and value may use generator expressions. - Specific properties may apply to installed files and/or directories. - - Path components have to be separated by forward slashes, - must be normalized and are case sensitive. - - To reference the installation prefix itself with a relative path use ``.``. - - Currently installed file properties are only defined for - the WIX generator where the given paths are relative - to the installation prefix. - -``TEST`` - Scope may name zero or more existing tests. - See also the :command:`set_tests_properties` command. - -``CACHE`` - Scope must name zero or more cache existing entries. - -The required ``PROPERTY`` option is immediately followed by the name of -the property to set. Remaining arguments are used to compose the -property value in the form of a semicolon-separated list. - -If the ``APPEND`` option is given the list is appended to any existing -property value (except that empty values are ignored and not appended). -If the ``APPEND_STRING`` option is given the string is -appended to any existing property value as string, i.e. it results in a -longer string and not a list of strings. When using ``APPEND`` or -``APPEND_STRING`` with a property defined to support ``INHERITED`` -behavior (see :command:`define_property`), no inheriting occurs when -finding the initial value to append to. If the property is not already -directly set in the nominated scope, the command will behave as though -``APPEND`` or ``APPEND_STRING`` had not been given. - -See the :manual:`cmake-properties(7)` manual for a list of properties -in each scope.
diff --git a/share/cmake-3.18/Help/command/set_source_files_properties.rst b/share/cmake-3.18/Help/command/set_source_files_properties.rst deleted file mode 100644 index 9558b40..0000000 --- a/share/cmake-3.18/Help/command/set_source_files_properties.rst +++ /dev/null
@@ -1,37 +0,0 @@ -set_source_files_properties ---------------------------- - -Source files can have properties that affect how they are built. - -.. code-block:: cmake - - set_source_files_properties(<files> ... - [DIRECTORY <dirs> ...] - [TARGET_DIRECTORY <targets> ...] - PROPERTIES <prop1> <value1> - [<prop2> <value2>] ...) - -Sets properties associated with source files using a key/value paired -list. - -By default, source file properties are only visible to targets added in the -same directory (``CMakeLists.txt``). Visibility can be set in other directory -scopes using one or both of the following options: - -``DIRECTORY <dirs>...`` - The source file properties will be set in each of the ``<dirs>`` - directories' scopes. CMake must already know about each of these - source directories, either by having added them through a call to - :command:`add_subdirectory` or it being the top level source directory. - Relative paths are treated as relative to the current source directory. - -``TARGET_DIRECTORY <targets>...`` - The source file properties will be set in each of the directory scopes - where any of the specified ``<targets>`` were created (the ``<targets>`` - must therefore already exist). - -Use :command:`get_source_file_property` to get property values. -See also the :command:`set_property(SOURCE)` command. - -See :ref:`Source File Properties` for the list of properties known -to CMake.
diff --git a/share/cmake-3.18/Help/command/site_name.rst b/share/cmake-3.18/Help/command/site_name.rst deleted file mode 100644 index 1bcaead..0000000 --- a/share/cmake-3.18/Help/command/site_name.rst +++ /dev/null
@@ -1,8 +0,0 @@ -site_name ---------- - -Set the given variable to the name of the computer. - -.. code-block:: cmake - - site_name(variable)
diff --git a/share/cmake-3.18/Help/command/source_group.rst b/share/cmake-3.18/Help/command/source_group.rst deleted file mode 100644 index 5ae9e51..0000000 --- a/share/cmake-3.18/Help/command/source_group.rst +++ /dev/null
@@ -1,60 +0,0 @@ -source_group ------------- - -Define a grouping for source files in IDE project generation. -There are two different signatures to create source groups. - -.. code-block:: cmake - - source_group(<name> [FILES <src>...] [REGULAR_EXPRESSION <regex>]) - source_group(TREE <root> [PREFIX <prefix>] [FILES <src>...]) - -Defines a group into which sources will be placed in project files. -This is intended to set up file tabs in Visual Studio. -The options are: - -``TREE`` - CMake will automatically detect, from ``<src>`` files paths, source groups - it needs to create, to keep structure of source groups analogically to the - actual files and directories structure in the project. Paths of ``<src>`` - files will be cut to be relative to ``<root>``. - -``PREFIX`` - Source group and files located directly in ``<root>`` path, will be placed - in ``<prefix>`` source groups. - -``FILES`` - Any source file specified explicitly will be placed in group - ``<name>``. Relative paths are interpreted with respect to the - current source directory. - -``REGULAR_EXPRESSION`` - Any source file whose name matches the regular expression will - be placed in group ``<name>``. - -If a source file matches multiple groups, the *last* group that -explicitly lists the file with ``FILES`` will be favored, if any. -If no group explicitly lists the file, the *last* group whose -regular expression matches the file will be favored. - -The ``<name>`` of the group and ``<prefix>`` argument may contain forward -slashes or backslashes to specify subgroups. Backslashes need to be escaped -appropriately: - -.. code-block:: cmake - - source_group(base/subdir ...) - source_group(outer\\inner ...) - source_group(TREE <root> PREFIX sources\\inc ...) - -For backwards compatibility, the short-hand signature - -.. code-block:: cmake - - source_group(<name> <regex>) - -is equivalent to - -.. code-block:: cmake - - source_group(<name> REGULAR_EXPRESSION <regex>)
diff --git a/share/cmake-3.18/Help/command/string.rst b/share/cmake-3.18/Help/command/string.rst deleted file mode 100644 index cfcf914..0000000 --- a/share/cmake-3.18/Help/command/string.rst +++ /dev/null
@@ -1,472 +0,0 @@ -string ------- - -String operations. - -Synopsis -^^^^^^^^ - -.. parsed-literal:: - - `Search and Replace`_ - string(`FIND`_ <string> <substring> <out-var> [...]) - string(`REPLACE`_ <match-string> <replace-string> <out-var> <input>...) - string(`REGEX MATCH`_ <match-regex> <out-var> <input>...) - string(`REGEX MATCHALL`_ <match-regex> <out-var> <input>...) - string(`REGEX REPLACE`_ <match-regex> <replace-expr> <out-var> <input>...) - - `Manipulation`_ - string(`APPEND`_ <string-var> [<input>...]) - string(`PREPEND`_ <string-var> [<input>...]) - string(`CONCAT`_ <out-var> [<input>...]) - string(`JOIN`_ <glue> <out-var> [<input>...]) - string(`TOLOWER`_ <string> <out-var>) - string(`TOUPPER`_ <string> <out-var>) - string(`LENGTH`_ <string> <out-var>) - string(`SUBSTRING`_ <string> <begin> <length> <out-var>) - string(`STRIP`_ <string> <out-var>) - string(`GENEX_STRIP`_ <string> <out-var>) - string(`REPEAT`_ <string> <count> <out-var>) - - `Comparison`_ - string(`COMPARE`_ <op> <string1> <string2> <out-var>) - - `Hashing`_ - string(`\<HASH\> <HASH_>`_ <out-var> <input>) - - `Generation`_ - string(`ASCII`_ <number>... <out-var>) - string(`HEX`_ <string> <out-var>) - string(`CONFIGURE`_ <string> <out-var> [...]) - string(`MAKE_C_IDENTIFIER`_ <string> <out-var>) - string(`RANDOM`_ [<option>...] <out-var>) - string(`TIMESTAMP`_ <out-var> [<format string>] [UTC]) - string(`UUID`_ <out-var> ...) - -Search and Replace -^^^^^^^^^^^^^^^^^^ - -Search and Replace With Plain Strings -""""""""""""""""""""""""""""""""""""" - -.. _FIND: - -.. code-block:: cmake - - string(FIND <string> <substring> <output_variable> [REVERSE]) - -Return the position where the given ``<substring>`` was found in -the supplied ``<string>``. If the ``REVERSE`` flag was used, the command will -search for the position of the last occurrence of the specified -``<substring>``. If the ``<substring>`` is not found, a position of -1 is -returned. - -The ``string(FIND)`` subcommand treats all strings as ASCII-only characters. -The index stored in ``<output_variable>`` will also be counted in bytes, -so strings containing multi-byte characters may lead to unexpected results. - -.. _REPLACE: - -.. code-block:: cmake - - string(REPLACE <match_string> - <replace_string> <output_variable> - <input> [<input>...]) - -Replace all occurrences of ``<match_string>`` in the ``<input>`` -with ``<replace_string>`` and store the result in the ``<output_variable>``. - -Search and Replace With Regular Expressions -""""""""""""""""""""""""""""""""""""""""""" - -.. _`REGEX MATCH`: - -.. code-block:: cmake - - string(REGEX MATCH <regular_expression> - <output_variable> <input> [<input>...]) - -Match the ``<regular_expression>`` once and store the match in the -``<output_variable>``. -All ``<input>`` arguments are concatenated before matching. -Regular expressions are specified in the subsection just below. - -.. _`REGEX MATCHALL`: - -.. code-block:: cmake - - string(REGEX MATCHALL <regular_expression> - <output_variable> <input> [<input>...]) - -Match the ``<regular_expression>`` as many times as possible and store the -matches in the ``<output_variable>`` as a list. -All ``<input>`` arguments are concatenated before matching. - -.. _`REGEX REPLACE`: - -.. code-block:: cmake - - string(REGEX REPLACE <regular_expression> - <replacement_expression> <output_variable> - <input> [<input>...]) - -Match the ``<regular_expression>`` as many times as possible and substitute -the ``<replacement_expression>`` for the match in the output. -All ``<input>`` arguments are concatenated before matching. - -The ``<replacement_expression>`` may refer to parenthesis-delimited -subexpressions of the match using ``\1``, ``\2``, ..., ``\9``. Note that -two backslashes (``\\1``) are required in CMake code to get a backslash -through argument parsing. - -.. _`Regex Specification`: - -Regex Specification -""""""""""""""""""" - -The following characters have special meaning in regular expressions: - -``^`` - Matches at beginning of input -``$`` - Matches at end of input -``.`` - Matches any single character -``\<char>`` - Matches the single character specified by ``<char>``. Use this to - match special regex characters, e.g. ``\.`` for a literal ``.`` - or ``\\`` for a literal backslash ``\``. Escaping a non-special - character is unnecessary but allowed, e.g. ``\a`` matches ``a``. -``[ ]`` - Matches any character(s) inside the brackets -``[^ ]`` - Matches any character(s) not inside the brackets -``-`` - Inside brackets, specifies an inclusive range between - characters on either side e.g. ``[a-f]`` is ``[abcdef]`` - To match a literal ``-`` using brackets, make it the first - or the last character e.g. ``[+*/-]`` matches basic - mathematical operators. -``*`` - Matches preceding pattern zero or more times -``+`` - Matches preceding pattern one or more times -``?`` - Matches preceding pattern zero or once only -``|`` - Matches a pattern on either side of the ``|`` -``()`` - Saves a matched subexpression, which can be referenced - in the ``REGEX REPLACE`` operation. Additionally it is saved - by all regular expression-related commands, including - e.g. :command:`if(MATCHES)`, in the variables - :variable:`CMAKE_MATCH_<n>` for ``<n>`` 0..9. - -``*``, ``+`` and ``?`` have higher precedence than concatenation. ``|`` -has lower precedence than concatenation. This means that the regular -expression ``^ab+d$`` matches ``abbd`` but not ``ababd``, and the regular -expression ``^(ab|cd)$`` matches ``ab`` but not ``abd``. - -CMake language :ref:`Escape Sequences` such as ``\t``, ``\r``, ``\n``, -and ``\\`` may be used to construct literal tabs, carriage returns, -newlines, and backslashes (respectively) to pass in a regex. For example: - -* The quoted argument ``"[ \t\r\n]"`` specifies a regex that matches - any single whitespace character. -* The quoted argument ``"[/\\]"`` specifies a regex that matches - a single forward slash ``/`` or backslash ``\``. -* The quoted argument ``"[A-Za-z0-9_]"`` specifies a regex that matches - any single "word" character in the C locale. -* The quoted argument ``"\\(\\a\\+b\\)"`` specifies a regex that matches - the exact string ``(a+b)``. Each ``\\`` is parsed in a quoted argument - as just ``\``, so the regex itself is actually ``\(\a\+\b\)``. This - can alternatively be specified in a :ref:`bracket argument` without - having to escape the backslashes, e.g. ``[[\(\a\+\b\)]]``. - -Manipulation -^^^^^^^^^^^^ - -.. _APPEND: - -.. code-block:: cmake - - string(APPEND <string_variable> [<input>...]) - -Append all the ``<input>`` arguments to the string. - -.. _PREPEND: - -.. code-block:: cmake - - string(PREPEND <string_variable> [<input>...]) - -Prepend all the ``<input>`` arguments to the string. - -.. _CONCAT: - -.. code-block:: cmake - - string(CONCAT <output_variable> [<input>...]) - -Concatenate all the ``<input>`` arguments together and store -the result in the named ``<output_variable>``. - -.. _JOIN: - -.. code-block:: cmake - - string(JOIN <glue> <output_variable> [<input>...]) - -Join all the ``<input>`` arguments together using the ``<glue>`` -string and store the result in the named ``<output_variable>``. - -To join a list's elements, prefer to use the ``JOIN`` operator -from the :command:`list` command. This allows for the elements to have -special characters like ``;`` in them. - -.. _TOLOWER: - -.. code-block:: cmake - - string(TOLOWER <string> <output_variable>) - -Convert ``<string>`` to lower characters. - -.. _TOUPPER: - -.. code-block:: cmake - - string(TOUPPER <string> <output_variable>) - -Convert ``<string>`` to upper characters. - -.. _LENGTH: - -.. code-block:: cmake - - string(LENGTH <string> <output_variable>) - -Store in an ``<output_variable>`` a given string's length in bytes. -Note that this means if ``<string>`` contains multi-byte characters, the -result stored in ``<output_variable>`` will *not* be the number of characters. - -.. _SUBSTRING: - -.. code-block:: cmake - - string(SUBSTRING <string> <begin> <length> <output_variable>) - -Store in an ``<output_variable>`` a substring of a given ``<string>``. If -``<length>`` is ``-1`` the remainder of the string starting at ``<begin>`` -will be returned. If ``<string>`` is shorter than ``<length>`` then the -end of the string is used instead. - -Both ``<begin>`` and ``<length>`` are counted in bytes, so care must -be exercised if ``<string>`` could contain multi-byte characters. - -.. note:: - CMake 3.1 and below reported an error if ``<length>`` pointed past - the end of ``<string>``. - -.. _STRIP: - -.. code-block:: cmake - - string(STRIP <string> <output_variable>) - -Store in an ``<output_variable>`` a substring of a given ``<string>`` with -leading and trailing spaces removed. - -.. _GENEX_STRIP: - -.. code-block:: cmake - - string(GENEX_STRIP <string> <output_variable>) - -Strip any :manual:`generator expressions <cmake-generator-expressions(7)>` -from the input ``<string>`` and store the result in the ``<output_variable>``. - -.. _REPEAT: - -.. code-block:: cmake - - string(REPEAT <string> <count> <output_variable>) - -Produce the output string as the input ``<string>`` repeated ``<count>`` times. - -Comparison -^^^^^^^^^^ - -.. _COMPARE: - -.. code-block:: cmake - - string(COMPARE LESS <string1> <string2> <output_variable>) - string(COMPARE GREATER <string1> <string2> <output_variable>) - string(COMPARE EQUAL <string1> <string2> <output_variable>) - string(COMPARE NOTEQUAL <string1> <string2> <output_variable>) - string(COMPARE LESS_EQUAL <string1> <string2> <output_variable>) - string(COMPARE GREATER_EQUAL <string1> <string2> <output_variable>) - -Compare the strings and store true or false in the ``<output_variable>``. - -.. _`Supported Hash Algorithms`: - -Hashing -^^^^^^^ - -.. _`HASH`: - -.. code-block:: cmake - - string(<HASH> <output_variable> <input>) - -Compute a cryptographic hash of the ``<input>`` string. -The supported ``<HASH>`` algorithm names are: - -``MD5`` - Message-Digest Algorithm 5, RFC 1321. -``SHA1`` - US Secure Hash Algorithm 1, RFC 3174. -``SHA224`` - US Secure Hash Algorithms, RFC 4634. -``SHA256`` - US Secure Hash Algorithms, RFC 4634. -``SHA384`` - US Secure Hash Algorithms, RFC 4634. -``SHA512`` - US Secure Hash Algorithms, RFC 4634. -``SHA3_224`` - Keccak SHA-3. -``SHA3_256`` - Keccak SHA-3. -``SHA3_384`` - Keccak SHA-3. -``SHA3_512`` - Keccak SHA-3. - -Generation -^^^^^^^^^^ - -.. _ASCII: - -.. code-block:: cmake - - string(ASCII <number> [<number> ...] <output_variable>) - -Convert all numbers into corresponding ASCII characters. - -.. _HEX: - -.. code-block:: cmake - - string(HEX <string> <output_variable>) - -Convert each byte in the input ``<string>`` to its hexadecimal representation -and store the concatenated hex digits in the ``<output_variable>``. Letters in -the output (``a`` through ``f``) are in lowercase. - -.. _CONFIGURE: - -.. code-block:: cmake - - string(CONFIGURE <string> <output_variable> - [@ONLY] [ESCAPE_QUOTES]) - -Transform a ``<string>`` like :command:`configure_file` transforms a file. - -.. _MAKE_C_IDENTIFIER: - -.. code-block:: cmake - - string(MAKE_C_IDENTIFIER <string> <output_variable>) - -Convert each non-alphanumeric character in the input ``<string>`` to an -underscore and store the result in the ``<output_variable>``. If the first -character of the ``<string>`` is a digit, an underscore will also be prepended -to the result. - -.. _RANDOM: - -.. code-block:: cmake - - string(RANDOM [LENGTH <length>] [ALPHABET <alphabet>] - [RANDOM_SEED <seed>] <output_variable>) - -Return a random string of given ``<length>`` consisting of -characters from the given ``<alphabet>``. Default length is 5 characters -and default alphabet is all numbers and upper and lower case letters. -If an integer ``RANDOM_SEED`` is given, its value will be used to seed the -random number generator. - -.. _TIMESTAMP: - -.. code-block:: cmake - - string(TIMESTAMP <output_variable> [<format_string>] [UTC]) - -Write a string representation of the current date -and/or time to the ``<output_variable>``. - -If the command is unable to obtain a timestamp, the ``<output_variable>`` -will be set to the empty string ``""``. - -The optional ``UTC`` flag requests the current date/time representation to -be in Coordinated Universal Time (UTC) rather than local time. - -The optional ``<format_string>`` may contain the following format -specifiers: - -:: - - %% A literal percent sign (%). - %d The day of the current month (01-31). - %H The hour on a 24-hour clock (00-23). - %I The hour on a 12-hour clock (01-12). - %j The day of the current year (001-366). - %m The month of the current year (01-12). - %b Abbreviated month name (e.g. Oct). - %B Full month name (e.g. October). - %M The minute of the current hour (00-59). - %s Seconds since midnight (UTC) 1-Jan-1970 (UNIX time). - %S The second of the current minute. - 60 represents a leap second. (00-60) - %U The week number of the current year (00-53). - %w The day of the current week. 0 is Sunday. (0-6) - %a Abbreviated weekday name (e.g. Fri). - %A Full weekday name (e.g. Friday). - %y The last two digits of the current year (00-99) - %Y The current year. - -Unknown format specifiers will be ignored and copied to the output -as-is. - -If no explicit ``<format_string>`` is given, it will default to: - -:: - - %Y-%m-%dT%H:%M:%S for local time. - %Y-%m-%dT%H:%M:%SZ for UTC. - -.. note:: - - If the ``SOURCE_DATE_EPOCH`` environment variable is set, - its value will be used instead of the current time. - See https://reproducible-builds.org/specs/source-date-epoch/ for details. - -.. _UUID: - -.. code-block:: cmake - - string(UUID <output_variable> NAMESPACE <namespace> NAME <name> - TYPE <MD5|SHA1> [UPPER]) - -Create a universally unique identifier (aka GUID) as per RFC4122 -based on the hash of the combined values of ``<namespace>`` -(which itself has to be a valid UUID) and ``<name>``. -The hash algorithm can be either ``MD5`` (Version 3 UUID) or -``SHA1`` (Version 5 UUID). -A UUID has the format ``xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`` -where each ``x`` represents a lower case hexadecimal character. -Where required, an uppercase representation can be requested -with the optional ``UPPER`` flag.
diff --git a/share/cmake-3.18/Help/command/target_compile_definitions.rst b/share/cmake-3.18/Help/command/target_compile_definitions.rst deleted file mode 100644 index 9e9c690..0000000 --- a/share/cmake-3.18/Help/command/target_compile_definitions.rst +++ /dev/null
@@ -1,39 +0,0 @@ -target_compile_definitions --------------------------- - -Add compile definitions to a target. - -.. code-block:: cmake - - target_compile_definitions(<target> - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -Specifies compile definitions to use when compiling a given ``<target>``. The -named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` -items will populate the :prop_tgt:`COMPILE_DEFINITIONS` property of -``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_COMPILE_DEFINITIONS` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -The following arguments specify compile definitions. Repeated calls for the -same ``<target>`` append items in the order called. - -Arguments to ``target_compile_definitions`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -Any leading ``-D`` on an item will be removed. Empty items are ignored. -For example, the following are all equivalent: - -.. code-block:: cmake - - target_compile_definitions(foo PUBLIC FOO) - target_compile_definitions(foo PUBLIC -DFOO) # -D removed - target_compile_definitions(foo PUBLIC "" FOO) # "" ignored - target_compile_definitions(foo PUBLIC -D FOO) # -D becomes "", then ignored
diff --git a/share/cmake-3.18/Help/command/target_compile_features.rst b/share/cmake-3.18/Help/command/target_compile_features.rst deleted file mode 100644 index c5401e6..0000000 --- a/share/cmake-3.18/Help/command/target_compile_features.rst +++ /dev/null
@@ -1,33 +0,0 @@ -target_compile_features ------------------------ - -Add expected compiler features to a target. - -.. code-block:: cmake - - target_compile_features(<target> <PRIVATE|PUBLIC|INTERFACE> <feature> [...]) - -Specifies compiler features required when compiling a given target. If the -feature is not listed in the :variable:`CMAKE_C_COMPILE_FEATURES`, -:variable:`CMAKE_CUDA_COMPILE_FEATURES`, or :variable:`CMAKE_CXX_COMPILE_FEATURES` -variables, then an error will be reported by CMake. If the use of the feature requires -an additional compiler flag, such as ``-std=gnu++11``, the flag will be added -automatically. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the features. ``PRIVATE`` and ``PUBLIC`` items will -populate the :prop_tgt:`COMPILE_FEATURES` property of ``<target>``. -``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_COMPILE_FEATURES` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -Repeated calls for the same ``<target>`` append items. - -The named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -Arguments to ``target_compile_features`` may use "generator expressions" -with the syntax ``$<...>``. -See the :manual:`cmake-generator-expressions(7)` manual for available -expressions. See the :manual:`cmake-compile-features(7)` manual for -information on compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/command/target_compile_options.rst b/share/cmake-3.18/Help/command/target_compile_options.rst deleted file mode 100644 index 3c733c5..0000000 --- a/share/cmake-3.18/Help/command/target_compile_options.rst +++ /dev/null
@@ -1,50 +0,0 @@ -target_compile_options ----------------------- - -Add compile options to a target. - -.. code-block:: cmake - - target_compile_options(<target> [BEFORE] - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -Adds options to the :prop_tgt:`COMPILE_OPTIONS` or -:prop_tgt:`INTERFACE_COMPILE_OPTIONS` target properties. These options -are used when compiling the given ``<target>``, which must have been -created by a command such as :command:`add_executable` or -:command:`add_library` and must not be an :ref:`ALIAS target <Alias Targets>`. - -Arguments -^^^^^^^^^ - -If ``BEFORE`` is specified, the content will be prepended to the property -instead of being appended. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` -items will populate the :prop_tgt:`COMPILE_OPTIONS` property of -``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_COMPILE_OPTIONS` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -The following arguments specify compile options. Repeated calls for the same -``<target>`` append items in the order called. - -Arguments to ``target_compile_options`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -.. include:: OPTIONS_SHELL.txt - -See Also -^^^^^^^^ - -This command can be used to add any options. However, for adding -preprocessor definitions and include directories it is recommended -to use the more specific commands :command:`target_compile_definitions` -and :command:`target_include_directories`. - -For directory-wide settings, there is the command :command:`add_compile_options`. - -For file-specific settings, there is the source file property :prop_sf:`COMPILE_OPTIONS`.
diff --git a/share/cmake-3.18/Help/command/target_include_directories.rst b/share/cmake-3.18/Help/command/target_include_directories.rst deleted file mode 100644 index 660e15c..0000000 --- a/share/cmake-3.18/Help/command/target_include_directories.rst +++ /dev/null
@@ -1,62 +0,0 @@ -target_include_directories --------------------------- - -Add include directories to a target. - -.. code-block:: cmake - - target_include_directories(<target> [SYSTEM] [BEFORE] - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -Specifies include directories to use when compiling a given target. -The named ``<target>`` must have been created by a command such -as :command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -If ``BEFORE`` is specified, the content will be prepended to the property -instead of being appended. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to specify -the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` items will -populate the :prop_tgt:`INCLUDE_DIRECTORIES` property of ``<target>``. -``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -The following arguments specify include directories. - -Specified include directories may be absolute paths or relative paths. -Repeated calls for the same <target> append items in the order called. If -``SYSTEM`` is specified, the compiler will be told the -directories are meant as system include directories on some platforms -(signalling this setting might achieve effects such as the compiler -skipping warnings, or these fixed-install system files not being -considered in dependency calculations - see compiler docs). If ``SYSTEM`` -is used together with ``PUBLIC`` or ``INTERFACE``, the -:prop_tgt:`INTERFACE_SYSTEM_INCLUDE_DIRECTORIES` target property will be -populated with the specified directories. - -Arguments to ``target_include_directories`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -Include directories usage requirements commonly differ between the build-tree -and the install-tree. The ``BUILD_INTERFACE`` and ``INSTALL_INTERFACE`` -generator expressions can be used to describe separate usage requirements -based on the usage location. Relative paths are allowed within the -``INSTALL_INTERFACE`` expression and are interpreted relative to the -installation prefix. For example: - -.. code-block:: cmake - - target_include_directories(mylib PUBLIC - $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include/mylib> - $<INSTALL_INTERFACE:include/mylib> # <prefix>/include/mylib - ) - -Creating Relocatable Packages -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. |INTERFACE_PROPERTY_LINK| replace:: :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` -.. include:: /include/INTERFACE_INCLUDE_DIRECTORIES_WARNING.txt
diff --git a/share/cmake-3.18/Help/command/target_link_directories.rst b/share/cmake-3.18/Help/command/target_link_directories.rst deleted file mode 100644 index 76da94d..0000000 --- a/share/cmake-3.18/Help/command/target_link_directories.rst +++ /dev/null
@@ -1,55 +0,0 @@ -target_link_directories ------------------------ - -Add link directories to a target. - -.. code-block:: cmake - - target_link_directories(<target> [BEFORE] - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -Specifies the paths in which the linker should search for libraries when -linking a given target. Each item can be an absolute or relative path, -with the latter being interpreted as relative to the current source -directory. These items will be added to the link command. - -The named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the items that follow them. ``PRIVATE`` and -``PUBLIC`` items will populate the :prop_tgt:`LINK_DIRECTORIES` property -of ``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_LINK_DIRECTORIES` property of ``<target>`` -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items). -Each item specifies a link directory and will be converted to an absolute -path if necessary before adding it to the relevant property. Repeated -calls for the same ``<target>`` append items in the order called. - -If ``BEFORE`` is specified, the content will be prepended to the relevant -property instead of being appended. - -Arguments to ``target_link_directories`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -.. note:: - - This command is rarely necessary and should be avoided where there are - other choices. Prefer to pass full absolute paths to libraries where - possible, since this ensures the correct library will always be linked. - The :command:`find_library` command provides the full path, which can - generally be used directly in calls to :command:`target_link_libraries`. - Situations where a library search path may be needed include: - - - Project generators like Xcode where the user can switch target - architecture at build time, but a full path to a library cannot - be used because it only provides one architecture (i.e. it is not - a universal binary). - - Libraries may themselves have other private library dependencies - that expect to be found via ``RPATH`` mechanisms, but some linkers - are not able to fully decode those paths (e.g. due to the presence - of things like ``$ORIGIN``).
diff --git a/share/cmake-3.18/Help/command/target_link_libraries.rst b/share/cmake-3.18/Help/command/target_link_libraries.rst deleted file mode 100644 index c2e7e8a..0000000 --- a/share/cmake-3.18/Help/command/target_link_libraries.rst +++ /dev/null
@@ -1,310 +0,0 @@ -target_link_libraries ---------------------- - -.. only:: html - - .. contents:: - -Specify libraries or flags to use when linking a given target and/or -its dependents. :ref:`Usage requirements <Target Usage Requirements>` -from linked library targets will be propagated. Usage requirements -of a target's dependencies affect compilation of its own sources. - -Overview -^^^^^^^^ - -This command has several signatures as detailed in subsections below. -All of them have the general form - -.. code-block:: cmake - - target_link_libraries(<target> ... <item>... ...) - -The named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. If policy :policy:`CMP0079` is not -set to ``NEW`` then the target must have been created in the current -directory. Repeated calls for the same ``<target>`` append items in -the order called. - -Each ``<item>`` may be: - -* **A library target name**: The generated link line will have the - full path to the linkable library file associated with the target. - The buildsystem will have a dependency to re-link ``<target>`` if - the library file changes. - - The named target must be created by :command:`add_library` within - the project or as an :ref:`IMPORTED library <Imported Targets>`. - If it is created within the project an ordering dependency will - automatically be added in the build system to make sure the named - library target is up-to-date before the ``<target>`` links. - - If an imported library has the :prop_tgt:`IMPORTED_NO_SONAME` - target property set, CMake may ask the linker to search for - the library instead of using the full path - (e.g. ``/usr/lib/libfoo.so`` becomes ``-lfoo``). - - The full path to the target's artifact will be quoted/escaped for - the shell automatically. - -* **A full path to a library file**: The generated link line will - normally preserve the full path to the file. The buildsystem will - have a dependency to re-link ``<target>`` if the library file changes. - - There are some cases where CMake may ask the linker to search for - the library (e.g. ``/usr/lib/libfoo.so`` becomes ``-lfoo``), such - as when a shared library is detected to have no ``SONAME`` field. - See policy :policy:`CMP0060` for discussion of another case. - - If the library file is in a macOS framework, the ``Headers`` directory - of the framework will also be processed as a - :ref:`usage requirement <Target Usage Requirements>`. This has the same - effect as passing the framework directory as an include directory. - - On :ref:`Visual Studio Generators` for VS 2010 and above, library files - ending in ``.targets`` will be treated as MSBuild targets files and - imported into generated project files. This is not supported by other - generators. - - The full path to the library file will be quoted/escaped for - the shell automatically. - -* **A plain library name**: The generated link line will ask the linker - to search for the library (e.g. ``foo`` becomes ``-lfoo`` or ``foo.lib``). - - The library name/flag is treated as a command-line string fragment and - will be used with no extra quoting or escaping. - -* **A link flag**: Item names starting with ``-``, but not ``-l`` or - ``-framework``, are treated as linker flags. Note that such flags will - be treated like any other library link item for purposes of transitive - dependencies, so they are generally safe to specify only as private link - items that will not propagate to dependents. - - Link flags specified here are inserted into the link command in the same - place as the link libraries. This might not be correct, depending on - the linker. Use the :prop_tgt:`LINK_OPTIONS` target property or - :command:`target_link_options` command to add link - flags explicitly. The flags will then be placed at the toolchain-defined - flag position in the link command. - - The link flag is treated as a command-line string fragment and - will be used with no extra quoting or escaping. - -* **A generator expression**: A ``$<...>`` :manual:`generator expression - <cmake-generator-expressions(7)>` may evaluate to any of the above - items or to a :ref:`semicolon-separated list <CMake Language Lists>` of them. - If the ``...`` contains any ``;`` characters, e.g. after evaluation - of a ``${list}`` variable, be sure to use an explicitly quoted - argument ``"$<...>"`` so that this command receives it as a - single ``<item>``. - - Additionally, a generator expression may be used as a fragment of - any of the above items, e.g. ``foo$<1:_d>``. - - Note that generator expressions will not be used in OLD handling of - policy :policy:`CMP0003` or policy :policy:`CMP0004`. - -* A ``debug``, ``optimized``, or ``general`` keyword immediately followed - by another ``<item>``. The item following such a keyword will be used - only for the corresponding build configuration. The ``debug`` keyword - corresponds to the ``Debug`` configuration (or to configurations named - in the :prop_gbl:`DEBUG_CONFIGURATIONS` global property if it is set). - The ``optimized`` keyword corresponds to all other configurations. The - ``general`` keyword corresponds to all configurations, and is purely - optional. Higher granularity may be achieved for per-configuration - rules by creating and linking to - :ref:`IMPORTED library targets <Imported Targets>`. - These keywords are interpreted immediately by this command and therefore - have no special meaning when produced by a generator expression. - -Items containing ``::``, such as ``Foo::Bar``, are assumed to be -:ref:`IMPORTED <Imported Targets>` or :ref:`ALIAS <Alias Targets>` library -target names and will cause an error if no such target exists. -See policy :policy:`CMP0028`. - -See the :manual:`cmake-buildsystem(7)` manual for more on defining -buildsystem properties. - -Libraries for a Target and/or its Dependents -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - target_link_libraries(<target> - <PRIVATE|PUBLIC|INTERFACE> <item>... - [<PRIVATE|PUBLIC|INTERFACE> <item>...]...) - -The ``PUBLIC``, ``PRIVATE`` and ``INTERFACE`` keywords can be used to -specify both the link dependencies and the link interface in one command. -Libraries and targets following ``PUBLIC`` are linked to, and are made -part of the link interface. Libraries and targets following ``PRIVATE`` -are linked to, but are not made part of the link interface. Libraries -following ``INTERFACE`` are appended to the link interface and are not -used for linking ``<target>``. - -Libraries for both a Target and its Dependents -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - target_link_libraries(<target> <item>...) - -Library dependencies are transitive by default with this signature. -When this target is linked into another target then the libraries -linked to this target will appear on the link line for the other -target too. This transitive "link interface" is stored in the -:prop_tgt:`INTERFACE_LINK_LIBRARIES` target property and may be overridden -by setting the property directly. When :policy:`CMP0022` is not set to -``NEW``, transitive linking is built in but may be overridden by the -:prop_tgt:`LINK_INTERFACE_LIBRARIES` property. Calls to other signatures -of this command may set the property making any libraries linked -exclusively by this signature private. - -Libraries for a Target and/or its Dependents (Legacy) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - target_link_libraries(<target> - <LINK_PRIVATE|LINK_PUBLIC> <lib>... - [<LINK_PRIVATE|LINK_PUBLIC> <lib>...]...) - -The ``LINK_PUBLIC`` and ``LINK_PRIVATE`` modes can be used to specify both -the link dependencies and the link interface in one command. - -This signature is for compatibility only. Prefer the ``PUBLIC`` or -``PRIVATE`` keywords instead. - -Libraries and targets following ``LINK_PUBLIC`` are linked to, and are -made part of the :prop_tgt:`INTERFACE_LINK_LIBRARIES`. If policy -:policy:`CMP0022` is not ``NEW``, they are also made part of the -:prop_tgt:`LINK_INTERFACE_LIBRARIES`. Libraries and targets following -``LINK_PRIVATE`` are linked to, but are not made part of the -:prop_tgt:`INTERFACE_LINK_LIBRARIES` (or :prop_tgt:`LINK_INTERFACE_LIBRARIES`). - -Libraries for Dependents Only (Legacy) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - target_link_libraries(<target> LINK_INTERFACE_LIBRARIES <item>...) - -The ``LINK_INTERFACE_LIBRARIES`` mode appends the libraries to the -:prop_tgt:`INTERFACE_LINK_LIBRARIES` target property instead of using them -for linking. If policy :policy:`CMP0022` is not ``NEW``, then this mode -also appends libraries to the :prop_tgt:`LINK_INTERFACE_LIBRARIES` and its -per-configuration equivalent. - -This signature is for compatibility only. Prefer the ``INTERFACE`` mode -instead. - -Libraries specified as ``debug`` are wrapped in a generator expression to -correspond to debug builds. If policy :policy:`CMP0022` is -not ``NEW``, the libraries are also appended to the -:prop_tgt:`LINK_INTERFACE_LIBRARIES_DEBUG <LINK_INTERFACE_LIBRARIES_<CONFIG>>` -property (or to the properties corresponding to configurations listed in -the :prop_gbl:`DEBUG_CONFIGURATIONS` global property if it is set). -Libraries specified as ``optimized`` are appended to the -:prop_tgt:`INTERFACE_LINK_LIBRARIES` property. If policy :policy:`CMP0022` -is not ``NEW``, they are also appended to the -:prop_tgt:`LINK_INTERFACE_LIBRARIES` property. Libraries specified as -``general`` (or without any keyword) are treated as if specified for both -``debug`` and ``optimized``. - -Linking Object Libraries -^^^^^^^^^^^^^^^^^^^^^^^^ - -:ref:`Object Libraries` may be used as the ``<target>`` (first) argument -of ``target_link_libraries`` to specify dependencies of their sources -on other libraries. For example, the code - -.. code-block:: cmake - - add_library(A SHARED a.c) - target_compile_definitions(A PUBLIC A) - - add_library(obj OBJECT obj.c) - target_compile_definitions(obj PUBLIC OBJ) - target_link_libraries(obj PUBLIC A) - -compiles ``obj.c`` with ``-DA -DOBJ`` and establishes usage requirements -for ``obj`` that propagate to its dependents. - -Normal libraries and executables may link to :ref:`Object Libraries` -to get their objects and usage requirements. Continuing the above -example, the code - -.. code-block:: cmake - - add_library(B SHARED b.c) - target_link_libraries(B PUBLIC obj) - -compiles ``b.c`` with ``-DA -DOBJ``, creates shared library ``B`` -with object files from ``b.c`` and ``obj.c``, and links ``B`` to ``A``. -Furthermore, the code - -.. code-block:: cmake - - add_executable(main main.c) - target_link_libraries(main B) - -compiles ``main.c`` with ``-DA -DOBJ`` and links executable ``main`` -to ``B`` and ``A``. The object library's usage requirements are -propagated transitively through ``B``, but its object files are not. - -:ref:`Object Libraries` may "link" to other object libraries to get -usage requirements, but since they do not have a link step nothing -is done with their object files. Continuing from the above example, -the code: - -.. code-block:: cmake - - add_library(obj2 OBJECT obj2.c) - target_link_libraries(obj2 PUBLIC obj) - - add_executable(main2 main2.c) - target_link_libraries(main2 obj2) - -compiles ``obj2.c`` with ``-DA -DOBJ``, creates executable ``main2`` -with object files from ``main2.c`` and ``obj2.c``, and links ``main2`` -to ``A``. - -In other words, when :ref:`Object Libraries` appear in a target's -:prop_tgt:`INTERFACE_LINK_LIBRARIES` property they will be -treated as :ref:`Interface Libraries`, but when they appear in -a target's :prop_tgt:`LINK_LIBRARIES` property their object files -will be included in the link too. - -Cyclic Dependencies of Static Libraries -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The library dependency graph is normally acyclic (a DAG), but in the case -of mutually-dependent ``STATIC`` libraries CMake allows the graph to -contain cycles (strongly connected components). When another target links -to one of the libraries, CMake repeats the entire connected component. -For example, the code - -.. code-block:: cmake - - add_library(A STATIC a.c) - add_library(B STATIC b.c) - target_link_libraries(A B) - target_link_libraries(B A) - add_executable(main main.c) - target_link_libraries(main A) - -links ``main`` to ``A B A B``. While one repetition is usually -sufficient, pathological object file and symbol arrangements can require -more. One may handle such cases by using the -:prop_tgt:`LINK_INTERFACE_MULTIPLICITY` target property or by manually -repeating the component in the last ``target_link_libraries`` call. -However, if two archives are really so interdependent they should probably -be combined into a single archive, perhaps by using :ref:`Object Libraries`. - -Creating Relocatable Packages -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. |INTERFACE_PROPERTY_LINK| replace:: :prop_tgt:`INTERFACE_LINK_LIBRARIES` -.. include:: /include/INTERFACE_LINK_LIBRARIES_WARNING.txt
diff --git a/share/cmake-3.18/Help/command/target_link_options.rst b/share/cmake-3.18/Help/command/target_link_options.rst deleted file mode 100644 index 89038e3..0000000 --- a/share/cmake-3.18/Help/command/target_link_options.rst +++ /dev/null
@@ -1,50 +0,0 @@ -target_link_options -------------------- - -Add options to the link step for an executable, shared library or module -library target. - -.. code-block:: cmake - - target_link_options(<target> [BEFORE] - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -The named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -This command can be used to add any link options, but alternative commands -exist to add libraries (:command:`target_link_libraries` or -:command:`link_libraries`). See documentation of the -:prop_dir:`directory <LINK_OPTIONS>` and -:prop_tgt:`target <LINK_OPTIONS>` ``LINK_OPTIONS`` properties. - -.. note:: - - This command cannot be used to add options for static library targets, - since they do not use a linker. To add archiver or MSVC librarian flags, - see the :prop_tgt:`STATIC_LIBRARY_OPTIONS` target property. - -If ``BEFORE`` is specified, the content will be prepended to the property -instead of being appended. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` -items will populate the :prop_tgt:`LINK_OPTIONS` property of -``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_LINK_OPTIONS` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -The following arguments specify link options. Repeated calls for the same -``<target>`` append items in the order called. - -Arguments to ``target_link_options`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -.. include:: DEVICE_LINK_OPTIONS.txt - -.. include:: OPTIONS_SHELL.txt - -.. include:: LINK_OPTIONS_LINKER.txt
diff --git a/share/cmake-3.18/Help/command/target_precompile_headers.rst b/share/cmake-3.18/Help/command/target_precompile_headers.rst deleted file mode 100644 index d4280b1..0000000 --- a/share/cmake-3.18/Help/command/target_precompile_headers.rst +++ /dev/null
@@ -1,123 +0,0 @@ -target_precompile_headers -------------------------- - -Add a list of header files to precompile. - -Precompiling header files can speed up compilation by creating a partially -processed version of some header files, and then using that version during -compilations rather than repeatedly parsing the original headers. - -Main Form -^^^^^^^^^ - -.. code-block:: cmake - - target_precompile_headers(<target> - <INTERFACE|PUBLIC|PRIVATE> [header1...] - [<INTERFACE|PUBLIC|PRIVATE> [header2...] ...]) - -The command adds header files to the :prop_tgt:`PRECOMPILE_HEADERS` and/or -:prop_tgt:`INTERFACE_PRECOMPILE_HEADERS` target properties of ``<target>``. -The named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` -items will populate the :prop_tgt:`PRECOMPILE_HEADERS` property of -``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_PRECOMPILE_HEADERS` property of ``<target>`` -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items). -Repeated calls for the same ``<target>`` will append items in the order called. - -Projects should generally avoid using ``PUBLIC`` or ``INTERFACE`` for targets -that will be :ref:`exported <install(EXPORT)>`, or they should at least use -the ``$<BUILD_INTERFACE:...>`` generator expression to prevent precompile -headers from appearing in an installed exported target. Consumers of a target -should typically be in control of what precompile headers they use, not have -precompile headers forced on them by the targets being consumed (since -precompile headers are not typically usage requirements). A notable exception -to this is where an :ref:`interface library <Interface Libraries>` is created -to define a commonly used set of precompile headers in one place and then other -targets link to that interface library privately. In this case, the interface -library exists specifically to propagate the precompile headers to its -consumers and the consumer is effectively still in control, since it decides -whether to link to the interface library or not. - -The list of header files is used to generate a header file named -``cmake_pch.h|xx`` which is used to generate the precompiled header file -(``.pch``, ``.gch``, ``.pchi``) artifact. The ``cmake_pch.h|xx`` header -file will be force included (``-include`` for GCC, ``/FI`` for MSVC) to -all source files, so sources do not need to have ``#include "pch.h"``. - -Header file names specified with angle brackets (e.g. ``<unordered_map>``) or -explicit double quotes (escaped for the :manual:`cmake-language(7)`, -e.g. ``[["other_header.h"]]``) will be treated as is, and include directories -must be available for the compiler to find them. Other header file names -(e.g. ``project_header.h``) are interpreted as being relative to the current -source directory (e.g. :variable:`CMAKE_CURRENT_SOURCE_DIR`) and will be -included by absolute path. For example: - -.. code-block:: cmake - - target_precompile_headers(myTarget - PUBLIC - project_header.h - PRIVATE - [["other_header.h"]] - <unordered_map> - ) - -Arguments to ``target_precompile_headers()`` may use "generator expressions" -with the syntax ``$<...>``. -See the :manual:`cmake-generator-expressions(7)` manual for available -expressions. -The ``$<COMPILE_LANGUAGE:...>`` generator expression is particularly -useful for specifying a language-specific header to precompile for -only one language (e.g. ``CXX`` and not ``C``). In this case, header -file names that are not explicitly in double quotes or angle brackets -must be specified by absolute path. Also, when specifying angle brackets -inside a generator expression, be sure to encode the closing ``>`` as -``$<ANGLE-R>``. For example: - -.. code-block:: cmake - - target_precompile_headers(mylib PRIVATE - "$<$<COMPILE_LANGUAGE:CXX>:${CMAKE_CURRENT_SOURCE_DIR}/cxx_only.h>" - "$<$<COMPILE_LANGUAGE:C>:<stddef.h$<ANGLE-R>>" - "$<$<COMPILE_LANGUAGE:CXX>:<cstddef$<ANGLE-R>>" - ) - - -Reusing Precompile Headers -^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The command also supports a second signature which can be used to specify that -one target re-uses a precompiled header file artifact from another target -instead of generating its own: - -.. code-block:: cmake - - target_precompile_headers(<target> REUSE_FROM <other_target>) - -This form sets the :prop_tgt:`PRECOMPILE_HEADERS_REUSE_FROM` property to -``<other_target>`` and adds a dependency such that ``<target>`` will depend -on ``<other_target>``. CMake will halt with an error if the -:prop_tgt:`PRECOMPILE_HEADERS` property of ``<target>`` is already set when -the ``REUSE_FROM`` form is used. - -.. note:: - - The ``REUSE_FROM`` form requires the same set of compiler options, - compiler flags and compiler definitions for both ``<target>`` and - ``<other_target>``. Some compilers (e.g. GCC) may issue a warning if the - precompiled header file cannot be used (``-Winvalid-pch``). - -See Also -^^^^^^^^ - -To disable precompile headers for specific targets, see the -:prop_tgt:`DISABLE_PRECOMPILE_HEADERS` target property. - -To prevent precompile headers from being used when compiling a specific -source file, see the :prop_sf:`SKIP_PRECOMPILE_HEADERS` source file property.
diff --git a/share/cmake-3.18/Help/command/target_sources.rst b/share/cmake-3.18/Help/command/target_sources.rst deleted file mode 100644 index 27e737b..0000000 --- a/share/cmake-3.18/Help/command/target_sources.rst +++ /dev/null
@@ -1,34 +0,0 @@ -target_sources --------------- - -Add sources to a target. - -.. code-block:: cmake - - target_sources(<target> - <INTERFACE|PUBLIC|PRIVATE> [items1...] - [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...]) - -Specifies sources to use when compiling a given target. Relative -source file paths are interpreted as being relative to the current -source directory (i.e. :variable:`CMAKE_CURRENT_SOURCE_DIR`). The -named ``<target>`` must have been created by a command such as -:command:`add_executable` or :command:`add_library` and must not be an -:ref:`ALIAS target <Alias Targets>`. - -The ``INTERFACE``, ``PUBLIC`` and ``PRIVATE`` keywords are required to -specify the scope of the following arguments. ``PRIVATE`` and ``PUBLIC`` -items will populate the :prop_tgt:`SOURCES` property of -``<target>``. ``PUBLIC`` and ``INTERFACE`` items will populate the -:prop_tgt:`INTERFACE_SOURCES` property of ``<target>``. -(:ref:`IMPORTED targets <Imported Targets>` only support ``INTERFACE`` items.) -The following arguments specify sources. Repeated calls for the same -``<target>`` append items in the order called. - -Arguments to ``target_sources`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. - -See also the :policy:`CMP0076` policy for older behavior related to the -handling of relative source file paths.
diff --git a/share/cmake-3.18/Help/command/try_compile.rst b/share/cmake-3.18/Help/command/try_compile.rst deleted file mode 100644 index 323077a..0000000 --- a/share/cmake-3.18/Help/command/try_compile.rst +++ /dev/null
@@ -1,192 +0,0 @@ -try_compile ------------ - -.. only:: html - - .. contents:: - -Try building some code. - -Try Compiling Whole Projects -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - try_compile(<resultVar> <bindir> <srcdir> - <projectName> [<targetName>] [CMAKE_FLAGS <flags>...] - [OUTPUT_VARIABLE <var>]) - -Try building a project. The success or failure of the ``try_compile``, -i.e. ``TRUE`` or ``FALSE`` respectively, is returned in ``<resultVar>``. - -In this form, ``<srcdir>`` should contain a complete CMake project with a -``CMakeLists.txt`` file and all sources. The ``<bindir>`` and ``<srcdir>`` -will not be deleted after this command is run. Specify ``<targetName>`` to -build a specific target instead of the ``all`` or ``ALL_BUILD`` target. See -below for the meaning of other options. - -Try Compiling Source Files -^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - try_compile(<resultVar> <bindir> <srcfile|SOURCES srcfile...> - [CMAKE_FLAGS <flags>...] - [COMPILE_DEFINITIONS <defs>...] - [LINK_OPTIONS <options>...] - [LINK_LIBRARIES <libs>...] - [OUTPUT_VARIABLE <var>] - [COPY_FILE <fileName> [COPY_FILE_ERROR <var>]] - [<LANG>_STANDARD <std>] - [<LANG>_STANDARD_REQUIRED <bool>] - [<LANG>_EXTENSIONS <bool>] - ) - -Try building an executable or static library from one or more source files -(which one is determined by the :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` -variable). The success or failure of the ``try_compile``, i.e. ``TRUE`` or -``FALSE`` respectively, is returned in ``<resultVar>``. - -In this form, one or more source files must be provided. If -:variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` is unset or is set to ``EXECUTABLE``, -the sources must include a definition for ``main`` and CMake will create a -``CMakeLists.txt`` file to build the source(s) as an executable. -If :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` is set to ``STATIC_LIBRARY``, -a static library will be built instead and no definition for ``main`` is -required. For an executable, the generated ``CMakeLists.txt`` file would -contain something like the following: - -.. code-block:: cmake - - add_definitions(<expanded COMPILE_DEFINITIONS from caller>) - include_directories(${INCLUDE_DIRECTORIES}) - link_directories(${LINK_DIRECTORIES}) - add_executable(cmTryCompileExec <srcfile>...) - target_link_options(cmTryCompileExec PRIVATE <LINK_OPTIONS from caller>) - target_link_libraries(cmTryCompileExec ${LINK_LIBRARIES}) - -The options are: - -``CMAKE_FLAGS <flags>...`` - Specify flags of the form ``-DVAR:TYPE=VALUE`` to be passed to - the ``cmake`` command-line used to drive the test build. - The above example shows how values for variables - ``INCLUDE_DIRECTORIES``, ``LINK_DIRECTORIES``, and ``LINK_LIBRARIES`` - are used. - -``COMPILE_DEFINITIONS <defs>...`` - Specify ``-Ddefinition`` arguments to pass to :command:`add_definitions` - in the generated test project. - -``COPY_FILE <fileName>`` - Copy the built executable or static library to the given ``<fileName>``. - -``COPY_FILE_ERROR <var>`` - Use after ``COPY_FILE`` to capture into variable ``<var>`` any error - message encountered while trying to copy the file. - -``LINK_LIBRARIES <libs>...`` - Specify libraries to be linked in the generated project. - The list of libraries may refer to system libraries and to - :ref:`Imported Targets <Imported Targets>` from the calling project. - - If this option is specified, any ``-DLINK_LIBRARIES=...`` value - given to the ``CMAKE_FLAGS`` option will be ignored. - -``LINK_OPTIONS <options>...`` - Specify link step options to pass to :command:`target_link_options` or to - set the :prop_tgt:`STATIC_LIBRARY_OPTIONS` target property in the generated - project, depending on the :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` variable. - -``OUTPUT_VARIABLE <var>`` - Store the output from the build process in the given variable. - -``<LANG>_STANDARD <std>`` - Specify the :prop_tgt:`C_STANDARD`, :prop_tgt:`CXX_STANDARD`, - :prop_tgt:`OBJC_STANDARD`, :prop_tgt:`OBJCXX_STANDARD`, - or :prop_tgt:`CUDA_STANDARD` target property of the generated project. - -``<LANG>_STANDARD_REQUIRED <bool>`` - Specify the :prop_tgt:`C_STANDARD_REQUIRED`, - :prop_tgt:`CXX_STANDARD_REQUIRED`, :prop_tgt:`OBJC_STANDARD_REQUIRED`, - :prop_tgt:`OBJCXX_STANDARD_REQUIRED`,or :prop_tgt:`CUDA_STANDARD_REQUIRED` - target property of the generated project. - -``<LANG>_EXTENSIONS <bool>`` - Specify the :prop_tgt:`C_EXTENSIONS`, :prop_tgt:`CXX_EXTENSIONS`, - :prop_tgt:`OBJC_EXTENSIONS`, :prop_tgt:`OBJCXX_EXTENSIONS`, - or :prop_tgt:`CUDA_EXTENSIONS` target property of the generated project. - -In this version all files in ``<bindir>/CMakeFiles/CMakeTmp`` will be -cleaned automatically. For debugging, ``--debug-trycompile`` can be -passed to ``cmake`` to avoid this clean. However, multiple sequential -``try_compile`` operations reuse this single output directory. If you use -``--debug-trycompile``, you can only debug one ``try_compile`` call at a time. -The recommended procedure is to protect all ``try_compile`` calls in your -project by ``if(NOT DEFINED <resultVar>)`` logic, configure with cmake -all the way through once, then delete the cache entry associated with -the try_compile call of interest, and then re-run cmake again with -``--debug-trycompile``. - -Other Behavior Settings -^^^^^^^^^^^^^^^^^^^^^^^ - -If set, the following variables are passed in to the generated -try_compile CMakeLists.txt to initialize compile target properties with -default values: - -* :variable:`CMAKE_CUDA_RUNTIME_LIBRARY` -* :variable:`CMAKE_ENABLE_EXPORTS` -* :variable:`CMAKE_LINK_SEARCH_START_STATIC` -* :variable:`CMAKE_LINK_SEARCH_END_STATIC` -* :variable:`CMAKE_MSVC_RUNTIME_LIBRARY` -* :variable:`CMAKE_POSITION_INDEPENDENT_CODE` - -If :policy:`CMP0056` is set to ``NEW``, then -:variable:`CMAKE_EXE_LINKER_FLAGS` is passed in as well. - -If :policy:`CMP0083` is set to ``NEW``, then in order to obtain correct -behavior at link time, the ``check_pie_supported()`` command from the -:module:`CheckPIESupported` module must be called before using the -:command:`try_compile` command. - -The current settings of :policy:`CMP0065` and :policy:`CMP0083` are propagated -through to the generated test project. - -Set the :variable:`CMAKE_TRY_COMPILE_CONFIGURATION` variable to choose -a build configuration. - -Set the :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` variable to specify -the type of target used for the source file signature. - -Set the :variable:`CMAKE_TRY_COMPILE_PLATFORM_VARIABLES` variable to specify -variables that must be propagated into the test project. This variable is -meant for use only in toolchain files and is only honored by the -``try_compile()`` command for the source files form, not when given a whole -project. - -If :policy:`CMP0067` is set to ``NEW``, or any of the ``<LANG>_STANDARD``, -``<LANG>_STANDARD_REQUIRED``, or ``<LANG>_EXTENSIONS`` options are used, -then the language standard variables are honored: - -* :variable:`CMAKE_C_STANDARD` -* :variable:`CMAKE_C_STANDARD_REQUIRED` -* :variable:`CMAKE_C_EXTENSIONS` -* :variable:`CMAKE_CXX_STANDARD` -* :variable:`CMAKE_CXX_STANDARD_REQUIRED` -* :variable:`CMAKE_CXX_EXTENSIONS` -* :variable:`CMAKE_OBJC_STANDARD` -* :variable:`CMAKE_OBJC_STANDARD_REQUIRED` -* :variable:`CMAKE_OBJC_EXTENSIONS` -* :variable:`CMAKE_OBJCXX_STANDARD` -* :variable:`CMAKE_OBJCXX_STANDARD_REQUIRED` -* :variable:`CMAKE_OBJCXX_EXTENSIONS` -* :variable:`CMAKE_CUDA_STANDARD` -* :variable:`CMAKE_CUDA_STANDARD_REQUIRED` -* :variable:`CMAKE_CUDA_EXTENSIONS` - -Their values are used to set the corresponding target properties in -the generated project (unless overridden by an explicit option). - -For the :generator:`Green Hills MULTI` generator the GHS toolset and target -system customization cache variables are also propagated into the test project.
diff --git a/share/cmake-3.18/Help/command/try_run.rst b/share/cmake-3.18/Help/command/try_run.rst deleted file mode 100644 index d401ebe..0000000 --- a/share/cmake-3.18/Help/command/try_run.rst +++ /dev/null
@@ -1,103 +0,0 @@ -try_run -------- - -.. only:: html - - .. contents:: - -Try compiling and then running some code. - -Try Compiling and Running Source Files -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. code-block:: cmake - - try_run(<runResultVar> <compileResultVar> - <bindir> <srcfile> [CMAKE_FLAGS <flags>...] - [COMPILE_DEFINITIONS <defs>...] - [LINK_OPTIONS <options>...] - [LINK_LIBRARIES <libs>...] - [COMPILE_OUTPUT_VARIABLE <var>] - [RUN_OUTPUT_VARIABLE <var>] - [OUTPUT_VARIABLE <var>] - [ARGS <args>...]) - -Try compiling a ``<srcfile>``. Returns ``TRUE`` or ``FALSE`` for success -or failure in ``<compileResultVar>``. If the compile succeeded, runs the -executable and returns its exit code in ``<runResultVar>``. If the -executable was built, but failed to run, then ``<runResultVar>`` will be -set to ``FAILED_TO_RUN``. See the :command:`try_compile` command for -information on how the test project is constructed to build the source file. - -The options are: - -``CMAKE_FLAGS <flags>...`` - Specify flags of the form ``-DVAR:TYPE=VALUE`` to be passed to - the ``cmake`` command-line used to drive the test build. - The example in :command:`try_compile` shows how values for variables - ``INCLUDE_DIRECTORIES``, ``LINK_DIRECTORIES``, and ``LINK_LIBRARIES`` - are used. - -``COMPILE_DEFINITIONS <defs>...`` - Specify ``-Ddefinition`` arguments to pass to :command:`add_definitions` - in the generated test project. - -``COMPILE_OUTPUT_VARIABLE <var>`` - Report the compile step build output in a given variable. - -``LINK_LIBRARIES <libs>...`` - Specify libraries to be linked in the generated project. - The list of libraries may refer to system libraries and to - :ref:`Imported Targets <Imported Targets>` from the calling project. - - If this option is specified, any ``-DLINK_LIBRARIES=...`` value - given to the ``CMAKE_FLAGS`` option will be ignored. - -``LINK_OPTIONS <options>...`` - Specify link step options to pass to :command:`target_link_options` in the - generated project. - -``OUTPUT_VARIABLE <var>`` - Report the compile build output and the output from running the executable - in the given variable. This option exists for legacy reasons. Prefer - ``COMPILE_OUTPUT_VARIABLE`` and ``RUN_OUTPUT_VARIABLE`` instead. - -``RUN_OUTPUT_VARIABLE <var>`` - Report the output from running the executable in a given variable. - -Other Behavior Settings -^^^^^^^^^^^^^^^^^^^^^^^ - -Set the :variable:`CMAKE_TRY_COMPILE_CONFIGURATION` variable to choose -a build configuration. - -Behavior when Cross Compiling -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -When cross compiling, the executable compiled in the first step -usually cannot be run on the build host. The ``try_run`` command checks -the :variable:`CMAKE_CROSSCOMPILING` variable to detect whether CMake is in -cross-compiling mode. If that is the case, it will still try to compile -the executable, but it will not try to run the executable unless the -:variable:`CMAKE_CROSSCOMPILING_EMULATOR` variable is set. Instead it -will create cache variables which must be filled by the user or by -presetting them in some CMake script file to the values the executable -would have produced if it had been run on its actual target platform. -These cache entries are: - -``<runResultVar>`` - Exit code if the executable were to be run on the target platform. - -``<runResultVar>__TRYRUN_OUTPUT`` - Output from stdout and stderr if the executable were to be run on - the target platform. This is created only if the - ``RUN_OUTPUT_VARIABLE`` or ``OUTPUT_VARIABLE`` option was used. - -In order to make cross compiling your project easier, use ``try_run`` -only if really required. If you use ``try_run``, use the -``RUN_OUTPUT_VARIABLE`` or ``OUTPUT_VARIABLE`` options only if really -required. Using them will require that when cross-compiling, the cache -variables will have to be set manually to the output of the executable. -You can also "guard" the calls to ``try_run`` with an :command:`if` -block checking the :variable:`CMAKE_CROSSCOMPILING` variable and -provide an easy-to-preset alternative for this case.
diff --git a/share/cmake-3.18/Help/command/variable_watch.rst b/share/cmake-3.18/Help/command/variable_watch.rst deleted file mode 100644 index ce69bcf..0000000 --- a/share/cmake-3.18/Help/command/variable_watch.rst +++ /dev/null
@@ -1,15 +0,0 @@ -variable_watch --------------- - -Watch the CMake variable for change. - -.. code-block:: cmake - - variable_watch(<variable> [<command>]) - -If the specified ``<variable>`` changes, a message will be printed -to inform about the change. - -Additionally, if ``<command>`` is given, this command will be executed. -The command will receive the following arguments: -``COMMAND(<variable> <access> <value> <current_list_file> <stack>)``
diff --git a/share/cmake-3.18/Help/cpack_gen/archive.rst b/share/cmake-3.18/Help/cpack_gen/archive.rst deleted file mode 100644 index 3656aa2..0000000 --- a/share/cmake-3.18/Help/cpack_gen/archive.rst +++ /dev/null
@@ -1,75 +0,0 @@ -CPack Archive Generator ------------------------ - -CPack generator for packaging files into an archive, which can have -any of the following formats: - - - 7Z - 7zip - (.7z) - - TBZ2 (.tar.bz2) - - TGZ (.tar.gz) - - TXZ (.tar.xz) - - TZ (.tar.Z) - - TZST (.tar.zst) - - ZIP (.zip) - -When this generator is called from ``CPackSourceConfig.cmake`` (or through -the ``package_source`` target), then the generated archive will contain all -files in the project directory, except those specified in -:variable:`CPACK_SOURCE_IGNORE_FILES`. The following is one example of -packaging all source files of a project: - -.. code-block:: cmake - - set(CPACK_SOURCE_GENERATOR "TGZ") - set(CPACK_SOURCE_IGNORE_FILES - \\.git/ - build/ - ".*~$" - ) - set(CPACK_VERBATIM_VARIABLES YES) - include(CPack) - -When this generator is called from ``CPackConfig.cmake`` (or through the -``package`` target), then the generated archive will contain all files -that have been installed via CMake's :command:`install` command (and the -deprecated commands :command:`install_files`, :command:`install_programs`, -and :command:`install_targets`). - -Variables specific to CPack Archive generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. variable:: CPACK_ARCHIVE_FILE_NAME - CPACK_ARCHIVE_<component>_FILE_NAME - - Package file name without extension. The extension is determined from the - archive format (see list above) and automatically appended to the file name. - The default is ``<CPACK_PACKAGE_FILE_NAME>[-<component>]``, with spaces - replaced by '-'. - -.. variable:: CPACK_ARCHIVE_COMPONENT_INSTALL - - Enable component packaging. If enabled (ON), then the archive generator - creates multiple packages. The default is OFF, which means that a single - package containing files of all components is generated. - -Variables used by CPack Archive generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -These variables are used by the Archive generator, but are also available to -CPack generators which are essentially archives at their core. These include: - - - :cpack_gen:`CPack Cygwin Generator` - - :cpack_gen:`CPack FreeBSD Generator` - -.. variable:: CPACK_ARCHIVE_THREADS - - The number of threads to use when performing the compression. If set to - ``0``, the number of available cores on the machine will be used instead. - The default is ``1`` which limits compression to a single thread. Note that - not all compression modes support threading in all environments. Currently, - only the XZ compression may support it. - -.. note:: - - Official CMake binaries available on ``cmake.org`` ship with a ``liblzma`` - that does not support parallel compression.
diff --git a/share/cmake-3.18/Help/cpack_gen/bundle.rst b/share/cmake-3.18/Help/cpack_gen/bundle.rst deleted file mode 100644 index b16dbda..0000000 --- a/share/cmake-3.18/Help/cpack_gen/bundle.rst +++ /dev/null
@@ -1,66 +0,0 @@ -CPack Bundle Generator ----------------------- - -CPack Bundle generator (macOS) specific options - -Variables specific to CPack Bundle generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Installers built on macOS using the Bundle generator use the -aforementioned DragNDrop (``CPACK_DMG_xxx``) variables, plus the following -Bundle-specific parameters (``CPACK_BUNDLE_xxx``). - -.. variable:: CPACK_BUNDLE_NAME - - The name of the generated bundle. This appears in the macOS Finder as the - bundle name. Required. - -.. variable:: CPACK_BUNDLE_PLIST - - Path to an macOS Property List (``.plist``) file that will be used - for the generated bundle. This - assumes that the caller has generated or specified their own ``Info.plist`` - file. Required. - -.. variable:: CPACK_BUNDLE_ICON - - Path to an macOS icon file that will be used as the icon for the generated - bundle. This is the icon that appears in the macOS Finder for the bundle, and - in the macOS dock when the bundle is opened. Required. - -.. variable:: CPACK_BUNDLE_STARTUP_COMMAND - - Path to a startup script. This is a path to an executable or script that - will be run whenever an end-user double-clicks the generated bundle in the - macOS Finder. Optional. - -.. variable:: CPACK_BUNDLE_APPLE_CERT_APP - - The name of your Apple supplied code signing certificate for the application. - The name usually takes the form ``Developer ID Application: [Name]`` or - ``3rd Party Mac Developer Application: [Name]``. If this variable is not set - the application will not be signed. - -.. variable:: CPACK_BUNDLE_APPLE_ENTITLEMENTS - - The name of the Property List (``.plist``) file that contains your Apple - entitlements for sandboxing your application. This file is required - for submission to the macOS App Store. - -.. variable:: CPACK_BUNDLE_APPLE_CODESIGN_FILES - - A list of additional files that you wish to be signed. You do not need to - list the main application folder, or the main executable. You should - list any frameworks and plugins that are included in your app bundle. - -.. variable:: CPACK_BUNDLE_APPLE_CODESIGN_PARAMETER - - Additional parameter that will passed to ``codesign``. - Default value: ``--deep -f`` - -.. variable:: CPACK_COMMAND_CODESIGN - - Path to the ``codesign(1)`` command used to sign applications with an - Apple cert. This variable can be used to override the automatically - detected command (or specify its location if the auto-detection fails - to find it).
diff --git a/share/cmake-3.18/Help/cpack_gen/cygwin.rst b/share/cmake-3.18/Help/cpack_gen/cygwin.rst deleted file mode 100644 index c65653e..0000000 --- a/share/cmake-3.18/Help/cpack_gen/cygwin.rst +++ /dev/null
@@ -1,28 +0,0 @@ -CPack Cygwin Generator ----------------------- - -Cygwin CPack generator (Cygwin). - -Variables affecting the CPack Cygwin generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - - :variable:`CPACK_ARCHIVE_THREADS` - -Variables specific to CPack Cygwin generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The -following variable is specific to installers build on and/or for -Cygwin: - -.. variable:: CPACK_CYGWIN_PATCH_NUMBER - - The Cygwin patch number. FIXME: This documentation is incomplete. - -.. variable:: CPACK_CYGWIN_PATCH_FILE - - The Cygwin patch file. FIXME: This documentation is incomplete. - -.. variable:: CPACK_CYGWIN_BUILD_SCRIPT - - The Cygwin build script. FIXME: This documentation is incomplete.
diff --git a/share/cmake-3.18/Help/cpack_gen/deb.rst b/share/cmake-3.18/Help/cpack_gen/deb.rst deleted file mode 100644 index bf50c55..0000000 --- a/share/cmake-3.18/Help/cpack_gen/deb.rst +++ /dev/null
@@ -1,565 +0,0 @@ -CPack DEB Generator -------------------- - -The built in (binary) CPack DEB generator (Unix only) - -Variables specific to CPack Debian (DEB) generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack DEB generator may be used to create DEB package using :module:`CPack`. -The CPack DEB generator is a :module:`CPack` generator thus it uses the -``CPACK_XXX`` variables used by :module:`CPack`. - -The CPack DEB generator should work on any Linux host but it will produce -better deb package when Debian specific tools ``dpkg-xxx`` are usable on -the build system. - -The CPack DEB generator has specific features which are controlled by the -specifics ``CPACK_DEBIAN_XXX`` variables. - -``CPACK_DEBIAN_<COMPONENT>_XXXX`` variables may be used in order to have -**component** specific values. Note however that ``<COMPONENT>`` refers to -the **grouping name** written in upper case. It may be either a component name -or a component GROUP name. - -Here are some CPack DEB generator wiki resources that are here for historic -reasons and are no longer maintained but may still prove useful: - - - https://gitlab.kitware.com/cmake/community/-/wikis/doc/cpack/Configuration - - https://gitlab.kitware.com/cmake/community/-/wikis/doc/cpack/PackageGenerators#deb-unix-only - -List of CPack DEB generator specific variables: - -.. variable:: CPACK_DEB_COMPONENT_INSTALL - - Enable component packaging for CPackDEB - - * Mandatory : NO - * Default : OFF - - If enabled (ON) multiple packages are generated. By default a single package - containing files of all components is generated. - -.. variable:: CPACK_DEBIAN_PACKAGE_NAME - CPACK_DEBIAN_<COMPONENT>_PACKAGE_NAME - - Set Package control field (variable is automatically transformed to lower - case). - - * Mandatory : YES - * Default : - - - :variable:`CPACK_PACKAGE_NAME` for non-component based - installations - - :variable:`CPACK_DEBIAN_PACKAGE_NAME` suffixed with -<COMPONENT> - for component-based installations. - - See https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source - -.. variable:: CPACK_DEBIAN_FILE_NAME - CPACK_DEBIAN_<COMPONENT>_FILE_NAME - - Package file name. - - * Mandatory : YES - * Default : ``<CPACK_PACKAGE_FILE_NAME>[-<component>].deb`` - - This may be set to ``DEB-DEFAULT`` to allow the CPack DEB generator to generate - package file name by itself in deb format:: - - <PackageName>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb - - Alternatively provided package file name must end - with either ``.deb`` or ``.ipk`` suffix. - - .. note:: - - Preferred setting of this variable is ``DEB-DEFAULT`` but for backward - compatibility with the CPack DEB generator in CMake prior to version 3.6 this - feature is disabled by default. - - .. note:: - - By using non default filenames duplicate names may occur. Duplicate files - get overwritten and it is up to the packager to set the variables in a - manner that will prevent such errors. - -.. variable:: CPACK_DEBIAN_PACKAGE_EPOCH - - The Debian package epoch - - * Mandatory : No - * Default : - - - Optional number that should be incremented when changing versioning schemas - or fixing mistakes in the version numbers of older packages. - -.. variable:: CPACK_DEBIAN_PACKAGE_VERSION - - The Debian package version - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_VERSION` - - This variable may contain only alphanumerics (A-Za-z0-9) and the characters - . + - ~ (full stop, plus, hyphen, tilde) and should start with a digit. If - :variable:`CPACK_DEBIAN_PACKAGE_RELEASE` is not set then hyphens are not - allowed. - - .. note:: - - For backward compatibility with CMake 3.9 and lower a failed test of this - variable's content is not a hard error when both - :variable:`CPACK_DEBIAN_PACKAGE_RELEASE` and - :variable:`CPACK_DEBIAN_PACKAGE_EPOCH` variables are not set. An author - warning is reported instead. - -.. variable:: CPACK_DEBIAN_PACKAGE_RELEASE - - The Debian package release - Debian revision number. - - * Mandatory : No - * Default : - - - This is the numbering of the DEB package itself, i.e. the version of the - packaging and not the version of the content (see - :variable:`CPACK_DEBIAN_PACKAGE_VERSION`). One may change the default value - if the previous packaging was buggy and/or you want to put here a fancy Linux - distro specific numbering. - -.. variable:: CPACK_DEBIAN_PACKAGE_ARCHITECTURE - CPACK_DEBIAN_<COMPONENT>_PACKAGE_ARCHITECTURE - - The Debian package architecture - - * Mandatory : YES - * Default : Output of ``dpkg --print-architecture`` (or ``i386`` - if ``dpkg`` is not found) - -.. variable:: CPACK_DEBIAN_PACKAGE_DEPENDS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_DEPENDS - - Sets the Debian dependencies of this package. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_DEPENDS` for component-based - installations. - - .. note:: - - If :variable:`CPACK_DEBIAN_PACKAGE_SHLIBDEPS` or - more specifically :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_SHLIBDEPS` - is set for this component, the discovered dependencies will be appended - to :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_DEPENDS` instead of - :variable:`CPACK_DEBIAN_PACKAGE_DEPENDS`. If - :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_DEPENDS` is an empty string, - only the automatically discovered dependencies will be set for this - component. - - Example:: - - set(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6 (>= 2.3.1-6), libc6 (< 2.4)") - -.. variable:: CPACK_DEBIAN_ENABLE_COMPONENT_DEPENDS - - Sets inter component dependencies if listed with - :variable:`CPACK_COMPONENT_<compName>_DEPENDS` variables. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_DEBIAN_PACKAGE_MAINTAINER - - The Debian package maintainer - - * Mandatory : YES - * Default : ``CPACK_PACKAGE_CONTACT`` - -.. variable:: CPACK_DEBIAN_PACKAGE_DESCRIPTION - CPACK_DEBIAN_<COMPONENT>_DESCRIPTION - - The Debian package description - - * Mandatory : YES - * Default : - - - :variable:`CPACK_DEBIAN_<COMPONENT>_DESCRIPTION` (component - based installers only) if set, or :variable:`CPACK_DEBIAN_PACKAGE_DESCRIPTION` if set, or - - :variable:`CPACK_COMPONENT_<compName>_DESCRIPTION` (component - based installers only) if set, or :variable:`CPACK_PACKAGE_DESCRIPTION` if set, or - - content of the file specified in :variable:`CPACK_PACKAGE_DESCRIPTION_FILE` if set - - If after that description is not set, :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY` going to be - used if set. Otherwise, :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY` will be added as the first - line of description as defined in `Debian Policy Manual`_. - -.. _Debian Policy Manual: https://www.debian.org/doc/debian-policy/ch-controlfields.html#description - -.. variable:: CPACK_DEBIAN_PACKAGE_SECTION - CPACK_DEBIAN_<COMPONENT>_PACKAGE_SECTION - - Set Section control field e.g. admin, devel, doc, ... - - * Mandatory : YES - * Default : "devel" - - See https://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections - -.. variable:: CPACK_DEBIAN_ARCHIVE_TYPE - - The archive format used for creating the Debian package. - - * Mandatory : YES - * Default : "gnutar" - - Possible value is: - - - gnutar - - .. note:: - - This variable previously defaulted to the ``paxr`` value, but ``dpkg`` - has never supported that tar format. For backwards compatibility the - ``paxr`` value will be mapped to ``gnutar`` and a deprecation message - will be emitted. - -.. variable:: CPACK_DEBIAN_COMPRESSION_TYPE - - The compression used for creating the Debian package. - - * Mandatory : YES - * Default : "gzip" - - Possible values are: - - - lzma - - xz - - bzip2 - - gzip - -.. variable:: CPACK_DEBIAN_PACKAGE_PRIORITY - CPACK_DEBIAN_<COMPONENT>_PACKAGE_PRIORITY - - Set Priority control field e.g. required, important, standard, optional, - extra - - * Mandatory : YES - * Default : "optional" - - See https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities - -.. variable:: CPACK_DEBIAN_PACKAGE_HOMEPAGE - - The URL of the web site for this package, preferably (when applicable) the - site from which the original source can be obtained and any additional - upstream documentation or information may be found. - - * Mandatory : NO - * Default : :variable:`CMAKE_PROJECT_HOMEPAGE_URL` - - .. note:: - - The content of this field is a simple URL without any surrounding - characters such as <>. - -.. variable:: CPACK_DEBIAN_PACKAGE_SHLIBDEPS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_SHLIBDEPS - - May be set to ON in order to use ``dpkg-shlibdeps`` to generate - better package dependency list. - - * Mandatory : NO - * Default : - - - :variable:`CPACK_DEBIAN_PACKAGE_SHLIBDEPS` if set or - - OFF - - .. note:: - - You may need set :variable:`CMAKE_INSTALL_RPATH` to an appropriate value - if you use this feature, because if you don't ``dpkg-shlibdeps`` - may fail to find your own shared libs. - See https://gitlab.kitware.com/cmake/community/-/wikis/doc/cmake/RPATH-handling - -.. variable:: CPACK_DEBIAN_PACKAGE_DEBUG - - May be set when invoking cpack in order to trace debug information - during the CPack DEB generator run. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_DEBIAN_PACKAGE_PREDEPENDS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_PREDEPENDS - - Sets the `Pre-Depends` field of the Debian package. - Like :variable:`Depends <CPACK_DEBIAN_PACKAGE_DEPENDS>`, except that it - also forces ``dpkg`` to complete installation of the packages named - before even starting the installation of the package which declares the - pre-dependency. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_PREDEPENDS` for component-based - installations. - - See http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps - -.. variable:: CPACK_DEBIAN_PACKAGE_ENHANCES - CPACK_DEBIAN_<COMPONENT>_PACKAGE_ENHANCES - - Sets the `Enhances` field of the Debian package. - Similar to :variable:`Suggests <CPACK_DEBIAN_PACKAGE_SUGGESTS>` but works - in the opposite direction: declares that a package can enhance the - functionality of another package. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_ENHANCES` for component-based - installations. - - See http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps - -.. variable:: CPACK_DEBIAN_PACKAGE_BREAKS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_BREAKS - - Sets the `Breaks` field of the Debian package. - When a binary package (P) declares that it breaks other packages (B), - ``dpkg`` will not allow the package (P) which declares `Breaks` be - **unpacked** unless the packages that will be broken (B) are deconfigured - first. - As long as the package (P) is configured, the previously deconfigured - packages (B) cannot be reconfigured again. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_BREAKS` for component-based - installations. - - See https://www.debian.org/doc/debian-policy/ch-relationships.html#s-breaks - -.. variable:: CPACK_DEBIAN_PACKAGE_CONFLICTS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_CONFLICTS - - Sets the `Conflicts` field of the Debian package. - When one binary package declares a conflict with another using a `Conflicts` - field, ``dpkg`` will not allow them to be unpacked on the system at - the same time. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_CONFLICTS` for component-based - installations. - - See https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts - - .. note:: - - This is a stronger restriction than - :variable:`Breaks <CPACK_DEBIAN_PACKAGE_BREAKS>`, which prevents the - broken package from being configured while the breaking package is in - the "Unpacked" state but allows both packages to be unpacked at the same - time. - -.. variable:: CPACK_DEBIAN_PACKAGE_PROVIDES - CPACK_DEBIAN_<COMPONENT>_PACKAGE_PROVIDES - - Sets the `Provides` field of the Debian package. - A virtual package is one which appears in the `Provides` control field of - another package. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_PROVIDES` for component-based - installations. - - See https://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual - -.. variable:: CPACK_DEBIAN_PACKAGE_REPLACES - CPACK_DEBIAN_<COMPONENT>_PACKAGE_REPLACES - - Sets the `Replaces` field of the Debian package. - Packages can declare in their control file that they should overwrite - files in certain other packages, or completely replace other packages. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_REPLACES` for component-based - installations. - - See http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps - -.. variable:: CPACK_DEBIAN_PACKAGE_RECOMMENDS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_RECOMMENDS - - Sets the `Recommends` field of the Debian package. - Allows packages to declare a strong, but not absolute, dependency on other - packages. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_RECOMMENDS` for component-based - installations. - - See http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps - -.. variable:: CPACK_DEBIAN_PACKAGE_SUGGESTS - CPACK_DEBIAN_<COMPONENT>_PACKAGE_SUGGESTS - - Sets the `Suggests` field of the Debian package. - Allows packages to declare a suggested package install grouping. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_SUGGESTS` for component-based - installations. - - See http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps - -.. variable:: CPACK_DEBIAN_PACKAGE_GENERATE_SHLIBS - - * Mandatory : NO - * Default : OFF - - Allows to generate shlibs control file automatically. Compatibility is defined by - :variable:`CPACK_DEBIAN_PACKAGE_GENERATE_SHLIBS_POLICY` variable value. - - .. note:: - - Libraries are only considered if they have both library name and version - set. This can be done by setting SOVERSION property with - :command:`set_target_properties` command. - -.. variable:: CPACK_DEBIAN_PACKAGE_GENERATE_SHLIBS_POLICY - - Compatibility policy for auto-generated shlibs control file. - - * Mandatory : NO - * Default : "=" - - Defines compatibility policy for auto-generated shlibs control file. - Possible values: "=", ">=" - - See https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-shlibdeps - -.. variable:: CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA - CPACK_DEBIAN_<COMPONENT>_PACKAGE_CONTROL_EXTRA - - This variable allow advanced user to add custom script to the - control.tar.gz. - Typical usage is for conffiles, postinst, postrm, prerm. - - * Mandatory : NO - * Default : - - - Usage:: - - set(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA - "${CMAKE_CURRENT_SOURCE_DIR}/prerm;${CMAKE_CURRENT_SOURCE_DIR}/postrm") - - .. note:: - - The original permissions of the files will be used in the final - package unless the variable - :variable:`CPACK_DEBIAN_PACKAGE_CONTROL_STRICT_PERMISSION` is set. - In particular, the scripts should have the proper executable - flag prior to the generation of the package. - -.. variable:: CPACK_DEBIAN_PACKAGE_CONTROL_STRICT_PERMISSION - CPACK_DEBIAN_<COMPONENT>_PACKAGE_CONTROL_STRICT_PERMISSION - - This variable indicates if the Debian policy on control files should be - strictly followed. - - * Mandatory : NO - * Default : FALSE - - Usage:: - - set(CPACK_DEBIAN_PACKAGE_CONTROL_STRICT_PERMISSION TRUE) - - .. note:: - - This overrides the permissions on the original files, following the rules - set by Debian policy - https://www.debian.org/doc/debian-policy/ch-files.html#s-permissions-owners - -.. variable:: CPACK_DEBIAN_PACKAGE_SOURCE - CPACK_DEBIAN_<COMPONENT>_PACKAGE_SOURCE - - Sets the ``Source`` field of the binary Debian package. - When the binary package name is not the same as the source package name - (in particular when several components/binaries are generated from one - source) the source from which the binary has been generated should be - indicated with the field ``Source``. - - * Mandatory : NO - * Default : - - - An empty string for non-component based installations - - :variable:`CPACK_DEBIAN_PACKAGE_SOURCE` for component-based - installations. - - See https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source - - .. note:: - - This value is not interpreted. It is possible to pass an optional - revision number of the referenced source package as well. - -Packaging of debug information -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Dbgsym packages contain debug symbols for debugging packaged binaries. - -Dbgsym packaging has its own set of variables: - -.. variable:: CPACK_DEBIAN_DEBUGINFO_PACKAGE - CPACK_DEBIAN_<component>_DEBUGINFO_PACKAGE - - Enable generation of dbgsym .ddeb package(s). - - * Mandatory : NO - * Default : OFF - -.. note:: - - Binaries must contain debug symbols before packaging so use either ``Debug`` - or ``RelWithDebInfo`` for :variable:`CMAKE_BUILD_TYPE` variable value. - -Building Debian packages on Windows -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -To communicate UNIX file permissions from the install stage -to the CPack DEB generator the "cmake_mode_t" NTFS -alternate data stream (ADT) is used. - -When a filesystem without ADT support is used only owner read/write -permissions can be preserved. - -Reproducible packages -^^^^^^^^^^^^^^^^^^^^^ - -The environment variable ``SOURCE_DATE_EPOCH`` may be set to a UNIX -timestamp, defined as the number of seconds, excluding leap seconds, -since 01 Jan 1970 00:00:00 UTC. If set, the CPack DEB generator will -use its value for timestamps in the package.
diff --git a/share/cmake-3.18/Help/cpack_gen/dmg.rst b/share/cmake-3.18/Help/cpack_gen/dmg.rst deleted file mode 100644 index cede0f2..0000000 --- a/share/cmake-3.18/Help/cpack_gen/dmg.rst +++ /dev/null
@@ -1,110 +0,0 @@ -CPack DragNDrop Generator -------------------------- - -The DragNDrop CPack generator (macOS) creates a DMG image. - -Variables specific to CPack DragNDrop generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variables are specific to the DragNDrop installers built -on macOS: - -.. variable:: CPACK_DMG_VOLUME_NAME - - The volume name of the generated disk image. Defaults to - CPACK_PACKAGE_FILE_NAME. - -.. variable:: CPACK_DMG_FORMAT - - The disk image format. Common values are ``UDRO`` (UDIF read-only), ``UDZO`` (UDIF - zlib-compressed) or ``UDBZ`` (UDIF bzip2-compressed). Refer to ``hdiutil(1)`` for - more information on other available formats. Defaults to ``UDZO``. - -.. variable:: CPACK_DMG_DS_STORE - - Path to a custom ``.DS_Store`` file. This ``.DS_Store`` file can be used to - specify the Finder window position/geometry and layout (such as hidden - toolbars, placement of the icons etc.). This file has to be generated by - the Finder (either manually or through AppleScript) using a normal folder - from which the ``.DS_Store`` file can then be extracted. - -.. variable:: CPACK_DMG_DS_STORE_SETUP_SCRIPT - - Path to a custom AppleScript file. This AppleScript is used to generate - a ``.DS_Store`` file which specifies the Finder window position/geometry and - layout (such as hidden toolbars, placement of the icons etc.). - By specifying a custom AppleScript there is no need to use - ``CPACK_DMG_DS_STORE``, as the ``.DS_Store`` that is generated by the AppleScript - will be packaged. - -.. variable:: CPACK_DMG_BACKGROUND_IMAGE - - Path to an image file to be used as the background. This file will be - copied to ``.background``/``background.<ext>``, where ``<ext>`` is the original image file - extension. The background image is installed into the image before - ``CPACK_DMG_DS_STORE_SETUP_SCRIPT`` is executed or ``CPACK_DMG_DS_STORE`` is - installed. By default no background image is set. - -.. variable:: CPACK_DMG_DISABLE_APPLICATIONS_SYMLINK - - Default behaviour is to include a symlink to ``/Applications`` in the DMG. - Set this option to ``ON`` to avoid adding the symlink. - -.. variable:: CPACK_DMG_SLA_DIR - - Directory where license and menu files for different languages are stored. - Setting this causes CPack to look for a ``<language>.menu.txt`` and - ``<language>.license.txt`` or ``<language>.license.rtf`` file for every - language defined in ``CPACK_DMG_SLA_LANGUAGES``. If both this variable and - ``CPACK_RESOURCE_FILE_LICENSE`` are set, CPack will only look for the menu - files and use the same license file for all languages. If both - ``<language>.license.txt`` and ``<language>.license.rtf`` exist, the ``.txt`` - file will be used. - -.. variable:: CPACK_DMG_SLA_LANGUAGES - - Languages for which a license agreement is provided when mounting the - generated DMG. A menu file consists of 9 lines of text. The first line is - is the name of the language itself, uppercase, in English (e.g. German). - The other lines are translations of the following strings: - - - Agree - - Disagree - - Print - - Save... - - You agree to the terms of the License Agreement when you click the - "Agree" button. - - Software License Agreement - - This text cannot be saved. The disk may be full or locked, or the file - may be locked. - - Unable to print. Make sure you have selected a printer. - - For every language in this list, CPack will try to find files - ``<language>.menu.txt`` and ``<language>.license.txt`` in the directory - specified by the :variable:`CPACK_DMG_SLA_DIR` variable. - -.. variable:: CPACK_DMG_<component>_FILE_NAME - - File name when packaging ``<component>`` as its own DMG - (``CPACK_COMPONENTS_GROUPING`` set to IGNORE). - - - Default: ``CPACK_PACKAGE_FILE_NAME-<component>`` - -.. variable:: CPACK_COMMAND_HDIUTIL - - Path to the ``hdiutil(1)`` command used to operate on disk image files on - macOS. This variable can be used to override the automatically detected - command (or specify its location if the auto-detection fails to find it). - -.. variable:: CPACK_COMMAND_SETFILE - - Path to the ``SetFile(1)`` command used to set extended attributes on files and - directories on macOS. This variable can be used to override the - automatically detected command (or specify its location if the - auto-detection fails to find it). - -.. variable:: CPACK_COMMAND_REZ - - Path to the ``Rez(1)`` command used to compile resources on macOS. This - variable can be used to override the automatically detected command (or - specify its location if the auto-detection fails to find it).
diff --git a/share/cmake-3.18/Help/cpack_gen/external.rst b/share/cmake-3.18/Help/cpack_gen/external.rst deleted file mode 100644 index 406f6be..0000000 --- a/share/cmake-3.18/Help/cpack_gen/external.rst +++ /dev/null
@@ -1,283 +0,0 @@ -CPack External Generator ------------------------- - -CPack provides many generators to create packages for a variety of platforms -and packaging systems. The intention is for CMake/CPack to be a complete -end-to-end solution for building and packaging a software project. However, it -may not always be possible to use CPack for the entire packaging process, due -to either technical limitations or policies that require the use of certain -tools. For this reason, CPack provides the "External" generator, which allows -external packaging software to take advantage of some of the functionality -provided by CPack, such as component installation and the dependency graph. - -Integration with External Packaging Tools -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack External generator generates a ``.json`` file containing the -CPack internal metadata, which gives external software information -on how to package the software. External packaging software may itself -invoke CPack, consume the generated metadata, -install and package files as required. - -Alternatively CPack can invoke an external packaging software -through an optional custom CMake script in -:variable:`CPACK_EXTERNAL_PACKAGE_SCRIPT` instead. - -Staging of installation files may also optionally be -taken care of by the generator when enabled through the -:variable:`CPACK_EXTERNAL_ENABLE_STAGING` variable. - -JSON Format -^^^^^^^^^^^ - -The JSON metadata file contains a list of CPack components and component groups, -the various options passed to :command:`cpack_add_component` and -:command:`cpack_add_component_group`, the dependencies between the components -and component groups, and various other options passed to CPack. - -The JSON's root object will always provide two fields: -``formatVersionMajor`` and ``formatVersionMinor``, which are always integers -that describe the output format of the generator. Backwards-compatible changes -to the output format (for example, adding a new field that didn't exist before) -cause the minor version to be incremented, and backwards-incompatible changes -(for example, deleting a field or changing its meaning) cause the major version -to be incremented and the minor version reset to 0. The format version is -always of the format ``major.minor``. In other words, it always has exactly two -parts, separated by a period. - -You can request one or more specific versions of the output format as described -below with :variable:`CPACK_EXTERNAL_REQUESTED_VERSIONS`. The output format will -have a major version that exactly matches the requested major version, and a -minor version that is greater than or equal to the requested minor version. If -no version is requested with :variable:`CPACK_EXTERNAL_REQUESTED_VERSIONS`, the -latest known major version is used by default. Currently, the only supported -format is 1.0, which is described below. - -Version 1.0 -*********** - -In addition to the standard format fields, format version 1.0 provides the -following fields in the root: - -``components`` - The ``components`` field is an object with component names as the keys and - objects describing the components as the values. The component objects have - the following fields: - - ``name`` - The name of the component. This is always the same as the key in the - ``components`` object. - - ``displayName`` - The value of the ``DISPLAY_NAME`` field passed to - :command:`cpack_add_component`. - - ``description`` - The value of the ``DESCRIPTION`` field passed to - :command:`cpack_add_component`. - - ``isHidden`` - True if ``HIDDEN`` was passed to :command:`cpack_add_component`, false if - it was not. - - ``isRequired`` - True if ``REQUIRED`` was passed to :command:`cpack_add_component`, false if - it was not. - - ``isDisabledByDefault`` - True if ``DISABLED`` was passed to :command:`cpack_add_component`, false if - it was not. - - ``group`` - Only present if ``GROUP`` was passed to :command:`cpack_add_component`. If - so, this field is a string value containing the component's group. - - ``dependencies`` - An array of components the component depends on. This contains the values - in the ``DEPENDS`` argument passed to :command:`cpack_add_component`. If no - ``DEPENDS`` argument was passed, this is an empty list. - - ``installationTypes`` - An array of installation types the component is part of. This contains the - values in the ``INSTALL_TYPES`` argument passed to - :command:`cpack_add_component`. If no ``INSTALL_TYPES`` argument was - passed, this is an empty list. - - ``isDownloaded`` - True if ``DOWNLOADED`` was passed to :command:`cpack_add_component`, false - if it was not. - - ``archiveFile`` - The name of the archive file passed with the ``ARCHIVE_FILE`` argument to - :command:`cpack_add_component`. If no ``ARCHIVE_FILE`` argument was passed, - this is an empty string. - -``componentGroups`` - The ``componentGroups`` field is an object with component group names as the - keys and objects describing the component groups as the values. The component - group objects have the following fields: - - ``name`` - The name of the component group. This is always the same as the key in the - ``componentGroups`` object. - - ``displayName`` - The value of the ``DISPLAY_NAME`` field passed to - :command:`cpack_add_component_group`. - - ``description`` - The value of the ``DESCRIPTION`` field passed to - :command:`cpack_add_component_group`. - - ``parentGroup`` - Only present if ``PARENT_GROUP`` was passed to - :command:`cpack_add_component_group`. If so, this field is a string value - containing the component group's parent group. - - ``isExpandedByDefault`` - True if ``EXPANDED`` was passed to :command:`cpack_add_component_group`, - false if it was not. - - ``isBold`` - True if ``BOLD_TITLE`` was passed to :command:`cpack_add_component_group`, - false if it was not. - - ``components`` - An array of names of components that are direct members of the group - (components that have this group as their ``GROUP``). Components of - subgroups are not included. - - ``subgroups`` - An array of names of component groups that are subgroups of the group - (groups that have this group as their ``PARENT_GROUP``). - -``installationTypes`` - The ``installationTypes`` field is an object with installation type names as - the keys and objects describing the installation types as the values. The - installation type objects have the following fields: - - ``name`` - The name of the installation type. This is always the same as the key in - the ``installationTypes`` object. - - ``displayName`` - The value of the ``DISPLAY_NAME`` field passed to - :command:`cpack_add_install_type`. - - ``index`` - The integer index of the installation type in the list. - -``projects`` - The ``projects`` field is an array of objects describing CMake projects which - comprise the CPack project. The values in this field are derived from - :variable:`CPACK_INSTALL_CMAKE_PROJECTS`. In most cases, this will be only a - single project. The project objects have the following fields: - - ``projectName`` - The project name passed to :variable:`CPACK_INSTALL_CMAKE_PROJECTS`. - - ``component`` - The name of the component or component set which comprises the project. - - ``directory`` - The build directory of the CMake project. This is the directory which - contains the ``cmake_install.cmake`` script. - - ``subDirectory`` - The subdirectory to install the project into inside the CPack package. - -``packageName`` - The package name given in :variable:`CPACK_PACKAGE_NAME`. Only present if - this option is set. - -``packageVersion`` - The package version given in :variable:`CPACK_PACKAGE_VERSION`. Only present - if this option is set. - -``packageDescriptionFile`` - The package description file given in - :variable:`CPACK_PACKAGE_DESCRIPTION_FILE`. Only present if this option is - set. - -``packageDescriptionSummary`` - The package description summary given in - :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY`. Only present if this option is - set. - -``buildConfig`` - The build configuration given to CPack with the ``-C`` option. Only present - if this option is set. - -``defaultDirectoryPermissions`` - The default directory permissions given in - :variable:`CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS`. Only present if this - option is set. - -``setDestdir`` - True if :variable:`CPACK_SET_DESTDIR` is true, false if it is not. - -``packagingInstallPrefix`` - The install prefix given in :variable:`CPACK_PACKAGING_INSTALL_PREFIX`. Only - present if :variable:`CPACK_SET_DESTDIR` is true. - -``stripFiles`` - True if :variable:`CPACK_STRIP_FILES` is true, false if it is not. - -``warnOnAbsoluteInstallDestination`` - True if :variable:`CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION` is true, false - if it is not. - -``errorOnAbsoluteInstallDestination`` - True if :variable:`CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION` is true, - false if it is not. - -Variables specific to CPack External generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. variable:: CPACK_EXTERNAL_REQUESTED_VERSIONS - - This variable is used to request a specific version of the CPack External - generator. It is a list of ``major.minor`` values, separated by semicolons. - - If this variable is set to a non-empty value, the CPack External generator - will iterate through each item in the list to search for a version that it - knows how to generate. Requested versions should be listed in order of - descending preference by the client software, as the first matching version - in the list will be generated. - - The generator knows how to generate the version if it has a versioned - generator whose major version exactly matches the requested major version, - and whose minor version is greater than or equal to the requested minor - version. For example, if ``CPACK_EXTERNAL_REQUESTED_VERSIONS`` contains 1.0, and - the CPack External generator knows how to generate 1.1, it will generate 1.1. - If the generator doesn't know how to generate a version in the list, it skips - the version and looks at the next one. If it doesn't know how to generate any - of the requested versions, an error is thrown. - - If this variable is not set, or is empty, the CPack External generator will - generate the highest major and minor version that it knows how to generate. - - If an invalid version is encountered in ``CPACK_EXTERNAL_REQUESTED_VERSIONS`` (one - that doesn't match ``major.minor``, where ``major`` and ``minor`` are - integers), it is ignored. - -.. variable:: CPACK_EXTERNAL_ENABLE_STAGING - - This variable can be set to true to enable optional installation - into a temporary staging area which can then be picked up - and packaged by an external packaging tool. - The top level directory used by CPack for the current packaging - task is contained in ``CPACK_TOPLEVEL_DIRECTORY``. - It is automatically cleaned up on each run before packaging is initiated - and can be used for custom temporary files required by - the external packaging tool. - It also contains the staging area ``CPACK_TEMPORARY_DIRECTORY`` - into which CPack performs the installation when staging is enabled. - -.. variable:: CPACK_EXTERNAL_PACKAGE_SCRIPT - - This variable can optionally specify the full path to - a CMake script file to be run as part of the CPack invocation. - It is invoked after (optional) staging took place and may - run an external packaging tool. The script has access to - the variables defined by the CPack config file.
diff --git a/share/cmake-3.18/Help/cpack_gen/freebsd.rst b/share/cmake-3.18/Help/cpack_gen/freebsd.rst deleted file mode 100644 index 47a7784..0000000 --- a/share/cmake-3.18/Help/cpack_gen/freebsd.rst +++ /dev/null
@@ -1,143 +0,0 @@ -CPack FreeBSD Generator ------------------------ - -The built in (binary) CPack FreeBSD (pkg) generator (Unix only) - -Variables affecting the CPack FreeBSD (pkg) generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - - :variable:`CPACK_ARCHIVE_THREADS` - -Variables specific to CPack FreeBSD (pkg) generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack FreeBSD generator may be used to create pkg(8) packages -- these may -be used on FreeBSD, DragonflyBSD, NetBSD, OpenBSD, but also on Linux or OSX, -depending on the installed package-management tools -- using :module:`CPack`. - -The CPack FreeBSD generator is a :module:`CPack` generator and uses the -``CPACK_XXX`` variables used by :module:`CPack`. It tries to re-use packaging -information that may already be specified for Debian packages for the -:cpack_gen:`CPack DEB Generator`. It also tries to re-use RPM packaging -information when Debian does not specify. - -The CPack FreeBSD generator should work on any host with libpkg installed. The -packages it produces are specific to the host architecture and ABI. - -The CPack FreeBSD generator sets package-metadata through -``CPACK_FREEBSD_XXX`` variables. The CPack FreeBSD generator, unlike the -CPack Deb generator, does not specially support componentized packages; a -single package is created from all the software artifacts created through -CMake. - -All of the variables can be set specifically for FreeBSD packaging in -the CPackConfig file or in CMakeLists.txt, but most of them have defaults -that use general settings (e.g. CMAKE_PROJECT_NAME) or Debian-specific -variables when those make sense (e.g. the homepage of an upstream project -is usually unchanged by the flavor of packaging). When there is no Debian -information to fall back on, but the RPM packaging has it, fall back to -the RPM information (e.g. package license). - -.. variable:: CPACK_FREEBSD_PACKAGE_NAME - - Sets the package name (in the package manifest, but also affects the - output filename). - - * Mandatory: YES - * Default: - - - :variable:`CPACK_PACKAGE_NAME` (this is always set by CPack itself, - based on CMAKE_PROJECT_NAME). - -.. variable:: CPACK_FREEBSD_PACKAGE_COMMENT - - Sets the package comment. This is the short description displayed by - pkg(8) in standard "pkg info" output. - - * Mandatory: YES - * Default: - - - :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY` (this is always set - by CPack itself, if nothing else sets it explicitly). - - :variable:`PROJECT_DESCRIPTION` (this can be set with the DESCRIPTION - parameter for :command:`project`). - -.. variable:: CPACK_FREEBSD_PACKAGE_DESCRIPTION - - Sets the package description. This is the long description of the package, - given by "pkg info" with a specific package as argument. - - * Mandatory: YES - * Default: - - - :variable:`CPACK_DEBIAN_PACKAGE_DESCRIPTION` (this may be set already - for Debian packaging, so we may as well re-use it). - -.. variable:: CPACK_FREEBSD_PACKAGE_WWW - - The URL of the web site for this package, preferably (when applicable) the - site from which the original source can be obtained and any additional - upstream documentation or information may be found. - - * Mandatory: YES - * Default: - - - :variable:`CMAKE_PROJECT_HOMEPAGE_URL`, or if that is not set, - :variable:`CPACK_DEBIAN_PACKAGE_HOMEPAGE` (this may be set already - for Debian packaging, so we may as well re-use it). - -.. variable:: CPACK_FREEBSD_PACKAGE_LICENSE - - The license, or licenses, which apply to this software package. This must - be one or more license-identifiers that pkg recognizes as acceptable license - identifiers (e.g. "GPLv2"). - - * Mandatory: YES - * Default: - - - :variable:`CPACK_RPM_PACKAGE_LICENSE` - -.. variable:: CPACK_FREEBSD_PACKAGE_LICENSE_LOGIC - - This variable is only of importance if there is more than one license. - The default is "single", which is only applicable to a single license. - Other acceptable values are determined by pkg -- those are "dual" or "multi" -- - meaning choice (OR) or simultaneous (AND) application of the licenses. - - * Mandatory: NO - * Default: single - -.. variable:: CPACK_FREEBSD_PACKAGE_MAINTAINER - - The FreeBSD maintainer (e.g. kde@freebsd.org) of this package. - - * Mandatory: YES - * Default: none - -.. variable:: CPACK_FREEBSD_PACKAGE_ORIGIN - - The origin (ports label) of this package; for packages built by CPack - outside of the ports system this is of less importance. The default - puts the package somewhere under misc/, as a stopgap. - - * Mandatory: YES - * Default: misc/<package name> - -.. variable:: CPACK_FREEBSD_PACKAGE_CATEGORIES - - The ports categories where this package lives (if it were to be built - from ports). If none is set a single category is determined based on - the package origin. - - * Mandatory: YES - * Default: derived from ORIGIN - -.. variable:: CPACK_FREEBSD_PACKAGE_DEPS - - A list of package origins that should be added as package dependencies. - These are in the form <category>/<packagename>, e.g. x11/libkonq. - No version information needs to be provided (this is not included - in the manifest). - - * Mandatory: NO - * Default: empty
diff --git a/share/cmake-3.18/Help/cpack_gen/ifw.rst b/share/cmake-3.18/Help/cpack_gen/ifw.rst deleted file mode 100644 index 776bb46..0000000 --- a/share/cmake-3.18/Help/cpack_gen/ifw.rst +++ /dev/null
@@ -1,347 +0,0 @@ -CPack IFW Generator -------------------- - -Configure and run the Qt Installer Framework to generate a Qt installer. - -.. only:: html - - .. contents:: - -Overview -^^^^^^^^ - -This :manual:`cpack generator <cpack-generators(7)>` generates -configuration and meta information for the `Qt Installer Framework -<http://doc.qt.io/qtinstallerframework/index.html>`_ (QtIFW), -and runs QtIFW tools to generate a Qt installer. - -QtIFW provides tools and utilities to create installers for -the platforms supported by `Qt <https://www.qt.io>`_: Linux, -Microsoft Windows, and macOS. - -To make use of this generator, QtIFW needs to be installed. -The :module:`CPackIFW` module looks for the location of the -QtIFW command-line utilities, and defines several commands to -control the behavior of this generator. - -Variables -^^^^^^^^^ - -You can use the following variables to change behavior of CPack ``IFW`` -generator. - -Debug -""""" - -.. variable:: CPACK_IFW_VERBOSE - - Set to ``ON`` to enable addition debug output. - By default is ``OFF``. - -Package -""""""" - -.. variable:: CPACK_IFW_PACKAGE_TITLE - - Name of the installer as displayed on the title bar. - By default used :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY`. - -.. variable:: CPACK_IFW_PACKAGE_PUBLISHER - - Publisher of the software (as shown in the Windows Control Panel). - By default used :variable:`CPACK_PACKAGE_VENDOR`. - -.. variable:: CPACK_IFW_PRODUCT_URL - - URL to a page that contains product information on your web site. - -.. variable:: CPACK_IFW_PACKAGE_ICON - - Filename for a custom installer icon. The actual file is '.icns' (macOS), - '.ico' (Windows). No functionality on Unix. - -.. variable:: CPACK_IFW_PACKAGE_WINDOW_ICON - - Filename for a custom window icon in PNG format for the Installer - application. - -.. variable:: CPACK_IFW_PACKAGE_LOGO - - Filename for a logo is used as QWizard::LogoPixmap. - -.. variable:: CPACK_IFW_PACKAGE_WATERMARK - - Filename for a watermark is used as QWizard::WatermarkPixmap. - -.. variable:: CPACK_IFW_PACKAGE_BANNER - - Filename for a banner is used as QWizard::BannerPixmap. - -.. variable:: CPACK_IFW_PACKAGE_BACKGROUND - - Filename for an image used as QWizard::BackgroundPixmap (only used by MacStyle). - -.. variable:: CPACK_IFW_PACKAGE_WIZARD_STYLE - - Wizard style to be used ("Modern", "Mac", "Aero" or "Classic"). - -.. variable:: CPACK_IFW_PACKAGE_STYLE_SHEET - - Filename for a stylesheet. - -.. variable:: CPACK_IFW_PACKAGE_WIZARD_DEFAULT_WIDTH - - Default width of the wizard in pixels. Setting a banner image will override this. - -.. variable:: CPACK_IFW_PACKAGE_WIZARD_DEFAULT_HEIGHT - - Default height of the wizard in pixels. Setting a watermark image will override this. - -.. variable:: CPACK_IFW_PACKAGE_TITLE_COLOR - - Color of the titles and subtitles (takes an HTML color code, such as "#88FF33"). - -.. variable:: CPACK_IFW_PACKAGE_START_MENU_DIRECTORY - - Name of the default program group for the product in the Windows Start menu. - - By default used :variable:`CPACK_IFW_PACKAGE_NAME`. - -.. variable:: CPACK_IFW_TARGET_DIRECTORY - - Default target directory for installation. - By default used - "@ApplicationsDir@/:variable:`CPACK_PACKAGE_INSTALL_DIRECTORY`" - (variables embedded in '@' are expanded by the - `QtIFW scripting engine <https://doc.qt.io/qtinstallerframework/scripting.html>`_). - - You can use predefined variables. - -.. variable:: CPACK_IFW_ADMIN_TARGET_DIRECTORY - - Default target directory for installation with administrator rights. - - You can use predefined variables. - -.. variable:: CPACK_IFW_PACKAGE_GROUP - - The group, which will be used to configure the root package - -.. variable:: CPACK_IFW_PACKAGE_NAME - - The root package name, which will be used if configuration group is not - specified - -.. variable:: CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME - - Filename of the generated maintenance tool. - The platform-specific executable file extension is appended. - - By default used QtIFW defaults (``maintenancetool``). - -.. variable:: CPACK_IFW_PACKAGE_REMOVE_TARGET_DIR - - Set to ``OFF`` if the target directory should not be deleted when uninstalling. - - Is ``ON`` by default - -.. variable:: CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_INI_FILE - - Filename for the configuration of the generated maintenance tool. - - By default used QtIFW defaults (``maintenancetool.ini``). - -.. variable:: CPACK_IFW_PACKAGE_ALLOW_NON_ASCII_CHARACTERS - - Set to ``ON`` if the installation path can contain non-ASCII characters. - - Is ``ON`` for QtIFW less 2.0 tools. - -.. variable:: CPACK_IFW_PACKAGE_ALLOW_SPACE_IN_PATH - - Set to ``OFF`` if the installation path cannot contain space characters. - - Is ``ON`` for QtIFW less 2.0 tools. - -.. variable:: CPACK_IFW_PACKAGE_CONTROL_SCRIPT - - Filename for a custom installer control script. - -.. variable:: CPACK_IFW_PACKAGE_RESOURCES - - List of additional resources ('.qrc' files) to include in the installer - binary. - - You can use :command:`cpack_ifw_add_package_resources` command to resolve - relative paths. - -.. variable:: CPACK_IFW_PACKAGE_FILE_EXTENSION - - The target binary extension. - - On Linux, the name of the target binary is automatically extended with - '.run', if you do not specify the extension. - - On Windows, the target is created as an application with the extension - '.exe', which is automatically added, if not supplied. - - On Mac, the target is created as an DMG disk image with the extension - '.dmg', which is automatically added, if not supplied. - -.. variable:: CPACK_IFW_REPOSITORIES_ALL - - The list of remote repositories. - - The default value of this variable is computed by CPack and contains - all repositories added with command :command:`cpack_ifw_add_repository` - or updated with command :command:`cpack_ifw_update_repository`. - -.. variable:: CPACK_IFW_DOWNLOAD_ALL - - If this is ``ON`` all components will be downloaded. - By default is ``OFF`` or used value - from ``CPACK_DOWNLOAD_ALL`` if set - -Components -"""""""""" - -.. variable:: CPACK_IFW_RESOLVE_DUPLICATE_NAMES - - Resolve duplicate names when installing components with groups. - -.. variable:: CPACK_IFW_PACKAGES_DIRECTORIES - - Additional prepared packages dirs that will be used to resolve - dependent components. - -.. variable:: CPACK_IFW_REPOSITORIES_DIRECTORIES - - Additional prepared repository dirs that will be used to resolve and - repack dependent components. This feature available only - since QtIFW 3.1. - -QtIFW Tools -""""""""""" - -.. variable:: CPACK_IFW_FRAMEWORK_VERSION - - The version of used QtIFW tools. - -The following variables provide the locations of the QtIFW -command-line tools as discovered by the module :module:`CPackIFW`. -These variables are cached, and may be configured if needed. - -.. variable:: CPACK_IFW_BINARYCREATOR_EXECUTABLE - - The path to ``binarycreator``. - -.. variable:: CPACK_IFW_REPOGEN_EXECUTABLE - - The path to ``repogen``. - -.. variable:: CPACK_IFW_INSTALLERBASE_EXECUTABLE - - The path to ``installerbase``. - -.. variable:: CPACK_IFW_DEVTOOL_EXECUTABLE - - The path to ``devtool``. - -Hints for Finding QtIFW -""""""""""""""""""""""" - -Generally, the CPack ``IFW`` generator automatically finds QtIFW tools, -but if you don't use a default path for installation of the QtIFW tools, -the path may be specified in either a CMake or an environment variable: - -.. variable:: CPACK_IFW_ROOT - - An CMake variable which specifies the location of the QtIFW tool suite. - - The variable will be cached in the ``CPackConfig.cmake`` file and used at - CPack runtime. - -.. variable:: QTIFWDIR - - An environment variable which specifies the location of the QtIFW tool - suite. - -.. note:: - The specified path should not contain "bin" at the end - (for example: "D:\\DevTools\\QtIFW2.0.5"). - -The :variable:`CPACK_IFW_ROOT` variable has a higher priority and overrides -the value of the :variable:`QTIFWDIR` variable. - -Other Settings -^^^^^^^^^^^^^^ - -Online installer -"""""""""""""""" - -By default, this generator generates an *offline installer*. This means that -that all packaged files are fully contained in the installer executable. - -In contrast, an *online installer* will download some or all components from -a remote server. - -The ``DOWNLOADED`` option in the :command:`cpack_add_component` command -specifies that a component is to be downloaded. Alternatively, the ``ALL`` -option in the :command:`cpack_configure_downloads` command specifies that -`all` components are to be be downloaded. - -The :command:`cpack_ifw_add_repository` command and the -:variable:`CPACK_IFW_DOWNLOAD_ALL` variable allow for more specific -configuration. - -When there are online components, CPack will write them to archive files. -The help page of the :module:`CPackComponent` module, especially the section -on the :command:`cpack_configure_downloads` function, explains how to make -these files accessible from a download URL. - -Internationalization -"""""""""""""""""""" - -Some variables and command arguments support internationalization via -CMake script. This is an optional feature. - -Installers created by QtIFW tools have built-in support for -internationalization and many phrases are localized to many languages, -but this does not apply to the description of the your components and groups -that will be distributed. - -Localization of the description of your components and groups is useful for -users of your installers. - -A localized variable or argument can contain a single default value, and a -set of pairs the name of the locale and the localized value. - -For example: - -.. code-block:: cmake - - set(LOCALIZABLE_VARIABLE "Default value" - en "English value" - en_US "American value" - en_GB "Great Britain value" - ) - -See Also -^^^^^^^^ - -Qt Installer Framework Manual: - -* Index page: - http://doc.qt.io/qtinstallerframework/index.html - -* Component Scripting: - http://doc.qt.io/qtinstallerframework/scripting.html - -* Predefined Variables: - http://doc.qt.io/qtinstallerframework/scripting.html#predefined-variables - -* Promoting Updates: - http://doc.qt.io/qtinstallerframework/ifw-updates.html - -Download Qt Installer Framework for your platform from Qt site: - http://download.qt.io/official_releases/qt-installer-framework
diff --git a/share/cmake-3.18/Help/cpack_gen/nsis.rst b/share/cmake-3.18/Help/cpack_gen/nsis.rst deleted file mode 100644 index 0dd876e..0000000 --- a/share/cmake-3.18/Help/cpack_gen/nsis.rst +++ /dev/null
@@ -1,161 +0,0 @@ -CPack NSIS Generator --------------------- - -CPack Nullsoft Scriptable Install System (NSIS) generator specific options. - -The NSIS generator requires NSIS 3.0 or newer. - -Variables specific to CPack NSIS generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variables are specific to the graphical installers built -on Windows Nullsoft Scriptable Install System. - -.. variable:: CPACK_NSIS_INSTALL_ROOT - - The default installation directory presented to the end user by the NSIS - installer is under this root dir. The full directory presented to the end - user is: ``${CPACK_NSIS_INSTALL_ROOT}/${CPACK_PACKAGE_INSTALL_DIRECTORY}`` - -.. variable:: CPACK_NSIS_MUI_ICON - - An icon filename. The name of a ``*.ico`` file used as the main icon for the - generated install program. - -.. variable:: CPACK_NSIS_MUI_UNIICON - - An icon filename. The name of a ``*.ico`` file used as the main icon for the - generated uninstall program. - -.. variable:: CPACK_NSIS_INSTALLER_MUI_ICON_CODE - - undocumented. - -.. variable:: CPACK_NSIS_MUI_WELCOMEFINISHPAGE_BITMAP - - The filename of a bitmap to use as the NSIS ``MUI_WELCOMEFINISHPAGE_BITMAP``. - -.. variable:: CPACK_NSIS_MUI_UNWELCOMEFINISHPAGE_BITMAP - - The filename of a bitmap to use as the NSIS ``MUI_UNWELCOMEFINISHPAGE_BITMAP``. - -.. variable:: CPACK_NSIS_EXTRA_PREINSTALL_COMMANDS - - Extra NSIS commands that will be added to the beginning of the install - Section, before your install tree is available on the target system. - -.. variable:: CPACK_NSIS_EXTRA_INSTALL_COMMANDS - - Extra NSIS commands that will be added to the end of the install Section, - after your install tree is available on the target system. - -.. variable:: CPACK_NSIS_EXTRA_UNINSTALL_COMMANDS - - Extra NSIS commands that will be added to the uninstall Section, before - your install tree is removed from the target system. - -.. variable:: CPACK_NSIS_COMPRESSOR - - The arguments that will be passed to the NSIS `SetCompressor` command. - -.. variable:: CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL - - Ask about uninstalling previous versions first. If this is set to ``ON``, - then an installer will look for previous installed versions and if one is - found, ask the user whether to uninstall it before proceeding with the - install. - -.. variable:: CPACK_NSIS_MODIFY_PATH - - Modify ``PATH`` toggle. If this is set to ``ON``, then an extra page will appear - in the installer that will allow the user to choose whether the program - directory should be added to the system ``PATH`` variable. - -.. variable:: CPACK_NSIS_DISPLAY_NAME - - The display name string that appears in the Windows `Apps & features` - in `Control Panel` - -.. variable:: CPACK_NSIS_PACKAGE_NAME - - The title displayed at the top of the installer. - -.. variable:: CPACK_NSIS_INSTALLED_ICON_NAME - - A path to the executable that contains the installer icon. - -.. variable:: CPACK_NSIS_HELP_LINK - - URL to a web site providing assistance in installing your application. - -.. variable:: CPACK_NSIS_URL_INFO_ABOUT - - URL to a web site providing more information about your application. - -.. variable:: CPACK_NSIS_CONTACT - - Contact information for questions and comments about the installation - process. - -.. variable:: CPACK_NSIS_<compName>_INSTALL_DIRECTORY - - Custom install directory for the specified component ``<compName>`` instead - of ``$INSTDIR``. - -.. variable:: CPACK_NSIS_CREATE_ICONS_EXTRA - - Additional NSIS commands for creating `Start Menu` shortcuts. - -.. variable:: CPACK_NSIS_DELETE_ICONS_EXTRA - - Additional NSIS commands to uninstall `Start Menu` shortcuts. - -.. variable:: CPACK_NSIS_EXECUTABLES_DIRECTORY - - Creating NSIS `Start Menu` links assumes that they are in ``bin`` unless this - variable is set. For example, you would set this to ``exec`` if your - executables are in an exec directory. - -.. variable:: CPACK_NSIS_MUI_FINISHPAGE_RUN - - Specify an executable to add an option to run on the finish page of the - NSIS installer. - -.. variable:: CPACK_NSIS_MENU_LINKS - - Specify links in ``[application]`` menu. This should contain a list of pair - ``link`` ``link name``. The link may be a URL or a path relative to - installation prefix. Like:: - - set(CPACK_NSIS_MENU_LINKS - "doc/cmake-@CMake_VERSION_MAJOR@.@CMake_VERSION_MINOR@/cmake.html" - "CMake Help" "https://cmake.org" "CMake Web Site") - -.. variable:: CPACK_NSIS_UNINSTALL_NAME - - Specify the name of the program to uninstall the version. - Default is ``Uninstall``. - -.. variable:: CPACK_NSIS_WELCOME_TITLE - - The title to display on the top of the page for the welcome page. - -.. variable:: CPACK_NSIS_WELCOME_TITLE_3LINES - - Display the title in the welcome page on 3 lines instead of 2. - -.. variable:: CPACK_NSIS_FINISH_TITLE - - The title to display on the top of the page for the finish page. - -.. variable:: CPACK_NSIS_FINISH_TITLE_3LINES - - Display the title in the finish page on 3 lines instead of 2. - -.. variable:: CPACK_NSIS_MUI_HEADERIMAGE - - The image to display on the header of installers pages. - -.. variable:: CPACK_NSIS_MANIFEST_DPI_AWARE - - If set, declares that the installer is DPI-aware.
diff --git a/share/cmake-3.18/Help/cpack_gen/nuget.rst b/share/cmake-3.18/Help/cpack_gen/nuget.rst deleted file mode 100644 index f8aa626..0000000 --- a/share/cmake-3.18/Help/cpack_gen/nuget.rst +++ /dev/null
@@ -1,189 +0,0 @@ -CPack NuGet Generator ---------------------- - -When build a NuGet package there is no direct way to control an output -filename due a lack of the corresponding CLI option of NuGet, so there -is no ``CPACK_NUGET_PACKAGE_FILENAME`` variable. To form the output filename -NuGet uses the package name and the version according to its built-in rules. - -Also, be aware that including a top level directory -(``CPACK_INCLUDE_TOPLEVEL_DIRECTORY``) is ignored by this generator. - - -Variables specific to CPack NuGet generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack NuGet generator may be used to create NuGet packages using -:module:`CPack`. The CPack NuGet generator is a :module:`CPack` generator thus -it uses the ``CPACK_XXX`` variables used by :module:`CPack`. - -The CPack NuGet generator has specific features which are controlled by the -specifics ``CPACK_NUGET_XXX`` variables. In the "one per group" mode -(see :variable:`CPACK_COMPONENTS_GROUPING`), ``<compName>`` placeholder -in the variables below would contain a group name (uppercased and turned into -a "C" identifier). - -List of CPack NuGet generator specific variables: - -.. variable:: CPACK_NUGET_COMPONENT_INSTALL - - Enable component packaging for CPack NuGet generator - - * Mandatory : NO - * Default : OFF - -.. variable:: CPACK_NUGET_PACKAGE_NAME - CPACK_NUGET_<compName>_PACKAGE_NAME - - The NUGET package name. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_NAME` - -.. variable:: CPACK_NUGET_PACKAGE_VERSION - CPACK_NUGET_<compName>_PACKAGE_VERSION - - The NuGet package version. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_VERSION` - -.. variable:: CPACK_NUGET_PACKAGE_DESCRIPTION - CPACK_NUGET_<compName>_PACKAGE_DESCRIPTION - - A long description of the package for UI display. - - * Mandatory : YES - * Default : - - :variable:`CPACK_COMPONENT_<compName>_DESCRIPTION`, - - ``CPACK_COMPONENT_GROUP_<groupName>_DESCRIPTION``, - - :variable:`CPACK_PACKAGE_DESCRIPTION` - -.. variable:: CPACK_NUGET_PACKAGE_AUTHORS - CPACK_NUGET_<compName>_PACKAGE_AUTHORS - - A comma-separated list of packages authors, matching the profile names - on nuget.org_. These are displayed in the NuGet Gallery on - nuget.org_ and are used to cross-reference packages by the same - authors. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_VENDOR` - -.. variable:: CPACK_NUGET_PACKAGE_TITLE - CPACK_NUGET_<compName>_PACKAGE_TITLE - - A human-friendly title of the package, typically used in UI displays - as on nuget.org_ and the Package Manager in Visual Studio. If not - specified, the package ID is used. - - * Mandatory : NO - * Default : - - :variable:`CPACK_COMPONENT_<compName>_DISPLAY_NAME`, - - ``CPACK_COMPONENT_GROUP_<groupName>_DISPLAY_NAME`` - -.. variable:: CPACK_NUGET_PACKAGE_OWNERS - CPACK_NUGET_<compName>_PACKAGE_OWNERS - - A comma-separated list of the package creators using profile names - on nuget.org_. This is often the same list as in authors, - and is ignored when uploading the package to nuget.org_. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_HOMEPAGE_URL - CPACK_NUGET_<compName>_PACKAGE_HOMEPAGE_URL - - A URL for the package's home page, often shown in UI displays as well - as nuget.org_. - - * Mandatory : NO - * Default : :variable:`CPACK_PACKAGE_HOMEPAGE_URL` - -.. variable:: CPACK_NUGET_PACKAGE_LICENSEURL - CPACK_NUGET_<compName>_PACKAGE_LICENSEURL - - A URL for the package's license, often shown in UI displays as well - as nuget.org_. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_ICONURL - CPACK_NUGET_<compName>_PACKAGE_ICONURL - - A URL for a 64x64 image with transparency background to use as the - icon for the package in UI display. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_DESCRIPTION_SUMMARY - CPACK_NUGET_<compName>_PACKAGE_DESCRIPTION_SUMMARY - - A short description of the package for UI display. If omitted, a - truncated version of description is used. - - * Mandatory : NO - * Default : :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY` - -.. variable:: CPACK_NUGET_PACKAGE_RELEASE_NOTES - CPACK_NUGET_<compName>_PACKAGE_RELEASE_NOTES - - A description of the changes made in this release of the package, - often used in UI like the Updates tab of the Visual Studio Package - Manager in place of the package description. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_COPYRIGHT - CPACK_NUGET_<compName>_PACKAGE_COPYRIGHT - - Copyright details for the package. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_TAGS - CPACK_NUGET_<compName>_PACKAGE_TAGS - - A space-delimited list of tags and keywords that describe the - package and aid discoverability of packages through search and - filtering. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_DEPENDENCIES - CPACK_NUGET_<compName>_PACKAGE_DEPENDENCIES - - A list of package dependencies. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_DEPENDENCIES_<dependency>_VERSION - CPACK_NUGET_<compName>_PACKAGE_DEPENDENCIES_<dependency>_VERSION - - A `version specification`_ for the particular dependency, where - ``<dependency>`` is an item of the dependency list (see above) - transformed with ``MAKE_C_IDENTIFIER`` function of :command:`string` - command. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_NUGET_PACKAGE_DEBUG - - Enable debug messages while executing CPack NuGet generator. - - * Mandatory : NO - * Default : OFF - - -.. _nuget.org: http://nuget.org -.. _version specification: https://docs.microsoft.com/en-us/nuget/reference/package-versioning#version-ranges-and-wildcards - -.. NuGet spec docs https://docs.microsoft.com/en-us/nuget/reference/nuspec
diff --git a/share/cmake-3.18/Help/cpack_gen/packagemaker.rst b/share/cmake-3.18/Help/cpack_gen/packagemaker.rst deleted file mode 100644 index c2a450e..0000000 --- a/share/cmake-3.18/Help/cpack_gen/packagemaker.rst +++ /dev/null
@@ -1,79 +0,0 @@ -CPack PackageMaker Generator ----------------------------- - -PackageMaker CPack generator (macOS). - -.. deprecated:: 3.17 - - Xcode no longer distributes the PackageMaker tools. - This CPack generator will be removed in a future version of CPack. - -Variables specific to CPack PackageMaker generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variable is specific to installers built on Mac -macOS using PackageMaker: - -.. variable:: CPACK_OSX_PACKAGE_VERSION - - The version of macOS that the resulting PackageMaker archive should be - compatible with. Different versions of macOS support different - features. For example, CPack can only build component-based installers for - macOS 10.4 or newer, and can only build installers that download - components on-the-fly for macOS 10.5 or newer. If left blank, this value - will be set to the minimum version of macOS that supports the requested - features. Set this variable to some value (e.g., 10.4) only if you want to - guarantee that your installer will work on that version of macOS, and - don't mind missing extra features available in the installer shipping with - later versions of macOS. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND - - Adds a background to Distribtion XML if specified. The value contains the - path to image in ``Resources`` directory. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_ALIGNMENT - - Adds an ``alignment`` attribute to the background in Distribution XML. - Refer to Apple documentation for valid values. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_SCALING - - Adds a ``scaling`` attribute to the background in Distribution XML. - Refer to Apple documentation for valid values. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_MIME_TYPE - - Adds a ``mime-type`` attribute to the background in Distribution XML. - The option contains MIME type of an image. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_UTI - - Adds an ``uti`` attribute to the background in Distribution XML. - The option contains UTI type of an image. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_DARKAQUA - - Adds a background for the Dark Aqua theme to Distribution XML if - specified. The value contains the path to image in ``Resources`` - directory. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_DARKAQUA_ALIGNMENT - - Does the same as :variable:`CPACK_PACKAGEMAKER_BACKGROUND_ALIGNMENT` option, - but for the dark theme. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_DARKAQUA_SCALING - - Does the same as :variable:`CPACK_PACKAGEMAKER_BACKGROUND_SCALING` option, - but for the dark theme. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_DARKAQUA_MIME_TYPE - - Does the same as :variable:`CPACK_PACKAGEMAKER_BACKGROUND_MIME_TYPE` option, - but for the dark theme. - -.. variable:: CPACK_PACKAGEMAKER_BACKGROUND_DARKAQUA_UTI - - Does the same as :variable:`CPACK_PACKAGEMAKER_BACKGROUND_UTI` option, - but for the dark theme.
diff --git a/share/cmake-3.18/Help/cpack_gen/productbuild.rst b/share/cmake-3.18/Help/cpack_gen/productbuild.rst deleted file mode 100644 index 82b79ae..0000000 --- a/share/cmake-3.18/Help/cpack_gen/productbuild.rst +++ /dev/null
@@ -1,118 +0,0 @@ -CPack productbuild Generator ----------------------------- - -productbuild CPack generator (macOS). - -Variables specific to CPack productbuild generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variable is specific to installers built on Mac -macOS using ProductBuild: - -.. variable:: CPACK_COMMAND_PRODUCTBUILD - - Path to the ``productbuild(1)`` command used to generate a product archive for - the macOS Installer or Mac App Store. This variable can be used to override - the automatically detected command (or specify its location if the - auto-detection fails to find it). - -.. variable:: CPACK_PRODUCTBUILD_IDENTITY_NAME - - Adds a digital signature to the resulting package. - - -.. variable:: CPACK_PRODUCTBUILD_KEYCHAIN_PATH - - Specify a specific keychain to search for the signing identity. - - -.. variable:: CPACK_COMMAND_PKGBUILD - - Path to the ``pkgbuild(1)`` command used to generate an macOS component package - on macOS. This variable can be used to override the automatically detected - command (or specify its location if the auto-detection fails to find it). - - -.. variable:: CPACK_PKGBUILD_IDENTITY_NAME - - Adds a digital signature to the resulting package. - - -.. variable:: CPACK_PKGBUILD_KEYCHAIN_PATH - - Specify a specific keychain to search for the signing identity. - - -.. variable:: CPACK_PREFLIGHT_<COMP>_SCRIPT - - Full path to a file that will be used as the ``preinstall`` script for the - named ``<COMP>`` component's package, where ``<COMP>`` is the uppercased - component name. No ``preinstall`` script is added if this variable is not - defined for a given component. - - -.. variable:: CPACK_POSTFLIGHT_<COMP>_SCRIPT - - Full path to a file that will be used as the ``postinstall`` script for the - named ``<COMP>`` component's package, where ``<COMP>`` is the uppercased - component name. No ``postinstall`` script is added if this variable is not - defined for a given component. - -.. variable:: CPACK_PRODUCTBUILD_RESOURCES_DIR - - If specified the productbuild generator copies files from this directory - (including subdirectories) to the ``Resources`` directory. This is done - before the :variable:`CPACK_RESOURCE_FILE_WELCOME`, - :variable:`CPACK_RESOURCE_FILE_README`, and - :variable:`CPACK_RESOURCE_FILE_LICENSE` files are copied. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND - - Adds a background to Distribtion XML if specified. The value contains the - path to image in ``Resources`` directory. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_ALIGNMENT - - Adds an ``alignment`` attribute to the background in Distribution XML. - Refer to Apple documentation for valid values. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_SCALING - - Adds a ``scaling`` attribute to the background in Distribution XML. - Refer to Apple documentation for valid values. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_MIME_TYPE - - Adds a ``mime-type`` attribute to the background in Distribution XML. - The option contains MIME type of an image. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_UTI - - Adds an ``uti`` attribute to the background in Distribution XML. - The option contains UTI type of an image. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_DARKAQUA - - Adds a background for the Dark Aqua theme to Distribution XML if - specified. The value contains the path to image in ``Resources`` - directory. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_DARKAQUA_ALIGNMENT - - Does the same as :variable:`CPACK_PRODUCTBUILD_BACKGROUND_ALIGNMENT` option, - but for the dark theme. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_DARKAQUA_SCALING - - Does the same as :variable:`CPACK_PRODUCTBUILD_BACKGROUND_SCALING` option, - but for the dark theme. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_DARKAQUA_MIME_TYPE - - Does the same as :variable:`CPACK_PRODUCTBUILD_BACKGROUND_MIME_TYPE` option, - but for the dark theme. - -.. variable:: CPACK_PRODUCTBUILD_BACKGROUND_DARKAQUA_UTI - - Does the same as :variable:`CPACK_PRODUCTBUILD_BACKGROUND_UTI` option, - but for the dark theme.
diff --git a/share/cmake-3.18/Help/cpack_gen/rpm.rst b/share/cmake-3.18/Help/cpack_gen/rpm.rst deleted file mode 100644 index ccb7ebd..0000000 --- a/share/cmake-3.18/Help/cpack_gen/rpm.rst +++ /dev/null
@@ -1,959 +0,0 @@ -CPack RPM Generator -------------------- - -The built in (binary) CPack RPM generator (Unix only) - -Variables specific to CPack RPM generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack RPM generator may be used to create RPM packages using :module:`CPack`. -The CPack RPM generator is a :module:`CPack` generator thus it uses the -``CPACK_XXX`` variables used by :module:`CPack`. - -The CPack RPM generator has specific features which are controlled by the specifics -``CPACK_RPM_XXX`` variables. - -``CPACK_RPM_<COMPONENT>_XXXX`` variables may be used in order to have -**component** specific values. Note however that ``<COMPONENT>`` refers to the -**grouping name** written in upper case. It may be either a component name or -a component GROUP name. Usually those variables correspond to RPM spec file -entities. One may find information about spec files here -http://www.rpm.org/wiki/Docs - -.. note:: - - `<COMPONENT>` part of variables is preferred to be in upper case (e.g. if - component is named ``foo`` then use ``CPACK_RPM_FOO_XXXX`` variable name format) - as is with other ``CPACK_<COMPONENT>_XXXX`` variables. - For the purposes of back compatibility (CMake/CPack version 3.5 and lower) - support for same cased component (e.g. ``fOo`` would be used as - ``CPACK_RPM_fOo_XXXX``) is still supported for variables defined in older - versions of CMake/CPack but is not guaranteed for variables that - will be added in the future. For the sake of back compatibility same cased - component variables also override upper cased versions where both are - present. - -Here are some CPack RPM generator wiki resources that are here for historic -reasons and are no longer maintained but may still prove useful: - - - https://gitlab.kitware.com/cmake/community/-/wikis/doc/cpack/Configuration - - https://gitlab.kitware.com/cmake/community/-/wikis/doc/cpack/PackageGenerators#rpm-unix-only - -List of CPack RPM generator specific variables: - -.. variable:: CPACK_RPM_COMPONENT_INSTALL - - Enable component packaging for CPack RPM generator - - * Mandatory : NO - * Default : OFF - - If enabled (``ON``) multiple packages are generated. By default - a single package containing files of all components is generated. - -.. variable:: CPACK_RPM_PACKAGE_SUMMARY - CPACK_RPM_<component>_PACKAGE_SUMMARY - - The RPM package summary. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_DESCRIPTION_SUMMARY` - -.. variable:: CPACK_RPM_PACKAGE_NAME - CPACK_RPM_<component>_PACKAGE_NAME - - The RPM package name. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_NAME` - -.. variable:: CPACK_RPM_FILE_NAME - CPACK_RPM_<component>_FILE_NAME - - Package file name. - - * Mandatory : YES - * Default : ``<CPACK_PACKAGE_FILE_NAME>[-<component>].rpm`` with spaces - replaced by '-' - - This may be set to ``RPM-DEFAULT`` to allow ``rpmbuild`` tool to generate package - file name by itself. - Alternatively provided package file name must end with ``.rpm`` suffix. - - .. note:: - - By using user provided spec file, rpm macro extensions such as for - generating ``debuginfo`` packages or by simply using multiple components more - than one rpm file may be generated, either from a single spec file or from - multiple spec files (each component execution produces its own spec file). - In such cases duplicate file names may occur as a result of this variable - setting or spec file content structure. Duplicate files get overwritten - and it is up to the packager to set the variables in a manner that will - prevent such errors. - -.. variable:: CPACK_RPM_MAIN_COMPONENT - - Main component that is packaged without component suffix. - - * Mandatory : NO - * Default : - - - This variable can be set to any component or group name so that component or - group rpm package is generated without component suffix in filename and - package name. - -.. variable:: CPACK_RPM_PACKAGE_EPOCH - - The RPM package epoch - - * Mandatory : No - * Default : - - - Optional number that should be incremented when changing versioning schemas - or fixing mistakes in the version numbers of older packages. - -.. variable:: CPACK_RPM_PACKAGE_VERSION - - The RPM package version. - - * Mandatory : YES - * Default : :variable:`CPACK_PACKAGE_VERSION` - -.. variable:: CPACK_RPM_PACKAGE_ARCHITECTURE - CPACK_RPM_<component>_PACKAGE_ARCHITECTURE - - The RPM package architecture. - - * Mandatory : YES - * Default : Native architecture output by ``uname -m`` - - This may be set to ``noarch`` if you know you are building a ``noarch`` package. - -.. variable:: CPACK_RPM_PACKAGE_RELEASE - - The RPM package release. - - * Mandatory : YES - * Default : 1 - - This is the numbering of the RPM package itself, i.e. the version of the - packaging and not the version of the content (see - :variable:`CPACK_RPM_PACKAGE_VERSION`). One may change the default value if - the previous packaging was buggy and/or you want to put here a fancy Linux - distro specific numbering. - -.. note:: - - This is the string that goes into the RPM ``Release:`` field. Some distros - (e.g. Fedora, CentOS) require ``1%{?dist}`` format and not just a number. - ``%{?dist}`` part can be added by setting :variable:`CPACK_RPM_PACKAGE_RELEASE_DIST`. - -.. variable:: CPACK_RPM_PACKAGE_RELEASE_DIST - - The dist tag that is added RPM ``Release:`` field. - - * Mandatory : NO - * Default : OFF - - This is the reported ``%{dist}`` tag from the current distribution or empty - ``%{dist}`` if RPM macro is not set. If this variable is set then RPM - ``Release:`` field value is set to ``${CPACK_RPM_PACKAGE_RELEASE}%{?dist}``. - -.. variable:: CPACK_RPM_PACKAGE_LICENSE - - The RPM package license policy. - - * Mandatory : YES - * Default : "unknown" - -.. variable:: CPACK_RPM_PACKAGE_GROUP - CPACK_RPM_<component>_PACKAGE_GROUP - - The RPM package group. - - * Mandatory : YES - * Default : "unknown" - -.. variable:: CPACK_RPM_PACKAGE_VENDOR - - The RPM package vendor. - - * Mandatory : YES - * Default : CPACK_PACKAGE_VENDOR if set or "unknown" - -.. variable:: CPACK_RPM_PACKAGE_URL - CPACK_RPM_<component>_PACKAGE_URL - - The projects URL. - - * Mandatory : NO - * Default : :variable:`CMAKE_PROJECT_HOMEPAGE_URL` - -.. variable:: CPACK_RPM_PACKAGE_DESCRIPTION - CPACK_RPM_<component>_PACKAGE_DESCRIPTION - - RPM package description. - - * Mandatory : YES - * Default : :variable:`CPACK_COMPONENT_<compName>_DESCRIPTION` (component - based installers only) if set, :variable:`CPACK_PACKAGE_DESCRIPTION_FILE` - if set or "no package description available" - -.. variable:: CPACK_RPM_COMPRESSION_TYPE - - RPM compression type. - - * Mandatory : NO - * Default : - - - May be used to override RPM compression type to be used to build the - RPM. For example some Linux distribution now default to ``lzma`` or ``xz`` - compression whereas older cannot use such RPM. Using this one can enforce - compression type to be used. - - Possible values are: - - - lzma - - xz - - bzip2 - - gzip - -.. variable:: CPACK_RPM_PACKAGE_AUTOREQ - CPACK_RPM_<component>_PACKAGE_AUTOREQ - - RPM spec autoreq field. - - * Mandatory : NO - * Default : - - - May be used to enable (``1``, ``yes``) or disable (``0``, ``no``) automatic - shared libraries dependency detection. Dependencies are added to requires list. - - .. note:: - - By default automatic dependency detection is enabled by rpm generator. - -.. variable:: CPACK_RPM_PACKAGE_AUTOPROV - CPACK_RPM_<component>_PACKAGE_AUTOPROV - - RPM spec autoprov field. - - * Mandatory : NO - * Default : - - - May be used to enable (``1``, ``yes``) or disable (``0``, ``no``) - automatic listing of shared libraries that are provided by the package. - Shared libraries are added to provides list. - - .. note:: - - By default automatic provides detection is enabled by rpm generator. - -.. variable:: CPACK_RPM_PACKAGE_AUTOREQPROV - CPACK_RPM_<component>_PACKAGE_AUTOREQPROV - - RPM spec autoreqprov field. - - * Mandatory : NO - * Default : - - - Variable enables/disables autoreq and autoprov at the same time. - See :variable:`CPACK_RPM_PACKAGE_AUTOREQ` and - :variable:`CPACK_RPM_PACKAGE_AUTOPROV` for more details. - - .. note:: - - By default automatic detection feature is enabled by rpm. - -.. variable:: CPACK_RPM_PACKAGE_REQUIRES - CPACK_RPM_<component>_PACKAGE_REQUIRES - - RPM spec requires field. - - * Mandatory : NO - * Default : - - - May be used to set RPM dependencies (requires). Note that you must enclose - the complete requires string between quotes, for example:: - - set(CPACK_RPM_PACKAGE_REQUIRES "python >= 2.5.0, cmake >= 2.8") - - The required package list of an RPM file could be printed with:: - - rpm -qp --requires file.rpm - -.. variable:: CPACK_RPM_PACKAGE_CONFLICTS - CPACK_RPM_<component>_PACKAGE_CONFLICTS - - RPM spec conflicts field. - - * Mandatory : NO - * Default : - - - May be used to set negative RPM dependencies (conflicts). Note that you must - enclose the complete requires string between quotes, for example:: - - set(CPACK_RPM_PACKAGE_CONFLICTS "libxml2") - - The conflicting package list of an RPM file could be printed with:: - - rpm -qp --conflicts file.rpm - -.. variable:: CPACK_RPM_PACKAGE_REQUIRES_PRE - CPACK_RPM_<component>_PACKAGE_REQUIRES_PRE - - RPM spec requires(pre) field. - - * Mandatory : NO - * Default : - - - May be used to set RPM preinstall dependencies (requires(pre)). Note that - you must enclose the complete requires string between quotes, for example:: - - set(CPACK_RPM_PACKAGE_REQUIRES_PRE "shadow-utils, initscripts") - -.. variable:: CPACK_RPM_PACKAGE_REQUIRES_POST - CPACK_RPM_<component>_PACKAGE_REQUIRES_POST - - RPM spec requires(post) field. - - * Mandatory : NO - * Default : - - - May be used to set RPM postinstall dependencies (requires(post)). Note that - you must enclose the complete requires string between quotes, for example:: - - set(CPACK_RPM_PACKAGE_REQUIRES_POST "shadow-utils, initscripts") - -.. variable:: CPACK_RPM_PACKAGE_REQUIRES_POSTUN - CPACK_RPM_<component>_PACKAGE_REQUIRES_POSTUN - - RPM spec requires(postun) field. - - * Mandatory : NO - * Default : - - - May be used to set RPM postuninstall dependencies (requires(postun)). Note - that you must enclose the complete requires string between quotes, for - example:: - - set(CPACK_RPM_PACKAGE_REQUIRES_POSTUN "shadow-utils, initscripts") - -.. variable:: CPACK_RPM_PACKAGE_REQUIRES_PREUN - CPACK_RPM_<component>_PACKAGE_REQUIRES_PREUN - - RPM spec requires(preun) field. - - * Mandatory : NO - * Default : - - - May be used to set RPM preuninstall dependencies (requires(preun)). Note that - you must enclose the complete requires string between quotes, for example:: - - set(CPACK_RPM_PACKAGE_REQUIRES_PREUN "shadow-utils, initscripts") - -.. variable:: CPACK_RPM_PACKAGE_SUGGESTS - CPACK_RPM_<component>_PACKAGE_SUGGESTS - - RPM spec suggest field. - - * Mandatory : NO - * Default : - - - May be used to set weak RPM dependencies (suggests). Note that you must - enclose the complete requires string between quotes. - -.. variable:: CPACK_RPM_PACKAGE_PROVIDES - CPACK_RPM_<component>_PACKAGE_PROVIDES - - RPM spec provides field. - - * Mandatory : NO - * Default : - - - May be used to set RPM dependencies (provides). The provided package list - of an RPM file could be printed with:: - - rpm -qp --provides file.rpm - -.. variable:: CPACK_RPM_PACKAGE_OBSOLETES - CPACK_RPM_<component>_PACKAGE_OBSOLETES - - RPM spec obsoletes field. - - * Mandatory : NO - * Default : - - - May be used to set RPM packages that are obsoleted by this one. - -.. variable:: CPACK_RPM_PACKAGE_RELOCATABLE - - build a relocatable RPM. - - * Mandatory : NO - * Default : CPACK_PACKAGE_RELOCATABLE - - If this variable is set to TRUE or ON, the CPack RPM generator will try - to build a relocatable RPM package. A relocatable RPM may - be installed using:: - - rpm --prefix or --relocate - - in order to install it at an alternate place see rpm(8). Note that - currently this may fail if :variable:`CPACK_SET_DESTDIR` is set to ``ON``. If - :variable:`CPACK_SET_DESTDIR` is set then you will get a warning message but - if there is file installed with absolute path you'll get unexpected behavior. - -.. variable:: CPACK_RPM_SPEC_INSTALL_POST - - Deprecated - use :variable:`CPACK_RPM_SPEC_MORE_DEFINE` instead. - - * Mandatory : NO - * Default : - - * Deprecated: YES - - May be used to override the ``__spec_install_post`` section within the - generated spec file. This affects the install step during package creation, - not during package installation. For adding operations to be performed - during package installation, use - :variable:`CPACK_RPM_POST_INSTALL_SCRIPT_FILE` instead. - -.. variable:: CPACK_RPM_SPEC_MORE_DEFINE - - RPM extended spec definitions lines. - - * Mandatory : NO - * Default : - - - May be used to add any ``%define`` lines to the generated spec file. An - example of its use is to prevent stripping of executables (but note that - this may also disable other default post install processing):: - - set(CPACK_RPM_SPEC_MORE_DEFINE "%define __spec_install_post /bin/true") - -.. variable:: CPACK_RPM_PACKAGE_DEBUG - - Toggle CPack RPM generator debug output. - - * Mandatory : NO - * Default : - - - May be set when invoking cpack in order to trace debug information - during CPack RPM run. For example you may launch CPack like this:: - - cpack -D CPACK_RPM_PACKAGE_DEBUG=1 -G RPM - -.. variable:: CPACK_RPM_USER_BINARY_SPECFILE - CPACK_RPM_<componentName>_USER_BINARY_SPECFILE - - A user provided spec file. - - * Mandatory : NO - * Default : - - - May be set by the user in order to specify a USER binary spec file - to be used by the CPack RPM generator instead of generating the file. - The specified file will be processed by configure_file( @ONLY). - -.. variable:: CPACK_RPM_GENERATE_USER_BINARY_SPECFILE_TEMPLATE - - Spec file template. - - * Mandatory : NO - * Default : - - - If set CPack will generate a template for USER specified binary - spec file and stop with an error. For example launch CPack like this:: - - cpack -D CPACK_RPM_GENERATE_USER_BINARY_SPECFILE_TEMPLATE=1 -G RPM - - The user may then use this file in order to hand-craft is own - binary spec file which may be used with - :variable:`CPACK_RPM_USER_BINARY_SPECFILE`. - -.. variable:: CPACK_RPM_PRE_INSTALL_SCRIPT_FILE - CPACK_RPM_PRE_UNINSTALL_SCRIPT_FILE - CPACK_RPM_PRE_TRANS_SCRIPT_FILE - - Path to file containing pre install/uninstall/transaction script. - - * Mandatory : NO - * Default : - - - May be used to embed a pre installation/uninstallation/transaction script in the spec file. - The referred script file (or both) will be read and directly - put after the ``%pre`` or ``%preun`` section - If :variable:`CPACK_RPM_COMPONENT_INSTALL` is set to ON the install/uninstall/transaction - script for each component can be overridden with - ``CPACK_RPM_<COMPONENT>_PRE_INSTALL_SCRIPT_FILE``, - ``CPACK_RPM_<COMPONENT>_PRE_UNINSTALL_SCRIPT_FILE``, and - ``CPACK_RPM_<COMPONENT>_PRE_TRANS_SCRIPT_FILE`` - One may verify which scriptlet has been included with:: - - rpm -qp --scripts package.rpm - -.. variable:: CPACK_RPM_POST_INSTALL_SCRIPT_FILE - CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE - CPACK_RPM_POST_TRANS_SCRIPT_FILE - - Path to file containing post install/uninstall/transaction script. - - * Mandatory : NO - * Default : - - - May be used to embed a post installation/uninstallation/transaction script in the spec file. - The referred script file (or both) will be read and directly - put after the ``%post`` or ``%postun`` section. - If :variable:`CPACK_RPM_COMPONENT_INSTALL` is set to ON the install/uninstall/transaction - script for each component can be overridden with - ``CPACK_RPM_<COMPONENT>_POST_INSTALL_SCRIPT_FILE``, - ``CPACK_RPM_<COMPONENT>_POST_UNINSTALL_SCRIPT_FILE``, and - ``CPACK_RPM_<COMPONENT>_POST_TRANS_SCRIPT_FILE`` - One may verify which scriptlet has been included with:: - - rpm -qp --scripts package.rpm - -.. variable:: CPACK_RPM_USER_FILELIST - CPACK_RPM_<COMPONENT>_USER_FILELIST - - * Mandatory : NO - * Default : - - - May be used to explicitly specify ``%(<directive>)`` file line - in the spec file. Like ``%config(noreplace)`` or any other directive - that be found in the ``%files`` section. You can have multiple directives - per line, as in ``%attr(600,root,root) %config(noreplace)``. Since - the CPack RPM generator is generating the list of files (and directories) the - user specified files of the ``CPACK_RPM_<COMPONENT>_USER_FILELIST`` list will - be removed from the generated list. If referring to directories do - not add a trailing slash. - -.. variable:: CPACK_RPM_CHANGELOG_FILE - - RPM changelog file. - - * Mandatory : NO - * Default : - - - May be used to embed a changelog in the spec file. - The referred file will be read and directly put after the ``%changelog`` - section. - -.. variable:: CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST - - list of path to be excluded. - - * Mandatory : NO - * Default : /etc /etc/init.d /usr /usr/bin /usr/include /usr/lib - /usr/libx32 /usr/lib64 /usr/share /usr/share/aclocal - /usr/share/doc - - May be used to exclude path (directories or files) from the auto-generated - list of paths discovered by CPack RPM. The default value contains a - reasonable set of values if the variable is not defined by the user. If the - variable is defined by the user then the CPack RPM generator will NOT any of - the default path. If you want to add some path to the default list then you - can use :variable:`CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST_ADDITION` variable. - -.. variable:: CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST_ADDITION - - additional list of path to be excluded. - - * Mandatory : NO - * Default : - - - May be used to add more exclude path (directories or files) from the initial - default list of excluded paths. See - :variable:`CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST`. - -.. variable:: CPACK_RPM_RELOCATION_PATHS - - Packages relocation paths list. - - * Mandatory : NO - * Default : - - - May be used to specify more than one relocation path per relocatable RPM. - Variable contains a list of relocation paths that if relative are prefixed - by the value of :variable:`CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX` or by the - value of :variable:`CPACK_PACKAGING_INSTALL_PREFIX` if the component version - is not provided. - Variable is not component based as its content can be used to set a different - path prefix for e.g. binary dir and documentation dir at the same time. - Only prefixes that are required by a certain component are added to that - component - component must contain at least one file/directory/symbolic link - with :variable:`CPACK_RPM_RELOCATION_PATHS` prefix for a certain relocation - path to be added. Package will not contain any relocation paths if there are - no files/directories/symbolic links on any of the provided prefix locations. - Packages that either do not contain any relocation paths or contain - files/directories/symbolic links that are outside relocation paths print - out an ``AUTHOR_WARNING`` that RPM will be partially relocatable. - -.. variable:: CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX - - Per component relocation path install prefix. - - * Mandatory : NO - * Default : CPACK_PACKAGING_INSTALL_PREFIX - - May be used to set per component :variable:`CPACK_PACKAGING_INSTALL_PREFIX` - for relocatable RPM packages. - -.. variable:: CPACK_RPM_NO_INSTALL_PREFIX_RELOCATION - CPACK_RPM_NO_<COMPONENT>_INSTALL_PREFIX_RELOCATION - - Removal of default install prefix from relocation paths list. - - * Mandatory : NO - * Default : CPACK_PACKAGING_INSTALL_PREFIX or CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX - are treated as one of relocation paths - - May be used to remove CPACK_PACKAGING_INSTALL_PREFIX and CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX - from relocatable RPM prefix paths. - -.. variable:: CPACK_RPM_ADDITIONAL_MAN_DIRS - - * Mandatory : NO - * Default : - - - May be used to set additional man dirs that could potentially be compressed - by brp-compress RPM macro. Variable content must be a list of regular - expressions that point to directories containing man files or to man files - directly. Note that in order to compress man pages a path must also be - present in brp-compress RPM script and that brp-compress script must be - added to RPM configuration by the operating system. - - Regular expressions that are added by default were taken from brp-compress - RPM macro: - - - /usr/man/man.* - - /usr/man/.*/man.* - - /usr/info.* - - /usr/share/man/man.* - - /usr/share/man/.*/man.* - - /usr/share/info.* - - /usr/kerberos/man.* - - /usr/X11R6/man/man.* - - /usr/lib/perl5/man/man.* - - /usr/share/doc/.*/man/man.* - - /usr/lib/.*/man/man.* - -.. variable:: CPACK_RPM_DEFAULT_USER - CPACK_RPM_<compName>_DEFAULT_USER - - default user ownership of RPM content - - * Mandatory : NO - * Default : root - - Value should be user name and not UID. - Note that <compName> must be in upper-case. - -.. variable:: CPACK_RPM_DEFAULT_GROUP - CPACK_RPM_<compName>_DEFAULT_GROUP - - default group ownership of RPM content - - * Mandatory : NO - * Default : root - - Value should be group name and not GID. - Note that <compName> must be in upper-case. - -.. variable:: CPACK_RPM_DEFAULT_FILE_PERMISSIONS - CPACK_RPM_<compName>_DEFAULT_FILE_PERMISSIONS - - default permissions used for packaged files - - * Mandatory : NO - * Default : - (system default) - - Accepted values are lists with ``PERMISSIONS``. Valid permissions - are: - - - OWNER_READ - - OWNER_WRITE - - OWNER_EXECUTE - - GROUP_READ - - GROUP_WRITE - - GROUP_EXECUTE - - WORLD_READ - - WORLD_WRITE - - WORLD_EXECUTE - - Note that <compName> must be in upper-case. - -.. variable:: CPACK_RPM_DEFAULT_DIR_PERMISSIONS - CPACK_RPM_<compName>_DEFAULT_DIR_PERMISSIONS - - default permissions used for packaged directories - - * Mandatory : NO - * Default : - (system default) - - Accepted values are lists with PERMISSIONS. Valid permissions - are the same as for :variable:`CPACK_RPM_DEFAULT_FILE_PERMISSIONS`. - Note that <compName> must be in upper-case. - -.. variable:: CPACK_RPM_INSTALL_WITH_EXEC - - force execute permissions on programs and shared libraries - - * Mandatory : NO - * Default : - (system default) - - Force set owner, group and world execute permissions on programs and shared - libraries. This can be used for creating valid rpm packages on systems such - as Debian where shared libraries do not have execute permissions set. - -.. note:: - - Programs and shared libraries without execute permissions are ignored during - separation of debug symbols from the binary for debuginfo packages. - -Packaging of Symbolic Links -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The CPack RPM generator supports packaging of symbolic links:: - - execute_process(COMMAND ${CMAKE_COMMAND} - -E create_symlink <relative_path_location> <symlink_name>) - install(FILES ${CMAKE_CURRENT_BINARY_DIR}/<symlink_name> - DESTINATION <symlink_location> COMPONENT libraries) - -Symbolic links will be optimized (paths will be shortened if possible) -before being added to the package or if multiple relocation paths are -detected, a post install symlink relocation script will be generated. - -Symbolic links may point to locations that are not packaged by the same -package (either a different component or even not packaged at all) but -those locations will be treated as if they were a part of the package -while determining if symlink should be either created or present in a -post install script - depending on relocation paths. - -Symbolic links that point to locations outside packaging path produce a -warning and are treated as non relocatable permanent symbolic links. - -Currently there are a few limitations though: - -* For component based packaging component interdependency is not checked - when processing symbolic links. Symbolic links pointing to content of - a different component are treated the same way as if pointing to location - that will not be packaged. - -* Symbolic links pointing to a location through one or more intermediate - symbolic links will not be handled differently - if the intermediate - symbolic link(s) is also on a relocatable path, relocating it during - package installation may cause initial symbolic link to point to an - invalid location. - -Packaging of debug information -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Debuginfo packages contain debug symbols and sources for debugging packaged -binaries. - -Debuginfo RPM packaging has its own set of variables: - -.. variable:: CPACK_RPM_DEBUGINFO_PACKAGE - CPACK_RPM_<component>_DEBUGINFO_PACKAGE - - Enable generation of debuginfo RPM package(s). - - * Mandatory : NO - * Default : OFF - -.. note:: - - Binaries must contain debug symbols before packaging so use either ``Debug`` - or ``RelWithDebInfo`` for :variable:`CMAKE_BUILD_TYPE` variable value. - -.. note:: - - Packages generated from packages without binary files, with binary files but - without execute permissions or without debug symbols will cause packaging - termination. - -.. variable:: CPACK_BUILD_SOURCE_DIRS - - Provides locations of root directories of source files from which binaries - were built. - - * Mandatory : YES if :variable:`CPACK_RPM_DEBUGINFO_PACKAGE` is set - * Default : - - -.. note:: - - For CMake project :variable:`CPACK_BUILD_SOURCE_DIRS` is set by default to - point to :variable:`CMAKE_SOURCE_DIR` and :variable:`CMAKE_BINARY_DIR` paths. - -.. note:: - - Sources with path prefixes that do not fall under any location provided with - :variable:`CPACK_BUILD_SOURCE_DIRS` will not be present in debuginfo package. - -.. variable:: CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX - CPACK_RPM_<component>_BUILD_SOURCE_DIRS_PREFIX - - Prefix of location where sources will be placed during package installation. - - * Mandatory : YES if :variable:`CPACK_RPM_DEBUGINFO_PACKAGE` is set - * Default : "/usr/src/debug/<CPACK_PACKAGE_FILE_NAME>" and - for component packaging "/usr/src/debug/<CPACK_PACKAGE_FILE_NAME>-<component>" - -.. note:: - - Each source path prefix is additionally suffixed by ``src_<index>`` where - index is index of the path used from :variable:`CPACK_BUILD_SOURCE_DIRS` - variable. This produces ``<CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX>/src_<index>`` - replacement path. - Limitation is that replaced path part must be shorter or of equal - length than the length of its replacement. If that is not the case either - :variable:`CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX` variable has to be set to - a shorter path or source directories must be placed on a longer path. - -.. variable:: CPACK_RPM_DEBUGINFO_EXCLUDE_DIRS - - Directories containing sources that should be excluded from debuginfo packages. - - * Mandatory : NO - * Default : "/usr /usr/src /usr/src/debug" - - Listed paths are owned by other RPM packages and should therefore not be - deleted on debuginfo package uninstallation. - -.. variable:: CPACK_RPM_DEBUGINFO_EXCLUDE_DIRS_ADDITION - - Paths that should be appended to :variable:`CPACK_RPM_DEBUGINFO_EXCLUDE_DIRS` - for exclusion. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_RPM_DEBUGINFO_SINGLE_PACKAGE - - Create a single debuginfo package even if components packaging is set. - - * Mandatory : NO - * Default : OFF - - When this variable is enabled it produces a single debuginfo package even if - component packaging is enabled. - - When using this feature in combination with components packaging and there is - more than one component this variable requires :variable:`CPACK_RPM_MAIN_COMPONENT` - to be set. - -.. note:: - - If none of the :variable:`CPACK_RPM_<component>_DEBUGINFO_PACKAGE` variables - is set then :variable:`CPACK_RPM_DEBUGINFO_PACKAGE` is automatically set to - ``ON`` when :variable:`CPACK_RPM_DEBUGINFO_SINGLE_PACKAGE` is set. - -.. variable:: CPACK_RPM_DEBUGINFO_FILE_NAME - CPACK_RPM_<component>_DEBUGINFO_FILE_NAME - - Debuginfo package file name. - - * Mandatory : NO - * Default : rpmbuild tool generated package file name - - Alternatively provided debuginfo package file name must end with ``.rpm`` - suffix and should differ from file names of other generated packages. - - Variable may contain ``@cpack_component@`` placeholder which will be - replaced by component name if component packaging is enabled otherwise it - deletes the placeholder. - - Setting the variable to ``RPM-DEFAULT`` may be used to explicitly set - filename generation to default. - -.. note:: - - :variable:`CPACK_RPM_FILE_NAME` also supports rpmbuild tool generated package - file name - disabled by default but can be enabled by setting the variable to - ``RPM-DEFAULT``. - -Packaging of sources (SRPM) -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -SRPM packaging is enabled by setting :variable:`CPACK_RPM_PACKAGE_SOURCES` -variable while usually using :variable:`CPACK_INSTALLED_DIRECTORIES` variable -to provide directory containing CMakeLists.txt and source files. - -For CMake projects SRPM package would be produced by executing:: - - cpack -G RPM --config ./CPackSourceConfig.cmake - -.. note:: - - Produced SRPM package is expected to be built with :manual:`cmake(1)` executable - and packaged with :manual:`cpack(1)` executable so CMakeLists.txt has to be - located in root source directory and must be able to generate binary rpm - packages by executing ``cpack -G`` command. The two executables as well as - rpmbuild must also be present when generating binary rpm packages from the - produced SRPM package. - -Once the SRPM package is generated it can be used to generate binary packages -by creating a directory structure for rpm generation and executing rpmbuild -tool:: - - mkdir -p build_dir/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS} - rpmbuild --define "_topdir <path_to_build_dir>" --rebuild <SRPM_file_name> - -Generated packages will be located in build_dir/RPMS directory or its sub -directories. - -.. note:: - - SRPM package internally uses CPack/RPM generator to generate binary packages - so CMakeScripts.txt can decide during the SRPM to binary rpm generation step - what content the package(s) should have as well as how they should be packaged - (monolithic or components). CMake can decide this for e.g. by reading environment - variables set by the package manager before starting the process of generating - binary rpm packages. This way a single SRPM package can be used to produce - different binary rpm packages on different platforms depending on the platform's - packaging rules. - -Source RPM packaging has its own set of variables: - -.. variable:: CPACK_RPM_PACKAGE_SOURCES - - Should the content be packaged as a source rpm (default is binary rpm). - - * Mandatory : NO - * Default : OFF - -.. note:: - - For cmake projects :variable:`CPACK_RPM_PACKAGE_SOURCES` variable is set - to ``OFF`` in CPackConfig.cmake and ``ON`` in CPackSourceConfig.cmake - generated files. - -.. variable:: CPACK_RPM_SOURCE_PKG_BUILD_PARAMS - - Additional command-line parameters provided to :manual:`cmake(1)` executable. - - * Mandatory : NO - * Default : - - -.. variable:: CPACK_RPM_SOURCE_PKG_PACKAGING_INSTALL_PREFIX - - Packaging install prefix that would be provided in :variable:`CPACK_PACKAGING_INSTALL_PREFIX` - variable for producing binary RPM packages. - - * Mandatory : YES - * Default : "/" - -.. VARIABLE:: CPACK_RPM_BUILDREQUIRES - - List of source rpm build dependencies. - - * Mandatory : NO - * Default : - - - May be used to set source RPM build dependencies (BuildRequires). Note that - you must enclose the complete build requirements string between quotes, for - example:: - - set(CPACK_RPM_BUILDREQUIRES "python >= 2.5.0, cmake >= 2.8")
diff --git a/share/cmake-3.18/Help/cpack_gen/wix.rst b/share/cmake-3.18/Help/cpack_gen/wix.rst deleted file mode 100644 index 7fb5a12..0000000 --- a/share/cmake-3.18/Help/cpack_gen/wix.rst +++ /dev/null
@@ -1,288 +0,0 @@ -CPack WIX Generator -------------------- - -CPack WIX generator specific options - -Variables specific to CPack WIX generator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variables are specific to the installers built on -Windows using WiX. - -.. variable:: CPACK_WIX_UPGRADE_GUID - - Upgrade GUID (``Product/@UpgradeCode``) - - Will be automatically generated unless explicitly provided. - - It should be explicitly set to a constant generated globally unique - identifier (GUID) to allow your installers to replace existing - installations that use the same GUID. - - You may for example explicitly set this variable in your - CMakeLists.txt to the value that has been generated per default. You - should not use GUIDs that you did not generate yourself or which may - belong to other projects. - - A GUID shall have the following fixed length syntax:: - - XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX - - (each X represents an uppercase hexadecimal digit) - -.. variable:: CPACK_WIX_PRODUCT_GUID - - Product GUID (``Product/@Id``) - - Will be automatically generated unless explicitly provided. - - If explicitly provided this will set the Product Id of your installer. - - The installer will abort if it detects a pre-existing installation that - uses the same GUID. - - The GUID shall use the syntax described for CPACK_WIX_UPGRADE_GUID. - -.. variable:: CPACK_WIX_LICENSE_RTF - - RTF License File - - If CPACK_RESOURCE_FILE_LICENSE has an .rtf extension it is used as-is. - - If CPACK_RESOURCE_FILE_LICENSE has an .txt extension it is implicitly - converted to RTF by the WIX Generator. - The expected encoding of the .txt file is UTF-8. - - With CPACK_WIX_LICENSE_RTF you can override the license file used by the - WIX Generator in case CPACK_RESOURCE_FILE_LICENSE is in an unsupported - format or the .txt -> .rtf conversion does not work as expected. - -.. variable:: CPACK_WIX_PRODUCT_ICON - - The Icon shown next to the program name in Add/Remove programs. - - If set, this icon is used in place of the default icon. - -.. variable:: CPACK_WIX_UI_REF - - This variable allows you to override the Id of the ``<UIRef>`` element - in the WiX template. - - The default is ``WixUI_InstallDir`` in case no CPack components have - been defined and ``WixUI_FeatureTree`` otherwise. - -.. variable:: CPACK_WIX_UI_BANNER - - The bitmap will appear at the top of all installer pages other than the - welcome and completion dialogs. - - If set, this image will replace the default banner image. - - This image must be 493 by 58 pixels. - -.. variable:: CPACK_WIX_UI_DIALOG - - Background bitmap used on the welcome and completion dialogs. - - If this variable is set, the installer will replace the default dialog - image. - - This image must be 493 by 312 pixels. - -.. variable:: CPACK_WIX_PROGRAM_MENU_FOLDER - - Start menu folder name for launcher. - - If this variable is not set, it will be initialized with CPACK_PACKAGE_NAME - - If this variable is set to ``.``, then application shortcuts will be - created directly in the start menu and the uninstaller shortcut will be - omitted. - -.. variable:: CPACK_WIX_CULTURES - - Language(s) of the installer - - Languages are compiled into the WixUI extension library. To use them, - simply provide the name of the culture. If you specify more than one - culture identifier in a comma or semicolon delimited list, the first one - that is found will be used. You can find a list of supported languages at: - http://wix.sourceforge.net/manual-wix3/WixUI_localization.htm - -.. variable:: CPACK_WIX_TEMPLATE - - Template file for WiX generation - - If this variable is set, the specified template will be used to generate - the WiX wxs file. This should be used if further customization of the - output is required. - - If this variable is not set, the default MSI template included with CMake - will be used. - -.. variable:: CPACK_WIX_PATCH_FILE - - Optional list of XML files with fragments to be inserted into - generated WiX sources - - This optional variable can be used to specify an XML file that the - WIX generator will use to inject fragments into its generated - source files. - - Patch files understood by the CPack WIX generator - roughly follow this RELAX NG compact schema: - - .. code-block:: none - - start = CPackWiXPatch - - CPackWiXPatch = element CPackWiXPatch { CPackWiXFragment* } - - CPackWiXFragment = element CPackWiXFragment - { - attribute Id { string }, - fragmentContent* - } - - fragmentContent = element * - CPackWiXFragment - { - (attribute * { text } | text | fragmentContent)* - } - - Currently fragments can be injected into most - Component, File, Directory and Feature elements. - - The following additional special Ids can be used: - - * ``#PRODUCT`` for the ``<Product>`` element. - * ``#PRODUCTFEATURE`` for the root ``<Feature>`` element. - - The following example illustrates how this works. - - Given that the WIX generator creates the following XML element: - - .. code-block:: xml - - <Component Id="CM_CP_applications.bin.my_libapp.exe" Guid="*"/> - - The following XML patch file may be used to inject an Environment element - into it: - - .. code-block:: xml - - <CPackWiXPatch> - <CPackWiXFragment Id="CM_CP_applications.bin.my_libapp.exe"> - <Environment Id="MyEnvironment" Action="set" - Name="MyVariableName" Value="MyVariableValue"/> - </CPackWiXFragment> - </CPackWiXPatch> - -.. variable:: CPACK_WIX_EXTRA_SOURCES - - Extra WiX source files - - This variable provides an optional list of extra WiX source files (.wxs) - that should be compiled and linked. The full path to source files is - required. - -.. variable:: CPACK_WIX_EXTRA_OBJECTS - - Extra WiX object files or libraries - - This variable provides an optional list of extra WiX object (.wixobj) - and/or WiX library (.wixlib) files. The full path to objects and libraries - is required. - -.. variable:: CPACK_WIX_EXTENSIONS - - This variable provides a list of additional extensions for the WiX - tools light and candle. - -.. variable:: CPACK_WIX_<TOOL>_EXTENSIONS - - This is the tool specific version of CPACK_WIX_EXTENSIONS. - ``<TOOL>`` can be either LIGHT or CANDLE. - -.. variable:: CPACK_WIX_<TOOL>_EXTRA_FLAGS - - This list variable allows you to pass additional - flags to the WiX tool ``<TOOL>``. - - Use it at your own risk. - Future versions of CPack may generate flags which may be in conflict - with your own flags. - - ``<TOOL>`` can be either LIGHT or CANDLE. - -.. variable:: CPACK_WIX_CMAKE_PACKAGE_REGISTRY - - If this variable is set the generated installer will create - an entry in the windows registry key - ``HKEY_LOCAL_MACHINE\Software\Kitware\CMake\Packages\<PackageName>`` - The value for ``<PackageName>`` is provided by this variable. - - Assuming you also install a CMake configuration file this will - allow other CMake projects to find your package with - the :command:`find_package` command. - -.. variable:: CPACK_WIX_PROPERTY_<PROPERTY> - - This variable can be used to provide a value for - the Windows Installer property ``<PROPERTY>`` - - The following list contains some example properties that can be used to - customize information under - "Programs and Features" (also known as "Add or Remove Programs") - - * ARPCOMMENTS - Comments - * ARPHELPLINK - Help and support information URL - * ARPURLINFOABOUT - General information URL - * ARPURLUPDATEINFO - Update information URL - * ARPHELPTELEPHONE - Help and support telephone number - * ARPSIZE - Size (in kilobytes) of the application - -.. variable:: CPACK_WIX_ROOT_FEATURE_TITLE - - Sets the name of the root install feature in the WIX installer. Same as - CPACK_COMPONENT_<compName>_DISPLAY_NAME for components. - -.. variable:: CPACK_WIX_ROOT_FEATURE_DESCRIPTION - - Sets the description of the root install feature in the WIX installer. Same as - CPACK_COMPONENT_<compName>_DESCRIPTION for components. - -.. variable:: CPACK_WIX_SKIP_PROGRAM_FOLDER - - If this variable is set to true, the default install location - of the generated package will be CPACK_PACKAGE_INSTALL_DIRECTORY directly. - The install location will not be located relatively below - ProgramFiles or ProgramFiles64. - - .. note:: - Installers created with this feature do not take differences - between the system on which the installer is created - and the system on which the installer might be used into account. - - It is therefore possible that the installer e.g. might try to install - onto a drive that is unavailable or unintended or a path that does not - follow the localization or convention of the system on which the - installation is performed. - -.. variable:: CPACK_WIX_ROOT_FOLDER_ID - - This variable allows specification of a custom root folder ID. - The generator specific ``<64>`` token can be used for - folder IDs that come in 32-bit and 64-bit variants. - In 32-bit builds the token will expand empty while in 64-bit builds - it will expand to ``64``. - - When unset generated installers will default installing to - ``ProgramFiles<64>Folder``. - -.. variable:: CPACK_WIX_ROOT - - This variable can optionally be set to the root directory - of a custom WiX Toolset installation. - - When unspecified CPack will try to locate a WiX Toolset - installation via the ``WIX`` environment variable instead.
diff --git a/share/cmake-3.18/Help/envvar/ASM_DIALECT.rst b/share/cmake-3.18/Help/envvar/ASM_DIALECT.rst deleted file mode 100644 index a06e3cb..0000000 --- a/share/cmake-3.18/Help/envvar/ASM_DIALECT.rst +++ /dev/null
@@ -1,14 +0,0 @@ -ASM<DIALECT> ------------- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling a specific dialect of assembly language -files. ``ASM<DIALECT>`` can be ``ASM``, ``ASM_NASM`` (Netwide Assembler), -``ASM_MASM`` (Microsoft Assembler) or ``ASM-ATT`` (Assembler AT&T). -Will only be used by CMake on the first configuration to determine -``ASM<DIALECT>`` compiler, after which the value for ``ASM<DIALECT>`` is stored -in the cache as -:variable:`CMAKE_ASM<DIALECT>_COMPILER <CMAKE_<LANG>_COMPILER>`. For subsequent -configuration runs, the environment variable will be ignored in favor of -:variable:`CMAKE_ASM<DIALECT>_COMPILER <CMAKE_<LANG>_COMPILER>`.
diff --git a/share/cmake-3.18/Help/envvar/CC.rst b/share/cmake-3.18/Help/envvar/CC.rst deleted file mode 100644 index ef12059..0000000 --- a/share/cmake-3.18/Help/envvar/CC.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CC --- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``C`` language files. Will only be used by -CMake on the first configuration to determine ``C`` compiler, after which the -value for ``CC`` is stored in the cache as -:variable:`CMAKE_C_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration run -(including the first), the environment variable will be ignored if the -:variable:`CMAKE_C_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/CCMAKE_COLORS.rst b/share/cmake-3.18/Help/envvar/CCMAKE_COLORS.rst deleted file mode 100644 index d4750c3..0000000 --- a/share/cmake-3.18/Help/envvar/CCMAKE_COLORS.rst +++ /dev/null
@@ -1,34 +0,0 @@ -CCMAKE_COLORS -------------- - -Determines what colors are used by the CMake curses interface, -when run on a terminal that supports colors. -The syntax follows the same conventions as ``LS_COLORS``; -that is, a list of key/value pairs separated by ``:``. - -Keys are a single letter corresponding to a CMake cache variable type: - -- ``s``: A ``STRING``. -- ``p``: A ``FILEPATH``. -- ``c``: A value which has an associated list of choices. -- ``y``: A ``BOOL`` which has a true-like value (e.g. ``ON``, ``YES``). -- ``n``: A ``BOOL`` which has a false-like value (e.g. ``OFF``, ``NO``). - -Values are an integer number that specifies what color to use. -``0`` is black (you probably don't want to use that). -Others are determined by your terminal's color support. -Most (color) terminals will support at least 8 or 16 colors. -Some will support up to 256 colors. The colors will likely match -`this chart <https://upload.wikimedia.org/wikipedia/commons/1/15/Xterm_256color_chart.svg>`_, -although the first 16 colors may match the original -`CGA color palette <https://en.wikipedia.org/wiki/Color_Graphics_Adapter#Color_palette>`_. -(Many modern terminal emulators also allow their color palette, -at least for the first 16 colors, to be configured by the user.) - -Note that fairly minimal checking is done for bad colors -(although a value higher than what curses believes your terminal supports -will be silently ignored) or bad syntax. - -For example:: - - CCMAKE_COLORS='s=39:p=220:c=207:n=196:y=46'
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_BUILD_PARALLEL_LEVEL.rst b/share/cmake-3.18/Help/envvar/CMAKE_BUILD_PARALLEL_LEVEL.rst deleted file mode 100644 index 199ca3e..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_BUILD_PARALLEL_LEVEL.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_BUILD_PARALLEL_LEVEL --------------------------- - -.. include:: ENV_VAR.txt - -Specifies the maximum number of concurrent processes to use when building -using the ``cmake --build`` command line -:ref:`Build Tool Mode <Build Tool Mode>`. - -If this variable is defined empty the native build tool's default number is -used.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_EXPORT_COMPILE_COMMANDS.rst b/share/cmake-3.18/Help/envvar/CMAKE_EXPORT_COMPILE_COMMANDS.rst deleted file mode 100644 index e9e0810..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_EXPORT_COMPILE_COMMANDS.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_EXPORT_COMPILE_COMMANDS ------------------------------ - -.. include:: ENV_VAR.txt - -The default value for :variable:`CMAKE_EXPORT_COMPILE_COMMANDS` when there -is no explicit configuration given on the first run while creating a new -build tree. On later runs in an existing build tree the value persists in -the cache as :variable:`CMAKE_EXPORT_COMPILE_COMMANDS`.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR.rst b/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR.rst deleted file mode 100644 index f2d055f..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_GENERATOR ---------------- - -.. include:: ENV_VAR.txt - -Specifies the CMake default generator to use when no generator is supplied -with ``-G``. If the provided value doesn't name a generator known by CMake, -the internal default is used. Either way the resulting generator selection -is stored in the :variable:`CMAKE_GENERATOR` variable. - -Some generators may be additionally configured using the environment -variables: - -* :envvar:`CMAKE_GENERATOR_PLATFORM` -* :envvar:`CMAKE_GENERATOR_TOOLSET` -* :envvar:`CMAKE_GENERATOR_INSTANCE`
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_INSTANCE.rst b/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_INSTANCE.rst deleted file mode 100644 index 1654fa1..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_INSTANCE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_GENERATOR_INSTANCE ------------------------- - -.. include:: ENV_VAR.txt - -Default value for :variable:`CMAKE_GENERATOR_INSTANCE` if no Cache entry is -present. This value is only applied if :envvar:`CMAKE_GENERATOR` is set.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_PLATFORM.rst b/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_PLATFORM.rst deleted file mode 100644 index 917b30b..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_PLATFORM.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_GENERATOR_PLATFORM ------------------------- - -.. include:: ENV_VAR.txt - -Default value for :variable:`CMAKE_GENERATOR_PLATFORM` if no Cache entry -is present and no value is specified by :manual:`cmake(1)` ``-A`` option. -This value is only applied if :envvar:`CMAKE_GENERATOR` is set.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_TOOLSET.rst b/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_TOOLSET.rst deleted file mode 100644 index 7ac3856..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_GENERATOR_TOOLSET.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_GENERATOR_TOOLSET ------------------------ - -.. include:: ENV_VAR.txt - -Default value for :variable:`CMAKE_GENERATOR_TOOLSET` if no Cache entry -is present and no value is specified by :manual:`cmake(1)` ``-T`` option. -This value is only applied if :envvar:`CMAKE_GENERATOR` is set.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_LANG_COMPILER_LAUNCHER.rst b/share/cmake-3.18/Help/envvar/CMAKE_LANG_COMPILER_LAUNCHER.rst deleted file mode 100644 index 4f91e9a..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_LANG_COMPILER_LAUNCHER.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_<LANG>_COMPILER_LAUNCHER ------------------------------- - -.. include:: ENV_VAR.txt - -Default compiler launcher to use for the specified language. Will only be used -by CMake to initialize the variable on the first configuration. Afterwards, it -is available through the cache setting of the variable of the same name. For -any configuration run (including the first), the environment variable will be -ignored if the :variable:`CMAKE_<LANG>_COMPILER_LAUNCHER` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/CMAKE_NO_VERBOSE.rst b/share/cmake-3.18/Help/envvar/CMAKE_NO_VERBOSE.rst deleted file mode 100644 index 149efbd..0000000 --- a/share/cmake-3.18/Help/envvar/CMAKE_NO_VERBOSE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_NO_VERBOSE ----------------- - -Disables verbose output from CMake when :envvar:`VERBOSE` environment variable -is set. - -Only your build tool of choice will still print verbose output when you start -to actually build your project.
diff --git a/share/cmake-3.18/Help/envvar/CSFLAGS.rst b/share/cmake-3.18/Help/envvar/CSFLAGS.rst deleted file mode 100644 index 8762982..0000000 --- a/share/cmake-3.18/Help/envvar/CSFLAGS.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CSFLAGS -------- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``CSharp`` language files. Will only be -used by CMake on the first configuration to determine ``CSharp`` default -compilation flags, after which the value for ``CSFLAGS`` is stored in the cache -as :variable:`CMAKE_CSharp_FLAGS <CMAKE_<LANG>_FLAGS>`. For any configuration -run (including the first), the environment variable will be ignored if the -:variable:`CMAKE_CSharp_FLAGS <CMAKE_<LANG>_FLAGS>` variable is defined. - -See also :variable:`CMAKE_CSharp_FLAGS_INIT <CMAKE_<LANG>_FLAGS_INIT>`.
diff --git a/share/cmake-3.18/Help/envvar/CTEST_PROGRESS_OUTPUT.rst b/share/cmake-3.18/Help/envvar/CTEST_PROGRESS_OUTPUT.rst deleted file mode 100644 index b36a6b8..0000000 --- a/share/cmake-3.18/Help/envvar/CTEST_PROGRESS_OUTPUT.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CTEST_PROGRESS_OUTPUT ---------------------- - -.. include:: ENV_VAR.txt - -Boolean environment variable that affects how :manual:`ctest <ctest(1)>` -command output reports overall progress. When set to ``1``, ``TRUE``, ``ON`` or anything -else that evaluates to boolean true, progress is reported by repeatedly -updating the same line. This greatly reduces the overall verbosity, but is -only supported when output is sent directly to a terminal. If the environment -variable is not set or has a value that evaluates to false, output is reported -normally with each test having its own start and end lines logged to the -output. - -The ``--progress`` option to :manual:`ctest <ctest(1)>` overrides this -environment variable if both are given.
diff --git a/share/cmake-3.18/Help/envvar/CUDACXX.rst b/share/cmake-3.18/Help/envvar/CUDACXX.rst deleted file mode 100644 index 10c0f9d..0000000 --- a/share/cmake-3.18/Help/envvar/CUDACXX.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CUDACXX -------- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``CUDA`` language files. Will only be used by -CMake on the first configuration to determine ``CUDA`` compiler, after which the -value for ``CUDA`` is stored in the cache as -:variable:`CMAKE_CUDA_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration -run (including the first), the environment variable will be ignored if the -:variable:`CMAKE_CUDA_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/CUDAFLAGS.rst b/share/cmake-3.18/Help/envvar/CUDAFLAGS.rst deleted file mode 100644 index 14c5d84..0000000 --- a/share/cmake-3.18/Help/envvar/CUDAFLAGS.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CUDAFLAGS ---------- - -.. include:: ENV_VAR.txt - -Default compilation flags to be used when compiling ``CUDA`` files. Will only be -used by CMake on the first configuration to determine ``CUDA`` default -compilation flags, after which the value for ``CUDAFLAGS`` is stored in the -cache as :variable:`CMAKE_CUDA_FLAGS <CMAKE_<LANG>_FLAGS>`. For any configuration -run (including the first), the environment variable will be ignored if -the :variable:`CMAKE_CUDA_FLAGS <CMAKE_<LANG>_FLAGS>` variable is defined. - -See also :variable:`CMAKE_CUDA_FLAGS_INIT <CMAKE_<LANG>_FLAGS_INIT>`.
diff --git a/share/cmake-3.18/Help/envvar/CUDAHOSTCXX.rst b/share/cmake-3.18/Help/envvar/CUDAHOSTCXX.rst deleted file mode 100644 index b9f65bd..0000000 --- a/share/cmake-3.18/Help/envvar/CUDAHOSTCXX.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CUDAHOSTCXX ------------ - -.. include:: ENV_VAR.txt - -Preferred executable for compiling host code when compiling ``CUDA`` -language files. Will only be used by CMake on the first configuration to -determine ``CUDA`` host compiler, after which the value for ``CUDAHOSTCXX`` is -stored in the cache as :variable:`CMAKE_CUDA_HOST_COMPILER`. For any -configuration run (including the first), the environment variable will be -ignored if the :variable:`CMAKE_CUDA_HOST_COMPILER` variable is defined. - -This environment variable is primarily meant for use with projects that -enable ``CUDA`` as a first-class language. The :module:`FindCUDA` -module will also use it to initialize its ``CUDA_HOST_COMPILER`` setting.
diff --git a/share/cmake-3.18/Help/envvar/CXX.rst b/share/cmake-3.18/Help/envvar/CXX.rst deleted file mode 100644 index d655350..0000000 --- a/share/cmake-3.18/Help/envvar/CXX.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CXX ---- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``CXX`` language files. Will only be used by -CMake on the first configuration to determine ``CXX`` compiler, after which the -value for ``CXX`` is stored in the cache as -:variable:`CMAKE_CXX_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration -run (including the first), the environment variable will be ignored if the -:variable:`CMAKE_CXX_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/FC.rst b/share/cmake-3.18/Help/envvar/FC.rst deleted file mode 100644 index d6cabbc..0000000 --- a/share/cmake-3.18/Help/envvar/FC.rst +++ /dev/null
@@ -1,12 +0,0 @@ -FC --- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``Fortran`` language files. Will only be used -by CMake on the first configuration to determine ``Fortran`` compiler, after -which the value for ``Fortran`` is stored in the cache as -:variable:`CMAKE_Fortran_COMPILER <CMAKE_<LANG>_COMPILER>`. For any -configuration run (including the first), the environment variable will be -ignored if the :variable:`CMAKE_Fortran_COMPILER <CMAKE_<LANG>_COMPILER>` -variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/OBJC.rst b/share/cmake-3.18/Help/envvar/OBJC.rst deleted file mode 100644 index 30c0d13..0000000 --- a/share/cmake-3.18/Help/envvar/OBJC.rst +++ /dev/null
@@ -1,14 +0,0 @@ -OBJC ----- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``OBJC`` language files. Will only be used -by CMake on the first configuration to determine ``OBJC`` compiler, after -which the value for ``OBJC`` is stored in the cache as -:variable:`CMAKE_OBJC_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration -run (including the first), the environment variable will be ignored if the -:variable:`CMAKE_OBJC_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined. - -If ``OBJC`` is not defined, the :envvar:`CC` environment variable will -be checked instead.
diff --git a/share/cmake-3.18/Help/envvar/OBJCXX.rst b/share/cmake-3.18/Help/envvar/OBJCXX.rst deleted file mode 100644 index a72f7e7..0000000 --- a/share/cmake-3.18/Help/envvar/OBJCXX.rst +++ /dev/null
@@ -1,14 +0,0 @@ -OBJCXX ------- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``OBJCXX`` language files. Will only be used -by CMake on the first configuration to determine ``OBJCXX`` compiler, after -which the value for ``OBJCXX`` is stored in the cache as -:variable:`CMAKE_OBJCXX_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration -run (including the first), the environment variable will be ignored if the -:variable:`CMAKE_OBJCXX_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined. - -If ``OBJCXX`` is not defined, the :envvar:`CXX` environment variable will -be checked instead.
diff --git a/share/cmake-3.18/Help/envvar/PackageName_ROOT.rst b/share/cmake-3.18/Help/envvar/PackageName_ROOT.rst deleted file mode 100644 index 82b0a06..0000000 --- a/share/cmake-3.18/Help/envvar/PackageName_ROOT.rst +++ /dev/null
@@ -1,17 +0,0 @@ -<PackageName>_ROOT ------------------- - -.. include:: ENV_VAR.txt - -Calls to :command:`find_package(<PackageName>)` will search in prefixes -specified by the ``<PackageName>_ROOT`` environment variable, where -``<PackageName>`` is the name given to the :command:`find_package` call -and ``_ROOT`` is literal. For example, ``find_package(Foo)`` will search -prefixes specified in the ``Foo_ROOT`` environment variable (if set). -See policy :policy:`CMP0074`. - -This variable may hold a single prefix or a list of prefixes separated -by ``:`` on UNIX or ``;`` on Windows (the same as the ``PATH`` environment -variable convention on those platforms). - -See also the :variable:`<PackageName>_ROOT` CMake variable.
diff --git a/share/cmake-3.18/Help/envvar/RC.rst b/share/cmake-3.18/Help/envvar/RC.rst deleted file mode 100644 index 557520e..0000000 --- a/share/cmake-3.18/Help/envvar/RC.rst +++ /dev/null
@@ -1,11 +0,0 @@ -RC --- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``resource`` files. Will only be used by CMake -on the first configuration to determine ``resource`` compiler, after which the -value for ``RC`` is stored in the cache as -:variable:`CMAKE_RC_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration run -(including the first), the environment variable will be ignored if the -:variable:`CMAKE_RC_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/SWIFTC.rst b/share/cmake-3.18/Help/envvar/SWIFTC.rst deleted file mode 100644 index b12e51d..0000000 --- a/share/cmake-3.18/Help/envvar/SWIFTC.rst +++ /dev/null
@@ -1,11 +0,0 @@ -SWIFTC ------- - -.. include:: ENV_VAR.txt - -Preferred executable for compiling ``Swift`` language files. Will only be used by -CMake on the first configuration to determine ``Swift`` compiler, after which the -value for ``SWIFTC`` is stored in the cache as -:variable:`CMAKE_Swift_COMPILER <CMAKE_<LANG>_COMPILER>`. For any configuration run -(including the first), the environment variable will be ignored if the -:variable:`CMAKE_Swift_COMPILER <CMAKE_<LANG>_COMPILER>` variable is defined.
diff --git a/share/cmake-3.18/Help/envvar/VERBOSE.rst b/share/cmake-3.18/Help/envvar/VERBOSE.rst deleted file mode 100644 index 2d775a5..0000000 --- a/share/cmake-3.18/Help/envvar/VERBOSE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VERBOSE -------- - -Activates verbose output from CMake and your build tools of choice when -you start to actually build your project. - -Note that any given value is ignored. It's just checked for existence. - -See also :ref:`Build Tool Mode <Build Tool Mode>` and -:envvar:`CMAKE_NO_VERBOSE` environment variable
diff --git a/share/cmake-3.18/Help/generator/CodeBlocks.rst b/share/cmake-3.18/Help/generator/CodeBlocks.rst deleted file mode 100644 index d830542..0000000 --- a/share/cmake-3.18/Help/generator/CodeBlocks.rst +++ /dev/null
@@ -1,32 +0,0 @@ -CodeBlocks ----------- - -Generates CodeBlocks project files. - -Project files for CodeBlocks will be created in the top directory and -in every subdirectory which features a ``CMakeLists.txt`` file containing -a :command:`project` call. Additionally a hierarchy of makefiles is generated -into the build tree. -The :variable:`CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES` variable may -be set to ``ON`` to exclude any files which are located outside of -the project root directory. -The appropriate make program can build the -project through the default ``all`` target. An ``install`` target is -also provided. - -This "extra" generator may be specified as: - -``CodeBlocks - MinGW Makefiles`` - Generate with :generator:`MinGW Makefiles`. - -``CodeBlocks - NMake Makefiles`` - Generate with :generator:`NMake Makefiles`. - -``CodeBlocks - NMake Makefiles JOM`` - Generate with :generator:`NMake Makefiles JOM`. - -``CodeBlocks - Ninja`` - Generate with :generator:`Ninja`. - -``CodeBlocks - Unix Makefiles`` - Generate with :generator:`Unix Makefiles`.
diff --git a/share/cmake-3.18/Help/generator/CodeLite.rst b/share/cmake-3.18/Help/generator/CodeLite.rst deleted file mode 100644 index 46fa5be..0000000 --- a/share/cmake-3.18/Help/generator/CodeLite.rst +++ /dev/null
@@ -1,28 +0,0 @@ -CodeLite ----------- - -Generates CodeLite project files. - -Project files for CodeLite will be created in the top directory and -in every subdirectory which features a CMakeLists.txt file containing -a :command:`project` call. -The :variable:`CMAKE_CODELITE_USE_TARGETS` variable may be set to ``ON`` -to change the default behavior from projects to targets as the basis -for project files. -The appropriate make program can build the -project through the default ``all`` target. An ``install`` target -is also provided. - -This "extra" generator may be specified as: - -``CodeLite - MinGW Makefiles`` - Generate with :generator:`MinGW Makefiles`. - -``CodeLite - NMake Makefiles`` - Generate with :generator:`NMake Makefiles`. - -``CodeLite - Ninja`` - Generate with :generator:`Ninja`. - -``CodeLite - Unix Makefiles`` - Generate with :generator:`Unix Makefiles`.
diff --git a/share/cmake-3.18/Help/generator/Green Hills MULTI.rst b/share/cmake-3.18/Help/generator/Green Hills MULTI.rst deleted file mode 100644 index dffc679..0000000 --- a/share/cmake-3.18/Help/generator/Green Hills MULTI.rst +++ /dev/null
@@ -1,69 +0,0 @@ -Green Hills MULTI ------------------ - -Generates Green Hills MULTI project files (experimental, work-in-progress). - -The buildsystem has predetermined build-configuration settings that can be controlled -via the :variable:`CMAKE_BUILD_TYPE` variable. - -Customizations that are used to pick toolset and target system: - -The ``-A <arch>`` can be supplied for setting the target architecture. -``<arch>`` usually is one of ``arm``, ``ppc``, ``86``, etcetera. -If the target architecture is not specified then -the default architecture of ``arm`` will be used. - -The ``-T <toolset>`` option can be used to set the directory location of the toolset. -Both absolute and relative paths are valid. Relative paths use ``GHS_TOOLSET_ROOT`` -as the root. If the toolset is not specified then the latest toolset found in -``GHS_TOOLSET_ROOT`` will be used. - -Cache variables that are used for toolset and target system customization: - -* ``GHS_TARGET_PLATFORM`` - - | Defaults to ``integrity``. - | Usual values are ``integrity``, ``threadx``, ``uvelosity``, ``velosity``, - ``vxworks``, ``standalone``. - -* ``GHS_PRIMARY_TARGET`` - - | Sets ``primaryTarget`` entry in project file. - | Defaults to ``<arch>_<GHS_TARGET_PLATFORM>.tgt``. - -* ``GHS_TOOLSET_ROOT`` - - | Root path for ``toolset`` searches. - | Defaults to ``C:/ghs`` in Windows or ``/usr/ghs`` in Linux. - -* ``GHS_OS_ROOT`` - - | Root path for RTOS searches. - | Defaults to ``C:/ghs`` in Windows or ``/usr/ghs`` in Linux. - -* ``GHS_OS_DIR`` and ``GHS_OS_DIR_OPTION`` - - | Sets ``-os_dir`` entry in project file. - | Defaults to latest platform OS installation at ``GHS_OS_ROOT``. Set this value if - a specific RTOS is to be used. - | ``GHS_OS_DIR_OPTION`` default value is ``-os_dir``. - -* ``GHS_BSP_NAME`` - - | Sets ``-bsp`` entry in project file. - | Defaults to ``sim<arch>`` for ``integrity`` platforms. - -Customizations are available through the following cache variables: - -* ``GHS_CUSTOMIZATION`` -* ``GHS_GPJ_MACROS`` - -The following properties are available: - -* :prop_tgt:`GHS_INTEGRITY_APP` -* :prop_tgt:`GHS_NO_SOURCE_GROUP_FILE` - -.. note:: - This generator is deemed experimental as of CMake |release| - and is still a work in progress. Future versions of CMake - may make breaking changes as the generator matures.
diff --git a/share/cmake-3.18/Help/generator/NMake Makefiles JOM.rst b/share/cmake-3.18/Help/generator/NMake Makefiles JOM.rst deleted file mode 100644 index 3a8744c..0000000 --- a/share/cmake-3.18/Help/generator/NMake Makefiles JOM.rst +++ /dev/null
@@ -1,4 +0,0 @@ -NMake Makefiles JOM -------------------- - -Generates JOM makefiles.
diff --git a/share/cmake-3.18/Help/generator/Ninja Multi-Config.rst b/share/cmake-3.18/Help/generator/Ninja Multi-Config.rst deleted file mode 100644 index f480eb8..0000000 --- a/share/cmake-3.18/Help/generator/Ninja Multi-Config.rst +++ /dev/null
@@ -1,87 +0,0 @@ -Ninja Multi-Config ------------------- - -Generates multiple ``build-<Config>.ninja`` files. - -This generator is very much like the :generator:`Ninja` generator, but with -some key differences. Only these differences will be discussed in this -document. - -Unlike the :generator:`Ninja` generator, ``Ninja Multi-Config`` generates -multiple configurations at once with :variable:`CMAKE_CONFIGURATION_TYPES` -instead of only one configuration with :variable:`CMAKE_BUILD_TYPE`. One -``build-<Config>.ninja`` file will be generated for each of these -configurations (with ``<Config>`` being the configuration name.) These files -are intended to be run with ``ninja -f build-<Config>.ninja``. A -``build.ninja`` file is also generated, using the configuration from either -:variable:`CMAKE_DEFAULT_BUILD_TYPE` or the first item from -:variable:`CMAKE_CONFIGURATION_TYPES`. - -``cmake --build . --config <Config>`` will always use ``build-<Config>.ninja`` -to build. If no ``--config`` argument is specified, ``cmake --build .`` will -default to ``build-Debug.ninja``, unless a ``build.ninja`` is generated (see -below), in which case that will be used instead. - -Each ``build-<Config>.ninja`` file contains ``<target>`` targets as well as -``<target>:<Config>`` targets, where ``<Config>`` is the same as the -configuration specified in ``build-<Config>.ninja`` Additionally, if -cross-config mode is enabled, ``build-<Config>.ninja`` may contain -``<target>:<OtherConfig>`` targets, where ``<OtherConfig>`` is a cross-config, -as well as ``<target>:all``, which builds the target in all cross-configs. See -below for how to enable cross-config mode. - -The ``Ninja Multi-Config`` generator recognizes the following variables: - -:variable:`CMAKE_CONFIGURATION_TYPES` - Specifies the total set of configurations to build. - -:variable:`CMAKE_CROSS_CONFIGS` - Specifies a :ref:`semicolon-separated list <CMake Language Lists>` of - configurations available from all ``build-<Config>.ninja`` files. - -:variable:`CMAKE_DEFAULT_BUILD_TYPE` - Specifies the configuration to use by default in a ``build.ninja`` file. - -:variable:`CMAKE_DEFAULT_CONFIGS` - Specifies a :ref:`semicolon-separated list <CMake Language Lists>` of - configurations to build for a target in ``build.ninja`` - if no ``:<Config>`` suffix is specified. - -Consider the following example: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.16) - project(MultiConfigNinja C) - - add_executable(generator generator.c) - add_custom_command(OUTPUT generated.c COMMAND generator generated.c) - add_library(generated ${CMAKE_BINARY_DIR}/generated.c) - -Now assume you configure the project with ``Ninja Multi-Config`` and run one of -the following commands: - -.. code-block:: shell - - ninja -f build-Debug.ninja generated - # OR - cmake --build . --config Debug --target generated - -This would build the ``Debug`` configuration of ``generator``, which would be -used to generate ``generated.c``, which would be used to build the ``Debug`` -configuration of ``generated``. - -But if :variable:`CMAKE_CROSS_CONFIGS` is set to ``all``, and you run the -following instead: - -.. code-block:: shell - - ninja -f build-Release.ninja generated:Debug - # OR - cmake --build . --config Release --target generated:Debug - -This would build the ``Release`` configuration of ``generator``, which would be -used to generate ``generated.c``, which would be used to build the ``Debug`` -configuration of ``generated``. This is useful for running a release-optimized -version of a generator utility while still building the debug version of the -targets built with the generated code.
diff --git a/share/cmake-3.18/Help/generator/Ninja.rst b/share/cmake-3.18/Help/generator/Ninja.rst deleted file mode 100644 index 08ee81b..0000000 --- a/share/cmake-3.18/Help/generator/Ninja.rst +++ /dev/null
@@ -1,42 +0,0 @@ -Ninja ------ - -Generates ``build.ninja`` files. - -A ``build.ninja`` file is generated into the build tree. Use the ninja -program to build the project through the ``all`` target and install the -project through the ``install`` (or ``install/strip``) target. - -For each subdirectory ``sub/dir`` of the project, additional targets -are generated: - -``sub/dir/all`` - Depends on all targets required by the subdirectory. - -``sub/dir/install`` - Runs the install step in the subdirectory, if any. - -``sub/dir/install/strip`` - Runs the install step in the subdirectory followed by a ``CMAKE_STRIP`` command, - if any. - - The ``CMAKE_STRIP`` variable will contain the platform's ``strip`` utility, which - removes symbols information from generated binaries. - -``sub/dir/test`` - Runs the test step in the subdirectory, if any. - -``sub/dir/package`` - Runs the package step in the subdirectory, if any. - -Fortran Support -^^^^^^^^^^^^^^^ - -The ``Ninja`` generator conditionally supports Fortran when the ``ninja`` -tool is at least version 1.10 (which has the required features). - -See Also -^^^^^^^^ - -The :generator:`Ninja Multi-Config` generator is similar to the ``Ninja`` -generator, but generates multiple configurations at once.
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 10 2010.rst b/share/cmake-3.18/Help/generator/Visual Studio 10 2010.rst deleted file mode 100644 index 4bf9a8f..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 10 2010.rst +++ /dev/null
@@ -1,43 +0,0 @@ -Visual Studio 10 2010 ---------------------- - -Generates Visual Studio 10 (VS 2010) project files. - -For compatibility with CMake versions prior to 3.0, one may specify this -generator using the name ``Visual Studio 10`` without the year component. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (Database, Website, etc.) are not supported. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 10 2010" -A Win32`` -* ``cmake -G "Visual Studio 10 2010" -A x64`` -* ``cmake -G "Visual Studio 10 2010" -A Itanium`` - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 10 2010 Win64`` - Specify target platform ``x64``. - -``Visual Studio 10 2010 IA64`` - Specify target platform ``Itanium``. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v100`` toolset that comes with Visual Studio 10 2010 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset.
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 11 2012.rst b/share/cmake-3.18/Help/generator/Visual Studio 11 2012.rst deleted file mode 100644 index 5d89a6e..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 11 2012.rst +++ /dev/null
@@ -1,48 +0,0 @@ -Visual Studio 11 2012 ---------------------- - -Generates Visual Studio 11 (VS 2012) project files. - -For compatibility with CMake versions prior to 3.0, one may specify this -generator using the name "Visual Studio 11" without the year component. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (JavaScript, Database, Website, etc.) are not supported. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 11 2012" -A Win32`` -* ``cmake -G "Visual Studio 11 2012" -A x64`` -* ``cmake -G "Visual Studio 11 2012" -A ARM`` -* ``cmake -G "Visual Studio 11 2012" -A <WinCE-SDK>`` - (Specify a target platform matching a Windows CE SDK name.) - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 11 2012 Win64`` - Specify target platform ``x64``. - -``Visual Studio 11 2012 ARM`` - Specify target platform ``ARM``. - -``Visual Studio 11 2012 <WinCE-SDK>`` - Specify target platform matching a Windows CE SDK name. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v110`` toolset that comes with Visual Studio 11 2012 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset.
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 12 2013.rst b/share/cmake-3.18/Help/generator/Visual Studio 12 2013.rst deleted file mode 100644 index fb8e021..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 12 2013.rst +++ /dev/null
@@ -1,48 +0,0 @@ -Visual Studio 12 2013 ---------------------- - -Generates Visual Studio 12 (VS 2013) project files. - -For compatibility with CMake versions prior to 3.0, one may specify this -generator using the name "Visual Studio 12" without the year component. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (JavaScript, Powershell, Python, etc.) are not supported. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 12 2013" -A Win32`` -* ``cmake -G "Visual Studio 12 2013" -A x64`` -* ``cmake -G "Visual Studio 12 2013" -A ARM`` - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 12 2013 Win64`` - Specify target platform ``x64``. - -``Visual Studio 12 2013 ARM`` - Specify target platform ``ARM``. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v120`` toolset that comes with Visual Studio 12 2013 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset. - -.. |VS_TOOLSET_HOST_ARCH_DEFAULT| replace:: - By default this generator uses the 32-bit variant even on a 64-bit host. - -.. include:: VS_TOOLSET_HOST_ARCH.txt
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 14 2015.rst b/share/cmake-3.18/Help/generator/Visual Studio 14 2015.rst deleted file mode 100644 index 7383f7a..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 14 2015.rst +++ /dev/null
@@ -1,45 +0,0 @@ -Visual Studio 14 2015 ---------------------- - -Generates Visual Studio 14 (VS 2015) project files. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (JavaScript, Powershell, Python, etc.) are not supported. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 14 2015" -A Win32`` -* ``cmake -G "Visual Studio 14 2015" -A x64`` -* ``cmake -G "Visual Studio 14 2015" -A ARM`` - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 14 2015 Win64`` - Specify target platform ``x64``. - -``Visual Studio 14 2015 ARM`` - Specify target platform ``ARM``. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v140`` toolset that comes with Visual Studio 14 2015 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset. - -.. |VS_TOOLSET_HOST_ARCH_DEFAULT| replace:: - By default this generator uses the 32-bit variant even on a 64-bit host. - -.. include:: VS_TOOLSET_HOST_ARCH.txt
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 15 2017.rst b/share/cmake-3.18/Help/generator/Visual Studio 15 2017.rst deleted file mode 100644 index 7e6f0fb..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 15 2017.rst +++ /dev/null
@@ -1,62 +0,0 @@ -Visual Studio 15 2017 ---------------------- - -Generates Visual Studio 15 (VS 2017) project files. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (JavaScript, Powershell, Python, etc.) are not supported. - -Instance Selection -^^^^^^^^^^^^^^^^^^ - -VS 2017 supports multiple installations on the same machine. -The :variable:`CMAKE_GENERATOR_INSTANCE` variable may be set as a -cache entry containing the absolute path to a Visual Studio instance. -If the value is not specified explicitly by the user or a toolchain file, -CMake queries the Visual Studio Installer to locate VS instances, chooses -one, and sets the variable as a cache entry to hold the value persistently. - -When CMake first chooses an instance, if the ``VS150COMNTOOLS`` environment -variable is set and points to the ``Common7/Tools`` directory within -one of the instances, that instance will be used. Otherwise, if more -than one instance is installed we do not define which one is chosen -by default. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 15 2017" -A Win32`` -* ``cmake -G "Visual Studio 15 2017" -A x64`` -* ``cmake -G "Visual Studio 15 2017" -A ARM`` -* ``cmake -G "Visual Studio 15 2017" -A ARM64`` - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 15 2017 Win64`` - Specify target platform ``x64``. - -``Visual Studio 15 2017 ARM`` - Specify target platform ``ARM``. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v141`` toolset that comes with Visual Studio 15 2017 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset. - -.. |VS_TOOLSET_HOST_ARCH_DEFAULT| replace:: - By default this generator uses the 32-bit variant even on a 64-bit host. - -.. include:: VS_TOOLSET_HOST_ARCH.txt
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 16 2019.rst b/share/cmake-3.18/Help/generator/Visual Studio 16 2019.rst deleted file mode 100644 index 4aec7f7..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 16 2019.rst +++ /dev/null
@@ -1,54 +0,0 @@ -Visual Studio 16 2019 ---------------------- - -Generates Visual Studio 16 (VS 2019) project files. - -Project Types -^^^^^^^^^^^^^ - -Only Visual C++ and C# projects may be generated. Other types of -projects (JavaScript, Powershell, Python, etc.) are not supported. - -Instance Selection -^^^^^^^^^^^^^^^^^^ - -VS 2019 supports multiple installations on the same machine. -The :variable:`CMAKE_GENERATOR_INSTANCE` variable may be set as a -cache entry containing the absolute path to a Visual Studio instance. -If the value is not specified explicitly by the user or a toolchain file, -CMake queries the Visual Studio Installer to locate VS instances, chooses -one, and sets the variable as a cache entry to hold the value persistently. - -When CMake first chooses an instance, if the ``VS160COMNTOOLS`` environment -variable is set and points to the ``Common7/Tools`` directory within -one of the instances, that instance will be used. Otherwise, if more -than one instance is installed we do not define which one is chosen -by default. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is that of the host -and is provided in the :variable:`CMAKE_VS_PLATFORM_NAME_DEFAULT` variable. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 16 2019" -A Win32`` -* ``cmake -G "Visual Studio 16 2019" -A x64`` -* ``cmake -G "Visual Studio 16 2019" -A ARM`` -* ``cmake -G "Visual Studio 16 2019" -A ARM64`` - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -The ``v142`` toolset that comes with Visual Studio 16 2019 is selected by -default. The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset. - -.. |VS_TOOLSET_HOST_ARCH_DEFAULT| replace:: - By default this generator uses the 64-bit variant on x64 hosts and - the 32-bit variant otherwise. - -.. include:: VS_TOOLSET_HOST_ARCH.txt
diff --git a/share/cmake-3.18/Help/generator/Visual Studio 9 2008.rst b/share/cmake-3.18/Help/generator/Visual Studio 9 2008.rst deleted file mode 100644 index a09d047..0000000 --- a/share/cmake-3.18/Help/generator/Visual Studio 9 2008.rst +++ /dev/null
@@ -1,32 +0,0 @@ -Visual Studio 9 2008 --------------------- - -Generates Visual Studio 9 2008 project files. - -Platform Selection -^^^^^^^^^^^^^^^^^^ - -The default target platform name (architecture) is ``Win32``. - -The :variable:`CMAKE_GENERATOR_PLATFORM` variable may be set, perhaps -via the :manual:`cmake(1)` ``-A`` option, to specify a target platform -name (architecture). For example: - -* ``cmake -G "Visual Studio 9 2008" -A Win32`` -* ``cmake -G "Visual Studio 9 2008" -A x64`` -* ``cmake -G "Visual Studio 9 2008" -A Itanium`` -* ``cmake -G "Visual Studio 9 2008" -A <WinCE-SDK>`` - (Specify a target platform matching a Windows CE SDK name.) - -For compatibility with CMake versions prior to 3.1, one may specify -a target platform name optionally at the end of the generator name. -This is supported only for: - -``Visual Studio 9 2008 Win64`` - Specify target platform ``x64``. - -``Visual Studio 9 2008 IA64`` - Specify target platform ``Itanium``. - -``Visual Studio 9 2008 <WinCE-SDK>`` - Specify target platform matching a Windows CE SDK name.
diff --git a/share/cmake-3.18/Help/generator/Xcode.rst b/share/cmake-3.18/Help/generator/Xcode.rst deleted file mode 100644 index d893ac5..0000000 --- a/share/cmake-3.18/Help/generator/Xcode.rst +++ /dev/null
@@ -1,13 +0,0 @@ -Xcode ------ - -Generate Xcode project files. - -This supports Xcode 5.0 and above. - -Toolset Selection -^^^^^^^^^^^^^^^^^ - -By default Xcode is allowed to select its own default toolchain. -The :variable:`CMAKE_GENERATOR_TOOLSET` option may be set, perhaps -via the :manual:`cmake(1)` ``-T`` option, to specify another toolset.
diff --git a/share/cmake-3.18/Help/index.rst b/share/cmake-3.18/Help/index.rst deleted file mode 100644 index 4d9a9c8..0000000 --- a/share/cmake-3.18/Help/index.rst +++ /dev/null
@@ -1,104 +0,0 @@ -.. title:: CMake Reference Documentation - -Introduction -############ - -CMake is a tool to manage building of source code. Originally, CMake was -designed as a generator for various dialects of ``Makefile``, today -CMake generates modern buildsystems such as ``Ninja`` as well as project -files for IDEs such as Visual Studio and Xcode. - -CMake is widely used for the C and C++ languages, but it may be used to -build source code of other languages too. - -People encountering CMake for the first time may have different initial -goals. To learn how to build a source code package downloaded from the -internet, start with the :guide:`User Interaction Guide`. -This will detail the steps needed to run the :manual:`cmake(1)` or -:manual:`cmake-gui(1)` executable and how to choose a generator, and -how to complete the build. - -The :guide:`Using Dependencies Guide` is aimed at developers -wishing to get started using a third-party library. - -For developers starting a project using CMake, the :guide:`CMake Tutorial` -is a suitable starting point. The :manual:`cmake-buildsystem(7)` -manual is aimed at developers expanding their knowledge of maintaining -a buildsystem and becoming familiar with the build targets that -can be represented in CMake. The :manual:`cmake-packages(7)` manual -explains how to create packages which can easily be consumed by -third-party CMake-based buildsystems. - -Command-Line Tools -################## - -.. toctree:: - :maxdepth: 1 - - /manual/cmake.1 - /manual/ctest.1 - /manual/cpack.1 - -Interactive Dialogs -################### - -.. toctree:: - :maxdepth: 1 - - /manual/cmake-gui.1 - /manual/ccmake.1 - -Reference Manuals -################# - -.. toctree:: - :maxdepth: 1 - - /manual/cmake-buildsystem.7 - /manual/cmake-commands.7 - /manual/cmake-compile-features.7 - /manual/cmake-developer.7 - /manual/cmake-env-variables.7 - /manual/cmake-file-api.7 - /manual/cmake-generator-expressions.7 - /manual/cmake-generators.7 - /manual/cmake-language.7 - /manual/cmake-modules.7 - /manual/cmake-packages.7 - /manual/cmake-policies.7 - /manual/cmake-properties.7 - /manual/cmake-qt.7 - /manual/cmake-server.7 - /manual/cmake-toolchains.7 - /manual/cmake-variables.7 - /manual/cpack-generators.7 - -.. only:: not man - - Guides - ###### - - .. toctree:: - :maxdepth: 1 - - /guide/tutorial/index - /guide/user-interaction/index - /guide/using-dependencies/index - -.. only:: html or text - - Release Notes - ############# - - .. toctree:: - :maxdepth: 1 - - /release/index - -.. only:: html - - Index and Search - ################ - - * :ref:`genindex` - * :ref:`search`
diff --git a/share/cmake-3.18/Help/manual/OPTIONS_BUILD.txt b/share/cmake-3.18/Help/manual/OPTIONS_BUILD.txt deleted file mode 100644 index 0947e41..0000000 --- a/share/cmake-3.18/Help/manual/OPTIONS_BUILD.txt +++ /dev/null
@@ -1,126 +0,0 @@ -``-S <path-to-source>`` - Path to root directory of the CMake project to build. - -``-B <path-to-build>`` - Path to directory which CMake will use as the root of build directory. - - If the directory doesn't already exist CMake will make it. - -``-C <initial-cache>`` - Pre-load a script to populate the cache. - - When CMake is first run in an empty build tree, it creates a - ``CMakeCache.txt`` file and populates it with customizable settings for - the project. This option may be used to specify a file from which - to load cache entries before the first pass through the project's - CMake listfiles. The loaded entries take priority over the - project's default values. The given file should be a CMake script - containing :command:`set` commands that use the ``CACHE`` option, not a - cache-format file. - - References to :variable:`CMAKE_SOURCE_DIR` and :variable:`CMAKE_BINARY_DIR` - within the script evaluate to the top-level source and build tree. - -``-D <var>:<type>=<value>, -D <var>=<value>`` - Create or update a CMake ``CACHE`` entry. - - When CMake is first run in an empty build tree, it creates a - ``CMakeCache.txt`` file and populates it with customizable settings for - the project. This option may be used to specify a setting that - takes priority over the project's default value. The option may be - repeated for as many ``CACHE`` entries as desired. - - If the ``:<type>`` portion is given it must be one of the types - specified by the :command:`set` command documentation for its - ``CACHE`` signature. - If the ``:<type>`` portion is omitted the entry will be created - with no type if it does not exist with a type already. If a - command in the project sets the type to ``PATH`` or ``FILEPATH`` - then the ``<value>`` will be converted to an absolute path. - - This option may also be given as a single argument: - ``-D<var>:<type>=<value>`` or ``-D<var>=<value>``. - -``-U <globbing_expr>`` - Remove matching entries from CMake ``CACHE``. - - This option may be used to remove one or more variables from the - ``CMakeCache.txt`` file, globbing expressions using ``*`` and ``?`` are - supported. The option may be repeated for as many ``CACHE`` entries as - desired. - - Use with care, you can make your ``CMakeCache.txt`` non-working. - -``-G <generator-name>`` - Specify a build system generator. - - CMake may support multiple native build systems on certain - platforms. A generator is responsible for generating a particular - build system. Possible generator names are specified in the - :manual:`cmake-generators(7)` manual. - - If not specified, CMake checks the :envvar:`CMAKE_GENERATOR` environment - variable and otherwise falls back to a builtin default selection. - -``-T <toolset-spec>`` - Toolset specification for the generator, if supported. - - Some CMake generators support a toolset specification to tell - the native build system how to choose a compiler. See the - :variable:`CMAKE_GENERATOR_TOOLSET` variable for details. - -``-A <platform-name>`` - Specify platform name if supported by generator. - - Some CMake generators support a platform name to be given to the - native build system to choose a compiler or SDK. See the - :variable:`CMAKE_GENERATOR_PLATFORM` variable for details. - -``-Wno-dev`` - Suppress developer warnings. - - Suppress warnings that are meant for the author of the - ``CMakeLists.txt`` files. By default this will also turn off - deprecation warnings. - -``-Wdev`` - Enable developer warnings. - - Enable warnings that are meant for the author of the ``CMakeLists.txt`` - files. By default this will also turn on deprecation warnings. - -``-Werror=dev`` - Make developer warnings errors. - - Make warnings that are meant for the author of the ``CMakeLists.txt`` files - errors. By default this will also turn on deprecated warnings as errors. - -``-Wno-error=dev`` - Make developer warnings not errors. - - Make warnings that are meant for the author of the ``CMakeLists.txt`` files not - errors. By default this will also turn off deprecated warnings as errors. - -``-Wdeprecated`` - Enable deprecated functionality warnings. - - Enable warnings for usage of deprecated functionality, that are meant - for the author of the ``CMakeLists.txt`` files. - -``-Wno-deprecated`` - Suppress deprecated functionality warnings. - - Suppress warnings for usage of deprecated functionality, that are meant - for the author of the ``CMakeLists.txt`` files. - -``-Werror=deprecated`` - Make deprecated macro and function warnings errors. - - Make warnings for usage of deprecated macros and functions, that are meant - for the author of the ``CMakeLists.txt`` files, errors. - -``-Wno-error=deprecated`` - Make deprecated macro and function warnings not errors. - - Make warnings for usage of deprecated macros and functions, that are meant - for the author of the ``CMakeLists.txt`` files, not errors.
diff --git a/share/cmake-3.18/Help/manual/VS-Choose-Arch.png b/share/cmake-3.18/Help/manual/VS-Choose-Arch.png deleted file mode 100644 index 816b0f4..0000000 --- a/share/cmake-3.18/Help/manual/VS-Choose-Arch.png +++ /dev/null Binary files differ
diff --git a/share/cmake-3.18/Help/manual/cmake-buildsystem.7.rst b/share/cmake-3.18/Help/manual/cmake-buildsystem.7.rst deleted file mode 100644 index d8142a2..0000000 --- a/share/cmake-3.18/Help/manual/cmake-buildsystem.7.rst +++ /dev/null
@@ -1,1011 +0,0 @@ -.. cmake-manual-description: CMake Buildsystem Reference - -cmake-buildsystem(7) -******************** - -.. only:: html - - .. contents:: - -Introduction -============ - -A CMake-based buildsystem is organized as a set of high-level logical -targets. Each target corresponds to an executable or library, or -is a custom target containing custom commands. Dependencies between the -targets are expressed in the buildsystem to determine the build order -and the rules for regeneration in response to change. - -Binary Targets -============== - -Executables and libraries are defined using the :command:`add_executable` -and :command:`add_library` commands. The resulting binary files have -appropriate :prop_tgt:`PREFIX`, :prop_tgt:`SUFFIX` and extensions for the platform targeted. -Dependencies between binary targets are expressed using the -:command:`target_link_libraries` command: - -.. code-block:: cmake - - add_library(archive archive.cpp zip.cpp lzma.cpp) - add_executable(zipapp zipapp.cpp) - target_link_libraries(zipapp archive) - -``archive`` is defined as a ``STATIC`` library -- an archive containing objects -compiled from ``archive.cpp``, ``zip.cpp``, and ``lzma.cpp``. ``zipapp`` -is defined as an executable formed by compiling and linking ``zipapp.cpp``. -When linking the ``zipapp`` executable, the ``archive`` static library is -linked in. - -Binary Executables ------------------- - -The :command:`add_executable` command defines an executable target: - -.. code-block:: cmake - - add_executable(mytool mytool.cpp) - -Commands such as :command:`add_custom_command`, which generates rules to be -run at build time can transparently use an :prop_tgt:`EXECUTABLE <TYPE>` -target as a ``COMMAND`` executable. The buildsystem rules will ensure that -the executable is built before attempting to run the command. - -Binary Library Types --------------------- - -.. _`Normal Libraries`: - -Normal Libraries -^^^^^^^^^^^^^^^^ - -By default, the :command:`add_library` command defines a ``STATIC`` library, -unless a type is specified. A type may be specified when using the command: - -.. code-block:: cmake - - add_library(archive SHARED archive.cpp zip.cpp lzma.cpp) - -.. code-block:: cmake - - add_library(archive STATIC archive.cpp zip.cpp lzma.cpp) - -The :variable:`BUILD_SHARED_LIBS` variable may be enabled to change the -behavior of :command:`add_library` to build shared libraries by default. - -In the context of the buildsystem definition as a whole, it is largely -irrelevant whether particular libraries are ``SHARED`` or ``STATIC`` -- -the commands, dependency specifications and other APIs work similarly -regardless of the library type. The ``MODULE`` library type is -dissimilar in that it is generally not linked to -- it is not used in -the right-hand-side of the :command:`target_link_libraries` command. -It is a type which is loaded as a plugin using runtime techniques. -If the library does not export any unmanaged symbols (e.g. Windows -resource DLL, C++/CLI DLL), it is required that the library not be a -``SHARED`` library because CMake expects ``SHARED`` libraries to export -at least one symbol. - -.. code-block:: cmake - - add_library(archive MODULE 7z.cpp) - -.. _`Apple Frameworks`: - -Apple Frameworks -"""""""""""""""" - -A ``SHARED`` library may be marked with the :prop_tgt:`FRAMEWORK` -target property to create an macOS or iOS Framework Bundle. -The ``MACOSX_FRAMEWORK_IDENTIFIER`` sets ``CFBundleIdentifier`` key -and it uniquely identifies the bundle. - -.. code-block:: cmake - - add_library(MyFramework SHARED MyFramework.cpp) - set_target_properties(MyFramework PROPERTIES - FRAMEWORK TRUE - FRAMEWORK_VERSION A - MACOSX_FRAMEWORK_IDENTIFIER org.cmake.MyFramework - ) - -.. _`Object Libraries`: - -Object Libraries -^^^^^^^^^^^^^^^^ - -The ``OBJECT`` library type defines a non-archival collection of object files -resulting from compiling the given source files. The object files collection -may be used as source inputs to other targets: - -.. code-block:: cmake - - add_library(archive OBJECT archive.cpp zip.cpp lzma.cpp) - - add_library(archiveExtras STATIC $<TARGET_OBJECTS:archive> extras.cpp) - - add_executable(test_exe $<TARGET_OBJECTS:archive> test.cpp) - -The link (or archiving) step of those other targets will use the object -files collection in addition to those from their own sources. - -Alternatively, object libraries may be linked into other targets: - -.. code-block:: cmake - - add_library(archive OBJECT archive.cpp zip.cpp lzma.cpp) - - add_library(archiveExtras STATIC extras.cpp) - target_link_libraries(archiveExtras PUBLIC archive) - - add_executable(test_exe test.cpp) - target_link_libraries(test_exe archive) - -The link (or archiving) step of those other targets will use the object -files from ``OBJECT`` libraries that are *directly* linked. Additionally, -usage requirements of the ``OBJECT`` libraries will be honored when compiling -sources in those other targets. Furthermore, those usage requirements -will propagate transitively to dependents of those other targets. - -Object libraries may not be used as the ``TARGET`` in a use of the -:command:`add_custom_command(TARGET)` command signature. However, -the list of objects can be used by :command:`add_custom_command(OUTPUT)` -or :command:`file(GENERATE)` by using ``$<TARGET_OBJECTS:objlib>``. - -Build Specification and Usage Requirements -========================================== - -The :command:`target_include_directories`, :command:`target_compile_definitions` -and :command:`target_compile_options` commands specify the build specifications -and the usage requirements of binary targets. The commands populate the -:prop_tgt:`INCLUDE_DIRECTORIES`, :prop_tgt:`COMPILE_DEFINITIONS` and -:prop_tgt:`COMPILE_OPTIONS` target properties respectively, and/or the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`, :prop_tgt:`INTERFACE_COMPILE_DEFINITIONS` -and :prop_tgt:`INTERFACE_COMPILE_OPTIONS` target properties. - -Each of the commands has a ``PRIVATE``, ``PUBLIC`` and ``INTERFACE`` mode. The -``PRIVATE`` mode populates only the non-``INTERFACE_`` variant of the target -property and the ``INTERFACE`` mode populates only the ``INTERFACE_`` variants. -The ``PUBLIC`` mode populates both variants of the respective target property. -Each command may be invoked with multiple uses of each keyword: - -.. code-block:: cmake - - target_compile_definitions(archive - PRIVATE BUILDING_WITH_LZMA - INTERFACE USING_ARCHIVE_LIB - ) - -Note that usage requirements are not designed as a way to make downstreams -use particular :prop_tgt:`COMPILE_OPTIONS` or -:prop_tgt:`COMPILE_DEFINITIONS` etc for convenience only. The contents of -the properties must be **requirements**, not merely recommendations or -convenience. - -See the :ref:`Creating Relocatable Packages` section of the -:manual:`cmake-packages(7)` manual for discussion of additional care -that must be taken when specifying usage requirements while creating -packages for redistribution. - -Target Properties ------------------ - -The contents of the :prop_tgt:`INCLUDE_DIRECTORIES`, -:prop_tgt:`COMPILE_DEFINITIONS` and :prop_tgt:`COMPILE_OPTIONS` target -properties are used appropriately when compiling the source files of a -binary target. - -Entries in the :prop_tgt:`INCLUDE_DIRECTORIES` are added to the compile line -with ``-I`` or ``-isystem`` prefixes and in the order of appearance in the -property value. - -Entries in the :prop_tgt:`COMPILE_DEFINITIONS` are prefixed with ``-D`` or -``/D`` and added to the compile line in an unspecified order. The -:prop_tgt:`DEFINE_SYMBOL` target property is also added as a compile -definition as a special convenience case for ``SHARED`` and ``MODULE`` -library targets. - -Entries in the :prop_tgt:`COMPILE_OPTIONS` are escaped for the shell and added -in the order of appearance in the property value. Several compile options have -special separate handling, such as :prop_tgt:`POSITION_INDEPENDENT_CODE`. - -The contents of the :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`, -:prop_tgt:`INTERFACE_COMPILE_DEFINITIONS` and -:prop_tgt:`INTERFACE_COMPILE_OPTIONS` target properties are -*Usage Requirements* -- they specify content which consumers -must use to correctly compile and link with the target they appear on. -For any binary target, the contents of each ``INTERFACE_`` property on -each target specified in a :command:`target_link_libraries` command is -consumed: - -.. code-block:: cmake - - set(srcs archive.cpp zip.cpp) - if (LZMA_FOUND) - list(APPEND srcs lzma.cpp) - endif() - add_library(archive SHARED ${srcs}) - if (LZMA_FOUND) - # The archive library sources are compiled with -DBUILDING_WITH_LZMA - target_compile_definitions(archive PRIVATE BUILDING_WITH_LZMA) - endif() - target_compile_definitions(archive INTERFACE USING_ARCHIVE_LIB) - - add_executable(consumer) - # Link consumer to archive and consume its usage requirements. The consumer - # executable sources are compiled with -DUSING_ARCHIVE_LIB. - target_link_libraries(consumer archive) - -Because it is common to require that the source directory and corresponding -build directory are added to the :prop_tgt:`INCLUDE_DIRECTORIES`, the -:variable:`CMAKE_INCLUDE_CURRENT_DIR` variable can be enabled to conveniently -add the corresponding directories to the :prop_tgt:`INCLUDE_DIRECTORIES` of -all targets. The variable :variable:`CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE` -can be enabled to add the corresponding directories to the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of all targets. This makes use of -targets in multiple different directories convenient through use of the -:command:`target_link_libraries` command. - - -.. _`Target Usage Requirements`: - -Transitive Usage Requirements ------------------------------ - -The usage requirements of a target can transitively propagate to dependents. -The :command:`target_link_libraries` command has ``PRIVATE``, -``INTERFACE`` and ``PUBLIC`` keywords to control the propagation. - -.. code-block:: cmake - - add_library(archive archive.cpp) - target_compile_definitions(archive INTERFACE USING_ARCHIVE_LIB) - - add_library(serialization serialization.cpp) - target_compile_definitions(serialization INTERFACE USING_SERIALIZATION_LIB) - - add_library(archiveExtras extras.cpp) - target_link_libraries(archiveExtras PUBLIC archive) - target_link_libraries(archiveExtras PRIVATE serialization) - # archiveExtras is compiled with -DUSING_ARCHIVE_LIB - # and -DUSING_SERIALIZATION_LIB - - add_executable(consumer consumer.cpp) - # consumer is compiled with -DUSING_ARCHIVE_LIB - target_link_libraries(consumer archiveExtras) - -Because ``archive`` is a ``PUBLIC`` dependency of ``archiveExtras``, the -usage requirements of it are propagated to ``consumer`` too. Because -``serialization`` is a ``PRIVATE`` dependency of ``archiveExtras``, the usage -requirements of it are not propagated to ``consumer``. - -Generally, a dependency should be specified in a use of -:command:`target_link_libraries` with the ``PRIVATE`` keyword if it is used by -only the implementation of a library, and not in the header files. If a -dependency is additionally used in the header files of a library (e.g. for -class inheritance), then it should be specified as a ``PUBLIC`` dependency. -A dependency which is not used by the implementation of a library, but only by -its headers should be specified as an ``INTERFACE`` dependency. The -:command:`target_link_libraries` command may be invoked with multiple uses of -each keyword: - -.. code-block:: cmake - - target_link_libraries(archiveExtras - PUBLIC archive - PRIVATE serialization - ) - -Usage requirements are propagated by reading the ``INTERFACE_`` variants -of target properties from dependencies and appending the values to the -non-``INTERFACE_`` variants of the operand. For example, the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of dependencies is read and -appended to the :prop_tgt:`INCLUDE_DIRECTORIES` of the operand. In cases -where order is relevant and maintained, and the order resulting from the -:command:`target_link_libraries` calls does not allow correct compilation, -use of an appropriate command to set the property directly may update the -order. - -For example, if the linked libraries for a target must be specified -in the order ``lib1`` ``lib2`` ``lib3`` , but the include directories must -be specified in the order ``lib3`` ``lib1`` ``lib2``: - -.. code-block:: cmake - - target_link_libraries(myExe lib1 lib2 lib3) - target_include_directories(myExe - PRIVATE $<TARGET_PROPERTY:lib3,INTERFACE_INCLUDE_DIRECTORIES>) - -Note that care must be taken when specifying usage requirements for targets -which will be exported for installation using the :command:`install(EXPORT)` -command. See :ref:`Creating Packages` for more. - -.. _`Compatible Interface Properties`: - -Compatible Interface Properties -------------------------------- - -Some target properties are required to be compatible between a target and -the interface of each dependency. For example, the -:prop_tgt:`POSITION_INDEPENDENT_CODE` target property may specify a -boolean value of whether a target should be compiled as -position-independent-code, which has platform-specific consequences. -A target may also specify the usage requirement -:prop_tgt:`INTERFACE_POSITION_INDEPENDENT_CODE` to communicate that -consumers must be compiled as position-independent-code. - -.. code-block:: cmake - - add_executable(exe1 exe1.cpp) - set_property(TARGET exe1 PROPERTY POSITION_INDEPENDENT_CODE ON) - - add_library(lib1 SHARED lib1.cpp) - set_property(TARGET lib1 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON) - - add_executable(exe2 exe2.cpp) - target_link_libraries(exe2 lib1) - -Here, both ``exe1`` and ``exe2`` will be compiled as position-independent-code. -``lib1`` will also be compiled as position-independent-code because that is the -default setting for ``SHARED`` libraries. If dependencies have conflicting, -non-compatible requirements :manual:`cmake(1)` issues a diagnostic: - -.. code-block:: cmake - - add_library(lib1 SHARED lib1.cpp) - set_property(TARGET lib1 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON) - - add_library(lib2 SHARED lib2.cpp) - set_property(TARGET lib2 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE OFF) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1) - set_property(TARGET exe1 PROPERTY POSITION_INDEPENDENT_CODE OFF) - - add_executable(exe2 exe2.cpp) - target_link_libraries(exe2 lib1 lib2) - -The ``lib1`` requirement ``INTERFACE_POSITION_INDEPENDENT_CODE`` is not -"compatible" with the :prop_tgt:`POSITION_INDEPENDENT_CODE` property of -the ``exe1`` target. The library requires that consumers are built as -position-independent-code, while the executable specifies to not built as -position-independent-code, so a diagnostic is issued. - -The ``lib1`` and ``lib2`` requirements are not "compatible". One of them -requires that consumers are built as position-independent-code, while -the other requires that consumers are not built as position-independent-code. -Because ``exe2`` links to both and they are in conflict, a diagnostic is -issued. - -To be "compatible", the :prop_tgt:`POSITION_INDEPENDENT_CODE` property, -if set must be either the same, in a boolean sense, as the -:prop_tgt:`INTERFACE_POSITION_INDEPENDENT_CODE` property of all transitively -specified dependencies on which that property is set. - -This property of "compatible interface requirement" may be extended to other -properties by specifying the property in the content of the -:prop_tgt:`COMPATIBLE_INTERFACE_BOOL` target property. Each specified property -must be compatible between the consuming target and the corresponding property -with an ``INTERFACE_`` prefix from each dependency: - -.. code-block:: cmake - - add_library(lib1Version2 SHARED lib1_v2.cpp) - set_property(TARGET lib1Version2 PROPERTY INTERFACE_CUSTOM_PROP ON) - set_property(TARGET lib1Version2 APPEND PROPERTY - COMPATIBLE_INTERFACE_BOOL CUSTOM_PROP - ) - - add_library(lib1Version3 SHARED lib1_v3.cpp) - set_property(TARGET lib1Version3 PROPERTY INTERFACE_CUSTOM_PROP OFF) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1Version2) # CUSTOM_PROP will be ON - - add_executable(exe2 exe2.cpp) - target_link_libraries(exe2 lib1Version2 lib1Version3) # Diagnostic - -Non-boolean properties may also participate in "compatible interface" -computations. Properties specified in the -:prop_tgt:`COMPATIBLE_INTERFACE_STRING` -property must be either unspecified or compare to the same string among -all transitively specified dependencies. This can be useful to ensure -that multiple incompatible versions of a library are not linked together -through transitive requirements of a target: - -.. code-block:: cmake - - add_library(lib1Version2 SHARED lib1_v2.cpp) - set_property(TARGET lib1Version2 PROPERTY INTERFACE_LIB_VERSION 2) - set_property(TARGET lib1Version2 APPEND PROPERTY - COMPATIBLE_INTERFACE_STRING LIB_VERSION - ) - - add_library(lib1Version3 SHARED lib1_v3.cpp) - set_property(TARGET lib1Version3 PROPERTY INTERFACE_LIB_VERSION 3) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1Version2) # LIB_VERSION will be "2" - - add_executable(exe2 exe2.cpp) - target_link_libraries(exe2 lib1Version2 lib1Version3) # Diagnostic - -The :prop_tgt:`COMPATIBLE_INTERFACE_NUMBER_MAX` target property specifies -that content will be evaluated numerically and the maximum number among all -specified will be calculated: - -.. code-block:: cmake - - add_library(lib1Version2 SHARED lib1_v2.cpp) - set_property(TARGET lib1Version2 PROPERTY INTERFACE_CONTAINER_SIZE_REQUIRED 200) - set_property(TARGET lib1Version2 APPEND PROPERTY - COMPATIBLE_INTERFACE_NUMBER_MAX CONTAINER_SIZE_REQUIRED - ) - - add_library(lib1Version3 SHARED lib1_v3.cpp) - set_property(TARGET lib1Version3 PROPERTY INTERFACE_CONTAINER_SIZE_REQUIRED 1000) - - add_executable(exe1 exe1.cpp) - # CONTAINER_SIZE_REQUIRED will be "200" - target_link_libraries(exe1 lib1Version2) - - add_executable(exe2 exe2.cpp) - # CONTAINER_SIZE_REQUIRED will be "1000" - target_link_libraries(exe2 lib1Version2 lib1Version3) - -Similarly, the :prop_tgt:`COMPATIBLE_INTERFACE_NUMBER_MIN` may be used to -calculate the numeric minimum value for a property from dependencies. - -Each calculated "compatible" property value may be read in the consumer at -generate-time using generator expressions. - -Note that for each dependee, the set of properties specified in each -compatible interface property must not intersect with the set specified in -any of the other properties. - -Property Origin Debugging -------------------------- - -Because build specifications can be determined by dependencies, the lack of -locality of code which creates a target and code which is responsible for -setting build specifications may make the code more difficult to reason about. -:manual:`cmake(1)` provides a debugging facility to print the origin of the -contents of properties which may be determined by dependencies. The properties -which can be debugged are listed in the -:variable:`CMAKE_DEBUG_TARGET_PROPERTIES` variable documentation: - -.. code-block:: cmake - - set(CMAKE_DEBUG_TARGET_PROPERTIES - INCLUDE_DIRECTORIES - COMPILE_DEFINITIONS - POSITION_INDEPENDENT_CODE - CONTAINER_SIZE_REQUIRED - LIB_VERSION - ) - add_executable(exe1 exe1.cpp) - -In the case of properties listed in :prop_tgt:`COMPATIBLE_INTERFACE_BOOL` or -:prop_tgt:`COMPATIBLE_INTERFACE_STRING`, the debug output shows which target -was responsible for setting the property, and which other dependencies also -defined the property. In the case of -:prop_tgt:`COMPATIBLE_INTERFACE_NUMBER_MAX` and -:prop_tgt:`COMPATIBLE_INTERFACE_NUMBER_MIN`, the debug output shows the -value of the property from each dependency, and whether the value determines -the new extreme. - -Build Specification with Generator Expressions ----------------------------------------------- - -Build specifications may use -:manual:`generator expressions <cmake-generator-expressions(7)>` containing -content which may be conditional or known only at generate-time. For example, -the calculated "compatible" value of a property may be read with the -``TARGET_PROPERTY`` expression: - -.. code-block:: cmake - - add_library(lib1Version2 SHARED lib1_v2.cpp) - set_property(TARGET lib1Version2 PROPERTY - INTERFACE_CONTAINER_SIZE_REQUIRED 200) - set_property(TARGET lib1Version2 APPEND PROPERTY - COMPATIBLE_INTERFACE_NUMBER_MAX CONTAINER_SIZE_REQUIRED - ) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1Version2) - target_compile_definitions(exe1 PRIVATE - CONTAINER_SIZE=$<TARGET_PROPERTY:CONTAINER_SIZE_REQUIRED> - ) - -In this case, the ``exe1`` source files will be compiled with -``-DCONTAINER_SIZE=200``. - -Configuration determined build specifications may be conveniently set using -the ``CONFIG`` generator expression. - -.. code-block:: cmake - - target_compile_definitions(exe1 PRIVATE - $<$<CONFIG:Debug>:DEBUG_BUILD> - ) - -The ``CONFIG`` parameter is compared case-insensitively with the configuration -being built. In the presence of :prop_tgt:`IMPORTED` targets, the content of -:prop_tgt:`MAP_IMPORTED_CONFIG_DEBUG <MAP_IMPORTED_CONFIG_<CONFIG>>` is also -accounted for by this expression. - -Some buildsystems generated by :manual:`cmake(1)` have a predetermined -build-configuration set in the :variable:`CMAKE_BUILD_TYPE` variable. The -buildsystem for the IDEs such as Visual Studio and Xcode are generated -independent of the build-configuration, and the actual build configuration -is not known until build-time. Therefore, code such as - -.. code-block:: cmake - - string(TOLOWER ${CMAKE_BUILD_TYPE} _type) - if (_type STREQUAL debug) - target_compile_definitions(exe1 PRIVATE DEBUG_BUILD) - endif() - -may appear to work for :ref:`Makefile Generators` and :generator:`Ninja` -generators, but is not portable to IDE generators. Additionally, -the :prop_tgt:`IMPORTED` configuration-mappings are not accounted for -with code like this, so it should be avoided. - -The unary ``TARGET_PROPERTY`` generator expression and the ``TARGET_POLICY`` -generator expression are evaluated with the consuming target context. This -means that a usage requirement specification may be evaluated differently based -on the consumer: - -.. code-block:: cmake - - add_library(lib1 lib1.cpp) - target_compile_definitions(lib1 INTERFACE - $<$<STREQUAL:$<TARGET_PROPERTY:TYPE>,EXECUTABLE>:LIB1_WITH_EXE> - $<$<STREQUAL:$<TARGET_PROPERTY:TYPE>,SHARED_LIBRARY>:LIB1_WITH_SHARED_LIB> - $<$<TARGET_POLICY:CMP0041>:CONSUMER_CMP0041_NEW> - ) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1) - - cmake_policy(SET CMP0041 NEW) - - add_library(shared_lib shared_lib.cpp) - target_link_libraries(shared_lib lib1) - -The ``exe1`` executable will be compiled with ``-DLIB1_WITH_EXE``, while the -``shared_lib`` shared library will be compiled with ``-DLIB1_WITH_SHARED_LIB`` -and ``-DCONSUMER_CMP0041_NEW``, because policy :policy:`CMP0041` is -``NEW`` at the point where the ``shared_lib`` target is created. - -The ``BUILD_INTERFACE`` expression wraps requirements which are only used when -consumed from a target in the same buildsystem, or when consumed from a target -exported to the build directory using the :command:`export` command. The -``INSTALL_INTERFACE`` expression wraps requirements which are only used when -consumed from a target which has been installed and exported with the -:command:`install(EXPORT)` command: - -.. code-block:: cmake - - add_library(ClimbingStats climbingstats.cpp) - target_compile_definitions(ClimbingStats INTERFACE - $<BUILD_INTERFACE:ClimbingStats_FROM_BUILD_LOCATION> - $<INSTALL_INTERFACE:ClimbingStats_FROM_INSTALLED_LOCATION> - ) - install(TARGETS ClimbingStats EXPORT libExport ${InstallArgs}) - install(EXPORT libExport NAMESPACE Upstream:: - DESTINATION lib/cmake/ClimbingStats) - export(EXPORT libExport NAMESPACE Upstream::) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 ClimbingStats) - -In this case, the ``exe1`` executable will be compiled with -``-DClimbingStats_FROM_BUILD_LOCATION``. The exporting commands generate -:prop_tgt:`IMPORTED` targets with either the ``INSTALL_INTERFACE`` or the -``BUILD_INTERFACE`` omitted, and the ``*_INTERFACE`` marker stripped away. -A separate project consuming the ``ClimbingStats`` package would contain: - -.. code-block:: cmake - - find_package(ClimbingStats REQUIRED) - - add_executable(Downstream main.cpp) - target_link_libraries(Downstream Upstream::ClimbingStats) - -Depending on whether the ``ClimbingStats`` package was used from the build -location or the install location, the ``Downstream`` target would be compiled -with either ``-DClimbingStats_FROM_BUILD_LOCATION`` or -``-DClimbingStats_FROM_INSTALL_LOCATION``. For more about packages and -exporting see the :manual:`cmake-packages(7)` manual. - -.. _`Include Directories and Usage Requirements`: - -Include Directories and Usage Requirements -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Include directories require some special consideration when specified as usage -requirements and when used with generator expressions. The -:command:`target_include_directories` command accepts both relative and -absolute include directories: - -.. code-block:: cmake - - add_library(lib1 lib1.cpp) - target_include_directories(lib1 PRIVATE - /absolute/path - relative/path - ) - -Relative paths are interpreted relative to the source directory where the -command appears. Relative paths are not allowed in the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of :prop_tgt:`IMPORTED` targets. - -In cases where a non-trivial generator expression is used, the -``INSTALL_PREFIX`` expression may be used within the argument of an -``INSTALL_INTERFACE`` expression. It is a replacement marker which -expands to the installation prefix when imported by a consuming project. - -Include directories usage requirements commonly differ between the build-tree -and the install-tree. The ``BUILD_INTERFACE`` and ``INSTALL_INTERFACE`` -generator expressions can be used to describe separate usage requirements -based on the usage location. Relative paths are allowed within the -``INSTALL_INTERFACE`` expression and are interpreted relative to the -installation prefix. For example: - -.. code-block:: cmake - - add_library(ClimbingStats climbingstats.cpp) - target_include_directories(ClimbingStats INTERFACE - $<BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}/generated> - $<INSTALL_INTERFACE:/absolute/path> - $<INSTALL_INTERFACE:relative/path> - $<INSTALL_INTERFACE:$<INSTALL_PREFIX>/$<CONFIG>/generated> - ) - -Two convenience APIs are provided relating to include directories usage -requirements. The :variable:`CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE` variable -may be enabled, with an equivalent effect to: - -.. code-block:: cmake - - set_property(TARGET tgt APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES - $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR};${CMAKE_CURRENT_BINARY_DIR}> - ) - -for each target affected. The convenience for installed targets is -an ``INCLUDES DESTINATION`` component with the :command:`install(TARGETS)` -command: - -.. code-block:: cmake - - install(TARGETS foo bar bat EXPORT tgts ${dest_args} - INCLUDES DESTINATION include - ) - install(EXPORT tgts ${other_args}) - install(FILES ${headers} DESTINATION include) - -This is equivalent to appending ``${CMAKE_INSTALL_PREFIX}/include`` to the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of each of the installed -:prop_tgt:`IMPORTED` targets when generated by :command:`install(EXPORT)`. - -When the :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of an -:ref:`imported target <Imported targets>` is consumed, the entries in the -property are treated as ``SYSTEM`` include directories, as if they were -listed in the :prop_tgt:`INTERFACE_SYSTEM_INCLUDE_DIRECTORIES` of the -dependency. This can result in omission of compiler warnings for headers -found in those directories. This behavior for :ref:`imported targets` may -be controlled by setting the :prop_tgt:`NO_SYSTEM_FROM_IMPORTED` target -property on the *consumers* of imported targets. - -If a binary target is linked transitively to a macOS :prop_tgt:`FRAMEWORK`, the -``Headers`` directory of the framework is also treated as a usage requirement. -This has the same effect as passing the framework directory as an include -directory. - -Link Libraries and Generator Expressions ----------------------------------------- - -Like build specifications, :prop_tgt:`link libraries <LINK_LIBRARIES>` may be -specified with generator expression conditions. However, as consumption of -usage requirements is based on collection from linked dependencies, there is -an additional limitation that the link dependencies must form a "directed -acyclic graph". That is, if linking to a target is dependent on the value of -a target property, that target property may not be dependent on the linked -dependencies: - -.. code-block:: cmake - - add_library(lib1 lib1.cpp) - add_library(lib2 lib2.cpp) - target_link_libraries(lib1 PUBLIC - $<$<TARGET_PROPERTY:POSITION_INDEPENDENT_CODE>:lib2> - ) - add_library(lib3 lib3.cpp) - set_property(TARGET lib3 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 lib1 lib3) - -As the value of the :prop_tgt:`POSITION_INDEPENDENT_CODE` property of -the ``exe1`` target is dependent on the linked libraries (``lib3``), and the -edge of linking ``exe1`` is determined by the same -:prop_tgt:`POSITION_INDEPENDENT_CODE` property, the dependency graph above -contains a cycle. :manual:`cmake(1)` issues a diagnostic in this case. - -.. _`Output Artifacts`: - -Output Artifacts ----------------- - -The buildsystem targets created by the :command:`add_library` and -:command:`add_executable` commands create rules to create binary outputs. -The exact output location of the binaries can only be determined at -generate-time because it can depend on the build-configuration and the -link-language of linked dependencies etc. ``TARGET_FILE``, -``TARGET_LINKER_FILE`` and related expressions can be used to access the -name and location of generated binaries. These expressions do not work -for ``OBJECT`` libraries however, as there is no single file generated -by such libraries which is relevant to the expressions. - -There are three kinds of output artifacts that may be build by targets -as detailed in the following sections. Their classification differs -between DLL platforms and non-DLL platforms. All Windows-based -systems including Cygwin are DLL platforms. - -.. _`Runtime Output Artifacts`: - -Runtime Output Artifacts -^^^^^^^^^^^^^^^^^^^^^^^^ - -A *runtime* output artifact of a buildsystem target may be: - -* The executable file (e.g. ``.exe``) of an executable target - created by the :command:`add_executable` command. - -* On DLL platforms: the executable file (e.g. ``.dll``) of a shared - library target created by the :command:`add_library` command - with the ``SHARED`` option. - -The :prop_tgt:`RUNTIME_OUTPUT_DIRECTORY` and :prop_tgt:`RUNTIME_OUTPUT_NAME` -target properties may be used to control runtime output artifact locations -and names in the build tree. - -.. _`Library Output Artifacts`: - -Library Output Artifacts -^^^^^^^^^^^^^^^^^^^^^^^^ - -A *library* output artifact of a buildsystem target may be: - -* The loadable module file (e.g. ``.dll`` or ``.so``) of a module - library target created by the :command:`add_library` command - with the ``MODULE`` option. - -* On non-DLL platforms: the shared library file (e.g. ``.so`` or ``.dylib``) - of a shared library target created by the :command:`add_library` - command with the ``SHARED`` option. - -The :prop_tgt:`LIBRARY_OUTPUT_DIRECTORY` and :prop_tgt:`LIBRARY_OUTPUT_NAME` -target properties may be used to control library output artifact locations -and names in the build tree. - -.. _`Archive Output Artifacts`: - -Archive Output Artifacts -^^^^^^^^^^^^^^^^^^^^^^^^ - -An *archive* output artifact of a buildsystem target may be: - -* The static library file (e.g. ``.lib`` or ``.a``) of a static - library target created by the :command:`add_library` command - with the ``STATIC`` option. - -* On DLL platforms: the import library file (e.g. ``.lib``) of a shared - library target created by the :command:`add_library` command - with the ``SHARED`` option. This file is only guaranteed to exist if - the library exports at least one unmanaged symbol. - -* On DLL platforms: the import library file (e.g. ``.lib``) of an - executable target created by the :command:`add_executable` command - when its :prop_tgt:`ENABLE_EXPORTS` target property is set. - -* On AIX: the linker import file (e.g. ``.imp``) of an executable target - created by the :command:`add_executable` command when its - :prop_tgt:`ENABLE_EXPORTS` target property is set. - -The :prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY` and :prop_tgt:`ARCHIVE_OUTPUT_NAME` -target properties may be used to control archive output artifact locations -and names in the build tree. - -Directory-Scoped Commands -------------------------- - -The :command:`target_include_directories`, -:command:`target_compile_definitions` and -:command:`target_compile_options` commands have an effect on only one -target at a time. The commands :command:`add_compile_definitions`, -:command:`add_compile_options` and :command:`include_directories` have -a similar function, but operate at directory scope instead of target -scope for convenience. - -Pseudo Targets -============== - -Some target types do not represent outputs of the buildsystem, but only inputs -such as external dependencies, aliases or other non-build artifacts. Pseudo -targets are not represented in the generated buildsystem. - -.. _`Imported Targets`: - -Imported Targets ----------------- - -An :prop_tgt:`IMPORTED` target represents a pre-existing dependency. Usually -such targets are defined by an upstream package and should be treated as -immutable. After declaring an :prop_tgt:`IMPORTED` target one can adjust its -target properties by using the customary commands such as -:command:`target_compile_definitions`, :command:`target_include_directories`, -:command:`target_compile_options` or :command:`target_link_libraries` just like -with any other regular target. - -:prop_tgt:`IMPORTED` targets may have the same usage requirement properties -populated as binary targets, such as -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`, -:prop_tgt:`INTERFACE_COMPILE_DEFINITIONS`, -:prop_tgt:`INTERFACE_COMPILE_OPTIONS`, -:prop_tgt:`INTERFACE_LINK_LIBRARIES`, and -:prop_tgt:`INTERFACE_POSITION_INDEPENDENT_CODE`. - -The :prop_tgt:`LOCATION` may also be read from an IMPORTED target, though there -is rarely reason to do so. Commands such as :command:`add_custom_command` can -transparently use an :prop_tgt:`IMPORTED` :prop_tgt:`EXECUTABLE <TYPE>` target -as a ``COMMAND`` executable. - -The scope of the definition of an :prop_tgt:`IMPORTED` target is the directory -where it was defined. It may be accessed and used from subdirectories, but -not from parent directories or sibling directories. The scope is similar to -the scope of a cmake variable. - -It is also possible to define a ``GLOBAL`` :prop_tgt:`IMPORTED` target which is -accessible globally in the buildsystem. - -See the :manual:`cmake-packages(7)` manual for more on creating packages -with :prop_tgt:`IMPORTED` targets. - -.. _`Alias Targets`: - -Alias Targets -------------- - -An ``ALIAS`` target is a name which may be used interchangeably with -a binary target name in read-only contexts. A primary use-case for ``ALIAS`` -targets is for example or unit test executables accompanying a library, which -may be part of the same buildsystem or built separately based on user -configuration. - -.. code-block:: cmake - - add_library(lib1 lib1.cpp) - install(TARGETS lib1 EXPORT lib1Export ${dest_args}) - install(EXPORT lib1Export NAMESPACE Upstream:: ${other_args}) - - add_library(Upstream::lib1 ALIAS lib1) - -In another directory, we can link unconditionally to the ``Upstream::lib1`` -target, which may be an :prop_tgt:`IMPORTED` target from a package, or an -``ALIAS`` target if built as part of the same buildsystem. - -.. code-block:: cmake - - if (NOT TARGET Upstream::lib1) - find_package(lib1 REQUIRED) - endif() - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 Upstream::lib1) - -``ALIAS`` targets are not mutable, installable or exportable. They are -entirely local to the buildsystem description. A name can be tested for -whether it is an ``ALIAS`` name by reading the :prop_tgt:`ALIASED_TARGET` -property from it: - -.. code-block:: cmake - - get_target_property(_aliased Upstream::lib1 ALIASED_TARGET) - if(_aliased) - message(STATUS "The name Upstream::lib1 is an ALIAS for ${_aliased}.") - endif() - -.. _`Interface Libraries`: - -Interface Libraries -------------------- - -An ``INTERFACE`` target has no :prop_tgt:`LOCATION` and is mutable, but is -otherwise similar to an :prop_tgt:`IMPORTED` target. - -It may specify usage requirements such as -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`, -:prop_tgt:`INTERFACE_COMPILE_DEFINITIONS`, -:prop_tgt:`INTERFACE_COMPILE_OPTIONS`, -:prop_tgt:`INTERFACE_LINK_LIBRARIES`, -:prop_tgt:`INTERFACE_SOURCES`, -and :prop_tgt:`INTERFACE_POSITION_INDEPENDENT_CODE`. -Only the ``INTERFACE`` modes of the :command:`target_include_directories`, -:command:`target_compile_definitions`, :command:`target_compile_options`, -:command:`target_sources`, and :command:`target_link_libraries` commands -may be used with ``INTERFACE`` libraries. - -A primary use-case for ``INTERFACE`` libraries is header-only libraries. - -.. code-block:: cmake - - add_library(Eigen INTERFACE) - target_include_directories(Eigen INTERFACE - $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/src> - $<INSTALL_INTERFACE:include/Eigen> - ) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 Eigen) - -Here, the usage requirements from the ``Eigen`` target are consumed and used -when compiling, but it has no effect on linking. - -Another use-case is to employ an entirely target-focussed design for usage -requirements: - -.. code-block:: cmake - - add_library(pic_on INTERFACE) - set_property(TARGET pic_on PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON) - add_library(pic_off INTERFACE) - set_property(TARGET pic_off PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE OFF) - - add_library(enable_rtti INTERFACE) - target_compile_options(enable_rtti INTERFACE - $<$<OR:$<COMPILER_ID:GNU>,$<COMPILER_ID:Clang>>:-rtti> - ) - - add_executable(exe1 exe1.cpp) - target_link_libraries(exe1 pic_on enable_rtti) - -This way, the build specification of ``exe1`` is expressed entirely as linked -targets, and the complexity of compiler-specific flags is encapsulated in an -``INTERFACE`` library target. - -The properties permitted to be set on or read from an ``INTERFACE`` library -are: - -* Properties matching ``INTERFACE_*`` -* Built-in properties matching ``COMPATIBLE_INTERFACE_*`` -* ``EXPORT_NAME`` -* ``EXPORT_PROPERTIES`` -* ``IMPORTED`` -* ``MANUALLY_ADDED_DEPENDENCIES`` -* ``NAME`` -* Properties matching ``IMPORTED_LIBNAME_*`` -* Properties matching ``MAP_IMPORTED_CONFIG_*`` - -``INTERFACE`` libraries may be installed and exported. Any content they refer -to must be installed separately: - -.. code-block:: cmake - - add_library(Eigen INTERFACE) - target_include_directories(Eigen INTERFACE - $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/src> - $<INSTALL_INTERFACE:include/Eigen> - ) - - install(TARGETS Eigen EXPORT eigenExport) - install(EXPORT eigenExport NAMESPACE Upstream:: - DESTINATION lib/cmake/Eigen - ) - install(FILES - ${CMAKE_CURRENT_SOURCE_DIR}/src/eigen.h - ${CMAKE_CURRENT_SOURCE_DIR}/src/vector.h - ${CMAKE_CURRENT_SOURCE_DIR}/src/matrix.h - DESTINATION include/Eigen - )
diff --git a/share/cmake-3.18/Help/manual/cmake-commands.7.rst b/share/cmake-3.18/Help/manual/cmake-commands.7.rst deleted file mode 100644 index 0aa4f75..0000000 --- a/share/cmake-3.18/Help/manual/cmake-commands.7.rst +++ /dev/null
@@ -1,173 +0,0 @@ -.. cmake-manual-description: CMake Language Command Reference - -cmake-commands(7) -***************** - -.. only:: html - - .. contents:: - -Scripting Commands -================== - -These commands are always available. - -.. toctree:: - :maxdepth: 1 - - /command/break - /command/cmake_host_system_information - /command/cmake_language - /command/cmake_minimum_required - /command/cmake_parse_arguments - /command/cmake_policy - /command/configure_file - /command/continue - /command/else - /command/elseif - /command/endforeach - /command/endfunction - /command/endif - /command/endmacro - /command/endwhile - /command/execute_process - /command/file - /command/find_file - /command/find_library - /command/find_package - /command/find_path - /command/find_program - /command/foreach - /command/function - /command/get_cmake_property - /command/get_directory_property - /command/get_filename_component - /command/get_property - /command/if - /command/include - /command/include_guard - /command/list - /command/macro - /command/mark_as_advanced - /command/math - /command/message - /command/option - /command/return - /command/separate_arguments - /command/set - /command/set_directory_properties - /command/set_property - /command/site_name - /command/string - /command/unset - /command/variable_watch - /command/while - -Project Commands -================ - -These commands are available only in CMake projects. - -.. toctree:: - :maxdepth: 1 - - /command/add_compile_definitions - /command/add_compile_options - /command/add_custom_command - /command/add_custom_target - /command/add_definitions - /command/add_dependencies - /command/add_executable - /command/add_library - /command/add_link_options - /command/add_subdirectory - /command/add_test - /command/aux_source_directory - /command/build_command - /command/create_test_sourcelist - /command/define_property - /command/enable_language - /command/enable_testing - /command/export - /command/fltk_wrap_ui - /command/get_source_file_property - /command/get_target_property - /command/get_test_property - /command/include_directories - /command/include_external_msproject - /command/include_regular_expression - /command/install - /command/link_directories - /command/link_libraries - /command/load_cache - /command/project - /command/remove_definitions - /command/set_source_files_properties - /command/set_target_properties - /command/set_tests_properties - /command/source_group - /command/target_compile_definitions - /command/target_compile_features - /command/target_compile_options - /command/target_include_directories - /command/target_link_directories - /command/target_link_libraries - /command/target_link_options - /command/target_precompile_headers - /command/target_sources - /command/try_compile - /command/try_run - -.. _`CTest Commands`: - -CTest Commands -============== - -These commands are available only in CTest scripts. - -.. toctree:: - :maxdepth: 1 - - /command/ctest_build - /command/ctest_configure - /command/ctest_coverage - /command/ctest_empty_binary_directory - /command/ctest_memcheck - /command/ctest_read_custom_files - /command/ctest_run_script - /command/ctest_sleep - /command/ctest_start - /command/ctest_submit - /command/ctest_test - /command/ctest_update - /command/ctest_upload - -Deprecated Commands -=================== - -These commands are deprecated and are only made available to maintain -backward compatibility. The documentation of each command states the -CMake version in which it was deprecated. Do not use these commands -in new code. - -.. toctree:: - :maxdepth: 1 - - /command/build_name - /command/exec_program - /command/export_library_dependencies - /command/install_files - /command/install_programs - /command/install_targets - /command/load_command - /command/make_directory - /command/output_required_files - /command/qt_wrap_cpp - /command/qt_wrap_ui - /command/remove - /command/subdir_depends - /command/subdirs - /command/use_mangled_mesa - /command/utility_source - /command/variable_requires - /command/write_file
diff --git a/share/cmake-3.18/Help/manual/cmake-compile-features.7.rst b/share/cmake-3.18/Help/manual/cmake-compile-features.7.rst deleted file mode 100644 index 05dc038..0000000 --- a/share/cmake-3.18/Help/manual/cmake-compile-features.7.rst +++ /dev/null
@@ -1,376 +0,0 @@ -.. cmake-manual-description: CMake Compile Features Reference - -cmake-compile-features(7) -************************* - -.. only:: html - - .. contents:: - -Introduction -============ - -Project source code may depend on, or be conditional on, the availability -of certain features of the compiler. There are three use-cases which arise: -`Compile Feature Requirements`_, `Optional Compile Features`_ -and `Conditional Compilation Options`_. - -While features are typically specified in programming language standards, -CMake provides a primary user interface based on granular handling of -the features, not the language standard that introduced the feature. - -The :prop_gbl:`CMAKE_C_KNOWN_FEATURES`, :prop_gbl:`CMAKE_CUDA_KNOWN_FEATURES`, -and :prop_gbl:`CMAKE_CXX_KNOWN_FEATURES` global properties contain all the -features known to CMake, regardless of compiler support for the feature. -The :variable:`CMAKE_C_COMPILE_FEATURES`, :variable:`CMAKE_CUDA_COMPILE_FEATURES` -, and :variable:`CMAKE_CXX_COMPILE_FEATURES` variables contain all features -CMake knows are known to the compiler, regardless of language standard -or compile flags needed to use them. - -Features known to CMake are named mostly following the same convention -as the Clang feature test macros. There are some exceptions, such as -CMake using ``cxx_final`` and ``cxx_override`` instead of the single -``cxx_override_control`` used by Clang. - -Note that there are no separate compile features properties or variables for -the ``OBJC`` or ``OBJCXX`` languages. These are based off ``C`` or ``C++`` -respectively, so the properties and variables for their corresponding base -language should be used instead. - -Compile Feature Requirements -============================ - -Compile feature requirements may be specified with the -:command:`target_compile_features` command. For example, if a target must -be compiled with compiler support for the -:prop_gbl:`cxx_constexpr <CMAKE_CXX_KNOWN_FEATURES>` feature: - -.. code-block:: cmake - - add_library(mylib requires_constexpr.cpp) - target_compile_features(mylib PRIVATE cxx_constexpr) - -In processing the requirement for the ``cxx_constexpr`` feature, -:manual:`cmake(1)` will ensure that the in-use C++ compiler is capable -of the feature, and will add any necessary flags such as ``-std=gnu++11`` -to the compile lines of C++ files in the ``mylib`` target. A -``FATAL_ERROR`` is issued if the compiler is not capable of the -feature. - -The exact compile flags and language standard are deliberately not part -of the user interface for this use-case. CMake will compute the -appropriate compile flags to use by considering the features specified -for each target. - -Such compile flags are added even if the compiler supports the -particular feature without the flag. For example, the GNU compiler -supports variadic templates (with a warning) even if ``-std=gnu++98`` is -used. CMake adds the ``-std=gnu++11`` flag if ``cxx_variadic_templates`` -is specified as a requirement. - -In the above example, ``mylib`` requires ``cxx_constexpr`` when it -is built itself, but consumers of ``mylib`` are not required to use a -compiler which supports ``cxx_constexpr``. If the interface of -``mylib`` does require the ``cxx_constexpr`` feature (or any other -known feature), that may be specified with the ``PUBLIC`` or -``INTERFACE`` signatures of :command:`target_compile_features`: - -.. code-block:: cmake - - add_library(mylib requires_constexpr.cpp) - # cxx_constexpr is a usage-requirement - target_compile_features(mylib PUBLIC cxx_constexpr) - - # main.cpp will be compiled with -std=gnu++11 on GNU for cxx_constexpr. - add_executable(myexe main.cpp) - target_link_libraries(myexe mylib) - -Feature requirements are evaluated transitively by consuming the link -implementation. See :manual:`cmake-buildsystem(7)` for more on -transitive behavior of build properties and usage requirements. - -Requiring Language Standards ----------------------------- - -In projects that use a large number of commonly available features from -a particular language standard (e.g. C++ 11) one may specify a -meta-feature (e.g. ``cxx_std_11``) that requires use of a compiler mode -that is at minimum aware of that standard, but could be greater. -This is simpler than specifying all the features individually, but does -not guarantee the existence of any particular feature. -Diagnosis of use of unsupported features will be delayed until compile time. - -For example, if C++ 11 features are used extensively in a project's -header files, then clients must use a compiler mode that is no less -than C++ 11. This can be requested with the code: - -.. code-block:: cmake - - target_compile_features(mylib PUBLIC cxx_std_11) - -In this example, CMake will ensure the compiler is invoked in a mode -of at-least C++ 11 (or C++ 14, C++ 17, ...), adding flags such as -``-std=gnu++11`` if necessary. This applies to sources within ``mylib`` -as well as any dependents (that may include headers from ``mylib``). - -Availability of Compiler Extensions ------------------------------------ - -Because the :prop_tgt:`CXX_EXTENSIONS` target property is ``ON`` by default, -CMake uses extended variants of language dialects by default, such as -``-std=gnu++11`` instead of ``-std=c++11``. That target property may be -set to ``OFF`` to use the non-extended variant of the dialect flag. Note -that because most compilers enable extensions by default, this could -expose cross-platform bugs in user code or in the headers of third-party -dependencies. - -Optional Compile Features -========================= - -Compile features may be preferred if available, without creating a hard -requirement. For example, a library may provides alternative -implementations depending on whether the ``cxx_variadic_templates`` -feature is available: - -.. code-block:: c++ - - #if Foo_COMPILER_CXX_VARIADIC_TEMPLATES - template<int I, int... Is> - struct Interface; - - template<int I> - struct Interface<I> - { - static int accumulate() - { - return I; - } - }; - - template<int I, int... Is> - struct Interface - { - static int accumulate() - { - return I + Interface<Is...>::accumulate(); - } - }; - #else - template<int I1, int I2 = 0, int I3 = 0, int I4 = 0> - struct Interface - { - static int accumulate() { return I1 + I2 + I3 + I4; } - }; - #endif - -Such an interface depends on using the correct preprocessor defines for the -compiler features. CMake can generate a header file containing such -defines using the :module:`WriteCompilerDetectionHeader` module. The -module contains the ``write_compiler_detection_header`` function which -accepts parameters to control the content of the generated header file: - -.. code-block:: cmake - - write_compiler_detection_header( - FILE "${CMAKE_CURRENT_BINARY_DIR}/foo_compiler_detection.h" - PREFIX Foo - COMPILERS GNU - FEATURES - cxx_variadic_templates - ) - -Such a header file may be used internally in the source code of a project, -and it may be installed and used in the interface of library code. - -For each feature listed in ``FEATURES``, a preprocessor definition -is created in the header file, and defined to either ``1`` or ``0``. - -Additionally, some features call for additional defines, such as the -``cxx_final`` and ``cxx_override`` features. Rather than being used in -``#ifdef`` code, the ``final`` keyword is abstracted by a symbol -which is defined to either ``final``, a compiler-specific equivalent, or -to empty. That way, C++ code can be written to unconditionally use the -symbol, and compiler support determines what it is expanded to: - -.. code-block:: c++ - - struct Interface { - virtual void Execute() = 0; - }; - - struct Concrete Foo_FINAL { - void Execute() Foo_OVERRIDE; - }; - -In this case, ``Foo_FINAL`` will expand to ``final`` if the -compiler supports the keyword, or to empty otherwise. - -In this use-case, the CMake code will wish to enable a particular language -standard if available from the compiler. The :prop_tgt:`CXX_STANDARD` -target property variable may be set to the desired language standard -for a particular target, and the :variable:`CMAKE_CXX_STANDARD` may be -set to influence all following targets: - -.. code-block:: cmake - - write_compiler_detection_header( - FILE "${CMAKE_CURRENT_BINARY_DIR}/foo_compiler_detection.h" - PREFIX Foo - COMPILERS GNU - FEATURES - cxx_final cxx_override - ) - - # Includes foo_compiler_detection.h and uses the Foo_FINAL symbol - # which will expand to 'final' if the compiler supports the requested - # CXX_STANDARD. - add_library(foo foo.cpp) - set_property(TARGET foo PROPERTY CXX_STANDARD 11) - - # Includes foo_compiler_detection.h and uses the Foo_FINAL symbol - # which will expand to 'final' if the compiler supports the feature, - # even though CXX_STANDARD is not set explicitly. The requirement of - # cxx_constexpr causes CMake to set CXX_STANDARD internally, which - # affects the compile flags. - add_library(foo_impl foo_impl.cpp) - target_compile_features(foo_impl PRIVATE cxx_constexpr) - -The ``write_compiler_detection_header`` function also creates compatibility -code for other features which have standard equivalents. For example, the -``cxx_static_assert`` feature is emulated with a template and abstracted -via the ``<PREFIX>_STATIC_ASSERT`` and ``<PREFIX>_STATIC_ASSERT_MSG`` -function-macros. - -Conditional Compilation Options -=============================== - -Libraries may provide entirely different header files depending on -requested compiler features. - -For example, a header at ``with_variadics/interface.h`` may contain: - -.. code-block:: c++ - - template<int I, int... Is> - struct Interface; - - template<int I> - struct Interface<I> - { - static int accumulate() - { - return I; - } - }; - - template<int I, int... Is> - struct Interface - { - static int accumulate() - { - return I + Interface<Is...>::accumulate(); - } - }; - -while a header at ``no_variadics/interface.h`` may contain: - -.. code-block:: c++ - - template<int I1, int I2 = 0, int I3 = 0, int I4 = 0> - struct Interface - { - static int accumulate() { return I1 + I2 + I3 + I4; } - }; - -It would be possible to write a abstraction ``interface.h`` header -containing something like: - -.. code-block:: c++ - - #include "foo_compiler_detection.h" - #if Foo_COMPILER_CXX_VARIADIC_TEMPLATES - #include "with_variadics/interface.h" - #else - #include "no_variadics/interface.h" - #endif - -However this could be unmaintainable if there are many files to -abstract. What is needed is to use alternative include directories -depending on the compiler capabilities. - -CMake provides a ``COMPILE_FEATURES`` -:manual:`generator expression <cmake-generator-expressions(7)>` to implement -such conditions. This may be used with the build-property commands such as -:command:`target_include_directories` and :command:`target_link_libraries` -to set the appropriate :manual:`buildsystem <cmake-buildsystem(7)>` -properties: - -.. code-block:: cmake - - add_library(foo INTERFACE) - set(with_variadics ${CMAKE_CURRENT_SOURCE_DIR}/with_variadics) - set(no_variadics ${CMAKE_CURRENT_SOURCE_DIR}/no_variadics) - target_include_directories(foo - INTERFACE - "$<$<COMPILE_FEATURES:cxx_variadic_templates>:${with_variadics}>" - "$<$<NOT:$<COMPILE_FEATURES:cxx_variadic_templates>>:${no_variadics}>" - ) - -Consuming code then simply links to the ``foo`` target as usual and uses -the feature-appropriate include directory - -.. code-block:: cmake - - add_executable(consumer_with consumer_with.cpp) - target_link_libraries(consumer_with foo) - set_property(TARGET consumer_with CXX_STANDARD 11) - - add_executable(consumer_no consumer_no.cpp) - target_link_libraries(consumer_no foo) - -Supported Compilers -=================== - -CMake is currently aware of the :prop_tgt:`C++ standards <CXX_STANDARD>` -and :prop_gbl:`compile features <CMAKE_CXX_KNOWN_FEATURES>` available from -the following :variable:`compiler ids <CMAKE_<LANG>_COMPILER_ID>` as of the -versions specified for each: - -* ``AppleClang``: Apple Clang for Xcode versions 4.4+. -* ``Clang``: Clang compiler versions 2.9+. -* ``GNU``: GNU compiler versions 4.4+. -* ``MSVC``: Microsoft Visual Studio versions 2010+. -* ``SunPro``: Oracle SolarisStudio versions 12.4+. -* ``Intel``: Intel compiler versions 12.1+. - -CMake is currently aware of the :prop_tgt:`C standards <C_STANDARD>` -and :prop_gbl:`compile features <CMAKE_C_KNOWN_FEATURES>` available from -the following :variable:`compiler ids <CMAKE_<LANG>_COMPILER_ID>` as of the -versions specified for each: - -* all compilers and versions listed above for C++. -* ``GNU``: GNU compiler versions 3.4+ - -CMake is currently aware of the :prop_tgt:`C++ standards <CXX_STANDARD>` and -their associated meta-features (e.g. ``cxx_std_11``) available from the -following :variable:`compiler ids <CMAKE_<LANG>_COMPILER_ID>` as of the -versions specified for each: - -* ``Cray``: Cray Compiler Environment version 8.1+. -* ``PGI``: PGI version 12.10+. -* ``XL``: IBM XL version 10.1+. - -CMake is currently aware of the :prop_tgt:`C standards <C_STANDARD>` and -their associated meta-features (e.g. ``c_std_99``) available from the -following :variable:`compiler ids <CMAKE_<LANG>_COMPILER_ID>` as of the -versions specified for each: - -* all compilers and versions listed above with only meta-features for C++. -* ``TI``: Texas Instruments compiler. - -CMake is currently aware of the :prop_tgt:`CUDA standards <CUDA_STANDARD>` and -their associated meta-features (e.g. ``cuda_std_11``) available from the -following :variable:`compiler ids <CMAKE_<LANG>_COMPILER_ID>` as of the -versions specified for each: - -* ``NVIDIA``: NVIDIA nvcc compiler 7.5+.
diff --git a/share/cmake-3.18/Help/manual/cmake-developer.7.rst b/share/cmake-3.18/Help/manual/cmake-developer.7.rst deleted file mode 100644 index 85ed935..0000000 --- a/share/cmake-3.18/Help/manual/cmake-developer.7.rst +++ /dev/null
@@ -1,433 +0,0 @@ -.. cmake-manual-description: CMake Developer Reference - -cmake-developer(7) -****************** - -.. only:: html - - .. contents:: - -Introduction -============ - -This manual is intended for reference by developers working with -:manual:`cmake-language(7)` code, whether writing their own modules, -authoring their own build systems, or working on CMake itself. - -See https://cmake.org/get-involved/ to get involved in development of -CMake upstream. It includes links to contribution instructions, which -in turn link to developer guides for CMake itself. - -.. _`Find Modules`: - -Find Modules -============ - -A "find module" is a ``Find<PackageName>.cmake`` file to be loaded -by the :command:`find_package` command when invoked for ``<PackageName>``. - -The primary task of a find module is to determine whether a package -exists on the system, set the ``<PackageName>_FOUND`` variable to reflect -this and provide any variables, macros and imported targets required to -use the package. A find module is useful in cases where an upstream -library does not provide a -:ref:`config file package <Config File Packages>`. - -The traditional approach is to use variables for everything, including -libraries and executables: see the `Standard Variable Names`_ section -below. This is what most of the existing find modules provided by CMake -do. - -The more modern approach is to behave as much like -:ref:`config file packages <Config File Packages>` files as possible, by -providing :ref:`imported target <Imported targets>`. This has the advantage -of propagating :ref:`Target Usage Requirements` to consumers. - -In either case (or even when providing both variables and imported -targets), find modules should provide backwards compatibility with old -versions that had the same name. - -A FindFoo.cmake module will typically be loaded by the command:: - - find_package(Foo [major[.minor[.patch[.tweak]]]] - [EXACT] [QUIET] [REQUIRED] - [[COMPONENTS] [components...]] - [OPTIONAL_COMPONENTS components...] - [NO_POLICY_SCOPE]) - -See the :command:`find_package` documentation for details on what -variables are set for the find module. Most of these are dealt with by -using :module:`FindPackageHandleStandardArgs`. - -Briefly, the module should only locate versions of the package -compatible with the requested version, as described by the -``Foo_FIND_VERSION`` family of variables. If ``Foo_FIND_QUIETLY`` is -set to true, it should avoid printing messages, including anything -complaining about the package not being found. If ``Foo_FIND_REQUIRED`` -is set to true, the module should issue a ``FATAL_ERROR`` if the package -cannot be found. If neither are set to true, it should print a -non-fatal message if it cannot find the package. - -Packages that find multiple semi-independent parts (like bundles of -libraries) should search for the components listed in -``Foo_FIND_COMPONENTS`` if it is set , and only set ``Foo_FOUND`` to -true if for each searched-for component ``<c>`` that was not found, -``Foo_FIND_REQUIRED_<c>`` is not set to true. The ``HANDLE_COMPONENTS`` -argument of ``find_package_handle_standard_args()`` can be used to -implement this. - -If ``Foo_FIND_COMPONENTS`` is not set, which modules are searched for -and required is up to the find module, but should be documented. - -For internal implementation, it is a generally accepted convention that -variables starting with underscore are for temporary use only. - - -.. _`CMake Developer Standard Variable Names`: - -Standard Variable Names ------------------------ - -For a ``FindXxx.cmake`` module that takes the approach of setting -variables (either instead of or in addition to creating imported -targets), the following variable names should be used to keep things -consistent between find modules. Note that all variables start with -``Xxx_`` to make sure they do not interfere with other find modules; the -same consideration applies to macros, functions and imported targets. - -``Xxx_INCLUDE_DIRS`` - The final set of include directories listed in one variable for use by - client code. This should not be a cache entry. - -``Xxx_LIBRARIES`` - The libraries to link against to use Xxx. These should include full - paths. This should not be a cache entry. - -``Xxx_DEFINITIONS`` - Definitions to use when compiling code that uses Xxx. This really - shouldn't include options such as ``-DHAS_JPEG`` that a client - source-code file uses to decide whether to ``#include <jpeg.h>`` - -``Xxx_EXECUTABLE`` - Where to find the Xxx tool. - -``Xxx_Yyy_EXECUTABLE`` - Where to find the Yyy tool that comes with Xxx. - -``Xxx_LIBRARY_DIRS`` - Optionally, the final set of library directories listed in one - variable for use by client code. This should not be a cache entry. - -``Xxx_ROOT_DIR`` - Where to find the base directory of Xxx. - -``Xxx_VERSION_Yy`` - Expect Version Yy if true. Make sure at most one of these is ever true. - -``Xxx_WRAP_Yy`` - If False, do not try to use the relevant CMake wrapping command. - -``Xxx_Yy_FOUND`` - If False, optional Yy part of Xxx system is not available. - -``Xxx_FOUND`` - Set to false, or undefined, if we haven't found, or don't want to use - Xxx. - -``Xxx_NOT_FOUND_MESSAGE`` - Should be set by config-files in the case that it has set - ``Xxx_FOUND`` to FALSE. The contained message will be printed by the - :command:`find_package` command and by - ``find_package_handle_standard_args()`` to inform the user about the - problem. - -``Xxx_RUNTIME_LIBRARY_DIRS`` - Optionally, the runtime library search path for use when running an - executable linked to shared libraries. The list should be used by - user code to create the ``PATH`` on windows or ``LD_LIBRARY_PATH`` on - UNIX. This should not be a cache entry. - -``Xxx_VERSION`` - The full version string of the package found, if any. Note that many - existing modules provide ``Xxx_VERSION_STRING`` instead. - -``Xxx_VERSION_MAJOR`` - The major version of the package found, if any. - -``Xxx_VERSION_MINOR`` - The minor version of the package found, if any. - -``Xxx_VERSION_PATCH`` - The patch version of the package found, if any. - -The following names should not usually be used in CMakeLists.txt files, but -are typically cache variables for users to edit and control the -behaviour of find modules (like entering the path to a library manually) - -``Xxx_LIBRARY`` - The path of the Xxx library (as used with :command:`find_library`, for - example). - -``Xxx_Yy_LIBRARY`` - The path of the Yy library that is part of the Xxx system. It may or - may not be required to use Xxx. - -``Xxx_INCLUDE_DIR`` - Where to find headers for using the Xxx library. - -``Xxx_Yy_INCLUDE_DIR`` - Where to find headers for using the Yy library of the Xxx system. - -To prevent users being overwhelmed with settings to configure, try to -keep as many options as possible out of the cache, leaving at least one -option which can be used to disable use of the module, or locate a -not-found library (e.g. ``Xxx_ROOT_DIR``). For the same reason, mark -most cache options as advanced. For packages which provide both debug -and release binaries, it is common to create cache variables with a -``_LIBRARY_<CONFIG>`` suffix, such as ``Foo_LIBRARY_RELEASE`` and -``Foo_LIBRARY_DEBUG``. - -While these are the standard variable names, you should provide -backwards compatibility for any old names that were actually in use. -Make sure you comment them as deprecated, so that no-one starts using -them. - - -A Sample Find Module --------------------- - -We will describe how to create a simple find module for a library ``Foo``. - -The top of the module should begin with a license notice, followed by -a blank line, and then followed by a :ref:`Bracket Comment`. The comment -should begin with ``.rst:`` to indicate that the rest of its content is -reStructuredText-format documentation. For example: - -:: - - # Distributed under the OSI-approved BSD 3-Clause License. See accompanying - # file Copyright.txt or https://cmake.org/licensing for details. - - #[=======================================================================[.rst: - FindFoo - ------- - - Finds the Foo library. - - Imported Targets - ^^^^^^^^^^^^^^^^ - - This module provides the following imported targets, if found: - - ``Foo::Foo`` - The Foo library - - Result Variables - ^^^^^^^^^^^^^^^^ - - This will define the following variables: - - ``Foo_FOUND`` - True if the system has the Foo library. - ``Foo_VERSION`` - The version of the Foo library which was found. - ``Foo_INCLUDE_DIRS`` - Include directories needed to use Foo. - ``Foo_LIBRARIES`` - Libraries needed to link to Foo. - - Cache Variables - ^^^^^^^^^^^^^^^ - - The following cache variables may also be set: - - ``Foo_INCLUDE_DIR`` - The directory containing ``foo.h``. - ``Foo_LIBRARY`` - The path to the Foo library. - - #]=======================================================================] - -The module documentation consists of: - -* An underlined heading specifying the module name. - -* A simple description of what the module finds. - More description may be required for some packages. If there are - caveats or other details users of the module should be aware of, - specify them here. - -* A section listing imported targets provided by the module, if any. - -* A section listing result variables provided by the module. - -* Optionally a section listing cache variables used by the module, if any. - -If the package provides any macros or functions, they should be listed in -an additional section, but can be documented by additional ``.rst:`` -comment blocks immediately above where those macros or functions are defined. - -The find module implementation may begin below the documentation block. -Now the actual libraries and so on have to be found. The code here will -obviously vary from module to module (dealing with that, after all, is the -point of find modules), but there tends to be a common pattern for libraries. - -First, we try to use ``pkg-config`` to find the library. Note that we -cannot rely on this, as it may not be available, but it provides a good -starting point. - -.. code-block:: cmake - - find_package(PkgConfig) - pkg_check_modules(PC_Foo QUIET Foo) - -This should define some variables starting ``PC_Foo_`` that contain the -information from the ``Foo.pc`` file. - -Now we need to find the libraries and include files; we use the -information from ``pkg-config`` to provide hints to CMake about where to -look. - -.. code-block:: cmake - - find_path(Foo_INCLUDE_DIR - NAMES foo.h - PATHS ${PC_Foo_INCLUDE_DIRS} - PATH_SUFFIXES Foo - ) - find_library(Foo_LIBRARY - NAMES foo - PATHS ${PC_Foo_LIBRARY_DIRS} - ) - -If you have a good way of getting the version (from a header file, for -example), you can use that information to set ``Foo_VERSION`` (although -note that find modules have traditionally used ``Foo_VERSION_STRING``, -so you may want to set both). Otherwise, attempt to use the information -from ``pkg-config`` - -.. code-block:: cmake - - set(Foo_VERSION ${PC_Foo_VERSION}) - -Now we can use :module:`FindPackageHandleStandardArgs` to do most of the -rest of the work for us - -.. code-block:: cmake - - include(FindPackageHandleStandardArgs) - find_package_handle_standard_args(Foo - FOUND_VAR Foo_FOUND - REQUIRED_VARS - Foo_LIBRARY - Foo_INCLUDE_DIR - VERSION_VAR Foo_VERSION - ) - -This will check that the ``REQUIRED_VARS`` contain values (that do not -end in ``-NOTFOUND``) and set ``Foo_FOUND`` appropriately. It will also -cache those values. If ``Foo_VERSION`` is set, and a required version -was passed to :command:`find_package`, it will check the requested version -against the one in ``Foo_VERSION``. It will also print messages as -appropriate; note that if the package was found, it will print the -contents of the first required variable to indicate where it was found. - -At this point, we have to provide a way for users of the find module to -link to the library or libraries that were found. There are two -approaches, as discussed in the `Find Modules`_ section above. The -traditional variable approach looks like - -.. code-block:: cmake - - if(Foo_FOUND) - set(Foo_LIBRARIES ${Foo_LIBRARY}) - set(Foo_INCLUDE_DIRS ${Foo_INCLUDE_DIR}) - set(Foo_DEFINITIONS ${PC_Foo_CFLAGS_OTHER}) - endif() - -If more than one library was found, all of them should be included in -these variables (see the `Standard Variable Names`_ section for more -information). - -When providing imported targets, these should be namespaced (hence the -``Foo::`` prefix); CMake will recognize that values passed to -:command:`target_link_libraries` that contain ``::`` in their name are -supposed to be imported targets (rather than just library names), and -will produce appropriate diagnostic messages if that target does not -exist (see policy :policy:`CMP0028`). - -.. code-block:: cmake - - if(Foo_FOUND AND NOT TARGET Foo::Foo) - add_library(Foo::Foo UNKNOWN IMPORTED) - set_target_properties(Foo::Foo PROPERTIES - IMPORTED_LOCATION "${Foo_LIBRARY}" - INTERFACE_COMPILE_OPTIONS "${PC_Foo_CFLAGS_OTHER}" - INTERFACE_INCLUDE_DIRECTORIES "${Foo_INCLUDE_DIR}" - ) - endif() - -One thing to note about this is that the ``INTERFACE_INCLUDE_DIRECTORIES`` and -similar properties should only contain information about the target itself, and -not any of its dependencies. Instead, those dependencies should also be -targets, and CMake should be told that they are dependencies of this target. -CMake will then combine all the necessary information automatically. - -The type of the :prop_tgt:`IMPORTED` target created in the -:command:`add_library` command can always be specified as ``UNKNOWN`` -type. This simplifies the code in cases where static or shared variants may -be found, and CMake will determine the type by inspecting the files. - -If the library is available with multiple configurations, the -:prop_tgt:`IMPORTED_CONFIGURATIONS` target property should also be -populated: - -.. code-block:: cmake - - if(Foo_FOUND) - if (NOT TARGET Foo::Foo) - add_library(Foo::Foo UNKNOWN IMPORTED) - endif() - if (Foo_LIBRARY_RELEASE) - set_property(TARGET Foo::Foo APPEND PROPERTY - IMPORTED_CONFIGURATIONS RELEASE - ) - set_target_properties(Foo::Foo PROPERTIES - IMPORTED_LOCATION_RELEASE "${Foo_LIBRARY_RELEASE}" - ) - endif() - if (Foo_LIBRARY_DEBUG) - set_property(TARGET Foo::Foo APPEND PROPERTY - IMPORTED_CONFIGURATIONS DEBUG - ) - set_target_properties(Foo::Foo PROPERTIES - IMPORTED_LOCATION_DEBUG "${Foo_LIBRARY_DEBUG}" - ) - endif() - set_target_properties(Foo::Foo PROPERTIES - INTERFACE_COMPILE_OPTIONS "${PC_Foo_CFLAGS_OTHER}" - INTERFACE_INCLUDE_DIRECTORIES "${Foo_INCLUDE_DIR}" - ) - endif() - -The ``RELEASE`` variant should be listed first in the property -so that the variant is chosen if the user uses a configuration which is -not an exact match for any listed ``IMPORTED_CONFIGURATIONS``. - -Most of the cache variables should be hidden in the ``ccmake`` interface unless -the user explicitly asks to edit them. - -.. code-block:: cmake - - mark_as_advanced( - Foo_INCLUDE_DIR - Foo_LIBRARY - ) - -If this module replaces an older version, you should set compatibility variables -to cause the least disruption possible. - -.. code-block:: cmake - - # compatibility variables - set(Foo_VERSION_STRING ${Foo_VERSION})
diff --git a/share/cmake-3.18/Help/manual/cmake-env-variables.7.rst b/share/cmake-3.18/Help/manual/cmake-env-variables.7.rst deleted file mode 100644 index ce1e360..0000000 --- a/share/cmake-3.18/Help/manual/cmake-env-variables.7.rst +++ /dev/null
@@ -1,92 +0,0 @@ -.. cmake-manual-description: CMake Environment Variables Reference - -cmake-env-variables(7) -********************** - -.. only:: html - - .. contents:: - -This page lists environment variables that have special -meaning to CMake. - -For general information on environment variables, see the -:ref:`Environment Variables <CMake Language Environment Variables>` -section in the cmake-language manual. - -Environment Variables that Change Behavior -========================================== - -.. toctree:: - :maxdepth: 1 - - /envvar/CMAKE_PREFIX_PATH - -Environment Variables that Control the Build -============================================ - -.. toctree:: - :maxdepth: 1 - - /envvar/CMAKE_BUILD_PARALLEL_LEVEL - /envvar/CMAKE_CONFIG_TYPE - /envvar/CMAKE_EXPORT_COMPILE_COMMANDS - /envvar/CMAKE_GENERATOR - /envvar/CMAKE_GENERATOR_INSTANCE - /envvar/CMAKE_GENERATOR_PLATFORM - /envvar/CMAKE_GENERATOR_TOOLSET - /envvar/CMAKE_LANG_COMPILER_LAUNCHER - /envvar/CMAKE_MSVCIDE_RUN_PATH - /envvar/CMAKE_NO_VERBOSE - /envvar/CMAKE_OSX_ARCHITECTURES - /envvar/DESTDIR - /envvar/LDFLAGS - /envvar/MACOSX_DEPLOYMENT_TARGET - /envvar/PackageName_ROOT - /envvar/VERBOSE - -Environment Variables for Languages -=================================== - -.. toctree:: - :maxdepth: 1 - - /envvar/ASM_DIALECT - /envvar/ASM_DIALECTFLAGS - /envvar/CC - /envvar/CFLAGS - /envvar/CSFLAGS - /envvar/CUDACXX - /envvar/CUDAFLAGS - /envvar/CUDAHOSTCXX - /envvar/CXX - /envvar/CXXFLAGS - /envvar/FC - /envvar/FFLAGS - /envvar/OBJC - /envvar/OBJCXX - /envvar/RC - /envvar/RCFLAGS - /envvar/SWIFTC - -Environment Variables for CTest -=============================== - -.. toctree:: - :maxdepth: 1 - - /envvar/CMAKE_CONFIG_TYPE - /envvar/CTEST_INTERACTIVE_DEBUG_MODE - /envvar/CTEST_OUTPUT_ON_FAILURE - /envvar/CTEST_PARALLEL_LEVEL - /envvar/CTEST_PROGRESS_OUTPUT - /envvar/CTEST_USE_LAUNCHERS_DEFAULT - /envvar/DASHBOARD_TEST_FROM_CTEST - -Environment Variables for the CMake curses interface -==================================================== - -.. toctree:: - :maxdepth: 1 - - /envvar/CCMAKE_COLORS
diff --git a/share/cmake-3.18/Help/manual/cmake-file-api.7.rst b/share/cmake-3.18/Help/manual/cmake-file-api.7.rst deleted file mode 100644 index cc50952..0000000 --- a/share/cmake-3.18/Help/manual/cmake-file-api.7.rst +++ /dev/null
@@ -1,1135 +0,0 @@ -.. cmake-manual-description: CMake File-Based API - -cmake-file-api(7) -***************** - -.. only:: html - - .. contents:: - -Introduction -============ - -CMake provides a file-based API that clients may use to get semantic -information about the buildsystems CMake generates. Clients may use -the API by writing query files to a specific location in a build tree -to request zero or more `Object Kinds`_. When CMake generates the -buildsystem in that build tree it will read the query files and write -reply files for the client to read. - -The file-based API uses a ``<build>/.cmake/api/`` directory at the top -of a build tree. The API is versioned to support changes to the layout -of files within the API directory. API file layout versioning is -orthogonal to the versioning of `Object Kinds`_ used in replies. -This version of CMake supports only one API version, `API v1`_. - -API v1 -====== - -API v1 is housed in the ``<build>/.cmake/api/v1/`` directory. -It has the following subdirectories: - -``query/`` - Holds query files written by clients. - These may be `v1 Shared Stateless Query Files`_, - `v1 Client Stateless Query Files`_, or `v1 Client Stateful Query Files`_. - -``reply/`` - Holds reply files written by CMake whenever it runs to generate a build - system. These are indexed by a `v1 Reply Index File`_ file that may - reference additional `v1 Reply Files`_. CMake owns all reply files. - Clients must never remove them. - - Clients may look for and read a reply index file at any time. - Clients may optionally create the ``reply/`` directory at any time - and monitor it for the appearance of a new reply index file. - -v1 Shared Stateless Query Files -------------------------------- - -Shared stateless query files allow clients to share requests for -major versions of the `Object Kinds`_ and get all requested versions -recognized by the CMake that runs. - -Clients may create shared requests by creating empty files in the -``v1/query/`` directory. The form is:: - - <build>/.cmake/api/v1/query/<kind>-v<major> - -where ``<kind>`` is one of the `Object Kinds`_, ``-v`` is literal, -and ``<major>`` is the major version number. - -Files of this form are stateless shared queries not owned by any specific -client. Once created they should not be removed without external client -coordination or human intervention. - -v1 Client Stateless Query Files -------------------------------- - -Client stateless query files allow clients to create owned requests for -major versions of the `Object Kinds`_ and get all requested versions -recognized by the CMake that runs. - -Clients may create owned requests by creating empty files in -client-specific query subdirectories. The form is:: - - <build>/.cmake/api/v1/query/client-<client>/<kind>-v<major> - -where ``client-`` is literal, ``<client>`` is a string uniquely -identifying the client, ``<kind>`` is one of the `Object Kinds`_, -``-v`` is literal, and ``<major>`` is the major version number. -Each client must choose a unique ``<client>`` identifier via its -own means. - -Files of this form are stateless queries owned by the client ``<client>``. -The owning client may remove them at any time. - -v1 Client Stateful Query Files ------------------------------- - -Stateful query files allow clients to request a list of versions of -each of the `Object Kinds`_ and get only the most recent version -recognized by the CMake that runs. - -Clients may create owned stateful queries by creating ``query.json`` -files in client-specific query subdirectories. The form is:: - - <build>/.cmake/api/v1/query/client-<client>/query.json - -where ``client-`` is literal, ``<client>`` is a string uniquely -identifying the client, and ``query.json`` is literal. Each client -must choose a unique ``<client>`` identifier via its own means. - -``query.json`` files are stateful queries owned by the client ``<client>``. -The owning client may update or remove them at any time. When a -given client installation is updated it may then update the stateful -query it writes to build trees to request newer object versions. -This can be used to avoid asking CMake to generate multiple object -versions unnecessarily. - -A ``query.json`` file must contain a JSON object: - -.. code-block:: json - - { - "requests": [ - { "kind": "<kind>" , "version": 1 }, - { "kind": "<kind>" , "version": { "major": 1, "minor": 2 } }, - { "kind": "<kind>" , "version": [2, 1] }, - { "kind": "<kind>" , "version": [2, { "major": 1, "minor": 2 }] }, - { "kind": "<kind>" , "version": 1, "client": {} }, - { "kind": "..." } - ], - "client": {} - } - -The members are: - -``requests`` - A JSON array containing zero or more requests. Each request is - a JSON object with members: - - ``kind`` - Specifies one of the `Object Kinds`_ to be included in the reply. - - ``version`` - Indicates the version(s) of the object kind that the client - understands. Versions have major and minor components following - semantic version conventions. The value must be - - * a JSON integer specifying a (non-negative) major version number, or - * a JSON object containing ``major`` and (optionally) ``minor`` - members specifying non-negative integer version components, or - * a JSON array whose elements are each one of the above. - - ``client`` - Optional member reserved for use by the client. This value is - preserved in the reply written for the client in the - `v1 Reply Index File`_ but is otherwise ignored. Clients may use - this to pass custom information with a request through to its reply. - - For each requested object kind CMake will choose the *first* version - that it recognizes for that kind among those listed in the request. - The response will use the selected *major* version with the highest - *minor* version known to the running CMake for that major version. - Therefore clients should list all supported major versions in - preferred order along with the minimal minor version required - for each major version. - -``client`` - Optional member reserved for use by the client. This value is - preserved in the reply written for the client in the - `v1 Reply Index File`_ but is otherwise ignored. Clients may use - this to pass custom information with a query through to its reply. - -Other ``query.json`` top-level members are reserved for future use. -If present they are ignored for forward compatibility. - -v1 Reply Index File -------------------- - -CMake writes an ``index-*.json`` file to the ``v1/reply/`` directory -whenever it runs to generate a build system. Clients must read the -reply index file first and may read other `v1 Reply Files`_ only by -following references. The form of the reply index file name is:: - - <build>/.cmake/api/v1/reply/index-<unspecified>.json - -where ``index-`` is literal and ``<unspecified>`` is an unspecified -name selected by CMake. Whenever a new index file is generated it -is given a new name and any old one is deleted. During the short -time between these steps there may be multiple index files present; -the one with the largest name in lexicographic order is the current -index file. - -The reply index file contains a JSON object: - -.. code-block:: json - - { - "cmake": { - "version": { - "major": 3, "minor": 14, "patch": 0, "suffix": "", - "string": "3.14.0", "isDirty": false - }, - "paths": { - "cmake": "/prefix/bin/cmake", - "ctest": "/prefix/bin/ctest", - "cpack": "/prefix/bin/cpack", - "root": "/prefix/share/cmake-3.14" - }, - "generator": { - "multiConfig": false, - "name": "Unix Makefiles" - } - }, - "objects": [ - { "kind": "<kind>", - "version": { "major": 1, "minor": 0 }, - "jsonFile": "<file>" }, - { "...": "..." } - ], - "reply": { - "<kind>-v<major>": { "kind": "<kind>", - "version": { "major": 1, "minor": 0 }, - "jsonFile": "<file>" }, - "<unknown>": { "error": "unknown query file" }, - "...": {}, - "client-<client>": { - "<kind>-v<major>": { "kind": "<kind>", - "version": { "major": 1, "minor": 0 }, - "jsonFile": "<file>" }, - "<unknown>": { "error": "unknown query file" }, - "...": {}, - "query.json": { - "requests": [ {}, {}, {} ], - "responses": [ - { "kind": "<kind>", - "version": { "major": 1, "minor": 0 }, - "jsonFile": "<file>" }, - { "error": "unknown query file" }, - { "...": {} } - ], - "client": {} - } - } - } - } - -The members are: - -``cmake`` - A JSON object containing information about the instance of CMake that - generated the reply. It contains members: - - ``version`` - A JSON object specifying the version of CMake with members: - - ``major``, ``minor``, ``patch`` - Integer values specifying the major, minor, and patch version components. - ``suffix`` - A string specifying the version suffix, if any, e.g. ``g0abc3``. - ``string`` - A string specifying the full version in the format - ``<major>.<minor>.<patch>[-<suffix>]``. - ``isDirty`` - A boolean indicating whether the version was built from a version - controlled source tree with local modifications. - - ``paths`` - A JSON object specifying paths to things that come with CMake. - It has members for ``cmake``, ``ctest``, and ``cpack`` whose values - are JSON strings specifying the absolute path to each tool, - represented with forward slashes. It also has a ``root`` member for - the absolute path to the directory containing CMake resources like the - ``Modules/`` directory (see :variable:`CMAKE_ROOT`). - - ``generator`` - A JSON object describing the CMake generator used for the build. - It has members: - - ``multiConfig`` - A boolean specifying whether the generator supports multiple output - configurations. - ``name`` - A string specifying the name of the generator. - ``platform`` - If the generator supports :variable:`CMAKE_GENERATOR_PLATFORM`, - this is a string specifying the generator platform name. - -``objects`` - A JSON array listing all versions of all `Object Kinds`_ generated - as part of the reply. Each array entry is a - `v1 Reply File Reference`_. - -``reply`` - A JSON object mirroring the content of the ``query/`` directory - that CMake loaded to produce the reply. The members are of the form - - ``<kind>-v<major>`` - A member of this form appears for each of the - `v1 Shared Stateless Query Files`_ that CMake recognized as a - request for object kind ``<kind>`` with major version ``<major>``. - The value is a `v1 Reply File Reference`_ to the corresponding - reply file for that object kind and version. - - ``<unknown>`` - A member of this form appears for each of the - `v1 Shared Stateless Query Files`_ that CMake did not recognize. - The value is a JSON object with a single ``error`` member - containing a string with an error message indicating that the - query file is unknown. - - ``client-<client>`` - A member of this form appears for each client-owned directory - holding `v1 Client Stateless Query Files`_. - The value is a JSON object mirroring the content of the - ``query/client-<client>/`` directory. The members are of the form: - - ``<kind>-v<major>`` - A member of this form appears for each of the - `v1 Client Stateless Query Files`_ that CMake recognized as a - request for object kind ``<kind>`` with major version ``<major>``. - The value is a `v1 Reply File Reference`_ to the corresponding - reply file for that object kind and version. - - ``<unknown>`` - A member of this form appears for each of the - `v1 Client Stateless Query Files`_ that CMake did not recognize. - The value is a JSON object with a single ``error`` member - containing a string with an error message indicating that the - query file is unknown. - - ``query.json`` - This member appears for clients using - `v1 Client Stateful Query Files`_. - If the ``query.json`` file failed to read or parse as a JSON object, - this member is a JSON object with a single ``error`` member - containing a string with an error message. Otherwise, this member - is a JSON object mirroring the content of the ``query.json`` file. - The members are: - - ``client`` - A copy of the ``query.json`` file ``client`` member, if it exists. - - ``requests`` - A copy of the ``query.json`` file ``requests`` member, if it exists. - - ``responses`` - If the ``query.json`` file ``requests`` member is missing or invalid, - this member is a JSON object with a single ``error`` member - containing a string with an error message. Otherwise, this member - contains a JSON array with a response for each entry of the - ``requests`` array, in the same order. Each response is - - * a JSON object with a single ``error`` member containing a string - with an error message, or - * a `v1 Reply File Reference`_ to the corresponding reply file for - the requested object kind and selected version. - -After reading the reply index file, clients may read the other -`v1 Reply Files`_ it references. - -v1 Reply File Reference -^^^^^^^^^^^^^^^^^^^^^^^ - -The reply index file represents each reference to another reply file -using a JSON object with members: - -``kind`` - A string specifying one of the `Object Kinds`_. -``version`` - A JSON object with members ``major`` and ``minor`` specifying - integer version components of the object kind. -``jsonFile`` - A JSON string specifying a path relative to the reply index file - to another JSON file containing the object. - -v1 Reply Files --------------- - -Reply files containing specific `Object Kinds`_ are written by CMake. -The names of these files are unspecified and must not be interpreted -by clients. Clients must first read the `v1 Reply Index File`_ and -and follow references to the names of the desired response objects. - -Reply files (including the index file) will never be replaced by -files of the same name but different content. This allows a client -to read the files concurrently with a running CMake that may generate -a new reply. However, after generating a new reply CMake will attempt -to remove reply files from previous runs that it did not just write. -If a client attempts to read a reply file referenced by the index but -finds the file missing, that means a concurrent CMake has generated -a new reply. The client may simply start again by reading the new -reply index file. - -.. _`file-api object kinds`: - -Object Kinds -============ - -The CMake file-based API reports semantic information about the build -system using the following kinds of JSON objects. Each kind of object -is versioned independently using semantic versioning with major and -minor components. Every kind of object has the form: - -.. code-block:: json - - { - "kind": "<kind>", - "version": { "major": 1, "minor": 0 }, - "...": {} - } - -The ``kind`` member is a string specifying the object kind name. -The ``version`` member is a JSON object with ``major`` and ``minor`` -members specifying integer components of the object kind's version. -Additional top-level members are specific to each object kind. - -Object Kind "codemodel" ------------------------ - -The ``codemodel`` object kind describes the build system structure as -modeled by CMake. - -There is only one ``codemodel`` object major version, version 2. -Version 1 does not exist to avoid confusion with that from -:manual:`cmake-server(7)` mode. - -"codemodel" version 2 -^^^^^^^^^^^^^^^^^^^^^ - -``codemodel`` object version 2 is a JSON object: - -.. code-block:: json - - { - "kind": "codemodel", - "version": { "major": 2, "minor": 1 }, - "paths": { - "source": "/path/to/top-level-source-dir", - "build": "/path/to/top-level-build-dir" - }, - "configurations": [ - { - "name": "Debug", - "directories": [ - { - "source": ".", - "build": ".", - "childIndexes": [ 1 ], - "projectIndex": 0, - "targetIndexes": [ 0 ], - "hasInstallRule": true, - "minimumCMakeVersion": { - "string": "3.14" - } - }, - { - "source": "sub", - "build": "sub", - "parentIndex": 0, - "projectIndex": 0, - "targetIndexes": [ 1 ], - "minimumCMakeVersion": { - "string": "3.14" - } - } - ], - "projects": [ - { - "name": "MyProject", - "directoryIndexes": [ 0, 1 ], - "targetIndexes": [ 0, 1 ] - } - ], - "targets": [ - { - "name": "MyExecutable", - "directoryIndex": 0, - "projectIndex": 0, - "jsonFile": "<file>" - }, - { - "name": "MyLibrary", - "directoryIndex": 1, - "projectIndex": 0, - "jsonFile": "<file>" - } - ] - } - ] - } - -The members specific to ``codemodel`` objects are: - -``paths`` - A JSON object containing members: - - ``source`` - A string specifying the absolute path to the top-level source directory, - represented with forward slashes. - - ``build`` - A string specifying the absolute path to the top-level build directory, - represented with forward slashes. - -``configurations`` - A JSON array of entries corresponding to available build configurations. - On single-configuration generators there is one entry for the value - of the :variable:`CMAKE_BUILD_TYPE` variable. For multi-configuration - generators there is an entry for each configuration listed in the - :variable:`CMAKE_CONFIGURATION_TYPES` variable. - Each entry is a JSON object containing members: - - ``name`` - A string specifying the name of the configuration, e.g. ``Debug``. - - ``directories`` - A JSON array of entries each corresponding to a build system directory - whose source directory contains a ``CMakeLists.txt`` file. The first - entry corresponds to the top-level directory. Each entry is a - JSON object containing members: - - ``source`` - A string specifying the path to the source directory, represented - with forward slashes. If the directory is inside the top-level - source directory then the path is specified relative to that - directory (with ``.`` for the top-level source directory itself). - Otherwise the path is absolute. - - ``build`` - A string specifying the path to the build directory, represented - with forward slashes. If the directory is inside the top-level - build directory then the path is specified relative to that - directory (with ``.`` for the top-level build directory itself). - Otherwise the path is absolute. - - ``parentIndex`` - Optional member that is present when the directory is not top-level. - The value is an unsigned integer 0-based index of another entry in - the main ``directories`` array that corresponds to the parent - directory that added this directory as a subdirectory. - - ``childIndexes`` - Optional member that is present when the directory has subdirectories. - The value is a JSON array of entries corresponding to child directories - created by the :command:`add_subdirectory` or :command:`subdirs` - command. Each entry is an unsigned integer 0-based index of another - entry in the main ``directories`` array. - - ``projectIndex`` - An unsigned integer 0-based index into the main ``projects`` array - indicating the build system project to which the this directory belongs. - - ``targetIndexes`` - Optional member that is present when the directory itself has targets, - excluding those belonging to subdirectories. The value is a JSON - array of entries corresponding to the targets. Each entry is an - unsigned integer 0-based index into the main ``targets`` array. - - ``minimumCMakeVersion`` - Optional member present when a minimum required version of CMake is - known for the directory. This is the ``<min>`` version given to the - most local call to the :command:`cmake_minimum_required(VERSION)` - command in the directory itself or one of its ancestors. - The value is a JSON object with one member: - - ``string`` - A string specifying the minimum required version in the format:: - - <major>.<minor>[.<patch>[.<tweak>]][<suffix>] - - Each component is an unsigned integer and the suffix may be an - arbitrary string. - - ``hasInstallRule`` - Optional member that is present with boolean value ``true`` when - the directory or one of its subdirectories contains any - :command:`install` rules, i.e. whether a ``make install`` - or equivalent rule is available. - - ``projects`` - A JSON array of entries corresponding to the top-level project - and sub-projects defined in the build system. Each (sub-)project - corresponds to a source directory whose ``CMakeLists.txt`` file - calls the :command:`project` command with a project name different - from its parent directory. The first entry corresponds to the - top-level project. - - Each entry is a JSON object containing members: - - ``name`` - A string specifying the name given to the :command:`project` command. - - ``parentIndex`` - Optional member that is present when the project is not top-level. - The value is an unsigned integer 0-based index of another entry in - the main ``projects`` array that corresponds to the parent project - that added this project as a sub-project. - - ``childIndexes`` - Optional member that is present when the project has sub-projects. - The value is a JSON array of entries corresponding to the sub-projects. - Each entry is an unsigned integer 0-based index of another - entry in the main ``projects`` array. - - ``directoryIndexes`` - A JSON array of entries corresponding to build system directories - that are part of the project. The first entry corresponds to the - top-level directory of the project. Each entry is an unsigned - integer 0-based index into the main ``directories`` array. - - ``targetIndexes`` - Optional member that is present when the project itself has targets, - excluding those belonging to sub-projects. The value is a JSON - array of entries corresponding to the targets. Each entry is an - unsigned integer 0-based index into the main ``targets`` array. - - ``targets`` - A JSON array of entries corresponding to the build system targets. - Such targets are created by calls to :command:`add_executable`, - :command:`add_library`, and :command:`add_custom_target`, excluding - imported targets and interface libraries (which do not generate any - build rules). Each entry is a JSON object containing members: - - ``name`` - A string specifying the target name. - - ``id`` - A string uniquely identifying the target. This matches the ``id`` - field in the file referenced by ``jsonFile``. - - ``directoryIndex`` - An unsigned integer 0-based index into the main ``directories`` array - indicating the build system directory in which the target is defined. - - ``projectIndex`` - An unsigned integer 0-based index into the main ``projects`` array - indicating the build system project in which the target is defined. - - ``jsonFile`` - A JSON string specifying a path relative to the codemodel file - to another JSON file containing a - `"codemodel" version 2 "target" object`_. - -"codemodel" version 2 "target" object -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -A codemodel "target" object is referenced by a `"codemodel" version 2`_ -object's ``targets`` array. Each "target" object is a JSON object -with members: - -``name`` - A string specifying the logical name of the target. - -``id`` - A string uniquely identifying the target. The format is unspecified - and should not be interpreted by clients. - -``type`` - A string specifying the type of the target. The value is one of - ``EXECUTABLE``, ``STATIC_LIBRARY``, ``SHARED_LIBRARY``, - ``MODULE_LIBRARY``, ``OBJECT_LIBRARY``, or ``UTILITY``. - -``backtrace`` - Optional member that is present when a CMake language backtrace to - the command in the source code that created the target is available. - The value is an unsigned integer 0-based index into the - ``backtraceGraph`` member's ``nodes`` array. - -``folder`` - Optional member that is present when the :prop_tgt:`FOLDER` target - property is set. The value is a JSON object with one member: - - ``name`` - A string specifying the name of the target folder. - -``paths`` - A JSON object containing members: - - ``source`` - A string specifying the path to the target's source directory, - represented with forward slashes. If the directory is inside the - top-level source directory then the path is specified relative to - that directory (with ``.`` for the top-level source directory itself). - Otherwise the path is absolute. - - ``build`` - A string specifying the path to the target's build directory, - represented with forward slashes. If the directory is inside the - top-level build directory then the path is specified relative to - that directory (with ``.`` for the top-level build directory itself). - Otherwise the path is absolute. - -``nameOnDisk`` - Optional member that is present for executable and library targets - that are linked or archived into a single primary artifact. - The value is a string specifying the file name of that artifact on disk. - -``artifacts`` - Optional member that is present for executable and library targets - that produce artifacts on disk meant for consumption by dependents. - The value is a JSON array of entries corresponding to the artifacts. - Each entry is a JSON object containing one member: - - ``path`` - A string specifying the path to the file on disk, represented with - forward slashes. If the file is inside the top-level build directory - then the path is specified relative to that directory. - Otherwise the path is absolute. - -``isGeneratorProvided`` - Optional member that is present with boolean value ``true`` if the - target is provided by CMake's build system generator rather than by - a command in the source code. - -``install`` - Optional member that is present when the target has an :command:`install` - rule. The value is a JSON object with members: - - ``prefix`` - A JSON object specifying the installation prefix. It has one member: - - ``path`` - A string specifying the value of :variable:`CMAKE_INSTALL_PREFIX`. - - ``destinations`` - A JSON array of entries specifying an install destination path. - Each entry is a JSON object with members: - - ``path`` - A string specifying the install destination path. The path may - be absolute or relative to the install prefix. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`install` command invocation that specified this - destination is available. The value is an unsigned integer 0-based - index into the ``backtraceGraph`` member's ``nodes`` array. - -``link`` - Optional member that is present for executables and shared library - targets that link into a runtime binary. The value is a JSON object - with members describing the link step: - - ``language`` - A string specifying the language (e.g. ``C``, ``CXX``, ``Fortran``) - of the toolchain is used to invoke the linker. - - ``commandFragments`` - Optional member that is present when fragments of the link command - line invocation are available. The value is a JSON array of entries - specifying ordered fragments. Each entry is a JSON object with members: - - ``fragment`` - A string specifying a fragment of the link command line invocation. - The value is encoded in the build system's native shell format. - - ``role`` - A string specifying the role of the fragment's content: - - * ``flags``: link flags. - * ``libraries``: link library file paths or flags. - * ``libraryPath``: library search path flags. - * ``frameworkPath``: macOS framework search path flags. - - ``lto`` - Optional member that is present with boolean value ``true`` - when link-time optimization (a.k.a. interprocedural optimization - or link-time code generation) is enabled. - - ``sysroot`` - Optional member that is present when the :variable:`CMAKE_SYSROOT_LINK` - or :variable:`CMAKE_SYSROOT` variable is defined. The value is a - JSON object with one member: - - ``path`` - A string specifying the absolute path to the sysroot, represented - with forward slashes. - -``archive`` - Optional member that is present for static library targets. The value - is a JSON object with members describing the archive step: - - ``commandFragments`` - Optional member that is present when fragments of the archiver command - line invocation are available. The value is a JSON array of entries - specifying the fragments. Each entry is a JSON object with members: - - ``fragment`` - A string specifying a fragment of the archiver command line invocation. - The value is encoded in the build system's native shell format. - - ``role`` - A string specifying the role of the fragment's content: - - * ``flags``: archiver flags. - - ``lto`` - Optional member that is present with boolean value ``true`` - when link-time optimization (a.k.a. interprocedural optimization - or link-time code generation) is enabled. - -``dependencies`` - Optional member that is present when the target depends on other targets. - The value is a JSON array of entries corresponding to the dependencies. - Each entry is a JSON object with members: - - ``id`` - A string uniquely identifying the target on which this target depends. - This matches the main ``id`` member of the other target. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`add_dependencies`, :command:`target_link_libraries`, - or other command invocation that created this dependency is - available. The value is an unsigned integer 0-based index into - the ``backtraceGraph`` member's ``nodes`` array. - -``sources`` - A JSON array of entries corresponding to the target's source files. - Each entry is a JSON object with members: - - ``path`` - A string specifying the path to the source file on disk, represented - with forward slashes. If the file is inside the top-level source - directory then the path is specified relative to that directory. - Otherwise the path is absolute. - - ``compileGroupIndex`` - Optional member that is present when the source is compiled. - The value is an unsigned integer 0-based index into the - ``compileGroups`` array. - - ``sourceGroupIndex`` - Optional member that is present when the source is part of a source - group either via the :command:`source_group` command or by default. - The value is an unsigned integer 0-based index into the - ``sourceGroups`` array. - - ``isGenerated`` - Optional member that is present with boolean value ``true`` if - the source is :prop_sf:`GENERATED`. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`target_sources`, :command:`add_executable`, - :command:`add_library`, :command:`add_custom_target`, or other - command invocation that added this source to the target is - available. The value is an unsigned integer 0-based index into - the ``backtraceGraph`` member's ``nodes`` array. - -``sourceGroups`` - Optional member that is present when sources are grouped together by - the :command:`source_group` command or by default. The value is a - JSON array of entries corresponding to the groups. Each entry is - a JSON object with members: - - ``name`` - A string specifying the name of the source group. - - ``sourceIndexes`` - A JSON array listing the sources belonging to the group. - Each entry is an unsigned integer 0-based index into the - main ``sources`` array for the target. - -``compileGroups`` - Optional member that is present when the target has sources that compile. - The value is a JSON array of entries corresponding to groups of sources - that all compile with the same settings. Each entry is a JSON object - with members: - - ``sourceIndexes`` - A JSON array listing the sources belonging to the group. - Each entry is an unsigned integer 0-based index into the - main ``sources`` array for the target. - - ``language`` - A string specifying the language (e.g. ``C``, ``CXX``, ``Fortran``) - of the toolchain is used to compile the source file. - - ``compileCommandFragments`` - Optional member that is present when fragments of the compiler command - line invocation are available. The value is a JSON array of entries - specifying ordered fragments. Each entry is a JSON object with - one member: - - ``fragment`` - A string specifying a fragment of the compile command line invocation. - The value is encoded in the build system's native shell format. - - ``includes`` - Optional member that is present when there are include directories. - The value is a JSON array with an entry for each directory. Each - entry is a JSON object with members: - - ``path`` - A string specifying the path to the include directory, - represented with forward slashes. - - ``isSystem`` - Optional member that is present with boolean value ``true`` if - the include directory is marked as a system include directory. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`target_include_directories` or other command invocation - that added this include directory is available. The value is - an unsigned integer 0-based index into the ``backtraceGraph`` - member's ``nodes`` array. - - ``precompileHeaders`` - Optional member that is present when :command:`target_precompile_headers` - or other command invocations set :prop_tgt:`PRECOMPILE_HEADERS` on the - target. The value is a JSON array with an entry for each header. Each - entry is a JSON object with members: - - ``header`` - Full path to the precompile header file. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`target_precompile_headers` or other command invocation - that added this precompiled header is available. The value is an - unsigned integer 0-based index into the ``backtraceGraph`` member's - ``nodes`` array. - - This field was added in codemodel version 2.1. - - ``defines`` - Optional member that is present when there are preprocessor definitions. - The value is a JSON array with an entry for each definition. Each - entry is a JSON object with members: - - ``define`` - A string specifying the preprocessor definition in the format - ``<name>[=<value>]``, e.g. ``DEF`` or ``DEF=1``. - - ``backtrace`` - Optional member that is present when a CMake language backtrace to - the :command:`target_compile_definitions` or other command invocation - that added this preprocessor definition is available. The value is - an unsigned integer 0-based index into the ``backtraceGraph`` - member's ``nodes`` array. - - ``sysroot`` - Optional member that is present when the - :variable:`CMAKE_SYSROOT_COMPILE` or :variable:`CMAKE_SYSROOT` - variable is defined. The value is a JSON object with one member: - - ``path`` - A string specifying the absolute path to the sysroot, represented - with forward slashes. - -``backtraceGraph`` - A JSON object describing the graph of backtraces whose nodes are - referenced from ``backtrace`` members elsewhere. The members are: - - ``nodes`` - A JSON array listing nodes in the backtrace graph. Each entry - is a JSON object with members: - - ``file`` - An unsigned integer 0-based index into the backtrace ``files`` array. - - ``line`` - An optional member present when the node represents a line within - the file. The value is an unsigned integer 1-based line number. - - ``command`` - An optional member present when the node represents a command - invocation within the file. The value is an unsigned integer - 0-based index into the backtrace ``commands`` array. - - ``parent`` - An optional member present when the node is not the bottom of - the call stack. The value is an unsigned integer 0-based index - of another entry in the backtrace ``nodes`` array. - - ``commands`` - A JSON array listing command names referenced by backtrace nodes. - Each entry is a string specifying a command name. - - ``files`` - A JSON array listing CMake language files referenced by backtrace nodes. - Each entry is a string specifying the path to a file, represented - with forward slashes. If the file is inside the top-level source - directory then the path is specified relative to that directory. - Otherwise the path is absolute. - -Object Kind "cache" -------------------- - -The ``cache`` object kind lists cache entries. These are the -:ref:`CMake Language Variables` stored in the persistent cache -(``CMakeCache.txt``) for the build tree. - -There is only one ``cache`` object major version, version 2. -Version 1 does not exist to avoid confusion with that from -:manual:`cmake-server(7)` mode. - -"cache" version 2 -^^^^^^^^^^^^^^^^^ - -``cache`` object version 2 is a JSON object: - -.. code-block:: json - - { - "kind": "cache", - "version": { "major": 2, "minor": 0 }, - "entries": [ - { - "name": "BUILD_SHARED_LIBS", - "value": "ON", - "type": "BOOL", - "properties": [ - { - "name": "HELPSTRING", - "value": "Build shared libraries" - } - ] - }, - { - "name": "CMAKE_GENERATOR", - "value": "Unix Makefiles", - "type": "INTERNAL", - "properties": [ - { - "name": "HELPSTRING", - "value": "Name of generator." - } - ] - } - ] - } - -The members specific to ``cache`` objects are: - -``entries`` - A JSON array whose entries are each a JSON object specifying a - cache entry. The members of each entry are: - - ``name`` - A string specifying the name of the entry. - - ``value`` - A string specifying the value of the entry. - - ``type`` - A string specifying the type of the entry used by - :manual:`cmake-gui(1)` to choose a widget for editing. - - ``properties`` - A JSON array of entries specifying associated - :ref:`cache entry properties <Cache Entry Properties>`. - Each entry is a JSON object containing members: - - ``name`` - A string specifying the name of the cache entry property. - - ``value`` - A string specifying the value of the cache entry property. - -Object Kind "cmakeFiles" ------------------------- - -The ``cmakeFiles`` object kind lists files used by CMake while -configuring and generating the build system. These include the -``CMakeLists.txt`` files as well as included ``.cmake`` files. - -There is only one ``cmakeFiles`` object major version, version 1. - -"cmakeFiles" version 1 -^^^^^^^^^^^^^^^^^^^^^^ - -``cmakeFiles`` object version 1 is a JSON object: - -.. code-block:: json - - { - "kind": "cmakeFiles", - "version": { "major": 1, "minor": 0 }, - "paths": { - "build": "/path/to/top-level-build-dir", - "source": "/path/to/top-level-source-dir" - }, - "inputs": [ - { - "path": "CMakeLists.txt" - }, - { - "isGenerated": true, - "path": "/path/to/top-level-build-dir/.../CMakeSystem.cmake" - }, - { - "isExternal": true, - "path": "/path/to/external/third-party/module.cmake" - }, - { - "isCMake": true, - "isExternal": true, - "path": "/path/to/cmake/Modules/CMakeGenericSystem.cmake" - } - ] - } - -The members specific to ``cmakeFiles`` objects are: - -``paths`` - A JSON object containing members: - - ``source`` - A string specifying the absolute path to the top-level source directory, - represented with forward slashes. - - ``build`` - A string specifying the absolute path to the top-level build directory, - represented with forward slashes. - -``inputs`` - A JSON array whose entries are each a JSON object specifying an input - file used by CMake when configuring and generating the build system. - The members of each entry are: - - ``path`` - A string specifying the path to an input file to CMake, represented - with forward slashes. If the file is inside the top-level source - directory then the path is specified relative to that directory. - Otherwise the path is absolute. - - ``isGenerated`` - Optional member that is present with boolean value ``true`` - if the path specifies a file that is under the top-level - build directory and the build is out-of-source. - This member is not available on in-source builds. - - ``isExternal`` - Optional member that is present with boolean value ``true`` - if the path specifies a file that is not under the top-level - source or build directories. - - ``isCMake`` - Optional member that is present with boolean value ``true`` - if the path specifies a file in the CMake installation.
diff --git a/share/cmake-3.18/Help/manual/cmake-generator-expressions.7.rst b/share/cmake-3.18/Help/manual/cmake-generator-expressions.7.rst deleted file mode 100644 index 124da44..0000000 --- a/share/cmake-3.18/Help/manual/cmake-generator-expressions.7.rst +++ /dev/null
@@ -1,791 +0,0 @@ -.. cmake-manual-description: CMake Generator Expressions - -cmake-generator-expressions(7) -****************************** - -.. only:: html - - .. contents:: - -Introduction -============ - -Generator expressions are evaluated during build system generation to produce -information specific to each build configuration. - -Generator expressions are allowed in the context of many target properties, -such as :prop_tgt:`LINK_LIBRARIES`, :prop_tgt:`INCLUDE_DIRECTORIES`, -:prop_tgt:`COMPILE_DEFINITIONS` and others. They may also be used when using -commands to populate those properties, such as :command:`target_link_libraries`, -:command:`target_include_directories`, :command:`target_compile_definitions` -and others. - -They enable conditional linking, conditional definitions used when compiling, -conditional include directories, and more. The conditions may be based on -the build configuration, target properties, platform information or any other -queryable information. - -Generator expressions have the form ``$<...>``. To avoid confusion, this page -deviates from most of the CMake documentation in that it omits angular brackets -``<...>`` around placeholders like ``condition``, ``string``, ``target``, -among others. - -Generator expressions can be nested, as shown in most of the examples below. - -.. _`Boolean Generator Expressions`: - -Boolean Generator Expressions -============================= - -Boolean expressions evaluate to either ``0`` or ``1``. -They are typically used to construct the condition in a :ref:`conditional -generator expression<Conditional Generator Expressions>`. - -Available boolean expressions are: - -Logical Operators ------------------ - -``$<BOOL:string>`` - Converts ``string`` to ``0`` or ``1``. Evaluates to ``0`` if any of the - following is true: - - * ``string`` is empty, - * ``string`` is a case-insensitive equal of - ``0``, ``FALSE``, ``OFF``, ``N``, ``NO``, ``IGNORE``, or ``NOTFOUND``, or - * ``string`` ends in the suffix ``-NOTFOUND`` (case-sensitive). - - Otherwise evaluates to ``1``. - -``$<AND:conditions>`` - where ``conditions`` is a comma-separated list of boolean expressions. - Evaluates to ``1`` if all conditions are ``1``. - Otherwise evaluates to ``0``. - -``$<OR:conditions>`` - where ``conditions`` is a comma-separated list of boolean expressions. - Evaluates to ``1`` if at least one of the conditions is ``1``. - Otherwise evaluates to ``0``. - -``$<NOT:condition>`` - ``0`` if ``condition`` is ``1``, else ``1``. - -String Comparisons ------------------- - -``$<STREQUAL:string1,string2>`` - ``1`` if ``string1`` and ``string2`` are equal, else ``0``. - The comparison is case-sensitive. For a case-insensitive comparison, - combine with a :ref:`string transforming generator expression - <String Transforming Generator Expressions>`, - - .. code-block:: cmake - - $<STREQUAL:$<UPPER_CASE:${foo}>,"BAR"> # "1" if ${foo} is any of "BAR", "Bar", "bar", ... - -``$<EQUAL:value1,value2>`` - ``1`` if ``value1`` and ``value2`` are numerically equal, else ``0``. -``$<IN_LIST:string,list>`` - ``1`` if ``string`` is member of the semicolon-separated ``list``, else ``0``. - Uses case-sensitive comparisons. -``$<VERSION_LESS:v1,v2>`` - ``1`` if ``v1`` is a version less than ``v2``, else ``0``. -``$<VERSION_GREATER:v1,v2>`` - ``1`` if ``v1`` is a version greater than ``v2``, else ``0``. -``$<VERSION_EQUAL:v1,v2>`` - ``1`` if ``v1`` is the same version as ``v2``, else ``0``. -``$<VERSION_LESS_EQUAL:v1,v2>`` - ``1`` if ``v1`` is a version less than or equal to ``v2``, else ``0``. -``$<VERSION_GREATER_EQUAL:v1,v2>`` - ``1`` if ``v1`` is a version greater than or equal to ``v2``, else ``0``. - - -Variable Queries ----------------- - -``$<TARGET_EXISTS:target>`` - ``1`` if ``target`` exists, else ``0``. -``$<CONFIG:cfg>`` - ``1`` if config is ``cfg``, else ``0``. This is a case-insensitive comparison. - The mapping in :prop_tgt:`MAP_IMPORTED_CONFIG_<CONFIG>` is also considered by - this expression when it is evaluated on a property on an :prop_tgt:`IMPORTED` - target. -``$<PLATFORM_ID:platform_ids>`` - where ``platform_ids`` is a comma-separated list. - ``1`` if the CMake's platform id matches any one of the entries in - ``platform_ids``, otherwise ``0``. - See also the :variable:`CMAKE_SYSTEM_NAME` variable. -``$<C_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the C compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<CXX_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the CXX compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<CUDA_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the CUDA compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<OBJC_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the Objective-C compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<OBJCXX_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the Objective-C++ compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<Fortran_COMPILER_ID:compiler_ids>`` - where ``compiler_ids`` is a comma-separated list. - ``1`` if the CMake's compiler id of the Fortran compiler matches any one - of the entries in ``compiler_ids``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<C_COMPILER_VERSION:version>`` - ``1`` if the version of the C compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<CXX_COMPILER_VERSION:version>`` - ``1`` if the version of the CXX compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<CUDA_COMPILER_VERSION:version>`` - ``1`` if the version of the CXX compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<OBJC_COMPILER_VERSION:version>`` - ``1`` if the version of the OBJC compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<OBJCXX_COMPILER_VERSION:version>`` - ``1`` if the version of the OBJCXX compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<Fortran_COMPILER_VERSION:version>`` - ``1`` if the version of the Fortran compiler matches ``version``, otherwise ``0``. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<TARGET_POLICY:policy>`` - ``1`` if the ``policy`` was NEW when the 'head' target was created, - else ``0``. If the ``policy`` was not set, the warning message for the policy - will be emitted. This generator expression only works for a subset of - policies. -``$<COMPILE_FEATURES:features>`` - where ``features`` is a comma-spearated list. - Evaluates to ``1`` if all of the ``features`` are available for the 'head' - target, and ``0`` otherwise. If this expression is used while evaluating - the link implementation of a target and if any dependency transitively - increases the required :prop_tgt:`C_STANDARD` or :prop_tgt:`CXX_STANDARD` - for the 'head' target, an error is reported. See the - :manual:`cmake-compile-features(7)` manual for information on - compile features and a list of supported compilers. - -.. _`Boolean COMPILE_LANGUAGE Generator Expression`: - -``$<COMPILE_LANG_AND_ID:language,compiler_ids>`` - ``1`` when the language used for compilation unit matches ``language`` and - the CMake's compiler id of the language compiler matches any one of the - entries in ``compiler_ids``, otherwise ``0``. This expression is a short form - for the combination of ``$<COMPILE_LANGUAGE:language>`` and - ``$<LANG_COMPILER_ID:compiler_ids>``. This expression may be used to specify - compile options, compile definitions, and include directories for source files of a - particular language and compiler combination in a target. For example: - - .. code-block:: cmake - - add_executable(myapp main.cpp foo.c bar.cpp zot.cu) - target_compile_definitions(myapp - PRIVATE $<$<COMPILE_LANG_AND_ID:CXX,AppleClang,Clang>:COMPILING_CXX_WITH_CLANG> - $<$<COMPILE_LANG_AND_ID:CXX,Intel>:COMPILING_CXX_WITH_INTEL> - $<$<COMPILE_LANG_AND_ID:C,Clang>:COMPILING_C_WITH_CLANG> - ) - - This specifies the use of different compile definitions based on both - the compiler id and compilation language. This example will have a - ``COMPILING_CXX_WITH_CLANG`` compile definition when Clang is the CXX - compiler, and ``COMPILING_CXX_WITH_INTEL`` when Intel is the CXX compiler. - Likewise when the C compiler is Clang it will only see the ``COMPILING_C_WITH_CLANG`` - definition. - - Without the ``COMPILE_LANG_AND_ID`` generator expression the same logic - would be expressed as: - - .. code-block:: cmake - - target_compile_definitions(myapp - PRIVATE $<$<AND:$<COMPILE_LANGUAGE:CXX>,$<CXX_COMPILER_ID:AppleClang,Clang>>:COMPILING_CXX_WITH_CLANG> - $<$<AND:$<COMPILE_LANGUAGE:CXX>,$<CXX_COMPILER_ID:Intel>>:COMPILING_CXX_WITH_INTEL> - $<$<AND:$<COMPILE_LANGUAGE:C>,$<C_COMPILER_ID:Clang>>:COMPILING_C_WITH_CLANG> - ) - -``$<COMPILE_LANGUAGE:languages>`` - ``1`` when the language used for compilation unit matches any of the entries - in ``languages``, otherwise ``0``. This expression may be used to specify - compile options, compile definitions, and include directories for source files of a - particular language in a target. For example: - - .. code-block:: cmake - - add_executable(myapp main.cpp foo.c bar.cpp zot.cu) - target_compile_options(myapp - PRIVATE $<$<COMPILE_LANGUAGE:CXX>:-fno-exceptions> - ) - target_compile_definitions(myapp - PRIVATE $<$<COMPILE_LANGUAGE:CXX>:COMPILING_CXX> - $<$<COMPILE_LANGUAGE:CUDA>:COMPILING_CUDA> - ) - target_include_directories(myapp - PRIVATE $<$<COMPILE_LANGUAGE:CXX,CUDA>:/opt/foo/headers> - ) - - This specifies the use of the ``-fno-exceptions`` compile option, - ``COMPILING_CXX`` compile definition, and ``cxx_headers`` include - directory for C++ only (compiler id checks elided). It also specifies - a ``COMPILING_CUDA`` compile definition for CUDA. - - Note that with :ref:`Visual Studio Generators` and :generator:`Xcode` there - is no way to represent target-wide compile definitions or include directories - separately for ``C`` and ``CXX`` languages. - Also, with :ref:`Visual Studio Generators` there is no way to represent - target-wide flags separately for ``C`` and ``CXX`` languages. Under these - generators, expressions for both C and C++ sources will be evaluated - using ``CXX`` if there are any C++ sources and otherwise using ``C``. - A workaround is to create separate libraries for each source file language - instead: - - .. code-block:: cmake - - add_library(myapp_c foo.c) - add_library(myapp_cxx bar.cpp) - target_compile_options(myapp_cxx PUBLIC -fno-exceptions) - add_executable(myapp main.cpp) - target_link_libraries(myapp myapp_c myapp_cxx) - -.. _`Boolean LINK_LANGUAGE Generator Expression`: - -``$<LINK_LANG_AND_ID:language,compiler_ids>`` - ``1`` when the language used for link step matches ``language`` and the - CMake's compiler id of the language linker matches any one of the entries - in ``compiler_ids``, otherwise ``0``. This expression is a short form for the - combination of ``$<LINK_LANGUAGE:language>`` and - ``$<LANG_COMPILER_ID:compiler_ids>``. This expression may be used to specify - link libraries, link options, link directories and link dependencies of a - particular language and linker combination in a target. For example: - - .. code-block:: cmake - - add_library(libC_Clang ...) - add_library(libCXX_Clang ...) - add_library(libC_Intel ...) - add_library(libCXX_Intel ...) - - add_executable(myapp main.c) - if (CXX_CONFIG) - target_sources(myapp PRIVATE file.cxx) - endif() - target_link_libraries(myapp - PRIVATE $<$<LINK_LANG_AND_ID:CXX,Clang,AppleClang>:libCXX_Clang> - $<$<LINK_LANG_AND_ID:C,Clang,AppleClang>:libC_Clang> - $<$<LINK_LANG_AND_ID:CXX,Intel>:libCXX_Intel> - $<$<LINK_LANG_AND_ID:C,Intel>:libC_Intel>) - - This specifies the use of different link libraries based on both the - compiler id and link language. This example will have target ``libCXX_Clang`` - as link dependency when ``Clang`` or ``AppleClang`` is the ``CXX`` - linker, and ``libCXX_Intel`` when ``Intel`` is the ``CXX`` linker. - Likewise when the ``C`` linker is ``Clang`` or ``AppleClang``, target - ``libC_Clang`` will be added as link dependency and ``libC_Intel`` when - ``Intel`` is the ``C`` linker. - - See :ref:`the note related to - <Constraints LINK_LANGUAGE Generator Expression>` - ``$<LINK_LANGUAGE:language>`` for constraints about the usage of this - generator expression. - -``$<LINK_LANGUAGE:languages>`` - ``1`` when the language used for link step matches any of the entries - in ``languages``, otherwise ``0``. This expression may be used to specify - link libraries, link options, link directories and link dependencies of a - particular language in a target. For example: - - .. code-block:: cmake - - add_library(api_C ...) - add_library(api_CXX ...) - add_library(api INTERFACE) - target_link_options(api INTERFACE $<$<LINK_LANGUAGE:C>:-opt_c> - $<$<LINK_LANGUAGE:CXX>:-opt_cxx>) - target_link_libraries(api INTERFACE $<$<LINK_LANGUAGE:C>:api_C> - $<$<LINK_LANGUAGE:CXX>:api_CXX>) - - add_executable(myapp1 main.c) - target_link_options(myapp1 PRIVATE api) - - add_executable(myapp2 main.cpp) - target_link_options(myapp2 PRIVATE api) - - This specifies to use the ``api`` target for linking targets ``myapp1`` and - ``myapp2``. In practice, ``myapp1`` will link with target ``api_C`` and - option ``-opt_c`` because it will use ``C`` as link language. And ``myapp2`` - will link with ``api_CXX`` and option ``-opt_cxx`` because ``CXX`` will be - the link language. - - .. _`Constraints LINK_LANGUAGE Generator Expression`: - - .. note:: - - To determine the link language of a target, it is required to collect, - transitively, all the targets which will be linked to it. So, for link - libraries properties, a double evaluation will be done. During the first - evaluation, ``$<LINK_LANGUAGE:..>`` expressions will always return ``0``. - The link language computed after this first pass will be used to do the - second pass. To avoid inconsistency, it is required that the second pass - do not change the link language. Moreover, to avoid unexpected - side-effects, it is required to specify complete entities as part of the - ``$<LINK_LANGUAGE:..>`` expression. For example: - - .. code-block:: cmake - - add_library(lib STATIC file.cxx) - add_library(libother STATIC file.c) - - # bad usage - add_executable(myapp1 main.c) - target_link_libraries(myapp1 PRIVATE lib$<$<LINK_LANGUAGE:C>:other>) - - # correct usage - add_executable(myapp2 main.c) - target_link_libraries(myapp2 PRIVATE $<$<LINK_LANGUAGE:C>:libother>) - - In this example, for ``myapp1``, the first pass will, unexpectedly, - determine that the link language is ``CXX`` because the evaluation of the - generator expression will be an empty string so ``myapp1`` will depends on - target ``lib`` which is ``C++``. On the contrary, for ``myapp2``, the first - evaluation will give ``C`` as link language, so the second pass will - correctly add target ``libother`` as link dependency. - -``$<DEVICE_LINK:list>`` - Returns the list if it is the device link step, an empty list otherwise. - The device link step is controlled by :prop_tgt:`CUDA_SEPARABLE_COMPILATION` - and :prop_tgt:`CUDA_RESOLVE_DEVICE_SYMBOLS` properties and - policy :policy:`CMP0105`. This expression can only be used to specify link - options. - -``$<HOST_LINK:list>`` - Returns the list if it is the normal link step, an empty list otherwise. - This expression is mainly useful when a device link step is also involved - (see ``$<DEVICE_LINK:list>`` generator expression). This expression can only - be used to specify link options. - -String-Valued Generator Expressions -=================================== - -These expressions expand to some string. -For example, - -.. code-block:: cmake - - include_directories(/usr/include/$<CXX_COMPILER_ID>/) - -expands to ``/usr/include/GNU/`` or ``/usr/include/Clang/`` etc, depending on -the compiler identifier. - -String-valued expressions may also be combined with other expressions. -Here an example for a string-valued expression within a boolean expressions -within a conditional expression: - -.. code-block:: cmake - - $<$<VERSION_LESS:$<CXX_COMPILER_VERSION>,4.2.0>:OLD_COMPILER> - -expands to ``OLD_COMPILER`` if the -:variable:`CMAKE_CXX_COMPILER_VERSION <CMAKE_<LANG>_COMPILER_VERSION>` is less -than 4.2.0. - -And here two nested string-valued expressions: - -.. code-block:: cmake - - -I$<JOIN:$<TARGET_PROPERTY:INCLUDE_DIRECTORIES>, -I> - -generates a string of the entries in the :prop_tgt:`INCLUDE_DIRECTORIES` target -property with each entry preceded by ``-I``. - -Expanding on the previous example, if one first wants to check if the -``INCLUDE_DIRECTORIES`` property is non-empty, then it is advisable to -introduce a helper variable to keep the code readable: - -.. code-block:: cmake - - set(prop "$<TARGET_PROPERTY:INCLUDE_DIRECTORIES>") # helper variable - $<$<BOOL:${prop}>:-I$<JOIN:${prop}, -I>> - -The following string-valued generator expressions are available: - -Escaped Characters ------------------- - -String literals to escape the special meaning a character would otherwise have: - -``$<ANGLE-R>`` - A literal ``>``. Used for example to compare strings that contain a ``>``. -``$<COMMA>`` - A literal ``,``. Used for example to compare strings which contain a ``,``. -``$<SEMICOLON>`` - A literal ``;``. Used to prevent list expansion on an argument with ``;``. - -.. _`Conditional Generator Expressions`: - -Conditional Expressions ------------------------ - -Conditional generator expressions depend on a boolean condition -that must be ``0`` or ``1``. - -``$<condition:true_string>`` - Evaluates to ``true_string`` if ``condition`` is ``1``. - Otherwise evaluates to the empty string. - -``$<IF:condition,true_string,false_string>`` - Evaluates to ``true_string`` if ``condition`` is ``1``. - Otherwise evaluates to ``false_string``. - -Typically, the ``condition`` is a :ref:`boolean generator expression -<Boolean Generator Expressions>`. For instance, - -.. code-block:: cmake - - $<$<CONFIG:Debug>:DEBUG_MODE> - -expands to ``DEBUG_MODE`` when the ``Debug`` configuration is used, and -otherwise expands to the empty string. - -.. _`String Transforming Generator Expressions`: - -String Transformations ----------------------- - -``$<JOIN:list,string>`` - Joins the list with the content of ``string``. -``$<REMOVE_DUPLICATES:list>`` - Removes duplicated items in the given ``list``. -``$<FILTER:list,INCLUDE|EXCLUDE,regex>`` - Includes or removes items from ``list`` that match the regular expression ``regex``. -``$<LOWER_CASE:string>`` - Content of ``string`` converted to lower case. -``$<UPPER_CASE:string>`` - Content of ``string`` converted to upper case. - -``$<GENEX_EVAL:expr>`` - Content of ``expr`` evaluated as a generator expression in the current - context. This enables consumption of generator expressions whose - evaluation results itself in generator expressions. -``$<TARGET_GENEX_EVAL:tgt,expr>`` - Content of ``expr`` evaluated as a generator expression in the context of - ``tgt`` target. This enables consumption of custom target properties that - themselves contain generator expressions. - - Having the capability to evaluate generator expressions is very useful when - you want to manage custom properties supporting generator expressions. - For example: - - .. code-block:: cmake - - add_library(foo ...) - - set_property(TARGET foo PROPERTY - CUSTOM_KEYS $<$<CONFIG:DEBUG>:FOO_EXTRA_THINGS> - ) - - add_custom_target(printFooKeys - COMMAND ${CMAKE_COMMAND} -E echo $<TARGET_PROPERTY:foo,CUSTOM_KEYS> - ) - - This naive implementation of the ``printFooKeys`` custom command is wrong - because ``CUSTOM_KEYS`` target property is not evaluated and the content - is passed as is (i.e. ``$<$<CONFIG:DEBUG>:FOO_EXTRA_THINGS>``). - - To have the expected result (i.e. ``FOO_EXTRA_THINGS`` if config is - ``Debug``), it is required to evaluate the output of - ``$<TARGET_PROPERTY:foo,CUSTOM_KEYS>``: - - .. code-block:: cmake - - add_custom_target(printFooKeys - COMMAND ${CMAKE_COMMAND} -E - echo $<TARGET_GENEX_EVAL:foo,$<TARGET_PROPERTY:foo,CUSTOM_KEYS>> - ) - -Variable Queries ----------------- - -``$<CONFIG>`` - Configuration name. -``$<CONFIGURATION>`` - Configuration name. Deprecated since CMake 3.0. Use ``CONFIG`` instead. -``$<PLATFORM_ID>`` - The current system's CMake platform id. - See also the :variable:`CMAKE_SYSTEM_NAME` variable. -``$<C_COMPILER_ID>`` - The CMake's compiler id of the C compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<CXX_COMPILER_ID>`` - The CMake's compiler id of the CXX compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<CUDA_COMPILER_ID>`` - The CMake's compiler id of the CUDA compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<OBJC_COMPILER_ID>`` - The CMake's compiler id of the OBJC compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<OBJCXX_COMPILER_ID>`` - The CMake's compiler id of the OBJCXX compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<Fortran_COMPILER_ID>`` - The CMake's compiler id of the Fortran compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_ID` variable. -``$<C_COMPILER_VERSION>`` - The version of the C compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<CXX_COMPILER_VERSION>`` - The version of the CXX compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<CUDA_COMPILER_VERSION>`` - The version of the CUDA compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<OBJC_COMPILER_VERSION>`` - The version of the OBJC compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<OBJCXX_COMPILER_VERSION>`` - The version of the OBJCXX compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<Fortran_COMPILER_VERSION>`` - The version of the Fortran compiler used. - See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable. -``$<COMPILE_LANGUAGE>`` - The compile language of source files when evaluating compile options. - See :ref:`the related boolean expression - <Boolean COMPILE_LANGUAGE Generator Expression>` - ``$<COMPILE_LANGUAGE:language>`` - for notes about the portability of this generator expression. -``$<LINK_LANGUAGE>`` - The link language of target when evaluating link options. - See :ref:`the related boolean expression - <Boolean LINK_LANGUAGE Generator Expression>` ``$<LINK_LANGUAGE:language>`` - for notes about the portability of this generator expression. - - .. note:: - - This generator expression is not supported by the link libraries - properties to avoid side-effects due to the double evaluation of - these properties. - -Target-Dependent Queries ------------------------- - -These queries refer to a target ``tgt``. This can be any runtime artifact, -namely: - -* an executable target created by :command:`add_executable` -* a shared library target (``.so``, ``.dll`` but not their ``.lib`` import library) - created by :command:`add_library` -* a static library target created by :command:`add_library` - -In the following, "the ``tgt`` filename" means the name of the ``tgt`` -binary file. This has to be distinguished from "the target name", -which is just the string ``tgt``. - -``$<TARGET_NAME_IF_EXISTS:tgt>`` - The target name ``tgt`` if the target exists, an empty string otherwise. -``$<TARGET_FILE:tgt>`` - Full path to the ``tgt`` binary file. -``$<TARGET_FILE_BASE_NAME:tgt>`` - Base name of ``tgt``, i.e. ``$<TARGET_FILE_NAME:tgt>`` without prefix and - suffix. - For example, if the ``tgt`` filename is ``libbase.so``, the base name is ``base``. - - See also the :prop_tgt:`OUTPUT_NAME`, :prop_tgt:`ARCHIVE_OUTPUT_NAME`, - :prop_tgt:`LIBRARY_OUTPUT_NAME` and :prop_tgt:`RUNTIME_OUTPUT_NAME` - target properties and their configuration specific variants - :prop_tgt:`OUTPUT_NAME_<CONFIG>`, :prop_tgt:`ARCHIVE_OUTPUT_NAME_<CONFIG>`, - :prop_tgt:`LIBRARY_OUTPUT_NAME_<CONFIG>` and - :prop_tgt:`RUNTIME_OUTPUT_NAME_<CONFIG>`. - - The :prop_tgt:`<CONFIG>_POSTFIX` and :prop_tgt:`DEBUG_POSTFIX` target - properties can also be considered. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_FILE_PREFIX:tgt>`` - Prefix of the ``tgt`` filename (such as ``lib``). - - See also the :prop_tgt:`PREFIX` target property. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_FILE_SUFFIX:tgt>`` - Suffix of the ``tgt`` filename (extension such as ``.so`` or ``.exe``). - - See also the :prop_tgt:`SUFFIX` target property. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_FILE_NAME:tgt>`` - The ``tgt`` filename. -``$<TARGET_FILE_DIR:tgt>`` - Directory of the ``tgt`` binary file. -``$<TARGET_LINKER_FILE:tgt>`` - File used when linking to the ``tgt`` target. This will usually - be the library that ``tgt`` represents (``.a``, ``.lib``, ``.so``), - but for a shared library on DLL platforms, it would be the ``.lib`` - import library associated with the DLL. -``$<TARGET_LINKER_FILE_BASE_NAME:tgt>`` - Base name of file used to link the target ``tgt``, i.e. - ``$<TARGET_LINKER_FILE_NAME:tgt>`` without prefix and suffix. For example, - if target file name is ``libbase.a``, the base name is ``base``. - - See also the :prop_tgt:`OUTPUT_NAME`, :prop_tgt:`ARCHIVE_OUTPUT_NAME`, - and :prop_tgt:`LIBRARY_OUTPUT_NAME` target properties and their configuration - specific variants :prop_tgt:`OUTPUT_NAME_<CONFIG>`, - :prop_tgt:`ARCHIVE_OUTPUT_NAME_<CONFIG>` and - :prop_tgt:`LIBRARY_OUTPUT_NAME_<CONFIG>`. - - The :prop_tgt:`<CONFIG>_POSTFIX` and :prop_tgt:`DEBUG_POSTFIX` target - properties can also be considered. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_LINKER_FILE_PREFIX:tgt>`` - Prefix of file used to link target ``tgt``. - - See also the :prop_tgt:`PREFIX` and :prop_tgt:`IMPORT_PREFIX` target - properties. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_LINKER_FILE_SUFFIX:tgt>`` - Suffix of file used to link where ``tgt`` is the name of a target. - - The suffix corresponds to the file extension (such as ".so" or ".lib"). - - See also the :prop_tgt:`SUFFIX` and :prop_tgt:`IMPORT_SUFFIX` target - properties. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_LINKER_FILE_NAME:tgt>`` - Name of file used to link target ``tgt``. -``$<TARGET_LINKER_FILE_DIR:tgt>`` - Directory of file used to link target ``tgt``. -``$<TARGET_SONAME_FILE:tgt>`` - File with soname (``.so.3``) where ``tgt`` is the name of a target. -``$<TARGET_SONAME_FILE_NAME:tgt>`` - Name of file with soname (``.so.3``). -``$<TARGET_SONAME_FILE_DIR:tgt>`` - Directory of with soname (``.so.3``). -``$<TARGET_PDB_FILE:tgt>`` - Full path to the linker generated program database file (.pdb) - where ``tgt`` is the name of a target. - - See also the :prop_tgt:`PDB_NAME` and :prop_tgt:`PDB_OUTPUT_DIRECTORY` - target properties and their configuration specific variants - :prop_tgt:`PDB_NAME_<CONFIG>` and :prop_tgt:`PDB_OUTPUT_DIRECTORY_<CONFIG>`. -``$<TARGET_PDB_FILE_BASE_NAME:tgt>`` - Base name of the linker generated program database file (.pdb) - where ``tgt`` is the name of a target. - - The base name corresponds to the target PDB file name (see - ``$<TARGET_PDB_FILE_NAME:tgt>``) without prefix and suffix. For example, - if target file name is ``base.pdb``, the base name is ``base``. - - See also the :prop_tgt:`PDB_NAME` target property and its configuration - specific variant :prop_tgt:`PDB_NAME_<CONFIG>`. - - The :prop_tgt:`<CONFIG>_POSTFIX` and :prop_tgt:`DEBUG_POSTFIX` target - properties can also be considered. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_PDB_FILE_NAME:tgt>`` - Name of the linker generated program database file (.pdb). -``$<TARGET_PDB_FILE_DIR:tgt>`` - Directory of the linker generated program database file (.pdb). -``$<TARGET_BUNDLE_DIR:tgt>`` - Full path to the bundle directory (``my.app``, ``my.framework``, or - ``my.bundle``) where ``tgt`` is the name of a target. -``$<TARGET_BUNDLE_CONTENT_DIR:tgt>`` - Full path to the bundle content directory where ``tgt`` is the name of a - target. For the macOS SDK it leads to ``my.app/Contents``, ``my.framework``, - or ``my.bundle/Contents``. For all other SDKs (e.g. iOS) it leads to - ``my.app``, ``my.framework``, or ``my.bundle`` due to the flat bundle - structure. -``$<TARGET_PROPERTY:tgt,prop>`` - Value of the property ``prop`` on the target ``tgt``. - - Note that ``tgt`` is not added as a dependency of the target this - expression is evaluated on. -``$<TARGET_PROPERTY:prop>`` - Value of the property ``prop`` on the target for which the expression - is being evaluated. Note that for generator expressions in - :ref:`Target Usage Requirements` this is the consuming target rather - than the target specifying the requirement. -``$<INSTALL_PREFIX>`` - Content of the install prefix when the target is exported via - :command:`install(EXPORT)`, or when evaluated in - :prop_tgt:`INSTALL_NAME_DIR`, and empty otherwise. - -Output-Related Expressions --------------------------- - -``$<TARGET_NAME:...>`` - Marks ``...`` as being the name of a target. This is required if exporting - targets to multiple dependent export sets. The ``...`` must be a literal - name of a target- it may not contain generator expressions. -``$<LINK_ONLY:...>`` - Content of ``...`` except when evaluated in a link interface while - propagating :ref:`Target Usage Requirements`, in which case it is the - empty string. - Intended for use only in an :prop_tgt:`INTERFACE_LINK_LIBRARIES` target - property, perhaps via the :command:`target_link_libraries` command, - to specify private link dependencies without other usage requirements. -``$<INSTALL_INTERFACE:...>`` - Content of ``...`` when the property is exported using :command:`install(EXPORT)`, - and empty otherwise. -``$<BUILD_INTERFACE:...>`` - Content of ``...`` when the property is exported using :command:`export`, or - when the target is used by another target in the same buildsystem. Expands to - the empty string otherwise. -``$<MAKE_C_IDENTIFIER:...>`` - Content of ``...`` converted to a C identifier. The conversion follows the - same behavior as :command:`string(MAKE_C_IDENTIFIER)`. -``$<TARGET_OBJECTS:objLib>`` - List of objects resulting from build of ``objLib``. -``$<SHELL_PATH:...>`` - Content of ``...`` converted to shell path style. For example, slashes are - converted to backslashes in Windows shells and drive letters are converted - to posix paths in MSYS shells. The ``...`` must be an absolute path. - The ``...`` may be a :ref:`semicolon-separated list <CMake Language Lists>` - of paths, in which case each path is converted individually and a result - list is generated using the shell path separator (``:`` on POSIX and - ``;`` on Windows). Be sure to enclose the argument containing this genex - in double quotes in CMake source code so that ``;`` does not split arguments. - -Debugging -========= - -Since generator expressions are evaluated during generation of the buildsystem, -and not during processing of ``CMakeLists.txt`` files, it is not possible to -inspect their result with the :command:`message()` command. - -One possible way to generate debug messages is to add a custom target, - -.. code-block:: cmake - - add_custom_target(genexdebug COMMAND ${CMAKE_COMMAND} -E echo "$<...>") - -The shell command ``make genexdebug`` (invoked after execution of ``cmake``) -would then print the result of ``$<...>``. - -Another way is to write debug messages to a file: - -.. code-block:: cmake - - file(GENERATE OUTPUT filename CONTENT "$<...>")
diff --git a/share/cmake-3.18/Help/manual/cmake-generators.7.rst b/share/cmake-3.18/Help/manual/cmake-generators.7.rst deleted file mode 100644 index 6f88c0a..0000000 --- a/share/cmake-3.18/Help/manual/cmake-generators.7.rst +++ /dev/null
@@ -1,118 +0,0 @@ -.. cmake-manual-description: CMake Generators Reference - -cmake-generators(7) -******************* - -.. only:: html - - .. contents:: - -Introduction -============ - -A *CMake Generator* is responsible for writing the input files for -a native build system. Exactly one of the `CMake Generators`_ must be -selected for a build tree to determine what native build system is to -be used. Optionally one of the `Extra Generators`_ may be selected -as a variant of some of the `Command-Line Build Tool Generators`_ to -produce project files for an auxiliary IDE. - -CMake Generators are platform-specific so each may be available only -on certain platforms. The :manual:`cmake(1)` command-line tool ``--help`` -output lists available generators on the current platform. Use its ``-G`` -option to specify the generator for a new build tree. -The :manual:`cmake-gui(1)` offers interactive selection of a generator -when creating a new build tree. - -CMake Generators -================ - -.. _`Command-Line Build Tool Generators`: - -Command-Line Build Tool Generators ----------------------------------- - -These generators support command-line build tools. In order to use them, -one must launch CMake from a command-line prompt whose environment is -already configured for the chosen compiler and build tool. - -.. _`Makefile Generators`: - -Makefile Generators -^^^^^^^^^^^^^^^^^^^ - -.. toctree:: - :maxdepth: 1 - - /generator/Borland Makefiles - /generator/MSYS Makefiles - /generator/MinGW Makefiles - /generator/NMake Makefiles - /generator/NMake Makefiles JOM - /generator/Unix Makefiles - /generator/Watcom WMake - -Ninja Generators -^^^^^^^^^^^^^^^^ - -.. toctree:: - :maxdepth: 1 - - /generator/Ninja - /generator/Ninja Multi-Config - -.. _`IDE Build Tool Generators`: - -IDE Build Tool Generators -------------------------- - -These generators support Integrated Development Environment (IDE) -project files. Since the IDEs configure their own environment -one may launch CMake from any environment. - -.. _`Visual Studio Generators`: - -Visual Studio Generators -^^^^^^^^^^^^^^^^^^^^^^^^ - -.. toctree:: - :maxdepth: 1 - - /generator/Visual Studio 6 - /generator/Visual Studio 7 - /generator/Visual Studio 7 .NET 2003 - /generator/Visual Studio 8 2005 - /generator/Visual Studio 9 2008 - /generator/Visual Studio 10 2010 - /generator/Visual Studio 11 2012 - /generator/Visual Studio 12 2013 - /generator/Visual Studio 14 2015 - /generator/Visual Studio 15 2017 - /generator/Visual Studio 16 2019 - -Other Generators -^^^^^^^^^^^^^^^^ - -.. toctree:: - :maxdepth: 1 - - /generator/Green Hills MULTI - /generator/Xcode - -Extra Generators -================ - -Some of the `CMake Generators`_ listed in the :manual:`cmake(1)` -command-line tool ``--help`` output may have variants that specify -an extra generator for an auxiliary IDE tool. Such generator -names have the form ``<extra-generator> - <main-generator>``. -The following extra generators are known to CMake. - -.. toctree:: - :maxdepth: 1 - - /generator/CodeBlocks - /generator/CodeLite - /generator/Eclipse CDT4 - /generator/Kate - /generator/Sublime Text 2
diff --git a/share/cmake-3.18/Help/manual/cmake-gui.1.rst b/share/cmake-3.18/Help/manual/cmake-gui.1.rst deleted file mode 100644 index ff8311b..0000000 --- a/share/cmake-3.18/Help/manual/cmake-gui.1.rst +++ /dev/null
@@ -1,44 +0,0 @@ -.. cmake-manual-description: CMake GUI Command-Line Reference - -cmake-gui(1) -************ - -Synopsis -======== - -.. parsed-literal:: - - cmake-gui [<options>] - cmake-gui [<options>] {<path-to-source> | <path-to-existing-build>} - cmake-gui [<options>] -S <path-to-source> -B <path-to-build> - -Description -=========== - -The **cmake-gui** executable is the CMake GUI. Project configuration -settings may be specified interactively. Brief instructions are -provided at the bottom of the window when the program is running. - -CMake is a cross-platform build system generator. Projects specify -their build process with platform-independent CMake listfiles included -in each directory of a source tree with the name ``CMakeLists.txt``. -Users build a project by using CMake to generate a build system for a -native tool on their platform. - -Options -======= - -``-S <path-to-source>`` - Path to root directory of the CMake project to build. - -``-B <path-to-build>`` - Path to directory which CMake will use as the root of build directory. - - If the directory doesn't already exist CMake will make it. - -.. include:: OPTIONS_HELP.txt - -See Also -======== - -.. include:: LINKS.txt
diff --git a/share/cmake-3.18/Help/manual/cmake-modules.7.rst b/share/cmake-3.18/Help/manual/cmake-modules.7.rst deleted file mode 100644 index 50131e8..0000000 --- a/share/cmake-3.18/Help/manual/cmake-modules.7.rst +++ /dev/null
@@ -1,319 +0,0 @@ -.. cmake-manual-description: CMake Modules Reference - -cmake-modules(7) -**************** - -The modules listed here are part of the CMake distribution. -Projects may provide further modules; their location(s) -can be specified in the :variable:`CMAKE_MODULE_PATH` variable. - -Utility Modules -^^^^^^^^^^^^^^^ - -These modules are loaded using the :command:`include` command. - -.. toctree:: - :maxdepth: 1 - - /module/AddFileDependencies - /module/AndroidTestUtilities - /module/BundleUtilities - /module/CheckCCompilerFlag - /module/CheckCSourceCompiles - /module/CheckCSourceRuns - /module/CheckCXXCompilerFlag - /module/CheckCXXSourceCompiles - /module/CheckCXXSourceRuns - /module/CheckCXXSymbolExists - /module/CheckFortranCompilerFlag - /module/CheckFortranFunctionExists - /module/CheckFortranSourceCompiles - /module/CheckFortranSourceRuns - /module/CheckFunctionExists - /module/CheckIPOSupported - /module/CheckIncludeFileCXX - /module/CheckIncludeFile - /module/CheckIncludeFiles - /module/CheckLanguage - /module/CheckLibraryExists - /module/CheckLinkerFlag - /module/CheckOBJCCompilerFlag - /module/CheckOBJCSourceCompiles - /module/CheckOBJCSourceRuns - /module/CheckOBJCXXCompilerFlag - /module/CheckOBJCXXSourceCompiles - /module/CheckOBJCXXSourceRuns - /module/CheckPIESupported - /module/CheckPrototypeDefinition - /module/CheckStructHasMember - /module/CheckSymbolExists - /module/CheckTypeSize - /module/CheckVariableExists - /module/CMakeAddFortranSubdirectory - /module/CMakeBackwardCompatibilityCXX - /module/CMakeDependentOption - /module/CMakeFindDependencyMacro - /module/CMakeFindFrameworks - /module/CMakeFindPackageMode - /module/CMakeGraphVizOptions - /module/CMakePackageConfigHelpers - /module/CMakePrintHelpers - /module/CMakePrintSystemInformation - /module/CMakePushCheckState - /module/CMakeVerifyManifest - /module/CPackComponent - /module/CPackIFW - /module/CPackIFWConfigureFile - /module/CPack - /module/CSharpUtilities - /module/CTest - /module/CTestCoverageCollectGCOV - /module/CTestScriptMode - /module/CTestUseLaunchers - /module/Dart - /module/DeployQt4 - /module/Documentation - /module/ExternalData - /module/ExternalProject - /module/FeatureSummary - /module/FetchContent - /module/FindPackageHandleStandardArgs - /module/FindPackageMessage - /module/FortranCInterface - /module/GenerateExportHeader - /module/GetPrerequisites - /module/GNUInstallDirs - /module/GoogleTest - /module/InstallRequiredSystemLibraries - /module/ProcessorCount - /module/SelectLibraryConfigurations - /module/SquishTestScript - /module/TestBigEndian - /module/TestForANSIForScope - /module/TestForANSIStreamHeaders - /module/TestForSSTREAM - /module/TestForSTDNamespace - /module/UseEcos - /module/UseJavaClassFilelist - /module/UseJava - /module/UseJavaSymlinks - /module/UseSWIG - /module/UsewxWidgets - /module/WriteCompilerDetectionHeader - -Find Modules -^^^^^^^^^^^^ - -These modules search for third-party software. -They are normally called through the :command:`find_package` command. - -.. toctree:: - :maxdepth: 1 - - /module/FindALSA - /module/FindArmadillo - /module/FindASPELL - /module/FindAVIFile - /module/FindBISON - /module/FindBLAS - /module/FindBacktrace - /module/FindBoost - /module/FindBullet - /module/FindBZip2 - /module/FindCABLE - /module/FindCoin3D - /module/FindCups - /module/FindCUDAToolkit - /module/FindCURL - /module/FindCurses - /module/FindCVS - /module/FindCxxTest - /module/FindCygwin - /module/FindDart - /module/FindDCMTK - /module/FindDevIL - /module/FindDoxygen - /module/FindEnvModules - /module/FindEXPAT - /module/FindFLEX - /module/FindFLTK2 - /module/FindFLTK - /module/FindFontconfig - /module/FindFreetype - /module/FindGCCXML - /module/FindGDAL - /module/FindGettext - /module/FindGIF - /module/FindGit - /module/FindGLEW - /module/FindGLUT - /module/FindGnuplot - /module/FindGnuTLS - /module/FindGSL - /module/FindGTest - /module/FindGTK2 - /module/FindGTK - /module/FindHDF5 - /module/FindHg - /module/FindHSPELL - /module/FindHTMLHelp - /module/FindIce - /module/FindIcotool - /module/FindICU - /module/FindImageMagick - /module/FindIconv - /module/FindIntl - /module/FindITK - /module/FindJasper - /module/FindJava - /module/FindJNI - /module/FindJPEG - /module/FindKDE3 - /module/FindKDE4 - /module/FindLAPACK - /module/FindLATEX - /module/FindLibArchive - /module/FindLibinput - /module/FindLibLZMA - /module/FindLibXml2 - /module/FindLibXslt - /module/FindLTTngUST - /module/FindLua50 - /module/FindLua51 - /module/FindLua - /module/FindMatlab - /module/FindMFC - /module/FindMotif - /module/FindMPEG2 - /module/FindMPEG - /module/FindMPI - /module/FindODBC - /module/FindOpenACC - /module/FindOpenAL - /module/FindOpenCL - /module/FindOpenGL - /module/FindOpenMP - /module/FindOpenSceneGraph - /module/FindOpenSSL - /module/FindOpenThreads - /module/FindosgAnimation - /module/FindosgDB - /module/Findosg_functions - /module/FindosgFX - /module/FindosgGA - /module/FindosgIntrospection - /module/FindosgManipulator - /module/FindosgParticle - /module/FindosgPresentation - /module/FindosgProducer - /module/FindosgQt - /module/Findosg - /module/FindosgShadow - /module/FindosgSim - /module/FindosgTerrain - /module/FindosgText - /module/FindosgUtil - /module/FindosgViewer - /module/FindosgVolume - /module/FindosgWidget - /module/FindPatch - /module/FindPerlLibs - /module/FindPerl - /module/FindPHP4 - /module/FindPhysFS - /module/FindPike - /module/FindPkgConfig - /module/FindPNG - /module/FindPostgreSQL - /module/FindProducer - /module/FindProtobuf - /module/FindPython - /module/FindPython2 - /module/FindPython3 - /module/FindQt3 - /module/FindQt4 - /module/FindQuickTime - /module/FindRTI - /module/FindRuby - /module/FindSDL_image - /module/FindSDL_mixer - /module/FindSDL_net - /module/FindSDL - /module/FindSDL_sound - /module/FindSDL_ttf - /module/FindSelfPackers - /module/FindSquish - /module/FindSQLite3 - /module/FindSubversion - /module/FindSWIG - /module/FindTCL - /module/FindTclsh - /module/FindTclStub - /module/FindThreads - /module/FindTIFF - /module/FindUnixCommands - /module/FindVTK - /module/FindVulkan - /module/FindWget - /module/FindWish - /module/FindwxWidgets - /module/FindXCTest - /module/FindXalanC - /module/FindXercesC - /module/FindX11 - /module/FindXMLRPC - /module/FindZLIB - -Deprecated Modules -^^^^^^^^^^^^^^^^^^^ - -Deprecated Utility Modules -========================== - -.. toctree:: - :maxdepth: 1 - - /module/CMakeDetermineVSServicePack - /module/CMakeExpandImportedTargets - /module/CMakeForceCompiler - /module/CMakeParseArguments - /module/MacroAddFileDependencies - /module/TestCXXAcceptsFlag - /module/UsePkgConfig - /module/Use_wxWindows - /module/WriteBasicConfigVersionFile - -Deprecated Find Modules -======================= - -.. toctree:: - :maxdepth: 1 - - /module/FindCUDA - /module/FindPythonInterp - /module/FindPythonLibs - /module/FindQt - /module/FindwxWindows - -Legacy CPack Modules -==================== - -These modules used to be mistakenly exposed to the user, and have been moved -out of user visibility. They are for CPack internal use, and should never be -used directly. - -.. toctree:: - :maxdepth: 1 - - /module/CPackArchive - /module/CPackBundle - /module/CPackCygwin - /module/CPackDeb - /module/CPackDMG - /module/CPackFreeBSD - /module/CPackNSIS - /module/CPackNuGet - /module/CPackPackageMaker - /module/CPackProductBuild - /module/CPackRPM - /module/CPackWIX
diff --git a/share/cmake-3.18/Help/manual/cmake-packages.7.rst b/share/cmake-3.18/Help/manual/cmake-packages.7.rst deleted file mode 100644 index 4b2934a..0000000 --- a/share/cmake-3.18/Help/manual/cmake-packages.7.rst +++ /dev/null
@@ -1,719 +0,0 @@ -.. cmake-manual-description: CMake Packages Reference - -cmake-packages(7) -***************** - -.. only:: html - - .. contents:: - -Introduction -============ - -Packages provide dependency information to CMake based buildsystems. Packages -are found with the :command:`find_package` command. The result of -using :command:`find_package` is either a set of :prop_tgt:`IMPORTED` targets, or -a set of variables corresponding to build-relevant information. - -Using Packages -============== - -CMake provides direct support for two forms of packages, -`Config-file Packages`_ and `Find-module Packages`_. -Indirect support for ``pkg-config`` packages is also provided via -the :module:`FindPkgConfig` module. In all cases, the basic form -of :command:`find_package` calls is the same: - -.. code-block:: cmake - - find_package(Qt4 4.7.0 REQUIRED) # CMake provides a Qt4 find-module - find_package(Qt5Core 5.1.0 REQUIRED) # Qt provides a Qt5 package config file. - find_package(LibXml2 REQUIRED) # Use pkg-config via the LibXml2 find-module - -In cases where it is known that a package configuration file is provided by -upstream, and only that should be used, the ``CONFIG`` keyword may be passed -to :command:`find_package`: - -.. code-block:: cmake - - find_package(Qt5Core 5.1.0 CONFIG REQUIRED) - find_package(Qt5Gui 5.1.0 CONFIG) - -Similarly, the ``MODULE`` keyword says to use only a find-module: - -.. code-block:: cmake - - find_package(Qt4 4.7.0 MODULE REQUIRED) - -Specifying the type of package explicitly improves the error message shown to -the user if it is not found. - -Both types of packages also support specifying components of a package, -either after the ``REQUIRED`` keyword: - -.. code-block:: cmake - - find_package(Qt5 5.1.0 CONFIG REQUIRED Widgets Xml Sql) - -or as a separate ``COMPONENTS`` list: - -.. code-block:: cmake - - find_package(Qt5 5.1.0 COMPONENTS Widgets Xml Sql) - -or as a separate ``OPTIONAL_COMPONENTS`` list: - -.. code-block:: cmake - - find_package(Qt5 5.1.0 COMPONENTS Widgets - OPTIONAL_COMPONENTS Xml Sql - ) - -Handling of ``COMPONENTS`` and ``OPTIONAL_COMPONENTS`` is defined by the -package. - -By setting the :variable:`CMAKE_DISABLE_FIND_PACKAGE_<PackageName>` variable to -``TRUE``, the ``<PackageName>`` package will not be searched, and will always -be ``NOTFOUND``. - -.. _`Config File Packages`: - -Config-file Packages --------------------- - -A config-file package is a set of files provided by upstreams for downstreams -to use. CMake searches in a number of locations for package configuration files, as -described in the :command:`find_package` documentation. The most simple way for -a CMake user to tell :manual:`cmake(1)` to search in a non-standard prefix for -a package is to set the ``CMAKE_PREFIX_PATH`` cache variable. - -Config-file packages are provided by upstream vendors as part of development -packages, that is, they belong with the header files and any other files -provided to assist downstreams in using the package. - -A set of variables which provide package status information are also set -automatically when using a config-file package. The ``<PackageName>_FOUND`` -variable is set to true or false, depending on whether the package was -found. The ``<PackageName>_DIR`` cache variable is set to the location of the -package configuration file. - -Find-module Packages --------------------- - -A find module is a file with a set of rules for finding the required pieces of -a dependency, primarily header files and libraries. Typically, a find module -is needed when the upstream is not built with CMake, or is not CMake-aware -enough to otherwise provide a package configuration file. Unlike a package configuration -file, it is not shipped with upstream, but is used by downstream to find the -files by guessing locations of files with platform-specific hints. - -Unlike the case of an upstream-provided package configuration file, no single point -of reference identifies the package as being found, so the ``<PackageName>_FOUND`` -variable is not automatically set by the :command:`find_package` command. It -can still be expected to be set by convention however and should be set by -the author of the Find-module. Similarly there is no ``<PackageName>_DIR`` variable, -but each of the artifacts such as library locations and header file locations -provide a separate cache variable. - -See the :manual:`cmake-developer(7)` manual for more information about creating -Find-module files. - -Package Layout -============== - -A config-file package consists of a `Package Configuration File`_ and -optionally a `Package Version File`_ provided with the project distribution. - -Package Configuration File --------------------------- - -Consider a project ``Foo`` that installs the following files:: - - <prefix>/include/foo-1.2/foo.h - <prefix>/lib/foo-1.2/libfoo.a - -It may also provide a CMake package configuration file:: - - <prefix>/lib/cmake/foo-1.2/FooConfig.cmake - -with content defining :prop_tgt:`IMPORTED` targets, or defining variables, such -as: - -.. code-block:: cmake - - # ... - # (compute PREFIX relative to file location) - # ... - set(Foo_INCLUDE_DIRS ${PREFIX}/include/foo-1.2) - set(Foo_LIBRARIES ${PREFIX}/lib/foo-1.2/libfoo.a) - -If another project wishes to use ``Foo`` it need only to locate the ``FooConfig.cmake`` -file and load it to get all the information it needs about package content -locations. Since the package configuration file is provided by the package -installation it already knows all the file locations. - -The :command:`find_package` command may be used to search for the package -configuration file. This command constructs a set of installation prefixes -and searches under each prefix in several locations. Given the name ``Foo``, -it looks for a file called ``FooConfig.cmake`` or ``foo-config.cmake``. -The full set of locations is specified in the :command:`find_package` command -documentation. One place it looks is:: - - <prefix>/lib/cmake/Foo*/ - -where ``Foo*`` is a case-insensitive globbing expression. In our example the -globbing expression will match ``<prefix>/lib/cmake/foo-1.2`` and the package -configuration file will be found. - -Once found, a package configuration file is immediately loaded. It, together -with a package version file, contains all the information the project needs to -use the package. - -Package Version File --------------------- - -When the :command:`find_package` command finds a candidate package configuration -file it looks next to it for a version file. The version file is loaded to test -whether the package version is an acceptable match for the version requested. -If the version file claims compatibility the configuration file is accepted. -Otherwise it is ignored. - -The name of the package version file must match that of the package configuration -file but has either ``-version`` or ``Version`` appended to the name before -the ``.cmake`` extension. For example, the files:: - - <prefix>/lib/cmake/foo-1.3/foo-config.cmake - <prefix>/lib/cmake/foo-1.3/foo-config-version.cmake - -and:: - - <prefix>/lib/cmake/bar-4.2/BarConfig.cmake - <prefix>/lib/cmake/bar-4.2/BarConfigVersion.cmake - -are each pairs of package configuration files and corresponding package version -files. - -When the :command:`find_package` command loads a version file it first sets the -following variables: - -``PACKAGE_FIND_NAME`` - The ``<PackageName>`` - -``PACKAGE_FIND_VERSION`` - Full requested version string - -``PACKAGE_FIND_VERSION_MAJOR`` - Major version if requested, else 0 - -``PACKAGE_FIND_VERSION_MINOR`` - Minor version if requested, else 0 - -``PACKAGE_FIND_VERSION_PATCH`` - Patch version if requested, else 0 - -``PACKAGE_FIND_VERSION_TWEAK`` - Tweak version if requested, else 0 - -``PACKAGE_FIND_VERSION_COUNT`` - Number of version components, 0 to 4 - -The version file must use these variables to check whether it is compatible or -an exact match for the requested version and set the following variables with -results: - -``PACKAGE_VERSION`` - Full provided version string - -``PACKAGE_VERSION_EXACT`` - True if version is exact match - -``PACKAGE_VERSION_COMPATIBLE`` - True if version is compatible - -``PACKAGE_VERSION_UNSUITABLE`` - True if unsuitable as any version - -Version files are loaded in a nested scope so they are free to set any variables -they wish as part of their computation. The find_package command wipes out the -scope when the version file has completed and it has checked the output -variables. When the version file claims to be an acceptable match for the -requested version the find_package command sets the following variables for -use by the project: - -``<PackageName>_VERSION`` - Full provided version string - -``<PackageName>_VERSION_MAJOR`` - Major version if provided, else 0 - -``<PackageName>_VERSION_MINOR`` - Minor version if provided, else 0 - -``<PackageName>_VERSION_PATCH`` - Patch version if provided, else 0 - -``<PackageName>_VERSION_TWEAK`` - Tweak version if provided, else 0 - -``<PackageName>_VERSION_COUNT`` - Number of version components, 0 to 4 - -The variables report the version of the package that was actually found. -The ``<PackageName>`` part of their name matches the argument given to the -:command:`find_package` command. - -.. _`Creating Packages`: - -Creating Packages -================= - -Usually, the upstream depends on CMake itself and can use some CMake facilities -for creating the package files. Consider an upstream which provides a single -shared library: - -.. code-block:: cmake - - project(UpstreamLib) - - set(CMAKE_INCLUDE_CURRENT_DIR ON) - set(CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE ON) - - set(Upstream_VERSION 3.4.1) - - include(GenerateExportHeader) - - add_library(ClimbingStats SHARED climbingstats.cpp) - generate_export_header(ClimbingStats) - set_property(TARGET ClimbingStats PROPERTY VERSION ${Upstream_VERSION}) - set_property(TARGET ClimbingStats PROPERTY SOVERSION 3) - set_property(TARGET ClimbingStats PROPERTY - INTERFACE_ClimbingStats_MAJOR_VERSION 3) - set_property(TARGET ClimbingStats APPEND PROPERTY - COMPATIBLE_INTERFACE_STRING ClimbingStats_MAJOR_VERSION - ) - - install(TARGETS ClimbingStats EXPORT ClimbingStatsTargets - LIBRARY DESTINATION lib - ARCHIVE DESTINATION lib - RUNTIME DESTINATION bin - INCLUDES DESTINATION include - ) - install( - FILES - climbingstats.h - "${CMAKE_CURRENT_BINARY_DIR}/climbingstats_export.h" - DESTINATION - include - COMPONENT - Devel - ) - - include(CMakePackageConfigHelpers) - write_basic_package_version_file( - "${CMAKE_CURRENT_BINARY_DIR}/ClimbingStats/ClimbingStatsConfigVersion.cmake" - VERSION ${Upstream_VERSION} - COMPATIBILITY AnyNewerVersion - ) - - export(EXPORT ClimbingStatsTargets - FILE "${CMAKE_CURRENT_BINARY_DIR}/ClimbingStats/ClimbingStatsTargets.cmake" - NAMESPACE Upstream:: - ) - configure_file(cmake/ClimbingStatsConfig.cmake - "${CMAKE_CURRENT_BINARY_DIR}/ClimbingStats/ClimbingStatsConfig.cmake" - COPYONLY - ) - - set(ConfigPackageLocation lib/cmake/ClimbingStats) - install(EXPORT ClimbingStatsTargets - FILE - ClimbingStatsTargets.cmake - NAMESPACE - Upstream:: - DESTINATION - ${ConfigPackageLocation} - ) - install( - FILES - cmake/ClimbingStatsConfig.cmake - "${CMAKE_CURRENT_BINARY_DIR}/ClimbingStats/ClimbingStatsConfigVersion.cmake" - DESTINATION - ${ConfigPackageLocation} - COMPONENT - Devel - ) - -The :module:`CMakePackageConfigHelpers` module provides a macro for creating -a simple ``ConfigVersion.cmake`` file. This file sets the version of the -package. It is read by CMake when :command:`find_package` is called to -determine the compatibility with the requested version, and to set some -version-specific variables ``<PackageName>_VERSION``, ``<PackageName>_VERSION_MAJOR``, -``<PackageName>_VERSION_MINOR`` etc. The :command:`install(EXPORT)` command is -used to export the targets in the ``ClimbingStatsTargets`` export-set, defined -previously by the :command:`install(TARGETS)` command. This command generates -the ``ClimbingStatsTargets.cmake`` file to contain :prop_tgt:`IMPORTED` -targets, suitable for use by downstreams and arranges to install it to -``lib/cmake/ClimbingStats``. The generated ``ClimbingStatsConfigVersion.cmake`` -and a ``cmake/ClimbingStatsConfig.cmake`` are installed to the same location, -completing the package. - -The generated :prop_tgt:`IMPORTED` targets have appropriate properties set -to define their :ref:`usage requirements <Target Usage Requirements>`, such as -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`, -:prop_tgt:`INTERFACE_COMPILE_DEFINITIONS` and other relevant built-in -``INTERFACE_`` properties. The ``INTERFACE`` variant of user-defined -properties listed in :prop_tgt:`COMPATIBLE_INTERFACE_STRING` and -other :ref:`Compatible Interface Properties` are also propagated to the -generated :prop_tgt:`IMPORTED` targets. In the above case, -``ClimbingStats_MAJOR_VERSION`` is defined as a string which must be -compatible among the dependencies of any depender. By setting this custom -defined user property in this version and in the next version of -``ClimbingStats``, :manual:`cmake(1)` will issue a diagnostic if there is an -attempt to use version 3 together with version 4. Packages can choose to -employ such a pattern if different major versions of the package are designed -to be incompatible. - -A ``NAMESPACE`` with double-colons is specified when exporting the targets -for installation. This convention of double-colons gives CMake a hint that -the name is an :prop_tgt:`IMPORTED` target when it is used by downstreams -with the :command:`target_link_libraries` command. This way, CMake can -issue a diagnostic if the package providing it has not yet been found. - -In this case, when using :command:`install(TARGETS)` the ``INCLUDES DESTINATION`` -was specified. This causes the ``IMPORTED`` targets to have their -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` populated with the ``include`` -directory in the :variable:`CMAKE_INSTALL_PREFIX`. When the ``IMPORTED`` -target is used by downstream, it automatically consumes the entries from -that property. - -Creating a Package Configuration File -------------------------------------- - -In this case, the ``ClimbingStatsConfig.cmake`` file could be as simple as: - -.. code-block:: cmake - - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStatsTargets.cmake") - -As this allows downstreams to use the ``IMPORTED`` targets. If any macros -should be provided by the ``ClimbingStats`` package, they should -be in a separate file which is installed to the same location as the -``ClimbingStatsConfig.cmake`` file, and included from there. - -This can also be extended to cover dependencies: - -.. code-block:: cmake - - # ... - add_library(ClimbingStats SHARED climbingstats.cpp) - generate_export_header(ClimbingStats) - - find_package(Stats 2.6.4 REQUIRED) - target_link_libraries(ClimbingStats PUBLIC Stats::Types) - -As the ``Stats::Types`` target is a ``PUBLIC`` dependency of ``ClimbingStats``, -downstreams must also find the ``Stats`` package and link to the ``Stats::Types`` -library. The ``Stats`` package should be found in the ``ClimbingStatsConfig.cmake`` -file to ensure this. The ``find_dependency`` macro from the -:module:`CMakeFindDependencyMacro` helps with this by propagating -whether the package is ``REQUIRED``, or ``QUIET`` etc. All ``REQUIRED`` -dependencies of a package should be found in the ``Config.cmake`` file: - -.. code-block:: cmake - - include(CMakeFindDependencyMacro) - find_dependency(Stats 2.6.4) - - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStatsTargets.cmake") - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStatsMacros.cmake") - -The ``find_dependency`` macro also sets ``ClimbingStats_FOUND`` to ``False`` if -the dependency is not found, along with a diagnostic that the ``ClimbingStats`` -package can not be used without the ``Stats`` package. - -If ``COMPONENTS`` are specified when the downstream uses :command:`find_package`, -they are listed in the ``<PackageName>_FIND_COMPONENTS`` variable. If a particular -component is non-optional, then the ``<PackageName>_FIND_REQUIRED_<comp>`` will -be true. This can be tested with logic in the package configuration file: - -.. code-block:: cmake - - include(CMakeFindDependencyMacro) - find_dependency(Stats 2.6.4) - - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStatsTargets.cmake") - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStatsMacros.cmake") - - set(_supported_components Plot Table) - - foreach(_comp ${ClimbingStats_FIND_COMPONENTS}) - if (NOT ";${_supported_components};" MATCHES _comp) - set(ClimbingStats_FOUND False) - set(ClimbingStats_NOT_FOUND_MESSAGE "Unsupported component: ${_comp}") - endif() - include("${CMAKE_CURRENT_LIST_DIR}/ClimbingStats${_comp}Targets.cmake") - endforeach() - -Here, the ``ClimbingStats_NOT_FOUND_MESSAGE`` is set to a diagnosis that the package -could not be found because an invalid component was specified. This message -variable can be set for any case where the ``_FOUND`` variable is set to ``False``, -and will be displayed to the user. - -Creating a Package Configuration File for the Build Tree -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The :command:`export(EXPORT)` command creates an :prop_tgt:`IMPORTED` targets -definition file which is specific to the build-tree, and is not relocatable. -This can similarly be used with a suitable package configuration file and -package version file to define a package for the build tree which may be used -without installation. Consumers of the build tree can simply ensure that the -:variable:`CMAKE_PREFIX_PATH` contains the build directory, or set the -``ClimbingStats_DIR`` to ``<build_dir>/ClimbingStats`` in the cache. - -.. _`Creating Relocatable Packages`: - -Creating Relocatable Packages ------------------------------ - -A relocatable package must not reference absolute paths of files on -the machine where the package is built that will not exist on the -machines where the package may be installed. - -Packages created by :command:`install(EXPORT)` are designed to be relocatable, -using paths relative to the location of the package itself. When defining -the interface of a target for ``EXPORT``, keep in mind that the include -directories should be specified as relative paths which are relative to the -:variable:`CMAKE_INSTALL_PREFIX`: - -.. code-block:: cmake - - target_include_directories(tgt INTERFACE - # Wrong, not relocatable: - $<INSTALL_INTERFACE:${CMAKE_INSTALL_PREFIX}/include/TgtName> - ) - - target_include_directories(tgt INTERFACE - # Ok, relocatable: - $<INSTALL_INTERFACE:include/TgtName> - ) - -The ``$<INSTALL_PREFIX>`` -:manual:`generator expression <cmake-generator-expressions(7)>` may be used as -a placeholder for the install prefix without resulting in a non-relocatable -package. This is necessary if complex generator expressions are used: - -.. code-block:: cmake - - target_include_directories(tgt INTERFACE - # Ok, relocatable: - $<INSTALL_INTERFACE:$<$<CONFIG:Debug>:$<INSTALL_PREFIX>/include/TgtName>> - ) - -This also applies to paths referencing external dependencies. -It is not advisable to populate any properties which may contain -paths, such as :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` and -:prop_tgt:`INTERFACE_LINK_LIBRARIES`, with paths relevant to dependencies. -For example, this code may not work well for a relocatable package: - -.. code-block:: cmake - - target_link_libraries(ClimbingStats INTERFACE - ${Foo_LIBRARIES} ${Bar_LIBRARIES} - ) - target_include_directories(ClimbingStats INTERFACE - "$<INSTALL_INTERFACE:${Foo_INCLUDE_DIRS};${Bar_INCLUDE_DIRS}>" - ) - -The referenced variables may contain the absolute paths to libraries -and include directories **as found on the machine the package was made on**. -This would create a package with hard-coded paths to dependencies and not -suitable for relocation. - -Ideally such dependencies should be used through their own -:ref:`IMPORTED targets <Imported Targets>` that have their own -:prop_tgt:`IMPORTED_LOCATION` and usage requirement properties -such as :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` populated -appropriately. Those imported targets may then be used with -the :command:`target_link_libraries` command for ``ClimbingStats``: - -.. code-block:: cmake - - target_link_libraries(ClimbingStats INTERFACE Foo::Foo Bar::Bar) - -With this approach the package references its external dependencies -only through the names of :ref:`IMPORTED targets <Imported Targets>`. -When a consumer uses the installed package, the consumer will run the -appropriate :command:`find_package` commands (via the ``find_dependency`` -macro described above) to find the dependencies and populate the -imported targets with appropriate paths on their own machine. - -Unfortunately many :manual:`modules <cmake-modules(7)>` shipped with -CMake do not yet provide :ref:`IMPORTED targets <Imported Targets>` -because their development pre-dated this approach. This may improve -incrementally over time. Workarounds to create relocatable packages -using such modules include: - -* When building the package, specify each ``Foo_LIBRARY`` cache - entry as just a library name, e.g. ``-DFoo_LIBRARY=foo``. This - tells the corresponding find module to populate the ``Foo_LIBRARIES`` - with just ``foo`` to ask the linker to search for the library - instead of hard-coding a path. - -* Or, after installing the package content but before creating the - package installation binary for redistribution, manually replace - the absolute paths with placeholders for substitution by the - installation tool when the package is installed. - -.. _`Package Registry`: - -Package Registry -================ - -CMake provides two central locations to register packages that have -been built or installed anywhere on a system: - -* `User Package Registry`_ -* `System Package Registry`_ - -The registries are especially useful to help projects find packages in -non-standard install locations or directly in their own build trees. -A project may populate either the user or system registry (using its own -means, see below) to refer to its location. -In either case the package should store at the registered location a -`Package Configuration File`_ (``<PackageName>Config.cmake``) and optionally a -`Package Version File`_ (``<PackageName>ConfigVersion.cmake``). - -The :command:`find_package` command searches the two package registries -as two of the search steps specified in its documentation. If it has -sufficient permissions it also removes stale package registry entries -that refer to directories that do not exist or do not contain a matching -package configuration file. - -.. _`User Package Registry`: - -User Package Registry ---------------------- - -The User Package Registry is stored in a per-user location. -The :command:`export(PACKAGE)` command may be used to register a project -build tree in the user package registry. CMake currently provides no -interface to add install trees to the user package registry. Installers -must be manually taught to register their packages if desired. - -On Windows the user package registry is stored in the Windows registry -under a key in ``HKEY_CURRENT_USER``. - -A ``<PackageName>`` may appear under registry key:: - - HKEY_CURRENT_USER\Software\Kitware\CMake\Packages\<PackageName> - -as a ``REG_SZ`` value, with arbitrary name, that specifies the directory -containing the package configuration file. - -On UNIX platforms the user package registry is stored in the user home -directory under ``~/.cmake/packages``. A ``<PackageName>`` may appear under -the directory:: - - ~/.cmake/packages/<PackageName> - -as a file, with arbitrary name, whose content specifies the directory -containing the package configuration file. - -.. _`System Package Registry`: - -System Package Registry ------------------------ - -The System Package Registry is stored in a system-wide location. -CMake currently provides no interface to add to the system package registry. -Installers must be manually taught to register their packages if desired. - -On Windows the system package registry is stored in the Windows registry -under a key in ``HKEY_LOCAL_MACHINE``. A ``<PackageName>`` may appear under -registry key:: - - HKEY_LOCAL_MACHINE\Software\Kitware\CMake\Packages\<PackageName> - -as a ``REG_SZ`` value, with arbitrary name, that specifies the directory -containing the package configuration file. - -There is no system package registry on non-Windows platforms. - -.. _`Disabling the Package Registry`: - -Disabling the Package Registry ------------------------------- - -In some cases using the Package Registries is not desirable. CMake -allows one to disable them using the following variables: - -* The :command:`export(PACKAGE)` command does not populate the user - package registry when :policy:`CMP0090` is set to ``NEW`` unless the - :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` variable explicitly enables it. - When :policy:`CMP0090` is *not* set to ``NEW`` then - :command:`export(PACKAGE)` populates the user package registry unless - the :variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` variable explicitly - disables it. -* :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` disables the - User Package Registry in all the :command:`find_package` calls when - set to ``FALSE``. -* Deprecated :variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` disables the - User Package Registry in all the :command:`find_package` calls when set - to ``TRUE``. This variable is ignored when - :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` has been set. -* :variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` disables - the System Package Registry in all the :command:`find_package` calls. - -Package Registry Example ------------------------- - -A simple convention for naming package registry entries is to use content -hashes. They are deterministic and unlikely to collide -(:command:`export(PACKAGE)` uses this approach). -The name of an entry referencing a specific directory is simply the content -hash of the directory path itself. - -If a project arranges for package registry entries to exist, such as:: - - > reg query HKCU\Software\Kitware\CMake\Packages\MyPackage - HKEY_CURRENT_USER\Software\Kitware\CMake\Packages\MyPackage - 45e7d55f13b87179bb12f907c8de6fc4 REG_SZ c:/Users/Me/Work/lib/cmake/MyPackage - 7b4a9844f681c80ce93190d4e3185db9 REG_SZ c:/Users/Me/Work/MyPackage-build - -or:: - - $ cat ~/.cmake/packages/MyPackage/7d1fb77e07ce59a81bed093bbee945bd - /home/me/work/lib/cmake/MyPackage - $ cat ~/.cmake/packages/MyPackage/f92c1db873a1937f3100706657c63e07 - /home/me/work/MyPackage-build - -then the ``CMakeLists.txt`` code: - -.. code-block:: cmake - - find_package(MyPackage) - -will search the registered locations for package configuration files -(``MyPackageConfig.cmake``). The search order among package registry -entries for a single package is unspecified and the entry names -(hashes in this example) have no meaning. Registered locations may -contain package version files (``MyPackageConfigVersion.cmake``) to -tell :command:`find_package` whether a specific location is suitable -for the version requested. - -Package Registry Ownership --------------------------- - -Package registry entries are individually owned by the project installations -that they reference. A package installer is responsible for adding its own -entry and the corresponding uninstaller is responsible for removing it. - -The :command:`export(PACKAGE)` command populates the user package registry -with the location of a project build tree. Build trees tend to be deleted by -developers and have no "uninstall" event that could trigger removal of their -entries. In order to keep the registries clean the :command:`find_package` -command automatically removes stale entries it encounters if it has sufficient -permissions. CMake provides no interface to remove an entry referencing an -existing build tree once :command:`export(PACKAGE)` has been invoked. -However, if the project removes its package configuration file from the build -tree then the entry referencing the location will be considered stale.
diff --git a/share/cmake-3.18/Help/manual/cmake-policies.7.rst b/share/cmake-3.18/Help/manual/cmake-policies.7.rst deleted file mode 100644 index e98038a..0000000 --- a/share/cmake-3.18/Help/manual/cmake-policies.7.rst +++ /dev/null
@@ -1,295 +0,0 @@ -.. cmake-manual-description: CMake Policies Reference - -cmake-policies(7) -***************** - -.. only:: html - - .. contents:: - -Introduction -============ - -Policies in CMake are used to preserve backward compatible behavior -across multiple releases. When a new policy is introduced, newer CMake -versions will begin to warn about the backward compatible behavior. It -is possible to disable the warning by explicitly requesting the OLD, or -backward compatible behavior using the :command:`cmake_policy` command. -It is also possible to request ``NEW``, or non-backward compatible behavior -for a policy, also avoiding the warning. Each policy can also be set to -either ``NEW`` or ``OLD`` behavior explicitly on the command line with the -:variable:`CMAKE_POLICY_DEFAULT_CMP<NNNN>` variable. - -A policy is a deprecation mechanism and not a reliable feature toggle. -A policy should almost never be set to ``OLD``, except to silence warnings -in an otherwise frozen or stable codebase, or temporarily as part of a -larger migration path. The ``OLD`` behavior of each policy is undesirable -and will be replaced with an error condition in a future release. - -The :command:`cmake_minimum_required` command does more than report an -error if a too-old version of CMake is used to build a project. It -also sets all policies introduced in that CMake version or earlier to -``NEW`` behavior. To manage policies without increasing the minimum required -CMake version, the :command:`if(POLICY)` command may be used: - -.. code-block:: cmake - - if(POLICY CMP0990) - cmake_policy(SET CMP0990 NEW) - endif() - -This has the effect of using the ``NEW`` behavior with newer CMake releases which -users may be using and not issuing a compatibility warning. - -The setting of a policy is confined in some cases to not propagate to the -parent scope. For example, if the files read by the :command:`include` command -or the :command:`find_package` command contain a use of :command:`cmake_policy`, -that policy setting will not affect the caller by default. Both commands accept -an optional ``NO_POLICY_SCOPE`` keyword to control this behavior. - -The :variable:`CMAKE_MINIMUM_REQUIRED_VERSION` variable may also be used -to determine whether to report an error on use of deprecated macros or -functions. - -Policies Introduced by CMake 3.18 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0108: A target cannot link to itself through an alias. </policy/CMP0108> - CMP0107: An ALIAS target cannot overwrite another target. </policy/CMP0107> - CMP0106: The Documentation module is removed. </policy/CMP0106> - CMP0105: Device link step uses the link options. </policy/CMP0105> - CMP0104: CMAKE_CUDA_ARCHITECTURES now detected for NVCC, empty CUDA_ARCHITECTURES not allowed. </policy/CMP0104> - CMP0103: Multiple export() with same FILE without APPEND is not allowed. </policy/CMP0103> - -Policies Introduced by CMake 3.17 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0102: mark_as_advanced() does nothing if a cache entry does not exist. </policy/CMP0102> - CMP0101: target_compile_options honors BEFORE keyword in all scopes. </policy/CMP0101> - CMP0100: Let AUTOMOC and AUTOUIC process .hh header files. </policy/CMP0100> - CMP0099: Link properties are transitive over private dependency on static libraries. </policy/CMP0099> - CMP0098: FindFLEX runs flex in CMAKE_CURRENT_BINARY_DIR when executing. </policy/CMP0098> - -Policies Introduced by CMake 3.16 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0097: ExternalProject_Add with GIT_SUBMODULES "" initializes no submodules. </policy/CMP0097> - CMP0096: project() preserves leading zeros in version components. </policy/CMP0096> - CMP0095: RPATH entries are properly escaped in the intermediary CMake install script. </policy/CMP0095> - -Policies Introduced by CMake 3.15 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0094: FindPython3, FindPython2 and FindPython use LOCATION for lookup strategy. </policy/CMP0094> - CMP0093: FindBoost reports Boost_VERSION in x.y.z format. </policy/CMP0093> - CMP0092: MSVC warning flags are not in CMAKE_{C,CXX}_FLAGS by default. </policy/CMP0092> - CMP0091: MSVC runtime library flags are selected by an abstraction. </policy/CMP0091> - CMP0090: export(PACKAGE) does not populate package registry by default. </policy/CMP0090> - CMP0089: Compiler id for IBM Clang-based XL compilers is now XLClang. </policy/CMP0089> - -Policies Introduced by CMake 3.14 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0088: FindBISON runs bison in CMAKE_CURRENT_BINARY_DIR when executing. </policy/CMP0088> - CMP0087: install(SCRIPT | CODE) supports generator expressions. </policy/CMP0087> - CMP0086: UseSWIG honors SWIG_MODULE_NAME via -module flag. </policy/CMP0086> - CMP0085: IN_LIST generator expression handles empty list items. </policy/CMP0085> - CMP0084: The FindQt module does not exist for find_package(). </policy/CMP0084> - CMP0083: Add PIE options when linking executable. </policy/CMP0083> - CMP0082: Install rules from add_subdirectory() are interleaved with those in caller. </policy/CMP0082> - - -Policies Introduced by CMake 3.13 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0081: Relative paths not allowed in LINK_DIRECTORIES target property. </policy/CMP0081> - CMP0080: BundleUtilities cannot be included at configure time. </policy/CMP0080> - CMP0079: target_link_libraries allows use with targets in other directories. </policy/CMP0079> - CMP0078: UseSWIG generates standard target names. </policy/CMP0078> - CMP0077: option() honors normal variables. </policy/CMP0077> - CMP0076: target_sources() command converts relative paths to absolute. </policy/CMP0076> - -Policies Introduced by CMake 3.12 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0075: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. </policy/CMP0075> - CMP0074: find_package uses PackageName_ROOT variables. </policy/CMP0074> - CMP0073: Do not produce legacy _LIB_DEPENDS cache entries. </policy/CMP0073> - -Policies Introduced by CMake 3.11 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0072: FindOpenGL prefers GLVND by default when available. </policy/CMP0072> - -Policies Introduced by CMake 3.10 -================================= - -.. toctree:: - :maxdepth: 1 - - CMP0071: Let AUTOMOC and AUTOUIC process GENERATED files. </policy/CMP0071> - CMP0070: Define file(GENERATE) behavior for relative paths. </policy/CMP0070> - -Policies Introduced by CMake 3.9 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0069: INTERPROCEDURAL_OPTIMIZATION is enforced when enabled. </policy/CMP0069> - CMP0068: RPATH settings on macOS do not affect install_name. </policy/CMP0068> - -Policies Introduced by CMake 3.8 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0067: Honor language standard in try_compile() source-file signature. </policy/CMP0067> - -Policies Introduced by CMake 3.7 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0066: Honor per-config flags in try_compile() source-file signature. </policy/CMP0066> - -Policies Introduced by CMake 3.4 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0065: Do not add flags to export symbols from executables without the ENABLE_EXPORTS target property. </policy/CMP0065> - CMP0064: Support new TEST if() operator. </policy/CMP0064> - -Policies Introduced by CMake 3.3 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0063: Honor visibility properties for all target types. </policy/CMP0063> - CMP0062: Disallow install() of export() result. </policy/CMP0062> - CMP0061: CTest does not by default tell make to ignore errors (-i). </policy/CMP0061> - CMP0060: Link libraries by full path even in implicit directories. </policy/CMP0060> - CMP0059: Do not treat DEFINITIONS as a built-in directory property. </policy/CMP0059> - CMP0058: Ninja requires custom command byproducts to be explicit. </policy/CMP0058> - CMP0057: Support new IN_LIST if() operator. </policy/CMP0057> - -Policies Introduced by CMake 3.2 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0056: Honor link flags in try_compile() source-file signature. </policy/CMP0056> - CMP0055: Strict checking for break() command. </policy/CMP0055> - -Policies Introduced by CMake 3.1 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0054: Only interpret if() arguments as variables or keywords when unquoted. </policy/CMP0054> - CMP0053: Simplify variable reference and escape sequence evaluation. </policy/CMP0053> - CMP0052: Reject source and build dirs in installed INTERFACE_INCLUDE_DIRECTORIES. </policy/CMP0052> - CMP0051: List TARGET_OBJECTS in SOURCES target property. </policy/CMP0051> - -Policies Introduced by CMake 3.0 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0050: Disallow add_custom_command SOURCE signatures. </policy/CMP0050> - CMP0049: Do not expand variables in target source entries. </policy/CMP0049> - CMP0048: project() command manages VERSION variables. </policy/CMP0048> - CMP0047: Use QCC compiler id for the qcc drivers on QNX. </policy/CMP0047> - CMP0046: Error on non-existent dependency in add_dependencies. </policy/CMP0046> - CMP0045: Error on non-existent target in get_target_property. </policy/CMP0045> - CMP0044: Case sensitive Lang_COMPILER_ID generator expressions. </policy/CMP0044> - CMP0043: Ignore COMPILE_DEFINITIONS_Config properties. </policy/CMP0043> - CMP0042: MACOSX_RPATH is enabled by default. </policy/CMP0042> - CMP0041: Error on relative include with generator expression. </policy/CMP0041> - CMP0040: The target in the TARGET signature of add_custom_command() must exist. </policy/CMP0040> - CMP0039: Utility targets may not have link dependencies. </policy/CMP0039> - CMP0038: Targets may not link directly to themselves. </policy/CMP0038> - CMP0037: Target names should not be reserved and should match a validity pattern. </policy/CMP0037> - CMP0036: The build_name command should not be called. </policy/CMP0036> - CMP0035: The variable_requires command should not be called. </policy/CMP0035> - CMP0034: The utility_source command should not be called. </policy/CMP0034> - CMP0033: The export_library_dependencies command should not be called. </policy/CMP0033> - CMP0032: The output_required_files command should not be called. </policy/CMP0032> - CMP0031: The load_command command should not be called. </policy/CMP0031> - CMP0030: The use_mangled_mesa command should not be called. </policy/CMP0030> - CMP0029: The subdir_depends command should not be called. </policy/CMP0029> - CMP0028: Double colon in target name means ALIAS or IMPORTED target. </policy/CMP0028> - CMP0027: Conditionally linked imported targets with missing include directories. </policy/CMP0027> - CMP0026: Disallow use of the LOCATION target property. </policy/CMP0026> - CMP0025: Compiler id for Apple Clang is now AppleClang. </policy/CMP0025> - CMP0024: Disallow include export result. </policy/CMP0024> - -Policies Introduced by CMake 2.8 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0023: Plain and keyword target_link_libraries signatures cannot be mixed. </policy/CMP0023> - CMP0022: INTERFACE_LINK_LIBRARIES defines the link interface. </policy/CMP0022> - CMP0021: Fatal error on relative paths in INCLUDE_DIRECTORIES target property. </policy/CMP0021> - CMP0020: Automatically link Qt executables to qtmain target on Windows. </policy/CMP0020> - CMP0019: Do not re-expand variables in include and link information. </policy/CMP0019> - CMP0018: Ignore CMAKE_SHARED_LIBRARY_Lang_FLAGS variable. </policy/CMP0018> - CMP0017: Prefer files from the CMake module directory when including from there. </policy/CMP0017> - CMP0016: target_link_libraries() reports error if its only argument is not a target. </policy/CMP0016> - CMP0015: link_directories() treats paths relative to the source dir. </policy/CMP0015> - CMP0014: Input directories must have CMakeLists.txt. </policy/CMP0014> - CMP0013: Duplicate binary directories are not allowed. </policy/CMP0013> - CMP0012: if() recognizes numbers and boolean constants. </policy/CMP0012> - -Policies Introduced by CMake 2.6 -================================ - -.. toctree:: - :maxdepth: 1 - - CMP0011: Included scripts do automatic cmake_policy PUSH and POP. </policy/CMP0011> - CMP0010: Bad variable reference syntax is an error. </policy/CMP0010> - CMP0009: FILE GLOB_RECURSE calls should not follow symlinks by default. </policy/CMP0009> - CMP0008: Libraries linked by full-path must have a valid library file name. </policy/CMP0008> - CMP0007: list command no longer ignores empty elements. </policy/CMP0007> - CMP0006: Installing MACOSX_BUNDLE targets requires a BUNDLE DESTINATION. </policy/CMP0006> - CMP0005: Preprocessor definition values are now escaped automatically. </policy/CMP0005> - CMP0004: Libraries linked may not have leading or trailing whitespace. </policy/CMP0004> - CMP0003: Libraries linked via full path no longer produce linker search paths. </policy/CMP0003> - CMP0002: Logical target names must be globally unique. </policy/CMP0002> - CMP0001: CMAKE_BACKWARDS_COMPATIBILITY should no longer be used. </policy/CMP0001> - CMP0000: A minimum required CMake version must be specified. </policy/CMP0000>
diff --git a/share/cmake-3.18/Help/manual/cmake-properties.7.rst b/share/cmake-3.18/Help/manual/cmake-properties.7.rst deleted file mode 100644 index 30b2a05..0000000 --- a/share/cmake-3.18/Help/manual/cmake-properties.7.rst +++ /dev/null
@@ -1,574 +0,0 @@ -.. cmake-manual-description: CMake Properties Reference - -cmake-properties(7) -******************* - -.. only:: html - - .. contents:: - -.. _`Global Properties`: - -Properties of Global Scope -========================== - -.. toctree:: - :maxdepth: 1 - - /prop_gbl/ALLOW_DUPLICATE_CUSTOM_TARGETS - /prop_gbl/AUTOGEN_SOURCE_GROUP - /prop_gbl/AUTOGEN_TARGETS_FOLDER - /prop_gbl/AUTOMOC_SOURCE_GROUP - /prop_gbl/AUTOMOC_TARGETS_FOLDER - /prop_gbl/AUTORCC_SOURCE_GROUP - /prop_gbl/CMAKE_C_KNOWN_FEATURES - /prop_gbl/CMAKE_CUDA_KNOWN_FEATURES - /prop_gbl/CMAKE_CXX_KNOWN_FEATURES - /prop_gbl/CMAKE_ROLE - /prop_gbl/DEBUG_CONFIGURATIONS - /prop_gbl/DISABLED_FEATURES - /prop_gbl/ECLIPSE_EXTRA_CPROJECT_CONTENTS - /prop_gbl/ECLIPSE_EXTRA_NATURES - /prop_gbl/ENABLED_FEATURES - /prop_gbl/ENABLED_LANGUAGES - /prop_gbl/FIND_LIBRARY_USE_LIB32_PATHS - /prop_gbl/FIND_LIBRARY_USE_LIB64_PATHS - /prop_gbl/FIND_LIBRARY_USE_LIBX32_PATHS - /prop_gbl/FIND_LIBRARY_USE_OPENBSD_VERSIONING - /prop_gbl/GENERATOR_IS_MULTI_CONFIG - /prop_gbl/GLOBAL_DEPENDS_DEBUG_MODE - /prop_gbl/GLOBAL_DEPENDS_NO_CYCLES - /prop_gbl/IN_TRY_COMPILE - /prop_gbl/JOB_POOLS - /prop_gbl/PACKAGES_FOUND - /prop_gbl/PACKAGES_NOT_FOUND - /prop_gbl/PREDEFINED_TARGETS_FOLDER - /prop_gbl/REPORT_UNDEFINED_PROPERTIES - /prop_gbl/RULE_LAUNCH_COMPILE - /prop_gbl/RULE_LAUNCH_CUSTOM - /prop_gbl/RULE_LAUNCH_LINK - /prop_gbl/RULE_MESSAGES - /prop_gbl/TARGET_ARCHIVES_MAY_BE_SHARED_LIBS - /prop_gbl/TARGET_MESSAGES - /prop_gbl/TARGET_SUPPORTS_SHARED_LIBS - /prop_gbl/USE_FOLDERS - /prop_gbl/XCODE_EMIT_EFFECTIVE_PLATFORM_NAME - -.. _`Directory Properties`: - -Properties on Directories -========================= - -.. toctree:: - :maxdepth: 1 - - /prop_dir/ADDITIONAL_CLEAN_FILES - /prop_dir/BINARY_DIR - /prop_dir/BUILDSYSTEM_TARGETS - /prop_dir/CACHE_VARIABLES - /prop_dir/CLEAN_NO_CUSTOM - /prop_dir/CMAKE_CONFIGURE_DEPENDS - /prop_dir/COMPILE_DEFINITIONS - /prop_dir/COMPILE_OPTIONS - /prop_dir/DEFINITIONS - /prop_dir/EXCLUDE_FROM_ALL - /prop_dir/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM - /prop_dir/INCLUDE_DIRECTORIES - /prop_dir/INCLUDE_REGULAR_EXPRESSION - /prop_dir/INTERPROCEDURAL_OPTIMIZATION_CONFIG - /prop_dir/INTERPROCEDURAL_OPTIMIZATION - /prop_dir/LABELS - /prop_dir/LINK_DIRECTORIES - /prop_dir/LINK_OPTIONS - /prop_dir/LISTFILE_STACK - /prop_dir/MACROS - /prop_dir/PARENT_DIRECTORY - /prop_dir/RULE_LAUNCH_COMPILE - /prop_dir/RULE_LAUNCH_CUSTOM - /prop_dir/RULE_LAUNCH_LINK - /prop_dir/SOURCE_DIR - /prop_dir/SUBDIRECTORIES - /prop_dir/TESTS - /prop_dir/TEST_INCLUDE_FILES - /prop_dir/VARIABLES - /prop_dir/VS_GLOBAL_SECTION_POST_section - /prop_dir/VS_GLOBAL_SECTION_PRE_section - /prop_dir/VS_STARTUP_PROJECT - -.. _`Target Properties`: - -Properties on Targets -===================== - -.. toctree:: - :maxdepth: 1 - - /prop_tgt/ADDITIONAL_CLEAN_FILES - /prop_tgt/AIX_EXPORT_ALL_SYMBOLS - /prop_tgt/ALIAS_GLOBAL - /prop_tgt/ALIASED_TARGET - /prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS - /prop_tgt/ANDROID_API - /prop_tgt/ANDROID_API_MIN - /prop_tgt/ANDROID_ARCH - /prop_tgt/ANDROID_ASSETS_DIRECTORIES - /prop_tgt/ANDROID_GUI - /prop_tgt/ANDROID_JAR_DEPENDENCIES - /prop_tgt/ANDROID_JAR_DIRECTORIES - /prop_tgt/ANDROID_JAVA_SOURCE_DIR - /prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES - /prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES - /prop_tgt/ANDROID_PROCESS_MAX - /prop_tgt/ANDROID_PROGUARD - /prop_tgt/ANDROID_PROGUARD_CONFIG_PATH - /prop_tgt/ANDROID_SECURE_PROPS_PATH - /prop_tgt/ANDROID_SKIP_ANT_STEP - /prop_tgt/ANDROID_STL_TYPE - /prop_tgt/ARCHIVE_OUTPUT_DIRECTORY_CONFIG - /prop_tgt/ARCHIVE_OUTPUT_DIRECTORY - /prop_tgt/ARCHIVE_OUTPUT_NAME_CONFIG - /prop_tgt/ARCHIVE_OUTPUT_NAME - /prop_tgt/AUTOGEN_BUILD_DIR - /prop_tgt/AUTOGEN_ORIGIN_DEPENDS - /prop_tgt/AUTOGEN_PARALLEL - /prop_tgt/AUTOGEN_TARGET_DEPENDS - /prop_tgt/AUTOMOC - /prop_tgt/AUTOMOC_COMPILER_PREDEFINES - /prop_tgt/AUTOMOC_DEPEND_FILTERS - /prop_tgt/AUTOMOC_EXECUTABLE - /prop_tgt/AUTOMOC_MACRO_NAMES - /prop_tgt/AUTOMOC_MOC_OPTIONS - /prop_tgt/AUTOMOC_PATH_PREFIX - /prop_tgt/AUTORCC - /prop_tgt/AUTORCC_EXECUTABLE - /prop_tgt/AUTORCC_OPTIONS - /prop_tgt/AUTOUIC - /prop_tgt/AUTOUIC_EXECUTABLE - /prop_tgt/AUTOUIC_OPTIONS - /prop_tgt/AUTOUIC_SEARCH_PATHS - /prop_tgt/BINARY_DIR - /prop_tgt/BUILD_RPATH - /prop_tgt/BUILD_RPATH_USE_ORIGIN - /prop_tgt/BUILD_WITH_INSTALL_NAME_DIR - /prop_tgt/BUILD_WITH_INSTALL_RPATH - /prop_tgt/BUNDLE_EXTENSION - /prop_tgt/BUNDLE - /prop_tgt/C_EXTENSIONS - /prop_tgt/C_STANDARD - /prop_tgt/C_STANDARD_REQUIRED - /prop_tgt/COMMON_LANGUAGE_RUNTIME - /prop_tgt/COMPATIBLE_INTERFACE_BOOL - /prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX - /prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN - /prop_tgt/COMPATIBLE_INTERFACE_STRING - /prop_tgt/COMPILE_DEFINITIONS - /prop_tgt/COMPILE_FEATURES - /prop_tgt/COMPILE_FLAGS - /prop_tgt/COMPILE_OPTIONS - /prop_tgt/COMPILE_PDB_NAME - /prop_tgt/COMPILE_PDB_NAME_CONFIG - /prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY - /prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG - /prop_tgt/CONFIG_OUTPUT_NAME - /prop_tgt/CONFIG_POSTFIX - /prop_tgt/CROSSCOMPILING_EMULATOR - /prop_tgt/CUDA_ARCHITECTURES - /prop_tgt/CUDA_PTX_COMPILATION - /prop_tgt/CUDA_SEPARABLE_COMPILATION - /prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS - /prop_tgt/CUDA_RUNTIME_LIBRARY - /prop_tgt/CUDA_EXTENSIONS - /prop_tgt/CUDA_STANDARD - /prop_tgt/CUDA_STANDARD_REQUIRED - /prop_tgt/CXX_EXTENSIONS - /prop_tgt/CXX_STANDARD - /prop_tgt/CXX_STANDARD_REQUIRED - /prop_tgt/DEBUG_POSTFIX - /prop_tgt/DEFINE_SYMBOL - /prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY - /prop_tgt/DEPLOYMENT_ADDITIONAL_FILES - /prop_tgt/DEPRECATION - /prop_tgt/DISABLE_PRECOMPILE_HEADERS - /prop_tgt/DOTNET_TARGET_FRAMEWORK - /prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION - /prop_tgt/EchoString - /prop_tgt/ENABLE_EXPORTS - /prop_tgt/EXCLUDE_FROM_ALL - /prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD_CONFIG - /prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD - /prop_tgt/EXPORT_NAME - /prop_tgt/EXPORT_PROPERTIES - /prop_tgt/FOLDER - /prop_tgt/Fortran_FORMAT - /prop_tgt/Fortran_MODULE_DIRECTORY - /prop_tgt/Fortran_PREPROCESS - /prop_tgt/FRAMEWORK - /prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG - /prop_tgt/FRAMEWORK_VERSION - /prop_tgt/GENERATOR_FILE_NAME - /prop_tgt/GHS_INTEGRITY_APP - /prop_tgt/GHS_NO_SOURCE_GROUP_FILE - /prop_tgt/GNUtoMS - /prop_tgt/HAS_CXX - /prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM - /prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME - /prop_tgt/IMPORTED_CONFIGURATIONS - /prop_tgt/IMPORTED_GLOBAL - /prop_tgt/IMPORTED_IMPLIB_CONFIG - /prop_tgt/IMPORTED_IMPLIB - /prop_tgt/IMPORTED_LIBNAME_CONFIG - /prop_tgt/IMPORTED_LIBNAME - /prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG - /prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES - /prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES_CONFIG - /prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES - /prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG - /prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES - /prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY_CONFIG - /prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY - /prop_tgt/IMPORTED_LOCATION_CONFIG - /prop_tgt/IMPORTED_LOCATION - /prop_tgt/IMPORTED_NO_SONAME_CONFIG - /prop_tgt/IMPORTED_NO_SONAME - /prop_tgt/IMPORTED_OBJECTS_CONFIG - /prop_tgt/IMPORTED_OBJECTS - /prop_tgt/IMPORTED - /prop_tgt/IMPORTED_SONAME_CONFIG - /prop_tgt/IMPORTED_SONAME - /prop_tgt/IMPORT_PREFIX - /prop_tgt/IMPORT_SUFFIX - /prop_tgt/INCLUDE_DIRECTORIES - /prop_tgt/INSTALL_NAME_DIR - /prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH - /prop_tgt/INSTALL_RPATH - /prop_tgt/INSTALL_RPATH_USE_LINK_PATH - /prop_tgt/INTERFACE_AUTOUIC_OPTIONS - /prop_tgt/INTERFACE_COMPILE_DEFINITIONS - /prop_tgt/INTERFACE_COMPILE_FEATURES - /prop_tgt/INTERFACE_COMPILE_OPTIONS - /prop_tgt/INTERFACE_INCLUDE_DIRECTORIES - /prop_tgt/INTERFACE_LINK_DEPENDS - /prop_tgt/INTERFACE_LINK_DIRECTORIES - /prop_tgt/INTERFACE_LINK_LIBRARIES - /prop_tgt/INTERFACE_LINK_OPTIONS - /prop_tgt/INTERFACE_PRECOMPILE_HEADERS - /prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE - /prop_tgt/INTERFACE_SOURCES - /prop_tgt/INTERFACE_SYSTEM_INCLUDE_DIRECTORIES - /prop_tgt/INTERPROCEDURAL_OPTIMIZATION_CONFIG - /prop_tgt/INTERPROCEDURAL_OPTIMIZATION - /prop_tgt/IOS_INSTALL_COMBINED - /prop_tgt/JOB_POOL_COMPILE - /prop_tgt/JOB_POOL_LINK - /prop_tgt/JOB_POOL_PRECOMPILE_HEADER - /prop_tgt/LABELS - /prop_tgt/LANG_CLANG_TIDY - /prop_tgt/LANG_COMPILER_LAUNCHER - /prop_tgt/LANG_CPPCHECK - /prop_tgt/LANG_CPPLINT - /prop_tgt/LANG_INCLUDE_WHAT_YOU_USE - /prop_tgt/LANG_VISIBILITY_PRESET - /prop_tgt/LIBRARY_OUTPUT_DIRECTORY_CONFIG - /prop_tgt/LIBRARY_OUTPUT_DIRECTORY - /prop_tgt/LIBRARY_OUTPUT_NAME_CONFIG - /prop_tgt/LIBRARY_OUTPUT_NAME - /prop_tgt/LINK_DEPENDS_NO_SHARED - /prop_tgt/LINK_DEPENDS - /prop_tgt/LINKER_LANGUAGE - /prop_tgt/LINK_DIRECTORIES - /prop_tgt/LINK_FLAGS_CONFIG - /prop_tgt/LINK_FLAGS - /prop_tgt/LINK_INTERFACE_LIBRARIES_CONFIG - /prop_tgt/LINK_INTERFACE_LIBRARIES - /prop_tgt/LINK_INTERFACE_MULTIPLICITY_CONFIG - /prop_tgt/LINK_INTERFACE_MULTIPLICITY - /prop_tgt/LINK_LIBRARIES - /prop_tgt/LINK_OPTIONS - /prop_tgt/LINK_SEARCH_END_STATIC - /prop_tgt/LINK_SEARCH_START_STATIC - /prop_tgt/LINK_WHAT_YOU_USE - /prop_tgt/LOCATION_CONFIG - /prop_tgt/LOCATION - /prop_tgt/MACHO_COMPATIBILITY_VERSION - /prop_tgt/MACHO_CURRENT_VERSION - /prop_tgt/MACOSX_BUNDLE_INFO_PLIST - /prop_tgt/MACOSX_BUNDLE - /prop_tgt/MACOSX_FRAMEWORK_INFO_PLIST - /prop_tgt/MACOSX_RPATH - /prop_tgt/MANUALLY_ADDED_DEPENDENCIES - /prop_tgt/MAP_IMPORTED_CONFIG_CONFIG - /prop_tgt/MSVC_RUNTIME_LIBRARY - /prop_tgt/NAME - /prop_tgt/NO_SONAME - /prop_tgt/NO_SYSTEM_FROM_IMPORTED - /prop_tgt/OBJC_EXTENSIONS - /prop_tgt/OBJC_STANDARD - /prop_tgt/OBJC_STANDARD_REQUIRED - /prop_tgt/OBJCXX_EXTENSIONS - /prop_tgt/OBJCXX_STANDARD - /prop_tgt/OBJCXX_STANDARD_REQUIRED - /prop_tgt/OSX_ARCHITECTURES_CONFIG - /prop_tgt/OSX_ARCHITECTURES - /prop_tgt/OUTPUT_NAME_CONFIG - /prop_tgt/OUTPUT_NAME - /prop_tgt/PCH_WARN_INVALID - /prop_tgt/PDB_NAME_CONFIG - /prop_tgt/PDB_NAME - /prop_tgt/PDB_OUTPUT_DIRECTORY_CONFIG - /prop_tgt/PDB_OUTPUT_DIRECTORY - /prop_tgt/POSITION_INDEPENDENT_CODE - /prop_tgt/PRECOMPILE_HEADERS - /prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM - /prop_tgt/PREFIX - /prop_tgt/PRIVATE_HEADER - /prop_tgt/PROJECT_LABEL - /prop_tgt/PUBLIC_HEADER - /prop_tgt/RESOURCE - /prop_tgt/RULE_LAUNCH_COMPILE - /prop_tgt/RULE_LAUNCH_CUSTOM - /prop_tgt/RULE_LAUNCH_LINK - /prop_tgt/RUNTIME_OUTPUT_DIRECTORY_CONFIG - /prop_tgt/RUNTIME_OUTPUT_DIRECTORY - /prop_tgt/RUNTIME_OUTPUT_NAME_CONFIG - /prop_tgt/RUNTIME_OUTPUT_NAME - /prop_tgt/SKIP_BUILD_RPATH - /prop_tgt/SOURCE_DIR - /prop_tgt/SOURCES - /prop_tgt/SOVERSION - /prop_tgt/STATIC_LIBRARY_FLAGS_CONFIG - /prop_tgt/STATIC_LIBRARY_FLAGS - /prop_tgt/STATIC_LIBRARY_OPTIONS - /prop_tgt/SUFFIX - /prop_tgt/Swift_DEPENDENCIES_FILE - /prop_tgt/Swift_LANGUAGE_VERSION - /prop_tgt/Swift_MODULE_DIRECTORY - /prop_tgt/Swift_MODULE_NAME - /prop_tgt/TYPE - /prop_tgt/UNITY_BUILD - /prop_tgt/UNITY_BUILD_BATCH_SIZE - /prop_tgt/UNITY_BUILD_CODE_AFTER_INCLUDE - /prop_tgt/UNITY_BUILD_CODE_BEFORE_INCLUDE - /prop_tgt/UNITY_BUILD_MODE - /prop_tgt/VERSION - /prop_tgt/VISIBILITY_INLINES_HIDDEN - /prop_tgt/VS_CONFIGURATION_TYPE - /prop_tgt/VS_DEBUGGER_COMMAND - /prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS - /prop_tgt/VS_DEBUGGER_ENVIRONMENT - /prop_tgt/VS_DEBUGGER_WORKING_DIRECTORY - /prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION - /prop_tgt/VS_DOTNET_REFERENCE_refname - /prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname - /prop_tgt/VS_DOTNET_REFERENCES - /prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL - /prop_tgt/VS_DOTNET_TARGET_FRAMEWORK_VERSION - /prop_tgt/VS_DOTNET_DOCUMENTATION_FILE - /prop_tgt/VS_DPI_AWARE - /prop_tgt/VS_GLOBAL_KEYWORD - /prop_tgt/VS_GLOBAL_PROJECT_TYPES - /prop_tgt/VS_GLOBAL_ROOTNAMESPACE - /prop_tgt/VS_GLOBAL_variable - /prop_tgt/VS_IOT_EXTENSIONS_VERSION - /prop_tgt/VS_IOT_STARTUP_TASK - /prop_tgt/VS_JUST_MY_CODE_DEBUGGING - /prop_tgt/VS_KEYWORD - /prop_tgt/VS_MOBILE_EXTENSIONS_VERSION - /prop_tgt/VS_NO_SOLUTION_DEPLOY - /prop_tgt/VS_PACKAGE_REFERENCES - /prop_tgt/VS_PLATFORM_TOOLSET - /prop_tgt/VS_PROJECT_IMPORT - /prop_tgt/VS_SCC_AUXPATH - /prop_tgt/VS_SCC_LOCALPATH - /prop_tgt/VS_SCC_PROJECTNAME - /prop_tgt/VS_SCC_PROVIDER - /prop_tgt/VS_SDK_REFERENCES - /prop_tgt/VS_SOLUTION_DEPLOY - /prop_tgt/VS_SOURCE_SETTINGS_tool - /prop_tgt/VS_USER_PROPS - /prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION - /prop_tgt/VS_WINRT_COMPONENT - /prop_tgt/VS_WINRT_EXTENSIONS - /prop_tgt/VS_WINRT_REFERENCES - /prop_tgt/WIN32_EXECUTABLE - /prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS - /prop_tgt/XCODE_ATTRIBUTE_an-attribute - /prop_tgt/XCODE_EXPLICIT_FILE_TYPE - /prop_tgt/XCODE_GENERATE_SCHEME - /prop_tgt/XCODE_PRODUCT_TYPE - /prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER - /prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN - /prop_tgt/XCODE_SCHEME_ARGUMENTS - /prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT - /prop_tgt/XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING - /prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER - /prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS - /prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE - /prop_tgt/XCODE_SCHEME_ENVIRONMENT - /prop_tgt/XCODE_SCHEME_EXECUTABLE - /prop_tgt/XCODE_SCHEME_GUARD_MALLOC - /prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP - /prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES - /prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE - /prop_tgt/XCODE_SCHEME_MALLOC_STACK - /prop_tgt/XCODE_SCHEME_THREAD_SANITIZER - /prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP - /prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER - /prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP - /prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY - /prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS - /prop_tgt/XCTEST - -.. _`Test Properties`: - -Properties on Tests -=================== - -.. toctree:: - :maxdepth: 1 - - /prop_test/ATTACHED_FILES_ON_FAIL - /prop_test/ATTACHED_FILES - /prop_test/COST - /prop_test/DEPENDS - /prop_test/DISABLED - /prop_test/ENVIRONMENT - /prop_test/FAIL_REGULAR_EXPRESSION - /prop_test/FIXTURES_CLEANUP - /prop_test/FIXTURES_REQUIRED - /prop_test/FIXTURES_SETUP - /prop_test/LABELS - /prop_test/MEASUREMENT - /prop_test/PASS_REGULAR_EXPRESSION - /prop_test/PROCESSOR_AFFINITY - /prop_test/PROCESSORS - /prop_test/REQUIRED_FILES - /prop_test/RESOURCE_GROUPS - /prop_test/RESOURCE_LOCK - /prop_test/RUN_SERIAL - /prop_test/SKIP_REGULAR_EXPRESSION - /prop_test/SKIP_RETURN_CODE - /prop_test/TIMEOUT - /prop_test/TIMEOUT_AFTER_MATCH - /prop_test/WILL_FAIL - /prop_test/WORKING_DIRECTORY - -.. _`Source File Properties`: - -Properties on Source Files -========================== - -.. toctree:: - :maxdepth: 1 - - /prop_sf/ABSTRACT - /prop_sf/AUTORCC_OPTIONS - /prop_sf/AUTOUIC_OPTIONS - /prop_sf/COMPILE_DEFINITIONS - /prop_sf/COMPILE_FLAGS - /prop_sf/COMPILE_OPTIONS - /prop_sf/EXTERNAL_OBJECT - /prop_sf/Fortran_FORMAT - /prop_sf/Fortran_PREPROCESS - /prop_sf/GENERATED - /prop_sf/HEADER_FILE_ONLY - /prop_sf/INCLUDE_DIRECTORIES - /prop_sf/KEEP_EXTENSION - /prop_sf/LABELS - /prop_sf/LANGUAGE - /prop_sf/LOCATION - /prop_sf/MACOSX_PACKAGE_LOCATION - /prop_sf/OBJECT_DEPENDS - /prop_sf/OBJECT_OUTPUTS - /prop_sf/SKIP_AUTOGEN - /prop_sf/SKIP_AUTOMOC - /prop_sf/SKIP_AUTORCC - /prop_sf/SKIP_AUTOUIC - /prop_sf/SKIP_PRECOMPILE_HEADERS - /prop_sf/SKIP_UNITY_BUILD_INCLUSION - /prop_sf/Swift_DEPENDENCIES_FILE - /prop_sf/Swift_DIAGNOSTICS_FILE - /prop_sf/SYMBOLIC - /prop_sf/UNITY_GROUP - /prop_sf/VS_COPY_TO_OUT_DIR - /prop_sf/VS_CSHARP_tagname - /prop_sf/VS_DEPLOYMENT_CONTENT - /prop_sf/VS_DEPLOYMENT_LOCATION - /prop_sf/VS_INCLUDE_IN_VSIX - /prop_sf/VS_RESOURCE_GENERATOR - /prop_sf/VS_SETTINGS - /prop_sf/VS_SHADER_DISABLE_OPTIMIZATIONS - /prop_sf/VS_SHADER_ENABLE_DEBUG - /prop_sf/VS_SHADER_ENTRYPOINT - /prop_sf/VS_SHADER_FLAGS - /prop_sf/VS_SHADER_MODEL - /prop_sf/VS_SHADER_OBJECT_FILE_NAME - /prop_sf/VS_SHADER_OUTPUT_HEADER_FILE - /prop_sf/VS_SHADER_TYPE - /prop_sf/VS_SHADER_VARIABLE_NAME - /prop_sf/VS_TOOL_OVERRIDE.rst - /prop_sf/VS_XAML_TYPE - /prop_sf/WRAP_EXCLUDE - /prop_sf/XCODE_EXPLICIT_FILE_TYPE - /prop_sf/XCODE_FILE_ATTRIBUTES - /prop_sf/XCODE_LAST_KNOWN_FILE_TYPE - -.. _`Cache Entry Properties`: - -Properties on Cache Entries -=========================== - -.. toctree:: - :maxdepth: 1 - - /prop_cache/ADVANCED - /prop_cache/HELPSTRING - /prop_cache/MODIFIED - /prop_cache/STRINGS - /prop_cache/TYPE - /prop_cache/VALUE - -.. _`Installed File Properties`: - -Properties on Installed Files -============================= - -.. toctree:: - :maxdepth: 1 - - /prop_inst/CPACK_DESKTOP_SHORTCUTS.rst - /prop_inst/CPACK_NEVER_OVERWRITE.rst - /prop_inst/CPACK_PERMANENT.rst - /prop_inst/CPACK_START_MENU_SHORTCUTS.rst - /prop_inst/CPACK_STARTUP_SHORTCUTS.rst - /prop_inst/CPACK_WIX_ACL.rst - - -Deprecated Properties on Directories -==================================== - -.. toctree:: - :maxdepth: 1 - - /prop_dir/ADDITIONAL_MAKE_CLEAN_FILES - /prop_dir/COMPILE_DEFINITIONS_CONFIG - /prop_dir/TEST_INCLUDE_FILE - - -Deprecated Properties on Targets -================================ - -.. toctree:: - :maxdepth: 1 - - /prop_tgt/COMPILE_DEFINITIONS_CONFIG - /prop_tgt/POST_INSTALL_SCRIPT - /prop_tgt/PRE_INSTALL_SCRIPT - - -Deprecated Properties on Source Files -===================================== - -.. toctree:: - :maxdepth: 1 - - /prop_sf/COMPILE_DEFINITIONS_CONFIG
diff --git a/share/cmake-3.18/Help/manual/cmake-qt.7.rst b/share/cmake-3.18/Help/manual/cmake-qt.7.rst deleted file mode 100644 index d8d6172..0000000 --- a/share/cmake-3.18/Help/manual/cmake-qt.7.rst +++ /dev/null
@@ -1,259 +0,0 @@ -.. cmake-manual-description: CMake Qt Features Reference - -cmake-qt(7) -*********** - -.. only:: html - - .. contents:: - -Introduction -============ - -CMake can find and use Qt 4 and Qt 5 libraries. The Qt 4 libraries are found -by the :module:`FindQt4` find-module shipped with CMake, whereas the -Qt 5 libraries are found using "Config-file Packages" shipped with Qt 5. See -:manual:`cmake-packages(7)` for more information about CMake packages, and -see `the Qt cmake manual <http://qt-project.org/doc/qt-5/cmake-manual.html>`_ -for your Qt version. - -Qt 4 and Qt 5 may be used together in the same -:manual:`CMake buildsystem <cmake-buildsystem(7)>`: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.8.0 FATAL_ERROR) - - project(Qt4And5) - - set(CMAKE_AUTOMOC ON) - - find_package(Qt5 COMPONENTS Widgets DBus REQUIRED) - add_executable(publisher publisher.cpp) - target_link_libraries(publisher Qt5::Widgets Qt5::DBus) - - find_package(Qt4 REQUIRED) - add_executable(subscriber subscriber.cpp) - target_link_libraries(subscriber Qt4::QtGui Qt4::QtDBus) - -A CMake target may not link to both Qt 4 and Qt 5. A diagnostic is issued if -this is attempted or results from transitive target dependency evaluation. - -Qt Build Tools -============== - -Qt relies on some bundled tools for code generation, such as ``moc`` for -meta-object code generation, ``uic`` for widget layout and population, -and ``rcc`` for virtual file system content generation. These tools may be -automatically invoked by :manual:`cmake(1)` if the appropriate conditions -are met. The automatic tool invocation may be used with both Qt 4 and Qt 5. - -AUTOMOC -^^^^^^^ - -The :prop_tgt:`AUTOMOC` target property controls whether :manual:`cmake(1)` -inspects the C++ files in the target to determine if they require ``moc`` to -be run, and to create rules to execute ``moc`` at the appropriate time. - -If a macro from :prop_tgt:`AUTOMOC_MACRO_NAMES` is found in a header file, -``moc`` will be run on the file. The result will be put into a file named -according to ``moc_<basename>.cpp``. -If the macro is found in a C++ implementation -file, the moc output will be put into a file named according to -``<basename>.moc``, following the Qt conventions. The ``<basename>.moc`` must -be included by the user in the C++ implementation file with a preprocessor -``#include``. - -Included ``moc_*.cpp`` and ``*.moc`` files will be generated in the -``<AUTOGEN_BUILD_DIR>/include`` directory which is -automatically added to the target's :prop_tgt:`INCLUDE_DIRECTORIES`. - -* This differs from CMake 3.7 and below; see their documentation for details. - -* For :prop_gbl:`multi configuration generators <GENERATOR_IS_MULTI_CONFIG>`, - the include directory is ``<AUTOGEN_BUILD_DIR>/include_<CONFIG>``. - -* See :prop_tgt:`AUTOGEN_BUILD_DIR`. - -Not included ``moc_<basename>.cpp`` files will be generated in custom -folders to avoid name collisions and included in a separate -``<AUTOGEN_BUILD_DIR>/mocs_compilation.cpp`` file which is compiled -into the target. - -* See :prop_tgt:`AUTOGEN_BUILD_DIR`. - -The ``moc`` command line will consume the :prop_tgt:`COMPILE_DEFINITIONS` and -:prop_tgt:`INCLUDE_DIRECTORIES` target properties from the target it is being -invoked for, and for the appropriate build configuration. - -The :prop_tgt:`AUTOMOC` target property may be pre-set for all -following targets by setting the :variable:`CMAKE_AUTOMOC` variable. The -:prop_tgt:`AUTOMOC_MOC_OPTIONS` target property may be populated to set -options to pass to ``moc``. The :variable:`CMAKE_AUTOMOC_MOC_OPTIONS` -variable may be populated to pre-set the options for all following targets. - -Additional macro names to search for can be added to -:prop_tgt:`AUTOMOC_MACRO_NAMES`. - -Additional ``moc`` dependency file names can be extracted from source code -by using :prop_tgt:`AUTOMOC_DEPEND_FILTERS`. - -Source C++ files can be excluded from :prop_tgt:`AUTOMOC` processing by -enabling :prop_sf:`SKIP_AUTOMOC` or the broader :prop_sf:`SKIP_AUTOGEN`. - -.. _`Qt AUTOUIC`: - -AUTOUIC -^^^^^^^ - -The :prop_tgt:`AUTOUIC` target property controls whether :manual:`cmake(1)` -inspects the C++ files in the target to determine if they require ``uic`` to -be run, and to create rules to execute ``uic`` at the appropriate time. - -If a preprocessor ``#include`` directive is found which matches -``<path>ui_<basename>.h``, and a ``<basename>.ui`` file exists, -then ``uic`` will be executed to generate the appropriate file. -The ``<basename>.ui`` file is searched for in the following places - -1. ``<source_dir>/<basename>.ui`` -2. ``<source_dir>/<path><basename>.ui`` -3. ``<AUTOUIC_SEARCH_PATHS>/<basename>.ui`` -4. ``<AUTOUIC_SEARCH_PATHS>/<path><basename>.ui`` - -where ``<source_dir>`` is the directory of the C++ file and -:prop_tgt:`AUTOUIC_SEARCH_PATHS` is a list of additional search paths. - -The generated generated ``ui_*.h`` files are placed in the -``<AUTOGEN_BUILD_DIR>/include`` directory which is -automatically added to the target's :prop_tgt:`INCLUDE_DIRECTORIES`. - -* This differs from CMake 3.7 and below; see their documentation for details. - -* For :prop_gbl:`multi configuration generators <GENERATOR_IS_MULTI_CONFIG>`, - the include directory is ``<AUTOGEN_BUILD_DIR>/include_<CONFIG>``. - -* See :prop_tgt:`AUTOGEN_BUILD_DIR`. - -The :prop_tgt:`AUTOUIC` target property may be pre-set for all following -targets by setting the :variable:`CMAKE_AUTOUIC` variable. The -:prop_tgt:`AUTOUIC_OPTIONS` target property may be populated to set options -to pass to ``uic``. The :variable:`CMAKE_AUTOUIC_OPTIONS` variable may be -populated to pre-set the options for all following targets. The -:prop_sf:`AUTOUIC_OPTIONS` source file property may be set on the -``<basename>.ui`` file to set particular options for the file. This -overrides options from the :prop_tgt:`AUTOUIC_OPTIONS` target property. - -A target may populate the :prop_tgt:`INTERFACE_AUTOUIC_OPTIONS` target -property with options that should be used when invoking ``uic``. This must be -consistent with the :prop_tgt:`AUTOUIC_OPTIONS` target property content of the -depender target. The :variable:`CMAKE_DEBUG_TARGET_PROPERTIES` variable may -be used to track the origin target of such -:prop_tgt:`INTERFACE_AUTOUIC_OPTIONS`. This means that a library which -provides an alternative translation system for Qt may specify options which -should be used when running ``uic``: - -.. code-block:: cmake - - add_library(KI18n klocalizedstring.cpp) - target_link_libraries(KI18n Qt5::Core) - - # KI18n uses the tr2i18n() function instead of tr(). That function is - # declared in the klocalizedstring.h header. - set(autouic_options - -tr tr2i18n - -include klocalizedstring.h - ) - - set_property(TARGET KI18n APPEND PROPERTY - INTERFACE_AUTOUIC_OPTIONS ${autouic_options} - ) - -A consuming project linking to the target exported from upstream automatically -uses appropriate options when ``uic`` is run by :prop_tgt:`AUTOUIC`, as a -result of linking with the :prop_tgt:`IMPORTED` target: - -.. code-block:: cmake - - set(CMAKE_AUTOUIC ON) - # Uses a libwidget.ui file: - add_library(LibWidget libwidget.cpp) - target_link_libraries(LibWidget - KF5::KI18n - Qt5::Widgets - ) - -Source files can be excluded from :prop_tgt:`AUTOUIC` processing by -enabling :prop_sf:`SKIP_AUTOUIC` or the broader :prop_sf:`SKIP_AUTOGEN`. - -.. _`Qt AUTORCC`: - -AUTORCC -^^^^^^^ - -The :prop_tgt:`AUTORCC` target property controls whether :manual:`cmake(1)` -creates rules to execute ``rcc`` at the appropriate time on source files -which have the suffix ``.qrc``. - -.. code-block:: cmake - - add_executable(myexe main.cpp resource_file.qrc) - -The :prop_tgt:`AUTORCC` target property may be pre-set for all following targets -by setting the :variable:`CMAKE_AUTORCC` variable. The -:prop_tgt:`AUTORCC_OPTIONS` target property may be populated to set options -to pass to ``rcc``. The :variable:`CMAKE_AUTORCC_OPTIONS` variable may be -populated to pre-set the options for all following targets. The -:prop_sf:`AUTORCC_OPTIONS` source file property may be set on the -``<name>.qrc`` file to set particular options for the file. This -overrides options from the :prop_tgt:`AUTORCC_OPTIONS` target property. - -Source files can be excluded from :prop_tgt:`AUTORCC` processing by -enabling :prop_sf:`SKIP_AUTORCC` or the broader :prop_sf:`SKIP_AUTOGEN`. - -The ``<ORIGIN>_autogen`` target -=============================== - -The ``moc`` and ``uic`` tools are executed as part of a synthesized -``<ORIGIN>_autogen`` :command:`custom target <add_custom_target>` generated by -CMake. By default that ``<ORIGIN>_autogen`` target inherits the dependencies -of the ``<ORIGIN>`` target (see :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS`). -Target dependencies may be added to the ``<ORIGIN>_autogen`` target by adding -them to the :prop_tgt:`AUTOGEN_TARGET_DEPENDS` target property. - -Visual Studio Generators -======================== - -When using the :manual:`Visual Studio generators <cmake-generators(7)>`, CMake -generates a ``PRE_BUILD`` :command:`custom command <add_custom_command>` -instead of the ``<ORIGIN>_autogen`` :command:`custom target <add_custom_target>` -(for :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`). -This isn't always possible though and -an ``<ORIGIN>_autogen`` :command:`custom target <add_custom_target>` is used, -when either - -- the ``<ORIGIN>`` target depends on :prop_sf:`GENERATED` files which aren't - excluded from :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` by - :prop_sf:`SKIP_AUTOMOC`, :prop_sf:`SKIP_AUTOUIC`, :prop_sf:`SKIP_AUTOGEN` - or :policy:`CMP0071` -- :prop_tgt:`AUTOGEN_TARGET_DEPENDS` lists a source file -- :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET` is enabled - -qtmain.lib on Windows -===================== - -The Qt 4 and 5 :prop_tgt:`IMPORTED` targets for the QtGui libraries specify -that the qtmain.lib static library shipped with Qt will be linked by all -dependent executables which have the :prop_tgt:`WIN32_EXECUTABLE` enabled. - -To disable this behavior, enable the ``Qt5_NO_LINK_QTMAIN`` target property for -Qt 5 based targets or ``QT4_NO_LINK_QTMAIN`` target property for Qt 4 based -targets. - -.. code-block:: cmake - - add_executable(myexe WIN32 main.cpp) - target_link_libraries(myexe Qt4::QtGui) - - add_executable(myexe_no_qtmain WIN32 main_no_qtmain.cpp) - set_property(TARGET main_no_qtmain PROPERTY QT4_NO_LINK_QTMAIN ON) - target_link_libraries(main_no_qtmain Qt4::QtGui)
diff --git a/share/cmake-3.18/Help/manual/cmake-server.7.rst b/share/cmake-3.18/Help/manual/cmake-server.7.rst deleted file mode 100644 index 8f10b9f..0000000 --- a/share/cmake-3.18/Help/manual/cmake-server.7.rst +++ /dev/null
@@ -1,744 +0,0 @@ -.. cmake-manual-description: CMake Server - -cmake-server(7) -*************** - -.. only:: html - - .. contents:: - -.. deprecated:: 3.15 - - This will be removed from a future version of CMake. - Clients should use the :manual:`cmake-file-api(7)` instead. - -Introduction -============ - -:manual:`cmake(1)` is capable of providing semantic information about -CMake code it executes to generate a buildsystem. If executed with -the ``-E server`` command line options, it starts in a long running mode -and allows a client to request the available information via a JSON protocol. - -The protocol is designed to be useful to IDEs, refactoring tools, and -other tools which have a need to understand the buildsystem in entirety. - -A single :manual:`cmake-buildsystem(7)` may describe buildsystem contents -and build properties which differ based on -:manual:`generation-time context <cmake-generator-expressions(7)>` -including: - -* The Platform (eg, Windows, APPLE, Linux). -* The build configuration (eg, Debug, Release, Coverage). -* The Compiler (eg, MSVC, GCC, Clang) and compiler version. -* The language of the source files compiled. -* Available compile features (eg CXX variadic templates). -* CMake policies. - -The protocol aims to provide information to tooling to satisfy several -needs: - -#. Provide a complete and easily parsed source of all information relevant - to the tooling as it relates to the source code. There should be no need - for tooling to parse generated buildsystems to access include directories - or compile definitions for example. -#. Semantic information about the CMake buildsystem itself. -#. Provide a stable interface for reading the information in the CMake cache. -#. Information for determining when cmake needs to be re-run as a result of - file changes. - - -Operation -========= - -Start :manual:`cmake(1)` in the server command mode, supplying the path to -the build directory to process:: - - cmake -E server (--debug|--pipe=<NAMED_PIPE>) - -The server will communicate using stdin/stdout (with the ``--debug`` parameter) -or using a named pipe (with the ``--pipe=<NAMED_PIPE>`` parameter). Note -that "named pipe" refers to a local domain socket on Unix and to a named pipe -on Windows. - -When connecting to the server (via named pipe or by starting it in ``--debug`` -mode), the server will reply with a hello message:: - - [== "CMake Server" ==[ - {"supportedProtocolVersions":[{"major":1,"minor":0}],"type":"hello"} - ]== "CMake Server" ==] - -Messages sent to and from the process are wrapped in magic strings:: - - [== "CMake Server" ==[ - { - ... some JSON message ... - } - ]== "CMake Server" ==] - -The server is now ready to accept further requests via the named pipe -or stdin. - - -Debugging -========= - -CMake server mode can be asked to provide statistics on execution times, etc. -or to dump a copy of the response into a file. This is done passing a "debug" -JSON object as a child of the request. - -The debug object supports the "showStats" key, which takes a boolean and makes -the server mode return a "zzzDebug" object with stats as part of its response. -"dumpToFile" takes a string value and will cause the cmake server to copy -the response into the given filename. - -This is a response from the cmake server with "showStats" set to true:: - - [== "CMake Server" ==[ - { - "cookie":"", - "errorMessage":"Waiting for type \"handshake\".", - "inReplyTo":"unknown", - "type":"error", - "zzzDebug": { - "dumpFile":"/tmp/error.txt", - "jsonSerialization":0.011016, - "size":111, - "totalTime":0.025995 - } - } - ]== "CMake Server" ==] - -The server has made a copy of this response into the file /tmp/error.txt and -took 0.011 seconds to turn the JSON response into a string, and it took 0.025 -seconds to process the request in total. The reply has a size of 111 bytes. - - -Protocol API -============ - - -General Message Layout ----------------------- - -All messages need to have a "type" value, which identifies the type of -message that is passed back or forth. E.g. the initial message sent by the -server is of type "hello". Messages without a type will generate an response -of type "error". - -All requests sent to the server may contain a "cookie" value. This value -will he handed back unchanged in all responses triggered by the request. - -All responses will contain a value "inReplyTo", which may be empty in -case of parse errors, but will contain the type of the request message -in all other cases. - - -Type "reply" -^^^^^^^^^^^^ - -This type is used by the server to reply to requests. - -The message may -- depending on the type of the original request -- -contain values. - -Example:: - - [== "CMake Server" ==[ - {"cookie":"zimtstern","inReplyTo":"handshake","type":"reply"} - ]== "CMake Server" ==] - - -Type "error" -^^^^^^^^^^^^ - -This type is used to return an error condition to the client. It will -contain an "errorMessage". - -Example:: - - [== "CMake Server" ==[ - {"cookie":"","errorMessage":"Protocol version not supported.","inReplyTo":"handshake","type":"error"} - ]== "CMake Server" ==] - - -Type "progress" -^^^^^^^^^^^^^^^ - -When the server is busy for a long time, it is polite to send back replies of -type "progress" to the client. These will contain a "progressMessage" with a -string describing the action currently taking place as well as -"progressMinimum", "progressMaximum" and "progressCurrent" with integer values -describing the range of progress. - -Messages of type "progress" will be followed by more "progress" messages or with -a message of type "reply" or "error" that complete the request. - -"progress" messages may not be emitted after the "reply" or "error" message for -the request that triggered the responses was delivered. - - -Type "message" -^^^^^^^^^^^^^^ - -A message is triggered when the server processes a request and produces some -form of output that should be displayed to the user. A Message has a "message" -with the actual text to display as well as a "title" with a suggested dialog -box title. - -Example:: - - [== "CMake Server" ==[ - {"cookie":"","message":"Something happened.","title":"Title Text","inReplyTo":"handshake","type":"message"} - ]== "CMake Server" ==] - - -Type "signal" -^^^^^^^^^^^^^ - -The server can send signals when it detects changes in the system state. Signals -are of type "signal", have an empty "cookie" and "inReplyTo" field and always -have a "name" set to show which signal was sent. - - -Specific Signals ----------------- - -The cmake server may sent signals with the following names: - -"dirty" Signal -^^^^^^^^^^^^^^ - -The "dirty" signal is sent whenever the server determines that the configuration -of the project is no longer up-to-date. This happens when any of the files that have -an influence on the build system is changed. - -The "dirty" signal may look like this:: - - [== "CMake Server" ==[ - { - "cookie":"", - "inReplyTo":"", - "name":"dirty", - "type":"signal"} - ]== "CMake Server" ==] - - -"fileChange" Signal -^^^^^^^^^^^^^^^^^^^ - -The "fileChange" signal is sent whenever a watched file is changed. It contains -the "path" that has changed and a list of "properties" with the kind of change -that was detected. Possible changes are "change" and "rename". - -The "fileChange" signal looks like this:: - - [== "CMake Server" ==[ - { - "cookie":"", - "inReplyTo":"", - "name":"fileChange", - "path":"/absolute/CMakeLists.txt", - "properties":["change"], - "type":"signal"} - ]== "CMake Server" ==] - - -Specific Message Types ----------------------- - - -Type "hello" -^^^^^^^^^^^^ - -The initial message send by the cmake server on startup is of type "hello". -This is the only message ever sent by the server that is not of type "reply", -"progress" or "error". - -It will contain "supportedProtocolVersions" with an array of server protocol -versions supported by the cmake server. These are JSON objects with "major" and -"minor" keys containing non-negative integer values. Some versions may be marked -as experimental. These will contain the "isExperimental" key set to true. Enabling -these requires a special command line argument when starting the cmake server mode. - -Within a "major" version all "minor" versions are fully backwards compatible. -New "minor" versions may introduce functionality in such a way that existing -clients of the same "major" version will continue to work, provided they -ignore keys in the output that they do not know about. - -Example:: - - [== "CMake Server" ==[ - {"supportedProtocolVersions":[{"major":0,"minor":1}],"type":"hello"} - ]== "CMake Server" ==] - - -Type "handshake" -^^^^^^^^^^^^^^^^ - -The first request that the client may send to the server is of type "handshake". - -This request needs to pass one of the "supportedProtocolVersions" of the "hello" -type response received earlier back to the server in the "protocolVersion" field. -Giving the "major" version of the requested protocol version will make the server -use the latest minor version of that protocol. Use this if you do not explicitly -need to depend on a specific minor version. - -Protocol version 1.0 requires the following attributes to be set: - - * "sourceDirectory" with a path to the sources - * "buildDirectory" with a path to the build directory - * "generator" with the generator name - * "extraGenerator" (optional!) with the extra generator to be used - * "platform" with the generator platform (if supported by the generator) - * "toolset" with the generator toolset (if supported by the generator) - -Protocol version 1.2 makes all but the build directory optional, provided -there is a valid cache in the build directory that contains all the other -information already. - -Example:: - - [== "CMake Server" ==[ - {"cookie":"zimtstern","type":"handshake","protocolVersion":{"major":0}, - "sourceDirectory":"/home/code/cmake", "buildDirectory":"/tmp/testbuild", - "generator":"Ninja"} - ]== "CMake Server" ==] - -which will result in a response type "reply":: - - [== "CMake Server" ==[ - {"cookie":"zimtstern","inReplyTo":"handshake","type":"reply"} - ]== "CMake Server" ==] - -indicating that the server is ready for action. - - -Type "globalSettings" -^^^^^^^^^^^^^^^^^^^^^ - -This request can be sent after the initial handshake. It will return a -JSON structure with information on cmake state. - -Example:: - - [== "CMake Server" ==[ - {"type":"globalSettings"} - ]== "CMake Server" ==] - -which will result in a response type "reply":: - - [== "CMake Server" ==[ - { - "buildDirectory": "/tmp/test-build", - "capabilities": { - "generators": [ - { - "extraGenerators": [], - "name": "Watcom WMake", - "platformSupport": false, - "toolsetSupport": false - }, - <...> - ], - "serverMode": false, - "version": { - "isDirty": false, - "major": 3, - "minor": 6, - "patch": 20160830, - "string": "3.6.20160830-gd6abad", - "suffix": "gd6abad" - } - }, - "checkSystemVars": false, - "cookie": "", - "extraGenerator": "", - "generator": "Ninja", - "debugOutput": false, - "inReplyTo": "globalSettings", - "sourceDirectory": "/home/code/cmake", - "trace": false, - "traceExpand": false, - "type": "reply", - "warnUninitialized": false, - "warnUnused": false, - "warnUnusedCli": true - } - ]== "CMake Server" ==] - - -Type "setGlobalSettings" -^^^^^^^^^^^^^^^^^^^^^^^^ - -This request can be sent to change the global settings attributes. Unknown -attributes are going to be ignored. Read-only attributes reported by -"globalSettings" are all capabilities, buildDirectory, generator, -extraGenerator and sourceDirectory. Any attempt to set these will be ignored, -too. - -All other settings will be changed. - -The server will respond with an empty reply message or an error. - -Example:: - - [== "CMake Server" ==[ - {"type":"setGlobalSettings","debugOutput":true} - ]== "CMake Server" ==] - -CMake will reply to this with:: - - [== "CMake Server" ==[ - {"inReplyTo":"setGlobalSettings","type":"reply"} - ]== "CMake Server" ==] - - -Type "configure" -^^^^^^^^^^^^^^^^ - -This request will configure a project for build. - -To configure a build directory already containing cmake files, it is enough to -set "buildDirectory" via "setGlobalSettings". To create a fresh build directory -you also need to set "currentGenerator" and "sourceDirectory" via "setGlobalSettings" -in addition to "buildDirectory". - -You may a list of strings to "configure" via the "cacheArguments" key. These -strings will be interpreted similar to command line arguments related to -cache handling that are passed to the cmake command line client. - -Example:: - - [== "CMake Server" ==[ - {"type":"configure", "cacheArguments":["-Dsomething=else"]} - ]== "CMake Server" ==] - -CMake will reply like this (after reporting progress for some time):: - - [== "CMake Server" ==[ - {"cookie":"","inReplyTo":"configure","type":"reply"} - ]== "CMake Server" ==] - - -Type "compute" -^^^^^^^^^^^^^^ - -This request will generate build system files in the build directory and -is only available after a project was successfully "configure"d. - -Example:: - - [== "CMake Server" ==[ - {"type":"compute"} - ]== "CMake Server" ==] - -CMake will reply (after reporting progress information):: - - [== "CMake Server" ==[ - {"cookie":"","inReplyTo":"compute","type":"reply"} - ]== "CMake Server" ==] - - -Type "codemodel" -^^^^^^^^^^^^^^^^ - -The "codemodel" request can be used after a project was "compute"d successfully. - -It will list the complete project structure as it is known to cmake. - -The reply will contain a key "configurations", which will contain a list of -configuration objects. Configuration objects are used to destinquish between -different configurations the build directory might have enabled. While most -generators only support one configuration, others might support several. - -Each configuration object can have the following keys: - -"name" - contains the name of the configuration. The name may be empty. -"projects" - contains a list of project objects, one for each build project. - -Project objects define one (sub-)project defined in the cmake build system. - -Each project object can have the following keys: - -"name" - contains the (sub-)projects name. -"minimumCMakeVersion" - contains the minimum cmake version allowed for this project, null if the - project doesn't specify one. -"hasInstallRule" - true if the project contains any install rules, false otherwise. -"sourceDirectory" - contains the current source directory -"buildDirectory" - contains the current build directory. -"targets" - contains a list of build system target objects. - -Target objects define individual build targets for a certain configuration. - -Each target object can have the following keys: - -"name" - contains the name of the target. -"type" - defines the type of build of the target. Possible values are - "STATIC_LIBRARY", "MODULE_LIBRARY", "SHARED_LIBRARY", "OBJECT_LIBRARY", - "EXECUTABLE", "UTILITY" and "INTERFACE_LIBRARY". -"fullName" - contains the full name of the build result (incl. extensions, etc.). -"sourceDirectory" - contains the current source directory. -"buildDirectory" - contains the current build directory. -"isGeneratorProvided" - true if the target is auto-created by a generator, false otherwise -"hasInstallRule" - true if the target contains any install rules, false otherwise. -"installPaths" - full path to the destination directories defined by target install rules. -"artifacts" - with a list of build artifacts. The list is sorted with the most - important artifacts first (e.g. a .DLL file is listed before a - .PDB file on windows). -"linkerLanguage" - contains the language of the linker used to produce the artifact. -"linkLibraries" - with a list of libraries to link to. This value is encoded in the - system's native shell format. -"linkFlags" - with a list of flags to pass to the linker. This value is encoded in - the system's native shell format. -"linkLanguageFlags" - with the flags for a compiler using the linkerLanguage. This value is - encoded in the system's native shell format. -"frameworkPath" - with the framework path (on Apple computers). This value is encoded - in the system's native shell format. -"linkPath" - with the link path. This value is encoded in the system's native shell - format. -"sysroot" - with the sysroot path. -"fileGroups" - contains the source files making up the target. - -FileGroups are used to group sources using similar settings together. - -Each fileGroup object may contain the following keys: - -"language" - contains the programming language used by all files in the group. -"compileFlags" - with a string containing all the flags passed to the compiler - when building any of the files in this group. This value is encoded in - the system's native shell format. -"includePath" - with a list of include paths. Each include path is an object - containing a "path" with the actual include path and "isSystem" with a bool - value informing whether this is a normal include or a system include. This - value is encoded in the system's native shell format. -"defines" - with a list of defines in the form "SOMEVALUE" or "SOMEVALUE=42". This - value is encoded in the system's native shell format. -"sources" - with a list of source files. - -All file paths in the fileGroup are either absolute or relative to the -sourceDirectory of the target. - -Example:: - - [== "CMake Server" ==[ - {"type":"codemodel"} - ]== "CMake Server" ==] - -CMake will reply:: - - [== "CMake Server" ==[ - { - "configurations": [ - { - "name": "", - "projects": [ - { - "buildDirectory": "/tmp/build/Source/CursesDialog/form", - "name": "CMAKE_FORM", - "sourceDirectory": "/home/code/src/cmake/Source/CursesDialog/form", - "targets": [ - { - "artifacts": [ "/tmp/build/Source/CursesDialog/form/libcmForm.a" ], - "buildDirectory": "/tmp/build/Source/CursesDialog/form", - "fileGroups": [ - { - "compileFlags": " -std=gnu11", - "defines": [ "CURL_STATICLIB", "LIBARCHIVE_STATIC" ], - "includePath": [ { "path": "/tmp/build/Utilities" }, <...> ], - "isGenerated": false, - "language": "C", - "sources": [ "fld_arg.c", <...> ] - } - ], - "fullName": "libcmForm.a", - "linkerLanguage": "C", - "name": "cmForm", - "sourceDirectory": "/home/code/src/cmake/Source/CursesDialog/form", - "type": "STATIC_LIBRARY" - } - ] - }, - <...> - ] - } - ], - "cookie": "", - "inReplyTo": "codemodel", - "type": "reply" - } - ]== "CMake Server" ==] - - -Type "ctestInfo" -^^^^^^^^^^^^^^^^ - -The "ctestInfo" request can be used after a project was "compute"d successfully. - -It will list the complete project test structure as it is known to cmake. - -The reply will contain a key "configurations", which will contain a list of -configuration objects. Configuration objects are used to destinquish between -different configurations the build directory might have enabled. While most -generators only support one configuration, others might support several. - -Each configuration object can have the following keys: - -"name" - contains the name of the configuration. The name may be empty. -"projects" - contains a list of project objects, one for each build project. - -Project objects define one (sub-)project defined in the cmake build system. - -Each project object can have the following keys: - -"name" - contains the (sub-)projects name. -"ctestInfo" - contains a list of test objects. - -Each test object can have the following keys: - -"ctestName" - contains the name of the test. -"ctestCommand" - contains the test command. -"properties" - contains a list of test property objects. - -Each test property object can have the following keys: - -"key" - contains the test property key. -"value" - contains the test property value. - - -Type "cmakeInputs" -^^^^^^^^^^^^^^^^^^ - -The "cmakeInputs" requests will report files used by CMake as part -of the build system itself. - -This request is only available after a project was successfully -"configure"d. - -Example:: - - [== "CMake Server" ==[ - {"type":"cmakeInputs"} - ]== "CMake Server" ==] - -CMake will reply with the following information:: - - [== "CMake Server" ==[ - {"buildFiles": - [ - {"isCMake":true,"isTemporary":false,"sources":["/usr/lib/cmake/...", ... ]}, - {"isCMake":false,"isTemporary":false,"sources":["CMakeLists.txt", ...]}, - {"isCMake":false,"isTemporary":true,"sources":["/tmp/build/CMakeFiles/...", ...]} - ], - "cmakeRootDirectory":"/usr/lib/cmake", - "sourceDirectory":"/home/code/src/cmake", - "cookie":"", - "inReplyTo":"cmakeInputs", - "type":"reply" - } - ]== "CMake Server" ==] - -All file names are either relative to the top level source directory or -absolute. - -The list of files which "isCMake" set to true are part of the cmake installation. - -The list of files witch "isTemporary" set to true are part of the build directory -and will not survive the build directory getting cleaned out. - - -Type "cache" -^^^^^^^^^^^^ - -The "cache" request will list the cached configuration values. - -Example:: - - [== "CMake Server" ==[ - {"type":"cache"} - ]== "CMake Server" ==] - -CMake will respond with the following output:: - - [== "CMake Server" ==[ - { - "cookie":"","inReplyTo":"cache","type":"reply", - "cache": - [ - { - "key":"SOMEVALUE", - "properties": - { - "ADVANCED":"1", - "HELPSTRING":"This is not helpful" - } - "type":"STRING", - "value":"TEST"} - ] - } - ]== "CMake Server" ==] - -The output can be limited to a list of keys by passing an array of key names -to the "keys" optional field of the "cache" request. - - -Type "fileSystemWatchers" -^^^^^^^^^^^^^^^^^^^^^^^^^ - -The server can watch the filesystem for changes. The "fileSystemWatchers" -command will report on the files and directories watched. - -Example:: - - [== "CMake Server" ==[ - {"type":"fileSystemWatchers"} - ]== "CMake Server" ==] - -CMake will respond with the following output:: - - [== "CMake Server" ==[ - { - "cookie":"","inReplyTo":"fileSystemWatchers","type":"reply", - "watchedFiles": [ "/absolute/path" ], - "watchedDirectories": [ "/absolute" ] - } - ]== "CMake Server" ==]
diff --git a/share/cmake-3.18/Help/manual/cmake-toolchains.7.rst b/share/cmake-3.18/Help/manual/cmake-toolchains.7.rst deleted file mode 100644 index e8badd4..0000000 --- a/share/cmake-3.18/Help/manual/cmake-toolchains.7.rst +++ /dev/null
@@ -1,666 +0,0 @@ -.. cmake-manual-description: CMake Toolchains Reference - -cmake-toolchains(7) -******************* - -.. only:: html - - .. contents:: - -Introduction -============ - -CMake uses a toolchain of utilities to compile, link libraries and create -archives, and other tasks to drive the build. The toolchain utilities available -are determined by the languages enabled. In normal builds, CMake automatically -determines the toolchain for host builds based on system introspection and -defaults. In cross-compiling scenarios, a toolchain file may be specified -with information about compiler and utility paths. - -Languages -========= - -Languages are enabled by the :command:`project` command. Language-specific -built-in variables, such as -:variable:`CMAKE_CXX_COMPILER <CMAKE_<LANG>_COMPILER>`, -:variable:`CMAKE_CXX_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` etc are set by -invoking the :command:`project` command. If no project command -is in the top-level CMakeLists file, one will be implicitly generated. By default -the enabled languages are ``C`` and ``CXX``: - -.. code-block:: cmake - - project(C_Only C) - -A special value of ``NONE`` can also be used with the :command:`project` command -to enable no languages: - -.. code-block:: cmake - - project(MyProject NONE) - -The :command:`enable_language` command can be used to enable languages after the -:command:`project` command: - -.. code-block:: cmake - - enable_language(CXX) - -When a language is enabled, CMake finds a compiler for that language, and -determines some information, such as the vendor and version of the compiler, -the target architecture and bitwidth, the location of corresponding utilities -etc. - -The :prop_gbl:`ENABLED_LANGUAGES` global property contains the languages which -are currently enabled. - -Variables and Properties -======================== - -Several variables relate to the language components of a toolchain which are -enabled. :variable:`CMAKE_<LANG>_COMPILER` is the full path to the compiler used -for ``<LANG>``. :variable:`CMAKE_<LANG>_COMPILER_ID` is the identifier used -by CMake for the compiler and :variable:`CMAKE_<LANG>_COMPILER_VERSION` is the -version of the compiler. - -The :variable:`CMAKE_<LANG>_FLAGS` variables and the configuration-specific -equivalents contain flags that will be added to the compile command when -compiling a file of a particular language. - -As the linker is invoked by the compiler driver, CMake needs a way to determine -which compiler to use to invoke the linker. This is calculated by the -:prop_sf:`LANGUAGE` of source files in the target, and in the case of static -libraries, the language of the dependent libraries. The choice CMake makes may -be overridden with the :prop_tgt:`LINKER_LANGUAGE` target property. - -Toolchain Features -================== - -CMake provides the :command:`try_compile` command and wrapper macros such as -:module:`CheckCXXSourceCompiles`, :module:`CheckCXXSymbolExists` and -:module:`CheckIncludeFile` to test capability and availability of various -toolchain features. These APIs test the toolchain in some way and cache the -result so that the test does not have to be performed again the next time -CMake runs. - -Some toolchain features have built-in handling in CMake, and do not require -compile-tests. For example, :prop_tgt:`POSITION_INDEPENDENT_CODE` allows -specifying that a target should be built as position-independent code, if -the compiler supports that feature. The :prop_tgt:`<LANG>_VISIBILITY_PRESET` -and :prop_tgt:`VISIBILITY_INLINES_HIDDEN` target properties add flags for -hidden visibility, if supported by the compiler. - -.. _`Cross Compiling Toolchain`: - -Cross Compiling -=============== - -If :manual:`cmake(1)` is invoked with the command line parameter -``-DCMAKE_TOOLCHAIN_FILE=path/to/file``, the file will be loaded early to set -values for the compilers. -The :variable:`CMAKE_CROSSCOMPILING` variable is set to true when CMake is -cross-compiling. - -Note that using the :variable:`CMAKE_SOURCE_DIR` or :variable:`CMAKE_BINARY_DIR` -variables inside a toolchain file is typically undesirable. The toolchain -file is used in contexts where these variables have different values when used -in different places (e.g. as part of a call to :command:`try_compile`). In most -cases, where there is a need to evaluate paths inside a toolchain file, the more -appropriate variable to use would be :variable:`CMAKE_CURRENT_LIST_DIR`, since -it always has an unambiguous, predictable value. - -Cross Compiling for Linux -------------------------- - -A typical cross-compiling toolchain for Linux has content such -as: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME Linux) - set(CMAKE_SYSTEM_PROCESSOR arm) - - set(CMAKE_SYSROOT /home/devel/rasp-pi-rootfs) - set(CMAKE_STAGING_PREFIX /home/devel/stage) - - set(tools /home/devel/gcc-4.7-linaro-rpi-gnueabihf) - set(CMAKE_C_COMPILER ${tools}/bin/arm-linux-gnueabihf-gcc) - set(CMAKE_CXX_COMPILER ${tools}/bin/arm-linux-gnueabihf-g++) - - set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) - set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) - set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY) - set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY) - -The :variable:`CMAKE_SYSTEM_NAME` is the CMake-identifier of the target platform -to build for. - -The :variable:`CMAKE_SYSTEM_PROCESSOR` is the CMake-identifier of the target architecture -to build for. - -The :variable:`CMAKE_SYSROOT` is optional, and may be specified if a sysroot -is available. - -The :variable:`CMAKE_STAGING_PREFIX` is also optional. It may be used to specify -a path on the host to install to. The :variable:`CMAKE_INSTALL_PREFIX` is always -the runtime installation location, even when cross-compiling. - -The :variable:`CMAKE_<LANG>_COMPILER` variables may be set to full paths, or to -names of compilers to search for in standard locations. For toolchains that -do not support linking binaries without custom flags or scripts one may set -the :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` variable to ``STATIC_LIBRARY`` -to tell CMake not to try to link executables during its checks. - -CMake ``find_*`` commands will look in the sysroot, and the :variable:`CMAKE_FIND_ROOT_PATH` -entries by default in all cases, as well as looking in the host system root prefix. -Although this can be controlled on a case-by-case basis, when cross-compiling, it -can be useful to exclude looking in either the host or the target for particular -artifacts. Generally, includes, libraries and packages should be found in the -target system prefixes, whereas executables which must be run as part of the build -should be found only on the host and not on the target. This is the purpose of -the ``CMAKE_FIND_ROOT_PATH_MODE_*`` variables. - -.. _`Cray Cross-Compile`: - -Cross Compiling for the Cray Linux Environment ----------------------------------------------- - -Cross compiling for compute nodes in the Cray Linux Environment can be done -without needing a separate toolchain file. Specifying -``-DCMAKE_SYSTEM_NAME=CrayLinuxEnvironment`` on the CMake command line will -ensure that the appropriate build settings and search paths are configured. -The platform will pull its configuration from the current environment -variables and will configure a project to use the compiler wrappers from the -Cray Programming Environment's ``PrgEnv-*`` modules if present and loaded. - -The default configuration of the Cray Programming Environment is to only -support static libraries. This can be overridden and shared libraries -enabled by setting the ``CRAYPE_LINK_TYPE`` environment variable to -``dynamic``. - -Running CMake without specifying :variable:`CMAKE_SYSTEM_NAME` will -run the configure step in host mode assuming a standard Linux environment. -If not overridden, the ``PrgEnv-*`` compiler wrappers will end up getting used, -which if targeting the either the login node or compute node, is likely not the -desired behavior. The exception to this would be if you are building directly -on a NID instead of cross-compiling from a login node. If trying to build -software for a login node, you will need to either first unload the -currently loaded ``PrgEnv-*`` module or explicitly tell CMake to use the -system compilers in ``/usr/bin`` instead of the Cray wrappers. If instead -targeting a compute node is desired, just specify the -:variable:`CMAKE_SYSTEM_NAME` as mentioned above. - -Cross Compiling using Clang ---------------------------- - -Some compilers such as Clang are inherently cross compilers. -The :variable:`CMAKE_<LANG>_COMPILER_TARGET` can be set to pass a -value to those supported compilers when compiling: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME Linux) - set(CMAKE_SYSTEM_PROCESSOR arm) - - set(triple arm-linux-gnueabihf) - - set(CMAKE_C_COMPILER clang) - set(CMAKE_C_COMPILER_TARGET ${triple}) - set(CMAKE_CXX_COMPILER clang++) - set(CMAKE_CXX_COMPILER_TARGET ${triple}) - -Similarly, some compilers do not ship their own supplementary utilities -such as linkers, but provide a way to specify the location of the external -toolchain which will be used by the compiler driver. The -:variable:`CMAKE_<LANG>_COMPILER_EXTERNAL_TOOLCHAIN` variable can be set in a -toolchain file to pass the path to the compiler driver. - -Cross Compiling for QNX ------------------------ - -As the Clang compiler the QNX QCC compile is inherently a cross compiler. -And the :variable:`CMAKE_<LANG>_COMPILER_TARGET` can be set to pass a -value to those supported compilers when compiling: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME QNX) - - set(arch gcc_ntoarmv7le) - - set(CMAKE_C_COMPILER qcc) - set(CMAKE_C_COMPILER_TARGET ${arch}) - set(CMAKE_CXX_COMPILER QCC) - set(CMAKE_CXX_COMPILER_TARGET ${arch}) - - set(CMAKE_SYSROOT $ENV{QNX_TARGET}) - - -Cross Compiling for Windows CE ------------------------------- - -Cross compiling for Windows CE requires the corresponding SDK being -installed on your system. These SDKs are usually installed under -``C:/Program Files (x86)/Windows CE Tools/SDKs``. - -A toolchain file to configure a Visual Studio generator for -Windows CE may look like this: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME WindowsCE) - - set(CMAKE_SYSTEM_VERSION 8.0) - set(CMAKE_SYSTEM_PROCESSOR arm) - - set(CMAKE_GENERATOR_TOOLSET CE800) # Can be omitted for 8.0 - set(CMAKE_GENERATOR_PLATFORM SDK_AM335X_SK_WEC2013_V310) - -The :variable:`CMAKE_GENERATOR_PLATFORM` tells the generator which SDK to use. -Further :variable:`CMAKE_SYSTEM_VERSION` tells the generator what version of -Windows CE to use. Currently version 8.0 (Windows Embedded Compact 2013) is -supported out of the box. Other versions may require one to set -:variable:`CMAKE_GENERATOR_TOOLSET` to the correct value. - -Cross Compiling for Windows 10 Universal Applications ------------------------------------------------------ - -A toolchain file to configure a Visual Studio generator for a -Windows 10 Universal Application may look like this: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME WindowsStore) - set(CMAKE_SYSTEM_VERSION 10.0) - -A Windows 10 Universal Application targets both Windows Store and -Windows Phone. Specify the :variable:`CMAKE_SYSTEM_VERSION` variable -to be ``10.0`` to build with the latest available Windows 10 SDK. -Specify a more specific version (e.g. ``10.0.10240.0`` for RTM) -to build with the corresponding SDK. - -Cross Compiling for Windows Phone ---------------------------------- - -A toolchain file to configure a Visual Studio generator for -Windows Phone may look like this: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME WindowsPhone) - set(CMAKE_SYSTEM_VERSION 8.1) - -Cross Compiling for Windows Store ---------------------------------- - -A toolchain file to configure a Visual Studio generator for -Windows Store may look like this: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME WindowsStore) - set(CMAKE_SYSTEM_VERSION 8.1) - -.. _`Cross Compiling for Android`: - -Cross Compiling for Android ---------------------------- - -A toolchain file may configure cross-compiling for Android by setting the -:variable:`CMAKE_SYSTEM_NAME` variable to ``Android``. Further configuration -is specific to the Android development environment to be used. - -For :ref:`Visual Studio Generators`, CMake expects :ref:`NVIDIA Nsight Tegra -Visual Studio Edition <Cross Compiling for Android with NVIDIA Nsight Tegra -Visual Studio Edition>` to be installed. See that section for further -configuration details. - -For :ref:`Makefile Generators` and the :generator:`Ninja` generator, -CMake expects one of these environments: - -* :ref:`NDK <Cross Compiling for Android with the NDK>` -* :ref:`Standalone Toolchain <Cross Compiling for Android with a Standalone Toolchain>` - -CMake uses the following steps to select one of the environments: - -* If the :variable:`CMAKE_ANDROID_NDK` variable is set, the NDK at the - specified location will be used. - -* Else, if the :variable:`CMAKE_ANDROID_STANDALONE_TOOLCHAIN` variable - is set, the Standalone Toolchain at the specified location will be used. - -* Else, if the :variable:`CMAKE_SYSROOT` variable is set to a directory - of the form ``<ndk>/platforms/android-<api>/arch-<arch>``, the ``<ndk>`` - part will be used as the value of :variable:`CMAKE_ANDROID_NDK` and the - NDK will be used. - -* Else, if the :variable:`CMAKE_SYSROOT` variable is set to a directory of the - form ``<standalone-toolchain>/sysroot``, the ``<standalone-toolchain>`` part - will be used as the value of :variable:`CMAKE_ANDROID_STANDALONE_TOOLCHAIN` - and the Standalone Toolchain will be used. - -* Else, if a cmake variable ``ANDROID_NDK`` is set it will be used - as the value of :variable:`CMAKE_ANDROID_NDK`, and the NDK will be used. - -* Else, if a cmake variable ``ANDROID_STANDALONE_TOOLCHAIN`` is set, it will be - used as the value of :variable:`CMAKE_ANDROID_STANDALONE_TOOLCHAIN`, and the - Standalone Toolchain will be used. - -* Else, if an environment variable ``ANDROID_NDK_ROOT`` or - ``ANDROID_NDK`` is set, it will be used as the value of - :variable:`CMAKE_ANDROID_NDK`, and the NDK will be used. - -* Else, if an environment variable ``ANDROID_STANDALONE_TOOLCHAIN`` is - set then it will be used as the value of - :variable:`CMAKE_ANDROID_STANDALONE_TOOLCHAIN`, and the Standalone - Toolchain will be used. - -* Else, an error diagnostic will be issued that neither the NDK or - Standalone Toolchain can be found. - -.. _`Cross Compiling for Android with the NDK`: - -Cross Compiling for Android with the NDK -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -A toolchain file may configure :ref:`Makefile Generators` or the -:generator:`Ninja` generator to target Android for cross-compiling. - -Configure use of an Android NDK with the following variables: - -:variable:`CMAKE_SYSTEM_NAME` - Set to ``Android``. Must be specified to enable cross compiling - for Android. - -:variable:`CMAKE_SYSTEM_VERSION` - Set to the Android API level. If not specified, the value is - determined as follows: - - * If the :variable:`CMAKE_ANDROID_API` variable is set, its value - is used as the API level. - * If the :variable:`CMAKE_SYSROOT` variable is set, the API level is - detected from the NDK directory structure containing the sysroot. - * Otherwise, the latest API level available in the NDK is used. - -:variable:`CMAKE_ANDROID_ARCH_ABI` - Set to the Android ABI (architecture). If not specified, this - variable will default to ``armeabi``. - The :variable:`CMAKE_ANDROID_ARCH` variable will be computed - from ``CMAKE_ANDROID_ARCH_ABI`` automatically. - Also see the :variable:`CMAKE_ANDROID_ARM_MODE` and - :variable:`CMAKE_ANDROID_ARM_NEON` variables. - -:variable:`CMAKE_ANDROID_NDK` - Set to the absolute path to the Android NDK root directory. - A ``${CMAKE_ANDROID_NDK}/platforms`` directory must exist. - If not specified, a default for this variable will be chosen - as specified :ref:`above <Cross Compiling for Android>`. - -:variable:`CMAKE_ANDROID_NDK_DEPRECATED_HEADERS` - Set to a true value to use the deprecated per-api-level headers - instead of the unified headers. If not specified, the default will - be false unless using a NDK that does not provide unified headers. - -:variable:`CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION` - On NDK r19 or above, this variable must be unset or set to ``clang``. - On NDK r18 or below, set this to the version of the NDK toolchain to - be selected as the compiler. If not specified, the default will be - the latest available GCC toolchain. - -:variable:`CMAKE_ANDROID_STL_TYPE` - Set to specify which C++ standard library to use. If not specified, - a default will be selected as described in the variable documentation. - -The following variables will be computed and provided automatically: - -:variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX` - The absolute path prefix to the binutils in the NDK toolchain. - -:variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX` - The host platform suffix of the binutils in the NDK toolchain. - - -For example, a toolchain file might contain: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME Android) - set(CMAKE_SYSTEM_VERSION 21) # API level - set(CMAKE_ANDROID_ARCH_ABI arm64-v8a) - set(CMAKE_ANDROID_NDK /path/to/android-ndk) - set(CMAKE_ANDROID_STL_TYPE gnustl_static) - -Alternatively one may specify the values without a toolchain file: - -.. code-block:: console - - $ cmake ../src \ - -DCMAKE_SYSTEM_NAME=Android \ - -DCMAKE_SYSTEM_VERSION=21 \ - -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a \ - -DCMAKE_ANDROID_NDK=/path/to/android-ndk \ - -DCMAKE_ANDROID_STL_TYPE=gnustl_static - -.. _`Cross Compiling for Android with a Standalone Toolchain`: - -Cross Compiling for Android with a Standalone Toolchain -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -A toolchain file may configure :ref:`Makefile Generators` or the -:generator:`Ninja` generator to target Android for cross-compiling -using a standalone toolchain. - -Configure use of an Android standalone toolchain with the following variables: - -:variable:`CMAKE_SYSTEM_NAME` - Set to ``Android``. Must be specified to enable cross compiling - for Android. - -:variable:`CMAKE_ANDROID_STANDALONE_TOOLCHAIN` - Set to the absolute path to the standalone toolchain root directory. - A ``${CMAKE_ANDROID_STANDALONE_TOOLCHAIN}/sysroot`` directory - must exist. - If not specified, a default for this variable will be chosen - as specified :ref:`above <Cross Compiling for Android>`. - -:variable:`CMAKE_ANDROID_ARM_MODE` - When the standalone toolchain targets ARM, optionally set this to ``ON`` - to target 32-bit ARM instead of 16-bit Thumb. - See variable documentation for details. - -:variable:`CMAKE_ANDROID_ARM_NEON` - When the standalone toolchain targets ARM v7, optionally set thisto ``ON`` - to target ARM NEON devices. See variable documentation for details. - -The following variables will be computed and provided automatically: - -:variable:`CMAKE_SYSTEM_VERSION` - The Android API level detected from the standalone toolchain. - -:variable:`CMAKE_ANDROID_ARCH_ABI` - The Android ABI detected from the standalone toolchain. - -:variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX` - The absolute path prefix to the ``binutils`` in the standalone toolchain. - -:variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX` - The host platform suffix of the ``binutils`` in the standalone toolchain. - -For example, a toolchain file might contain: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME Android) - set(CMAKE_ANDROID_STANDALONE_TOOLCHAIN /path/to/android-toolchain) - -Alternatively one may specify the values without a toolchain file: - -.. code-block:: console - - $ cmake ../src \ - -DCMAKE_SYSTEM_NAME=Android \ - -DCMAKE_ANDROID_STANDALONE_TOOLCHAIN=/path/to/android-toolchain - -.. _`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition`: - -Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -A toolchain file to configure one of the :ref:`Visual Studio Generators` -to build using NVIDIA Nsight Tegra targeting Android may look like this: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME Android) - -The :variable:`CMAKE_GENERATOR_TOOLSET` may be set to select -the Nsight Tegra "Toolchain Version" value. - -See also target properties: - -* :prop_tgt:`ANDROID_ANT_ADDITIONAL_OPTIONS` -* :prop_tgt:`ANDROID_API_MIN` -* :prop_tgt:`ANDROID_API` -* :prop_tgt:`ANDROID_ARCH` -* :prop_tgt:`ANDROID_ASSETS_DIRECTORIES` -* :prop_tgt:`ANDROID_GUI` -* :prop_tgt:`ANDROID_JAR_DEPENDENCIES` -* :prop_tgt:`ANDROID_JAR_DIRECTORIES` -* :prop_tgt:`ANDROID_JAVA_SOURCE_DIR` -* :prop_tgt:`ANDROID_NATIVE_LIB_DEPENDENCIES` -* :prop_tgt:`ANDROID_NATIVE_LIB_DIRECTORIES` -* :prop_tgt:`ANDROID_PROCESS_MAX` -* :prop_tgt:`ANDROID_PROGUARD_CONFIG_PATH` -* :prop_tgt:`ANDROID_PROGUARD` -* :prop_tgt:`ANDROID_SECURE_PROPS_PATH` -* :prop_tgt:`ANDROID_SKIP_ANT_STEP` -* :prop_tgt:`ANDROID_STL_TYPE` - -.. _`Cross Compiling for iOS, tvOS, or watchOS`: - -Cross Compiling for iOS, tvOS, or watchOS ------------------------------------------ - -For cross-compiling to iOS, tvOS, or watchOS, the :generator:`Xcode` -generator is recommended. The :generator:`Unix Makefiles` or -:generator:`Ninja` generators can also be used, but they require the -project to handle more areas like target CPU selection and code signing. - -Any of the three systems can be targeted by setting the -:variable:`CMAKE_SYSTEM_NAME` variable to a value from the table below. -By default, the latest Device SDK is chosen. As for all Apple platforms, -a different SDK (e.g. a simulator) can be selected by setting the -:variable:`CMAKE_OSX_SYSROOT` variable, although this should rarely be -necessary (see :ref:`Switching Between Device and Simulator` below). -A list of available SDKs can be obtained by running ``xcodebuild -showsdks``. - -======= ================= ==================== ================ -OS CMAKE_SYSTEM_NAME Device SDK (default) Simulator SDK -======= ================= ==================== ================ -iOS iOS iphoneos iphonesimulator -tvOS tvOS appletvos appletvsimulator -watchOS watchOS watchos watchsimulator -======= ================= ==================== ================ - -For example, to create a CMake configuration for iOS, the following -command is sufficient: - -.. code-block:: console - - cmake .. -GXcode -DCMAKE_SYSTEM_NAME=iOS - -Variable :variable:`CMAKE_OSX_ARCHITECTURES` can be used to set architectures -for both device and simulator. Variable :variable:`CMAKE_OSX_DEPLOYMENT_TARGET` -can be used to set an iOS/tvOS/watchOS deployment target. - -Next configuration will install fat 5 architectures iOS library -and add the ``-miphoneos-version-min=9.3``/``-mios-simulator-version-min=9.3`` -flags to the compiler: - -.. code-block:: console - - $ cmake -S. -B_builds -GXcode \ - -DCMAKE_SYSTEM_NAME=iOS \ - "-DCMAKE_OSX_ARCHITECTURES=armv7;armv7s;arm64;i386;x86_64" \ - -DCMAKE_OSX_DEPLOYMENT_TARGET=9.3 \ - -DCMAKE_INSTALL_PREFIX=`pwd`/_install \ - -DCMAKE_XCODE_ATTRIBUTE_ONLY_ACTIVE_ARCH=NO \ - -DCMAKE_IOS_INSTALL_COMBINED=YES - -Example: - -.. code-block:: cmake - - # CMakeLists.txt - cmake_minimum_required(VERSION 3.14) - project(foo) - add_library(foo foo.cpp) - install(TARGETS foo DESTINATION lib) - -Install: - -.. code-block:: console - - $ cmake --build _builds --config Release --target install - -Check library: - -.. code-block:: console - - $ lipo -info _install/lib/libfoo.a - Architectures in the fat file: _install/lib/libfoo.a are: i386 armv7 armv7s x86_64 arm64 - -.. code-block:: console - - $ otool -l _install/lib/libfoo.a | grep -A2 LC_VERSION_MIN_IPHONEOS - cmd LC_VERSION_MIN_IPHONEOS - cmdsize 16 - version 9.3 - -Code Signing -^^^^^^^^^^^^ - -Some build artifacts for the embedded Apple platforms require mandatory -code signing. If the :generator:`Xcode` generator is being used and -code signing is required or desired, the development team ID can be -specified via the ``CMAKE_XCODE_ATTRIBUTE_DEVELOPMENT_TEAM`` CMake variable. -This team ID will then be included in the generated Xcode project. -By default, CMake avoids the need for code signing during the internal -configuration phase (i.e compiler ID and feature detection). - -.. _`Switching Between Device and Simulator`: - -Switching Between Device and Simulator -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -When configuring for any of the embedded platforms, one can target either -real devices or the simulator. Both have their own separate SDK, but CMake -only supports specifying a single SDK for the configuration phase. This -means the developer must select one or the other at configuration time. -When using the :generator:`Xcode` generator, this is less of a limitation -because Xcode still allows you to build for either a device or a simulator, -even though configuration was only performed for one of the two. From -within the Xcode IDE, builds are performed for the selected "destination" -platform. When building from the command line, the desired sdk can be -specified directly by passing a ``-sdk`` option to the underlying build -tool (``xcodebuild``). For example: - -.. code-block:: console - - $ cmake --build ... -- -sdk iphonesimulator - -Please note that checks made during configuration were performed against -the configure-time SDK and might not hold true for other SDKs. Commands -like :command:`find_package`, :command:`find_library`, etc. store and use -details only for the configured SDK/platform, so they can be problematic -if wanting to switch between device and simulator builds. You can follow -the next rules to make device + simulator configuration work: - -- Use explicit ``-l`` linker flag, - e.g. ``target_link_libraries(foo PUBLIC "-lz")`` - -- Use explicit ``-framework`` linker flag, - e.g. ``target_link_libraries(foo PUBLIC "-framework CoreFoundation")`` - -- Use :command:`find_package` only for libraries installed with - :variable:`CMAKE_IOS_INSTALL_COMBINED` feature
diff --git a/share/cmake-3.18/Help/manual/cmake-variables.7.rst b/share/cmake-3.18/Help/manual/cmake-variables.7.rst deleted file mode 100644 index 6480db1..0000000 --- a/share/cmake-3.18/Help/manual/cmake-variables.7.rst +++ /dev/null
@@ -1,690 +0,0 @@ -.. cmake-manual-description: CMake Variables Reference - -cmake-variables(7) -****************** - -.. only:: html - - .. contents:: - -This page documents variables that are provided by CMake -or have meaning to CMake when set by project code. - -For general information on variables, see the -:ref:`Variables <CMake Language Variables>` -section in the cmake-language manual. - -.. include:: ID_RESERVE.txt - -Variables that Provide Information -================================== - -.. toctree:: - :maxdepth: 1 - - /variable/CMAKE_AR - /variable/CMAKE_ARGC - /variable/CMAKE_ARGV0 - /variable/CMAKE_BINARY_DIR - /variable/CMAKE_BUILD_TOOL - /variable/CMAKE_CACHEFILE_DIR - /variable/CMAKE_CACHE_MAJOR_VERSION - /variable/CMAKE_CACHE_MINOR_VERSION - /variable/CMAKE_CACHE_PATCH_VERSION - /variable/CMAKE_CFG_INTDIR - /variable/CMAKE_COMMAND - /variable/CMAKE_CPACK_COMMAND - /variable/CMAKE_CROSSCOMPILING - /variable/CMAKE_CROSSCOMPILING_EMULATOR - /variable/CMAKE_CTEST_COMMAND - /variable/CMAKE_CURRENT_BINARY_DIR - /variable/CMAKE_CURRENT_FUNCTION - /variable/CMAKE_CURRENT_FUNCTION_LIST_DIR - /variable/CMAKE_CURRENT_FUNCTION_LIST_FILE - /variable/CMAKE_CURRENT_FUNCTION_LIST_LINE - /variable/CMAKE_CURRENT_LIST_DIR - /variable/CMAKE_CURRENT_LIST_FILE - /variable/CMAKE_CURRENT_LIST_LINE - /variable/CMAKE_CURRENT_SOURCE_DIR - /variable/CMAKE_DEBUG_TARGET_PROPERTIES - /variable/CMAKE_DIRECTORY_LABELS - /variable/CMAKE_DL_LIBS - /variable/CMAKE_DOTNET_TARGET_FRAMEWORK - /variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION - /variable/CMAKE_EDIT_COMMAND - /variable/CMAKE_EXECUTABLE_SUFFIX - /variable/CMAKE_EXTRA_GENERATOR - /variable/CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES - /variable/CMAKE_FIND_DEBUG_MODE - /variable/CMAKE_FIND_PACKAGE_NAME - /variable/CMAKE_FIND_PACKAGE_SORT_DIRECTION - /variable/CMAKE_FIND_PACKAGE_SORT_ORDER - /variable/CMAKE_GENERATOR - /variable/CMAKE_GENERATOR_INSTANCE - /variable/CMAKE_GENERATOR_PLATFORM - /variable/CMAKE_GENERATOR_TOOLSET - /variable/CMAKE_IMPORT_LIBRARY_PREFIX - /variable/CMAKE_IMPORT_LIBRARY_SUFFIX - /variable/CMAKE_JOB_POOL_COMPILE - /variable/CMAKE_JOB_POOL_LINK - /variable/CMAKE_JOB_POOL_PRECOMPILE_HEADER - /variable/CMAKE_JOB_POOLS - /variable/CMAKE_LANG_COMPILER_AR - /variable/CMAKE_LANG_COMPILER_RANLIB - /variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX - /variable/CMAKE_LINK_LIBRARY_SUFFIX - /variable/CMAKE_LINK_SEARCH_END_STATIC - /variable/CMAKE_LINK_SEARCH_START_STATIC - /variable/CMAKE_MAJOR_VERSION - /variable/CMAKE_MAKE_PROGRAM - /variable/CMAKE_MATCH_COUNT - /variable/CMAKE_MATCH_n - /variable/CMAKE_MINIMUM_REQUIRED_VERSION - /variable/CMAKE_MINOR_VERSION - /variable/CMAKE_NETRC - /variable/CMAKE_NETRC_FILE - /variable/CMAKE_PARENT_LIST_FILE - /variable/CMAKE_PATCH_VERSION - /variable/CMAKE_PROJECT_DESCRIPTION - /variable/CMAKE_PROJECT_HOMEPAGE_URL - /variable/CMAKE_PROJECT_NAME - /variable/CMAKE_PROJECT_VERSION - /variable/CMAKE_PROJECT_VERSION_MAJOR - /variable/CMAKE_PROJECT_VERSION_MINOR - /variable/CMAKE_PROJECT_VERSION_PATCH - /variable/CMAKE_PROJECT_VERSION_TWEAK - /variable/CMAKE_RANLIB - /variable/CMAKE_ROOT - /variable/CMAKE_RULE_MESSAGES - /variable/CMAKE_SCRIPT_MODE_FILE - /variable/CMAKE_SHARED_LIBRARY_PREFIX - /variable/CMAKE_SHARED_LIBRARY_SUFFIX - /variable/CMAKE_SHARED_MODULE_PREFIX - /variable/CMAKE_SHARED_MODULE_SUFFIX - /variable/CMAKE_SIZEOF_VOID_P - /variable/CMAKE_SKIP_INSTALL_RULES - /variable/CMAKE_SKIP_RPATH - /variable/CMAKE_SOURCE_DIR - /variable/CMAKE_STATIC_LIBRARY_PREFIX - /variable/CMAKE_STATIC_LIBRARY_SUFFIX - /variable/CMAKE_Swift_MODULE_DIRECTORY - /variable/CMAKE_Swift_NUM_THREADS - /variable/CMAKE_TOOLCHAIN_FILE - /variable/CMAKE_TWEAK_VERSION - /variable/CMAKE_VERBOSE_MAKEFILE - /variable/CMAKE_VERSION - /variable/CMAKE_VS_DEVENV_COMMAND - /variable/CMAKE_VS_MSBUILD_COMMAND - /variable/CMAKE_VS_NsightTegra_VERSION - /variable/CMAKE_VS_PLATFORM_NAME - /variable/CMAKE_VS_PLATFORM_NAME_DEFAULT - /variable/CMAKE_VS_PLATFORM_TOOLSET - /variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA - /variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR - /variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE - /variable/CMAKE_VS_PLATFORM_TOOLSET_VERSION - /variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION - /variable/CMAKE_XCODE_GENERATE_SCHEME - /variable/CMAKE_XCODE_PLATFORM_TOOLSET - /variable/PROJECT-NAME_BINARY_DIR - /variable/PROJECT-NAME_DESCRIPTION - /variable/PROJECT-NAME_HOMEPAGE_URL - /variable/PROJECT-NAME_SOURCE_DIR - /variable/PROJECT-NAME_VERSION - /variable/PROJECT-NAME_VERSION_MAJOR - /variable/PROJECT-NAME_VERSION_MINOR - /variable/PROJECT-NAME_VERSION_PATCH - /variable/PROJECT-NAME_VERSION_TWEAK - /variable/PROJECT_BINARY_DIR - /variable/PROJECT_DESCRIPTION - /variable/PROJECT_HOMEPAGE_URL - /variable/PROJECT_NAME - /variable/PROJECT_SOURCE_DIR - /variable/PROJECT_VERSION - /variable/PROJECT_VERSION_MAJOR - /variable/PROJECT_VERSION_MINOR - /variable/PROJECT_VERSION_PATCH - /variable/PROJECT_VERSION_TWEAK - -Variables that Change Behavior -============================== - -.. toctree:: - :maxdepth: 1 - - /variable/BUILD_SHARED_LIBS - /variable/CMAKE_ABSOLUTE_DESTINATION_FILES - /variable/CMAKE_APPBUNDLE_PATH - /variable/CMAKE_AUTOMOC_RELAXED_MODE - /variable/CMAKE_BACKWARDS_COMPATIBILITY - /variable/CMAKE_BUILD_TYPE - /variable/CMAKE_CODEBLOCKS_COMPILER_ID - /variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES - /variable/CMAKE_CODELITE_USE_TARGETS - /variable/CMAKE_COLOR_MAKEFILE - /variable/CMAKE_CONFIGURATION_TYPES - /variable/CMAKE_DEPENDS_IN_PROJECT_ONLY - /variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName - /variable/CMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES - /variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT - /variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS - /variable/CMAKE_ECLIPSE_RESOURCE_ENCODING - /variable/CMAKE_ECLIPSE_VERSION - /variable/CMAKE_ERROR_DEPRECATED - /variable/CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION - /variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO - /variable/CMAKE_EXPORT_COMPILE_COMMANDS - /variable/CMAKE_EXPORT_PACKAGE_REGISTRY - /variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY - /variable/CMAKE_FIND_APPBUNDLE - /variable/CMAKE_FIND_FRAMEWORK - /variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX - /variable/CMAKE_FIND_LIBRARY_PREFIXES - /variable/CMAKE_FIND_LIBRARY_SUFFIXES - /variable/CMAKE_FIND_NO_INSTALL_PREFIX - /variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY - /variable/CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY - /variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG - /variable/CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS - /variable/CMAKE_FIND_PACKAGE_WARN_NO_MODULE - /variable/CMAKE_FIND_ROOT_PATH - /variable/CMAKE_FIND_ROOT_PATH_MODE_INCLUDE - /variable/CMAKE_FIND_ROOT_PATH_MODE_LIBRARY - /variable/CMAKE_FIND_ROOT_PATH_MODE_PACKAGE - /variable/CMAKE_FIND_ROOT_PATH_MODE_PROGRAM - /variable/CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH - /variable/CMAKE_FIND_USE_CMAKE_PATH - /variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH - /variable/CMAKE_FIND_USE_PACKAGE_REGISTRY - /variable/CMAKE_FIND_USE_PACKAGE_ROOT_PATH - /variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH - /variable/CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY - /variable/CMAKE_FRAMEWORK_PATH - /variable/CMAKE_IGNORE_PATH - /variable/CMAKE_INCLUDE_DIRECTORIES_BEFORE - /variable/CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE - /variable/CMAKE_INCLUDE_PATH - /variable/CMAKE_INSTALL_DEFAULT_COMPONENT_NAME - /variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS - /variable/CMAKE_INSTALL_MESSAGE - /variable/CMAKE_INSTALL_PREFIX - /variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT - /variable/CMAKE_LIBRARY_PATH - /variable/CMAKE_LINK_DIRECTORIES_BEFORE - /variable/CMAKE_MFC_FLAG - /variable/CMAKE_MAXIMUM_RECURSION_DEPTH - /variable/CMAKE_MESSAGE_CONTEXT - /variable/CMAKE_MESSAGE_CONTEXT_SHOW - /variable/CMAKE_MESSAGE_INDENT - /variable/CMAKE_MESSAGE_LOG_LEVEL - /variable/CMAKE_MODULE_PATH - /variable/CMAKE_POLICY_DEFAULT_CMPNNNN - /variable/CMAKE_POLICY_WARNING_CMPNNNN - /variable/CMAKE_PREFIX_PATH - /variable/CMAKE_PROGRAM_PATH - /variable/CMAKE_PROJECT_INCLUDE - /variable/CMAKE_PROJECT_INCLUDE_BEFORE - /variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE - /variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE - /variable/CMAKE_SKIP_INSTALL_ALL_DEPENDENCY - /variable/CMAKE_STAGING_PREFIX - /variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS - /variable/CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE - /variable/CMAKE_SUPPRESS_REGENERATION - /variable/CMAKE_SYSROOT - /variable/CMAKE_SYSROOT_COMPILE - /variable/CMAKE_SYSROOT_LINK - /variable/CMAKE_SYSTEM_APPBUNDLE_PATH - /variable/CMAKE_SYSTEM_FRAMEWORK_PATH - /variable/CMAKE_SYSTEM_IGNORE_PATH - /variable/CMAKE_SYSTEM_INCLUDE_PATH - /variable/CMAKE_SYSTEM_LIBRARY_PATH - /variable/CMAKE_SYSTEM_PREFIX_PATH - /variable/CMAKE_SYSTEM_PROGRAM_PATH - /variable/CMAKE_USER_MAKE_RULES_OVERRIDE - /variable/CMAKE_WARN_DEPRECATED - /variable/CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION - /variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY - /variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER - /variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN - /variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING - /variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER - /variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS - /variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE - /variable/CMAKE_XCODE_SCHEME_ENVIRONMENT - /variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC - /variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP - /variable/CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES - /variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE - /variable/CMAKE_XCODE_SCHEME_MALLOC_STACK - /variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER - /variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP - /variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER - /variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP - /variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY - /variable/CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS - /variable/PackageName_ROOT - -Variables that Describe the System -================================== - -.. toctree:: - :maxdepth: 1 - - /variable/ANDROID - /variable/APPLE - /variable/BORLAND - /variable/CMAKE_CL_64 - /variable/CMAKE_COMPILER_2005 - /variable/CMAKE_HOST_APPLE - /variable/CMAKE_HOST_SOLARIS - /variable/CMAKE_HOST_SYSTEM - /variable/CMAKE_HOST_SYSTEM_NAME - /variable/CMAKE_HOST_SYSTEM_PROCESSOR - /variable/CMAKE_HOST_SYSTEM_VERSION - /variable/CMAKE_HOST_UNIX - /variable/CMAKE_HOST_WIN32 - /variable/CMAKE_LIBRARY_ARCHITECTURE - /variable/CMAKE_LIBRARY_ARCHITECTURE_REGEX - /variable/CMAKE_OBJECT_PATH_MAX - /variable/CMAKE_SYSTEM - /variable/CMAKE_SYSTEM_NAME - /variable/CMAKE_SYSTEM_PROCESSOR - /variable/CMAKE_SYSTEM_VERSION - /variable/CYGWIN - /variable/GHS-MULTI - /variable/IOS - /variable/MINGW - /variable/MSVC - /variable/MSVC10 - /variable/MSVC11 - /variable/MSVC12 - /variable/MSVC14 - /variable/MSVC60 - /variable/MSVC70 - /variable/MSVC71 - /variable/MSVC80 - /variable/MSVC90 - /variable/MSVC_IDE - /variable/MSVC_TOOLSET_VERSION - /variable/MSVC_VERSION - /variable/MSYS - /variable/UNIX - /variable/WIN32 - /variable/WINCE - /variable/WINDOWS_PHONE - /variable/WINDOWS_STORE - /variable/XCODE - /variable/XCODE_VERSION - -Variables that Control the Build -================================ - -.. toctree:: - :maxdepth: 1 - - /variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS - /variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS - /variable/CMAKE_ANDROID_API - /variable/CMAKE_ANDROID_API_MIN - /variable/CMAKE_ANDROID_ARCH - /variable/CMAKE_ANDROID_ARCH_ABI - /variable/CMAKE_ANDROID_ARM_MODE - /variable/CMAKE_ANDROID_ARM_NEON - /variable/CMAKE_ANDROID_ASSETS_DIRECTORIES - /variable/CMAKE_ANDROID_EXCEPTIONS - /variable/CMAKE_ANDROID_GUI - /variable/CMAKE_ANDROID_JAR_DEPENDENCIES - /variable/CMAKE_ANDROID_JAR_DIRECTORIES - /variable/CMAKE_ANDROID_JAVA_SOURCE_DIR - /variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES - /variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES - /variable/CMAKE_ANDROID_NDK - /variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS - /variable/CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG - /variable/CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION - /variable/CMAKE_ANDROID_PROCESS_MAX - /variable/CMAKE_ANDROID_PROGUARD - /variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH - /variable/CMAKE_ANDROID_RTTI - /variable/CMAKE_ANDROID_SECURE_PROPS_PATH - /variable/CMAKE_ANDROID_SKIP_ANT_STEP - /variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN - /variable/CMAKE_ANDROID_STL_TYPE - /variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY - /variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG - /variable/CMAKE_AUTOGEN_ORIGIN_DEPENDS - /variable/CMAKE_AUTOGEN_PARALLEL - /variable/CMAKE_AUTOGEN_VERBOSE - /variable/CMAKE_AUTOMOC - /variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES - /variable/CMAKE_AUTOMOC_DEPEND_FILTERS - /variable/CMAKE_AUTOMOC_MACRO_NAMES - /variable/CMAKE_AUTOMOC_MOC_OPTIONS - /variable/CMAKE_AUTOMOC_PATH_PREFIX - /variable/CMAKE_AUTORCC - /variable/CMAKE_AUTORCC_OPTIONS - /variable/CMAKE_AUTOUIC - /variable/CMAKE_AUTOUIC_OPTIONS - /variable/CMAKE_AUTOUIC_SEARCH_PATHS - /variable/CMAKE_BUILD_RPATH - /variable/CMAKE_BUILD_RPATH_USE_ORIGIN - /variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR - /variable/CMAKE_BUILD_WITH_INSTALL_RPATH - /variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY - /variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG - /variable/CMAKE_CONFIG_POSTFIX - /variable/CMAKE_CROSS_CONFIGS - /variable/CMAKE_CTEST_ARGUMENTS - /variable/CMAKE_CUDA_SEPARABLE_COMPILATION - /variable/CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS - /variable/CMAKE_CUDA_RUNTIME_LIBRARY - /variable/CMAKE_DEBUG_POSTFIX - /variable/CMAKE_DEFAULT_BUILD_TYPE - /variable/CMAKE_DEFAULT_CONFIGS - /variable/CMAKE_DISABLE_PRECOMPILE_HEADERS - /variable/CMAKE_ENABLE_EXPORTS - /variable/CMAKE_EXE_LINKER_FLAGS - /variable/CMAKE_EXE_LINKER_FLAGS_CONFIG - /variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT - /variable/CMAKE_EXE_LINKER_FLAGS_INIT - /variable/CMAKE_FOLDER - /variable/CMAKE_FRAMEWORK - /variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG - /variable/CMAKE_Fortran_FORMAT - /variable/CMAKE_Fortran_MODULE_DIRECTORY - /variable/CMAKE_Fortran_PREPROCESS - /variable/CMAKE_GHS_NO_SOURCE_GROUP_FILE - /variable/CMAKE_GLOBAL_AUTOGEN_TARGET - /variable/CMAKE_GLOBAL_AUTOGEN_TARGET_NAME - /variable/CMAKE_GLOBAL_AUTORCC_TARGET - /variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME - /variable/CMAKE_GNUtoMS - /variable/CMAKE_INCLUDE_CURRENT_DIR - /variable/CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE - /variable/CMAKE_INSTALL_NAME_DIR - /variable/CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH - /variable/CMAKE_INSTALL_RPATH - /variable/CMAKE_INSTALL_RPATH_USE_LINK_PATH - /variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION - /variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION_CONFIG - /variable/CMAKE_IOS_INSTALL_COMBINED - /variable/CMAKE_LANG_CLANG_TIDY - /variable/CMAKE_LANG_COMPILER_LAUNCHER - /variable/CMAKE_LANG_CPPCHECK - /variable/CMAKE_LANG_CPPLINT - /variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE - /variable/CMAKE_LANG_LINK_LIBRARY_FILE_FLAG - /variable/CMAKE_LANG_LINK_LIBRARY_FLAG - /variable/CMAKE_LANG_VISIBILITY_PRESET - /variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY - /variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG - /variable/CMAKE_LIBRARY_PATH_FLAG - /variable/CMAKE_LINK_DEF_FILE_FLAG - /variable/CMAKE_LINK_DEPENDS_NO_SHARED - /variable/CMAKE_LINK_INTERFACE_LIBRARIES - /variable/CMAKE_LINK_LIBRARY_FILE_FLAG - /variable/CMAKE_LINK_LIBRARY_FLAG - /variable/CMAKE_LINK_WHAT_YOU_USE - /variable/CMAKE_MACOSX_BUNDLE - /variable/CMAKE_MACOSX_RPATH - /variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG - /variable/CMAKE_MODULE_LINKER_FLAGS - /variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG - /variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT - /variable/CMAKE_MODULE_LINKER_FLAGS_INIT - /variable/CMAKE_MSVCIDE_RUN_PATH - /variable/CMAKE_MSVC_RUNTIME_LIBRARY - /variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX - /variable/CMAKE_NO_BUILTIN_CHRPATH - /variable/CMAKE_NO_SYSTEM_FROM_IMPORTED - /variable/CMAKE_OSX_ARCHITECTURES - /variable/CMAKE_OSX_DEPLOYMENT_TARGET - /variable/CMAKE_OSX_SYSROOT - /variable/CMAKE_PCH_WARN_INVALID - /variable/CMAKE_PDB_OUTPUT_DIRECTORY - /variable/CMAKE_PDB_OUTPUT_DIRECTORY_CONFIG - /variable/CMAKE_POSITION_INDEPENDENT_CODE - /variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY - /variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG - /variable/CMAKE_SHARED_LINKER_FLAGS - /variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG - /variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT - /variable/CMAKE_SHARED_LINKER_FLAGS_INIT - /variable/CMAKE_SKIP_BUILD_RPATH - /variable/CMAKE_SKIP_INSTALL_RPATH - /variable/CMAKE_STATIC_LINKER_FLAGS - /variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG - /variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT - /variable/CMAKE_STATIC_LINKER_FLAGS_INIT - /variable/CMAKE_TRY_COMPILE_CONFIGURATION - /variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES - /variable/CMAKE_TRY_COMPILE_TARGET_TYPE - /variable/CMAKE_UNITY_BUILD - /variable/CMAKE_UNITY_BUILD_BATCH_SIZE - /variable/CMAKE_USE_RELATIVE_PATHS - /variable/CMAKE_VISIBILITY_INLINES_HIDDEN - /variable/CMAKE_VS_GLOBALS - /variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD - /variable/CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD - /variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING - /variable/CMAKE_VS_SDK_EXCLUDE_DIRECTORIES - /variable/CMAKE_VS_SDK_EXECUTABLE_DIRECTORIES - /variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES - /variable/CMAKE_VS_SDK_LIBRARY_DIRECTORIES - /variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES - /variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES - /variable/CMAKE_VS_SDK_SOURCE_DIRECTORIES - /variable/CMAKE_VS_WINRT_BY_DEFAULT - /variable/CMAKE_WIN32_EXECUTABLE - /variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS - /variable/CMAKE_XCODE_ATTRIBUTE_an-attribute - /variable/EXECUTABLE_OUTPUT_PATH - /variable/LIBRARY_OUTPUT_PATH - -Variables for Languages -======================= - -.. toctree:: - :maxdepth: 1 - - /variable/CMAKE_COMPILER_IS_GNUCC - /variable/CMAKE_COMPILER_IS_GNUCXX - /variable/CMAKE_COMPILER_IS_GNUG77 - /variable/CMAKE_CUDA_ARCHITECTURES - /variable/CMAKE_CUDA_COMPILE_FEATURES - /variable/CMAKE_CUDA_HOST_COMPILER - /variable/CMAKE_CUDA_EXTENSIONS - /variable/CMAKE_CUDA_STANDARD - /variable/CMAKE_CUDA_STANDARD_REQUIRED - /variable/CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES - /variable/CMAKE_CXX_COMPILE_FEATURES - /variable/CMAKE_CXX_EXTENSIONS - /variable/CMAKE_CXX_STANDARD - /variable/CMAKE_CXX_STANDARD_REQUIRED - /variable/CMAKE_C_COMPILE_FEATURES - /variable/CMAKE_C_EXTENSIONS - /variable/CMAKE_C_STANDARD - /variable/CMAKE_C_STANDARD_REQUIRED - /variable/CMAKE_Fortran_MODDIR_DEFAULT - /variable/CMAKE_Fortran_MODDIR_FLAG - /variable/CMAKE_Fortran_MODOUT_FLAG - /variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE - /variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX - /variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX - /variable/CMAKE_LANG_ARCHIVE_APPEND - /variable/CMAKE_LANG_ARCHIVE_CREATE - /variable/CMAKE_LANG_ARCHIVE_FINISH - /variable/CMAKE_LANG_COMPILER - /variable/CMAKE_LANG_COMPILER_EXTERNAL_TOOLCHAIN - /variable/CMAKE_LANG_COMPILER_ID - /variable/CMAKE_LANG_COMPILER_LOADED - /variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND - /variable/CMAKE_LANG_COMPILER_TARGET - /variable/CMAKE_LANG_COMPILER_VERSION - /variable/CMAKE_LANG_COMPILE_OBJECT - /variable/CMAKE_LANG_CREATE_SHARED_LIBRARY - /variable/CMAKE_LANG_CREATE_SHARED_MODULE - /variable/CMAKE_LANG_CREATE_STATIC_LIBRARY - /variable/CMAKE_LANG_FLAGS - /variable/CMAKE_LANG_FLAGS_CONFIG - /variable/CMAKE_LANG_FLAGS_CONFIG_INIT - /variable/CMAKE_LANG_FLAGS_DEBUG - /variable/CMAKE_LANG_FLAGS_DEBUG_INIT - /variable/CMAKE_LANG_FLAGS_INIT - /variable/CMAKE_LANG_FLAGS_MINSIZEREL - /variable/CMAKE_LANG_FLAGS_MINSIZEREL_INIT - /variable/CMAKE_LANG_FLAGS_RELEASE - /variable/CMAKE_LANG_FLAGS_RELEASE_INIT - /variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO - /variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO_INIT - /variable/CMAKE_LANG_IGNORE_EXTENSIONS - /variable/CMAKE_LANG_IMPLICIT_INCLUDE_DIRECTORIES - /variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES - /variable/CMAKE_LANG_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES - /variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES - /variable/CMAKE_LANG_LIBRARY_ARCHITECTURE - /variable/CMAKE_LANG_LINKER_PREFERENCE - /variable/CMAKE_LANG_LINKER_PREFERENCE_PROPAGATES - /variable/CMAKE_LANG_LINKER_WRAPPER_FLAG - /variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP - /variable/CMAKE_LANG_LINK_EXECUTABLE - /variable/CMAKE_LANG_OUTPUT_EXTENSION - /variable/CMAKE_LANG_SIMULATE_ID - /variable/CMAKE_LANG_SIMULATE_VERSION - /variable/CMAKE_LANG_SIZEOF_DATA_PTR - /variable/CMAKE_LANG_SOURCE_FILE_EXTENSIONS - /variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES - /variable/CMAKE_LANG_STANDARD_LIBRARIES - /variable/CMAKE_OBJC_EXTENSIONS - /variable/CMAKE_OBJC_STANDARD - /variable/CMAKE_OBJC_STANDARD_REQUIRED - /variable/CMAKE_OBJCXX_EXTENSIONS - /variable/CMAKE_OBJCXX_STANDARD - /variable/CMAKE_OBJCXX_STANDARD_REQUIRED - /variable/CMAKE_Swift_LANGUAGE_VERSION - /variable/CMAKE_USER_MAKE_RULES_OVERRIDE_LANG - -Variables for CTest -=================== - -.. toctree:: - :maxdepth: 1 - - /variable/CTEST_BINARY_DIRECTORY - /variable/CTEST_BUILD_COMMAND - /variable/CTEST_BUILD_NAME - /variable/CTEST_BZR_COMMAND - /variable/CTEST_BZR_UPDATE_OPTIONS - /variable/CTEST_CHANGE_ID - /variable/CTEST_CHECKOUT_COMMAND - /variable/CTEST_CONFIGURATION_TYPE - /variable/CTEST_CONFIGURE_COMMAND - /variable/CTEST_COVERAGE_COMMAND - /variable/CTEST_COVERAGE_EXTRA_FLAGS - /variable/CTEST_CURL_OPTIONS - /variable/CTEST_CUSTOM_COVERAGE_EXCLUDE - /variable/CTEST_CUSTOM_ERROR_EXCEPTION - /variable/CTEST_CUSTOM_ERROR_MATCH - /variable/CTEST_CUSTOM_ERROR_POST_CONTEXT - /variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT - /variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE - /variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS - /variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS - /variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE - /variable/CTEST_CUSTOM_MEMCHECK_IGNORE - /variable/CTEST_CUSTOM_POST_MEMCHECK - /variable/CTEST_CUSTOM_POST_TEST - /variable/CTEST_CUSTOM_PRE_MEMCHECK - /variable/CTEST_CUSTOM_PRE_TEST - /variable/CTEST_CUSTOM_TESTS_IGNORE - /variable/CTEST_CUSTOM_WARNING_EXCEPTION - /variable/CTEST_CUSTOM_WARNING_MATCH - /variable/CTEST_CVS_CHECKOUT - /variable/CTEST_CVS_COMMAND - /variable/CTEST_CVS_UPDATE_OPTIONS - /variable/CTEST_DROP_LOCATION - /variable/CTEST_DROP_METHOD - /variable/CTEST_DROP_SITE - /variable/CTEST_DROP_SITE_CDASH - /variable/CTEST_DROP_SITE_PASSWORD - /variable/CTEST_DROP_SITE_USER - /variable/CTEST_EXTRA_COVERAGE_GLOB - /variable/CTEST_GIT_COMMAND - /variable/CTEST_GIT_INIT_SUBMODULES - /variable/CTEST_GIT_UPDATE_CUSTOM - /variable/CTEST_GIT_UPDATE_OPTIONS - /variable/CTEST_HG_COMMAND - /variable/CTEST_HG_UPDATE_OPTIONS - /variable/CTEST_LABELS_FOR_SUBPROJECTS - /variable/CTEST_MEMORYCHECK_COMMAND - /variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS - /variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS - /variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE - /variable/CTEST_MEMORYCHECK_TYPE - /variable/CTEST_NIGHTLY_START_TIME - /variable/CTEST_P4_CLIENT - /variable/CTEST_P4_COMMAND - /variable/CTEST_P4_OPTIONS - /variable/CTEST_P4_UPDATE_OPTIONS - /variable/CTEST_RESOURCE_SPEC_FILE - /variable/CTEST_RUN_CURRENT_SCRIPT - /variable/CTEST_SCP_COMMAND - /variable/CTEST_SITE - /variable/CTEST_SUBMIT_URL - /variable/CTEST_SOURCE_DIRECTORY - /variable/CTEST_SVN_COMMAND - /variable/CTEST_SVN_OPTIONS - /variable/CTEST_SVN_UPDATE_OPTIONS - /variable/CTEST_TEST_LOAD - /variable/CTEST_TEST_TIMEOUT - /variable/CTEST_TRIGGER_SITE - /variable/CTEST_UPDATE_COMMAND - /variable/CTEST_UPDATE_OPTIONS - /variable/CTEST_UPDATE_VERSION_ONLY - /variable/CTEST_UPDATE_VERSION_OVERRIDE - /variable/CTEST_USE_LAUNCHERS - -Variables for CPack -=================== - -.. toctree:: - :maxdepth: 1 - - /variable/CPACK_ABSOLUTE_DESTINATION_FILES - /variable/CPACK_COMPONENT_INCLUDE_TOPLEVEL_DIRECTORY - /variable/CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION - /variable/CPACK_INCLUDE_TOPLEVEL_DIRECTORY - /variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS - /variable/CPACK_PACKAGING_INSTALL_PREFIX - /variable/CPACK_SET_DESTDIR - /variable/CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION - -Variable Expansion Operators -============================ - -.. toctree:: - :maxdepth: 1 - - /variable/CACHE - /variable/ENV - -Internal Variables -================== - -CMake has many internal variables. Most of them are undocumented. -Some of them, however, were at some point described as normal -variables, and therefore may be encountered in legacy code. They -are subject to change, and not recommended for use in project code. - -.. toctree:: - :maxdepth: 1 - - /variable/CMAKE_HOME_DIRECTORY - /variable/CMAKE_INTERNAL_PLATFORM_ABI - /variable/CMAKE_LANG_COMPILER_ABI - /variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID - /variable/CMAKE_LANG_COMPILER_VERSION_INTERNAL - /variable/CMAKE_LANG_PLATFORM_ID - /variable/CMAKE_NOT_USING_CONFIG_FLAGS - /variable/CMAKE_VS_INTEL_Fortran_PROJECT_VERSION
diff --git a/share/cmake-3.18/Help/manual/cmake.1.rst b/share/cmake-3.18/Help/manual/cmake.1.rst deleted file mode 100644 index 9becfc6..0000000 --- a/share/cmake-3.18/Help/manual/cmake.1.rst +++ /dev/null
@@ -1,804 +0,0 @@ -.. cmake-manual-description: CMake Command-Line Reference - -cmake(1) -******** - -Synopsis -======== - -.. parsed-literal:: - - `Generate a Project Buildsystem`_ - cmake [<options>] <path-to-source> - cmake [<options>] <path-to-existing-build> - cmake [<options>] -S <path-to-source> -B <path-to-build> - - `Build a Project`_ - cmake --build <dir> [<options>] [-- <build-tool-options>] - - `Install a Project`_ - cmake --install <dir> [<options>] - - `Open a Project`_ - cmake --open <dir> - - `Run a Script`_ - cmake [{-D <var>=<value>}...] -P <cmake-script-file> - - `Run a Command-Line Tool`_ - cmake -E <command> [<options>] - - `Run the Find-Package Tool`_ - cmake --find-package [<options>] - - `View Help`_ - cmake --help[-<topic>] - -Description -=========== - -The **cmake** executable is the command-line interface of the cross-platform -buildsystem generator CMake. The above `Synopsis`_ lists various actions -the tool can perform as described in sections below. - -To build a software project with CMake, `Generate a Project Buildsystem`_. -Optionally use **cmake** to `Build a Project`_, `Install a Project`_ or just -run the corresponding build tool (e.g. ``make``) directly. **cmake** can also -be used to `View Help`_. - -The other actions are meant for use by software developers writing -scripts in the :manual:`CMake language <cmake-language(7)>` to support -their builds. - -For graphical user interfaces that may be used in place of **cmake**, -see :manual:`ccmake <ccmake(1)>` and :manual:`cmake-gui <cmake-gui(1)>`. -For command-line interfaces to the CMake testing and packaging facilities, -see :manual:`ctest <ctest(1)>` and :manual:`cpack <cpack(1)>`. - -For more information on CMake at large, `see also`_ the links at the end -of this manual. - - -Introduction to CMake Buildsystems -================================== - -A *buildsystem* describes how to build a project's executables and libraries -from its source code using a *build tool* to automate the process. For -example, a buildsystem may be a ``Makefile`` for use with a command-line -``make`` tool or a project file for an Integrated Development Environment -(IDE). In order to avoid maintaining multiple such buildsystems, a project -may specify its buildsystem abstractly using files written in the -:manual:`CMake language <cmake-language(7)>`. From these files CMake -generates a preferred buildsystem locally for each user through a backend -called a *generator*. - -To generate a buildsystem with CMake, the following must be selected: - -Source Tree - The top-level directory containing source files provided by the project. - The project specifies its buildsystem using files as described in the - :manual:`cmake-language(7)` manual, starting with a top-level file named - ``CMakeLists.txt``. These files specify build targets and their - dependencies as described in the :manual:`cmake-buildsystem(7)` manual. - -Build Tree - The top-level directory in which buildsystem files and build output - artifacts (e.g. executables and libraries) are to be stored. - CMake will write a ``CMakeCache.txt`` file to identify the directory - as a build tree and store persistent information such as buildsystem - configuration options. - - To maintain a pristine source tree, perform an *out-of-source* build - by using a separate dedicated build tree. An *in-source* build in - which the build tree is placed in the same directory as the source - tree is also supported, but discouraged. - -Generator - This chooses the kind of buildsystem to generate. See the - :manual:`cmake-generators(7)` manual for documentation of all generators. - Run ``cmake --help`` to see a list of generators available locally. - Optionally use the ``-G`` option below to specify a generator, or simply - accept the default CMake chooses for the current platform. - - When using one of the :ref:`Command-Line Build Tool Generators` - CMake expects that the environment needed by the compiler toolchain - is already configured in the shell. When using one of the - :ref:`IDE Build Tool Generators`, no particular environment is needed. - - -Generate a Project Buildsystem -============================== - -Run CMake with one of the following command signatures to specify the -source and build trees and generate a buildsystem: - -``cmake [<options>] <path-to-source>`` - Uses the current working directory as the build tree, and - ``<path-to-source>`` as the source tree. The specified path may - be absolute or relative to the current working directory. - The source tree must contain a ``CMakeLists.txt`` file and must - *not* contain a ``CMakeCache.txt`` file because the latter - identifies an existing build tree. For example: - - .. code-block:: console - - $ mkdir build ; cd build - $ cmake ../src - -``cmake [<options>] <path-to-existing-build>`` - Uses ``<path-to-existing-build>`` as the build tree, and loads the - path to the source tree from its ``CMakeCache.txt`` file, which must - have already been generated by a previous run of CMake. The specified - path may be absolute or relative to the current working directory. - For example: - - .. code-block:: console - - $ cd build - $ cmake . - -``cmake [<options>] -S <path-to-source> -B <path-to-build>`` - Uses ``<path-to-build>`` as the build tree and ``<path-to-source>`` - as the source tree. The specified paths may be absolute or relative - to the current working directory. The source tree must contain a - ``CMakeLists.txt`` file. The build tree will be created automatically - if it does not already exist. For example: - - .. code-block:: console - - $ cmake -S src -B build - -In all cases the ``<options>`` may be zero or more of the `Options`_ below. - -After generating a buildsystem one may use the corresponding native -build tool to build the project. For example, after using the -:generator:`Unix Makefiles` generator one may run ``make`` directly: - - .. code-block:: console - - $ make - $ make install - -Alternatively, one may use **cmake** to `Build a Project`_ by -automatically choosing and invoking the appropriate native build tool. - -.. _`CMake Options`: - -Options -------- - -.. include:: OPTIONS_BUILD.txt - -``-L[A][H]`` - List non-advanced cached variables. - - List ``CACHE`` variables will run CMake and list all the variables from - the CMake ``CACHE`` that are not marked as ``INTERNAL`` or :prop_cache:`ADVANCED`. - This will effectively display current CMake settings, which can then be - changed with ``-D`` option. Changing some of the variables may result - in more variables being created. If ``A`` is specified, then it will - display also advanced variables. If ``H`` is specified, it will also - display help for each variable. - -``-N`` - View mode only. - - Only load the cache. Do not actually run configure and generate - steps. - -``--graphviz=[file]`` - Generate graphviz of dependencies, see :module:`CMakeGraphVizOptions` for more. - - Generate a graphviz input file that will contain all the library and - executable dependencies in the project. See the documentation for - :module:`CMakeGraphVizOptions` for more details. - -``--system-information [file]`` - Dump information about this system. - - Dump a wide range of information about the current system. If run - from the top of a binary tree for a CMake project it will dump - additional information such as the cache, log files etc. - -``--log-level=<ERROR|WARNING|NOTICE|STATUS|VERBOSE|DEBUG|TRACE>`` - Set the log level. - - The :command:`message` command will only output messages of the specified - log level or higher. The default log level is ``STATUS``. - - To make a log level persist between CMake runs, set - :variable:`CMAKE_MESSAGE_LOG_LEVEL` as a cache variable instead. - If both the command line option and the variable are given, the command line - option takes precedence. - - For backward compatibility reasons, ``--loglevel`` is also accepted as a - synonym for this option. - -``--log-context`` - Enable the :command:`message` command outputting context attached to each - message. - - This option turns on showing context for the current CMake run only. - To make showing the context persistent for all subsequent CMake runs, set - :variable:`CMAKE_MESSAGE_CONTEXT_SHOW` as a cache variable instead. - When this command line option is given, :variable:`CMAKE_MESSAGE_CONTEXT_SHOW` - is ignored. - -``--debug-trycompile`` - Do not delete the :command:`try_compile` build tree. - Only useful on one :command:`try_compile` at a time. - - Do not delete the files and directories created for :command:`try_compile` - calls. This is useful in debugging failed try_compiles. It may - however change the results of the try-compiles as old junk from a - previous try-compile may cause a different test to either pass or - fail incorrectly. This option is best used for one try-compile at a - time, and only when debugging. - -``--debug-output`` - Put cmake in a debug mode. - - Print extra information during the cmake run like stack traces with - :command:`message(SEND_ERROR)` calls. - -``--debug-find`` - Put cmake find commands in a debug mode. - - Print extra find call information during the cmake run to standard - error. Output is designed for human consumption and not for parsing. - See also the :variable:`CMAKE_FIND_DEBUG_MODE` variable for debugging - a more local part of the project. - -``--trace`` - Put cmake in trace mode. - - Print a trace of all calls made and from where. - -``--trace-expand`` - Put cmake in trace mode. - - Like ``--trace``, but with variables expanded. - -``--trace-format=<format>`` - Put cmake in trace mode and sets the trace output format. - - ``<format>`` can be one of the following values. - - ``human`` - Prints each trace line in a human-readable format. This is the - default format. - - ``json-v1`` - Prints each line as a separate JSON document. Each document is - separated by a newline ( ``\n`` ). It is guaranteed that no - newline characters will be present inside a JSON document. - - JSON trace format: - - .. code-block:: json - - { - "file": "/full/path/to/the/CMake/file.txt", - "line": 0, - "cmd": "add_executable", - "args": ["foo", "bar"], - "time": 1579512535.9687231, - "frame": 2 - } - - The members are: - - ``file`` - The full path to the CMake source file where the function - was called. - - ``line`` - The line in ``file`` of the function call. - - ``cmd`` - The name of the function that was called. - - ``args`` - A string list of all function parameters. - - ``time`` - Timestamp (seconds since epoch) of the function call. - - ``frame`` - Stack frame depth of the function that was called. - - Additionally, the first JSON document outputted contains the - ``version`` key for the current major and minor version of the - - JSON trace format: - - .. code-block:: json - - { - "version": { - "major": 1, - "minor": 0 - } - } - - The members are: - - ``version`` - Indicates the version of the JSON format. The version has a - major and minor components following semantic version conventions. - -``--trace-source=<file>`` - Put cmake in trace mode, but output only lines of a specified file. - - Multiple options are allowed. - -``--trace-redirect=<file>`` - Put cmake in trace mode and redirect trace output to a file instead of stderr. - -``--warn-uninitialized`` - Warn about uninitialized values. - - Print a warning when an uninitialized variable is used. - -``--warn-unused-vars`` - Warn about unused variables. - - Find variables that are declared or set, but not used. - -``--no-warn-unused-cli`` - Don't warn about command line options. - - Don't find variables that are declared on the command line, but not - used. - -``--check-system-vars`` - Find problems with variable usage in system files. - - Normally, unused and uninitialized variables are searched for only - in :variable:`CMAKE_SOURCE_DIR` and :variable:`CMAKE_BINARY_DIR`. - This flag tells CMake to warn about other files as well. - -``--profiling-output=<path>`` - Used in conjuction with ``--profiling-format`` to output to a given path. - -``--profiling-format=<file>`` - Enable the output of profiling data of CMake script in the given format. - - This can aid performance analysis of CMake scripts executed. Third party - applications should be used to process the output into human readable format. - - Currently supported values are: - ``google-trace`` Outputs in Google Trace Format, which can be parsed by the - about:tracing tab of Google Chrome or using a plugin for a tool like Trace - Compass. - -.. _`Build Tool Mode`: - -Build a Project -=============== - -CMake provides a command-line signature to build an already-generated -project binary tree: - -.. code-block:: shell - - cmake --build <dir> [<options>] [-- <build-tool-options>] - -This abstracts a native build tool's command-line interface with the -following options: - -``--build <dir>`` - Project binary directory to be built. This is required and must be first. - -``--parallel [<jobs>], -j [<jobs>]`` - The maximum number of concurrent processes to use when building. - If ``<jobs>`` is omitted the native build tool's default number is used. - - The :envvar:`CMAKE_BUILD_PARALLEL_LEVEL` environment variable, if set, - specifies a default parallel level when this option is not given. - - Some native build tools always build in parallel. The use of ``<jobs>`` - value of ``1`` can be used to limit to a single job. - -``--target <tgt>..., -t <tgt>...`` - Build ``<tgt>`` instead of the default target. Multiple targets may be - given, separated by spaces. - -``--config <cfg>`` - For multi-configuration tools, choose configuration ``<cfg>``. - -``--clean-first`` - Build target ``clean`` first, then build. - (To clean only, use ``--target clean``.) - -``--use-stderr`` - Ignored. Behavior is default in CMake >= 3.0. - -``--verbose, -v`` - Enable verbose output - if supported - including the build commands to be - executed. - - This option can be omitted if :envvar:`VERBOSE` environment variable or - :variable:`CMAKE_VERBOSE_MAKEFILE` cached variable is set. - - -``--`` - Pass remaining options to the native tool. - -Run ``cmake --build`` with no options for quick help. - -Install a Project -================= - -CMake provides a command-line signature to install an already-generated -project binary tree: - -.. code-block:: shell - - cmake --install <dir> [<options>] - -This may be used after building a project to run installation without -using the generated build system or the native build tool. -The options are: - -``--install <dir>`` - Project binary directory to install. This is required and must be first. - -``--config <cfg>`` - For multi-configuration generators, choose configuration ``<cfg>``. - -``--component <comp>`` - Component-based install. Only install component ``<comp>``. - -``--prefix <prefix>`` - Override the installation prefix, :variable:`CMAKE_INSTALL_PREFIX`. - -``--strip`` - Strip before installing. - -``-v, --verbose`` - Enable verbose output. - - This option can be omitted if :envvar:`VERBOSE` environment variable is set. - -Run ``cmake --install`` with no options for quick help. - -Open a Project -============== - -.. code-block:: shell - - cmake --open <dir> - -Open the generated project in the associated application. This is only -supported by some generators. - - -.. _`Script Processing Mode`: - -Run a Script -============ - -.. code-block:: shell - - cmake [{-D <var>=<value>}...] -P <cmake-script-file> [-- <unparsed-options>...] - -Process the given cmake file as a script written in the CMake -language. No configure or generate step is performed and the cache -is not modified. If variables are defined using ``-D``, this must be -done before the ``-P`` argument. - -Any options after ``--`` are not parsed by CMake, but they are still included -in the set of :variable:`CMAKE_ARGV<n> <CMAKE_ARGV0>` variables passed to the -script (including the ``--`` itself). - - -Run a Command-Line Tool -======================= - -CMake provides builtin command-line tools through the signature - -.. code-block:: shell - - cmake -E <command> [<options>] - -Run ``cmake -E`` or ``cmake -E help`` for a summary of commands. -Available commands are: - -``capabilities`` - Report cmake capabilities in JSON format. The output is a JSON object - with the following keys: - - ``version`` - A JSON object with version information. Keys are: - - ``string`` - The full version string as displayed by cmake ``--version``. - ``major`` - The major version number in integer form. - ``minor`` - The minor version number in integer form. - ``patch`` - The patch level in integer form. - ``suffix`` - The cmake version suffix string. - ``isDirty`` - A bool that is set if the cmake build is from a dirty tree. - - ``generators`` - A list available generators. Each generator is a JSON object with the - following keys: - - ``name`` - A string containing the name of the generator. - ``toolsetSupport`` - ``true`` if the generator supports toolsets and ``false`` otherwise. - ``platformSupport`` - ``true`` if the generator supports platforms and ``false`` otherwise. - ``extraGenerators`` - A list of strings with all the extra generators compatible with - the generator. - - ``fileApi`` - Optional member that is present when the :manual:`cmake-file-api(7)` - is available. The value is a JSON object with one member: - - ``requests`` - A JSON array containing zero or more supported file-api requests. - Each request is a JSON object with members: - - ``kind`` - Specifies one of the supported :ref:`file-api object kinds`. - - ``version`` - A JSON array whose elements are each a JSON object containing - ``major`` and ``minor`` members specifying non-negative integer - version components. - - ``serverMode`` - ``true`` if cmake supports server-mode and ``false`` otherwise. - -``cat <files>...`` - Concatenate files and print on the standard output. - -``chdir <dir> <cmd> [<arg>...]`` - Change the current working directory and run a command. - -``compare_files [--ignore-eol] <file1> <file2>`` - Check if ``<file1>`` is same as ``<file2>``. If files are the same, - then returns ``0``, if not it returns ``1``. The ``--ignore-eol`` option - implies line-wise comparison and ignores LF/CRLF differences. - -``copy <file>... <destination>`` - Copy files to ``<destination>`` (either file or directory). - If multiple files are specified, the ``<destination>`` must be - directory and it must exist. Wildcards are not supported. - ``copy`` does follow symlinks. That means it does not copy symlinks, - but the files or directories it point to. - -``copy_directory <dir>... <destination>`` - Copy content of ``<dir>...`` directories to ``<destination>`` directory. - If ``<destination>`` directory does not exist it will be created. - ``copy_directory`` does follow symlinks. - -``copy_if_different <file>... <destination>`` - Copy files to ``<destination>`` (either file or directory) if - they have changed. - If multiple files are specified, the ``<destination>`` must be - directory and it must exist. - ``copy_if_different`` does follow symlinks. - -``create_symlink <old> <new>`` - Create a symbolic link ``<new>`` naming ``<old>``. - - .. note:: - Path to where ``<new>`` symbolic link will be created has to exist beforehand. - -``echo [<string>...]`` - Displays arguments as text. - -``echo_append [<string>...]`` - Displays arguments as text but no new line. - -``env [--unset=NAME]... [NAME=VALUE]... COMMAND [ARG]...`` - Run command in a modified environment. - -``environment`` - Display the current environment variables. - -``false`` - Do nothing, with an exit code of 1. - -``make_directory <dir>...`` - Create ``<dir>`` directories. If necessary, create parent - directories too. If a directory already exists it will be - silently ignored. - -``md5sum <file>...`` - Create MD5 checksum of files in ``md5sum`` compatible format:: - - 351abe79cd3800b38cdfb25d45015a15 file1.txt - 052f86c15bbde68af55c7f7b340ab639 file2.txt - -``sha1sum <file>...`` - Create SHA1 checksum of files in ``sha1sum`` compatible format:: - - 4bb7932a29e6f73c97bb9272f2bdc393122f86e0 file1.txt - 1df4c8f318665f9a5f2ed38f55adadb7ef9f559c file2.txt - -``sha224sum <file>...`` - Create SHA224 checksum of files in ``sha224sum`` compatible format:: - - b9b9346bc8437bbda630b0b7ddfc5ea9ca157546dbbf4c613192f930 file1.txt - 6dfbe55f4d2edc5fe5c9197bca51ceaaf824e48eba0cc453088aee24 file2.txt - -``sha256sum <file>...`` - Create SHA256 checksum of files in ``sha256sum`` compatible format:: - - 76713b23615d31680afeb0e9efe94d47d3d4229191198bb46d7485f9cb191acc file1.txt - 15b682ead6c12dedb1baf91231e1e89cfc7974b3787c1e2e01b986bffadae0ea file2.txt - -``sha384sum <file>...`` - Create SHA384 checksum of files in ``sha384sum`` compatible format:: - - acc049fedc091a22f5f2ce39a43b9057fd93c910e9afd76a6411a28a8f2b8a12c73d7129e292f94fc0329c309df49434 file1.txt - 668ddeb108710d271ee21c0f3acbd6a7517e2b78f9181c6a2ff3b8943af92b0195dcb7cce48aa3e17893173c0a39e23d file2.txt - -``sha512sum <file>...`` - Create SHA512 checksum of files in ``sha512sum`` compatible format:: - - 2a78d7a6c5328cfb1467c63beac8ff21794213901eaadafd48e7800289afbc08e5fb3e86aa31116c945ee3d7bf2a6194489ec6101051083d1108defc8e1dba89 file1.txt - 7a0b54896fe5e70cca6dd643ad6f672614b189bf26f8153061c4d219474b05dad08c4e729af9f4b009f1a1a280cb625454bf587c690f4617c27e3aebdf3b7a2d file2.txt - -``remove [-f] <file>...`` - .. deprecated:: 3.17 - - Remove the file(s). The planned behaviour was that if any of the - listed files already do not exist, the command returns a non-zero exit code, - but no message is logged. The ``-f`` option changes the behavior to return a - zero exit code (i.e. success) in such situations instead. - ``remove`` does not follow symlinks. That means it remove only symlinks - and not files it point to. - - The implementation was buggy and always returned 0. It cannot be fixed without - breaking backwards compatibility. Use ``rm`` instead. - -``remove_directory <dir>...`` - .. deprecated:: 3.17 - - Remove ``<dir>`` directories and their contents. If a directory does - not exist it will be silently ignored. If ``<dir>`` is a symlink to - a directory, just the symlink will be removed. - Use ``rm`` instead. - -``rename <oldname> <newname>`` - Rename a file or directory (on one volume). If file with the ``<newname>`` name - already exists, then it will be silently replaced. - -``rm [-rRf] <file> <dir>...`` - Remove the files ``<file>`` or directories ``dir``. - Use ``-r`` or ``-R`` to remove directories and their contents recursively. - If any of the listed files/directories do not exist, the command returns a - non-zero exit code, but no message is logged. The ``-f`` option changes - the behavior to return a zero exit code (i.e. success) in such - situations instead. - -``server`` - Launch :manual:`cmake-server(7)` mode. - -``sleep <number>...`` - Sleep for given number of seconds. - -``tar [cxt][vf][zjJ] file.tar [<options>] [--] [<pathname>...]`` - Create or extract a tar or zip archive. Options are: - - ``c`` - Create a new archive containing the specified files. - If used, the ``<pathname>...`` argument is mandatory. - ``x`` - Extract to disk from the archive. - The ``<pathname>...`` argument could be used to extract only selected files - or directories. - When extracting selected files or directories, you must provide their exact - names including the path, as printed by list (``-t``). - ``t`` - List archive contents. - The ``<pathname>...`` argument could be used to list only selected files - or directories. - ``v`` - Produce verbose output. - ``z`` - Compress the resulting archive with gzip. - ``j`` - Compress the resulting archive with bzip2. - ``J`` - Compress the resulting archive with XZ. - ``--zstd`` - Compress the resulting archive with Zstandard. - ``--files-from=<file>`` - Read file names from the given file, one per line. - Blank lines are ignored. Lines may not start in ``-`` - except for ``--add-file=<name>`` to add files whose - names start in ``-``. - ``--format=<format>`` - Specify the format of the archive to be created. - Supported formats are: ``7zip``, ``gnutar``, ``pax``, - ``paxr`` (restricted pax, default), and ``zip``. - ``--mtime=<date>`` - Specify modification time recorded in tarball entries. - ``--`` - Stop interpreting options and treat all remaining arguments - as file names, even if they start with ``-``. - - -``time <command> [<args>...]`` - Run command and display elapsed time. - -``touch <file>...`` - Creates ``<file>`` if file do not exist. - If ``<file>`` exists, it is changing ``<file>`` access and modification times. - -``touch_nocreate <file>...`` - Touch a file if it exists but do not create it. If a file does - not exist it will be silently ignored. - -``true`` - Do nothing, with an exit code of 0. - -Windows-specific Command-Line Tools ------------------------------------ - -The following ``cmake -E`` commands are available only on Windows: - -``delete_regv <key>`` - Delete Windows registry value. - -``env_vs8_wince <sdkname>`` - Displays a batch file which sets the environment for the provided - Windows CE SDK installed in VS2005. - -``env_vs9_wince <sdkname>`` - Displays a batch file which sets the environment for the provided - Windows CE SDK installed in VS2008. - -``write_regv <key> <value>`` - Write Windows registry value. - - -Run the Find-Package Tool -========================= - -CMake provides a pkg-config like helper for Makefile-based projects: - -.. code-block:: shell - - cmake --find-package [<options>] - -It searches a package using :command:`find_package()` and prints the -resulting flags to stdout. This can be used instead of pkg-config -to find installed libraries in plain Makefile-based projects or in -autoconf-based projects (via ``share/aclocal/cmake.m4``). - -.. note:: - This mode is not well-supported due to some technical limitations. - It is kept for compatibility but should not be used in new projects. - - -View Help -========= - -To print selected pages from the CMake documentation, use - -.. code-block:: shell - - cmake --help[-<topic>] - -with one of the following options: - -.. include:: OPTIONS_HELP.txt - - -See Also -======== - -.. include:: LINKS.txt
diff --git a/share/cmake-3.18/Help/manual/ctest.1.rst b/share/cmake-3.18/Help/manual/ctest.1.rst deleted file mode 100644 index d3ab75a..0000000 --- a/share/cmake-3.18/Help/manual/ctest.1.rst +++ /dev/null
@@ -1,1593 +0,0 @@ -.. cmake-manual-description: CTest Command-Line Reference - -ctest(1) -******** - -.. contents:: - -Synopsis -======== - -.. parsed-literal:: - - ctest [<options>] - ctest --build-and-test <path-to-source> <path-to-build> - --build-generator <generator> [<options>...] - [--build-options <opts>...] [--test-command <command> [<args>...]] - ctest {-D <dashboard> | -M <model> -T <action> | -S <script> | -SP <script>} - [-- <dashboard-options>...] - -Description -=========== - -The **ctest** executable is the CMake test driver program. -CMake-generated build trees created for projects that use the -:command:`enable_testing` and :command:`add_test` commands have testing support. -This program will run the tests and report results. - -Options -======= - -``-C <cfg>, --build-config <cfg>`` - Choose configuration to test. - - Some CMake-generated build trees can have multiple build - configurations in the same tree. This option can be used to specify - which one should be tested. Example configurations are ``Debug`` and - ``Release``. - -``--progress`` - Enable short progress output from tests. - - When the output of **ctest** is being sent directly to a terminal, the - progress through the set of tests is reported by updating the same line - rather than printing start and end messages for each test on new lines. - This can significantly reduce the verbosity of the test output. - Test completion messages are still output on their own line for failed - tests and the final test summary will also still be logged. - - This option can also be enabled by setting the environment variable - :envvar:`CTEST_PROGRESS_OUTPUT`. - -``-V,--verbose`` - Enable verbose output from tests. - - Test output is normally suppressed and only summary information is - displayed. This option will show all test output. - -``-VV,--extra-verbose`` - Enable more verbose output from tests. - - Test output is normally suppressed and only summary information is - displayed. This option will show even more test output. - -``--debug`` - Displaying more verbose internals of CTest. - - This feature will result in a large number of output that is mostly - useful for debugging dashboard problems. - -``--output-on-failure`` - Output anything outputted by the test program if the test should fail. - This option can also be enabled by setting the - :envvar:`CTEST_OUTPUT_ON_FAILURE` environment variable - -``--stop-on-failure`` - Stop running the tests when the first failure happens. - -``-F`` - Enable failover. - - This option allows CTest to resume a test set execution that was - previously interrupted. If no interruption occurred, the ``-F`` option - will have no effect. - -``-j <jobs>, --parallel <jobs>`` - Run the tests in parallel using the given number of jobs. - - This option tells CTest to run the tests in parallel using given - number of jobs. This option can also be set by setting the - :envvar:`CTEST_PARALLEL_LEVEL` environment variable. - - This option can be used with the :prop_test:`PROCESSORS` test property. - - See `Label and Subproject Summary`_. - -``--resource-spec-file <file>`` - Run CTest with :ref:`resource allocation <ctest-resource-allocation>` enabled, - using the - :ref:`resource specification file <ctest-resource-specification-file>` - specified in ``<file>``. - - When ``ctest`` is run as a `Dashboard Client`_ this sets the - ``ResourceSpecFile`` option of the `CTest Test Step`_. - -``--test-load <level>`` - While running tests in parallel (e.g. with ``-j``), try not to start - tests when they may cause the CPU load to pass above a given threshold. - - When ``ctest`` is run as a `Dashboard Client`_ this sets the - ``TestLoad`` option of the `CTest Test Step`_. - -``-Q,--quiet`` - Make CTest quiet. - - This option will suppress all the output. The output log file will - still be generated if the ``--output-log`` is specified. Options such - as ``--verbose``, ``--extra-verbose``, and ``--debug`` are ignored - if ``--quiet`` is specified. - -``-O <file>, --output-log <file>`` - Output to log file. - - This option tells CTest to write all its output to a ``<file>`` log file. - -``-N,--show-only[=<format>]`` - Disable actual execution of tests. - - This option tells CTest to list the tests that would be run but not - actually run them. Useful in conjunction with the ``-R`` and ``-E`` - options. - - ``<format>`` can be one of the following values. - - ``human`` - Human-friendly output. This is not guaranteed to be stable. - This is the default. - - ``json-v1`` - Dump the test information in JSON format. - See `Show as JSON Object Model`_. - -``-L <regex>, --label-regex <regex>`` - Run tests with labels matching regular expression. - - This option tells CTest to run only the tests whose labels match the - given regular expression. - -``-R <regex>, --tests-regex <regex>`` - Run tests matching regular expression. - - This option tells CTest to run only the tests whose names match the - given regular expression. - -``-E <regex>, --exclude-regex <regex>`` - Exclude tests matching regular expression. - - This option tells CTest to NOT run the tests whose names match the - given regular expression. - -``-LE <regex>, --label-exclude <regex>`` - Exclude tests with labels matching regular expression. - - This option tells CTest to NOT run the tests whose labels match the - given regular expression. - -``-FA <regex>, --fixture-exclude-any <regex>`` - Exclude fixtures matching ``<regex>`` from automatically adding any tests to - the test set. - - If a test in the set of tests to be executed requires a particular fixture, - that fixture's setup and cleanup tests would normally be added to the test set - automatically. This option prevents adding setup or cleanup tests for fixtures - matching the ``<regex>``. Note that all other fixture behavior is retained, - including test dependencies and skipping tests that have fixture setup tests - that fail. - -``-FS <regex>, --fixture-exclude-setup <regex>`` - Same as ``-FA`` except only matching setup tests are excluded. - -``-FC <regex>, --fixture-exclude-cleanup <regex>`` - Same as ``-FA`` except only matching cleanup tests are excluded. - -``-D <dashboard>, --dashboard <dashboard>`` - Execute dashboard test. - - This option tells CTest to act as a CDash client and perform a - dashboard test. All tests are ``<Mode><Test>``, where ``<Mode>`` can be - ``Experimental``, ``Nightly``, and ``Continuous``, and ``<Test>`` can be - ``Start``, ``Update``, ``Configure``, ``Build``, ``Test``, - ``Coverage``, and ``Submit``. - - See `Dashboard Client`_. - -``-D <var>:<type>=<value>`` - Define a variable for script mode. - - Pass in variable values on the command line. Use in conjunction - with ``-S`` to pass variable values to a dashboard script. Parsing ``-D`` - arguments as variable values is only attempted if the value - following ``-D`` does not match any of the known dashboard types. - -``-M <model>, --test-model <model>`` - Sets the model for a dashboard. - - This option tells CTest to act as a CDash client where the ``<model>`` - can be ``Experimental``, ``Nightly``, and ``Continuous``. - Combining ``-M`` and ``-T`` is similar to ``-D``. - - See `Dashboard Client`_. - -``-T <action>, --test-action <action>`` - Sets the dashboard action to perform. - - This option tells CTest to act as a CDash client and perform some - action such as ``start``, ``build``, ``test`` etc. See - `Dashboard Client Steps`_ for the full list of actions. - Combining ``-M`` and ``-T`` is similar to ``-D``. - - See `Dashboard Client`_. - -``-S <script>, --script <script>`` - Execute a dashboard for a configuration. - - This option tells CTest to load in a configuration script which sets - a number of parameters such as the binary and source directories. - Then CTest will do what is required to create and run a dashboard. - This option basically sets up a dashboard and then runs ``ctest -D`` - with the appropriate options. - - See `Dashboard Client`_. - -``-SP <script>, --script-new-process <script>`` - Execute a dashboard for a configuration. - - This option does the same operations as ``-S`` but it will do them in a - separate process. This is primarily useful in cases where the - script may modify the environment and you do not want the modified - environment to impact other ``-S`` scripts. - - See `Dashboard Client`_. - -``-I [Start,End,Stride,test#,test#|Test file], --tests-information`` - Run a specific number of tests by number. - - This option causes CTest to run tests starting at number ``Start``, - ending at number ``End``, and incrementing by ``Stride``. Any additional - numbers after ``Stride`` are considered individual test numbers. ``Start``, - ``End``, or ``Stride`` can be empty. Optionally a file can be given that - contains the same syntax as the command line. - -``-U, --union`` - Take the Union of ``-I`` and ``-R``. - - When both ``-R`` and ``-I`` are specified by default the intersection of - tests are run. By specifying ``-U`` the union of tests is run instead. - -``--rerun-failed`` - Run only the tests that failed previously. - - This option tells CTest to perform only the tests that failed during - its previous run. When this option is specified, CTest ignores all - other options intended to modify the list of tests to run (``-L``, ``-R``, - ``-E``, ``-LE``, ``-I``, etc). In the event that CTest runs and no tests - fail, subsequent calls to CTest with the ``--rerun-failed`` option will run - the set of tests that most recently failed (if any). - -``--repeat <mode>:<n>`` - Run tests repeatedly based on the given ``<mode>`` up to ``<n>`` times. - The modes are: - - ``until-fail`` - Require each test to run ``<n>`` times without failing in order to pass. - This is useful in finding sporadic failures in test cases. - - ``until-pass`` - Allow each test to run up to ``<n>`` times in order to pass. - Repeats tests if they fail for any reason. - This is useful in tolerating sporadic failures in test cases. - - ``after-timeout`` - Allow each test to run up to ``<n>`` times in order to pass. - Repeats tests only if they timeout. - This is useful in tolerating sporadic timeouts in test cases - on busy machines. - -``--repeat-until-fail <n>`` - Equivalent to ``--repeat until-fail:<n>``. - -``--max-width <width>`` - Set the max width for a test name to output. - - Set the maximum width for each test name to show in the output. - This allows the user to widen the output to avoid clipping the test - name which can be very annoying. - -``--interactive-debug-mode [0|1]`` - Set the interactive mode to ``0`` or ``1``. - - This option causes CTest to run tests in either an interactive mode - or a non-interactive mode. On Windows this means that in - non-interactive mode, all system debug pop up windows are blocked. - In dashboard mode (``Experimental``, ``Nightly``, ``Continuous``), the default - is non-interactive. When just running tests not for a dashboard the - default is to allow popups and interactive debugging. - -``--no-label-summary`` - Disable timing summary information for labels. - - This option tells CTest not to print summary information for each - label associated with the tests run. If there are no labels on the - tests, nothing extra is printed. - - See `Label and Subproject Summary`_. - -``--no-subproject-summary`` - Disable timing summary information for subprojects. - - This option tells CTest not to print summary information for each - subproject associated with the tests run. If there are no subprojects on the - tests, nothing extra is printed. - - See `Label and Subproject Summary`_. - -``--build-and-test`` -See `Build and Test Mode`_. - -``--test-output-size-passed <size>`` - Limit the output for passed tests to ``<size>`` bytes. - -``--test-output-size-failed <size>`` - Limit the output for failed tests to ``<size>`` bytes. - -``--overwrite`` - Overwrite CTest configuration option. - - By default CTest uses configuration options from configuration file. - This option will overwrite the configuration option. - -``--force-new-ctest-process`` - Run child CTest instances as new processes. - - By default CTest will run child CTest instances within the same - process. If this behavior is not desired, this argument will - enforce new processes for child CTest processes. - -``--schedule-random`` - Use a random order for scheduling tests. - - This option will run the tests in a random order. It is commonly - used to detect implicit dependencies in a test suite. - -``--submit-index`` - Legacy option for old Dart2 dashboard server feature. - Do not use. - -``--timeout <seconds>`` - Set the default test timeout. - - This option effectively sets a timeout on all tests that do not - already have a timeout set on them via the :prop_test:`TIMEOUT` - property. - -``--stop-time <time>`` - Set a time at which all tests should stop running. - - Set a real time of day at which all tests should timeout. Example: - ``7:00:00 -0400``. Any time format understood by the curl date parser - is accepted. Local time is assumed if no timezone is specified. - -``--print-labels`` - Print all available test labels. - - This option will not run any tests, it will simply print the list of - all labels associated with the test set. - -``--no-tests=<[error|ignore]>`` - Regard no tests found either as error or ignore it. - - If no tests were found, the default behavior of CTest is to always log an - error message but to return an error code in script mode only. This option - unifies the behavior of CTest by either returning an error code if no tests - were found or by ignoring it. - -.. include:: OPTIONS_HELP.txt - -.. _`Label and Subproject Summary`: - -Label and Subproject Summary -============================ - -CTest prints timing summary information for each ``LABEL`` and subproject -associated with the tests run. The label time summary will not include labels -that are mapped to subprojects. - -When the :prop_test:`PROCESSORS` test property is set, CTest will display a -weighted test timing result in label and subproject summaries. The time is -reported with `sec*proc` instead of just `sec`. - -The weighted time summary reported for each label or subproject ``j`` -is computed as:: - - Weighted Time Summary for Label/Subproject j = - sum(raw_test_time[j,i] * num_processors[j,i], i=1...num_tests[j]) - - for labels/subprojects j=1...total - -where: - -* ``raw_test_time[j,i]``: Wall-clock time for the ``i`` test - for the ``j`` label or subproject -* ``num_processors[j,i]``: Value of the CTest :prop_test:`PROCESSORS` property - for the ``i`` test for the ``j`` label or subproject -* ``num_tests[j]``: Number of tests associated with the ``j`` label or subproject -* ``total``: Total number of labels or subprojects that have at least one test run - -Therefore, the weighted time summary for each label or subproject represents -the amount of time that CTest gave to run the tests for each label or -subproject and gives a good representation of the total expense of the tests -for each label or subproject when compared to other labels or subprojects. - -For example, if ``SubprojectA`` showed ``100 sec*proc`` and ``SubprojectB`` showed -``10 sec*proc``, then CTest allocated approximately 10 times the CPU/core time -to run the tests for ``SubprojectA`` than for ``SubprojectB`` (e.g. so if effort -is going to be expended to reduce the cost of the test suite for the whole -project, then reducing the cost of the test suite for ``SubprojectA`` would -likely have a larger impact than effort to reduce the cost of the test suite -for ``SubprojectB``). - -.. _`Build and Test Mode`: - -Build and Test Mode -=================== - -CTest provides a command-line signature to configure (i.e. run cmake on), -build, and/or execute a test:: - - ctest --build-and-test <path-to-source> <path-to-build> - --build-generator <generator> - [<options>...] - [--build-options <opts>...] - [--test-command <command> [<args>...]] - -The configure and test steps are optional. The arguments to this command line -are the source and binary directories. The ``--build-generator`` option *must* -be provided to use ``--build-and-test``. If ``--test-command`` is specified -then that will be run after the build is complete. Other options that affect -this mode include: - -``--build-target`` - Specify a specific target to build. - - If left out the ``all`` target is built. - -``--build-nocmake`` - Run the build without running cmake first. - - Skip the cmake step. - -``--build-run-dir`` - Specify directory to run programs from. - - Directory where programs will be after it has been compiled. - -``--build-two-config`` - Run CMake twice. - -``--build-exe-dir`` - Specify the directory for the executable. - -``--build-generator`` - Specify the generator to use. See the :manual:`cmake-generators(7)` manual. - -``--build-generator-platform`` - Specify the generator-specific platform. - -``--build-generator-toolset`` - Specify the generator-specific toolset. - -``--build-project`` - Specify the name of the project to build. - -``--build-makeprogram`` - Specify the explicit make program to be used by CMake when configuring and - building the project. Only applicable for Make and Ninja based generators. - -``--build-noclean`` - Skip the make clean step. - -``--build-config-sample`` - A sample executable to use to determine the configuration that - should be used. e.g. ``Debug``, ``Release`` etc. - -``--build-options`` - Additional options for configuring the build (i.e. for CMake, not for - the build tool). Note that if this is specified, the ``--build-options`` - keyword and its arguments must be the last option given on the command - line, with the possible exception of ``--test-command``. - -``--test-command`` - The command to run as the test step with the ``--build-and-test`` option. - All arguments following this keyword will be assumed to be part of the - test command line, so it must be the last option given. - -``--test-timeout`` - The time limit in seconds - -.. _`Dashboard Client`: - -Dashboard Client -================ - -CTest can operate as a client for the `CDash`_ software quality dashboard -application. As a dashboard client, CTest performs a sequence of steps -to configure, build, and test software, and then submits the results to -a `CDash`_ server. The command-line signature used to submit to `CDash`_ is:: - - ctest (-D <dashboard> | -M <model> -T <action> | -S <script> | -SP <script>) - [-- <dashboard-options>...] - -Options for Dashboard Client include: - -``--group <group>`` - Specify what group you'd like to submit results to - - Submit dashboard to specified group instead of default one. By - default, the dashboard is submitted to Nightly, Experimental, or - Continuous group, but by specifying this option, the group can be - arbitrary. - - This replaces the deprecated option ``--track``. - Despite the name change its behavior is unchanged. - -``-A <file>, --add-notes <file>`` - Add a notes file with submission. - - This option tells CTest to include a notes file when submitting - dashboard. - -``--tomorrow-tag`` - ``Nightly`` or ``Experimental`` starts with next day tag. - - This is useful if the build will not finish in one day. - -``--extra-submit <file>[;<file>]`` - Submit extra files to the dashboard. - - This option will submit extra files to the dashboard. - -``--http1.0`` - Submit using `HTTP 1.0`. - - This option will force CTest to use `HTTP 1.0` to submit files to the - dashboard, instead of `HTTP 1.1`. - -``--no-compress-output`` - Do not compress test output when submitting. - - This flag will turn off automatic compression of test output. Use - this to maintain compatibility with an older version of CDash which - doesn't support compressed test output. - -Dashboard Client Steps ----------------------- - -CTest defines an ordered list of testing steps of which some or all may -be run as a dashboard client: - -``Start`` - Start a new dashboard submission to be composed of results recorded - by the following steps. - See the `CTest Start Step`_ section below. - -``Update`` - Update the source tree from its version control repository. - Record the old and new versions and the list of updated source files. - See the `CTest Update Step`_ section below. - -``Configure`` - Configure the software by running a command in the build tree. - Record the configuration output log. - See the `CTest Configure Step`_ section below. - -``Build`` - Build the software by running a command in the build tree. - Record the build output log and detect warnings and errors. - See the `CTest Build Step`_ section below. - -``Test`` - Test the software by loading a ``CTestTestfile.cmake`` - from the build tree and executing the defined tests. - Record the output and result of each test. - See the `CTest Test Step`_ section below. - -``Coverage`` - Compute coverage of the source code by running a coverage - analysis tool and recording its output. - See the `CTest Coverage Step`_ section below. - -``MemCheck`` - Run the software test suite through a memory check tool. - Record the test output, results, and issues reported by the tool. - See the `CTest MemCheck Step`_ section below. - -``Submit`` - Submit results recorded from other testing steps to the - software quality dashboard server. - See the `CTest Submit Step`_ section below. - -Dashboard Client Modes ----------------------- - -CTest defines three modes of operation as a dashboard client: - -``Nightly`` - This mode is intended to be invoked once per day, typically at night. - It enables the ``Start``, ``Update``, ``Configure``, ``Build``, ``Test``, - ``Coverage``, and ``Submit`` steps by default. Selected steps run even - if the ``Update`` step reports no changes to the source tree. - -``Continuous`` - This mode is intended to be invoked repeatedly throughout the day. - It enables the ``Start``, ``Update``, ``Configure``, ``Build``, ``Test``, - ``Coverage``, and ``Submit`` steps by default, but exits after the - ``Update`` step if it reports no changes to the source tree. - -``Experimental`` - This mode is intended to be invoked by a developer to test local changes. - It enables the ``Start``, ``Configure``, ``Build``, ``Test``, ``Coverage``, - and ``Submit`` steps by default. - -Dashboard Client via CTest Command-Line ---------------------------------------- - -CTest can perform testing on an already-generated build tree. -Run the ``ctest`` command with the current working directory set -to the build tree and use one of these signatures:: - - ctest -D <mode>[<step>] - ctest -M <mode> [ -T <step> ]... - -The ``<mode>`` must be one of the above `Dashboard Client Modes`_, -and each ``<step>`` must be one of the above `Dashboard Client Steps`_. - -CTest reads the `Dashboard Client Configuration`_ settings from -a file in the build tree called either ``CTestConfiguration.ini`` -or ``DartConfiguration.tcl`` (the names are historical). The format -of the file is:: - - # Lines starting in '#' are comments. - # Other non-blank lines are key-value pairs. - <setting>: <value> - -where ``<setting>`` is the setting name and ``<value>`` is the -setting value. - -In build trees generated by CMake, this configuration file is -generated by the :module:`CTest` module if included by the project. -The module uses variables to obtain a value for each setting -as documented with the settings below. - -.. _`CTest Script`: - -Dashboard Client via CTest Script ---------------------------------- - -CTest can perform testing driven by a :manual:`cmake-language(7)` -script that creates and maintains the source and build tree as -well as performing the testing steps. Run the ``ctest`` command -with the current working directory set outside of any build tree -and use one of these signatures:: - - ctest -S <script> - ctest -SP <script> - -The ``<script>`` file must call :ref:`CTest Commands` commands -to run testing steps explicitly as documented below. The commands -obtain `Dashboard Client Configuration`_ settings from their -arguments or from variables set in the script. - -Dashboard Client Configuration -============================== - -The `Dashboard Client Steps`_ may be configured by named -settings as documented in the following sections. - -.. _`CTest Start Step`: - -CTest Start Step ----------------- - -Start a new dashboard submission to be composed of results recorded -by the following steps. - -In a `CTest Script`_, the :command:`ctest_start` command runs this step. -Arguments to the command may specify some of the step settings. -The command first runs the command-line specified by the -``CTEST_CHECKOUT_COMMAND`` variable, if set, to initialize the source -directory. - -Configuration settings include: - -``BuildDirectory`` - The full path to the project build tree. - - * `CTest Script`_ variable: :variable:`CTEST_BINARY_DIRECTORY` - * :module:`CTest` module variable: :variable:`PROJECT_BINARY_DIR` - -``SourceDirectory`` - The full path to the project source tree. - - * `CTest Script`_ variable: :variable:`CTEST_SOURCE_DIRECTORY` - * :module:`CTest` module variable: :variable:`PROJECT_SOURCE_DIR` - -.. _`CTest Update Step`: - -CTest Update Step ------------------ - -In a `CTest Script`_, the :command:`ctest_update` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings to specify the version control tool include: - -``BZRCommand`` - ``bzr`` command-line tool to use if source tree is managed by Bazaar. - - * `CTest Script`_ variable: :variable:`CTEST_BZR_COMMAND` - * :module:`CTest` module variable: none - -``BZRUpdateOptions`` - Command-line options to the ``BZRCommand`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_BZR_UPDATE_OPTIONS` - * :module:`CTest` module variable: none - -``CVSCommand`` - ``cvs`` command-line tool to use if source tree is managed by CVS. - - * `CTest Script`_ variable: :variable:`CTEST_CVS_COMMAND` - * :module:`CTest` module variable: ``CVSCOMMAND`` - -``CVSUpdateOptions`` - Command-line options to the ``CVSCommand`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_CVS_UPDATE_OPTIONS` - * :module:`CTest` module variable: ``CVS_UPDATE_OPTIONS`` - -``GITCommand`` - ``git`` command-line tool to use if source tree is managed by Git. - - * `CTest Script`_ variable: :variable:`CTEST_GIT_COMMAND` - * :module:`CTest` module variable: ``GITCOMMAND`` - - The source tree is updated by ``git fetch`` followed by - ``git reset --hard`` to the ``FETCH_HEAD``. The result is the same - as ``git pull`` except that any local modifications are overwritten. - Use ``GITUpdateCustom`` to specify a different approach. - -``GITInitSubmodules`` - If set, CTest will update the repository's submodules before updating. - - * `CTest Script`_ variable: :variable:`CTEST_GIT_INIT_SUBMODULES` - * :module:`CTest` module variable: ``CTEST_GIT_INIT_SUBMODULES`` - -``GITUpdateCustom`` - Specify a custom command line (as a semicolon-separated list) to run - in the source tree (Git work tree) to update it instead of running - the ``GITCommand``. - - * `CTest Script`_ variable: :variable:`CTEST_GIT_UPDATE_CUSTOM` - * :module:`CTest` module variable: ``CTEST_GIT_UPDATE_CUSTOM`` - -``GITUpdateOptions`` - Command-line options to the ``GITCommand`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_GIT_UPDATE_OPTIONS` - * :module:`CTest` module variable: ``GIT_UPDATE_OPTIONS`` - -``HGCommand`` - ``hg`` command-line tool to use if source tree is managed by Mercurial. - - * `CTest Script`_ variable: :variable:`CTEST_HG_COMMAND` - * :module:`CTest` module variable: none - -``HGUpdateOptions`` - Command-line options to the ``HGCommand`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_HG_UPDATE_OPTIONS` - * :module:`CTest` module variable: none - -``P4Client`` - Value of the ``-c`` option to the ``P4Command``. - - * `CTest Script`_ variable: :variable:`CTEST_P4_CLIENT` - * :module:`CTest` module variable: ``CTEST_P4_CLIENT`` - -``P4Command`` - ``p4`` command-line tool to use if source tree is managed by Perforce. - - * `CTest Script`_ variable: :variable:`CTEST_P4_COMMAND` - * :module:`CTest` module variable: ``P4COMMAND`` - -``P4Options`` - Command-line options to the ``P4Command`` for all invocations. - - * `CTest Script`_ variable: :variable:`CTEST_P4_OPTIONS` - * :module:`CTest` module variable: ``CTEST_P4_OPTIONS`` - -``P4UpdateCustom`` - Specify a custom command line (as a semicolon-separated list) to run - in the source tree (Perforce tree) to update it instead of running - the ``P4Command``. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``CTEST_P4_UPDATE_CUSTOM`` - -``P4UpdateOptions`` - Command-line options to the ``P4Command`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_P4_UPDATE_OPTIONS` - * :module:`CTest` module variable: ``CTEST_P4_UPDATE_OPTIONS`` - -``SVNCommand`` - ``svn`` command-line tool to use if source tree is managed by Subversion. - - * `CTest Script`_ variable: :variable:`CTEST_SVN_COMMAND` - * :module:`CTest` module variable: ``SVNCOMMAND`` - -``SVNOptions`` - Command-line options to the ``SVNCommand`` for all invocations. - - * `CTest Script`_ variable: :variable:`CTEST_SVN_OPTIONS` - * :module:`CTest` module variable: ``CTEST_SVN_OPTIONS`` - -``SVNUpdateOptions`` - Command-line options to the ``SVNCommand`` when updating the source. - - * `CTest Script`_ variable: :variable:`CTEST_SVN_UPDATE_OPTIONS` - * :module:`CTest` module variable: ``SVN_UPDATE_OPTIONS`` - -``UpdateCommand`` - Specify the version-control command-line tool to use without - detecting the VCS that manages the source tree. - - * `CTest Script`_ variable: :variable:`CTEST_UPDATE_COMMAND` - * :module:`CTest` module variable: ``<VCS>COMMAND`` - when ``UPDATE_TYPE`` is ``<vcs>``, else ``UPDATE_COMMAND`` - -``UpdateOptions`` - Command-line options to the ``UpdateCommand``. - - * `CTest Script`_ variable: :variable:`CTEST_UPDATE_OPTIONS` - * :module:`CTest` module variable: ``<VCS>_UPDATE_OPTIONS`` - when ``UPDATE_TYPE`` is ``<vcs>``, else ``UPDATE_OPTIONS`` - -``UpdateType`` - Specify the version-control system that manages the source - tree if it cannot be detected automatically. - The value may be ``bzr``, ``cvs``, ``git``, ``hg``, - ``p4``, or ``svn``. - - * `CTest Script`_ variable: none, detected from source tree - * :module:`CTest` module variable: ``UPDATE_TYPE`` if set, - else ``CTEST_UPDATE_TYPE`` - -.. _`UpdateVersionOnly`: - -``UpdateVersionOnly`` - Specify that you want the version control update command to only - discover the current version that is checked out, and not to update - to a different version. - - * `CTest Script`_ variable: :variable:`CTEST_UPDATE_VERSION_ONLY` - -.. _`UpdateVersionOverride`: - -``UpdateVersionOverride`` - Specify the current version of your source tree. - - When this variable is set to a non-empty string, CTest will report the value - you specified rather than using the update command to discover the current - version that is checked out. Use of this variable supersedes - ``UpdateVersionOnly``. Like ``UpdateVersionOnly``, using this variable tells - CTest not to update the source tree to a different version. - - * `CTest Script`_ variable: :variable:`CTEST_UPDATE_VERSION_OVERRIDE` - -Additional configuration settings include: - -``NightlyStartTime`` - In the ``Nightly`` dashboard mode, specify the "nightly start time". - With centralized version control systems (``cvs`` and ``svn``), - the ``Update`` step checks out the version of the software as of - this time so that multiple clients choose a common version to test. - This is not well-defined in distributed version-control systems so - the setting is ignored. - - * `CTest Script`_ variable: :variable:`CTEST_NIGHTLY_START_TIME` - * :module:`CTest` module variable: ``NIGHTLY_START_TIME`` if set, - else ``CTEST_NIGHTLY_START_TIME`` - -.. _`CTest Configure Step`: - -CTest Configure Step --------------------- - -In a `CTest Script`_, the :command:`ctest_configure` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``ConfigureCommand`` - Command-line to launch the software configuration process. - It will be executed in the location specified by the - ``BuildDirectory`` setting. - - * `CTest Script`_ variable: :variable:`CTEST_CONFIGURE_COMMAND` - * :module:`CTest` module variable: :variable:`CMAKE_COMMAND` - followed by :variable:`PROJECT_SOURCE_DIR` - -``LabelsForSubprojects`` - Specify a semicolon-separated list of labels that will be treated as - subprojects. This mapping will be passed on to CDash when configure, test or - build results are submitted. - - * `CTest Script`_ variable: :variable:`CTEST_LABELS_FOR_SUBPROJECTS` - * :module:`CTest` module variable: ``CTEST_LABELS_FOR_SUBPROJECTS`` - - See `Label and Subproject Summary`_. - -.. _`CTest Build Step`: - -CTest Build Step ----------------- - -In a `CTest Script`_, the :command:`ctest_build` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``DefaultCTestConfigurationType`` - When the build system to be launched allows build-time selection - of the configuration (e.g. ``Debug``, ``Release``), this specifies - the default configuration to be built when no ``-C`` option is - given to the ``ctest`` command. The value will be substituted into - the value of ``MakeCommand`` to replace the literal string - ``${CTEST_CONFIGURATION_TYPE}`` if it appears. - - * `CTest Script`_ variable: :variable:`CTEST_CONFIGURATION_TYPE` - * :module:`CTest` module variable: ``DEFAULT_CTEST_CONFIGURATION_TYPE``, - initialized by the :envvar:`CMAKE_CONFIG_TYPE` environment variable - -``LabelsForSubprojects`` - Specify a semicolon-separated list of labels that will be treated as - subprojects. This mapping will be passed on to CDash when configure, test or - build results are submitted. - - * `CTest Script`_ variable: :variable:`CTEST_LABELS_FOR_SUBPROJECTS` - * :module:`CTest` module variable: ``CTEST_LABELS_FOR_SUBPROJECTS`` - - See `Label and Subproject Summary`_. - -``MakeCommand`` - Command-line to launch the software build process. - It will be executed in the location specified by the - ``BuildDirectory`` setting. - - * `CTest Script`_ variable: :variable:`CTEST_BUILD_COMMAND` - * :module:`CTest` module variable: ``MAKECOMMAND``, - initialized by the :command:`build_command` command - -``UseLaunchers`` - For build trees generated by CMake using one of the - :ref:`Makefile Generators` or the :generator:`Ninja` - generator, specify whether the - ``CTEST_USE_LAUNCHERS`` feature is enabled by the - :module:`CTestUseLaunchers` module (also included by the - :module:`CTest` module). When enabled, the generated build - system wraps each invocation of the compiler, linker, or - custom command line with a "launcher" that communicates - with CTest via environment variables and files to report - granular build warning and error information. Otherwise, - CTest must "scrape" the build output log for diagnostics. - - * `CTest Script`_ variable: :variable:`CTEST_USE_LAUNCHERS` - * :module:`CTest` module variable: ``CTEST_USE_LAUNCHERS`` - -.. _`CTest Test Step`: - -CTest Test Step ---------------- - -In a `CTest Script`_, the :command:`ctest_test` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``ResourceSpecFile`` - Specify a - :ref:`resource specification file <ctest-resource-specification-file>`. - - * `CTest Script`_ variable: :variable:`CTEST_RESOURCE_SPEC_FILE` - * :module:`CTest` module variable: ``CTEST_RESOURCE_SPEC_FILE`` - - See :ref:`ctest-resource-allocation` for more information. - -``LabelsForSubprojects`` - Specify a semicolon-separated list of labels that will be treated as - subprojects. This mapping will be passed on to CDash when configure, test or - build results are submitted. - - * `CTest Script`_ variable: :variable:`CTEST_LABELS_FOR_SUBPROJECTS` - * :module:`CTest` module variable: ``CTEST_LABELS_FOR_SUBPROJECTS`` - - See `Label and Subproject Summary`_. - -``TestLoad`` - While running tests in parallel (e.g. with ``-j``), try not to start - tests when they may cause the CPU load to pass above a given threshold. - - * `CTest Script`_ variable: :variable:`CTEST_TEST_LOAD` - * :module:`CTest` module variable: ``CTEST_TEST_LOAD`` - -``TimeOut`` - The default timeout for each test if not specified by the - :prop_test:`TIMEOUT` test property. - - * `CTest Script`_ variable: :variable:`CTEST_TEST_TIMEOUT` - * :module:`CTest` module variable: ``DART_TESTING_TIMEOUT`` - -.. _`CTest Coverage Step`: - -CTest Coverage Step -------------------- - -In a `CTest Script`_, the :command:`ctest_coverage` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``CoverageCommand`` - Command-line tool to perform software coverage analysis. - It will be executed in the location specified by the - ``BuildDirectory`` setting. - - * `CTest Script`_ variable: :variable:`CTEST_COVERAGE_COMMAND` - * :module:`CTest` module variable: ``COVERAGE_COMMAND`` - -``CoverageExtraFlags`` - Specify command-line options to the ``CoverageCommand`` tool. - - * `CTest Script`_ variable: :variable:`CTEST_COVERAGE_EXTRA_FLAGS` - * :module:`CTest` module variable: ``COVERAGE_EXTRA_FLAGS`` - - These options are the first arguments passed to ``CoverageCommand``. - -.. _`CTest MemCheck Step`: - -CTest MemCheck Step -------------------- - -In a `CTest Script`_, the :command:`ctest_memcheck` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``MemoryCheckCommand`` - Command-line tool to perform dynamic analysis. Test command lines - will be launched through this tool. - - * `CTest Script`_ variable: :variable:`CTEST_MEMORYCHECK_COMMAND` - * :module:`CTest` module variable: ``MEMORYCHECK_COMMAND`` - -``MemoryCheckCommandOptions`` - Specify command-line options to the ``MemoryCheckCommand`` tool. - They will be placed prior to the test command line. - - * `CTest Script`_ variable: :variable:`CTEST_MEMORYCHECK_COMMAND_OPTIONS` - * :module:`CTest` module variable: ``MEMORYCHECK_COMMAND_OPTIONS`` - -``MemoryCheckType`` - Specify the type of memory checking to perform. - - * `CTest Script`_ variable: :variable:`CTEST_MEMORYCHECK_TYPE` - * :module:`CTest` module variable: ``MEMORYCHECK_TYPE`` - -``MemoryCheckSanitizerOptions`` - Specify options to sanitizers when running with a sanitize-enabled build. - - * `CTest Script`_ variable: :variable:`CTEST_MEMORYCHECK_SANITIZER_OPTIONS` - * :module:`CTest` module variable: ``MEMORYCHECK_SANITIZER_OPTIONS`` - -``MemoryCheckSuppressionFile`` - Specify a file containing suppression rules for the - ``MemoryCheckCommand`` tool. It will be passed with options - appropriate to the tool. - - * `CTest Script`_ variable: :variable:`CTEST_MEMORYCHECK_SUPPRESSIONS_FILE` - * :module:`CTest` module variable: ``MEMORYCHECK_SUPPRESSIONS_FILE`` - -Additional configuration settings include: - -``BoundsCheckerCommand`` - Specify a ``MemoryCheckCommand`` that is known to be command-line - compatible with Bounds Checker. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: none - -``PurifyCommand`` - Specify a ``MemoryCheckCommand`` that is known to be command-line - compatible with Purify. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``PURIFYCOMMAND`` - -``ValgrindCommand`` - Specify a ``MemoryCheckCommand`` that is known to be command-line - compatible with Valgrind. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``VALGRIND_COMMAND`` - -``ValgrindCommandOptions`` - Specify command-line options to the ``ValgrindCommand`` tool. - They will be placed prior to the test command line. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``VALGRIND_COMMAND_OPTIONS`` - -``DrMemoryCommand`` - Specify a ``MemoryCheckCommand`` that is known to be a command-line - compatible with DrMemory. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``DRMEMORY_COMMAND`` - -``DrMemoryCommandOptions`` - Specify command-line options to the ``DrMemoryCommand`` tool. - They will be placed prior to the test command line. - - * `CTest Script`_ variable: none - * :module:`CTest` module variable: ``DRMEMORY_COMMAND_OPTIONS`` - -.. _`CTest Submit Step`: - -CTest Submit Step ------------------ - -In a `CTest Script`_, the :command:`ctest_submit` command runs this step. -Arguments to the command may specify some of the step settings. - -Configuration settings include: - -``BuildName`` - Describe the dashboard client platform with a short string. - (Operating system, compiler, etc.) - - * `CTest Script`_ variable: :variable:`CTEST_BUILD_NAME` - * :module:`CTest` module variable: ``BUILDNAME`` - -``CDashVersion`` - Legacy option. Not used. - - * `CTest Script`_ variable: none, detected from server - * :module:`CTest` module variable: ``CTEST_CDASH_VERSION`` - -``CTestSubmitRetryCount`` - Specify a number of attempts to retry submission on network failure. - - * `CTest Script`_ variable: none, - use the :command:`ctest_submit` ``RETRY_COUNT`` option. - * :module:`CTest` module variable: ``CTEST_SUBMIT_RETRY_COUNT`` - -``CTestSubmitRetryDelay`` - Specify a delay before retrying submission on network failure. - - * `CTest Script`_ variable: none, - use the :command:`ctest_submit` ``RETRY_DELAY`` option. - * :module:`CTest` module variable: ``CTEST_SUBMIT_RETRY_DELAY`` - -``CurlOptions`` - Specify a semicolon-separated list of options to control the - Curl library that CTest uses internally to connect to the - server. Possible options are ``CURLOPT_SSL_VERIFYPEER_OFF`` - and ``CURLOPT_SSL_VERIFYHOST_OFF``. - - * `CTest Script`_ variable: :variable:`CTEST_CURL_OPTIONS` - * :module:`CTest` module variable: ``CTEST_CURL_OPTIONS`` - -``DropLocation`` - Legacy option. When ``SubmitURL`` is not set, it is constructed from - ``DropMethod``, ``DropSiteUser``, ``DropSitePassword``, ``DropSite``, and - ``DropLocation``. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_LOCATION` - * :module:`CTest` module variable: ``DROP_LOCATION`` if set, - else ``CTEST_DROP_LOCATION`` - -``DropMethod`` - Legacy option. When ``SubmitURL`` is not set, it is constructed from - ``DropMethod``, ``DropSiteUser``, ``DropSitePassword``, ``DropSite``, and - ``DropLocation``. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_METHOD` - * :module:`CTest` module variable: ``DROP_METHOD`` if set, - else ``CTEST_DROP_METHOD`` - -``DropSite`` - Legacy option. When ``SubmitURL`` is not set, it is constructed from - ``DropMethod``, ``DropSiteUser``, ``DropSitePassword``, ``DropSite``, and - ``DropLocation``. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_SITE` - * :module:`CTest` module variable: ``DROP_SITE`` if set, - else ``CTEST_DROP_SITE`` - -``DropSitePassword`` - Legacy option. When ``SubmitURL`` is not set, it is constructed from - ``DropMethod``, ``DropSiteUser``, ``DropSitePassword``, ``DropSite``, and - ``DropLocation``. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_SITE_PASSWORD` - * :module:`CTest` module variable: ``DROP_SITE_PASSWORD`` if set, - else ``CTEST_DROP_SITE_PASWORD`` - -``DropSiteUser`` - Legacy option. When ``SubmitURL`` is not set, it is constructed from - ``DropMethod``, ``DropSiteUser``, ``DropSitePassword``, ``DropSite``, and - ``DropLocation``. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_SITE_USER` - * :module:`CTest` module variable: ``DROP_SITE_USER`` if set, - else ``CTEST_DROP_SITE_USER`` - -``IsCDash`` - Legacy option. Not used. - - * `CTest Script`_ variable: :variable:`CTEST_DROP_SITE_CDASH` - * :module:`CTest` module variable: ``CTEST_DROP_SITE_CDASH`` - -``ScpCommand`` - Legacy option. Not used. - - * `CTest Script`_ variable: :variable:`CTEST_SCP_COMMAND` - * :module:`CTest` module variable: ``SCPCOMMAND`` - -``Site`` - Describe the dashboard client host site with a short string. - (Hostname, domain, etc.) - - * `CTest Script`_ variable: :variable:`CTEST_SITE` - * :module:`CTest` module variable: ``SITE``, - initialized by the :command:`site_name` command - -``SubmitURL`` - The ``http`` or ``https`` URL of the dashboard server to send the submission - to. - - * `CTest Script`_ variable: :variable:`CTEST_SUBMIT_URL` - * :module:`CTest` module variable: ``SUBMIT_URL`` if set, - else ``CTEST_SUBMIT_URL`` - -``TriggerSite`` - Legacy option. Not used. - - * `CTest Script`_ variable: :variable:`CTEST_TRIGGER_SITE` - * :module:`CTest` module variable: ``TRIGGER_SITE`` if set, - else ``CTEST_TRIGGER_SITE`` - -.. _`Show as JSON Object Model`: - -Show as JSON Object Model -========================= - -When the ``--show-only=json-v1`` command line option is given, the test -information is output in JSON format. Version 1.0 of the JSON object -model is defined as follows: - -``kind`` - The string "ctestInfo". - -``version`` - A JSON object specifying the version components. Its members are - - ``major`` - A non-negative integer specifying the major version component. - ``minor`` - A non-negative integer specifying the minor version component. - -``backtraceGraph`` - JSON object representing backtrace information with the - following members: - - ``commands`` - List of command names. - ``files`` - List of file names. - ``nodes`` - List of node JSON objects with members: - - ``command`` - Index into the ``commands`` member of the ``backtraceGraph``. - ``file`` - Index into the ``files`` member of the ``backtraceGraph``. - ``line`` - Line number in the file where the backtrace was added. - ``parent`` - Index into the ``nodes`` member of the ``backtraceGraph`` - representing the parent in the graph. - -``tests`` - A JSON array listing information about each test. Each entry - is a JSON object with members: - - ``name`` - Test name. - ``config`` - Configuration that the test can run on. - Empty string means any config. - ``command`` - List where the first element is the test command and the - remaining elements are the command arguments. - ``backtrace`` - Index into the ``nodes`` member of the ``backtraceGraph``. - ``properties`` - Test properties. - Can contain keys for each of the supported test properties. - -.. _`ctest-resource-allocation`: - -Resource Allocation -=================== - -CTest provides a mechanism for tests to specify the resources that they need -in a fine-grained way, and for users to specify the resources availiable on -the running machine. This allows CTest to internally keep track of which -resources are in use and which are free, scheduling tests in a way that -prevents them from trying to claim resources that are not available. - -When the resource allocation feature is used, CTest will not oversubscribe -resources. For example, if a resource has 8 slots, CTest will not run tests -that collectively use more than 8 slots at a time. This has the effect of -limiting how many tests can run at any given time, even if a high ``-j`` -argument is used, if those tests all use some slots from the same resource. -In addition, it means that a single test that uses more of a resource than is -available on a machine will not run at all (and will be reported as -``Not Run``). - -A common use case for this feature is for tests that require the use of a GPU. -Multiple tests can simultaneously allocate memory from a GPU, but if too many -tests try to do this at once, some of them will fail to allocate, resulting in -a failed test, even though the test would have succeeded if it had the memory -it needed. By using the resource allocation feature, each test can specify how -much memory it requires from a GPU, allowing CTest to schedule tests in a way -that running several of these tests at once does not exhaust the GPU's memory -pool. - -Please note that CTest has no concept of what a GPU is or how much memory it -has, nor does it have any way of communicating with a GPU to retrieve this -information or perform any memory management. CTest simply keeps track of a -list of abstract resource types, each of which has a certain number of slots -available for tests to use. Each test specifies the number of slots that it -requires from a certain resource, and CTest then schedules them in a way that -prevents the total number of slots in use from exceeding the listed capacity. -When a test is executed, and slots from a resource are allocated to that test, -tests may assume that they have exclusive use of those slots for the duration -of the test's process. - -The CTest resource allocation feature consists of two inputs: - -* The :ref:`resource specification file <ctest-resource-specification-file>`, - described below, which describes the resources available on the system. -* The :prop_test:`RESOURCE_GROUPS` property of tests, which describes the - resources required by the test. - -When CTest runs a test, the resources allocated to that test are passed in the -form of a set of -:ref:`environment variables <ctest-resource-environment-variables>` as -described below. Using this information to decide which resource to connect to -is left to the test writer. - -The ``RESOURCE_GROUPS`` property tells CTest what resources a test expects -to use grouped in a way meaningful to the test. The test itself must read -the :ref:`environment variables <ctest-resource-environment-variables>` to -determine which resources have been allocated to each group. For example, -each group may correspond to a process the test will spawn when executed. - -Note that even if a test specifies a ``RESOURCE_GROUPS`` property, it is still -possible for that to test to run without any resource allocation (and without -the corresponding -:ref:`environment variables <ctest-resource-environment-variables>`) -if the user does not pass a resource specification file. Passing this file, -either through the ``--resource-spec-file`` command-line argument or the -``RESOURCE_SPEC_FILE`` argument to :command:`ctest_test`, is what activates the -resource allocation feature. Tests should check the -``CTEST_RESOURCE_GROUP_COUNT`` environment variable to find out whether or not -resource allocation is activated. This variable will always (and only) be -defined if resource allocation is activated. If resource allocation is not -activated, then the ``CTEST_RESOURCE_GROUP_COUNT`` variable will not exist, -even if it exists for the parent ``ctest`` process. If a test absolutely must -have resource allocation, then it can return a failing exit code or use the -:prop_test:`SKIP_RETURN_CODE` or :prop_test:`SKIP_REGULAR_EXPRESSION` -properties to indicate a skipped test. - -.. _`ctest-resource-specification-file`: - -Resource Specification File ---------------------------- - -The resource specification file is a JSON file which is passed to CTest, either -on the :manual:`ctest(1)` command line as ``--resource-spec-file``, or as the -``RESOURCE_SPEC_FILE`` argument of :command:`ctest_test`. If a dashboard script -is used and ``RESOURCE_SPEC_FILE`` is not specified, the value of -:variable:`CTEST_RESOURCE_SPEC_FILE` in the dashboard script is used instead. -If ``--resource-spec-file``, ``RESOURCE_SPEC_FILE``, and -:variable:`CTEST_RESOURCE_SPEC_FILE` in the dashboard script are not specified, -the value of :variable:`CTEST_RESOURCE_SPEC_FILE` in the CMake build is used -instead. If none of these are specified, no resource spec file is used. - -The resource specification file must be a JSON object. All examples in this -document assume the following resource specification file: - -.. code-block:: json - - { - "version": { - "major": 1, - "minor": 0 - }, - "local": [ - { - "gpus": [ - { - "id": "0", - "slots": 2 - }, - { - "id": "1", - "slots": 4 - }, - { - "id": "2", - "slots": 2 - }, - { - "id": "3" - } - ], - "crypto_chips": [ - { - "id": "card0", - "slots": 4 - } - ] - } - ] - } - -The members are: - -``version`` - An object containing a ``major`` integer field and a ``minor`` integer field. - Currently, the only supported version is major ``1``, minor ``0``. Any other - value is an error. - -``local`` - A JSON array of resource sets present on the system. Currently, this array - is restricted to being of size 1. - - Each array element is a JSON object with members whose names are equal to the - desired resource types, such as ``gpus``. These names must start with a - lowercase letter or an underscore, and subsequent characters can be a - lowercase letter, a digit, or an underscore. Uppercase letters are not - allowed, because certain platforms have case-insensitive environment - variables. See the `Environment Variables`_ section below for - more information. It is recommended that the resource type name be the plural - of a noun, such as ``gpus`` or ``crypto_chips`` (and not ``gpu`` or - ``crypto_chip``.) - - Please note that the names ``gpus`` and ``crypto_chips`` are just examples, - and CTest does not interpret them in any way. You are free to make up any - resource type you want to meet your own requirements. - - The value for each resource type is a JSON array consisting of JSON objects, - each of which describe a specific instance of the specified resource. These - objects have the following members: - - ``id`` - A string consisting of an identifier for the resource. Each character in - the identifier can be a lowercase letter, a digit, or an underscore. - Uppercase letters are not allowed. - - Identifiers must be unique within a resource type. However, they do not - have to be unique across resource types. For example, it is valid to have a - ``gpus`` resource named ``0`` and a ``crypto_chips`` resource named ``0``, - but not two ``gpus`` resources both named ``0``. - - Please note that the IDs ``0``, ``1``, ``2``, ``3``, and ``card0`` are just - examples, and CTest does not interpret them in any way. You are free to - make up any IDs you want to meet your own requirements. - - ``slots`` - An optional unsigned number specifying the number of slots available on the - resource. For example, this could be megabytes of RAM on a GPU, or - cryptography units available on a cryptography chip. If ``slots`` is not - specified, a default value of ``1`` is assumed. - -In the example file above, there are four GPUs with ID's 0 through 3. GPU 0 has -2 slots, GPU 1 has 4, GPU 2 has 2, and GPU 3 has a default of 1 slot. There is -also one cryptography chip with 4 slots. - -``RESOURCE_GROUPS`` Property ----------------------------- - -See :prop_test:`RESOURCE_GROUPS` for a description of this property. - -.. _`ctest-resource-environment-variables`: - -Environment Variables ---------------------- - -Once CTest has decided which resources to allocate to a test, it passes this -information to the test executable as a series of environment variables. For -each example below, we will assume that the test in question has a -:prop_test:`RESOURCE_GROUPS` property of -``2,gpus:2;gpus:4,gpus:1,crypto_chips:2``. - -The following variables are passed to the test process: - -.. envvar:: CTEST_RESOURCE_GROUP_COUNT - - The total number of groups specified by the :prop_test:`RESOURCE_GROUPS` - property. For example: - - * ``CTEST_RESOURCE_GROUP_COUNT=3`` - - This variable will only be defined if :manual:`ctest(1)` has been given a - ``--resource-spec-file``, or if :command:`ctest_test` has been given a - ``RESOURCE_SPEC_FILE``. If no resource specification file has been given, - this variable will not be defined. - -.. envvar:: CTEST_RESOURCE_GROUP_<num> - - The list of resource types allocated to each group, with each item - separated by a comma. ``<num>`` is a number from zero to - ``CTEST_RESOURCE_GROUP_COUNT`` minus one. ``CTEST_RESOURCE_GROUP_<num>`` - is defined for each ``<num>`` in this range. For example: - - * ``CTEST_RESOURCE_GROUP_0=gpus`` - * ``CTEST_RESOURCE_GROUP_1=gpus`` - * ``CTEST_RESOURCE_GROUP_2=crypto_chips,gpus`` - -.. envvar:: CTEST_RESOURCE_GROUP_<num>_<resource-type> - - The list of resource IDs and number of slots from each ID allocated to each - group for a given resource type. This variable consists of a series of - pairs, each pair separated by a semicolon, and with the two items in the pair - separated by a comma. The first item in each pair is ``id:`` followed by the - ID of a resource of type ``<resource-type>``, and the second item is - ``slots:`` followed by the number of slots from that resource allocated to - the given group. For example: - - * ``CTEST_RESOURCE_GROUP_0_GPUS=id:0,slots:2`` - * ``CTEST_RESOURCE_GROUP_1_GPUS=id:2,slots:2`` - * ``CTEST_RESOURCE_GROUP_2_GPUS=id:1,slots:4;id:3,slots:1`` - * ``CTEST_RESOURCE_GROUP_2_CRYPTO_CHIPS=id:card0,slots:2`` - - In this example, group 0 gets 2 slots from GPU ``0``, group 1 gets 2 slots - from GPU ``2``, and group 2 gets 4 slots from GPU ``1``, 1 slot from GPU - ``3``, and 2 slots from cryptography chip ``card0``. - - ``<num>`` is a number from zero to ``CTEST_RESOURCE_GROUP_COUNT`` minus one. - ``<resource-type>`` is the name of a resource type, converted to uppercase. - ``CTEST_RESOURCE_GROUP_<num>_<resource-type>`` is defined for the product - of each ``<num>`` in the range listed above and each resource type listed in - ``CTEST_RESOURCE_GROUP_<num>``. - - Because some platforms have case-insensitive names for environment variables, - the names of resource types may not clash in a case-insensitive environment. - Because of this, for the sake of simplicity, all resource types must be - listed in all lowercase in the - :ref:`resource specification file <ctest-resource-specification-file>` and - in the :prop_test:`RESOURCE_GROUPS` property, and they are converted to all - uppercase in the ``CTEST_RESOURCE_GROUP_<num>_<resource-type>`` environment - variable. - -See Also -======== - -.. include:: LINKS.txt - -.. _`CDash`: http://cdash.org/
diff --git a/share/cmake-3.18/Help/module/CPackArchive.rst b/share/cmake-3.18/Help/module/CPackArchive.rst deleted file mode 100644 index 8616098..0000000 --- a/share/cmake-3.18/Help/module/CPackArchive.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CPackArchive ------------- - -The documentation for the CPack Archive generator has moved here: :cpack_gen:`CPack Archive Generator`
diff --git a/share/cmake-3.18/Help/module/CPackFreeBSD.rst b/share/cmake-3.18/Help/module/CPackFreeBSD.rst deleted file mode 100644 index 69701b8..0000000 --- a/share/cmake-3.18/Help/module/CPackFreeBSD.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CPackFreeBSD ------------- - -The documentation for the CPack FreeBSD generator has moved here: :cpack_gen:`CPack FreeBSD Generator`
diff --git a/share/cmake-3.18/Help/module/CPackNuGet.rst b/share/cmake-3.18/Help/module/CPackNuGet.rst deleted file mode 100644 index 4f39b3a..0000000 --- a/share/cmake-3.18/Help/module/CPackNuGet.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CPackNuGet ----------- - -The documentation for the CPack NuGet generator has moved here: :cpack_gen:`CPack NuGet Generator`
diff --git a/share/cmake-3.18/Help/module/CPackProductBuild.rst b/share/cmake-3.18/Help/module/CPackProductBuild.rst deleted file mode 100644 index 8cd9198..0000000 --- a/share/cmake-3.18/Help/module/CPackProductBuild.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CPackProductBuild ------------------ - -The documentation for the CPack productbuild generator has moved here: :cpack_gen:`CPack productbuild Generator`
diff --git a/share/cmake-3.18/Help/module/UseJavaClassFilelist.rst b/share/cmake-3.18/Help/module/UseJavaClassFilelist.rst deleted file mode 100644 index b9cd476..0000000 --- a/share/cmake-3.18/Help/module/UseJavaClassFilelist.rst +++ /dev/null
@@ -1 +0,0 @@ -.. cmake-module:: ../../Modules/UseJavaClassFilelist.cmake
diff --git a/share/cmake-3.18/Help/module/UseJavaSymlinks.rst b/share/cmake-3.18/Help/module/UseJavaSymlinks.rst deleted file mode 100644 index 2fab8e8..0000000 --- a/share/cmake-3.18/Help/module/UseJavaSymlinks.rst +++ /dev/null
@@ -1 +0,0 @@ -.. cmake-module:: ../../Modules/UseJavaSymlinks.cmake
diff --git a/share/cmake-3.18/Help/policy/CMP0026.rst b/share/cmake-3.18/Help/policy/CMP0026.rst deleted file mode 100644 index 3401d4a..0000000 --- a/share/cmake-3.18/Help/policy/CMP0026.rst +++ /dev/null
@@ -1,29 +0,0 @@ -CMP0026 -------- - -Disallow use of the LOCATION property for build targets. - -CMake 2.8.12 and lower allowed reading the :prop_tgt:`LOCATION` target -property (and configuration-specific variants) to -determine the eventual location of build targets. This relies on the -assumption that all necessary information is available at -configure-time to determine the final location and filename of the -target. However, this property is not fully determined until later at -generate-time. At generate time, the ``$<TARGET_FILE>`` generator -expression can be used to determine the eventual :prop_tgt:`LOCATION` of a target -output. - -Code which reads the :prop_tgt:`LOCATION` target property can be ported to -use the ``$<TARGET_FILE>`` generator expression together with the -:command:`file(GENERATE)` subcommand to generate a file containing -the target location. - -The ``OLD`` behavior for this policy is to allow reading the :prop_tgt:`LOCATION` -properties from build-targets. The ``NEW`` behavior for this policy is to -not to allow reading the :prop_tgt:`LOCATION` properties from build-targets. - -This policy was introduced in CMake version 3.0. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. Use -the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0051.rst b/share/cmake-3.18/Help/policy/CMP0051.rst deleted file mode 100644 index 6b679e5..0000000 --- a/share/cmake-3.18/Help/policy/CMP0051.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0051 -------- - -List TARGET_OBJECTS in SOURCES target property. - -CMake 3.0 and lower did not include the ``TARGET_OBJECTS`` -:manual:`generator expression <cmake-generator-expressions(7)>` when -returning the :prop_tgt:`SOURCES` target property. - -Configure-time CMake code is not able to handle generator expressions. If -using the :prop_tgt:`SOURCES` target property at configure time, it may be -necessary to first remove generator expressions using the -:command:`string(GENEX_STRIP)` command. Generate-time CMake code such as -:command:`file(GENERATE)` can handle the content without stripping. - -The ``OLD`` behavior for this policy is to omit ``TARGET_OBJECTS`` -expressions from the :prop_tgt:`SOURCES` target property. The ``NEW`` -behavior for this policy is to include ``TARGET_OBJECTS`` expressions -in the output. - -This policy was introduced in CMake version 3.1. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set it -to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0052.rst b/share/cmake-3.18/Help/policy/CMP0052.rst deleted file mode 100644 index ee2e6e8..0000000 --- a/share/cmake-3.18/Help/policy/CMP0052.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMP0052 -------- - -Reject source and build dirs in installed -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES`. - -CMake 3.0 and lower allowed subdirectories of the source directory or build -directory to be in the :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of -installed and exported targets, if the directory was also a subdirectory of -the installation prefix. This makes the installation depend on the -existence of the source dir or binary dir, and the installation will be -broken if either are removed after installation. - -See :ref:`Include Directories and Usage Requirements` for more on -specifying include directories for targets. - -The ``OLD`` behavior for this policy is to export the content of the -:prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` with the source or binary -directory. The ``NEW`` behavior for this -policy is to issue an error if such a directory is used. - -This policy was introduced in CMake version 3.1. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set it -to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0053.rst b/share/cmake-3.18/Help/policy/CMP0053.rst deleted file mode 100644 index 032b3e5..0000000 --- a/share/cmake-3.18/Help/policy/CMP0053.rst +++ /dev/null
@@ -1,50 +0,0 @@ -CMP0053 -------- - -Simplify variable reference and escape sequence evaluation. - -CMake 3.1 introduced a much faster implementation of evaluation of the -:ref:`Variable References` and :ref:`Escape Sequences` documented in the -:manual:`cmake-language(7)` manual. While the behavior is identical -to the legacy implementation in most cases, some corner cases were -cleaned up to simplify the behavior. Specifically: - -* Expansion of ``@VAR@`` reference syntax defined by the - :command:`configure_file` and :command:`string(CONFIGURE)` - commands is no longer performed in other contexts. - -* Literal ``${VAR}`` reference syntax may contain only - alphanumeric characters (``A-Z``, ``a-z``, ``0-9``) and - the characters ``_``, ``.``, ``/``, ``-``, and ``+``. - Note that ``$`` is technically allowed in the ``NEW`` behavior, but is - invalid for ``OLD`` behavior. This is due to an oversight during the - implementation of :policy:`CMP0053` and its use as a literal variable - reference is discouraged for this reason. - Variables with other characters in their name may still - be referenced indirectly, e.g. - - .. code-block:: cmake - - set(varname "otherwise & disallowed $ characters") - message("${${varname}}") - -* The setting of policy :policy:`CMP0010` is not considered, - so improper variable reference syntax is always an error. - -* More characters are allowed to be escaped in variable names. - Previously, only ``()#" \@^`` were valid characters to - escape. Now any non-alphanumeric, non-semicolon, non-NUL - character may be escaped following the ``escape_identity`` - production in the :ref:`Escape Sequences` section of the - :manual:`cmake-language(7)` manual. - -The ``OLD`` behavior for this policy is to honor the legacy behavior for -variable references and escape sequences. The ``NEW`` behavior is to -use the simpler variable expansion and escape sequence evaluation rules. - -This policy was introduced in CMake version 3.1. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set -it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0054.rst b/share/cmake-3.18/Help/policy/CMP0054.rst deleted file mode 100644 index 1e000a6..0000000 --- a/share/cmake-3.18/Help/policy/CMP0054.rst +++ /dev/null
@@ -1,52 +0,0 @@ -CMP0054 -------- - -Only interpret :command:`if` arguments as variables or keywords when unquoted. - -CMake 3.1 and above no longer implicitly dereference variables or -interpret keywords in an :command:`if` command argument when -it is a :ref:`Quoted Argument` or a :ref:`Bracket Argument`. - -The ``OLD`` behavior for this policy is to dereference variables and -interpret keywords even if they are quoted or bracketed. -The ``NEW`` behavior is to not dereference variables or interpret keywords -that have been quoted or bracketed. - -Given the following partial example: - -:: - - set(A E) - set(E "") - - if("${A}" STREQUAL "") - message("Result is TRUE before CMake 3.1 or when CMP0054 is OLD") - else() - message("Result is FALSE in CMake 3.1 and above if CMP0054 is NEW") - endif() - -After explicit expansion of variables this gives: - -:: - - if("E" STREQUAL "") - -With the policy set to ``OLD`` implicit expansion reduces this semantically to: - -:: - - if("" STREQUAL "") - -With the policy set to ``NEW`` the quoted arguments will not be -further dereferenced: - -:: - - if("E" STREQUAL "") - -This policy was introduced in CMake version 3.1. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set -it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0055.rst b/share/cmake-3.18/Help/policy/CMP0055.rst deleted file mode 100644 index bc5ad08..0000000 --- a/share/cmake-3.18/Help/policy/CMP0055.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0055 -------- - -Strict checking for the :command:`break` command. - -CMake 3.1 and lower allowed calls to the :command:`break` command -outside of a loop context and also ignored any given arguments. -This was undefined behavior. - -The ``OLD`` behavior for this policy is to allow :command:`break` to be placed -outside of loop contexts and ignores any arguments. The ``NEW`` behavior for this -policy is to issue an error if a misplaced break or any arguments are found. - -This policy was introduced in CMake version 3.2. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set it to ``OLD`` or -``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0056.rst b/share/cmake-3.18/Help/policy/CMP0056.rst deleted file mode 100644 index 834da84..0000000 --- a/share/cmake-3.18/Help/policy/CMP0056.rst +++ /dev/null
@@ -1,34 +0,0 @@ -CMP0056 -------- - -Honor link flags in :command:`try_compile` source-file signature. - -The :command:`try_compile` command source-file signature generates a -``CMakeLists.txt`` file to build the source file into an executable. -In order to compile the source the same way as it might be compiled -by the calling project, the generated project sets the value of the -:variable:`CMAKE_<LANG>_FLAGS` variable to that in the calling project. -The value of the :variable:`CMAKE_EXE_LINKER_FLAGS` variable may be -needed in some cases too, but CMake 3.1 and lower did not set it in -the generated project. CMake 3.2 and above prefer to set it so that -linker flags are honored as well as compiler flags. This policy -provides compatibility with the pre-3.2 behavior. - -The ``OLD`` behavior for this policy is to not set the value of the -:variable:`CMAKE_EXE_LINKER_FLAGS` variable in the generated test -project. The ``NEW`` behavior for this policy is to set the value of -the :variable:`CMAKE_EXE_LINKER_FLAGS` variable in the test project -to the same as it is in the calling project. - -If the project code does not set the policy explicitly, users may -set it on the command line by defining the -:variable:`CMAKE_POLICY_DEFAULT_CMP0056 <CMAKE_POLICY_DEFAULT_CMP<NNNN>>` -variable in the cache. - -This policy was introduced in CMake version 3.2. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0056 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0057.rst b/share/cmake-3.18/Help/policy/CMP0057.rst deleted file mode 100644 index 83db186..0000000 --- a/share/cmake-3.18/Help/policy/CMP0057.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMP0057 -------- - -Support new :command:`if` IN_LIST operator. - -CMake 3.3 adds support for the new IN_LIST operator. - -The ``OLD`` behavior for this policy is to ignore the IN_LIST operator. -The ``NEW`` behavior is to interpret the IN_LIST operator. - -This policy was introduced in CMake version 3.3. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set -it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0058.rst b/share/cmake-3.18/Help/policy/CMP0058.rst deleted file mode 100644 index 05efd48..0000000 --- a/share/cmake-3.18/Help/policy/CMP0058.rst +++ /dev/null
@@ -1,110 +0,0 @@ -CMP0058 -------- - -Ninja requires custom command byproducts to be explicit. - -When an intermediate file generated during the build is consumed -by an expensive operation or a large tree of dependents, one may -reduce the work needed for an incremental rebuild by updating the -file timestamp only when its content changes. With this approach -the generation rule must have a separate output file that is always -updated with a new timestamp that is newer than any dependencies of -the rule so that the build tool re-runs the rule only when the input -changes. We refer to the separate output file as a rule's *witness* -and the generated file as a rule's *byproduct*. - -Byproducts may not be listed as outputs because their timestamps are -allowed to be older than the inputs. No build tools (like ``make``) -that existed when CMake was designed have a way to express byproducts. -Therefore CMake versions prior to 3.2 had no way to specify them. -Projects typically left byproducts undeclared in the rules that -generate them. For example: - -.. code-block:: cmake - - add_custom_command( - OUTPUT witness.txt - COMMAND ${CMAKE_COMMAND} -E copy_if_different - ${CMAKE_CURRENT_SOURCE_DIR}/input.txt - byproduct.txt # timestamp may not change - COMMAND ${CMAKE_COMMAND} -E touch witness.txt - DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/input.txt - ) - add_custom_target(Provider DEPENDS witness.txt) - add_custom_command( - OUTPUT generated.c - COMMAND expensive-task -i byproduct.txt -o generated.c - DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/byproduct.txt - ) - add_library(Consumer generated.c) - add_dependencies(Consumer Provider) - -This works well for all generators except :generator:`Ninja`. -The Ninja build tool sees a rule listing ``byproduct.txt`` -as a dependency and no rule listing it as an output. Ninja then -complains that there is no way to satisfy the dependency and -stops building even though there are order-only dependencies -that ensure ``byproduct.txt`` will exist before its consumers -need it. See discussion of this problem in `Ninja Issue 760`_ -for further details on why Ninja works this way. - -.. _`Ninja Issue 760`: https://github.com/martine/ninja/issues/760 - -Instead of leaving byproducts undeclared in the rules that generate -them, Ninja expects byproducts to be listed along with other outputs. -Such rules may be marked with a ``restat`` option that tells Ninja -to check the timestamps of outputs after the rules run. This -prevents byproducts whose timestamps do not change from causing -their dependents to re-build unnecessarily. - -Since the above approach does not tell CMake what custom command -generates ``byproduct.txt``, the Ninja generator does not have -enough information to add the byproduct as an output of any rule. -CMake 2.8.12 and above work around this problem and allow projects -using the above approach to build by generating ``phony`` build -rules to tell Ninja to tolerate such missing files. However, this -workaround prevents Ninja from diagnosing a dependency that is -really missing. It also works poorly in in-source builds where -every custom command dependency, even on source files, needs to -be treated this way because CMake does not have enough information -to know which files are generated as byproducts of custom commands. - -CMake 3.2 introduced the ``BYPRODUCTS`` option to the -:command:`add_custom_command` and :command:`add_custom_target` -commands. This option allows byproducts to be specified explicitly: - -.. code-block:: cmake - - add_custom_command( - OUTPUT witness.txt - BYPRODUCTS byproduct.txt # explicit byproduct specification - COMMAND ${CMAKE_COMMAND} -E copy_if_different - ${CMAKE_CURRENT_SOURCE_DIR}/input.txt - byproduct.txt # timestamp may not change - ... - -The ``BYPRODUCTS`` option is used by the :generator:`Ninja` generator -to list byproducts among the outputs of the custom commands that -generate them, and is ignored by other generators. - -CMake 3.3 and above prefer to require projects to specify custom -command byproducts explicitly so that it can avoid using the -``phony`` rule workaround altogether. Policy ``CMP0058`` was -introduced to provide compatibility with existing projects that -still need the workaround. - -This policy has no effect on generators other than :generator:`Ninja`. -The ``OLD`` behavior for this policy is to generate Ninja ``phony`` -rules for unknown dependencies in the build tree. The ``NEW`` -behavior for this policy is to not generate these and instead -require projects to specify custom command ``BYPRODUCTS`` explicitly. - -This policy was introduced in CMake version 3.3. -CMake version |release| warns when it sees unknown dependencies in -out-of-source build trees if the policy is not set and then uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set -the policy to ``OLD`` or ``NEW`` explicitly. The policy setting -must be in scope at the end of the top-level ``CMakeLists.txt`` -file of the project and has global effect. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0059.rst b/share/cmake-3.18/Help/policy/CMP0059.rst deleted file mode 100644 index bce982e..0000000 --- a/share/cmake-3.18/Help/policy/CMP0059.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0059 -------- - -Do not treat ``DEFINITIONS`` as a built-in directory property. - -CMake 3.3 and above no longer make a list of definitions available through -the :prop_dir:`DEFINITIONS` directory property. The -:prop_dir:`COMPILE_DEFINITIONS` directory property may be used instead. - -The ``OLD`` behavior for this policy is to provide the list of flags given -so far to the :command:`add_definitions` command. The ``NEW`` behavior is -to behave as a normal user-defined directory property. - -This policy was introduced in CMake version 3.3. -CMake version |release| warns when the policy is not set and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set -it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0060.rst b/share/cmake-3.18/Help/policy/CMP0060.rst deleted file mode 100644 index 98ac2cf..0000000 --- a/share/cmake-3.18/Help/policy/CMP0060.rst +++ /dev/null
@@ -1,65 +0,0 @@ -CMP0060 -------- - -Link libraries by full path even in implicit directories. - -Policy :policy:`CMP0003` was introduced with the intention of always -linking library files by full path when a full path is given to the -:command:`target_link_libraries` command. However, on some platforms -(e.g. HP-UX) the compiler front-end adds alternative library search paths -for the current architecture (e.g. ``/usr/lib/<arch>`` has alternatives -to libraries in ``/usr/lib`` for the current architecture). -On such platforms the :command:`find_library` may find a library such as -``/usr/lib/libfoo.so`` that does not belong to the current architecture. - -Prior to policy :policy:`CMP0003` projects would still build in such -cases because the incorrect library path would be converted to ``-lfoo`` -on the link line and the linker would find the proper library in the -arch-specific search path provided by the compiler front-end implicitly. -At the time we chose to remain compatible with such projects by always -converting library files found in implicit link directories to ``-lfoo`` -flags to ask the linker to search for them. This approach allowed existing -projects to continue to build while still linking to libraries outside -implicit link directories via full path (such as those in the build tree). - -CMake does allow projects to override this behavior by using an -:ref:`IMPORTED library target <Imported Targets>` with its -:prop_tgt:`IMPORTED_LOCATION` property set to the desired full path to -a library file. In fact, many :ref:`Find Modules` are learning to provide -:ref:`Imported Targets` instead of just the traditional ``Foo_LIBRARIES`` -variable listing library files. However, this makes the link line -generated for a library found by a Find Module depend on whether it -is linked through an imported target or not, which is inconsistent. -Furthermore, this behavior has been a source of confusion because the -generated link line for a library file depends on its location. It is -also problematic for projects trying to link statically because flags -like ``-Wl,-Bstatic -lfoo -Wl,-Bdynamic`` may be used to help the linker -select ``libfoo.a`` instead of ``libfoo.so`` but then leak dynamic linking -to following libraries. (See the :prop_tgt:`LINK_SEARCH_END_STATIC` -target property for a solution typically used for that problem.) - -When the special case for libraries in implicit link directories was first -introduced the list of implicit link directories was simply hard-coded -(e.g. ``/lib``, ``/usr/lib``, and a few others). Since that time, CMake -has learned to detect the implicit link directories used by the compiler -front-end. If necessary, the :command:`find_library` command could be -taught to use this information to help find libraries of the proper -architecture. - -For these reasons, CMake 3.3 and above prefer to drop the special case -and link libraries by full path even when they are in implicit link -directories. Policy ``CMP0060`` provides compatibility for existing -projects. - -The ``OLD`` behavior for this policy is to ask the linker to search for -libraries whose full paths are known to be in implicit link directories. -The ``NEW`` behavior for this policy is to link libraries by full path even -if they are in implicit link directories. - -This policy was introduced in CMake version 3.3. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0060 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0061.rst b/share/cmake-3.18/Help/policy/CMP0061.rst deleted file mode 100644 index 57e4161..0000000 --- a/share/cmake-3.18/Help/policy/CMP0061.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0061 -------- - -CTest does not by default tell ``make`` to ignore errors (``-i``). - -The :command:`ctest_build` and :command:`build_command` commands no -longer generate build commands for :ref:`Makefile Generators` with -the ``-i`` option. Previously this was done to help build as much -of tested projects as possible. However, this behavior is not -consistent with other generators and also causes the return code -of the ``make`` tool to be meaningless. - -Of course users may still add this option manually by setting -:variable:`CTEST_BUILD_COMMAND` or the ``MAKECOMMAND`` cache entry. -See the :ref:`CTest Build Step` ``MakeCommand`` setting documentation -for their effects. - -The ``OLD`` behavior for this policy is to add ``-i`` to ``make`` -calls in CTest. The ``NEW`` behavior for this policy is to not -add ``-i``. - -This policy was introduced in CMake version 3.3. Unlike most policies, -CMake version |release| does *not* warn when this policy is not set and -simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0062.rst b/share/cmake-3.18/Help/policy/CMP0062.rst deleted file mode 100644 index 0db7aaf..0000000 --- a/share/cmake-3.18/Help/policy/CMP0062.rst +++ /dev/null
@@ -1,29 +0,0 @@ -CMP0062 -------- - -Disallow :command:`install` of :command:`export` result. - -The :command:`export()` command generates a file containing -:ref:`Imported Targets`, which is suitable for use from the build -directory. It is not suitable for installation because it contains absolute -paths to buildsystem locations, and is particular to a single build -configuration. - -The :command:`install(EXPORT)` generates and installs files which contain -:ref:`Imported Targets`. These files are generated with relative paths -(unless the user specifies absolute paths), and are designed for -multi-configuration use. See :ref:`Creating Packages` for more. - -CMake 3.3 no longer allows the use of the :command:`install(FILES)` command -with the result of the :command:`export()` command. - -The ``OLD`` behavior for this policy is to allow installing the result of -an :command:`export()` command. The ``NEW`` behavior for this policy is -not to allow installing the result of an :command:`export()` command. - -This policy was introduced in CMake version 3.3. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. Use -the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0063.rst b/share/cmake-3.18/Help/policy/CMP0063.rst deleted file mode 100644 index d736d06..0000000 --- a/share/cmake-3.18/Help/policy/CMP0063.rst +++ /dev/null
@@ -1,28 +0,0 @@ -CMP0063 -------- - -Honor visibility properties for all target types. - -The :prop_tgt:`<LANG>_VISIBILITY_PRESET` and -:prop_tgt:`VISIBILITY_INLINES_HIDDEN` target properties affect visibility -of symbols during dynamic linking. When first introduced these properties -affected compilation of sources only in shared libraries, module libraries, -and executables with the :prop_tgt:`ENABLE_EXPORTS` property set. This -was sufficient for the basic use cases of shared libraries and executables -with plugins. However, some sources may be compiled as part of static -libraries or object libraries and then linked into a shared library later. -CMake 3.3 and above prefer to honor these properties for sources compiled -in all target types. This policy preserves compatibility for projects -expecting the properties to work only for some target types. - -The ``OLD`` behavior for this policy is to ignore the visibility properties -for static libraries, object libraries, and executables without exports. -The ``NEW`` behavior for this policy is to honor the visibility properties -for all target types. - -This policy was introduced in CMake version 3.3. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. Use -the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0064.rst b/share/cmake-3.18/Help/policy/CMP0064.rst deleted file mode 100644 index e9a061b..0000000 --- a/share/cmake-3.18/Help/policy/CMP0064.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMP0064 -------- - -Recognize ``TEST`` as a operator for the :command:`if` command. - -The ``TEST`` operator was added to the :command:`if` command to determine if a -given test name was created by the :command:`add_test` command. - -The ``OLD`` behavior for this policy is to ignore the ``TEST`` operator. -The ``NEW`` behavior is to interpret the ``TEST`` operator. - -This policy was introduced in CMake version 3.4. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. Use -the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0065.rst b/share/cmake-3.18/Help/policy/CMP0065.rst deleted file mode 100644 index b820aad..0000000 --- a/share/cmake-3.18/Help/policy/CMP0065.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMP0065 -------- - -Do not add flags to export symbols from executables without -the :prop_tgt:`ENABLE_EXPORTS` target property. - -CMake 3.3 and below, for historical reasons, always linked executables -on some platforms with flags like ``-rdynamic`` to export symbols from -the executables for use by any plugins they may load via ``dlopen``. -CMake 3.4 and above prefer to do this only for executables that are -explicitly marked with the :prop_tgt:`ENABLE_EXPORTS` target property. - -The ``OLD`` behavior of this policy is to always use the additional link -flags when linking executables regardless of the value of the -:prop_tgt:`ENABLE_EXPORTS` target property. - -The ``NEW`` behavior of this policy is to only use the additional link -flags when linking executables if the :prop_tgt:`ENABLE_EXPORTS` target -property is set to ``True``. - -This policy was introduced in CMake version 3.4. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0065 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0066.rst b/share/cmake-3.18/Help/policy/CMP0066.rst deleted file mode 100644 index e110ae1..0000000 --- a/share/cmake-3.18/Help/policy/CMP0066.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMP0066 -------- - -Honor per-config flags in :command:`try_compile` source-file signature. - -The source file signature of the :command:`try_compile` command uses the value -of the :variable:`CMAKE_<LANG>_FLAGS` variable in the test project so that the -test compilation works as it would in the main project. However, CMake 3.6 and -below do not also honor config-specific compiler flags such as those in the -:variable:`CMAKE_<LANG>_FLAGS_DEBUG` variable. CMake 3.7 and above prefer to -honor config-specific compiler flags too. This policy provides compatibility -for projects that do not expect config-specific compiler flags to be used. - -The ``OLD`` behavior of this policy is to ignore config-specific flag -variables like :variable:`CMAKE_<LANG>_FLAGS_DEBUG` and only use CMake's -built-in defaults for the current compiler and platform. - -The ``NEW`` behavior of this policy is to honor config-specific flag -variabldes like :variable:`CMAKE_<LANG>_FLAGS_DEBUG`. - -This policy was introduced in CMake version 3.7. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0066 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0067.rst b/share/cmake-3.18/Help/policy/CMP0067.rst deleted file mode 100644 index f802787..0000000 --- a/share/cmake-3.18/Help/policy/CMP0067.rst +++ /dev/null
@@ -1,37 +0,0 @@ -CMP0067 -------- - -Honor language standard in :command:`try_compile` source-file signature. - -The :command:`try_compile` source file signature is intended to allow -callers to check whether they will be able to compile a given source file -with the current toolchain. In order to match compiler behavior, any -language standard mode should match. However, CMake 3.7 and below did not -do this. CMake 3.8 and above prefer to honor the language standard settings -for ``C``, ``CXX`` (C++), and ``CUDA`` using the values of the variables: - -* :variable:`CMAKE_C_STANDARD` -* :variable:`CMAKE_C_STANDARD_REQUIRED` -* :variable:`CMAKE_C_EXTENSIONS` -* :variable:`CMAKE_CXX_STANDARD` -* :variable:`CMAKE_CXX_STANDARD_REQUIRED` -* :variable:`CMAKE_CXX_EXTENSIONS` -* :variable:`CMAKE_CUDA_STANDARD` -* :variable:`CMAKE_CUDA_STANDARD_REQUIRED` -* :variable:`CMAKE_CUDA_EXTENSIONS` - -This policy provides compatibility for projects that do not expect -the language standard settings to be used automatically. - -The ``OLD`` behavior of this policy is to ignore language standard -setting variables when generating the ``try_compile`` test project. -The ``NEW`` behavior of this policy is to honor language standard -setting variables. - -This policy was introduced in CMake version 3.8. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0067 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0068.rst b/share/cmake-3.18/Help/policy/CMP0068.rst deleted file mode 100644 index 978a6e3..0000000 --- a/share/cmake-3.18/Help/policy/CMP0068.rst +++ /dev/null
@@ -1,35 +0,0 @@ -CMP0068 -------- - -``RPATH`` settings on macOS do not affect ``install_name``. - -CMake 3.9 and newer remove any effect the following settings may have on the -``install_name`` of a target on macOS: - -* :prop_tgt:`BUILD_WITH_INSTALL_RPATH` target property -* :prop_tgt:`SKIP_BUILD_RPATH` target property -* :variable:`CMAKE_SKIP_RPATH` variable -* :variable:`CMAKE_SKIP_INSTALL_RPATH` variable - -Previously, setting :prop_tgt:`BUILD_WITH_INSTALL_RPATH` had the effect of -setting both the ``install_name`` of a target to :prop_tgt:`INSTALL_NAME_DIR` -and the ``RPATH`` to :prop_tgt:`INSTALL_RPATH`. In CMake 3.9, it only affects -setting of ``RPATH``. However, if one wants :prop_tgt:`INSTALL_NAME_DIR` to -apply to the target in the build tree, one may set -:prop_tgt:`BUILD_WITH_INSTALL_NAME_DIR`. - -If :prop_tgt:`SKIP_BUILD_RPATH`, :variable:`CMAKE_SKIP_RPATH` or -:variable:`CMAKE_SKIP_INSTALL_RPATH` were used to strip the directory portion -of the ``install_name`` of a target, one may set ``INSTALL_NAME_DIR=""`` -instead. - -The ``OLD`` behavior of this policy is to use the ``RPATH`` settings for -``install_name`` on macOS. The ``NEW`` behavior of this policy is to ignore -the ``RPATH`` settings for ``install_name`` on macOS. - -This policy was introduced in CMake version 3.9. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0069.rst b/share/cmake-3.18/Help/policy/CMP0069.rst deleted file mode 100644 index 0d5ddfd..0000000 --- a/share/cmake-3.18/Help/policy/CMP0069.rst +++ /dev/null
@@ -1,92 +0,0 @@ -CMP0069 -------- - -:prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` is enforced when enabled. - -CMake 3.9 and newer prefer to add IPO flags whenever the -:prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` target property is enabled and -produce an error if flags are not known to CMake for the current compiler. -Since a given compiler may not support IPO flags in all environments in which -it is used, it is now the project's responsibility to use the -:module:`CheckIPOSupported` module to check for support before enabling the -:prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` target property. This approach -allows a project to conditionally activate IPO when supported. It also -allows an end user to set the :variable:`CMAKE_INTERPROCEDURAL_OPTIMIZATION` -variable in an environment known to support IPO even if the project does -not enable the property. - -Since CMake 3.8 and lower only honored :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` -for the Intel compiler on Linux, some projects may unconditionally enable the -target property. Policy ``CMP0069`` provides compatibility with such projects. - -This policy takes effect whenever the IPO property is enabled. The ``OLD`` -behavior for this policy is to add IPO flags only for Intel compiler on Linux. -The ``NEW`` behavior for this policy is to add IPO flags for the current -compiler or produce an error if CMake does not know the flags. - -This policy was introduced in CMake version 3.9. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt - -Examples -^^^^^^^^ - -Behave like CMake 3.8 and do not apply any IPO flags except for Intel compiler -on Linux: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.8) - project(foo) - - # ... - - set_property(TARGET ... PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE) - -Use the :module:`CheckIPOSupported` module to detect whether IPO is -supported by the current compiler, environment, and CMake version. -Produce a fatal error if support is not available: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.9) # CMP0069 NEW - project(foo) - - include(CheckIPOSupported) - check_ipo_supported() - - # ... - - set_property(TARGET ... PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE) - -Apply IPO flags only if compiler supports it: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.9) # CMP0069 NEW - project(foo) - - include(CheckIPOSupported) - - # ... - - check_ipo_supported(RESULT result) - if(result) - set_property(TARGET ... PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE) - endif() - -Apply IPO flags without any checks. This may lead to build errors if IPO -is not supported by the compiler in the current environment. Produce an -error if CMake does not know IPO flags for the current compiler: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.9) # CMP0069 NEW - project(foo) - - # ... - - set_property(TARGET ... PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE)
diff --git a/share/cmake-3.18/Help/policy/CMP0070.rst b/share/cmake-3.18/Help/policy/CMP0070.rst deleted file mode 100644 index 0fb3617..0000000 --- a/share/cmake-3.18/Help/policy/CMP0070.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMP0070 -------- - -Define :command:`file(GENERATE)` behavior for relative paths. - -CMake 3.10 and newer define that relative paths given to ``INPUT`` and -``OUTPUT`` arguments of ``file(GENERATE)`` are interpreted relative to the -current source and binary directories, respectively. CMake 3.9 and lower did -not define any behavior for relative paths but did not diagnose them either -and accidentally treated them relative to the process working directory. -Policy ``CMP0070`` provides compatibility with projects that used the old -undefined behavior. - -This policy affects behavior of relative paths given to ``file(GENERATE)``. -The ``OLD`` behavior for this policy is to treat the paths relative to the -working directory of CMake. The ``NEW`` behavior for this policy is to -interpret relative paths with respect to the current source or binary -directory of the caller. - -This policy was introduced in CMake version 3.10. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0071.rst b/share/cmake-3.18/Help/policy/CMP0071.rst deleted file mode 100644 index 855ecf0..0000000 --- a/share/cmake-3.18/Help/policy/CMP0071.rst +++ /dev/null
@@ -1,42 +0,0 @@ -CMP0071 -------- - -Let :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` process -:prop_sf:`GENERATED` files. - -Since version 3.10, CMake processes **regular** and :prop_sf:`GENERATED` -source files in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. -In earlier CMake versions, only **regular** source files were processed. -:prop_sf:`GENERATED` source files were ignored silently. - -This policy affects how source files that are :prop_sf:`GENERATED` -get treated in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -The ``OLD`` behavior for this policy is to ignore :prop_sf:`GENERATED` -source files in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -The ``NEW`` behavior for this policy is to process :prop_sf:`GENERATED` -source files in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` just like regular -source files. - -.. note:: - - To silence the ``CMP0071`` warning source files can be excluded from - :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` processing by setting the - source file properties :prop_sf:`SKIP_AUTOMOC`, :prop_sf:`SKIP_AUTOUIC` or - :prop_sf:`SKIP_AUTOGEN`. - -Source skip example:: - - # ... - set_property(SOURCE /path/to/file1.h PROPERTY SKIP_AUTOMOC ON) - set_property(SOURCE /path/to/file2.h PROPERTY SKIP_AUTOUIC ON) - set_property(SOURCE /path/to/file3.h PROPERTY SKIP_AUTOGEN ON) - # ... - -This policy was introduced in CMake version 3.10. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0072.rst b/share/cmake-3.18/Help/policy/CMP0072.rst deleted file mode 100644 index 3abbad7..0000000 --- a/share/cmake-3.18/Help/policy/CMP0072.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0072 -------- - -:module:`FindOpenGL` prefers GLVND by default when available. - -The :module:`FindOpenGL` module provides an ``OpenGL::GL`` target and an -``OPENGL_LIBRARIES`` variable for projects to use for legacy GL interfaces. -When both a legacy GL library (e.g. ``libGL.so``) and GLVND libraries -for OpenGL and GLX (e.g. ``libOpenGL.so`` and ``libGLX.so``) are available, -the module must choose between them. It documents an ``OpenGL_GL_PREFERENCE`` -variable that can be used to specify an explicit preference. When no such -preference is set, the module must choose a default preference. - -CMake 3.11 and above prefer to choose GLVND libraries. This policy provides -compatibility with projects that expect the legacy GL library to be used. - -The ``OLD`` behavior for this policy is to set ``OpenGL_GL_PREFERENCE`` to -``LEGACY``. The ``NEW`` behavior for this policy is to set -``OpenGL_GL_PREFERENCE`` to ``GLVND``. - -This policy was introduced in CMake version 3.11. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0073.rst b/share/cmake-3.18/Help/policy/CMP0073.rst deleted file mode 100644 index 9bfa0e9..0000000 --- a/share/cmake-3.18/Help/policy/CMP0073.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMP0073 -------- - -Do not produce legacy ``_LIB_DEPENDS`` cache entries. - -Ancient CMake versions once used ``<tgt>_LIB_DEPENDS`` cache entries to -propagate library link dependencies. This has long been done by other -means, leaving the :command:`export_library_dependencies` command as the -only user of these values. That command has long been disallowed by -policy :policy:`CMP0033`, but the ``<tgt>_LIB_DEPENDS`` cache entries -were left for compatibility with possible non-standard uses by projects. - -CMake 3.12 and above now prefer to not produce these cache entries -at all. This policy provides compatibility with projects that have -not been updated to avoid using them. - -The ``OLD`` behavior for this policy is to set ``<tgt>_LIB_DEPENDS`` cache -entries. The ``NEW`` behavior for this policy is to not set them. - -This policy was introduced in CMake version 3.12. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0074.rst b/share/cmake-3.18/Help/policy/CMP0074.rst deleted file mode 100644 index 63ebf7b..0000000 --- a/share/cmake-3.18/Help/policy/CMP0074.rst +++ /dev/null
@@ -1,23 +0,0 @@ -CMP0074 -------- - -:command:`find_package` uses ``<PackageName>_ROOT`` variables. - -In CMake 3.12 and above the :command:`find_package(<PackageName>)` command now -searches prefixes specified by the :variable:`<PackageName>_ROOT` CMake -variable and the :envvar:`<PackageName>_ROOT` environment variable. -Package roots are maintained as a stack so nested calls to all ``find_*`` -commands inside find modules and config packages also search the roots as -prefixes. This policy provides compatibility with projects that have not been -updated to avoid using ``<PackageName>_ROOT`` variables for other purposes. - -The ``OLD`` behavior for this policy is to ignore ``<PackageName>_ROOT`` -variables. The ``NEW`` behavior for this policy is to use -``<PackageName>_ROOT`` variables. - -This policy was introduced in CMake version 3.12. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0075.rst b/share/cmake-3.18/Help/policy/CMP0075.rst deleted file mode 100644 index aa5c3f7..0000000 --- a/share/cmake-3.18/Help/policy/CMP0075.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0075 -------- - -Include file check macros honor ``CMAKE_REQUIRED_LIBRARIES``. - -In CMake 3.12 and above, the - -* ``check_include_file`` macro in the :module:`CheckIncludeFile` module, the -* ``check_include_file_cxx`` macro in the - :module:`CheckIncludeFileCXX` module, and the -* ``check_include_files`` macro in the :module:`CheckIncludeFiles` module - -now prefer to link the check executable to the libraries listed in the -``CMAKE_REQUIRED_LIBRARIES`` variable. This policy provides compatibility -with projects that have not been updated to expect this behavior. - -The ``OLD`` behavior for this policy is to ignore ``CMAKE_REQUIRED_LIBRARIES`` -in the include file check macros. The ``NEW`` behavior of this policy is to -honor ``CMAKE_REQUIRED_LIBRARIES`` in the include file check macros. - -This policy was introduced in CMake version 3.12. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0076.rst b/share/cmake-3.18/Help/policy/CMP0076.rst deleted file mode 100644 index dd25f80..0000000 --- a/share/cmake-3.18/Help/policy/CMP0076.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0076 -------- - -The :command:`target_sources` command converts relative paths to absolute. - -In CMake 3.13 and above, the :command:`target_sources` command now converts -relative source file paths to absolute paths in the following cases: - -* Source files are added to the target's :prop_tgt:`INTERFACE_SOURCES` - property. -* The target's :prop_tgt:`SOURCE_DIR` property differs from - :variable:`CMAKE_CURRENT_SOURCE_DIR`. - -A path that begins with a generator expression is always left unmodified. - -This policy provides compatibility with projects that have not been updated -to expect this behavior. The ``OLD`` behavior for this policy is to leave -all relative source file paths unmodified. The ``NEW`` behavior of this -policy is to convert relative paths to absolute according to above rules. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0077.rst b/share/cmake-3.18/Help/policy/CMP0077.rst deleted file mode 100644 index 44797b6..0000000 --- a/share/cmake-3.18/Help/policy/CMP0077.rst +++ /dev/null
@@ -1,52 +0,0 @@ -CMP0077 -------- - -:command:`option` honors normal variables. - -The :command:`option` command is typically used to create a cache entry -to allow users to set the option. However, there are cases in which a -normal (non-cached) variable of the same name as the option may be -defined by the project prior to calling the :command:`option` command. -For example, a project that embeds another project as a subdirectory -may want to hard-code options of the subproject to build the way it needs. - -For historical reasons in CMake 3.12 and below the :command:`option` -command *removes* a normal (non-cached) variable of the same name when: - -* a cache entry of the specified name does not exist at all, or -* a cache entry of the specified name exists but has not been given - a type (e.g. via ``-D<name>=ON`` on the command line). - -In both of these cases (typically on the first run in a new build tree), -the :command:`option` command gives the cache entry type ``BOOL`` and -removes any normal (non-cached) variable of the same name. In the -remaining case that the cache entry of the specified name already -exists and has a type (typically on later runs in a build tree), the -:command:`option` command changes nothing and any normal variable of -the same name remains set. - -In CMake 3.13 and above the :command:`option` command prefers to -do nothing when a normal variable of the given name already exists. -It does not create or update a cache entry or remove the normal variable. -The new behavior is consistent between the first and later runs in a -build tree. This policy provides compatibility with projects that have -not been updated to expect the new behavior. - -When the :command:`option` command sees a normal variable of the given -name: - -* The ``OLD`` behavior for this policy is to proceed even when a normal - variable of the same name exists. If the cache entry does not already - exist and have a type then it is created and/or given a type and the - normal variable is removed. - -* The ``NEW`` behavior for this policy is to do nothing when a normal - variable of the same name exists. The normal variable is not removed. - The cache entry is not created or updated and is ignored if it exists. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0078.rst b/share/cmake-3.18/Help/policy/CMP0078.rst deleted file mode 100644 index 2e97934..0000000 --- a/share/cmake-3.18/Help/policy/CMP0078.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMP0078 -------- - -:module:`UseSWIG` generates standard target names. - -Starting with CMake 3.13, :module:`UseSWIG` generates now standard target -names. This policy provides compatibility with projects that expect the legacy -behavior. - -The ``OLD`` behavior for this policy relies on -``UseSWIG_TARGET_NAME_PREFERENCE`` variable that can be used to specify an -explicit preference. The value may be one of: - -* ``LEGACY``: legacy strategy is applied. Variable - ``SWIG_MODULE_<name>_REAL_NAME`` must be used to get real target name. - This is the default if not specified. -* ``STANDARD``: target name matches specified name. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0079.rst b/share/cmake-3.18/Help/policy/CMP0079.rst deleted file mode 100644 index 0244d6c..0000000 --- a/share/cmake-3.18/Help/policy/CMP0079.rst +++ /dev/null
@@ -1,40 +0,0 @@ -CMP0079 -------- - -:command:`target_link_libraries` allows use with targets in other directories. - -Prior to CMake 3.13 the :command:`target_link_libraries` command did not -accept targets not created in the calling directory as its first argument -for calls that update the :prop_tgt:`LINK_LIBRARIES` of the target itself. -It did accidentally accept targets from other directories on calls that -only update the :prop_tgt:`INTERFACE_LINK_LIBRARIES`, but would simply -add entries to the property as if the call were made in the original -directory. Thus link interface libraries specified this way were always -looked up by generators in the scope of the original target rather than -in the scope that called :command:`target_link_libraries`. - -CMake 3.13 now allows the :command:`target_link_libraries` command to -be called from any directory to add link dependencies and link interface -libraries to targets created in other directories. The entries are added -to :prop_tgt:`LINK_LIBRARIES` and :prop_tgt:`INTERFACE_LINK_LIBRARIES` -using a special (internal) suffix to tell the generators to look up the -names in the calling scope rather than the scope that created the target. - -This policy provides compatibility with projects that already use -:command:`target_link_libraries` with the ``INTERFACE`` keyword -on a target in another directory to add :prop_tgt:`INTERFACE_LINK_LIBRARIES` -entries to be looked up in the target's directory. Such projects should -be updated to be aware of the new scoping rules in that case. - -The ``OLD`` behavior of this policy is to disallow -:command:`target_link_libraries` calls naming targets from another directory -except in the previously accidentally allowed case of using the ``INTERFACE`` -keyword only. The ``NEW`` behavior of this policy is to allow all such -calls but use the new scoping rules. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0080.rst b/share/cmake-3.18/Help/policy/CMP0080.rst deleted file mode 100644 index 5ce9591..0000000 --- a/share/cmake-3.18/Help/policy/CMP0080.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMP0080 -------- - -:module:`BundleUtilities` cannot be included at configure time. - -The macros provided by :module:`BundleUtilities` are intended to be invoked -at install time rather than at configure time, because they depend on the -listed targets already existing at the time they are invoked. If they are -invoked at configure time, the targets haven't been built yet, and the -commands will fail. - -This policy restricts the inclusion of :module:`BundleUtilities` to -``cmake -P`` style scripts and install rules. Specifically, it looks for the -presence of :variable:`CMAKE_GENERATOR` and throws a fatal error if it exists. - -The ``OLD`` behavior of this policy is to allow :module:`BundleUtilities` to -be included at configure time. The ``NEW`` behavior of this policy is to -disallow such inclusion. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0081.rst b/share/cmake-3.18/Help/policy/CMP0081.rst deleted file mode 100644 index d3b2872..0000000 --- a/share/cmake-3.18/Help/policy/CMP0081.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMP0081 -------- - -Relative paths not allowed in :prop_tgt:`LINK_DIRECTORIES` target property. - -CMake 3.12 and lower allowed the :prop_dir:`LINK_DIRECTORIES` directory -property to contain relative paths. The base path for such relative -entries is not well defined. CMake 3.13 and later will issue a -``FATAL_ERROR`` if the :prop_tgt:`LINK_DIRECTORIES` target property -(which is initialized by the :prop_dir:`LINK_DIRECTORIES` directory property) -contains a relative path. - -The ``OLD`` behavior for this policy is not to warn about relative paths -in the :prop_tgt:`LINK_DIRECTORIES` target property. The ``NEW`` behavior for -this policy is to issue a ``FATAL_ERROR`` if :prop_tgt:`LINK_DIRECTORIES` -contains a relative path. - -This policy was introduced in CMake version 3.13. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. Use -the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0082.rst b/share/cmake-3.18/Help/policy/CMP0082.rst deleted file mode 100644 index d887616..0000000 --- a/share/cmake-3.18/Help/policy/CMP0082.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0082 -------- - -Install rules from :command:`add_subdirectory` calls are interleaved with -those in caller. - -CMake 3.13 and lower ran the install rules from :command:`add_subdirectory` -after all other install rules, even if :command:`add_subdirectory` was called -before the other install rules. CMake 3.14 and above prefer to interleave -these :command:`add_subdirectory` install rules with the others so that -they are run in the order they are declared. This policy provides -compatibility for projects that have not been updated to expect the -new behavior. - -The ``OLD`` behavior for this policy is to run the install rules from -:command:`add_subdirectory` after the other install rules. The ``NEW`` -behavior for this policy is to run all install rules in the order they are -declared. - -This policy was introduced in CMake version 3.14. Unlike most policies, -CMake version |release| does *not* warn by default when this policy -is not set and simply uses ``OLD`` behavior. See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0082 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0083.rst b/share/cmake-3.18/Help/policy/CMP0083.rst deleted file mode 100644 index e0b09cf..0000000 --- a/share/cmake-3.18/Help/policy/CMP0083.rst +++ /dev/null
@@ -1,69 +0,0 @@ -CMP0083 -------- - -To control generation of Position Independent Executable (``PIE``) or not, some -flags are required at link time. - -CMake 3.13 and lower did not add these link flags when -:prop_tgt:`POSITION_INDEPENDENT_CODE` is set. - -The ``OLD`` behavior for this policy is to not manage ``PIE`` link flags. The -``NEW`` behavior is to add link flags if :prop_tgt:`POSITION_INDEPENDENT_CODE` -is set: - -* Set to ``TRUE``: flags to produce a position independent executable are - passed to the linker step. For example ``-pie`` for ``GCC``. -* Set to ``FALSE``: flags not to produce a position independent executable are - passed to the linker step. For example ``-no-pie`` for ``GCC``. -* Not set: no flags are passed to the linker step. - -Since a given linker may not support ``PIE`` flags in all environments in -which it is used, it is the project's responsibility to use the -:module:`CheckPIESupported` module to check for support to ensure that the -:prop_tgt:`POSITION_INDEPENDENT_CODE` target property for executables will be -honored at link time. - -This policy was introduced in CMake version 3.14. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does not warn when this policy is -not set and simply uses ``OLD`` behavior. - -.. Note:: - - Android platform has a special handling of ``PIE`` so it is not required - to use the :module:`CheckPIESupported` module to ensure flags are passed to - the linker. - -.. include:: DEPRECATED.txt - -Examples -^^^^^^^^ - -Behave like CMake 3.13 and do not apply any ``PIE`` flags at link stage. - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.13) - project(foo) - - # ... - - add_executable(foo ...) - set_property(TARGET foo PROPERTY POSITION_INDEPENDENT_CODE TRUE) - -Use the :module:`CheckPIESupported` module to detect whether ``PIE`` is -supported by the current linker and environment. Apply ``PIE`` flags only -if the linker supports them. - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.14) # CMP0083 NEW - project(foo) - - include(CheckPIESupported) - check_pie_supported() - - # ... - - add_executable(foo ...) - set_property(TARGET foo PROPERTY POSITION_INDEPENDENT_CODE TRUE)
diff --git a/share/cmake-3.18/Help/policy/CMP0084.rst b/share/cmake-3.18/Help/policy/CMP0084.rst deleted file mode 100644 index 713d295..0000000 --- a/share/cmake-3.18/Help/policy/CMP0084.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMP0084 -------- - -The :module:`FindQt` module does not exist for :command:`find_package`. - -The existence of :module:`FindQt` means that for Qt upstream to provide -package config files that can be found by ``find_package(Qt)``, the consuming -project has to explicitly specify ``find_package(Qt CONFIG)``. Removing this -module gives Qt a path forward for exporting its own config files which can -easily be found by consuming projects. - -This policy pretends that CMake's internal :module:`FindQt` module does not -exist for :command:`find_package`. If a project really wants to use Qt 3 or 4, -it can call ``find_package(Qt[34])``, ``include(FindQt)``, or add -:module:`FindQt` to their :variable:`CMAKE_MODULE_PATH`. - -The ``OLD`` behavior of this policy is for :module:`FindQt` to exist for -:command:`find_package`. The ``NEW`` behavior is to pretend that it doesn't -exist for :command:`find_package`. - -This policy was introduced in CMake version 3.14. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0085.rst b/share/cmake-3.18/Help/policy/CMP0085.rst deleted file mode 100644 index d9ec9a2..0000000 --- a/share/cmake-3.18/Help/policy/CMP0085.rst +++ /dev/null
@@ -1,21 +0,0 @@ -CMP0085 -------- - -``$<IN_LIST:...>`` handles empty list items. - -In CMake 3.13 and lower, the ``$<IN_LIST:...>`` generator expression always -returned ``0`` if the first argument was empty, even if the list contained an -empty item. This behavior is inconsistent with the ``IN_LIST`` behavior of -:command:`if`, which this generator expression is meant to emulate. CMake 3.14 -and later handles this case correctly. - -The ``OLD`` behavior of this policy is for ``$<IN_LIST:...>`` to always return -``0`` if the first argument is empty. The ``NEW`` behavior is to return ``1`` -if the first argument is empty and the list contains an empty item. - -This policy was introduced in CMake version 3.14. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0086.rst b/share/cmake-3.18/Help/policy/CMP0086.rst deleted file mode 100644 index 4a9e8b8..0000000 --- a/share/cmake-3.18/Help/policy/CMP0086.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMP0086 -------- - -:module:`UseSWIG` honors ``SWIG_MODULE_NAME`` via ``-module`` flag. - -Starting with CMake 3.14, :module:`UseSWIG` passes option -``-module <module_name>`` to ``SWIG`` compiler if the file property -``SWIG_MODULE_NAME`` is specified. This policy provides compatibility with -projects that expect the legacy behavior. - -The ``OLD`` behavior for this policy is to never pass ``-module`` option. -The ``NEW`` behavior is to pass ``-module`` option to ``SWIG`` compiler if -``SWIG_MODULE_NAME`` is specified. - -This policy was introduced in CMake version 3.14. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0087.rst b/share/cmake-3.18/Help/policy/CMP0087.rst deleted file mode 100644 index 4c45b99..0000000 --- a/share/cmake-3.18/Help/policy/CMP0087.rst +++ /dev/null
@@ -1,29 +0,0 @@ -CMP0087 -------- - -:command:`install(CODE)` and :command:`install(SCRIPT)` support generator -expressions. - -In CMake 3.13 and earlier, :command:`install(CODE)` and -:command:`install(SCRIPT)` did not evaluate generator expressions. CMake 3.14 -and later will evaluate generator expressions for :command:`install(CODE)` and -:command:`install(SCRIPT)`. - -The ``OLD`` behavior of this policy is for :command:`install(CODE)` and -:command:`install(SCRIPT)` to not evaluate generator expressions. The ``NEW`` -behavior is to evaluate generator expressions for :command:`install(CODE)` and -:command:`install(SCRIPT)`. - -Note that it is the value of this policy setting at the end of the directory -scope that is important, not its setting at the time of the call to -:command:`install(CODE)` or :command:`install(SCRIPT)`. This has implications -for calling these commands from places that have their own policy scope but not -their own directory scope (e.g. from files brought in via :command:`include()` -rather than :command:`add_subdirectory()`). - -This policy was introduced in CMake version 3.14. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0088.rst b/share/cmake-3.18/Help/policy/CMP0088.rst deleted file mode 100644 index 82c04ef..0000000 --- a/share/cmake-3.18/Help/policy/CMP0088.rst +++ /dev/null
@@ -1,29 +0,0 @@ -CMP0088 -------- - -:module:`FindBISON` runs bison in :variable:`CMAKE_CURRENT_BINARY_DIR` -when executing. - -The module provides a ``BISON_TARGET`` macro which generates BISON output. -In CMake 3.13 and below the macro would generate a custom command that runs -``bison`` in the source directory. CMake 3.14 and later prefer to run it -in the build directory and use :variable:`CMAKE_CURRENT_BINARY_DIR` as the -``WORKING_DIRECTORY`` of its :command:`add_custom_command` invocation. -This ensures that any implicitly generated file is written to the build -tree rather than the source. - -This policy provides compatibility for projects that have not been updated -to expect the new behavior. - -The ``OLD`` behavior for this policy is for ``BISON_TARGET`` to use -the current source directory for the ``WORKING_DIRECTORY`` and where -to generate implicit files. The ``NEW`` behavior of this policy is to -use the current binary directory for the ``WORKING_DIRECTORY`` and where -to generate implicit files. - -This policy was introduced in CMake version 3.14. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0089.rst b/share/cmake-3.18/Help/policy/CMP0089.rst deleted file mode 100644 index 029de55..0000000 --- a/share/cmake-3.18/Help/policy/CMP0089.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMP0089 -------- - -Compiler id for IBM Clang-based XL compilers is now ``XLClang``. - -CMake 3.15 and above recognize that IBM's Clang-based XL compilers -that define ``__ibmxl__`` are a new front-end distinct from ``xlc`` -with a different command line and set of capabilities. -CMake now prefers to present this to projects by setting the -:variable:`CMAKE_<LANG>_COMPILER_ID` variable to ``XLClang`` instead -of ``XL``. However, existing projects may assume the compiler id for -Clang-based XL is just ``XL`` as it was in CMake versions prior to 3.15. -Therefore this policy determines for Clang-based XL compilers which -compiler id to report in the :variable:`CMAKE_<LANG>_COMPILER_ID` -variable after language ``<LANG>`` is enabled by the :command:`project` -or :command:`enable_language` command. The policy must be set prior -to the invocation of either command. - -The ``OLD`` behavior for this policy is to use compiler id ``XL``. The -``NEW`` behavior for this policy is to use compiler id ``XLClang``. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set this policy to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does *not* warn -by default when this policy is not set and simply uses ``OLD`` behavior. -See documentation of the -:variable:`CMAKE_POLICY_WARNING_CMP0089 <CMAKE_POLICY_WARNING_CMP<NNNN>>` -variable to control the warning. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0090.rst b/share/cmake-3.18/Help/policy/CMP0090.rst deleted file mode 100644 index 720c17c..0000000 --- a/share/cmake-3.18/Help/policy/CMP0090.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMP0090 -------- - -:command:`export(PACKAGE)` does not populate package registry by default. - -In CMake 3.14 and below the :command:`export(PACKAGE)` command populated the -user package registry by default and users needed to set the -:variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` to disable it, e.g. in automated -build and packaging environments. Since the user package registry is stored -outside the build tree, this side effect should not be enabled by default. -Therefore CMake 3.15 and above prefer that :command:`export(PACKAGE)` does -nothing unless an explicit :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` variable -is set to enable it. This policy provides compatibility with projects that -have not been updated. - -The ``OLD`` behavior for this policy is for :command:`export(PACKAGE)` command -to populate the user package registry unless -:variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` is enabled. -The ``NEW`` behavior is for :command:`export(PACKAGE)` command to do nothing -unless the :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` is enabled. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0091.rst b/share/cmake-3.18/Help/policy/CMP0091.rst deleted file mode 100644 index 1a5878a..0000000 --- a/share/cmake-3.18/Help/policy/CMP0091.rst +++ /dev/null
@@ -1,49 +0,0 @@ -CMP0091 -------- - -MSVC runtime library flags are selected by an abstraction. - -Compilers targeting the MSVC ABI have flags to select the MSVC runtime library. -Runtime library selection typically varies with build configuration because -there is a separate runtime library for Debug builds. - -In CMake 3.14 and below, MSVC runtime library selection flags are added to -the default :variable:`CMAKE_<LANG>_FLAGS_<CONFIG>` cache entries by CMake -automatically. This allows users to edit their cache entries to adjust the -flags. However, the presence of such default flags is problematic for -projects that want to choose a different runtime library programmatically. -In particular, it requires string editing of the -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>` variables with knowledge of the -CMake builtin defaults so they can be replaced. - -CMake 3.15 and above prefer to leave the MSVC runtime library selection flags -out of the default :variable:`CMAKE_<LANG>_FLAGS_<CONFIG>` values and instead -offer a first-class abstraction. The :variable:`CMAKE_MSVC_RUNTIME_LIBRARY` -variable and :prop_tgt:`MSVC_RUNTIME_LIBRARY` target property may be set to -select the MSVC runtime library. If they are not set then CMake uses the -default value ``MultiThreaded$<$<CONFIG:Debug>:Debug>DLL`` which is -equivalent to the original flags. - -This policy provides compatibility with projects that have not been updated -to be aware of the abstraction. The policy setting takes effect as of the -first :command:`project` or :command:`enable_language` command that enables -a language whose compiler targets the MSVC ABI. - -.. note:: - - Once the policy has taken effect at the top of a project, that choice - must be used throughout the tree. In projects that have nested projects - in subdirectories, be sure to convert everything together. - -The ``OLD`` behavior for this policy is to place MSVC runtime library -flags in the default :variable:`CMAKE_<LANG>_FLAGS_<CONFIG>` cache -entries and ignore the :variable:`CMAKE_MSVC_RUNTIME_LIBRARY` abstraction. -The ``NEW`` behavior for this policy is to *not* place MSVC runtime -library flags in the default cache entries and use the abstraction instead. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0092.rst b/share/cmake-3.18/Help/policy/CMP0092.rst deleted file mode 100644 index 8d3a288..0000000 --- a/share/cmake-3.18/Help/policy/CMP0092.rst +++ /dev/null
@@ -1,38 +0,0 @@ -CMP0092 -------- - -MSVC warning flags are not in :variable:`CMAKE_<LANG>_FLAGS` by default. - -When using MSVC-like compilers in CMake 3.14 and below, warning flags -like ``/W3`` are added to :variable:`CMAKE_<LANG>_FLAGS` by default. -This is problematic for projects that want to choose a different warning -level programmatically. In particular, it requires string editing of the -:variable:`CMAKE_<LANG>_FLAGS` variables with knowledge of the -CMake builtin defaults so they can be replaced. - -CMake 3.15 and above prefer to leave out warning flags from the value of -:variable:`CMAKE_<LANG>_FLAGS` by default. - -This policy provides compatibility with projects that have not been updated -to expect the lack of warning flags. The policy setting takes effect as of -the first :command:`project` or :command:`enable_language` command that -initializes :variable:`CMAKE_<LANG>_FLAGS` for a given lanuage ``<LANG>``. - -.. note:: - - Once the policy has taken effect at the top of a project for a given - language, that choice must be used throughout the tree for that language. - In projects that have nested projects in subdirectories, be sure to - convert everything together. - -The ``OLD`` behavior for this policy is to place MSVC warning flags in the -default :variable:`CMAKE_<LANG>_FLAGS` cache entries. The ``NEW`` behavior -for this policy is to *not* place MSVC warning flags in the default cache -entries. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0093.rst b/share/cmake-3.18/Help/policy/CMP0093.rst deleted file mode 100644 index 0ffc493..0000000 --- a/share/cmake-3.18/Help/policy/CMP0093.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMP0093 -------- - -:module:`FindBoost` reports ``Boost_VERSION`` in ``x.y.z`` format. - -In CMake 3.14 and below the module would report the Boost version -number as specified in the preprocessor definition ``BOOST_VERSION`` in -the ``boost/version.hpp`` file. In CMake 3.15 and later it is preferred -that the reported version number matches the ``x.y.z`` format reported -by the CMake package shipped with Boost ``1.70.0`` and later. The macro -value is still reported in the ``Boost_VERSION_MACRO`` variable. - -The ``OLD`` behavior for this policy is for :module:`FindBoost` to report -``Boost_VERSION`` as specified in the preprocessor definition -``BOOST_VERSION`` in ``boost/version.hpp``. The ``NEW`` behavior for this -policy is for :module:`FindBoost` to report ``Boost_VERSION`` in -``x.y.z`` format. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses the ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0094.rst b/share/cmake-3.18/Help/policy/CMP0094.rst deleted file mode 100644 index 836f30f..0000000 --- a/share/cmake-3.18/Help/policy/CMP0094.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMP0094 -------- - -Modules :module:`FindPython3`, :module:`FindPython2` and :module:`FindPython` -use ``LOCATION`` for lookup strategy. - -Starting with CMake 3.15, Modules :module:`FindPython3`, :module:`FindPython2` -and :module:`FindPython` set value ``LOCATION`` for, respectively, variables -``Python3_FIND_STRATEGY``, ``Python2_FIND_STRATEGY`` and -``Python_FIND_STRATEGY``. This policy provides compatibility with projects that -expect the legacy behavior. - -The ``OLD`` behavior for this policy set value ``VERSION`` for variables -``Python3_FIND_STRATEGY``, ``Python2_FIND_STRATEGY`` and -``Python_FIND_STRATEGY``. - -This policy was introduced in CMake version 3.15. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses the ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0095.rst b/share/cmake-3.18/Help/policy/CMP0095.rst deleted file mode 100644 index 4c56a05..0000000 --- a/share/cmake-3.18/Help/policy/CMP0095.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMP0095 -------- - -``RPATH`` entries are properly escaped in the intermediary CMake install script. - -In CMake 3.15 and earlier, ``RPATH`` entries set via -:variable:`CMAKE_INSTALL_RPATH` or via :prop_tgt:`INSTALL_RPATH` have not been -escaped before being inserted into the ``cmake_install.cmake`` script. Dynamic -linkers on ELF-based systems (e.g. Linux and FreeBSD) allow certain keywords in -``RPATH`` entries, such as ``${ORIGIN}`` (More details are available in the -``ld.so`` man pages on those systems). The syntax of these keywords can match -CMake's variable syntax. In order to not be substituted (usually to an empty -string) already by the intermediary ``cmake_install.cmake`` script, the user had -to double-escape such ``RPATH`` keywords, e.g. -``set(CMAKE_INSTALL_RPATH "\\\${ORIGIN}/../lib")``. Since the intermediary -``cmake_install.cmake`` script is an implementation detail of CMake, CMake 3.16 -and later will make sure ``RPATH`` entries are inserted literally by escaping -any coincidental CMake syntax. - -The ``OLD`` behavior of this policy is to not escape ``RPATH`` entries in the -intermediary ``cmake_install.cmake`` script. The ``NEW`` behavior is to properly -escape coincidental CMake syntax in ``RPATH`` entries when generating the -intermediary ``cmake_install.cmake`` script. - -This policy was introduced in CMake version 3.16. CMake version |release| warns -when the policy is not set and detected usage of CMake-like syntax and uses -``OLD`` behavior. Use the :command:`cmake_policy` command to set it to ``OLD`` -or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0096.rst b/share/cmake-3.18/Help/policy/CMP0096.rst deleted file mode 100644 index 8eaf0f9..0000000 --- a/share/cmake-3.18/Help/policy/CMP0096.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMP0096 -------- - -The :command:`project` command preserves leading zeros in version components. - -When a ``VERSION <major>[.<minor>[.<patch>[.<tweak>]]]]`` argument is given -to the :command:`project` command, it stores the version string in the -``PROJECT_VERSION`` variable and stores individual integer version components -in ``PROJECT_VERSION_{MAJOR,MINOR,PATCH,TWEAK}`` variables (see policy -:policy:`CMP0048`). CMake 3.15 and below dropped leading zeros from each -component. CMake 3.16 and higher prefer to preserve leading zeros. This -policy provides compatibility for projects that have not been updated to -expect the new behavior. - -The ``OLD`` behavior of this policy drops leading zeros in all components, -e.g. such that version ``1.07.06`` becomes ``1.7.6``. The ``NEW`` behavior -of this policy preserves the leading zeros in all components, such that -version ``1.07.06`` remains unchanged. - -This policy was introduced in CMake version 3.16. Unlike many policies, CMake -version |release| does *not* warn when this policy is not set and simply uses -the ``OLD`` behavior. Use the :command:`cmake_policy` command to set it to -``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0097.rst b/share/cmake-3.18/Help/policy/CMP0097.rst deleted file mode 100644 index 4840aa6..0000000 --- a/share/cmake-3.18/Help/policy/CMP0097.rst +++ /dev/null
@@ -1,23 +0,0 @@ -CMP0097 -------- - -:command:`ExternalProject_Add` with ``GIT_SUBMODULES ""`` initializes no -submodules. - -The module provides a ``GIT_SUBMODULES`` option which controls what submodules -to initialize and update. Starting with CMake 3.16, explicitly setting -``GIT_SUBMODULES`` to an empty string means no submodules will be initialized -or updated. - -This policy provides compatibility for projects that have not been updated -to expect the new behavior. - -The ``OLD`` behavior for this policy is for ``GIT_SUBMODULES`` when set to -an empty string to initialize and update all git submodules. -The ``NEW`` behavior for this policy is for ``GIT_SUBMODULES`` when set to -an empty string to initialize and update no git submodules. - -This policy was introduced in CMake version 3.16. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike most policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior.
diff --git a/share/cmake-3.18/Help/policy/CMP0098.rst b/share/cmake-3.18/Help/policy/CMP0098.rst deleted file mode 100644 index 6d1443b..0000000 --- a/share/cmake-3.18/Help/policy/CMP0098.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMP0098 -------- - -:module:`FindFLEX` runs ``flex`` in directory -:variable:`CMAKE_CURRENT_BINARY_DIR` when executing. - -The module provides a ``FLEX_TARGET`` macro which generates FLEX output. -In CMake 3.16 and below the macro would generate a custom command that runs -``flex`` in the current source directory. CMake 3.17 and later prefer to -run it in the build directory and use :variable:`CMAKE_CURRENT_BINARY_DIR` -as the ``WORKING_DIRECTORY`` of its :command:`add_custom_command` invocation. -This ensures that any implicitly generated file is written relative to the -build tree rather than the source tree, unless the generated file is -provided as absolute path. - -This policy provides compatibility for projects that have not been updated -to expect the new behavior. - -The ``OLD`` behavior for this policy is for ``FLEX_TARGET`` to use -the current source directory for the ``WORKING_DIRECTORY`` and where -to generate implicit files. The ``NEW`` behavior of this policy is to -use the current binary directory for the ``WORKING_DIRECTORY`` relative to -which implicit files are generated unless provided as absolute path. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0099.rst b/share/cmake-3.18/Help/policy/CMP0099.rst deleted file mode 100644 index c897e7b..0000000 --- a/share/cmake-3.18/Help/policy/CMP0099.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMP0099 -------- - -Target link properties :prop_tgt:`INTERFACE_LINK_OPTIONS`, -:prop_tgt:`INTERFACE_LINK_DIRECTORIES` and :prop_tgt:`INTERFACE_LINK_DEPENDS` -are now transitive over private dependencies of static libraries. - -In CMake 3.16 and below the interface link properties attached to libraries -are not propagated for private dependencies of static libraries. -Only the libraries themselves are propagated to link the dependent binary. -CMake 3.17 and later prefer to propagate all interface link properties. -This policy provides compatibility for projects that have not been updated -to expect the new behavior. - -The ``OLD`` behavior for this policy is to not propagate interface link -properties. The ``NEW`` behavior of this policy is to propagate interface link -properties. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0100.rst b/share/cmake-3.18/Help/policy/CMP0100.rst deleted file mode 100644 index b24d013..0000000 --- a/share/cmake-3.18/Help/policy/CMP0100.rst +++ /dev/null
@@ -1,40 +0,0 @@ -CMP0100 -------- - -Let :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` process -header files that end with a ``.hh`` extension. - -Since version 3.17, CMake processes header files that end with a -``.hh`` extension in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. -In earlier CMake versions, these header files were ignored by -:prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -This policy affects how header files that end with a ``.hh`` extension -get treated in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -The ``OLD`` behavior for this policy is to ignore ``.hh`` header files -in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -The ``NEW`` behavior for this policy is to process ``.hh`` header files -in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` just like other header files. - -.. note:: - - To silence the ``CMP0100`` warning source files can be excluded from - :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` processing by setting the - source file properties :prop_sf:`SKIP_AUTOMOC`, :prop_sf:`SKIP_AUTOUIC` or - :prop_sf:`SKIP_AUTOGEN`. - - .. code-block:: cmake - - # Source skip example: - set_property(SOURCE /path/to/file1.hh PROPERTY SKIP_AUTOMOC ON) - set_property(SOURCE /path/to/file2.hh PROPERTY SKIP_AUTOUIC ON) - set_property(SOURCE /path/to/file3.hh PROPERTY SKIP_AUTOGEN ON) - -This policy was introduced in CMake version 3.17.0. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0101.rst b/share/cmake-3.18/Help/policy/CMP0101.rst deleted file mode 100644 index 9941acf..0000000 --- a/share/cmake-3.18/Help/policy/CMP0101.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMP0101 -------- - -:command:`target_compile_options` now honors ``BEFORE`` keyword in all scopes. - -In CMake 3.16 and below the :command:`target_compile_options` ignores the -``BEFORE`` keyword in private scope. CMake 3.17 and later honors -``BEFORE`` keyword in all scopes. This policy provides compatibility for -projects that have not been updated to expect the new behavior. - -The ``OLD`` behavior for this policy is to not honor ``BEFORE`` keyword in -private scope. The ``NEW`` behavior of this policy is to honor -``BEFORE`` keyword in all scopes. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0102.rst b/share/cmake-3.18/Help/policy/CMP0102.rst deleted file mode 100644 index 9859006..0000000 --- a/share/cmake-3.18/Help/policy/CMP0102.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMP0102 -------- - -The :command:`mark_as_advanced` command no longer creates a cache entry if one -does not already exist. - -In CMake 3.16 and below, if a variable was not defined at all or just defined -locally, the :command:`mark_as_advanced` command would create a new cache -entry with an ``UNINITIALIZED`` type and no value. When a :command:`find_path` -(or other similar ``find_`` command) would next run, it would find this -undefined cache entry and set it up with an empty string value. This process -would end up deleting the local variable in the process (due to the way the -cache works), effectively clearing any stored ``find_`` results that were only -available in the local scope. - -The ``OLD`` behavior for this policy is to create the empty cache definition. -The ``NEW`` behavior of this policy is to ignore variables which do not -already exist in the cache. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0103.rst b/share/cmake-3.18/Help/policy/CMP0103.rst deleted file mode 100644 index 223e0cb..0000000 --- a/share/cmake-3.18/Help/policy/CMP0103.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMP0103 -------- - -Multiple calls to :command:`export` command with same ``FILE`` without -``APPEND`` is no longer allowed. - -In CMake 3.17 and below, multiple calls to :command:`export` command with the -same ``FILE`` without ``APPEND`` are accepted silently but only the last -occurrence is taken into account during the generation. - -The ``OLD`` behavior for this policy is to ignore the multiple occurrences of - :command:`export` command except the last one. - -The ``NEW`` behavior of this policy is to raise an error on second call to -:command:`export` command with same ``FILE`` without ``APPEND``. - -This policy was introduced in CMake version 3.18. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0104.rst b/share/cmake-3.18/Help/policy/CMP0104.rst deleted file mode 100644 index 8516716..0000000 --- a/share/cmake-3.18/Help/policy/CMP0104.rst +++ /dev/null
@@ -1,56 +0,0 @@ -CMP0104 -------- - -Initialize :variable:`CMAKE_CUDA_ARCHITECTURES` when -:variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` is ``NVIDIA``. -Raise an error if :prop_tgt:`CUDA_ARCHITECTURES` is empty. - -:variable:`CMAKE_CUDA_ARCHITECTURES` introduced in CMake 3.18 is used to -initialize :prop_tgt:`CUDA_ARCHITECTURES`, which passes correct code generation -flags to the CUDA compiler. - -Previous to this users had to manually specify the code generation flags. This -policy is for backwards compatibility with manually specifying code generation -flags. - -The ``OLD`` behavior for this policy is to not initialize -:variable:`CMAKE_CUDA_ARCHITECTURES` when -:variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` is ``NVIDIA``. -Empty :prop_tgt:`CUDA_ARCHITECTURES` is allowed. - -The ``NEW`` behavior of this policy is to initialize -:variable:`CMAKE_CUDA_ARCHITECTURES` when -:variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` is ``NVIDIA`` -and raise an error if :prop_tgt:`CUDA_ARCHITECTURES` is empty during generation. - -If :prop_tgt:`CUDA_ARCHITECTURES` is set to a false value no architectures -flags are passed to the compiler. This is intended to support packagers and -the rare cases where full control over the passed flags is required. - -This policy was introduced in CMake version 3.18. CMake version -|release| warns when the policy is not set and uses ``OLD`` behavior. -Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` -explicitly. - -.. include:: DEPRECATED.txt - -Examples -^^^^^^^^ - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 35 50 72) - -Generates code for real and virtual architectures ``30``, ``50`` and ``72``. - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 70-real 72-virtual) - -Generates code for real architecture ``70`` and virtual architecture ``72``. - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES OFF) - -CMake will not pass any architecture flags to the compiler.
diff --git a/share/cmake-3.18/Help/policy/CMP0105.rst b/share/cmake-3.18/Help/policy/CMP0105.rst deleted file mode 100644 index 19a1edb..0000000 --- a/share/cmake-3.18/Help/policy/CMP0105.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0105 -------- - -:prop_tgt:`LINK_OPTIONS` and :prop_tgt:`INTERFACE_LINK_OPTIONS` target -properties are now used for the device link step. - -In CMake 3.17 and below, link options are not used by the device link step. - -The ``OLD`` behavior for this policy is to ignore the link options. - -The ``NEW`` behavior of this policy is to use the link options during the -device link step. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0106.rst b/share/cmake-3.18/Help/policy/CMP0106.rst deleted file mode 100644 index e34d15a..0000000 --- a/share/cmake-3.18/Help/policy/CMP0106.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0106 -------- - -The :module:`Documentation` module is removed. - -The :module:`Documentation` was added as a support mechanism for the VTK -project and was tuned for that project. Instead of CMake providing this module -with (now old) VTK patterns for cache variables and required packages, the -module is now deprecated by CMake itself. - -The ``OLD`` behavior of this policy is for :module:`Documentation` to add -cache variables and find VTK documentation dependent packages. The ``NEW`` -behavior is to act as an empty module. - -This policy was introduced in CMake version 3.18. CMake version |release| -warns when the policy is not set and uses ``OLD`` behavior. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0107.rst b/share/cmake-3.18/Help/policy/CMP0107.rst deleted file mode 100644 index 111bef7..0000000 --- a/share/cmake-3.18/Help/policy/CMP0107.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0107 -------- - -It is not allowed to create an ``ALIAS`` target with the same name as an -another target. - -In CMake 3.17 and below, an ``ALIAS`` target can overwrite silently an existing -target with the same name. - -The ``OLD`` behavior for this policy is to allow target overwrite. - -The ``NEW`` behavior of this policy is to prevent target overwriting. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/policy/CMP0108.rst b/share/cmake-3.18/Help/policy/CMP0108.rst deleted file mode 100644 index 0d54cfa..0000000 --- a/share/cmake-3.18/Help/policy/CMP0108.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMP0108 -------- - -A target is not allowed to link to itself even through an ``ALIAS`` target. - -In CMake 3.17 and below, a target can link to a target aliased to itself. - -The ``OLD`` behavior for this policy is to allow a target to link to a target -aliased to itself. - -The ``NEW`` behavior of this policy is to prevent a target to link to itself -through an ``ALIAS`` target. - -This policy was introduced in CMake version 3.17. Use the -:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. -Unlike many policies, CMake version |release| does *not* warn -when this policy is not set and simply uses ``OLD`` behavior. - -.. include:: DEPRECATED.txt
diff --git a/share/cmake-3.18/Help/prop_dir/ADDITIONAL_CLEAN_FILES.rst b/share/cmake-3.18/Help/prop_dir/ADDITIONAL_CLEAN_FILES.rst deleted file mode 100644 index 051d22a..0000000 --- a/share/cmake-3.18/Help/prop_dir/ADDITIONAL_CLEAN_FILES.rst +++ /dev/null
@@ -1,21 +0,0 @@ -ADDITIONAL_CLEAN_FILES ----------------------- - -A :ref:`;-list <CMake Language Lists>` of files or directories that will be -removed as a part of the global ``clean`` target. It is useful for -specifying generated files or directories that are used by multiple targets -or by CMake itself, or that are generated in ways which cannot be captured as -outputs or byproducts of custom commands. - -If an additional clean file is specific to a single target only, then the -:prop_tgt:`ADDITIONAL_CLEAN_FILES` target property would usually be a better -choice than this directory property. - -Relative paths are allowed and are interpreted relative to the -current binary directory. - -Contents of ``ADDITIONAL_CLEAN_FILES`` may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. - -This property only works for the :generator:`Ninja` and the Makefile -generators. It is ignored by other generators.
diff --git a/share/cmake-3.18/Help/prop_dir/BINARY_DIR.rst b/share/cmake-3.18/Help/prop_dir/BINARY_DIR.rst deleted file mode 100644 index 597c79a..0000000 --- a/share/cmake-3.18/Help/prop_dir/BINARY_DIR.rst +++ /dev/null
@@ -1,5 +0,0 @@ -BINARY_DIR ----------- - -This read-only directory property reports absolute path to the binary -directory corresponding to the source on which it is read.
diff --git a/share/cmake-3.18/Help/prop_dir/BUILDSYSTEM_TARGETS.rst b/share/cmake-3.18/Help/prop_dir/BUILDSYSTEM_TARGETS.rst deleted file mode 100644 index 04bb56e..0000000 --- a/share/cmake-3.18/Help/prop_dir/BUILDSYSTEM_TARGETS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -BUILDSYSTEM_TARGETS -------------------- - -This read-only directory property contains a -:ref:`semicolon-separated list <CMake Language Lists>` of buildsystem targets added in the -directory by calls to the :command:`add_library`, :command:`add_executable`, -and :command:`add_custom_target` commands. The list does not include any -:ref:`Imported Targets` or :ref:`Alias Targets`, but does include -:ref:`Interface Libraries`. Each entry in the list is the logical name -of a target, suitable to pass to the :command:`get_property` command -``TARGET`` option.
diff --git a/share/cmake-3.18/Help/prop_dir/LABELS.rst b/share/cmake-3.18/Help/prop_dir/LABELS.rst deleted file mode 100644 index de27d90..0000000 --- a/share/cmake-3.18/Help/prop_dir/LABELS.rst +++ /dev/null
@@ -1,13 +0,0 @@ -LABELS ------- - -Specify a list of text labels associated with a directory and all of its -subdirectories. This is equivalent to setting the :prop_tgt:`LABELS` target -property and the :prop_test:`LABELS` test property on all targets and tests in -the current directory and subdirectories. Note: Launchers must enabled to -propagate labels to targets. - -The :variable:`CMAKE_DIRECTORY_LABELS` variable can be used to initialize this -property. - -The list is reported in dashboard submissions.
diff --git a/share/cmake-3.18/Help/prop_dir/LINK_OPTIONS.rst b/share/cmake-3.18/Help/prop_dir/LINK_OPTIONS.rst deleted file mode 100644 index f229ba6..0000000 --- a/share/cmake-3.18/Help/prop_dir/LINK_OPTIONS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -LINK_OPTIONS ------------- - -List of options to use for the link step of shared library, module -and executable targets as well as the device link step. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of options -given so far to the :command:`add_link_options` command. - -This property is used to initialize the :prop_tgt:`LINK_OPTIONS` target -property when a target is created, which is used by the generators to set -the options for the compiler. - -Contents of ``LINK_OPTIONS`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_dir/SOURCE_DIR.rst b/share/cmake-3.18/Help/prop_dir/SOURCE_DIR.rst deleted file mode 100644 index ac98c3b..0000000 --- a/share/cmake-3.18/Help/prop_dir/SOURCE_DIR.rst +++ /dev/null
@@ -1,5 +0,0 @@ -SOURCE_DIR ----------- - -This read-only directory property reports absolute path to the source -directory on which it is read.
diff --git a/share/cmake-3.18/Help/prop_dir/SUBDIRECTORIES.rst b/share/cmake-3.18/Help/prop_dir/SUBDIRECTORIES.rst deleted file mode 100644 index 6a0ac80..0000000 --- a/share/cmake-3.18/Help/prop_dir/SUBDIRECTORIES.rst +++ /dev/null
@@ -1,15 +0,0 @@ -SUBDIRECTORIES --------------- - -This read-only directory property contains a -:ref:`semicolon-separated list <CMake Language Lists>` of subdirectories processed so far by -the :command:`add_subdirectory` or :command:`subdirs` commands. Each entry is -the absolute path to the source directory (containing the ``CMakeLists.txt`` -file). This is suitable to pass to the :command:`get_property` command -``DIRECTORY`` option. - -.. note:: - - The :command:`subdirs` command does not process its arguments until - after the calling directory is fully processed. Therefore looking - up this property in the current directory will not see them.
diff --git a/share/cmake-3.18/Help/prop_dir/TESTS.rst b/share/cmake-3.18/Help/prop_dir/TESTS.rst deleted file mode 100644 index 1c9f6e5..0000000 --- a/share/cmake-3.18/Help/prop_dir/TESTS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -TESTS ------ - -List of tests. - -This read-only property holds a -:ref:`semicolon-separated list <CMake Language Lists>` of tests -defined so far, in the current directory, by the :command:`add_test` command.
diff --git a/share/cmake-3.18/Help/prop_dir/TEST_INCLUDE_FILES.rst b/share/cmake-3.18/Help/prop_dir/TEST_INCLUDE_FILES.rst deleted file mode 100644 index c3e4602..0000000 --- a/share/cmake-3.18/Help/prop_dir/TEST_INCLUDE_FILES.rst +++ /dev/null
@@ -1,7 +0,0 @@ -TEST_INCLUDE_FILES ------------------- - -A list of cmake files that will be included when ctest is run. - -If you specify ``TEST_INCLUDE_FILES``, those files will be included and -processed when ctest is run on the directory.
diff --git a/share/cmake-3.18/Help/prop_dir/VS_STARTUP_PROJECT.rst b/share/cmake-3.18/Help/prop_dir/VS_STARTUP_PROJECT.rst deleted file mode 100644 index 2680dfa..0000000 --- a/share/cmake-3.18/Help/prop_dir/VS_STARTUP_PROJECT.rst +++ /dev/null
@@ -1,18 +0,0 @@ -VS_STARTUP_PROJECT ------------------- - -Specify the default startup project in a Visual Studio solution. - -The :ref:`Visual Studio Generators` create a ``.sln`` file for each directory -whose ``CMakeLists.txt`` file calls the :command:`project` command. Set this -property in the same directory as a :command:`project` command call (e.g. in -the top-level ``CMakeLists.txt`` file) to specify the default startup project -for the corresponding solution file. - -The property must be set to the name of an existing target. This -will cause that project to be listed first in the generated solution -file causing Visual Studio to make it the startup project if the -solution has never been opened before. - -If this property is not specified, then the ``ALL_BUILD`` project -will be the default.
diff --git a/share/cmake-3.18/Help/prop_gbl/AUTOGEN_SOURCE_GROUP.rst b/share/cmake-3.18/Help/prop_gbl/AUTOGEN_SOURCE_GROUP.rst deleted file mode 100644 index d294eb1..0000000 --- a/share/cmake-3.18/Help/prop_gbl/AUTOGEN_SOURCE_GROUP.rst +++ /dev/null
@@ -1,15 +0,0 @@ -AUTOGEN_SOURCE_GROUP --------------------- - -Name of the :command:`source_group` for :prop_tgt:`AUTOMOC` and -:prop_tgt:`AUTORCC` generated files. - -Files generated by :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTORCC` are not always -known at configure time and therefore can't be passed to -:command:`source_group`. -:prop_gbl:`AUTOGEN_SOURCE_GROUP` an be used instead to generate or select -a source group for :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTORCC` generated files. - -For :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTORCC` specific overrides see -:prop_gbl:`AUTOMOC_SOURCE_GROUP` and :prop_gbl:`AUTORCC_SOURCE_GROUP` -respectively.
diff --git a/share/cmake-3.18/Help/prop_gbl/AUTOMOC_SOURCE_GROUP.rst b/share/cmake-3.18/Help/prop_gbl/AUTOMOC_SOURCE_GROUP.rst deleted file mode 100644 index 2455dc7..0000000 --- a/share/cmake-3.18/Help/prop_gbl/AUTOMOC_SOURCE_GROUP.rst +++ /dev/null
@@ -1,7 +0,0 @@ -AUTOMOC_SOURCE_GROUP --------------------- - -Name of the :command:`source_group` for :prop_tgt:`AUTOMOC` generated files. - -When set this is used instead of :prop_gbl:`AUTOGEN_SOURCE_GROUP` for -files generated by :prop_tgt:`AUTOMOC`.
diff --git a/share/cmake-3.18/Help/prop_gbl/AUTORCC_SOURCE_GROUP.rst b/share/cmake-3.18/Help/prop_gbl/AUTORCC_SOURCE_GROUP.rst deleted file mode 100644 index 65ea95b..0000000 --- a/share/cmake-3.18/Help/prop_gbl/AUTORCC_SOURCE_GROUP.rst +++ /dev/null
@@ -1,7 +0,0 @@ -AUTORCC_SOURCE_GROUP --------------------- - -Name of the :command:`source_group` for :prop_tgt:`AUTORCC` generated files. - -When set this is used instead of :prop_gbl:`AUTOGEN_SOURCE_GROUP` for -files generated by :prop_tgt:`AUTORCC`.
diff --git a/share/cmake-3.18/Help/prop_gbl/CMAKE_CUDA_KNOWN_FEATURES.rst b/share/cmake-3.18/Help/prop_gbl/CMAKE_CUDA_KNOWN_FEATURES.rst deleted file mode 100644 index 44e37fe..0000000 --- a/share/cmake-3.18/Help/prop_gbl/CMAKE_CUDA_KNOWN_FEATURES.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMAKE_CUDA_KNOWN_FEATURES -------------------------- - -List of CUDA features known to this version of CMake. - -The features listed in this global property may be known to be available to the -CUDA compiler. If the feature is available with the C++ compiler, it will -be listed in the :variable:`CMAKE_CUDA_COMPILE_FEATURES` variable. - -The features listed here may be used with the :command:`target_compile_features` -command. See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - - -The features known to this version of CMake are: - -``cuda_std_03`` - Compiler mode is at least CUDA/C++ 03. - -``cuda_std_11`` - Compiler mode is at least CUDA/C++ 11. - -``cuda_std_14`` - Compiler mode is at least CUDA/C++ 14. - -``cuda_std_17`` - Compiler mode is at least CUDA/C++ 17. - -``cuda_std_20`` - Compiler mode is at least CUDA/C++ 20.
diff --git a/share/cmake-3.18/Help/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.rst b/share/cmake-3.18/Help/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.rst deleted file mode 100644 index b921c6b..0000000 --- a/share/cmake-3.18/Help/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.rst +++ /dev/null
@@ -1,318 +0,0 @@ -CMAKE_CXX_KNOWN_FEATURES ------------------------- - -List of C++ features known to this version of CMake. - -The features listed in this global property may be known to be available to the -C++ compiler. If the feature is available with the C++ compiler, it will -be listed in the :variable:`CMAKE_CXX_COMPILE_FEATURES` variable. - -The features listed here may be used with the :command:`target_compile_features` -command. See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - - -The features known to this version of CMake are: - -``cxx_std_98`` - Compiler mode is at least C++ 98. - -``cxx_std_11`` - Compiler mode is at least C++ 11. - -``cxx_std_14`` - Compiler mode is at least C++ 14. - -``cxx_std_17`` - Compiler mode is at least C++ 17. - -``cxx_std_20`` - Compiler mode is at least C++ 20. - -``cxx_aggregate_default_initializers`` - Aggregate default initializers, as defined in N3605_. - - .. _N3605: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3605.html - -``cxx_alias_templates`` - Template aliases, as defined in N2258_. - - .. _N2258: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2258.pdf - -``cxx_alignas`` - Alignment control ``alignas``, as defined in N2341_. - - .. _N2341: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2341.pdf - -``cxx_alignof`` - Alignment control ``alignof``, as defined in N2341_. - - .. _N2341: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2341.pdf - -``cxx_attributes`` - Generic attributes, as defined in N2761_. - - .. _N2761: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2761.pdf - -``cxx_attribute_deprecated`` - ``[[deprecated]]`` attribute, as defined in N3760_. - - .. _N3760: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3760.html - -``cxx_auto_type`` - Automatic type deduction, as defined in N1984_. - - .. _N1984: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1984.pdf - -``cxx_binary_literals`` - Binary literals, as defined in N3472_. - - .. _N3472: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3472.pdf - -``cxx_constexpr`` - Constant expressions, as defined in N2235_. - - .. _N2235: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2235.pdf - -``cxx_contextual_conversions`` - Contextual conversions, as defined in N3323_. - - .. _N3323: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3323.pdf - -``cxx_decltype_incomplete_return_types`` - Decltype on incomplete return types, as defined in N3276_. - - .. _N3276 : http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf - -``cxx_decltype`` - Decltype, as defined in N2343_. - - .. _N2343: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2343.pdf - -``cxx_decltype_auto`` - ``decltype(auto)`` semantics, as defined in N3638_. - - .. _N3638: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3638.html - -``cxx_default_function_template_args`` - Default template arguments for function templates, as defined in DR226_ - - .. _DR226: http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#226 - -``cxx_defaulted_functions`` - Defaulted functions, as defined in N2346_. - - .. _N2346: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2346.htm - -``cxx_defaulted_move_initializers`` - Defaulted move initializers, as defined in N3053_. - - .. _N3053: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3053.html - -``cxx_delegating_constructors`` - Delegating constructors, as defined in N1986_. - - .. _N1986: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1986.pdf - -``cxx_deleted_functions`` - Deleted functions, as defined in N2346_. - - .. _N2346: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2346.htm - -``cxx_digit_separators`` - Digit separators, as defined in N3781_. - - .. _N3781: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3781.pdf - -``cxx_enum_forward_declarations`` - Enum forward declarations, as defined in N2764_. - - .. _N2764: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2764.pdf - -``cxx_explicit_conversions`` - Explicit conversion operators, as defined in N2437_. - - .. _N2437: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2437.pdf - -``cxx_extended_friend_declarations`` - Extended friend declarations, as defined in N1791_. - - .. _N1791: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1791.pdf - -``cxx_extern_templates`` - Extern templates, as defined in N1987_. - - .. _N1987: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1987.htm - -``cxx_final`` - Override control ``final`` keyword, as defined in N2928_, N3206_ and N3272_. - - .. _N2928: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2928.htm - .. _N3206: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3206.htm - .. _N3272: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3272.htm - -``cxx_func_identifier`` - Predefined ``__func__`` identifier, as defined in N2340_. - - .. _N2340: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2340.htm - -``cxx_generalized_initializers`` - Initializer lists, as defined in N2672_. - - .. _N2672: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2672.htm - -``cxx_generic_lambdas`` - Generic lambdas, as defined in N3649_. - - .. _N3649: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3649.html - -``cxx_inheriting_constructors`` - Inheriting constructors, as defined in N2540_. - - .. _N2540: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2540.htm - -``cxx_inline_namespaces`` - Inline namespaces, as defined in N2535_. - - .. _N2535: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2535.htm - -``cxx_lambdas`` - Lambda functions, as defined in N2927_. - - .. _N2927: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2927.pdf - -``cxx_lambda_init_captures`` - Initialized lambda captures, as defined in N3648_. - - .. _N3648: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3648.html - -``cxx_local_type_template_args`` - Local and unnamed types as template arguments, as defined in N2657_. - - .. _N2657: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2657.htm - -``cxx_long_long_type`` - ``long long`` type, as defined in N1811_. - - .. _N1811: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1811.pdf - -``cxx_noexcept`` - Exception specifications, as defined in N3050_. - - .. _N3050: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3050.html - -``cxx_nonstatic_member_init`` - Non-static data member initialization, as defined in N2756_. - - .. _N2756: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2756.htm - -``cxx_nullptr`` - Null pointer, as defined in N2431_. - - .. _N2431: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2431.pdf - -``cxx_override`` - Override control ``override`` keyword, as defined in N2928_, N3206_ - and N3272_. - - .. _N2928: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2928.htm - .. _N3206: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3206.htm - .. _N3272: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3272.htm - -``cxx_range_for`` - Range-based for, as defined in N2930_. - - .. _N2930: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2930.html - -``cxx_raw_string_literals`` - Raw string literals, as defined in N2442_. - - .. _N2442: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2442.htm - -``cxx_reference_qualified_functions`` - Reference qualified functions, as defined in N2439_. - - .. _N2439: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2439.htm - -``cxx_relaxed_constexpr`` - Relaxed constexpr, as defined in N3652_. - - .. _N3652: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3652.html - -``cxx_return_type_deduction`` - Return type deduction on normal functions, as defined in N3386_. - - .. _N3386: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3386.html - -``cxx_right_angle_brackets`` - Right angle bracket parsing, as defined in N1757_. - - .. _N1757: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1757.html - -``cxx_rvalue_references`` - R-value references, as defined in N2118_. - - .. _N2118: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2118.html - -``cxx_sizeof_member`` - Size of non-static data members, as defined in N2253_. - - .. _N2253: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2253.html - -``cxx_static_assert`` - Static assert, as defined in N1720_. - - .. _N1720: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1720.html - -``cxx_strong_enums`` - Strongly typed enums, as defined in N2347_. - - .. _N2347: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2347.pdf - -``cxx_thread_local`` - Thread-local variables, as defined in N2659_. - - .. _N2659: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2659.htm - -``cxx_trailing_return_types`` - Automatic function return type, as defined in N2541_. - - .. _N2541: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2541.htm - -``cxx_unicode_literals`` - Unicode string literals, as defined in N2442_. - - .. _N2442: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2442.htm - -``cxx_uniform_initialization`` - Uniform initialization, as defined in N2640_. - - .. _N2640: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2640.pdf - -``cxx_unrestricted_unions`` - Unrestricted unions, as defined in N2544_. - - .. _N2544: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2544.pdf - -``cxx_user_literals`` - User-defined literals, as defined in N2765_. - - .. _N2765: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2765.pdf - -``cxx_variable_templates`` - Variable templates, as defined in N3651_. - - .. _N3651: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3651.pdf - -``cxx_variadic_macros`` - Variadic macros, as defined in N1653_. - - .. _N1653: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1653.htm - -``cxx_variadic_templates`` - Variadic templates, as defined in N2242_. - - .. _N2242: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2242.pdf - -``cxx_template_template_parameters`` - Template template parameters, as defined in ``ISO/IEC 14882:1998``.
diff --git a/share/cmake-3.18/Help/prop_gbl/CMAKE_C_KNOWN_FEATURES.rst b/share/cmake-3.18/Help/prop_gbl/CMAKE_C_KNOWN_FEATURES.rst deleted file mode 100644 index e5f896e..0000000 --- a/share/cmake-3.18/Help/prop_gbl/CMAKE_C_KNOWN_FEATURES.rst +++ /dev/null
@@ -1,35 +0,0 @@ -CMAKE_C_KNOWN_FEATURES ----------------------- - -List of C features known to this version of CMake. - -The features listed in this global property may be known to be available to the -C compiler. If the feature is available with the C compiler, it will -be listed in the :variable:`CMAKE_C_COMPILE_FEATURES` variable. - -The features listed here may be used with the :command:`target_compile_features` -command. See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -The features known to this version of CMake are: - -``c_std_90`` - Compiler mode is at least C 90. - -``c_std_99`` - Compiler mode is at least C 99. - -``c_std_11`` - Compiler mode is at least C 11. - -``c_function_prototypes`` - Function prototypes, as defined in ``ISO/IEC 9899:1990``. - -``c_restrict`` - ``restrict`` keyword, as defined in ``ISO/IEC 9899:1999``. - -``c_static_assert`` - Static assert, as defined in ``ISO/IEC 9899:2011``. - -``c_variadic_macros`` - Variadic macros, as defined in ``ISO/IEC 9899:1999``.
diff --git a/share/cmake-3.18/Help/prop_gbl/CMAKE_ROLE.rst b/share/cmake-3.18/Help/prop_gbl/CMAKE_ROLE.rst deleted file mode 100644 index 27512fa..0000000 --- a/share/cmake-3.18/Help/prop_gbl/CMAKE_ROLE.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_ROLE ----------- - -Tells what mode the current running script is in. Could be one of several -values: - -``PROJECT`` - Running in project mode (processing a ``CMakeLists.txt`` file). - -``SCRIPT`` - Running in ``-P`` script mode. - -``FIND_PACKAGE`` - Running in ``--find-package`` mode. - -``CTEST`` - Running in CTest script mode. - -``CPACK`` - Running in CPack.
diff --git a/share/cmake-3.18/Help/prop_gbl/ECLIPSE_EXTRA_CPROJECT_CONTENTS.rst b/share/cmake-3.18/Help/prop_gbl/ECLIPSE_EXTRA_CPROJECT_CONTENTS.rst deleted file mode 100644 index 50c41a9..0000000 --- a/share/cmake-3.18/Help/prop_gbl/ECLIPSE_EXTRA_CPROJECT_CONTENTS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -ECLIPSE_EXTRA_CPROJECT_CONTENTS -------------------------------- - -Additional contents to be inserted into the generated Eclipse cproject file. - -The cproject file defines the CDT specific information. Some third party IDE's -are based on Eclipse with the addition of other information specific to that IDE. -Through this property, it is possible to add this additional contents to -the generated project. -It is expected to contain valid XML. - -Also see the :prop_gbl:`ECLIPSE_EXTRA_NATURES` property.
diff --git a/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIB32_PATHS.rst b/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIB32_PATHS.rst deleted file mode 100644 index 8396026..0000000 --- a/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIB32_PATHS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -FIND_LIBRARY_USE_LIB32_PATHS ----------------------------- - -Whether the :command:`find_library` command should automatically search -``lib32`` directories. - -``FIND_LIBRARY_USE_LIB32_PATHS`` is a boolean specifying whether the -:command:`find_library` command should automatically search the ``lib32`` -variant of directories called ``lib`` in the search path when building 32-bit -binaries. - -See also the :variable:`CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX` variable.
diff --git a/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIBX32_PATHS.rst b/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIBX32_PATHS.rst deleted file mode 100644 index b87b09b..0000000 --- a/share/cmake-3.18/Help/prop_gbl/FIND_LIBRARY_USE_LIBX32_PATHS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -FIND_LIBRARY_USE_LIBX32_PATHS ------------------------------ - -Whether the :command:`find_library` command should automatically search -``libx32`` directories. - -``FIND_LIBRARY_USE_LIBX32_PATHS`` is a boolean specifying whether the -:command:`find_library` command should automatically search the ``libx32`` -variant of directories called ``lib`` in the search path when building -x32-abi binaries. - -See also the :variable:`CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX` variable.
diff --git a/share/cmake-3.18/Help/prop_gbl/GENERATOR_IS_MULTI_CONFIG.rst b/share/cmake-3.18/Help/prop_gbl/GENERATOR_IS_MULTI_CONFIG.rst deleted file mode 100644 index b8ec8a6..0000000 --- a/share/cmake-3.18/Help/prop_gbl/GENERATOR_IS_MULTI_CONFIG.rst +++ /dev/null
@@ -1,9 +0,0 @@ -GENERATOR_IS_MULTI_CONFIG -------------------------- - -Read-only property that is true on multi-configuration generators. - -True when using a multi-configuration generator -(such as :ref:`Visual Studio Generators` or :generator:`Xcode`). -Multi-config generators use :variable:`CMAKE_CONFIGURATION_TYPES` -as the set of configurations and ignore :variable:`CMAKE_BUILD_TYPE`.
diff --git a/share/cmake-3.18/Help/prop_gbl/TARGET_MESSAGES.rst b/share/cmake-3.18/Help/prop_gbl/TARGET_MESSAGES.rst deleted file mode 100644 index 275b074..0000000 --- a/share/cmake-3.18/Help/prop_gbl/TARGET_MESSAGES.rst +++ /dev/null
@@ -1,20 +0,0 @@ -TARGET_MESSAGES ---------------- - -Specify whether to report the completion of each target. - -This property specifies whether :ref:`Makefile Generators` should -add a progress message describing that each target has been completed. -If the property is not set the default is ``ON``. Set the property -to ``OFF`` to disable target completion messages. - -This option is intended to reduce build output when little or no -work needs to be done to bring the build tree up to date. - -If a ``CMAKE_TARGET_MESSAGES`` cache entry exists its value -initializes the value of this property. - -Non-Makefile generators currently ignore this property. - -See the counterpart property :prop_gbl:`RULE_MESSAGES` to disable -everything except for target completion messages.
diff --git a/share/cmake-3.18/Help/prop_gbl/XCODE_EMIT_EFFECTIVE_PLATFORM_NAME.rst b/share/cmake-3.18/Help/prop_gbl/XCODE_EMIT_EFFECTIVE_PLATFORM_NAME.rst deleted file mode 100644 index 9500443..0000000 --- a/share/cmake-3.18/Help/prop_gbl/XCODE_EMIT_EFFECTIVE_PLATFORM_NAME.rst +++ /dev/null
@@ -1,25 +0,0 @@ -XCODE_EMIT_EFFECTIVE_PLATFORM_NAME ----------------------------------- - -Control emission of ``EFFECTIVE_PLATFORM_NAME`` by the :generator:`Xcode` -generator. - -It is required for building the same target with multiple SDKs. A -common use case is the parallel use of ``iphoneos`` and -``iphonesimulator`` SDKs. - -Three different states possible that control when the :generator:`Xcode` -generator emits the ``EFFECTIVE_PLATFORM_NAME`` variable: - -- If set to ``ON`` it will always be emitted -- If set to ``OFF`` it will never be emitted -- If unset (the default) it will only be emitted when the project was - configured for an embedded Xcode SDK like iOS, tvOS, watchOS or any - of the simulators. - -.. note:: - - When this behavior is enable for generated Xcode projects, the - ``EFFECTIVE_PLATFORM_NAME`` variable will leak into - :manual:`Generator expressions <cmake-generator-expressions(7)>` - like ``TARGET_FILE`` and will render those mostly unusable.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_DESKTOP_SHORTCUTS.rst b/share/cmake-3.18/Help/prop_inst/CPACK_DESKTOP_SHORTCUTS.rst deleted file mode 100644 index 729ab60..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_DESKTOP_SHORTCUTS.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CPACK_DESKTOP_SHORTCUTS ------------------------ - -Species a list of shortcut names that should be created on the `Desktop` -for this file. - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_NEVER_OVERWRITE.rst b/share/cmake-3.18/Help/prop_inst/CPACK_NEVER_OVERWRITE.rst deleted file mode 100644 index 4789e25..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_NEVER_OVERWRITE.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CPACK_NEVER_OVERWRITE ---------------------- - -Request that this file not be overwritten on install or reinstall. - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_PERMANENT.rst b/share/cmake-3.18/Help/prop_inst/CPACK_PERMANENT.rst deleted file mode 100644 index 985de0d..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_PERMANENT.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CPACK_PERMANENT ---------------- - -Request that this file not be removed on uninstall. - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_STARTUP_SHORTCUTS.rst b/share/cmake-3.18/Help/prop_inst/CPACK_STARTUP_SHORTCUTS.rst deleted file mode 100644 index d9208b9..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_STARTUP_SHORTCUTS.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CPACK_STARTUP_SHORTCUTS ------------------------ - -Species a list of shortcut names that should be created in the `Startup` folder -for this file. - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_START_MENU_SHORTCUTS.rst b/share/cmake-3.18/Help/prop_inst/CPACK_START_MENU_SHORTCUTS.rst deleted file mode 100644 index 092334a..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_START_MENU_SHORTCUTS.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CPACK_START_MENU_SHORTCUTS --------------------------- - -Species a list of shortcut names that should be created in the `Start Menu` -for this file. - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_inst/CPACK_WIX_ACL.rst b/share/cmake-3.18/Help/prop_inst/CPACK_WIX_ACL.rst deleted file mode 100644 index c88f426..0000000 --- a/share/cmake-3.18/Help/prop_inst/CPACK_WIX_ACL.rst +++ /dev/null
@@ -1,21 +0,0 @@ -CPACK_WIX_ACL -------------- - -Specifies access permissions for files or directories -installed by a WiX installer. - -The property can contain multiple list entries, -each of which has to match the following format. - -:: - - <user>[@<domain>]=<permission>[,<permission>] - -``<user>`` and ``<domain>`` specify the windows user and domain for which the -``<Permission>`` element should be generated. - -``<permission>`` is any of the YesNoType attributes listed here:: - - http://wixtoolset.org/documentation/manual/v3/xsd/wix/permission.html - -The property is currently only supported by the :cpack_gen:`CPack WIX Generator`.
diff --git a/share/cmake-3.18/Help/prop_sf/COMPILE_FLAGS.rst b/share/cmake-3.18/Help/prop_sf/COMPILE_FLAGS.rst deleted file mode 100644 index c211b89..0000000 --- a/share/cmake-3.18/Help/prop_sf/COMPILE_FLAGS.rst +++ /dev/null
@@ -1,19 +0,0 @@ -COMPILE_FLAGS -------------- - -Additional flags to be added when compiling this source file. - -The ``COMPILE_FLAGS`` property, managed as a string, sets additional compiler -flags used to build source files. Use :prop_sf:`COMPILE_DEFINITIONS` to pass -additional preprocessor definitions. - -Contents of ``COMPILE_FLAGS`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. However, :generator:`Xcode` -does not support per-config per-source settings, so expressions -that depend on the build configuration are not allowed with that -generator. - -.. note:: - - This property has been superseded by the :prop_sf:`COMPILE_OPTIONS` property.
diff --git a/share/cmake-3.18/Help/prop_sf/COMPILE_OPTIONS.rst b/share/cmake-3.18/Help/prop_sf/COMPILE_OPTIONS.rst deleted file mode 100644 index 537dcec..0000000 --- a/share/cmake-3.18/Help/prop_sf/COMPILE_OPTIONS.rst +++ /dev/null
@@ -1,32 +0,0 @@ -COMPILE_OPTIONS ---------------- - -List of additional options to pass to the compiler. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of options -and will be added to the list of compile flags when this -source file builds. - -Contents of ``COMPILE_OPTIONS`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. However, :generator:`Xcode` -does not support per-config per-source settings, so expressions -that depend on the build configuration are not allowed with that -generator. - -Usage example: - -.. code-block:: cmake - - set_source_files_properties(foo.cpp PROPERTIES COMPILE_OPTIONS "-Wno-unused-parameter;-Wno-missing-field-initializer") - -Related properties: - -* Prefer this property over :prop_sf:`COMPILE_FLAGS`. -* Use :prop_sf:`COMPILE_DEFINITIONS` to pass additional preprocessor definitions. -* Use :prop_sf:`INCLUDE_DIRECTORIES` to pass additional include directories. - -Related commands: - -* :command:`add_compile_options` for directory-wide settings -* :command:`target_compile_options` for target-specific settings
diff --git a/share/cmake-3.18/Help/prop_sf/Fortran_PREPROCESS.rst b/share/cmake-3.18/Help/prop_sf/Fortran_PREPROCESS.rst deleted file mode 100644 index 25ea827..0000000 --- a/share/cmake-3.18/Help/prop_sf/Fortran_PREPROCESS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -Fortran_PREPROCESS ------------------- - -Control whether the Fortran source file should be unconditionally preprocessed. - -If unset or empty, rely on the compiler to determine whether the file -should be preprocessed. If explicitly set to ``OFF`` then the file -does not need to be preprocessed. If explicitly set to ``ON``, then -the file does need to be preprocessed as part of the compilation step. - -When using the :generator:`Ninja` generator, all source files are -first preprocessed in order to generate module dependency -information. Setting this property to ``OFF`` will make ``Ninja`` -skip this step. - -Consider using the target-wide :prop_tgt:`Fortran_PREPROCESS` property -if all source files in a target need to be preprocessed.
diff --git a/share/cmake-3.18/Help/prop_sf/GENERATED.rst b/share/cmake-3.18/Help/prop_sf/GENERATED.rst deleted file mode 100644 index 48ff70c..0000000 --- a/share/cmake-3.18/Help/prop_sf/GENERATED.rst +++ /dev/null
@@ -1,36 +0,0 @@ -GENERATED ---------- - -Is this source file generated as part of the build or CMake process. - -Tells the internal CMake engine that a source file is generated by an outside -process such as another build step, or the execution of CMake itself. -This information is then used to exempt the file from any existence or -validity checks. - -Any file that is - -- created by the execution of commands such as - :command:`add_custom_command` and :command:`file(GENERATE)` -- listed as one of the ``BYPRODUCTS`` of an :command:`add_custom_command` - or :command:`add_custom_target` command, or -- created by a CMake ``AUTOGEN`` operation such as :prop_tgt:`AUTOMOC`, - :prop_tgt:`AUTORCC`, or :prop_tgt:`AUTOUIC` - -will be marked with the ``GENERATED`` property. - -When a generated file created as the ``OUTPUT`` of an -:command:`add_custom_command` command is explicitly listed as a source file -for any target in the same directory scope (which usually means the same -``CMakeLists.txt`` file), CMake will automatically create a dependency to -make sure the file is generated before building that target. - -The :ref:`Makefile Generators` will remove ``GENERATED`` files during -``make clean``. - -Generated sources may be hidden in some IDE tools, while in others they might -be shown. For the special case of sources generated by CMake's :prop_tgt:`AUTOMOC` -or :prop_tgt:`AUTORCC` functionality, the :prop_gbl:`AUTOGEN_SOURCE_GROUP`, -:prop_gbl:`AUTOMOC_SOURCE_GROUP` and :prop_gbl:`AUTORCC_SOURCE_GROUP` target -properties may influence where the generated sources are grouped in the project's -file lists.
diff --git a/share/cmake-3.18/Help/prop_sf/INCLUDE_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_sf/INCLUDE_DIRECTORIES.rst deleted file mode 100644 index 23de70e..0000000 --- a/share/cmake-3.18/Help/prop_sf/INCLUDE_DIRECTORIES.rst +++ /dev/null
@@ -1,18 +0,0 @@ -INCLUDE_DIRECTORIES -------------------- - -List of preprocessor include file search directories. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of paths -and will be added to the list of include directories when this -source file builds. These directories will take precedence over directories -defined at target level except for :generator:`Xcode` generator due to technical -limitations. - -Relative paths should not be added to this property directly. - -Contents of ``INCLUDE_DIRECTORIES`` may use "generator expressions" with -the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. However, :generator:`Xcode` does not support -per-config per-source settings, so expressions that depend on the build -configuration are not allowed with that generator.
diff --git a/share/cmake-3.18/Help/prop_sf/LANGUAGE.rst b/share/cmake-3.18/Help/prop_sf/LANGUAGE.rst deleted file mode 100644 index 88d438e..0000000 --- a/share/cmake-3.18/Help/prop_sf/LANGUAGE.rst +++ /dev/null
@@ -1,11 +0,0 @@ -LANGUAGE --------- - -What programming language is the file. - -A property that can be set to indicate what programming language the -source file is. If it is not set the language is determined based on -the file extension. Typical values are ``CXX`` (i.e. C++), ``C``, -``CSharp``, ``CUDA``, ``Fortran``, and ``ASM``. Setting this -property for a file means this file will be compiled. Do not set this -for headers or files that should not be compiled.
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOGEN.rst b/share/cmake-3.18/Help/prop_sf/SKIP_AUTOGEN.rst deleted file mode 100644 index f31185a..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOGEN.rst +++ /dev/null
@@ -1,17 +0,0 @@ -SKIP_AUTOGEN ------------- - -Exclude the source file from :prop_tgt:`AUTOMOC`, :prop_tgt:`AUTOUIC` and -:prop_tgt:`AUTORCC` processing (for Qt projects). - -For finer exclusion control see :prop_sf:`SKIP_AUTOMOC`, -:prop_sf:`SKIP_AUTOUIC` and :prop_sf:`SKIP_AUTORCC`. - -EXAMPLE -^^^^^^^ - -.. code-block:: cmake - - # ... - set_property(SOURCE file.h PROPERTY SKIP_AUTOGEN ON) - # ...
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOMOC.rst b/share/cmake-3.18/Help/prop_sf/SKIP_AUTOMOC.rst deleted file mode 100644 index a929448..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOMOC.rst +++ /dev/null
@@ -1,15 +0,0 @@ -SKIP_AUTOMOC ------------- - -Exclude the source file from :prop_tgt:`AUTOMOC` processing (for Qt projects). - -For broader exclusion control see :prop_sf:`SKIP_AUTOGEN`. - -EXAMPLE -^^^^^^^ - -.. code-block:: cmake - - # ... - set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON) - # ...
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_AUTORCC.rst b/share/cmake-3.18/Help/prop_sf/SKIP_AUTORCC.rst deleted file mode 100644 index bccccfc..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_AUTORCC.rst +++ /dev/null
@@ -1,15 +0,0 @@ -SKIP_AUTORCC ------------- - -Exclude the source file from :prop_tgt:`AUTORCC` processing (for Qt projects). - -For broader exclusion control see :prop_sf:`SKIP_AUTOGEN`. - -EXAMPLE -^^^^^^^ - -.. code-block:: cmake - - # ... - set_property(SOURCE file.qrc PROPERTY SKIP_AUTORCC ON) - # ...
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOUIC.rst b/share/cmake-3.18/Help/prop_sf/SKIP_AUTOUIC.rst deleted file mode 100644 index 8c962db..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_AUTOUIC.rst +++ /dev/null
@@ -1,20 +0,0 @@ -SKIP_AUTOUIC ------------- - -Exclude the source file from :prop_tgt:`AUTOUIC` processing (for Qt projects). - -:prop_sf:`SKIP_AUTOUIC` can be set on C++ header and source files and on -``.ui`` files. - -For broader exclusion control see :prop_sf:`SKIP_AUTOGEN`. - -EXAMPLE -^^^^^^^ - -.. code-block:: cmake - - # ... - set_property(SOURCE file.h PROPERTY SKIP_AUTOUIC ON) - set_property(SOURCE file.cpp PROPERTY SKIP_AUTOUIC ON) - set_property(SOURCE widget.ui PROPERTY SKIP_AUTOUIC ON) - # ...
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_PRECOMPILE_HEADERS.rst b/share/cmake-3.18/Help/prop_sf/SKIP_PRECOMPILE_HEADERS.rst deleted file mode 100644 index 0031da3..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_PRECOMPILE_HEADERS.rst +++ /dev/null
@@ -1,13 +0,0 @@ -SKIP_PRECOMPILE_HEADERS ------------------------ - -Is this source file skipped by :prop_tgt:`PRECOMPILE_HEADERS` feature. - -This property helps with build problems that one would run into -when using the :prop_tgt:`PRECOMPILE_HEADERS` feature. - -One example would be the usage of Objective-C (``*.m``) files, and -Objective-C++ (``*.mm``) files, which lead to compilation failure -because they are treated (in case of Ninja / Makefile generator) -as C, and CXX respectively. The precompile headers are not -compatible between languages.
diff --git a/share/cmake-3.18/Help/prop_sf/SKIP_UNITY_BUILD_INCLUSION.rst b/share/cmake-3.18/Help/prop_sf/SKIP_UNITY_BUILD_INCLUSION.rst deleted file mode 100644 index 6d1e60d..0000000 --- a/share/cmake-3.18/Help/prop_sf/SKIP_UNITY_BUILD_INCLUSION.rst +++ /dev/null
@@ -1,11 +0,0 @@ -SKIP_UNITY_BUILD_INCLUSION --------------------------- - -Setting this property to true ensures the source file will be skipped by -unity builds when its associated target has its :prop_tgt:`UNITY_BUILD` -property set to true. The source file will instead be compiled on its own -in the same way as it would with unity builds disabled. - -This property helps with "ODR (One definition rule)" problems where combining -a particular source file with others might lead to build errors or other -unintended side effects.
diff --git a/share/cmake-3.18/Help/prop_sf/Swift_DEPENDENCIES_FILE.rst b/share/cmake-3.18/Help/prop_sf/Swift_DEPENDENCIES_FILE.rst deleted file mode 100644 index faac2df..0000000 --- a/share/cmake-3.18/Help/prop_sf/Swift_DEPENDENCIES_FILE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -Swift_DEPENDENCIES_FILE ------------------------ - -This property sets the path for the Swift dependency file (swiftdeps) for the -source. If one is not specified, it will default to ``<OBJECT>.swiftdeps``.
diff --git a/share/cmake-3.18/Help/prop_sf/Swift_DIAGNOSTICS_FILE.rst b/share/cmake-3.18/Help/prop_sf/Swift_DIAGNOSTICS_FILE.rst deleted file mode 100644 index 5bf5d59..0000000 --- a/share/cmake-3.18/Help/prop_sf/Swift_DIAGNOSTICS_FILE.rst +++ /dev/null
@@ -1,4 +0,0 @@ -Swift_DIAGNOSTICS_FILE ----------------------- - -This property controls where the Swift diagnostics are serialized.
diff --git a/share/cmake-3.18/Help/prop_sf/UNITY_GROUP.rst b/share/cmake-3.18/Help/prop_sf/UNITY_GROUP.rst deleted file mode 100644 index ec6b0f6..0000000 --- a/share/cmake-3.18/Help/prop_sf/UNITY_GROUP.rst +++ /dev/null
@@ -1,5 +0,0 @@ -UNITY_GROUP ------------ - -This property controls which *bucket* the source will be part of when -the :prop_tgt:`UNITY_BUILD_MODE` is set to ``GROUP``.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_COPY_TO_OUT_DIR.rst b/share/cmake-3.18/Help/prop_sf/VS_COPY_TO_OUT_DIR.rst deleted file mode 100644 index 16c8d83..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_COPY_TO_OUT_DIR.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_COPY_TO_OUT_DIR ------------------- - -Sets the ``<CopyToOutputDirectory>`` tag for a source file in a -Visual Studio project file. Valid values are ``Never``, ``Always`` -and ``PreserveNewest``.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_CSHARP_tagname.rst b/share/cmake-3.18/Help/prop_sf/VS_CSHARP_tagname.rst deleted file mode 100644 index 91c4a06..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_CSHARP_tagname.rst +++ /dev/null
@@ -1,20 +0,0 @@ -VS_CSHARP_<tagname> -------------------- - -Visual Studio and CSharp source-file-specific configuration. - -Tell the :manual:`Visual Studio generators <cmake-generators(7)>` -to set the source file tag ``<tagname>`` -to a given value in the generated Visual Studio CSharp -project. Ignored on other generators and languages. This property -can be used to define dependencies between source files or set any -other Visual Studio specific parameters. - -Example usage: - -.. code-block:: cmake - - set_source_files_property(<filename> - PROPERTIES - VS_CSHARP_DependentUpon <other file> - VS_CSHARP_SubType "Form")
diff --git a/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_CONTENT.rst b/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_CONTENT.rst deleted file mode 100644 index 6a38478..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_CONTENT.rst +++ /dev/null
@@ -1,12 +0,0 @@ -VS_DEPLOYMENT_CONTENT ---------------------- - -Mark a source file as content for deployment with a Windows Phone or -Windows Store application when built with a -:manual:`Visual Studio generators <cmake-generators(7)>`. -The value must evaluate to either ``1`` or ``0`` and may use -:manual:`generator expressions <cmake-generator-expressions(7)>` -to make the choice based on the build configuration. -The ``.vcxproj`` file entry for the source file will be -marked either ``DeploymentContent`` or ``ExcludedFromBuild`` -for values ``1`` and ``0``, respectively.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_LOCATION.rst b/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_LOCATION.rst deleted file mode 100644 index 2ce22fc..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_DEPLOYMENT_LOCATION.rst +++ /dev/null
@@ -1,9 +0,0 @@ -VS_DEPLOYMENT_LOCATION ----------------------- - -Specifies the deployment location for a content source file with a Windows -Phone or Windows Store application when built -with a :manual:`Visual Studio generators <cmake-generators(7)>`. -This property is only applicable when using :prop_sf:`VS_DEPLOYMENT_CONTENT`. -The value represent the path relative to the app package and applies to all -configurations.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_INCLUDE_IN_VSIX.rst b/share/cmake-3.18/Help/prop_sf/VS_INCLUDE_IN_VSIX.rst deleted file mode 100644 index db470ef..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_INCLUDE_IN_VSIX.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_INCLUDE_IN_VSIX ------------------- - -Boolean property to specify if the file should be included within a -VSIX (Visual Studio Integration Extension) extension package. -This is needed for development of Visual Studio extensions.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_RESOURCE_GENERATOR.rst b/share/cmake-3.18/Help/prop_sf/VS_RESOURCE_GENERATOR.rst deleted file mode 100644 index 97e5aac..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_RESOURCE_GENERATOR.rst +++ /dev/null
@@ -1,8 +0,0 @@ -VS_RESOURCE_GENERATOR ---------------------- - -This property allows to specify the resource generator to be used -on this file. It defaults to ``PublicResXFileCodeGenerator`` if -not set. - -This property only applies to C# projects.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SETTINGS.rst b/share/cmake-3.18/Help/prop_sf/VS_SETTINGS.rst deleted file mode 100644 index 50034fb..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SETTINGS.rst +++ /dev/null
@@ -1,18 +0,0 @@ -VS_SETTINGS ------------ - -Set any item metadata on a non-built file. - -Takes a list of ``Key=Value`` pairs. Tells the Visual Studio generator to set -``Key`` to ``Value`` as item metadata on the file. - -For example: - -.. code-block:: cmake - - set_property(SOURCE file.hlsl PROPERTY VS_SETTINGS "Key=Value" "Key2=Value2") - -will set ``Key`` to ``Value`` and ``Key2`` to ``Value2`` on the -``file.hlsl`` item as metadata. - -:manual:`Generator expressions <cmake-generator-expressions(7)>` are supported.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_DISABLE_OPTIMIZATIONS.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_DISABLE_OPTIMIZATIONS.rst deleted file mode 100644 index 446dd26..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_DISABLE_OPTIMIZATIONS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_SHADER_DISABLE_OPTIMIZATIONS -------------------------------- - -Disable compiler optimizations for an ``.hlsl`` source file. This adds the -``-Od`` flag to the command line for the FxCompiler tool. Specify the value -``true`` for this property to disable compiler optimizations.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENABLE_DEBUG.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENABLE_DEBUG.rst deleted file mode 100644 index c0e60a3..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENABLE_DEBUG.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_SHADER_ENABLE_DEBUG ----------------------- - -Enable debugging information for an ``.hlsl`` source file. This adds the -``-Zi`` flag to the command line for the FxCompiler tool. Specify the value -``true`` to generate debugging information for the compiled shader.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENTRYPOINT.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENTRYPOINT.rst deleted file mode 100644 index fe3471f..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_ENTRYPOINT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -VS_SHADER_ENTRYPOINT --------------------- - -Specifies the name of the entry point for the shader of a ``.hlsl`` source -file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_FLAGS.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_FLAGS.rst deleted file mode 100644 index 0a53afd..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_FLAGS.rst +++ /dev/null
@@ -1,4 +0,0 @@ -VS_SHADER_FLAGS ---------------- - -Set additional Visual Studio shader flags of a ``.hlsl`` source file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_MODEL.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_MODEL.rst deleted file mode 100644 index b1cf0df..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_MODEL.rst +++ /dev/null
@@ -1,5 +0,0 @@ -VS_SHADER_MODEL ---------------- - -Specifies the shader model of a ``.hlsl`` source file. Some shader types can -only be used with recent shader models
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_OBJECT_FILE_NAME.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_OBJECT_FILE_NAME.rst deleted file mode 100644 index 093bcc6..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_OBJECT_FILE_NAME.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_SHADER_OBJECT_FILE_NAME --------------------------- - -Specifies a file name for the compiled shader object file for an ``.hlsl`` -source file. This adds the ``-Fo`` flag to the command line for the FxCompiler -tool.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_OUTPUT_HEADER_FILE.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_OUTPUT_HEADER_FILE.rst deleted file mode 100644 index e6763d3..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_OUTPUT_HEADER_FILE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -VS_SHADER_OUTPUT_HEADER_FILE ----------------------------- - -Set filename for output header file containing object code of a ``.hlsl`` -source file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_TYPE.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_TYPE.rst deleted file mode 100644 index f104837..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_TYPE.rst +++ /dev/null
@@ -1,4 +0,0 @@ -VS_SHADER_TYPE --------------- - -Set the Visual Studio shader type of a ``.hlsl`` source file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_SHADER_VARIABLE_NAME.rst b/share/cmake-3.18/Help/prop_sf/VS_SHADER_VARIABLE_NAME.rst deleted file mode 100644 index 1a5e369..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_SHADER_VARIABLE_NAME.rst +++ /dev/null
@@ -1,5 +0,0 @@ -VS_SHADER_VARIABLE_NAME ------------------------ - -Set name of variable in header file containing object code of a ``.hlsl`` -source file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_TOOL_OVERRIDE.rst b/share/cmake-3.18/Help/prop_sf/VS_TOOL_OVERRIDE.rst deleted file mode 100644 index 8bdc5ca..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_TOOL_OVERRIDE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -VS_TOOL_OVERRIDE ----------------- - -Override the default Visual Studio tool that will be applied to the source file -with a new tool not based on the extension of the file.
diff --git a/share/cmake-3.18/Help/prop_sf/VS_XAML_TYPE.rst b/share/cmake-3.18/Help/prop_sf/VS_XAML_TYPE.rst deleted file mode 100644 index 1a274ba..0000000 --- a/share/cmake-3.18/Help/prop_sf/VS_XAML_TYPE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -VS_XAML_TYPE ------------- - -Mark a Extensible Application Markup Language (XAML) source file -as a different type than the default ``Page``. -The most common usage would be to set the default ``App.xaml`` file as -``ApplicationDefinition``.
diff --git a/share/cmake-3.18/Help/prop_sf/XCODE_EXPLICIT_FILE_TYPE.rst b/share/cmake-3.18/Help/prop_sf/XCODE_EXPLICIT_FILE_TYPE.rst deleted file mode 100644 index b8cf946..0000000 --- a/share/cmake-3.18/Help/prop_sf/XCODE_EXPLICIT_FILE_TYPE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -XCODE_EXPLICIT_FILE_TYPE ------------------------- - -Set the :generator:`Xcode` ``explicitFileType`` attribute on its reference to a -source file. CMake computes a default based on file extension but -can be told explicitly with this property. - -See also :prop_sf:`XCODE_LAST_KNOWN_FILE_TYPE`.
diff --git a/share/cmake-3.18/Help/prop_sf/XCODE_FILE_ATTRIBUTES.rst b/share/cmake-3.18/Help/prop_sf/XCODE_FILE_ATTRIBUTES.rst deleted file mode 100644 index 4c93f44..0000000 --- a/share/cmake-3.18/Help/prop_sf/XCODE_FILE_ATTRIBUTES.rst +++ /dev/null
@@ -1,11 +0,0 @@ -XCODE_FILE_ATTRIBUTES ---------------------- - -Add values to the :generator:`Xcode` ``ATTRIBUTES`` setting on its reference to a -source file. Among other things, this can be used to set the role on -a ``.mig`` file:: - - set_source_files_properties(defs.mig - PROPERTIES - XCODE_FILE_ATTRIBUTES "Client;Server" - )
diff --git a/share/cmake-3.18/Help/prop_sf/XCODE_LAST_KNOWN_FILE_TYPE.rst b/share/cmake-3.18/Help/prop_sf/XCODE_LAST_KNOWN_FILE_TYPE.rst deleted file mode 100644 index b21891f..0000000 --- a/share/cmake-3.18/Help/prop_sf/XCODE_LAST_KNOWN_FILE_TYPE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -XCODE_LAST_KNOWN_FILE_TYPE --------------------------- - -Set the :generator:`Xcode` ``lastKnownFileType`` attribute on its reference to -a source file. CMake computes a default based on file extension but -can be told explicitly with this property. - -See also :prop_sf:`XCODE_EXPLICIT_FILE_TYPE`, which is preferred -over this property if set.
diff --git a/share/cmake-3.18/Help/prop_test/DISABLED.rst b/share/cmake-3.18/Help/prop_test/DISABLED.rst deleted file mode 100644 index 1d469e8..0000000 --- a/share/cmake-3.18/Help/prop_test/DISABLED.rst +++ /dev/null
@@ -1,15 +0,0 @@ -DISABLED --------- - -If set to ``True``, the test will be skipped and its status will be 'Not Run'. A -``DISABLED`` test will not be counted in the total number of tests and its -completion status will be reported to CDash as ``Disabled``. - -A ``DISABLED`` test does not participate in test fixture dependency resolution. -If a ``DISABLED`` test has fixture requirements defined in its -:prop_test:`FIXTURES_REQUIRED` property, it will not cause setup or cleanup -tests for those fixtures to be added to the test set. - -If a test with the :prop_test:`FIXTURES_SETUP` property set is ``DISABLED``, -the fixture behavior will be as though that setup test was passing and any test -case requiring that fixture will still run.
diff --git a/share/cmake-3.18/Help/prop_test/ENVIRONMENT.rst b/share/cmake-3.18/Help/prop_test/ENVIRONMENT.rst deleted file mode 100644 index 102c792..0000000 --- a/share/cmake-3.18/Help/prop_test/ENVIRONMENT.rst +++ /dev/null
@@ -1,9 +0,0 @@ -ENVIRONMENT ------------ - -Specify environment variables that should be defined for running a test. - -If set to a list of environment variables and values of the form -``MYVAR=value`` those environment variables will be defined while running -the test. The environment is restored to its previous state after the -test is done.
diff --git a/share/cmake-3.18/Help/prop_test/FAIL_REGULAR_EXPRESSION.rst b/share/cmake-3.18/Help/prop_test/FAIL_REGULAR_EXPRESSION.rst deleted file mode 100644 index facf902..0000000 --- a/share/cmake-3.18/Help/prop_test/FAIL_REGULAR_EXPRESSION.rst +++ /dev/null
@@ -1,15 +0,0 @@ -FAIL_REGULAR_EXPRESSION ------------------------ - -If the output matches this regular expression the test will fail. - -If set, if the output matches one of specified regular expressions, -the test will fail. Example: - -.. code-block:: cmake - - set_tests_properties(mytest PROPERTIES - FAIL_REGULAR_EXPRESSION "[^a-z]Error;ERROR;Failed" - ) - -``FAIL_REGULAR_EXPRESSION`` expects a list of regular expressions.
diff --git a/share/cmake-3.18/Help/prop_test/FIXTURES_CLEANUP.rst b/share/cmake-3.18/Help/prop_test/FIXTURES_CLEANUP.rst deleted file mode 100644 index 3075b4d..0000000 --- a/share/cmake-3.18/Help/prop_test/FIXTURES_CLEANUP.rst +++ /dev/null
@@ -1,47 +0,0 @@ -FIXTURES_CLEANUP ----------------- - -Specifies a list of fixtures for which the test is to be treated as a cleanup -test. These fixture names are distinct from test case names and are not -required to have any similarity to the names of tests associated with them. - -Fixture cleanup tests are ordinary tests with all of the usual test -functionality. Setting the ``FIXTURES_CLEANUP`` property for a test has two -primary effects: - -- CTest will ensure the test executes after all other tests which list any of - the fixtures in its :prop_test:`FIXTURES_REQUIRED` property. - -- If CTest is asked to run only a subset of tests (e.g. using regular - expressions or the ``--rerun-failed`` option) and the cleanup test is not in - the set of tests to run, it will automatically be added if any tests in the - set require any fixture listed in ``FIXTURES_CLEANUP``. - -A cleanup test can have multiple fixtures listed in its ``FIXTURES_CLEANUP`` -property. It will execute only once for the whole CTest run, not once for each -fixture. A fixture can also have more than one cleanup test defined. If there -are multiple cleanup tests for a fixture, projects can control their order with -the usual :prop_test:`DEPENDS` test property if necessary. - -A cleanup test is allowed to require other fixtures, but not any fixture listed -in its ``FIXTURES_CLEANUP`` property. For example: - -.. code-block:: cmake - - # Ok: Dependent fixture is different to cleanup - set_tests_properties(cleanupFoo PROPERTIES - FIXTURES_CLEANUP Foo - FIXTURES_REQUIRED Bar - ) - - # Error: cannot require same fixture as cleanup - set_tests_properties(cleanupFoo PROPERTIES - FIXTURES_CLEANUP Foo - FIXTURES_REQUIRED Foo - ) - -Cleanup tests will execute even if setup or regular tests for that fixture fail -or are skipped. - -See :prop_test:`FIXTURES_REQUIRED` for a more complete discussion of how to use -test fixtures.
diff --git a/share/cmake-3.18/Help/prop_test/FIXTURES_REQUIRED.rst b/share/cmake-3.18/Help/prop_test/FIXTURES_REQUIRED.rst deleted file mode 100644 index e3f60c4..0000000 --- a/share/cmake-3.18/Help/prop_test/FIXTURES_REQUIRED.rst +++ /dev/null
@@ -1,96 +0,0 @@ -FIXTURES_REQUIRED ------------------ - -Specifies a list of fixtures the test requires. Fixture names are case -sensitive and they are not required to have any similarity to test names. - -Fixtures are a way to attach setup and cleanup tasks to a set of tests. If a -test requires a given fixture, then all tests marked as setup tasks for that -fixture will be executed first (once for the whole set of tests, not once per -test requiring the fixture). After all tests requiring a particular fixture -have completed, CTest will ensure all tests marked as cleanup tasks for that -fixture are then executed. Tests are marked as setup tasks with the -:prop_test:`FIXTURES_SETUP` property and as cleanup tasks with the -:prop_test:`FIXTURES_CLEANUP` property. If any of a fixture's setup tests fail, -all tests listing that fixture in their ``FIXTURES_REQUIRED`` property will not -be executed. The cleanup tests for the fixture will always be executed, even if -some setup tests fail. - -When CTest is asked to execute only a subset of tests (e.g. by the use of -regular expressions or when run with the ``--rerun-failed`` command line -option), it will automatically add any setup or cleanup tests for fixtures -required by any of the tests that are in the execution set. This behavior can -be overridden with the ``-FS``, ``-FC`` and ``-FA`` command line options to -:manual:`ctest(1)` if desired. - -Since setup and cleanup tasks are also tests, they can have an ordering -specified by the :prop_test:`DEPENDS` test property just like any other tests. -This can be exploited to implement setup or cleanup using multiple tests for a -single fixture to modularise setup or cleanup logic. - -The concept of a fixture is different to that of a resource specified by -:prop_test:`RESOURCE_LOCK`, but they may be used together. A fixture defines a -set of tests which share setup and cleanup requirements, whereas a resource -lock has the effect of ensuring a particular set of tests do not run in -parallel. Some situations may need both, such as setting up a database, -serialising test access to that database and deleting the database again at the -end. For such cases, tests would populate both ``FIXTURES_REQUIRED`` and -:prop_test:`RESOURCE_LOCK` to combine the two behaviours. Names used for -:prop_test:`RESOURCE_LOCK` have no relationship with names of fixtures, so note -that a resource lock does not imply a fixture and vice versa. - -Consider the following example which represents a database test scenario -similar to that mentioned above: - -.. code-block:: cmake - - add_test(NAME testsDone COMMAND emailResults) - add_test(NAME fooOnly COMMAND testFoo) - add_test(NAME dbOnly COMMAND testDb) - add_test(NAME dbWithFoo COMMAND testDbWithFoo) - add_test(NAME createDB COMMAND initDB) - add_test(NAME setupUsers COMMAND userCreation) - add_test(NAME cleanupDB COMMAND deleteDB) - add_test(NAME cleanupFoo COMMAND removeFoos) - - set_tests_properties(setupUsers PROPERTIES DEPENDS createDB) - - set_tests_properties(createDB PROPERTIES FIXTURES_SETUP DB) - set_tests_properties(setupUsers PROPERTIES FIXTURES_SETUP DB) - set_tests_properties(cleanupDB PROPERTIES FIXTURES_CLEANUP DB) - set_tests_properties(cleanupFoo PROPERTIES FIXTURES_CLEANUP Foo) - set_tests_properties(testsDone PROPERTIES FIXTURES_CLEANUP "DB;Foo") - - set_tests_properties(fooOnly PROPERTIES FIXTURES_REQUIRED Foo) - set_tests_properties(dbOnly PROPERTIES FIXTURES_REQUIRED DB) - set_tests_properties(dbWithFoo PROPERTIES FIXTURES_REQUIRED "DB;Foo") - - set_tests_properties(dbOnly dbWithFoo createDB setupUsers cleanupDB - PROPERTIES RESOURCE_LOCK DbAccess) - -Key points from this example: - -- Two fixtures are defined: ``DB`` and ``Foo``. Tests can require a single - fixture as ``fooOnly`` and ``dbOnly`` do, or they can depend on multiple - fixtures like ``dbWithFoo`` does. - -- A ``DEPENDS`` relationship is set up to ensure ``setupUsers`` happens after - ``createDB``, both of which are setup tests for the ``DB`` fixture and will - therefore be executed before the ``dbOnly`` and ``dbWithFoo`` tests - automatically. - -- No explicit ``DEPENDS`` relationships were needed to make the setup tests run - before or the cleanup tests run after the regular tests. - -- The ``Foo`` fixture has no setup tests defined, only a single cleanup test. - -- ``testsDone`` is a cleanup test for both the ``DB`` and ``Foo`` fixtures. - Therefore, it will only execute once regular tests for both fixtures have - finished (i.e. after ``fooOnly``, ``dbOnly`` and ``dbWithFoo``). No - ``DEPENDS`` relationship was specified for ``testsDone``, so it is free to - run before, after or concurrently with other cleanup tests for either - fixture. - -- The setup and cleanup tests never list the fixtures they are for in their own - ``FIXTURES_REQUIRED`` property, as that would result in a dependency on - themselves and be considered an error.
diff --git a/share/cmake-3.18/Help/prop_test/FIXTURES_SETUP.rst b/share/cmake-3.18/Help/prop_test/FIXTURES_SETUP.rst deleted file mode 100644 index fdb21cc..0000000 --- a/share/cmake-3.18/Help/prop_test/FIXTURES_SETUP.rst +++ /dev/null
@@ -1,48 +0,0 @@ -FIXTURES_SETUP --------------- - -Specifies a list of fixtures for which the test is to be treated as a setup -test. These fixture names are distinct from test case names and are not -required to have any similarity to the names of tests associated with them. - -Fixture setup tests are ordinary tests with all of the usual test -functionality. Setting the ``FIXTURES_SETUP`` property for a test has two -primary effects: - -- CTest will ensure the test executes before any other test which lists the - fixture name(s) in its :prop_test:`FIXTURES_REQUIRED` property. - -- If CTest is asked to run only a subset of tests (e.g. using regular - expressions or the ``--rerun-failed`` option) and the setup test is not in - the set of tests to run, it will automatically be added if any tests in the - set require any fixture listed in ``FIXTURES_SETUP``. - -A setup test can have multiple fixtures listed in its ``FIXTURES_SETUP`` -property. It will execute only once for the whole CTest run, not once for each -fixture. A fixture can also have more than one setup test defined. If there are -multiple setup tests for a fixture, projects can control their order with the -usual :prop_test:`DEPENDS` test property if necessary. - -A setup test is allowed to require other fixtures, but not any fixture listed -in its ``FIXTURES_SETUP`` property. For example: - -.. code-block:: cmake - - # Ok: dependent fixture is different to setup - set_tests_properties(setupFoo PROPERTIES - FIXTURES_SETUP Foo - FIXTURES_REQUIRED Bar - ) - - # Error: cannot require same fixture as setup - set_tests_properties(setupFoo PROPERTIES - FIXTURES_SETUP Foo - FIXTURES_REQUIRED Foo - ) - -If any of a fixture's setup tests fail, none of the tests listing that fixture -in its :prop_test:`FIXTURES_REQUIRED` property will be run. Cleanup tests will, -however, still be executed. - -See :prop_test:`FIXTURES_REQUIRED` for a more complete discussion of how to use -test fixtures.
diff --git a/share/cmake-3.18/Help/prop_test/LABELS.rst b/share/cmake-3.18/Help/prop_test/LABELS.rst deleted file mode 100644 index 8d75570..0000000 --- a/share/cmake-3.18/Help/prop_test/LABELS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -LABELS ------- - -Specify a list of text labels associated with a test. - -The list is reported in dashboard submissions.
diff --git a/share/cmake-3.18/Help/prop_test/PASS_REGULAR_EXPRESSION.rst b/share/cmake-3.18/Help/prop_test/PASS_REGULAR_EXPRESSION.rst deleted file mode 100644 index 0cd6215..0000000 --- a/share/cmake-3.18/Help/prop_test/PASS_REGULAR_EXPRESSION.rst +++ /dev/null
@@ -1,16 +0,0 @@ -PASS_REGULAR_EXPRESSION ------------------------ - -The output must match this regular expression for the test to pass. - -If set, the test output will be checked against the specified regular -expressions and at least one of the regular expressions has to match, -otherwise the test will fail. Example: - -.. code-block:: cmake - - set_tests_properties(mytest PROPERTIES - PASS_REGULAR_EXPRESSION "TestPassed;All ok" - ) - -``PASS_REGULAR_EXPRESSION`` expects a list of regular expressions.
diff --git a/share/cmake-3.18/Help/prop_test/PROCESSOR_AFFINITY.rst b/share/cmake-3.18/Help/prop_test/PROCESSOR_AFFINITY.rst deleted file mode 100644 index 38ec179..0000000 --- a/share/cmake-3.18/Help/prop_test/PROCESSOR_AFFINITY.rst +++ /dev/null
@@ -1,11 +0,0 @@ -PROCESSOR_AFFINITY ------------------- - -Set to a true value to ask CTest to launch the test process with CPU affinity -for a fixed set of processors. If enabled and supported for the current -platform, CTest will choose a set of processors to place in the CPU affinity -mask when launching the test process. The number of processors in the set is -determined by the :prop_test:`PROCESSORS` test property or the number of -processors available to CTest, whichever is smaller. The set of processors -chosen will be disjoint from the processors assigned to other concurrently -running tests that also have the ``PROCESSOR_AFFINITY`` property enabled.
diff --git a/share/cmake-3.18/Help/prop_test/RESOURCE_GROUPS.rst b/share/cmake-3.18/Help/prop_test/RESOURCE_GROUPS.rst deleted file mode 100644 index 63c56ce..0000000 --- a/share/cmake-3.18/Help/prop_test/RESOURCE_GROUPS.rst +++ /dev/null
@@ -1,70 +0,0 @@ -RESOURCE_GROUPS ---------------- - -Specify resources required by a test, grouped in a way that is meaningful to -the test. See :ref:`resource allocation <ctest-resource-allocation>` -for more information on how this property integrates into the CTest resource -allocation feature. - -The ``RESOURCE_GROUPS`` property is a :ref:`semicolon-separated list <CMake -Language Lists>` of group descriptions. Each entry consists of an optional -number of groups using the description followed by a series of resource -requirements for those groups. These requirements (and the number of groups) -are separated by commas. The resource requirements consist of the name of a -resource type, followed by a colon, followed by an unsigned integer -specifying the number of slots required on one resource of the given type. - -The ``RESOURCE_GROUPS`` property tells CTest what resources a test expects -to use grouped in a way meaningful to the test. The test itself must read -the :ref:`environment variables <ctest-resource-environment-variables>` to -determine which resources have been allocated to each group. For example, -each group may correspond to a process the test will spawn when executed. - -Consider the following example: - -.. code-block:: cmake - - add_test(NAME MyTest COMMAND MyExe) - set_property(TEST MyTest PROPERTY RESOURCE_GROUPS - "2,gpus:2" - "gpus:4,crypto_chips:2") - -In this example, there are two group descriptions (implicitly separated by a -semicolon.) The content of the first description is ``2,gpus:2``. This -description specifies 2 groups, each of which requires 2 slots from a single -GPU. The content of the second description is ``gpus:4,crypto_chips:2``. This -description does not specify a group count, so a default of 1 is assumed. -This single group requires 4 slots from a single GPU and 2 slots from a -single cryptography chip. In total, 3 resource groups are specified for this -test, each with its own unique requirements. - -Note that the number of slots following the resource type specifies slots from -a *single* instance of the resource. If the resource group can tolerate -receiving slots from different instances of the same resource, it can indicate -this by splitting the specification into multiple requirements of one slot. For -example: - -.. code-block:: cmake - - add_test(NAME MyTest COMMAND MyExe) - set_property(TEST MyTest PROPERTY RESOURCE_GROUPS - "gpus:1,gpus:1,gpus:1,gpus:1") - -In this case, the single resource group indicates that it needs four GPU slots, -all of which may come from separate GPUs (though they don't have to; CTest may -still assign slots from the same GPU.) - -When CTest sets the :ref:`environment variables -<ctest-resource-environment-variables>` for a test, it assigns a group number -based on the group description, starting at 0 on the left and the number of -groups minus 1 on the right. For example, in the example above, the two -groups in the first description would have IDs of 0 and 1, and the single -group in the second description would have an ID of 2. - -Both the ``RESOURCE_GROUPS`` and :prop_test:`RESOURCE_LOCK` properties serve -similar purposes, but they are distinct and orthogonal. Resources specified by -``RESOURCE_GROUPS`` do not affect :prop_test:`RESOURCE_LOCK`, and vice versa. -Whereas :prop_test:`RESOURCE_LOCK` is a simpler property that is used for -locking one global resource, ``RESOURCE_GROUPS`` is a more advanced property -that allows multiple tests to simultaneously use multiple resources of the -same type, specifying their requirements in a fine-grained manner.
diff --git a/share/cmake-3.18/Help/prop_test/SKIP_REGULAR_EXPRESSION.rst b/share/cmake-3.18/Help/prop_test/SKIP_REGULAR_EXPRESSION.rst deleted file mode 100644 index 2c6d980..0000000 --- a/share/cmake-3.18/Help/prop_test/SKIP_REGULAR_EXPRESSION.rst +++ /dev/null
@@ -1,17 +0,0 @@ -SKIP_REGULAR_EXPRESSION ------------------------ - -If the output matches this regular expression the test will be marked as skipped. - -If set, if the output matches one of specified regular expressions, -the test will be marked as skipped. Example: - -.. code-block:: cmake - - set_property(TEST mytest PROPERTY - SKIP_REGULAR_EXPRESSION "[^a-z]Skip" "SKIP" "Skipped" - ) - -``SKIP_REGULAR_EXPRESSION`` expects a list of regular expressions. - -See also the :prop_test:`SKIP_RETURN_CODE` property.
diff --git a/share/cmake-3.18/Help/prop_test/TIMEOUT_AFTER_MATCH.rst b/share/cmake-3.18/Help/prop_test/TIMEOUT_AFTER_MATCH.rst deleted file mode 100644 index d607992..0000000 --- a/share/cmake-3.18/Help/prop_test/TIMEOUT_AFTER_MATCH.rst +++ /dev/null
@@ -1,39 +0,0 @@ -TIMEOUT_AFTER_MATCH -------------------- - -Change a test's timeout duration after a matching line is encountered -in its output. - -Usage -^^^^^ - -.. code-block:: cmake - - add_test(mytest ...) - set_property(TEST mytest PROPERTY TIMEOUT_AFTER_MATCH "${seconds}" "${regex}") - -Description -^^^^^^^^^^^ - -Allow a test ``seconds`` to complete after ``regex`` is encountered in -its output. - -When the test outputs a line that matches ``regex`` its start time is -reset to the current time and its timeout duration is changed to -``seconds``. Prior to this, the timeout duration is determined by the -:prop_test:`TIMEOUT` property or the :variable:`CTEST_TEST_TIMEOUT` -variable if either of these are set. Because the test's start time is -reset, its execution time will not include any time that was spent -waiting for the matching output. - -:prop_test:`TIMEOUT_AFTER_MATCH` is useful for avoiding spurious -timeouts when your test must wait for some system resource to become -available before it can execute. Set :prop_test:`TIMEOUT` to a longer -duration that accounts for resource acquisition and use -:prop_test:`TIMEOUT_AFTER_MATCH` to control how long the actual test -is allowed to run. - -If the required resource can be controlled by CTest you should use -:prop_test:`RESOURCE_LOCK` instead of :prop_test:`TIMEOUT_AFTER_MATCH`. -This property should be used when only the test itself can determine -when its required resources are available.
diff --git a/share/cmake-3.18/Help/prop_tgt/ADDITIONAL_CLEAN_FILES.rst b/share/cmake-3.18/Help/prop_tgt/ADDITIONAL_CLEAN_FILES.rst deleted file mode 100644 index 3b9d965..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ADDITIONAL_CLEAN_FILES.rst +++ /dev/null
@@ -1,23 +0,0 @@ -ADDITIONAL_CLEAN_FILES ----------------------- - -A :ref:`;-list <CMake Language Lists>` of files or directories that will be -removed as a part of the global ``clean`` target. It can be used to specify -files and directories that are generated as part of building the target or -that are directly associated with the target in some way (e.g. created as a -result of running the target). - -For custom targets, if such files can be captured as outputs or byproducts -instead, then that should be preferred over adding them to this property. -If an additional clean file is used by multiple targets or isn't -target-specific, then the :prop_dir:`ADDITIONAL_CLEAN_FILES` directory -property may be the more appropriate property to use. - -Relative paths are allowed and are interpreted relative to the -current binary directory. - -Contents of ``ADDITIONAL_CLEAN_FILES`` may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. - -This property only works for the :generator:`Ninja` and the Makefile -generators. It is ignored by other generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.rst b/share/cmake-3.18/Help/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.rst deleted file mode 100644 index 15ddc0b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -AIX_EXPORT_ALL_SYMBOLS ----------------------- - -On AIX, CMake automatically exports all symbols from shared libraries, and -from executables with the :prop_tgt:`ENABLE_EXPORTS` target property set. -Explicitly disable this boolean property to suppress the behavior and -export no symbols by default. In this case it is expected that the project -will use other means to export some symbols. - -This property is initialized by the value of -the :variable:`CMAKE_AIX_EXPORT_ALL_SYMBOLS` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ALIAS_GLOBAL.rst b/share/cmake-3.18/Help/prop_tgt/ALIAS_GLOBAL.rst deleted file mode 100644 index 8854f57..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ALIAS_GLOBAL.rst +++ /dev/null
@@ -1,17 +0,0 @@ -ALIAS_GLOBAL ------------- - -Read-only property indicating of whether an :ref:`ALIAS target <Alias Targets>` -is globally visible. - -The boolean value of this property is ``TRUE`` for aliases to -:ref:`IMPORTED targets <Imported Targets>` created -with the ``GLOBAL`` options to :command:`add_executable()` or -:command:`add_library()`, ``FALSE`` otherwise. It is undefined for -targets built within the project. - -.. note:: - - Promoting an :ref:`IMPORTED target <Imported Targets>` from ``LOCAL`` - to ``GLOBAL`` scope by changing the value or :prop_tgt:`IMPORTED_GLOBAL` - target property do not change the scope of local aliases.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.rst deleted file mode 100644 index af6b405..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -ANDROID_ANT_ADDITIONAL_OPTIONS ------------------------------- - -Set the additional options for Android Ant build system. This is -a string value containing all command line options for the Ant build. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS` variable if it is -set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_API.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_API.rst deleted file mode 100644 index 63464d7..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_API.rst +++ /dev/null
@@ -1,8 +0,0 @@ -ANDROID_API ------------ - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this property sets the Android target API version (e.g. ``15``). -The version number must be a positive decimal integer. This property is -initialized by the value of the :variable:`CMAKE_ANDROID_API` variable if -it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_API_MIN.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_API_MIN.rst deleted file mode 100644 index 773ab3f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_API_MIN.rst +++ /dev/null
@@ -1,7 +0,0 @@ -ANDROID_API_MIN ---------------- - -Set the Android MIN API version (e.g. ``9``). The version number -must be a positive decimal integer. This property is initialized by -the value of the :variable:`CMAKE_ANDROID_API_MIN` variable if it is set -when a target is created. Native code builds using this API version.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_ARCH.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_ARCH.rst deleted file mode 100644 index 3e07e5a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_ARCH.rst +++ /dev/null
@@ -1,18 +0,0 @@ -ANDROID_ARCH ------------- - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this property sets the Android target architecture. - -This is a string property that could be set to the one of -the following values: - -* ``armv7-a``: "ARMv7-A (armv7-a)" -* ``armv7-a-hard``: "ARMv7-A, hard-float ABI (armv7-a)" -* ``arm64-v8a``: "ARMv8-A, 64bit (arm64-v8a)" -* ``x86``: "x86 (x86)" -* ``x86_64``: "x86_64 (x86_64)" - -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_ARCH` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_ASSETS_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_ASSETS_DIRECTORIES.rst deleted file mode 100644 index 764a582..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_ASSETS_DIRECTORIES.rst +++ /dev/null
@@ -1,9 +0,0 @@ -ANDROID_ASSETS_DIRECTORIES --------------------------- - -Set the Android assets directories to copy into the main assets -folder before build. This a string property that contains the -directory paths separated by semicolon. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_ASSETS_DIRECTORIES` variable if it is set when -a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_GUI.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_GUI.rst deleted file mode 100644 index 92e2041..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_GUI.rst +++ /dev/null
@@ -1,15 +0,0 @@ -ANDROID_GUI ------------ - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this property specifies whether to build an executable as an -application package on Android. - -When this property is set to true the executable when built for Android -will be created as an application package. This property is initialized -by the value of the :variable:`CMAKE_ANDROID_GUI` variable if it is set -when a target is created. - -Add the ``AndroidManifest.xml`` source file explicitly to the -target :command:`add_executable` command invocation to specify the -root directory of the application package source.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DEPENDENCIES.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DEPENDENCIES.rst deleted file mode 100644 index 42937c1..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DEPENDENCIES.rst +++ /dev/null
@@ -1,7 +0,0 @@ -ANDROID_JAR_DEPENDENCIES ------------------------- - -Set the Android property that specifies JAR dependencies. -This is a string value property. This property is initialized -by the value of the :variable:`CMAKE_ANDROID_JAR_DEPENDENCIES` -variable if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DIRECTORIES.rst deleted file mode 100644 index 54f0a8f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAR_DIRECTORIES.rst +++ /dev/null
@@ -1,14 +0,0 @@ -ANDROID_JAR_DIRECTORIES ------------------------ - -Set the Android property that specifies directories to search for -the JAR libraries. - -This a string property that contains the directory paths separated by -semicolons. This property is initialized by the value of the -:variable:`CMAKE_ANDROID_JAR_DIRECTORIES` variable if it is set when -a target is created. - -Contents of ``ANDROID_JAR_DIRECTORIES`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAVA_SOURCE_DIR.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_JAVA_SOURCE_DIR.rst deleted file mode 100644 index 90ef1ce..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_JAVA_SOURCE_DIR.rst +++ /dev/null
@@ -1,8 +0,0 @@ -ANDROID_JAVA_SOURCE_DIR ------------------------ - -Set the Android property that defines the Java source code root directories. -This a string property that contains the directory paths separated by semicolon. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_JAVA_SOURCE_DIR` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.rst deleted file mode 100644 index 759a37b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.rst +++ /dev/null
@@ -1,14 +0,0 @@ -ANDROID_NATIVE_LIB_DEPENDENCIES -------------------------------- - -Set the Android property that specifies the .so dependencies. -This is a string property. - -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES` variable if it is set -when a target is created. - -Contents of ``ANDROID_NATIVE_LIB_DEPENDENCIES`` may use -"generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for -available expressions.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.rst deleted file mode 100644 index d0cd29d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.rst +++ /dev/null
@@ -1,16 +0,0 @@ -ANDROID_NATIVE_LIB_DIRECTORIES ------------------------------- - -Set the Android property that specifies directories to search for the ``.so`` -libraries. - -This a string property that contains the directory paths separated -by semicolons. - -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES` variable if it is set when a -target is created. - -Contents of ``ANDROID_NATIVE_LIB_DIRECTORIES`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROCESS_MAX.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_PROCESS_MAX.rst deleted file mode 100644 index 847acae..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROCESS_MAX.rst +++ /dev/null
@@ -1,8 +0,0 @@ -ANDROID_PROCESS_MAX -------------------- - -Set the Android property that defines the maximum number of a -parallel Android NDK compiler processes (e.g. ``4``). -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_PROCESS_MAX` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD.rst deleted file mode 100644 index dafc51e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD.rst +++ /dev/null
@@ -1,9 +0,0 @@ -ANDROID_PROGUARD ----------------- - -When this property is set to true that enables the ProGuard tool to shrink, -optimize, and obfuscate the code by removing unused code and renaming -classes, fields, and methods with semantically obscure names. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_PROGUARD` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.rst deleted file mode 100644 index 0e929d1..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.rst +++ /dev/null
@@ -1,9 +0,0 @@ -ANDROID_PROGUARD_CONFIG_PATH ----------------------------- - -Set the Android property that specifies the location of the ProGuard -config file. Leave empty to use the default one. -This a string property that contains the path to ProGuard config file. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_PROGUARD_CONFIG_PATH` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_SECURE_PROPS_PATH.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_SECURE_PROPS_PATH.rst deleted file mode 100644 index 9533f1a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_SECURE_PROPS_PATH.rst +++ /dev/null
@@ -1,8 +0,0 @@ -ANDROID_SECURE_PROPS_PATH -------------------------- - -Set the Android property that states the location of the secure properties file. -This is a string property that contains the file path. -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_SECURE_PROPS_PATH` variable -if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_SKIP_ANT_STEP.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_SKIP_ANT_STEP.rst deleted file mode 100644 index 6361896..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_SKIP_ANT_STEP.rst +++ /dev/null
@@ -1,6 +0,0 @@ -ANDROID_SKIP_ANT_STEP ---------------------- - -Set the Android property that defines whether or not to skip the Ant build step. -This is a boolean property initialized by the value of the -:variable:`CMAKE_ANDROID_SKIP_ANT_STEP` variable if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ANDROID_STL_TYPE.rst b/share/cmake-3.18/Help/prop_tgt/ANDROID_STL_TYPE.rst deleted file mode 100644 index 386e96e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ANDROID_STL_TYPE.rst +++ /dev/null
@@ -1,27 +0,0 @@ -ANDROID_STL_TYPE ----------------- - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this property specifies the type of STL support for the project. -This is a string property that could set to the one of the following values: - -``none`` - No C++ Support -``system`` - Minimal C++ without STL -``gabi++_static`` - GAbi++ Static -``gabi++_shared`` - GAbi++ Shared -``gnustl_static`` - GNU libstdc++ Static -``gnustl_shared`` - GNU libstdc++ Shared -``stlport_static`` - STLport Static -``stlport_shared`` - STLport Shared - -This property is initialized by the value of the -:variable:`CMAKE_ANDROID_STL_TYPE` variable if it is set when a target is -created.
diff --git a/share/cmake-3.18/Help/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.rst deleted file mode 100644 index 4221069..0000000 --- a/share/cmake-3.18/Help/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.rst +++ /dev/null
@@ -1,9 +0,0 @@ -ARCHIVE_OUTPUT_DIRECTORY ------------------------- - -.. |XXX| replace:: :ref:`ARCHIVE <Archive Output Artifacts>` -.. |xxx| replace:: archive -.. |CMAKE_XXX_OUTPUT_DIRECTORY| replace:: CMAKE_ARCHIVE_OUTPUT_DIRECTORY -.. include:: XXX_OUTPUT_DIRECTORY.txt - -See also the :prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>` target property.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_BUILD_DIR.rst b/share/cmake-3.18/Help/prop_tgt/AUTOGEN_BUILD_DIR.rst deleted file mode 100644 index 909b14c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_BUILD_DIR.rst +++ /dev/null
@@ -1,17 +0,0 @@ -AUTOGEN_BUILD_DIR ------------------ - -Directory where :prop_tgt:`AUTOMOC`, :prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` -generate files for the target. - -The directory is created on demand and automatically added to the -:prop_tgt:`ADDITIONAL_CLEAN_FILES` target property. - -When unset or empty the directory ``<dir>/<target-name>_autogen`` is used where -``<dir>`` is :variable:`CMAKE_CURRENT_BINARY_DIR` and ``<target-name>`` -is :prop_tgt:`NAME`. - -By default :prop_tgt:`AUTOGEN_BUILD_DIR` is unset. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.rst b/share/cmake-3.18/Help/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.rst deleted file mode 100644 index 022bab5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.rst +++ /dev/null
@@ -1,38 +0,0 @@ -AUTOGEN_ORIGIN_DEPENDS ----------------------- - -Switch for forwarding origin target dependencies to the corresponding -``_autogen`` target. - -Targets which have their :prop_tgt:`AUTOMOC` or :prop_tgt:`AUTOUIC` property -``ON`` have a corresponding ``_autogen`` target which generates -``moc`` and ``uic`` files. As this ``_autogen`` target is created at -generate-time, it is not possible to define dependencies of it using -e.g. :command:`add_dependencies`. Instead the -:prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` target property decides whether the origin -target dependencies should be forwarded to the ``_autogen`` target or not. - -By default :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` is initialized from -:variable:`CMAKE_AUTOGEN_ORIGIN_DEPENDS` which is ``ON`` by default. - -In total the dependencies of the ``_autogen`` target are composed from - -- forwarded origin target dependencies - (enabled by default via :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS`) -- additional user defined dependencies from :prop_tgt:`AUTOGEN_TARGET_DEPENDS` - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt. - -Note -^^^^ - -Disabling :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` is useful to avoid building of -origin target dependencies when building the ``_autogen`` target only. -This is especially interesting when a -:variable:`global autogen target <CMAKE_GLOBAL_AUTOGEN_TARGET>` is enabled. - -When the ``_autogen`` target doesn't require all the origin target's -dependencies, and :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` is disabled, it might be -necessary to extend :prop_tgt:`AUTOGEN_TARGET_DEPENDS` to add missing -dependencies.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_PARALLEL.rst b/share/cmake-3.18/Help/prop_tgt/AUTOGEN_PARALLEL.rst deleted file mode 100644 index 968b619..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOGEN_PARALLEL.rst +++ /dev/null
@@ -1,21 +0,0 @@ -AUTOGEN_PARALLEL ----------------- - -Number of parallel ``moc`` or ``uic`` processes to start when using -:prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -The custom ``<origin>_autogen`` target starts a number of threads of which -each one parses a source file and on demand starts a ``moc`` or ``uic`` -process. ``AUTOGEN_PARALLEL`` controls how many parallel threads -(and therefore ``moc`` or ``uic`` processes) are started. - -- An empty (or unset) value or the string ``AUTO`` sets the number of - threads/processes to the number of physical CPUs on the host system. -- A positive non zero integer value sets the exact thread/process count. -- Otherwise a single thread/process is started. - -By default ``AUTOGEN_PARALLEL`` is initialized from -:variable:`CMAKE_AUTOGEN_PARALLEL`. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC.rst deleted file mode 100644 index c18859b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC.rst +++ /dev/null
@@ -1,247 +0,0 @@ -AUTOMOC -------- - -Should the target be processed with auto-moc (for Qt projects). - -:prop_tgt:`AUTOMOC` is a boolean specifying whether CMake will handle the Qt -``moc`` preprocessor automatically, i.e. without having to use the -:module:`QT4_WRAP_CPP() <FindQt4>` or ``QT5_WRAP_CPP()`` macro. -Currently Qt4 and Qt5 are supported. - -This property is initialized by the value of the :variable:`CMAKE_AUTOMOC` -variable if it is set when a target is created. - -When this property is set ``ON``, CMake will scan the header and -source files at build time and invoke ``moc`` accordingly. - - -Header file processing -^^^^^^^^^^^^^^^^^^^^^^ - -At configuration time, a list of header files that should be scanned by -:prop_tgt:`AUTOMOC` is computed from the target's sources. - -- All header files in the target's sources are added to the scan list. -- For all C++ source files ``<source_base>.<source_extension>`` in the - target's sources, CMake searches for - - - a regular header with the same base name - (``<source_base>.<header_extention>``) and - - a private header with the same base name and a ``_p`` suffix - (``<source_base>_p.<header_extention>``) - - and adds these to the scan list. - -At build time, CMake scans each unknown or modified header file from the -list and searches for - -- a Qt macro from :prop_tgt:`AUTOMOC_MACRO_NAMES`, -- additional file dependencies from the ``FILE`` argument of a - ``Q_PLUGIN_METADATA`` macro and -- additional file dependencies detected by filters defined in - :prop_tgt:`AUTOMOC_DEPEND_FILTERS`. - -If a Qt macro is found, then the header will be compiled by the ``moc`` to the -output file ``moc_<base_name>.cpp``. The complete output file path is -described in the section `Output file location`_. - -The header will be ``moc`` compiled again if a file from the additional file -dependencies changes. - -Header ``moc`` output files ``moc_<base_name>.cpp`` can be included in source -files. In the section `Including header moc files in sources`_ there is more -information on that topic. - - -Source file processing -^^^^^^^^^^^^^^^^^^^^^^ - -At build time, CMake scans each unknown or modified C++ source file from the -target's sources for - -- a Qt macro from :prop_tgt:`AUTOMOC_MACRO_NAMES`, -- includes of header ``moc`` files - (see `Including header moc files in sources`_), -- additional file dependencies from the ``FILE`` argument of a - ``Q_PLUGIN_METADATA`` macro and -- additional file dependencies detected by filters defined in - :prop_tgt:`AUTOMOC_DEPEND_FILTERS`. - -If a Qt macro is found, then the C++ source file -``<base>.<source_extension>`` is expected to as well contain an include -statement - -.. code-block:: c++ - - #include <<base>.moc> // or - #include "<base>.moc" - -The source file then will be compiled by the ``moc`` to the output file -``<base>.moc``. A description of the complete output file path is in section -`Output file location`_. - -The source will be ``moc`` compiled again if a file from the additional file -dependencies changes. - -Including header moc files in sources -""""""""""""""""""""""""""""""""""""" - -A source file can include the ``moc`` output file of a header -``<header_base>.<header_extension>`` by using an include statement of -the form - -.. code-block:: c++ - - #include <moc_<header_base>.cpp> // or - #include "moc_<header_base>.cpp" - -If the ``moc`` output file of a header is included by a source, it will -be generated in a different location than if it was not included. This is -described in the section `Output file location`_. - - -Output file location -^^^^^^^^^^^^^^^^^^^^ - -Included moc output files -""""""""""""""""""""""""" - -``moc`` output files that are included by a source file will be generated in - -- ``<AUTOGEN_BUILD_DIR>/include`` - for single configuration generators or in -- ``<AUTOGEN_BUILD_DIR>/include_<CONFIG>`` - for :prop_gbl:`multi configuration <GENERATOR_IS_MULTI_CONFIG>` generators. - -Where ``<AUTOGEN_BUILD_DIR>`` is the value of the target property -:prop_tgt:`AUTOGEN_BUILD_DIR`. - -The include directory is automatically added to the target's -:prop_tgt:`INCLUDE_DIRECTORIES`. - -Not included moc output files -""""""""""""""""""""""""""""" - -``moc`` output files that are not included in a source file will be generated -in - -- ``<AUTOGEN_BUILD_DIR>/<SOURCE_DIR_CHECKSUM>`` - for single configuration generators or in, -- ``<AUTOGEN_BUILD_DIR>/include_<CONFIG>/<SOURCE_DIR_CHECKSUM>`` - for :prop_gbl:`multi configuration <GENERATOR_IS_MULTI_CONFIG>` generators. - -Where ``<SOURCE_DIR_CHECKSUM>`` is a checksum computed from the relative -parent directory path of the ``moc`` input file. This scheme allows to have -``moc`` input files with the same name in different directories. - -All not included ``moc`` output files will be included automatically by the -CMake generated file - -- ``<AUTOGEN_BUILD_DIR>/mocs_compilation.cpp``, - -which is added to the target's sources. - - -Qt version detection -^^^^^^^^^^^^^^^^^^^^ - -:prop_tgt:`AUTOMOC` enabled targets need to know the Qt major and minor -version they're working with. The major version usually is provided by the -``INTERFACE_QT_MAJOR_VERSION`` property of the ``Qt[45]Core`` library, -that the target links to. To find the minor version, CMake builds a list of -available Qt versions from - -- ``Qt5Core_VERSION_MAJOR`` and ``Qt5Core_VERSION_MINOR`` variables - (usually set by ``find_package(Qt5...)``) -- ``Qt5Core_VERSION_MAJOR`` and ``Qt5Core_VERSION_MINOR`` directory properties -- ``QT_VERSION_MAJOR`` and ``QT_VERSION_MINOR`` variables - (usually set by ``find_package(Qt4...)``) -- ``QT_VERSION_MAJOR`` and ``QT_VERSION_MINOR`` directory properties - -in the context of the :command:`add_executable` or :command:`add_library` call. - -Assumed ``INTERFACE_QT_MAJOR_VERSION`` is a valid number, the first -entry in the list with a matching major version is taken. If no matching major -version was found, an error is generated. -If ``INTERFACE_QT_MAJOR_VERSION`` is not a valid number, the first -entry in the list is taken. - -A ``find_package(Qt[45]...)`` call sets the ``QT/Qt5Core_VERSION_MAJOR/MINOR`` -variables. If the call is in a different context than the -:command:`add_executable` or :command:`add_library` call, e.g. in a function, -then the version variables might not be available to the :prop_tgt:`AUTOMOC` -enabled target. -In that case the version variables can be forwarded from the -``find_package(Qt[45]...)`` calling context to the :command:`add_executable` -or :command:`add_library` calling context as directory properties. -The following Qt5 example demonstrates the procedure. - -.. code-block:: cmake - - function (add_qt5_client) - find_package(Qt5 REQUIRED QUIET COMPONENTS Core Widgets) - ... - set_property(DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}" - PROPERTY Qt5Core_VERSION_MAJOR "${Qt5Core_VERSION_MAJOR}") - set_property(DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}" - PROPERTY Qt5Core_VERSION_MINOR "${Qt5Core_VERSION_MAJOR}") - ... - endfunction () - ... - add_qt5_client() - add_executable(myTarget main.cpp) - target_link_libraries(myTarget Qt5::QtWidgets) - set_property(TARGET myTarget PROPERTY AUTOMOC ON) - - -Modifiers -^^^^^^^^^ - -:prop_tgt:`AUTOMOC_EXECUTABLE`: -The ``moc`` executable will be detected automatically, but can be forced to -a certain binary using this target property. - -:prop_tgt:`AUTOMOC_MOC_OPTIONS`: -Additional command line options for ``moc`` can be set in this target property. - -:prop_tgt:`AUTOMOC_MACRO_NAMES`: -This list of Qt macro names can be extended to search for additional macros in -headers and sources. - -:prop_tgt:`AUTOMOC_DEPEND_FILTERS`: -``moc`` dependency file names can be extracted from headers or sources by -defining file name filters in this target property. - -:prop_tgt:`AUTOMOC_COMPILER_PREDEFINES`: -Compiler pre definitions for ``moc`` are written to the ``moc_predefs.h`` file. -The generation of this file can be enabled or disabled in this target property. - -:prop_sf:`SKIP_AUTOMOC`: -Sources and headers can be excluded from :prop_tgt:`AUTOMOC` processing by -setting this source file property. - -:prop_sf:`SKIP_AUTOGEN`: -Source files can be excluded from :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` processing by -setting this source file property. - -:prop_gbl:`AUTOGEN_SOURCE_GROUP`: -This global property can be used to group files generated by -:prop_tgt:`AUTOMOC` or :prop_tgt:`AUTORCC` together in an IDE, e.g. in MSVS. - -:prop_gbl:`AUTOGEN_TARGETS_FOLDER`: -This global property can be used to group :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` targets together in an IDE, -e.g. in MSVS. - -:variable:`CMAKE_GLOBAL_AUTOGEN_TARGET`: -A global ``autogen`` target, that depends on all :prop_tgt:`AUTOMOC` or -:prop_tgt:`AUTOUIC` generated ``<ORIGIN>_autogen`` targets in the project, -will be generated when this variable is ``ON``. - -:prop_tgt:`AUTOGEN_PARALLEL`: -This target property controls the number of ``moc`` or ``uic`` processes to -start in parallel during builds. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.rst deleted file mode 100644 index 57a647f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.rst +++ /dev/null
@@ -1,24 +0,0 @@ -AUTOMOC_COMPILER_PREDEFINES ---------------------------- - -Boolean value used by :prop_tgt:`AUTOMOC` to determine if the -compiler pre definitions file ``moc_predefs.h`` should be generated. - -CMake generates a ``moc_predefs.h`` file with compiler pre definitions -from the output of the command defined in -:variable:`CMAKE_CXX_COMPILER_PREDEFINES_COMMAND <CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND>` -when - -- :prop_tgt:`AUTOMOC` is enabled, -- :prop_tgt:`AUTOMOC_COMPILER_PREDEFINES` is enabled, -- :variable:`CMAKE_CXX_COMPILER_PREDEFINES_COMMAND <CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND>` isn't empty and -- the Qt version is greater or equal 5.8. - -The ``moc_predefs.h`` file, which is generated in :prop_tgt:`AUTOGEN_BUILD_DIR`, -is passed to ``moc`` as the argument to the ``--include`` option. - -By default :prop_tgt:`AUTOMOC_COMPILER_PREDEFINES` is initialized from -:variable:`CMAKE_AUTOMOC_COMPILER_PREDEFINES`, which is ON by default. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_DEPEND_FILTERS.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC_DEPEND_FILTERS.rst deleted file mode 100644 index 6eda26c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_DEPEND_FILTERS.rst +++ /dev/null
@@ -1,107 +0,0 @@ -AUTOMOC_DEPEND_FILTERS ----------------------- - -Filter definitions used by :prop_tgt:`AUTOMOC` to extract file names from a -source file that are registered as additional dependencies for the -``moc`` file of the source file. - -Filters are defined as ``KEYWORD;REGULAR_EXPRESSION`` pairs. First the file -content is searched for ``KEYWORD``. If it is found at least once, then file -names are extracted by successively searching for ``REGULAR_EXPRESSION`` and -taking the first match group. - -The file name found in the first match group is searched for - -- first in the vicinity of the source file -- and afterwards in the target's :prop_tgt:`INCLUDE_DIRECTORIES`. - -If any of the extracted files changes, then the ``moc`` file for the source -file gets rebuilt even when the source file itself doesn't change. - -If any of the extracted files is :prop_sf:`GENERATED` or if it is not in the -target's sources, then it might be necessary to add it to the -``_autogen`` target dependencies. -See :prop_tgt:`AUTOGEN_TARGET_DEPENDS` for reference. - -By default :prop_tgt:`AUTOMOC_DEPEND_FILTERS` is initialized from -:variable:`CMAKE_AUTOMOC_DEPEND_FILTERS`, which is empty by default. - -From Qt 5.15.0 on this variable is ignored as moc is able to output the correct -dependencies. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt. - - -Example 1 -^^^^^^^^^ - -A header file ``my_class.hpp`` uses a custom macro ``JSON_FILE_MACRO`` which -is defined in an other header ``macros.hpp``. -We want the ``moc`` file of ``my_class.hpp`` to depend on the file name -argument of ``JSON_FILE_MACRO``:: - - // my_class.hpp - class My_Class : public QObject - { - Q_OBJECT - JSON_FILE_MACRO ( "info.json" ) - ... - }; - -In ``CMakeLists.txt`` we add a filter to -:variable:`CMAKE_AUTOMOC_DEPEND_FILTERS` like this:: - - list( APPEND CMAKE_AUTOMOC_DEPEND_FILTERS - "JSON_FILE_MACRO" - "[\n][ \t]*JSON_FILE_MACRO[ \t]*\\([ \t]*\"([^\"]+)\"" - ) - -We assume ``info.json`` is a plain (not :prop_sf:`GENERATED`) file that is -listed in the target's source. Therefore we do not need to add it to -:prop_tgt:`AUTOGEN_TARGET_DEPENDS`. - -Example 2 -^^^^^^^^^ - -In the target ``my_target`` a header file ``complex_class.hpp`` uses a -custom macro ``JSON_BASED_CLASS`` which is defined in an other header -``macros.hpp``:: - - // macros.hpp - ... - #define JSON_BASED_CLASS(name, json) \ - class name : public QObject \ - { \ - Q_OBJECT \ - Q_PLUGIN_METADATA(IID "demo" FILE json) \ - name() {} \ - }; - ... - -:: - - // complex_class.hpp - #pragma once - JSON_BASED_CLASS(Complex_Class, "meta.json") - // end of file - -Since ``complex_class.hpp`` doesn't contain a ``Q_OBJECT`` macro it would be -ignored by :prop_tgt:`AUTOMOC`. We change this by adding ``JSON_BASED_CLASS`` -to :variable:`CMAKE_AUTOMOC_MACRO_NAMES`:: - - list(APPEND CMAKE_AUTOMOC_MACRO_NAMES "JSON_BASED_CLASS") - -We want the ``moc`` file of ``complex_class.hpp`` to depend on -``meta.json``. So we add a filter to -:variable:`CMAKE_AUTOMOC_DEPEND_FILTERS`:: - - list(APPEND CMAKE_AUTOMOC_DEPEND_FILTERS - "JSON_BASED_CLASS" - "[\n^][ \t]*JSON_BASED_CLASS[ \t]*\\([^,]*,[ \t]*\"([^\"]+)\"" - ) - -Additionally we assume ``meta.json`` is :prop_sf:`GENERATED` which is -why we have to add it to :prop_tgt:`AUTOGEN_TARGET_DEPENDS`:: - - set_property(TARGET my_target APPEND PROPERTY AUTOGEN_TARGET_DEPENDS "meta.json")
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_EXECUTABLE.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC_EXECUTABLE.rst deleted file mode 100644 index 6b66ce8..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_EXECUTABLE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -AUTOMOC_EXECUTABLE ------------------- - -:prop_tgt:`AUTOMOC_EXECUTABLE` is file path pointing to the ``moc`` -executable to use for :prop_tgt:`AUTOMOC` enabled files. Setting -this property will make CMake skip the automatic detection of the -``moc`` binary as well as the sanity-tests normally run to ensure -that the binary is available and working as expected. - -Usually this property does not need to be set. Only consider this -property if auto-detection of ``moc`` can not work -- e.g. because -you are building the ``moc`` binary as part of your project. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_MACRO_NAMES.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC_MACRO_NAMES.rst deleted file mode 100644 index 5329bba..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_MACRO_NAMES.rst +++ /dev/null
@@ -1,32 +0,0 @@ -AUTOMOC_MACRO_NAMES -------------------- - -A :ref:`semicolon-separated list <CMake Language Lists>` list of macro names used by -:prop_tgt:`AUTOMOC` to determine if a C++ file needs to be processed by ``moc``. - -This property is only used if the :prop_tgt:`AUTOMOC` property is ``ON`` -for this target. - -When running :prop_tgt:`AUTOMOC`, CMake searches for the strings listed in -:prop_tgt:`AUTOMOC_MACRO_NAMES` in C++ source and header files. -If any of the strings is found - -- as the first non space string on a new line or -- as the first non space string after a ``{`` on a new line, - -then the file will be processed by ``moc``. - -By default :prop_tgt:`AUTOMOC_MACRO_NAMES` is initialized from -:variable:`CMAKE_AUTOMOC_MACRO_NAMES`. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt. - -Example -^^^^^^^ - -In this case the ``Q_OBJECT`` macro is hidden inside another macro -called ``CUSTOM_MACRO``. To let CMake know that source files that contain -``CUSTOM_MACRO`` need to be ``moc`` processed, we call:: - - set_property(TARGET tgt APPEND PROPERTY AUTOMOC_MACRO_NAMES "CUSTOM_MACRO")
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_PATH_PREFIX.rst b/share/cmake-3.18/Help/prop_tgt/AUTOMOC_PATH_PREFIX.rst deleted file mode 100644 index 3e3059d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOMOC_PATH_PREFIX.rst +++ /dev/null
@@ -1,32 +0,0 @@ -AUTOMOC_PATH_PREFIX -------------------- - -When this property is ``ON``, CMake will generate the ``-p`` path prefix -option for ``moc`` on :prop_tgt:`AUTOMOC` enabled Qt targets. - -To generate the path prefix, CMake tests if the header compiled by ``moc`` -is in any of the target -:command:`include directories <target_include_directories>`. If so, CMake will -compute the relative path accordingly. If the header is not in the -:command:`include directories <target_include_directories>`, CMake will omit -the ``-p`` path prefix option. ``moc`` usually generates a -relative include path in that case. - -:prop_tgt:`AUTOMOC_PATH_PREFIX` is initialized from the variable -:variable:`CMAKE_AUTOMOC_PATH_PREFIX`, which is ``ON`` by default. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt. - -Reproducible builds -^^^^^^^^^^^^^^^^^^^ - -For reproducible builds it is recommended to keep headers that are ``moc`` -compiled in one of the target -:command:`include directories <target_include_directories>` and set -:prop_tgt:`AUTOMOC_PATH_PREFIX` to ``ON`` (which is the default). This ensures -that: - -- ``moc`` output files are identical on different build setups, -- ``moc`` output files will compile correctly when the source and/or - build directory is a symbolic link.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTORCC.rst b/share/cmake-3.18/Help/prop_tgt/AUTORCC.rst deleted file mode 100644 index 9a98f44..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTORCC.rst +++ /dev/null
@@ -1,62 +0,0 @@ -AUTORCC -------- - -Should the target be processed with auto-rcc (for Qt projects). - -:prop_tgt:`AUTORCC` is a boolean specifying whether CMake will handle -the Qt ``rcc`` code generator automatically, i.e. without having to use -the :module:`QT4_ADD_RESOURCES() <FindQt4>` or ``QT5_ADD_RESOURCES()`` -macro. Currently Qt4 and Qt5 are supported. - -When this property is ``ON``, CMake will handle ``.qrc`` files added -as target sources at build time and invoke ``rcc`` accordingly. -This property is initialized by the value of the :variable:`CMAKE_AUTORCC` -variable if it is set when a target is created. - -By default :prop_tgt:`AUTORCC` is processed by a -:command:`custom command <add_custom_command>`. -If the ``.qrc`` file is :prop_sf:`GENERATED`, a -:command:`custom target <add_custom_target>` is used instead. - -When there are multiple ``.qrc`` files with the same name, CMake will -generate unspecified unique output file names for ``rcc``. Therefore, if -``Q_INIT_RESOURCE()`` or ``Q_CLEANUP_RESOURCE()`` need to be used, the -``.qrc`` file name must be unique. - - -Modifiers -^^^^^^^^^ - -:prop_tgt:`AUTORCC_EXECUTABLE`: -The ``rcc`` executable will be detected automatically, but can be forced to -a certain binary by setting this target property. - -:prop_tgt:`AUTORCC_OPTIONS`: -Additional command line options for ``rcc`` can be set via this target -property. The corresponding :prop_sf:`AUTORCC_OPTIONS` source file property -can be used to specify options to be applied only to a specific ``.qrc`` file. - -:prop_sf:`SKIP_AUTORCC`: -``.qrc`` files can be excluded from :prop_tgt:`AUTORCC` processing by -setting this source file property. - -:prop_sf:`SKIP_AUTOGEN`: -Source files can be excluded from :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` processing by -setting this source file property. - -:prop_gbl:`AUTOGEN_SOURCE_GROUP`: -This global property can be used to group files generated by -:prop_tgt:`AUTOMOC` or :prop_tgt:`AUTORCC` together in an IDE, e.g. in MSVS. - -:prop_gbl:`AUTOGEN_TARGETS_FOLDER`: -This global property can be used to group :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` targets together in an IDE, -e.g. in MSVS. - -:variable:`CMAKE_GLOBAL_AUTORCC_TARGET`: -A global ``autorcc`` target that depends on all :prop_tgt:`AUTORCC` targets -in the project will be generated when this variable is ``ON``. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTORCC_EXECUTABLE.rst b/share/cmake-3.18/Help/prop_tgt/AUTORCC_EXECUTABLE.rst deleted file mode 100644 index ca0fbd7..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTORCC_EXECUTABLE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -AUTORCC_EXECUTABLE ------------------- - -:prop_tgt:`AUTORCC_EXECUTABLE` is file path pointing to the ``rcc`` -executable to use for :prop_tgt:`AUTORCC` enabled files. Setting -this property will make CMake skip the automatic detection of the -``rcc`` binary as well as the sanity-tests normally run to ensure -that the binary is available and working as expected. - -Usually this property does not need to be set. Only consider this -property if auto-detection of ``rcc`` can not work -- e.g. because -you are building the ``rcc`` binary as part of your project. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOUIC.rst b/share/cmake-3.18/Help/prop_tgt/AUTOUIC.rst deleted file mode 100644 index cd24f5e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOUIC.rst +++ /dev/null
@@ -1,85 +0,0 @@ -AUTOUIC -------- - -Should the target be processed with auto-uic (for Qt projects). - -:prop_tgt:`AUTOUIC` is a boolean specifying whether CMake will handle -the Qt ``uic`` code generator automatically, i.e. without having to use -the :module:`QT4_WRAP_UI() <FindQt4>` or ``QT5_WRAP_UI()`` macro. Currently -Qt4 and Qt5 are supported. - -This property is initialized by the value of the :variable:`CMAKE_AUTOUIC` -variable if it is set when a target is created. - -When this property is ``ON``, CMake will scan the header and source files at -build time and invoke ``uic`` accordingly. - - -Header and source file processing -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -At build time, CMake scans each header and source file from the -target's sources for include statements of the form - -.. code-block:: c++ - - #include "ui_<ui_base>.h" - -Once such an include statement is found in a file, CMake searches for the -``uic`` input file ``<ui_base>.ui`` - -- in the vicinity of the file and -- in the :prop_tgt:`AUTOUIC_SEARCH_PATHS` of the target. - -If the ``<ui_base>.ui`` file was found, ``uic`` is called on it to generate -``ui_<ui_base>.h`` in the directory - -- ``<AUTOGEN_BUILD_DIR>/include`` for single configuration generators or in -- ``<AUTOGEN_BUILD_DIR>/include_<CONFIG>`` for - :prop_gbl:`multi configuration <GENERATOR_IS_MULTI_CONFIG>` generators. - -Where ``<AUTOGEN_BUILD_DIR>`` is the value of the target property -:prop_tgt:`AUTOGEN_BUILD_DIR`. - -The include directory is automatically added to the target's -:prop_tgt:`INCLUDE_DIRECTORIES`. - - -Modifiers -^^^^^^^^^ - -:prop_tgt:`AUTOUIC_EXECUTABLE`: -The ``uic`` executable will be detected automatically, but can be forced to -a certain binary using this target property. - -:prop_tgt:`AUTOUIC_OPTIONS`: -Additional command line options for ``uic`` can be set via this target -property. The corresponding :prop_sf:`AUTOUIC_OPTIONS` source file property -can be used to specify options to be applied only to a specific -``<base_name>.ui`` file. - -:prop_sf:`SKIP_AUTOUIC`: -Source files can be excluded from :prop_tgt:`AUTOUIC` processing by setting -this source file property. - -:prop_sf:`SKIP_AUTOGEN`: -Source files can be excluded from :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` processing by -setting this source file property. - -:prop_gbl:`AUTOGEN_TARGETS_FOLDER`: -This global property can be used to group :prop_tgt:`AUTOMOC`, -:prop_tgt:`AUTOUIC` and :prop_tgt:`AUTORCC` targets together in an IDE, -e.g. in MSVS. - -:variable:`CMAKE_GLOBAL_AUTOGEN_TARGET`: -A global ``autogen`` target, that depends on all :prop_tgt:`AUTOMOC` or -:prop_tgt:`AUTOUIC` generated ``<ORIGIN>_autogen`` targets in the project, -will be generated when this variable is ``ON``. - -:prop_tgt:`AUTOGEN_PARALLEL`: -This target property controls the number of ``moc`` or ``uic`` processes to -start in parallel during builds. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOUIC_EXECUTABLE.rst b/share/cmake-3.18/Help/prop_tgt/AUTOUIC_EXECUTABLE.rst deleted file mode 100644 index 03bd554..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOUIC_EXECUTABLE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -AUTOUIC_EXECUTABLE ------------------- - -:prop_tgt:`AUTOUIC_EXECUTABLE` is file path pointing to the ``uic`` -executable to use for :prop_tgt:`AUTOUIC` enabled files. Setting -this property will make CMake skip the automatic detection of the -``uic`` binary as well as the sanity-tests normally run to ensure -that the binary is available and working as expected. - -Usually this property does not need to be set. Only consider this -property if auto-detection of ``uic`` can not work -- e.g. because -you are building the ``uic`` binary as part of your project. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/AUTOUIC_SEARCH_PATHS.rst b/share/cmake-3.18/Help/prop_tgt/AUTOUIC_SEARCH_PATHS.rst deleted file mode 100644 index 96d9f89..0000000 --- a/share/cmake-3.18/Help/prop_tgt/AUTOUIC_SEARCH_PATHS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -AUTOUIC_SEARCH_PATHS --------------------- - -Search path list used by :prop_tgt:`AUTOUIC` to find included -``.ui`` files. - -This property is initialized by the value of the -:variable:`CMAKE_AUTOUIC_SEARCH_PATHS` variable if it is set -when a target is created. Otherwise it is empty. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/prop_tgt/BINARY_DIR.rst b/share/cmake-3.18/Help/prop_tgt/BINARY_DIR.rst deleted file mode 100644 index 246f7e6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/BINARY_DIR.rst +++ /dev/null
@@ -1,6 +0,0 @@ -BINARY_DIR ----------- - -This read-only property reports the value of the -:variable:`CMAKE_CURRENT_BINARY_DIR` variable in the directory in which -the target was defined.
diff --git a/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH.rst b/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH.rst deleted file mode 100644 index d978b94..0000000 --- a/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH.rst +++ /dev/null
@@ -1,13 +0,0 @@ -BUILD_RPATH ------------ - -A :ref:`semicolon-separated list <CMake Language Lists>` specifying runtime path (``RPATH``) -entries to add to binaries linked in the build tree (for platforms that -support it). The entries will *not* be used for binaries in the install -tree. See also the :prop_tgt:`INSTALL_RPATH` target property. - -This property is initialized by the value of the variable -:variable:`CMAKE_BUILD_RPATH` if it is set when a target is created. - -This property supports -:manual:`generator expressions <cmake-generator-expressions(7)>`.
diff --git a/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH_USE_ORIGIN.rst b/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH_USE_ORIGIN.rst deleted file mode 100644 index 3378797..0000000 --- a/share/cmake-3.18/Help/prop_tgt/BUILD_RPATH_USE_ORIGIN.rst +++ /dev/null
@@ -1,24 +0,0 @@ -BUILD_RPATH_USE_ORIGIN ----------------------- - -Whether to use relative paths for the build ``RPATH``. - -This property is initialized by the value of the variable -:variable:`CMAKE_BUILD_RPATH_USE_ORIGIN`. - -On platforms that support runtime paths (``RPATH``) with the -``$ORIGIN`` token, setting this property to ``TRUE`` enables relative -paths in the build ``RPATH`` for executables and shared libraries that -point to shared libraries in the same build tree. - -Normally the build ``RPATH`` of a binary contains absolute paths -to the directory of each shared library it links to. The ``RPATH`` -entries for directories contained within the build tree can be made -relative to enable relocatable builds and to help achieve reproducible -builds by omitting the build directory from the build environment. - -This property has no effect on platforms that do not support the -``$ORIGIN`` token in ``RPATH``, or when the :variable:`CMAKE_SKIP_RPATH` -variable is set. The runtime path set through the -:prop_tgt:`BUILD_RPATH` target property is also unaffected by this -property.
diff --git a/share/cmake-3.18/Help/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.rst b/share/cmake-3.18/Help/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.rst deleted file mode 100644 index bbb9a24..0000000 --- a/share/cmake-3.18/Help/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.rst +++ /dev/null
@@ -1,13 +0,0 @@ -BUILD_WITH_INSTALL_NAME_DIR ---------------------------- - -``BUILD_WITH_INSTALL_NAME_DIR`` is a boolean specifying whether the macOS -``install_name`` of a target in the build tree uses the directory given by -:prop_tgt:`INSTALL_NAME_DIR`. This setting only applies to targets on macOS. - -This property is initialized by the value of the variable -:variable:`CMAKE_BUILD_WITH_INSTALL_NAME_DIR` if it is set when a target is -created. - -If this property is not set and policy :policy:`CMP0068` is not ``NEW``, the -value of :prop_tgt:`BUILD_WITH_INSTALL_RPATH` is used in its place.
diff --git a/share/cmake-3.18/Help/prop_tgt/COMMON_LANGUAGE_RUNTIME.rst b/share/cmake-3.18/Help/prop_tgt/COMMON_LANGUAGE_RUNTIME.rst deleted file mode 100644 index 052ac6d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMMON_LANGUAGE_RUNTIME.rst +++ /dev/null
@@ -1,22 +0,0 @@ -COMMON_LANGUAGE_RUNTIME ------------------------ - -By setting this target property, the target is configured to build with -``C++/CLI`` support. - -The Visual Studio generator defines the ``clr`` parameter depending on -the value of ``COMMON_LANGUAGE_RUNTIME``: - -* property not set: native C++ (i.e. default) -* property set but empty: mixed unmanaged/managed C++ -* property set to any non empty value: managed C++ - -Supported values: ``""``, ``"pure"``, ``"safe"`` - -This property is only evaluated :ref:`Visual Studio Generators` for -VS 2010 and above. - -To be able to build managed C++ targets with VS 2017 and above the component -``C++/CLI support`` must be installed, which may not be done by default. - -See also :prop_tgt:`IMPORTED_COMMON_LANGUAGE_RUNTIME`
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_FEATURES.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_FEATURES.rst deleted file mode 100644 index 46aec4f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_FEATURES.rst +++ /dev/null
@@ -1,13 +0,0 @@ -COMPILE_FEATURES ----------------- - -Compiler features enabled for this target. - -The list of features in this property are a subset of the features listed -in the :variable:`CMAKE_C_COMPILE_FEATURES`, :variable:`CMAKE_CUDA_COMPILE_FEATURES`, and -:variable:`CMAKE_CXX_COMPILE_FEATURES` variables. - -Contents of ``COMPILE_FEATURES`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual for -available expressions. See the :manual:`cmake-compile-features(7)` manual -for information on compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_OPTIONS.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_OPTIONS.rst deleted file mode 100644 index 0cd6836..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_OPTIONS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -COMPILE_OPTIONS ---------------- - -List of options to pass to the compiler. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of options -specified so far for its target. Use the :command:`target_compile_options` -command to append more options. - -This property is initialized by the :prop_dir:`COMPILE_OPTIONS` directory -property when a target is created, and is used by the generators to set -the options for the compiler. - -Contents of ``COMPILE_OPTIONS`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME.rst deleted file mode 100644 index 24a9f62..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME.rst +++ /dev/null
@@ -1,11 +0,0 @@ -COMPILE_PDB_NAME ----------------- - -Output name for the MS debug symbol ``.pdb`` file generated by the -compiler while building source files. - -This property specifies the base name for the debug symbols file. -If not set, the default is unspecified. - -.. |PDB_XXX| replace:: :prop_tgt:`PDB_NAME` -.. include:: COMPILE_PDB_NOTE.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME_CONFIG.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME_CONFIG.rst deleted file mode 100644 index e4077f5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_NAME_CONFIG.rst +++ /dev/null
@@ -1,10 +0,0 @@ -COMPILE_PDB_NAME_<CONFIG> -------------------------- - -Per-configuration output name for the MS debug symbol ``.pdb`` file -generated by the compiler while building source files. - -This is the configuration-specific version of :prop_tgt:`COMPILE_PDB_NAME`. - -.. |PDB_XXX| replace:: :prop_tgt:`PDB_NAME_<CONFIG>` -.. include:: COMPILE_PDB_NOTE.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.rst deleted file mode 100644 index 34f49be..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.rst +++ /dev/null
@@ -1,13 +0,0 @@ -COMPILE_PDB_OUTPUT_DIRECTORY ----------------------------- - -Output directory for the MS debug symbol ``.pdb`` file -generated by the compiler while building source files. - -This property specifies the directory into which the MS debug symbols -will be placed by the compiler. This property is initialized by the -value of the :variable:`CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY` variable -if it is set when a target is created. - -.. |PDB_XXX| replace:: :prop_tgt:`PDB_OUTPUT_DIRECTORY` -.. include:: COMPILE_PDB_NOTE.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst b/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst deleted file mode 100644 index f261756..0000000 --- a/share/cmake-3.18/Help/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst +++ /dev/null
@@ -1,16 +0,0 @@ -COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> -------------------------------------- - -Per-configuration output directory for the MS debug symbol ``.pdb`` file -generated by the compiler while building source files. - -This is a per-configuration version of -:prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY`, -but multi-configuration generators (Visual Studio, Xcode) do NOT append a -per-configuration subdirectory to the specified directory. This -property is initialized by the value of the -:variable:`CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>` variable -if it is set when a target is created. - -.. |PDB_XXX| replace:: :prop_tgt:`PDB_OUTPUT_DIRECTORY_<CONFIG>` -.. include:: COMPILE_PDB_NOTE.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/CROSSCOMPILING_EMULATOR.rst b/share/cmake-3.18/Help/prop_tgt/CROSSCOMPILING_EMULATOR.rst deleted file mode 100644 index 87c5978..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CROSSCOMPILING_EMULATOR.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CROSSCOMPILING_EMULATOR ------------------------ - -Use the given emulator to run executables created when crosscompiling. -This command will be added as a prefix to :command:`add_test`, -:command:`add_custom_command`, and :command:`add_custom_target` commands -for built target system executables. - -If this property contains a :ref:`semicolon-separated list <CMake Language -Lists>`, then the first value is the command and remaining values are its -arguments. - -This property is initialized by the value of the -:variable:`CMAKE_CROSSCOMPILING_EMULATOR` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_ARCHITECTURES.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_ARCHITECTURES.rst deleted file mode 100644 index bae3c6f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_ARCHITECTURES.rst +++ /dev/null
@@ -1,40 +0,0 @@ -CUDA_ARCHITECTURES ------------------- - -List of architectures to generate device code for. - -An architecture can be suffixed by either ``-real`` or ``-virtual`` to specify -the kind of architecture to generate code for. -If no suffix is given then code is generated for both real and virtual -architectures. - -A non-empty false value (e.g. ``OFF``) disables adding architectures. -This is intended to support packagers and rare cases where full control -over the passed flags is required. - -This property is initialized by the value of the :variable:`CMAKE_CUDA_ARCHITECTURES` -variable if it is set when a target is created. - -The ``CUDA_ARCHITECTURES`` target property must be set to a non-empty value on targets -that compile CUDA sources, or it is an error. See policy :policy:`CMP0104`. - -Examples -^^^^^^^^ - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 35 50 72) - -Generates code for real and virtual architectures ``30``, ``50`` and ``72``. - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 70-real 72-virtual) - -Generates code for real architecture ``70`` and virtual architecture ``72``. - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES OFF) - -CMake will not pass any architecture flags to the compiler.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_EXTENSIONS.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_EXTENSIONS.rst deleted file mode 100644 index 098ca3c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_EXTENSIONS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CUDA_EXTENSIONS ---------------- - -Boolean specifying whether compiler specific extensions are requested. - -This property specifies whether compiler specific extensions should be -used. For some compilers, this results in adding a flag such -as ``-std=gnu++11`` instead of ``-std=c++11`` to the compile line. This -property is ``ON`` by default. The basic CUDA/C++ standard level is -controlled by the :prop_tgt:`CUDA_STANDARD` target property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CUDA_EXTENSIONS` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_PTX_COMPILATION.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_PTX_COMPILATION.rst deleted file mode 100644 index 0ee372b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_PTX_COMPILATION.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CUDA_PTX_COMPILATION --------------------- - -Compile CUDA sources to ``.ptx`` files instead of ``.obj`` files -within :ref:`Object Libraries`. - -For example: - -.. code-block:: cmake - - add_library(myptx OBJECT a.cu b.cu) - set_property(TARGET myptx PROPERTY CUDA_PTX_COMPILATION ON)
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.rst deleted file mode 100644 index dae960f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CUDA_RESOLVE_DEVICE_SYMBOLS ---------------------------- - -CUDA only: Enables device linking for the specific library target where -required. - -If set, this will tell the required compilers to enable device linking -on the library target. Device linking is an additional link step -required by some CUDA compilers when :prop_tgt:`CUDA_SEPARABLE_COMPILATION` is -enabled. Normally device linking is deferred until a shared library or -executable is generated, allowing for multiple static libraries to resolve -device symbols at the same time when they are used by a shared library or -executable. - -By default static library targets have this property is disabled, -while shared, module, and executable targets have this property enabled. - -Note that device linking is not supported for :ref:`Object Libraries`. - - -For instance: - -.. code-block:: cmake - - set_property(TARGET mystaticlib PROPERTY CUDA_RESOLVE_DEVICE_SYMBOLS ON)
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_RUNTIME_LIBRARY.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_RUNTIME_LIBRARY.rst deleted file mode 100644 index 11b344c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_RUNTIME_LIBRARY.rst +++ /dev/null
@@ -1,21 +0,0 @@ -CUDA_RUNTIME_LIBRARY --------------------- - -Select the CUDA runtime library for use by compilers targeting the CUDA language. - -The allowed case insensitive values are: - -.. include:: CUDA_RUNTIME_LIBRARY-VALUES.txt - -Contents of ``CUDA_RUNTIME_LIBRARY`` may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. - -If that property is not set then CMake uses an appropriate default -value based on the compiler to select the CUDA runtime library. - -.. note:: - - This property has effect only when the ``CUDA`` language is enabled. To - control the CUDA runtime linking when only using the CUDA SDK with the - ``C`` or ``C++`` language we recommend using the :module:`FindCUDAToolkit` - module.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_SEPARABLE_COMPILATION.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_SEPARABLE_COMPILATION.rst deleted file mode 100644 index d306d7f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_SEPARABLE_COMPILATION.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CUDA_SEPARABLE_COMPILATION --------------------------- - -CUDA only: Enables separate compilation of device code - -If set this will enable separable compilation for all CUDA files for -the given target. - -For instance: - -.. code-block:: cmake - - set_property(TARGET myexe PROPERTY CUDA_SEPARABLE_COMPILATION ON) - -This property is initialized by the value of the -:variable:`CMAKE_CUDA_SEPARABLE_COMPILATION` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD.rst deleted file mode 100644 index 6d6774e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD.rst +++ /dev/null
@@ -1,32 +0,0 @@ -CUDA_STANDARD -------------- - -The CUDA/C++ standard whose features are requested to build this target. - -This property specifies the CUDA/C++ standard whose features are requested -to build this target. For some compilers, this results in adding a -flag such as ``-std=gnu++11`` to the compile line. - -Supported values are ``98``, ``03``, ``11``, ``14``, ``17``, ``20``. - -If the value requested does not result in a compile flag being added for -the compiler in use, a previous standard flag will be added instead. This -means that using: - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CUDA_STANDARD 11) - -with a compiler which does not support ``-std=gnu++11`` or an equivalent -flag will not result in an error or warning, but will instead add the -``-std=gnu++98`` flag if supported. This "decay" behavior may be controlled -with the :prop_tgt:`CUDA_STANDARD_REQUIRED` target property. -Additionally, the :prop_tgt:`CUDA_EXTENSIONS` target property may be used to -control whether compiler-specific extensions are enabled on a per-target basis. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CUDA_STANDARD` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD_REQUIRED.rst deleted file mode 100644 index b2d5b28..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CUDA_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,18 +0,0 @@ -CUDA_STANDARD_REQUIRED ----------------------- - -Boolean describing whether the value of :prop_tgt:`CUDA_STANDARD` is a requirement. - -If this property is set to ``ON``, then the value of the -:prop_tgt:`CUDA_STANDARD` target property is treated as a requirement. If this -property is ``OFF`` or unset, the :prop_tgt:`CUDA_STANDARD` target property is -treated as optional and may "decay" to a previous standard if the requested is -not available. For compilers that have no notion of a standard level, such as -MSVC, this has no effect. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CUDA_STANDARD_REQUIRED` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CXX_EXTENSIONS.rst b/share/cmake-3.18/Help/prop_tgt/CXX_EXTENSIONS.rst deleted file mode 100644 index 280bb3a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CXX_EXTENSIONS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CXX_EXTENSIONS --------------- - -Boolean specifying whether compiler specific extensions are requested. - -This property specifies whether compiler specific extensions should be -used. For some compilers, this results in adding a flag such -as ``-std=gnu++11`` instead of ``-std=c++11`` to the compile line. This -property is ``ON`` by default. The basic C++ standard level is -controlled by the :prop_tgt:`CXX_STANDARD` target property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CXX_EXTENSIONS` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD.rst b/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD.rst deleted file mode 100644 index ccc0147..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD.rst +++ /dev/null
@@ -1,34 +0,0 @@ -CXX_STANDARD ------------- - -The C++ standard whose features are requested to build this target. - -This property specifies the C++ standard whose features are requested -to build this target. For some compilers, this results in adding a -flag such as ``-std=gnu++11`` to the compile line. For compilers that -have no notion of a standard level, such as Microsoft Visual C++ before -2015 Update 3, this has no effect. - -Supported values are ``98``, ``11``, ``14``, ``17``, and ``20``. - -If the value requested does not result in a compile flag being added for -the compiler in use, a previous standard flag will be added instead. This -means that using: - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY CXX_STANDARD 11) - -with a compiler which does not support ``-std=gnu++11`` or an equivalent -flag will not result in an error or warning, but will instead add the -``-std=gnu++98`` flag if supported. This "decay" behavior may be controlled -with the :prop_tgt:`CXX_STANDARD_REQUIRED` target property. -Additionally, the :prop_tgt:`CXX_EXTENSIONS` target property may be used to -control whether compiler-specific extensions are enabled on a per-target basis. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CXX_STANDARD` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD_REQUIRED.rst deleted file mode 100644 index 697d7f6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/CXX_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,18 +0,0 @@ -CXX_STANDARD_REQUIRED ---------------------- - -Boolean describing whether the value of :prop_tgt:`CXX_STANDARD` is a requirement. - -If this property is set to ``ON``, then the value of the -:prop_tgt:`CXX_STANDARD` target property is treated as a requirement. If this -property is ``OFF`` or unset, the :prop_tgt:`CXX_STANDARD` target property is -treated as optional and may "decay" to a previous standard if the requested is -not available. For compilers that have no notion of a standard level, such as -MSVC, this has no effect. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_CXX_STANDARD_REQUIRED` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/C_EXTENSIONS.rst b/share/cmake-3.18/Help/prop_tgt/C_EXTENSIONS.rst deleted file mode 100644 index 05b14ce..0000000 --- a/share/cmake-3.18/Help/prop_tgt/C_EXTENSIONS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -C_EXTENSIONS ------------- - -Boolean specifying whether compiler specific extensions are requested. - -This property specifies whether compiler specific extensions should be -used. For some compilers, this results in adding a flag such -as ``-std=gnu11`` instead of ``-std=c11`` to the compile line. This -property is ``ON`` by default. The basic C standard level is -controlled by the :prop_tgt:`C_STANDARD` target property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_C_EXTENSIONS` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/C_STANDARD.rst b/share/cmake-3.18/Help/prop_tgt/C_STANDARD.rst deleted file mode 100644 index 6a05139..0000000 --- a/share/cmake-3.18/Help/prop_tgt/C_STANDARD.rst +++ /dev/null
@@ -1,34 +0,0 @@ -C_STANDARD ----------- - -The C standard whose features are requested to build this target. - -This property specifies the C standard whose features are requested -to build this target. For some compilers, this results in adding a -flag such as ``-std=gnu11`` to the compile line. For compilers that -have no notion of a C standard level, such as all versions of -MSVC known as of this version of CMake, this has no effect. - -Supported values are ``90``, ``99`` and ``11``. - -If the value requested does not result in a compile flag being added for -the compiler in use, a previous standard flag will be added instead. This -means that using: - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY C_STANDARD 11) - -with a compiler which does not support ``-std=gnu11`` or an equivalent -flag will not result in an error or warning, but will instead add the -``-std=gnu99`` or ``-std=gnu90`` flag if supported. This "decay" behavior may -be controlled with the :prop_tgt:`C_STANDARD_REQUIRED` target property. -Additionally, the :prop_tgt:`C_EXTENSIONS` target property may be used to -control whether compiler-specific extensions are enabled on a per-target basis. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_C_STANDARD` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/C_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/prop_tgt/C_STANDARD_REQUIRED.rst deleted file mode 100644 index acfad98..0000000 --- a/share/cmake-3.18/Help/prop_tgt/C_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,18 +0,0 @@ -C_STANDARD_REQUIRED -------------------- - -Boolean describing whether the value of :prop_tgt:`C_STANDARD` is a requirement. - -If this property is set to ``ON``, then the value of the -:prop_tgt:`C_STANDARD` target property is treated as a requirement. If this -property is ``OFF`` or unset, the :prop_tgt:`C_STANDARD` target property is -treated as optional and may "decay" to a previous standard if the requested is -not available. For compilers that have no notion of a standard level, such as -MSVC, this has no effect. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_C_STANDARD_REQUIRED` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/DEBUG_POSTFIX.rst b/share/cmake-3.18/Help/prop_tgt/DEBUG_POSTFIX.rst deleted file mode 100644 index 04e312e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DEBUG_POSTFIX.rst +++ /dev/null
@@ -1,7 +0,0 @@ -DEBUG_POSTFIX -------------- - -See target property ``<CONFIG>_POSTFIX``. - -This property is a special case of the more-general ``<CONFIG>_POSTFIX`` -property for the ``DEBUG`` configuration.
diff --git a/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.rst b/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.rst deleted file mode 100644 index 5e9c191..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.rst +++ /dev/null
@@ -1,18 +0,0 @@ -DEPLOYMENT_ADDITIONAL_FILES ---------------------------- - -Set the WinCE project ``AdditionalFiles`` in ``DeploymentTool`` in ``.vcproj`` -files generated by the :generator:`Visual Studio 9 2008` generator. -This is useful when you want to debug on remote WinCE device. -Specify additional files that will be copied to the device. -For example: - -.. code-block:: cmake - - set_property(TARGET ${TARGET} PROPERTY - DEPLOYMENT_ADDITIONAL_FILES "english.lng|local_folder|remote_folder|0" - "german.lng|local_folder|remote_folder|0") - -produces:: - - <DeploymentTool AdditionalFiles="english.lng|local_folder|remote_folder|0;german.lng|local_folder|remote_folder|0" ... />
diff --git a/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.rst deleted file mode 100644 index 368768a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.rst +++ /dev/null
@@ -1,18 +0,0 @@ -DEPLOYMENT_REMOTE_DIRECTORY ---------------------------- - -Set the WinCE project ``RemoteDirectory`` in ``DeploymentTool`` and -``RemoteExecutable`` in ``DebuggerTool`` in ``.vcproj`` files generated -by the :generator:`Visual Studio 9 2008` generator. -This is useful when you want to debug on remote WinCE device. -For example: - -.. code-block:: cmake - - set_property(TARGET ${TARGET} PROPERTY - DEPLOYMENT_REMOTE_DIRECTORY "\\FlashStorage") - -produces:: - - <DeploymentTool RemoteDirectory="\FlashStorage" ... /> - <DebuggerTool RemoteExecutable="\FlashStorage\target_file" ... />
diff --git a/share/cmake-3.18/Help/prop_tgt/DEPRECATION.rst b/share/cmake-3.18/Help/prop_tgt/DEPRECATION.rst deleted file mode 100644 index fef2e2e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DEPRECATION.rst +++ /dev/null
@@ -1,7 +0,0 @@ -DEPRECATION ------------ - -Deprecation message from imported target's developer. - -``DEPRECATION`` is the message regarding a deprecation status to be displayed -to downstream users of a target.
diff --git a/share/cmake-3.18/Help/prop_tgt/DISABLE_PRECOMPILE_HEADERS.rst b/share/cmake-3.18/Help/prop_tgt/DISABLE_PRECOMPILE_HEADERS.rst deleted file mode 100644 index 4cef023..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DISABLE_PRECOMPILE_HEADERS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -DISABLE_PRECOMPILE_HEADERS --------------------------- - -Disables the precompilation of header files specified by -:prop_tgt:`PRECOMPILE_HEADERS` property. - -If the property is not set, CMake will use the value provided -by :variable:`CMAKE_DISABLE_PRECOMPILE_HEADERS`.
diff --git a/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK.rst b/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK.rst deleted file mode 100644 index 8698eb6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK.rst +++ /dev/null
@@ -1,13 +0,0 @@ -DOTNET_TARGET_FRAMEWORK ------------------------ - -Specify the .NET target framework. - -Used to specify the .NET target framework for C++/CLI and C#. For -example: ``netcoreapp2.1``. - -This property is only evaluated for :ref:`Visual Studio Generators` -VS 2010 and above. - -Can be initialized for all targets using the variable -:variable:`CMAKE_DOTNET_TARGET_FRAMEWORK`.
diff --git a/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.rst deleted file mode 100644 index b33f4fb..0000000 --- a/share/cmake-3.18/Help/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.rst +++ /dev/null
@@ -1,15 +0,0 @@ -DOTNET_TARGET_FRAMEWORK_VERSION -------------------------------- - -Specify the .NET target framework version. - -Used to specify the .NET target framework version for C++/CLI and C#. -For example: ``v4.5``. - -This property is only evaluated for :ref:`Visual Studio Generators` -VS 2010 and above. - -To initialize this variable for all targets set -:variable:`CMAKE_DOTNET_TARGET_FRAMEWORK` or -:variable:`CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION`. If both are set, -the latter is ignored.
diff --git a/share/cmake-3.18/Help/prop_tgt/EXCLUDE_FROM_ALL.rst b/share/cmake-3.18/Help/prop_tgt/EXCLUDE_FROM_ALL.rst deleted file mode 100644 index c9ece22..0000000 --- a/share/cmake-3.18/Help/prop_tgt/EXCLUDE_FROM_ALL.rst +++ /dev/null
@@ -1,21 +0,0 @@ -EXCLUDE_FROM_ALL ----------------- - -Set this target property to a true (or false) value to exclude (or include) -the target from the "all" target of the containing directory and its -ancestors. If excluded, running e.g. ``make`` in the containing directory -or its ancestors will not build the target by default. - -If this target property is not set then the target will be included in -the "all" target of the containing directory. Furthermore, it will be -included in the "all" target of its ancestor directories unless the -:prop_dir:`EXCLUDE_FROM_ALL` directory property is set. - -With ``EXCLUDE_FROM_ALL`` set to false or not set at all, the target -will be brought up to date as part of doing a ``make install`` or its -equivalent for the CMake generator being used. - -If a target has ``EXCLUDE_FROM_ALL`` set to true, it may still be listed -in an :command:`install(TARGETS)` command, but the user is responsible for -ensuring that the target's build artifacts are not missing or outdated when -an install is performed.
diff --git a/share/cmake-3.18/Help/prop_tgt/EXPORT_PROPERTIES.rst b/share/cmake-3.18/Help/prop_tgt/EXPORT_PROPERTIES.rst deleted file mode 100644 index bcf47a6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/EXPORT_PROPERTIES.rst +++ /dev/null
@@ -1,14 +0,0 @@ -EXPORT_PROPERTIES ------------------ - -List additional properties to export for a target. - -This property contains a list of property names that should be exported by -the :command:`install(EXPORT)` and :command:`export` commands. By default -only a limited number of properties are exported. This property can be used -to additionally export other properties as well. - -Properties starting with ``INTERFACE_`` or ``IMPORTED_`` are not allowed as -they are reserved for internal CMake use. - -Properties containing generator expressions are also not allowed.
diff --git a/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst b/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst deleted file mode 100644 index 243c0cd..0000000 --- a/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst +++ /dev/null
@@ -1,26 +0,0 @@ -FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> ---------------------------------------- - -Postfix to append to the framework file name for configuration ``<CONFIG>``, -when using a multi-config generator (like Xcode and Ninja Multi-Config). - -When building with configuration ``<CONFIG>`` the value of this property -is appended to the framework file name built on disk. - -For example, given a framework called ``my_fw``, a value of ``_debug`` -for the ``FRAMEWORK_MULTI_CONFIG_POSTFIX_DEBUG`` property, and -``Debug;Release`` in :variable:`CMAKE_CONFIGURATION_TYPES`, the following -relevant files would be created for the ``Debug`` and ``Release`` -configurations: - -- ``Release/my_fw.framework/my_fw`` -- ``Release/my_fw.framework/Versions/A/my_fw`` -- ``Debug/my_fw.framework/my_fw_debug`` -- ``Debug/my_fw.framework/Versions/A/my_fw_debug`` - -For framework targets, this property is initialized by the value of the -:variable:`CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>` variable if it -is set when a target is created. - -This property is ignored for non-framework targets, and when using single -config generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_VERSION.rst deleted file mode 100644 index c2ae7b9..0000000 --- a/share/cmake-3.18/Help/prop_tgt/FRAMEWORK_VERSION.rst +++ /dev/null
@@ -1,8 +0,0 @@ -FRAMEWORK_VERSION ------------------ - -Version of a framework created using the :prop_tgt:`FRAMEWORK` target -property (e.g. ``A``). - -This property only affects macOS, as iOS doesn't have versioned -directory structure.
diff --git a/share/cmake-3.18/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst deleted file mode 100644 index e061863..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst +++ /dev/null
@@ -1,17 +0,0 @@ -Fortran_MODULE_DIRECTORY ------------------------- - -Specify output directory for Fortran modules provided by the target. - -If the target contains Fortran source files that provide modules and -the compiler supports a module output directory this specifies the -directory in which the modules will be placed. When this property is -not set the modules will be placed in the build directory -corresponding to the target's source directory. If the variable -:variable:`CMAKE_Fortran_MODULE_DIRECTORY` is set when a target is created its -value is used to initialize this property. - -Note that some compilers will automatically search the module output -directory for modules USEd during compilation but others will not. If -your sources USE modules their location must be specified by -:prop_tgt:`INCLUDE_DIRECTORIES` regardless of this property.
diff --git a/share/cmake-3.18/Help/prop_tgt/Fortran_PREPROCESS.rst b/share/cmake-3.18/Help/prop_tgt/Fortran_PREPROCESS.rst deleted file mode 100644 index 47a15c0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Fortran_PREPROCESS.rst +++ /dev/null
@@ -1,23 +0,0 @@ -Fortran_PREPROCESS ------------------- - -Control whether the Fortran source file should be unconditionally -preprocessed. - -If unset or empty, rely on the compiler to determine whether the file -should be preprocessed. If explicitly set to ``OFF`` then the file does not -need to be preprocessed. If explicitly set to ``ON``, then the file does -need to be preprocessed as part of the compilation step. - -When using the :generator:`Ninja` generator, all source files are -first preprocessed in order to generate module dependency -information. Setting this property to ``OFF`` will make ``Ninja`` -skip this step. - -Use the source-specific :prop_sf:`Fortran_PREPROCESS` property if a single -file needs to be preprocessed. If the variable -:variable:`CMAKE_Fortran_PREPROCESS` is set when a target is created its -value is used to initialize this property. - -.. note:: For some compilers, ``NAG``, ``PGI`` and ``Solaris Studio``, - setting this to ``OFF`` will have no effect.
diff --git a/share/cmake-3.18/Help/prop_tgt/GHS_INTEGRITY_APP.rst b/share/cmake-3.18/Help/prop_tgt/GHS_INTEGRITY_APP.rst deleted file mode 100644 index b669781..0000000 --- a/share/cmake-3.18/Help/prop_tgt/GHS_INTEGRITY_APP.rst +++ /dev/null
@@ -1,10 +0,0 @@ -GHS_INTEGRITY_APP ------------------ - -``ON`` / ``OFF`` boolean to determine if an executable target should -be treated as an `Integrity Application`. - -If no value is set and if a ``.int`` file is added as a source file to the -executable target it will be treated as an `Integrity Application`. - -Supported on :generator:`Green Hills MULTI`.
diff --git a/share/cmake-3.18/Help/prop_tgt/GHS_NO_SOURCE_GROUP_FILE.rst b/share/cmake-3.18/Help/prop_tgt/GHS_NO_SOURCE_GROUP_FILE.rst deleted file mode 100644 index 11ce0b2..0000000 --- a/share/cmake-3.18/Help/prop_tgt/GHS_NO_SOURCE_GROUP_FILE.rst +++ /dev/null
@@ -1,13 +0,0 @@ -GHS_NO_SOURCE_GROUP_FILE ------------------------- - -``ON`` / ``OFF`` boolean to control if the project file for a target should -be one single file or multiple files. - -The default behavior or when the property is ``OFF`` is to generate a project -file for the target and then a sub-project file for each source group. - -When this property is ``ON`` or if :variable:`CMAKE_GHS_NO_SOURCE_GROUP_FILE` -is ``ON`` then only a single project file is generated for the target. - -Supported on :generator:`Green Hills MULTI`.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.rst b/share/cmake-3.18/Help/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.rst deleted file mode 100644 index dc73807..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.rst +++ /dev/null
@@ -1,32 +0,0 @@ -IMPLICIT_DEPENDS_INCLUDE_TRANSFORM ----------------------------------- - -Specify #include line transforms for dependencies in a target. - -This property specifies rules to transform macro-like #include lines -during implicit dependency scanning of C and C++ source files. The -list of rules must be semicolon-separated with each entry of the form -"A_MACRO(%)=value-with-%" (the % must be literal). During dependency -scanning occurrences of A_MACRO(...) on #include lines will be -replaced by the value given with the macro argument substituted for -'%'. For example, the entry - -:: - - MYDIR(%)=<mydir/%> - -will convert lines of the form - -:: - - #include MYDIR(myheader.h) - -to - -:: - - #include <mydir/myheader.h> - -allowing the dependency to be followed. - -This property applies to sources in the target on which it is set.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.rst deleted file mode 100644 index 99e3bc4..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.rst +++ /dev/null
@@ -1,8 +0,0 @@ -IMPORTED_COMMON_LANGUAGE_RUNTIME --------------------------------- - -Property to define if the target uses ``C++/CLI``. - -Ignored for non-imported targets. - -See also the :prop_tgt:`COMMON_LANGUAGE_RUNTIME` target property.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_GLOBAL.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_GLOBAL.rst deleted file mode 100644 index 1a9129f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_GLOBAL.rst +++ /dev/null
@@ -1,30 +0,0 @@ -IMPORTED_GLOBAL ---------------- - -Indication of whether an :ref:`IMPORTED target <Imported Targets>` is -globally visible. - -The boolean value of this property is True for targets created with the -``IMPORTED`` ``GLOBAL`` options to :command:`add_executable()` or -:command:`add_library()`. It is always False for targets built within the -project. - -For targets created with the ``IMPORTED`` option to -:command:`add_executable()` or :command:`add_library()` but without the -additional option ``GLOBAL`` this is False, too. However, setting this -property for such a locally ``IMPORTED`` target to True promotes that -target to global scope. This promotion can only be done in the same -directory where that ``IMPORTED`` target was created in the first place. - -.. note:: - - Once an imported target has been made global, it cannot be changed back to - non-global. Therefore, if a project sets this property, it may only - provide a value of True. CMake will issue an error if the project tries to - set the property to a non-True value, even if the value was already False. - -.. note:: - - Local :ref:`ALIAS targets <Alias Targets>` created before promoting an - :ref:`IMPORTED target <Imported Targets>` from ``LOCAL`` to ``GLOBAL``, keep - their initial scope (see :prop_tgt:`ALIAS_GLOBAL` target property).
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME.rst deleted file mode 100644 index 1943dba..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME.rst +++ /dev/null
@@ -1,23 +0,0 @@ -IMPORTED_LIBNAME ----------------- - -Specify the link library name for an :ref:`imported <Imported Targets>` -:ref:`Interface Library <Interface Libraries>`. - -An interface library builds no library file itself but does specify -usage requirements for its consumers. The ``IMPORTED_LIBNAME`` -property may be set to specify a single library name to be placed -on the link line in place of the interface library target name as -a requirement for using the interface. - -This property is intended for use in naming libraries provided by -a platform SDK for which the full path to a library file may not -be known. The value may be a plain library name such as ``foo`` -but may *not* be a path (e.g. ``/usr/lib/libfoo.so``) or a flag -(e.g. ``-Wl,...``). The name is never treated as a library target -name even if it happens to name one. - -The ``IMPORTED_LIBNAME`` property is allowed only on -:ref:`imported <Imported Targets>` :ref:`Interface Libraries` -and is rejected on targets of other types (for which -the :prop_tgt:`IMPORTED_LOCATION` target property may be used).
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME_CONFIG.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME_CONFIG.rst deleted file mode 100644 index a28b838..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LIBNAME_CONFIG.rst +++ /dev/null
@@ -1,7 +0,0 @@ -IMPORTED_LIBNAME_<CONFIG> -------------------------- - -<CONFIG>-specific version of :prop_tgt:`IMPORTED_LIBNAME` property. - -Configuration names correspond to those provided by the project from -which the target is imported.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LOCATION.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_LOCATION.rst deleted file mode 100644 index f0a1646..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_LOCATION.rst +++ /dev/null
@@ -1,31 +0,0 @@ -IMPORTED_LOCATION ------------------ - -Full path to the main file on disk for an ``IMPORTED`` target. - -Set this to the location of an ``IMPORTED`` target file on disk. For -executables this is the location of the executable file. For bundles -on macOS this is the location of the executable file inside -``Contents/MacOS`` under the application bundle folder. For ``STATIC`` -libraries and modules this is the location of the library or module. -For ``SHARED`` libraries on non-DLL platforms this is the location of the -shared library. For frameworks on macOS this is the location of the -library file symlink just inside the framework folder. For DLLs this -is the location of the ``.dll`` part of the library. For ``UNKNOWN`` -libraries this is the location of the file to be linked. Ignored for -non-imported targets. - -The ``IMPORTED_LOCATION`` target property may be overridden for a -given configuration ``<CONFIG>`` by the configuration-specific -:prop_tgt:`IMPORTED_LOCATION_<CONFIG>` target property. Furthermore, -the :prop_tgt:`MAP_IMPORTED_CONFIG_<CONFIG>` target property may be -used to map between a project's configurations and those of an imported -target. If none of these is set then the name of any other configuration -listed in the :prop_tgt:`IMPORTED_CONFIGURATIONS` target property may be -selected and its :prop_tgt:`IMPORTED_LOCATION_<CONFIG>` value used. - -To get the location of an imported target read one of the :prop_tgt:`LOCATION` -or ``LOCATION_<CONFIG>`` properties. - -For platforms with import libraries (e.g. Windows) see also -:prop_tgt:`IMPORTED_IMPLIB`.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS.rst deleted file mode 100644 index 50a329f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -IMPORTED_OBJECTS ----------------- - -A :ref:`semicolon-separated list <CMake Language Lists>` of absolute paths to the object -files on disk for an :ref:`imported <Imported targets>` -:ref:`object library <object libraries>`. - -Ignored for non-imported targets. - -Projects may skip ``IMPORTED_OBJECTS`` if the configuration-specific -property :prop_tgt:`IMPORTED_OBJECTS_<CONFIG>` is set instead.
diff --git a/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS_CONFIG.rst b/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS_CONFIG.rst deleted file mode 100644 index 4419ed1..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IMPORTED_OBJECTS_CONFIG.rst +++ /dev/null
@@ -1,7 +0,0 @@ -IMPORTED_OBJECTS_<CONFIG> -------------------------- - -<CONFIG>-specific version of :prop_tgt:`IMPORTED_OBJECTS` property. - -Configuration names correspond to those provided by the project from -which the target is imported.
diff --git a/share/cmake-3.18/Help/prop_tgt/INSTALL_NAME_DIR.rst b/share/cmake-3.18/Help/prop_tgt/INSTALL_NAME_DIR.rst deleted file mode 100644 index 747615a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INSTALL_NAME_DIR.rst +++ /dev/null
@@ -1,16 +0,0 @@ -INSTALL_NAME_DIR ----------------- - -macOS directory name for installed targets. - -``INSTALL_NAME_DIR`` is a string specifying the directory portion of the -"install_name" field of shared libraries on macOS to use in the -installed targets. - -This property is initialized by the value of the variable -:variable:`CMAKE_INSTALL_NAME_DIR` if it is set when a target is -created. - -This property supports :manual:`generator expressions <cmake-generator-expressions(7)>`. -In particular, the ``$<INSTALL_PREFIX>`` generator expression can be used to set the -directory relative to the install-time prefix.
diff --git a/share/cmake-3.18/Help/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.rst b/share/cmake-3.18/Help/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.rst deleted file mode 100644 index 72dcaa0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.rst +++ /dev/null
@@ -1,16 +0,0 @@ -INSTALL_REMOVE_ENVIRONMENT_RPATH --------------------------------- - -Controls whether toolchain-defined rpaths should be removed during installation. - -When a target is being installed, CMake may need to rewrite its rpath -information. This occurs when the install rpath (as specified by the -:prop_tgt:`INSTALL_RPATH` target property) has different contents to the rpath -that the target was built with. Some toolchains insert their own rpath -contents into the binary as part of the build. By default, CMake will -preserve those extra inserted contents in the install rpath. For those -scenarios where such toolchain-inserted entries need to be discarded during -install, set the ``INSTALL_REMOVE_ENVIRONMENT_RPATH`` target property to true. - -This property is initialized by the value of -:variable:`CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH` when the target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_COMPILE_FEATURES.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_COMPILE_FEATURES.rst deleted file mode 100644 index 31b594f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_COMPILE_FEATURES.rst +++ /dev/null
@@ -1,12 +0,0 @@ -INTERFACE_COMPILE_FEATURES --------------------------- - -.. |property_name| replace:: compile features -.. |command_name| replace:: :command:`target_compile_features` -.. |PROPERTY_INTERFACE_NAME| replace:: ``INTERFACE_COMPILE_FEATURES`` -.. |PROPERTY_LINK| replace:: :prop_tgt:`COMPILE_FEATURES` -.. |PROPERTY_GENEX| replace:: ``$<TARGET_PROPERTY:foo,INTERFACE_COMPILE_FEATURES>`` -.. include:: INTERFACE_BUILD_PROPERTY.txt - -See the :manual:`cmake-compile-features(7)` manual for information on compile -features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DEPENDS.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DEPENDS.rst deleted file mode 100644 index 790554d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DEPENDS.rst +++ /dev/null
@@ -1,32 +0,0 @@ -INTERFACE_LINK_DEPENDS ----------------------- - -Additional public interface files on which a target binary depends for linking. - -This property is supported only by :generator:`Ninja` and -:ref:`Makefile Generators`. -It is intended to specify dependencies on "linker scripts" for -custom Makefile link rules. - -When target dependencies are specified using :command:`target_link_libraries`, -CMake will read this property from all target dependencies to determine the -build properties of the consumer. - -Contents of ``INTERFACE_LINK_DEPENDS`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` --manual for more on defining buildsystem properties. - -Link dependency files usage requirements commonly differ between the build-tree -and the install-tree. The ``BUILD_INTERFACE`` and ``INSTALL_INTERFACE`` -generator expressions can be used to describe separate usage requirements -based on the usage location. Relative paths are allowed within the -``INSTALL_INTERFACE`` expression and are interpreted relative to the -installation prefix. For example: - -.. code-block:: cmake - - set_property(TARGET mylib PROPERTY INTERFACE_LINK_DEPENDS - $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/mylinkscript> - $<INSTALL_INTERFACE:mylinkscript> # <prefix>/mylinkscript - )
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DIRECTORIES.rst deleted file mode 100644 index 56a4ec0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_DIRECTORIES.rst +++ /dev/null
@@ -1,9 +0,0 @@ -INTERFACE_LINK_DIRECTORIES --------------------------- - -.. |property_name| replace:: link directories -.. |command_name| replace:: :command:`target_link_directories` -.. |PROPERTY_INTERFACE_NAME| replace:: ``INTERFACE_LINK_DIRECTORIES`` -.. |PROPERTY_LINK| replace:: :prop_tgt:`LINK_DIRECTORIES` -.. |PROPERTY_GENEX| replace:: ``$<TARGET_PROPERTY:foo,INTERFACE_LINK_DIRECTORIES>`` -.. include:: INTERFACE_BUILD_PROPERTY.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_OPTIONS.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_OPTIONS.rst deleted file mode 100644 index c293b98..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_LINK_OPTIONS.rst +++ /dev/null
@@ -1,9 +0,0 @@ -INTERFACE_LINK_OPTIONS ----------------------- - -.. |property_name| replace:: link options -.. |command_name| replace:: :command:`target_link_options` -.. |PROPERTY_INTERFACE_NAME| replace:: ``INTERFACE_LINK_OPTIONS`` -.. |PROPERTY_LINK| replace:: :prop_tgt:`LINK_OPTIONS` -.. |PROPERTY_GENEX| replace:: ``$<TARGET_PROPERTY:foo,INTERFACE_LINK_OPTIONS>`` -.. include:: INTERFACE_BUILD_PROPERTY.txt
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.rst deleted file mode 100644 index e285407..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.rst +++ /dev/null
@@ -1,16 +0,0 @@ -INTERFACE_PRECOMPILE_HEADERS ----------------------------- - -List of interface header files to precompile into consuming targets. - -Targets may populate this property to publish the header files -for consuming targets to precompile. The :command:`target_precompile_headers` -command populates this property with values given to the ``PUBLIC`` and -``INTERFACE`` keywords. Projects may also get and set the property directly. -See the discussion in :command:`target_precompile_headers` for guidance on -appropriate use of this property for installed or exported targets. - -Contents of ``INTERFACE_PRECOMPILE_HEADERS`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/INTERFACE_SOURCES.rst b/share/cmake-3.18/Help/prop_tgt/INTERFACE_SOURCES.rst deleted file mode 100644 index a224b68..0000000 --- a/share/cmake-3.18/Help/prop_tgt/INTERFACE_SOURCES.rst +++ /dev/null
@@ -1,18 +0,0 @@ -INTERFACE_SOURCES ------------------ - -List of interface sources to compile into consuming targets. - -Targets may populate this property to publish the sources -for consuming targets to compile. The :command:`target_sources` command -populates this property with values given to the ``PUBLIC`` and -``INTERFACE`` keywords. Projects may also get and set the property directly. - -When target dependencies are specified using :command:`target_link_libraries`, -CMake will read this property from all target dependencies to determine the -sources of the consumer. - -Contents of ``INTERFACE_SOURCES`` may use "generator expressions" -with the syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/IOS_INSTALL_COMBINED.rst b/share/cmake-3.18/Help/prop_tgt/IOS_INSTALL_COMBINED.rst deleted file mode 100644 index 59f67a7..0000000 --- a/share/cmake-3.18/Help/prop_tgt/IOS_INSTALL_COMBINED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -IOS_INSTALL_COMBINED --------------------- - -Build a combined (device and simulator) target when installing. - -When this property is set to set to false (which is the default) then it will -either be built with the device SDK or the simulator SDK depending on the SDK -set. But if this property is set to true then the target will at install time -also be built for the corresponding SDK and combined into one library. - -This feature requires at least Xcode version 6.
diff --git a/share/cmake-3.18/Help/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.rst b/share/cmake-3.18/Help/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.rst deleted file mode 100644 index ece28a4..0000000 --- a/share/cmake-3.18/Help/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.rst +++ /dev/null
@@ -1,21 +0,0 @@ -JOB_POOL_PRECOMPILE_HEADER --------------------------- - -Ninja only: Pool used for generating pre-compiled headers. - -The number of parallel compile processes could be limited by defining -pools with the global :prop_gbl:`JOB_POOLS` -property and then specifying here the pool name. - -For instance: - -.. code-block:: cmake - - set_property(TARGET myexe PROPERTY JOB_POOL_PRECOMPILE_HEADER two_jobs) - -This property is initialized by the value of -:variable:`CMAKE_JOB_POOL_PRECOMPILE_HEADER`. - -If neither :prop_tgt:`JOB_POOL_PRECOMPILE_HEADER` nor -:variable:`CMAKE_JOB_POOL_PRECOMPILE_HEADER` are set then -:prop_tgt:`JOB_POOL_COMPILE` will be used for this task.
diff --git a/share/cmake-3.18/Help/prop_tgt/LANG_CLANG_TIDY.rst b/share/cmake-3.18/Help/prop_tgt/LANG_CLANG_TIDY.rst deleted file mode 100644 index 2bfef66..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LANG_CLANG_TIDY.rst +++ /dev/null
@@ -1,13 +0,0 @@ -<LANG>_CLANG_TIDY ------------------ - -This property is implemented only when ``<LANG>`` is ``C`` or ``CXX``. - -Specify a :ref:`semicolon-separated list <CMake Language Lists>` containing a command -line for the ``clang-tidy`` tool. The :ref:`Makefile Generators` -and the :generator:`Ninja` generator will run this tool along with the -compiler and report a warning if the tool reports any problems. - -This property is initialized by the value of -the :variable:`CMAKE_<LANG>_CLANG_TIDY` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LANG_COMPILER_LAUNCHER.rst b/share/cmake-3.18/Help/prop_tgt/LANG_COMPILER_LAUNCHER.rst deleted file mode 100644 index a6f2b24..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LANG_COMPILER_LAUNCHER.rst +++ /dev/null
@@ -1,14 +0,0 @@ -<LANG>_COMPILER_LAUNCHER ------------------------- - -This property is implemented only when ``<LANG>`` is ``C``, ``CXX``, -``Fortran``, ``OBJC``, ``OBJCXX``, or ``CUDA``. - -Specify a :ref:`semicolon-separated list <CMake Language Lists>` containing a command line -for a compiler launching tool. The :ref:`Makefile Generators` and the -:generator:`Ninja` generator will run this tool and pass the compiler and -its arguments to the tool. Some example tools are distcc and ccache. - -This property is initialized by the value of -the :variable:`CMAKE_<LANG>_COMPILER_LAUNCHER` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LANG_CPPCHECK.rst b/share/cmake-3.18/Help/prop_tgt/LANG_CPPCHECK.rst deleted file mode 100644 index 60785d0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LANG_CPPCHECK.rst +++ /dev/null
@@ -1,15 +0,0 @@ -<LANG>_CPPCHECK ---------------- - -This property is supported only when ``<LANG>`` is ``C`` or ``CXX``. - -Specify a :ref:`semicolon-separated list <CMake Language Lists>` containing a command line -for the ``cppcheck`` static analysis tool. The :ref:`Makefile Generators` -and the :generator:`Ninja` generator will run ``cppcheck`` along with the -compiler and report any problems. If the command-line specifies the -exit code options to ``cppcheck`` then the build will fail if the -tool returns non-zero. - -This property is initialized by the value of the -:variable:`CMAKE_<LANG>_CPPCHECK` variable if it is set when a target is -created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LANG_CPPLINT.rst b/share/cmake-3.18/Help/prop_tgt/LANG_CPPLINT.rst deleted file mode 100644 index 9944c88..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LANG_CPPLINT.rst +++ /dev/null
@@ -1,13 +0,0 @@ -<LANG>_CPPLINT --------------- - -This property is supported only when ``<LANG>`` is ``C`` or ``CXX``. - -Specify a :ref:`semicolon-separated list <CMake Language Lists>` containing a command line -for the ``cpplint`` style checker. The :ref:`Makefile Generators` and the -:generator:`Ninja` generator will run ``cpplint`` along with the compiler -and report any problems. - -This property is initialized by the value of the -:variable:`CMAKE_<LANG>_CPPLINT` variable if it is set when a target is -created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.rst b/share/cmake-3.18/Help/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.rst deleted file mode 100644 index 35220e4..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.rst +++ /dev/null
@@ -1,13 +0,0 @@ -<LANG>_INCLUDE_WHAT_YOU_USE ---------------------------- - -This property is implemented only when ``<LANG>`` is ``C`` or ``CXX``. - -Specify a :ref:`semicolon-separated list <CMake Language Lists>` containing a command -line for the ``include-what-you-use`` tool. The :ref:`Makefile Generators` -and the :generator:`Ninja` generator will run this tool along with the -compiler and report a warning if the tool reports any problems. - -This property is initialized by the value of -the :variable:`CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.rst deleted file mode 100644 index 785a57b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.rst +++ /dev/null
@@ -1,9 +0,0 @@ -LIBRARY_OUTPUT_DIRECTORY ------------------------- - -.. |XXX| replace:: :ref:`LIBRARY <Library Output Artifacts>` -.. |xxx| replace:: library -.. |CMAKE_XXX_OUTPUT_DIRECTORY| replace:: CMAKE_LIBRARY_OUTPUT_DIRECTORY -.. include:: XXX_OUTPUT_DIRECTORY.txt - -See also the :prop_tgt:`LIBRARY_OUTPUT_DIRECTORY_<CONFIG>` target property.
diff --git a/share/cmake-3.18/Help/prop_tgt/LINK_DEPENDS_NO_SHARED.rst b/share/cmake-3.18/Help/prop_tgt/LINK_DEPENDS_NO_SHARED.rst deleted file mode 100644 index 5c6778d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LINK_DEPENDS_NO_SHARED.rst +++ /dev/null
@@ -1,14 +0,0 @@ -LINK_DEPENDS_NO_SHARED ----------------------- - -Do not depend on linked shared library files. - -Set this property to true to tell CMake generators not to add -file-level dependencies on the shared library files linked by this -target. Modification to the shared libraries will not be sufficient -to re-link this target. Logical target-level dependencies will not be -affected so the linked shared libraries will still be brought up to -date before this target is built. - -This property is initialized by the value of the variable -CMAKE_LINK_DEPENDS_NO_SHARED if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/LINK_DIRECTORIES.rst b/share/cmake-3.18/Help/prop_tgt/LINK_DIRECTORIES.rst deleted file mode 100644 index c2905b3..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LINK_DIRECTORIES.rst +++ /dev/null
@@ -1,18 +0,0 @@ -LINK_DIRECTORIES ----------------- - -List of directories to use for the link step of shared library, module -and executable targets. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of directories -specified so far for its target. Use the :command:`target_link_directories` -command to append more search directories. - -This property is initialized by the :prop_dir:`LINK_DIRECTORIES` directory -property when a target is created, and is used by the generators to set -the search directories for the linker. - -Contents of ``LINK_DIRECTORIES`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/LINK_OPTIONS.rst b/share/cmake-3.18/Help/prop_tgt/LINK_OPTIONS.rst deleted file mode 100644 index ff3ee87..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LINK_OPTIONS.rst +++ /dev/null
@@ -1,28 +0,0 @@ -LINK_OPTIONS ------------- - -List of options to use for the link step of shared library, module -and executable targets as well as the device link step. Targets that are static -libraries need to use the :prop_tgt:`STATIC_LIBRARY_OPTIONS` target property. - -These options are used for both normal linking and device linking -(see policy :policy:`CMP0105`). To control link options for normal and device -link steps, ``$<HOST_LINK>`` and ``$<DEVICE_LINK>`` -:manual:`generator expressions <cmake-generator-expressions(7)>` can be used. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of -options specified so far for its target. Use the :command:`target_link_options` -command to append more options. - -This property is initialized by the :prop_dir:`LINK_OPTIONS` directory -property when a target is created, and is used by the generators to set -the options for the compiler. - -Contents of ``LINK_OPTIONS`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties. - -.. note:: - - This property must be used in preference to :prop_tgt:`LINK_FLAGS` property.
diff --git a/share/cmake-3.18/Help/prop_tgt/LINK_WHAT_YOU_USE.rst b/share/cmake-3.18/Help/prop_tgt/LINK_WHAT_YOU_USE.rst deleted file mode 100644 index 32d6edb..0000000 --- a/share/cmake-3.18/Help/prop_tgt/LINK_WHAT_YOU_USE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -LINK_WHAT_YOU_USE ---------------------------- - -This is a boolean option that when set to ``TRUE`` will automatically run -``ldd -r -u`` on the target after it is linked. In addition, the linker flag -``-Wl,--no-as-needed`` will be passed to the target with the link command so -that all libraries specified on the command line will be linked into the -target. This will result in the link producing a list of libraries that -provide no symbols used by this target but are being linked to it. -This is only applicable to executable and shared library targets and -will only work when ld and ldd accept the flags used. - -This property is initialized by the value of -the :variable:`CMAKE_LINK_WHAT_YOU_USE` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/MACHO_COMPATIBILITY_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/MACHO_COMPATIBILITY_VERSION.rst deleted file mode 100644 index 26d5cc8..0000000 --- a/share/cmake-3.18/Help/prop_tgt/MACHO_COMPATIBILITY_VERSION.rst +++ /dev/null
@@ -1,25 +0,0 @@ -MACHO_COMPATIBILITY_VERSION ---------------------------- - -What compatibility version number is this target for Mach-O binaries. - -For shared libraries on Mach-O systems (e.g. macOS, iOS) -the ``MACHO_COMPATIBILITY_VERSION`` property corresponds to the -*compatibility version* and :prop_tgt:`MACHO_CURRENT_VERSION` corresponds to -the *current version*. These are both embedded in the shared library binary -and can be checked with the ``otool -L <binary>`` command. - -It should be noted that the :prop_tgt:`MACHO_CURRENT_VERSION` and -``MACHO_COMPATIBILITY_VERSION`` properties do not affect the file -names or version-related symlinks that CMake generates for the library. -The :prop_tgt:`VERSION` and :prop_tgt:`SOVERSION` target properties still -control the file and symlink names. The ``install_name`` is also still -controlled by :prop_tgt:`SOVERSION`. - -When :prop_tgt:`MACHO_CURRENT_VERSION` and ``MACHO_COMPATIBILITY_VERSION`` -are not given, :prop_tgt:`VERSION` and :prop_tgt:`SOVERSION` are used for -the version details to be embedded in the binaries respectively. -The :prop_tgt:`MACHO_CURRENT_VERSION` and ``MACHO_COMPATIBILITY_VERSION`` -properties only need to be given if the project needs to decouple the file -and symlink naming from the version details embedded in the binaries -(e.g. to match libtool conventions).
diff --git a/share/cmake-3.18/Help/prop_tgt/MACHO_CURRENT_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/MACHO_CURRENT_VERSION.rst deleted file mode 100644 index 9afb356..0000000 --- a/share/cmake-3.18/Help/prop_tgt/MACHO_CURRENT_VERSION.rst +++ /dev/null
@@ -1,25 +0,0 @@ -MACHO_CURRENT_VERSION ---------------------- - -What current version number is this target for Mach-O binaries. - -For shared libraries on Mach-O systems (e.g. macOS, iOS) -the :prop_tgt:`MACHO_COMPATIBILITY_VERSION` property corresponds to the -*compatibility version* and ``MACHO_CURRENT_VERSION`` corresponds to the -*current version*. These are both embedded in the shared library binary -and can be checked with the ``otool -L <binary>`` command. - -It should be noted that the ``MACHO_CURRENT_VERSION`` and -:prop_tgt:`MACHO_COMPATIBILITY_VERSION` properties do not affect the file -names or version-related symlinks that CMake generates for the library. -The :prop_tgt:`VERSION` and :prop_tgt:`SOVERSION` target properties still -control the file and symlink names. The ``install_name`` is also still -controlled by :prop_tgt:`SOVERSION`. - -When ``MACHO_CURRENT_VERSION`` and :prop_tgt:`MACHO_COMPATIBILITY_VERSION` -are not given, :prop_tgt:`VERSION` and :prop_tgt:`SOVERSION` are used for -the version details to be embedded in the binaries respectively. -The ``MACHO_CURRENT_VERSION`` and :prop_tgt:`MACHO_COMPATIBILITY_VERSION` -properties only need to be given if the project needs to decouple the file -and symlink naming from the version details embedded in the binaries -(e.g. to match libtool conventions).
diff --git a/share/cmake-3.18/Help/prop_tgt/MANUALLY_ADDED_DEPENDENCIES.rst b/share/cmake-3.18/Help/prop_tgt/MANUALLY_ADDED_DEPENDENCIES.rst deleted file mode 100644 index c12ea14..0000000 --- a/share/cmake-3.18/Help/prop_tgt/MANUALLY_ADDED_DEPENDENCIES.rst +++ /dev/null
@@ -1,8 +0,0 @@ -MANUALLY_ADDED_DEPENDENCIES ---------------------------- - -Get manually added dependencies to other top-level targets. - -This read-only property can be used to query all dependencies that -were added for this target with the :command:`add_dependencies` -command.
diff --git a/share/cmake-3.18/Help/prop_tgt/MSVC_RUNTIME_LIBRARY.rst b/share/cmake-3.18/Help/prop_tgt/MSVC_RUNTIME_LIBRARY.rst deleted file mode 100644 index 73792de..0000000 --- a/share/cmake-3.18/Help/prop_tgt/MSVC_RUNTIME_LIBRARY.rst +++ /dev/null
@@ -1,29 +0,0 @@ -MSVC_RUNTIME_LIBRARY --------------------- - -Select the MSVC runtime library for use by compilers targeting the MSVC ABI. - -The allowed values are: - -.. include:: MSVC_RUNTIME_LIBRARY-VALUES.txt - -Use :manual:`generator expressions <cmake-generator-expressions(7)>` to -support per-configuration specification. For example, the code: - -.. code-block:: cmake - - add_executable(foo foo.c) - set_property(TARGET foo PROPERTY - MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>") - -selects for the target ``foo`` a multi-threaded statically-linked runtime -library with or without debug information depending on the configuration. - -If this property is not set then CMake uses the default value -``MultiThreaded$<$<CONFIG:Debug>:Debug>DLL`` to select a MSVC runtime library. - -.. note:: - - This property has effect only when policy :policy:`CMP0091` is set to ``NEW`` - prior to the first :command:`project` or :command:`enable_language` command - that enables a language using a compiler targeting the MSVC ABI.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJCXX_EXTENSIONS.rst b/share/cmake-3.18/Help/prop_tgt/OBJCXX_EXTENSIONS.rst deleted file mode 100644 index 9f9d804..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJCXX_EXTENSIONS.rst +++ /dev/null
@@ -1,20 +0,0 @@ -OBJCXX_EXTENSIONS ------------------ - -Boolean specifying whether compiler specific extensions are requested. - -This property specifies whether compiler specific extensions should be -used. For some compilers, this results in adding a flag such -as ``-std=gnu++11`` instead of ``-std=c++11`` to the compile line. This -property is ``ON`` by default. The basic ObjC++ standard level is -controlled by the :prop_tgt:`OBJCXX_STANDARD` target property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -If the property is not set, and the project has set the :prop_tgt:`CXX_EXTENSIONS`, -the value of :prop_tgt:`CXX_EXTENSIONS` is set for :prop_tgt:`OBJCXX_EXTENSIONS`. - -This property is initialized by the value of -the :variable:`CMAKE_OBJCXX_EXTENSIONS` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD.rst b/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD.rst deleted file mode 100644 index 3c925dc..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD.rst +++ /dev/null
@@ -1,35 +0,0 @@ -OBJCXX_STANDARD ---------------- - -The ObjC++ standard whose features are requested to build this target. - -This property specifies the ObjC++ standard whose features are requested -to build this target. For some compilers, this results in adding a -flag such as ``-std=gnu++11`` to the compile line. - -Supported values are ``98``, ``11``, ``14``, ``17``, and ``20``. - -If the value requested does not result in a compile flag being added for -the compiler in use, a previous standard flag will be added instead. This -means that using: - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY OBJCXX_STANDARD 11) - -with a compiler which does not support ``-std=gnu++11`` or an equivalent -flag will not result in an error or warning, but will instead add the -``-std=gnu++98`` flag if supported. This "decay" behavior may be controlled -with the :prop_tgt:`OBJCXX_STANDARD_REQUIRED` target property. -Additionally, the :prop_tgt:`OBJCXX_EXTENSIONS` target property may be used to -control whether compiler-specific extensions are enabled on a per-target basis. - -If the property is not set, and the project has set the :prop_tgt:`CXX_STANDARD`, -the value of :prop_tgt:`CXX_STANDARD` is set for :prop_tgt:`OBJCXX_STANDARD`. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_OBJCXX_STANDARD` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD_REQUIRED.rst deleted file mode 100644 index c330abf..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJCXX_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,20 +0,0 @@ -OBJCXX_STANDARD_REQUIRED ------------------------- - -Boolean describing whether the value of :prop_tgt:`OBJCXX_STANDARD` is a requirement. - -If this property is set to ``ON``, then the value of the -:prop_tgt:`OBJCXX_STANDARD` target property is treated as a requirement. If this -property is ``OFF`` or unset, the :prop_tgt:`OBJCXX_STANDARD` target property is -treated as optional and may "decay" to a previous standard if the requested is -not available. - -If the property is not set, and the project has set the :prop_tgt:`CXX_STANDARD_REQUIRED`, -the value of :prop_tgt:`CXX_STANDARD_REQUIRED` is set for :prop_tgt:`OBJCXX_STANDARD_REQUIRED`. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_OBJCXX_STANDARD_REQUIRED` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJC_EXTENSIONS.rst b/share/cmake-3.18/Help/prop_tgt/OBJC_EXTENSIONS.rst deleted file mode 100644 index 2de9e48..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJC_EXTENSIONS.rst +++ /dev/null
@@ -1,20 +0,0 @@ -OBJC_EXTENSIONS ---------------- - -Boolean specifying whether compiler specific extensions are requested. - -This property specifies whether compiler specific extensions should be -used. For some compilers, this results in adding a flag such -as ``-std=gnu11`` instead of ``-std=c11`` to the compile line. This -property is ``ON`` by default. The basic OBJC standard level is -controlled by the :prop_tgt:`OBJC_STANDARD` target property. - -If the property is not set, and the project has set the :prop_tgt:`C_EXTENSIONS`, -the value of :prop_tgt:`C_EXTENSIONS` is set for :prop_tgt:`OBJC_EXTENSIONS`. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_OBJC_EXTENSIONS` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD.rst b/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD.rst deleted file mode 100644 index d1e1b24..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD.rst +++ /dev/null
@@ -1,35 +0,0 @@ -OBJC_STANDARD -------------- - -The OBJC standard whose features are requested to build this target. - -This property specifies the OBJC standard whose features are requested -to build this target. For some compilers, this results in adding a -flag such as ``-std=gnu11`` to the compile line. - -Supported values are ``90``, ``99`` and ``11``. - -If the value requested does not result in a compile flag being added for -the compiler in use, a previous standard flag will be added instead. This -means that using: - -.. code-block:: cmake - - set_property(TARGET tgt PROPERTY OBJC_STANDARD 11) - -with a compiler which does not support ``-std=gnu11`` or an equivalent -flag will not result in an error or warning, but will instead add the -``-std=gnu99`` or ``-std=gnu90`` flag if supported. This "decay" behavior may -be controlled with the :prop_tgt:`OBJC_STANDARD_REQUIRED` target property. -Additionally, the :prop_tgt:`OBJC_EXTENSIONS` target property may be used to -control whether compiler-specific extensions are enabled on a per-target basis. - -If the property is not set, and the project has set the :prop_tgt:`C_STANDARD`, -the value of :prop_tgt:`C_STANDARD` is set for :prop_tgt:`OBJC_STANDARD`. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_OBJC_STANDARD` variable if it is set when a target -is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD_REQUIRED.rst deleted file mode 100644 index 8cf377c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/OBJC_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,20 +0,0 @@ -OBJC_STANDARD_REQUIRED ----------------------- - -Boolean describing whether the value of :prop_tgt:`OBJC_STANDARD` is a requirement. - -If this property is set to ``ON``, then the value of the -:prop_tgt:`OBJC_STANDARD` target property is treated as a requirement. If this -property is ``OFF`` or unset, the :prop_tgt:`OBJC_STANDARD` target property is -treated as optional and may "decay" to a previous standard if the requested is -not available. - -If the property is not set, and the project has set the :prop_tgt:`C_STANDARD_REQUIRED`, -the value of :prop_tgt:`C_STANDARD_REQUIRED` is set for :prop_tgt:`OBJC_STANDARD_REQUIRED`. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers. - -This property is initialized by the value of -the :variable:`CMAKE_OBJC_STANDARD_REQUIRED` variable if it is set when a -target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/PCH_WARN_INVALID.rst b/share/cmake-3.18/Help/prop_tgt/PCH_WARN_INVALID.rst deleted file mode 100644 index 96e1abd..0000000 --- a/share/cmake-3.18/Help/prop_tgt/PCH_WARN_INVALID.rst +++ /dev/null
@@ -1,10 +0,0 @@ -PCH_WARN_INVALID ----------------- - -When this property is set to true, the precompile header compiler options -will contain a compiler flag which should warn about invalid precompiled -headers e.g. ``-Winvalid-pch`` for GNU compiler. - -This property is initialized by the value of the -:variable:`CMAKE_PCH_WARN_INVALID` variable if it is set when a target is -created. If that variable is not set, the property defaults to ``ON``.
diff --git a/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS.rst b/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS.rst deleted file mode 100644 index 9e70b65..0000000 --- a/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -PRECOMPILE_HEADERS ------------------- - -List of header files to precompile. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` -of header files to precompile specified so far for its target. -Use the :command:`target_precompile_headers` command to append more header -files. - -This property supports -:manual:`generator expressions <cmake-generator-expressions(7)>`.
diff --git a/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.rst b/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.rst deleted file mode 100644 index 9c3e7ea..0000000 --- a/share/cmake-3.18/Help/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.rst +++ /dev/null
@@ -1,7 +0,0 @@ -PRECOMPILE_HEADERS_REUSE_FROM ------------------------------ - -Target from which to reuse the precompiled headers build artifact. - -See the second signature of :command:`target_precompile_headers` command -for more detailed information.
diff --git a/share/cmake-3.18/Help/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.rst deleted file mode 100644 index 12390f5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.rst +++ /dev/null
@@ -1,9 +0,0 @@ -RUNTIME_OUTPUT_DIRECTORY ------------------------- - -.. |XXX| replace:: :ref:`RUNTIME <Runtime Output Artifacts>` -.. |xxx| replace:: runtime -.. |CMAKE_XXX_OUTPUT_DIRECTORY| replace:: CMAKE_RUNTIME_OUTPUT_DIRECTORY -.. include:: XXX_OUTPUT_DIRECTORY.txt - -See also the :prop_tgt:`RUNTIME_OUTPUT_DIRECTORY_<CONFIG>` target property.
diff --git a/share/cmake-3.18/Help/prop_tgt/SOURCE_DIR.rst b/share/cmake-3.18/Help/prop_tgt/SOURCE_DIR.rst deleted file mode 100644 index b25813b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/SOURCE_DIR.rst +++ /dev/null
@@ -1,6 +0,0 @@ -SOURCE_DIR ----------- - -This read-only property reports the value of the -:variable:`CMAKE_CURRENT_SOURCE_DIR` variable in the directory in which -the target was defined.
diff --git a/share/cmake-3.18/Help/prop_tgt/STATIC_LIBRARY_OPTIONS.rst b/share/cmake-3.18/Help/prop_tgt/STATIC_LIBRARY_OPTIONS.rst deleted file mode 100644 index d05fda4..0000000 --- a/share/cmake-3.18/Help/prop_tgt/STATIC_LIBRARY_OPTIONS.rst +++ /dev/null
@@ -1,20 +0,0 @@ -STATIC_LIBRARY_OPTIONS ----------------------- - -Archiver (or MSVC librarian) flags for a static library target. -Targets that are shared libraries, modules, or executables need to use -the :prop_tgt:`LINK_OPTIONS` target property. - -This property holds a :ref:`semicolon-separated list <CMake Language Lists>` of options -specified so far for its target. Use :command:`set_target_properties` or -:command:`set_property` commands to set its content. - -Contents of ``STATIC_LIBRARY_OPTIONS`` may use "generator expressions" with the -syntax ``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual -for available expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties. - -.. note:: - - This property must be used in preference to :prop_tgt:`STATIC_LIBRARY_FLAGS` - property.
diff --git a/share/cmake-3.18/Help/prop_tgt/Swift_DEPENDENCIES_FILE.rst b/share/cmake-3.18/Help/prop_tgt/Swift_DEPENDENCIES_FILE.rst deleted file mode 100644 index 46c9a1d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Swift_DEPENDENCIES_FILE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -Swift_DEPENDENCIES_FILE ------------------------ - -This property sets the path for the Swift dependency file (swiftdep) for the -target. If one is not specified, it will default to ``<TARGET>.swiftdeps``.
diff --git a/share/cmake-3.18/Help/prop_tgt/Swift_LANGUAGE_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/Swift_LANGUAGE_VERSION.rst deleted file mode 100644 index 7579447..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Swift_LANGUAGE_VERSION.rst +++ /dev/null
@@ -1,6 +0,0 @@ -Swift_LANGUAGE_VERSION ----------------------- - -This property sets the language version for the Swift sources in the target. If -one is not specified, it will default to ``<CMAKE_Swift_LANGUAGE_VERSION>`` if -specified, otherwise it is the latest version supported by the compiler.
diff --git a/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_DIRECTORY.rst deleted file mode 100644 index d404251..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_DIRECTORY.rst +++ /dev/null
@@ -1,10 +0,0 @@ -Swift_MODULE_DIRECTORY ----------------------- - -Specify output directory for Swift modules provided by the target. - -If the target contains Swift source files, this specifies the directory in which -the modules will be placed. When this property is not set, the modules will be -placed in the build directory corresponding to the target's source directory. -If the variable :variable:`CMAKE_Swift_MODULE_DIRECTORY` is set when a target is -created its value is used to initialise this property.
diff --git a/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_NAME.rst b/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_NAME.rst deleted file mode 100644 index 2866020..0000000 --- a/share/cmake-3.18/Help/prop_tgt/Swift_MODULE_NAME.rst +++ /dev/null
@@ -1,5 +0,0 @@ -Swift_MODULE_NAME ------------------ - -This property specifies the name of the Swift module. It is defaulted to the -name of the target.
diff --git a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD.rst b/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD.rst deleted file mode 100644 index e140952..0000000 --- a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD.rst +++ /dev/null
@@ -1,80 +0,0 @@ -UNITY_BUILD ------------ - -When this property is set to true, the target source files will be combined -into batches for faster compilation. This is done by creating a (set of) -unity sources which ``#include`` the original sources, then compiling these -unity sources instead of the originals. This is known as a *Unity* or *Jumbo* -build. - -CMake provides different algorithms for selecting which sources are grouped -together into a *bucket*. Algorithm selection is decided by the -:prop_tgt:`UNITY_BUILD_MODE` target property, which has the following acceptable -values: - -* ``BATCH`` - When in this mode CMake determines which files are grouped together. - The :prop_tgt:`UNITY_BUILD_BATCH_SIZE` property controls the upper limit on - how many sources can be combined per unity source file. - -* ``GROUP`` - When in this mode each target explicitly specifies how to group - source files. Each source file that has the same - :prop_sf:`UNITY_GROUP` value will be grouped together. Any sources - that don't have this property will be compiled individually. The - :prop_tgt:`UNITY_BUILD_BATCH_SIZE` property is ignored when using - this mode. - -If no explicit :prop_tgt:`UNITY_BUILD_MODE` has been specified, CMake will -default to ``BATCH``. - -Unity builds are not currently supported for all languages. CMake version -|release| supports combining ``C`` and ``CXX`` source files. For targets that -mix source files from more than one language, CMake will separate the languages -such that each generated unity source file only contains sources for a single -language. - -This property is initialized by the value of the :variable:`CMAKE_UNITY_BUILD` -variable when a target is created. - -.. note:: - - Projects should not directly set the ``UNITY_BUILD`` property or its - associated :variable:`CMAKE_UNITY_BUILD` variable to true. Depending - on the capabilities of the build machine and compiler used, it might or - might not be appropriate to enable unity builds. Therefore, this feature - should be under developer control, which would normally be through the - developer choosing whether or not to set the :variable:`CMAKE_UNITY_BUILD` - variable on the :manual:`cmake(1)` command line or some other equivalent - method. However, it IS recommended to set the ``UNITY_BUILD`` target - property to false if it is known that enabling unity builds for the - target can lead to problems. - -ODR (One definition rule) errors -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -When multiple source files are included into one source file, as is done -for unity builds, it can potentially lead to ODR errors. CMake provides -a number of measures to help address such problems: - -* Any source file that has a non-empty :prop_sf:`COMPILE_OPTIONS`, - :prop_sf:`COMPILE_DEFINITIONS`, :prop_sf:`COMPILE_FLAGS`, or - :prop_sf:`INCLUDE_DIRECTORIES` source property will not be combined - into a unity source. - -* Projects can prevent an individual source file from being combined into - a unity source by setting its :prop_sf:`SKIP_UNITY_BUILD_INCLUSION` - source property to true. This can be a more effective way to prevent - problems with specific files than disabling unity builds for an entire - target. - -* The :prop_tgt:`UNITY_BUILD_CODE_BEFORE_INCLUDE` and - :prop_tgt:`UNITY_BUILD_CODE_AFTER_INCLUDE` target properties can be used - to inject code into the unity source files before and after every - ``#include`` statement. - -* The order of source files added to the target via commands like - :command:`add_library`, :command:`add_executable` or - :command:`target_sources` will be preserved in the generated unity source - files. This can be used to manually enforce a specific grouping based on - the :prop_tgt:`UNITY_BUILD_BATCH_SIZE` target property.
diff --git a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_BATCH_SIZE.rst b/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_BATCH_SIZE.rst deleted file mode 100644 index 44ffe27..0000000 --- a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_BATCH_SIZE.rst +++ /dev/null
@@ -1,23 +0,0 @@ -UNITY_BUILD_BATCH_SIZE ----------------------- - -Specifies the maximum number of source files that can be combined into any one -unity source file when unity builds are enabled by the :prop_tgt:`UNITY_BUILD` -target property. The original source files will be distributed across as many -unity source files as necessary to honor this limit. - -The initial value for this property is taken from the -:variable:`CMAKE_UNITY_BUILD_BATCH_SIZE` variable when the target is created. -If that variable has not been set, the initial value will be 8. - -The batch size needs to be selected carefully. If set too high, the size of -the combined source files could result in the compiler using excessive memory -or hitting other similar limits. In extreme cases, this can even result in -build failure. On the other hand, if the batch size is too low, there will be -little gain in build performance. - -Although strongly discouraged, the batch size may be set to a value of 0 to -combine all the sources for the target into a single unity file, regardless of -how many sources are involved. This runs the risk of creating an excessively -large unity source file and negatively impacting the build performance, so -a value of 0 is not generally recommended.
diff --git a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_AFTER_INCLUDE.rst b/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_AFTER_INCLUDE.rst deleted file mode 100644 index 7231b61..0000000 --- a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_AFTER_INCLUDE.rst +++ /dev/null
@@ -1,19 +0,0 @@ -UNITY_BUILD_CODE_AFTER_INCLUDE ------------------------------- - -Code snippet which is included verbatim by the :prop_tgt:`UNITY_BUILD` -feature just after every ``#include`` statement in the generated unity -source files. For example: - -.. code-block:: cmake - - set(after [[ - #if defined(NOMINMAX) - #undef NOMINMAX - #endif - ]]) - set_target_properties(myTarget PROPERTIES - UNITY_BUILD_CODE_AFTER_INCLUDE "${after}" - ) - -See also :prop_tgt:`UNITY_BUILD_CODE_BEFORE_INCLUDE`.
diff --git a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_BEFORE_INCLUDE.rst b/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_BEFORE_INCLUDE.rst deleted file mode 100644 index 7ed6fa1..0000000 --- a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_CODE_BEFORE_INCLUDE.rst +++ /dev/null
@@ -1,19 +0,0 @@ -UNITY_BUILD_CODE_BEFORE_INCLUDE -------------------------------- - -Code snippet which is included verbatim by the :prop_tgt:`UNITY_BUILD` -feature just before every ``#include`` statement in the generated unity -source files. For example: - -.. code-block:: cmake - - set(before [[ - #if !defined(NOMINMAX) - #define NOMINMAX - #endif - ]]) - set_target_properties(myTarget PROPERTIES - UNITY_BUILD_CODE_BEFORE_INCLUDE "${before}" - ) - -See also :prop_tgt:`UNITY_BUILD_CODE_AFTER_INCLUDE`.
diff --git a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_MODE.rst b/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_MODE.rst deleted file mode 100644 index 1ebab23..0000000 --- a/share/cmake-3.18/Help/prop_tgt/UNITY_BUILD_MODE.rst +++ /dev/null
@@ -1,58 +0,0 @@ -UNITY_BUILD_MODE ----------------- - -CMake provides different algorithms for selecting which sources are grouped -together into a *bucket*. Selection is decided by this property, -which has the following acceptable values: - -``BATCH`` - When in this mode CMake determines which files are grouped together. - The :prop_tgt:`UNITY_BUILD_BATCH_SIZE` property controls the upper limit on - how many sources can be combined per unity source file. - - Example usage: - - .. code-block:: cmake - - add_library(example_library - source1.cxx - source2.cxx - source3.cxx - source4.cxx) - - set_target_properties(example_library PROPERTIES - UNITY_BUILD_MODE BATCH - UNITY_BUILD_BATCH_SIZE 2 - ) - -``GROUP`` - When in this mode each target explicitly specifies how to group - source files. Each source file that has the same - :prop_sf:`UNITY_GROUP` value will be grouped together. Any sources - that don't have this property will be compiled individually. The - :prop_tgt:`UNITY_BUILD_BATCH_SIZE` property is ignored when using - this mode. - - Example usage: - - .. code-block:: cmake - - add_library(example_library - source1.cxx - source2.cxx - source3.cxx - source4.cxx) - - set_target_properties(example_library PROPERTIES - UNITY_BUILD_MODE GROUP - ) - - set_source_files_properties(source1.cxx source2.cxx source3.cxx - PROPERTIES UNITY_GROUP "bucket1" - ) - set_source_files_properties(source4.cxx - PROPERTIES UNITY_GROUP "bucket2" - ) - -If no explicit :prop_tgt:`UNITY_BUILD_MODE` has been specified, CMake will -default to ``BATCH``.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_CONFIGURATION_TYPE.rst b/share/cmake-3.18/Help/prop_tgt/VS_CONFIGURATION_TYPE.rst deleted file mode 100644 index 640bed5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_CONFIGURATION_TYPE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -VS_CONFIGURATION_TYPE ---------------------- - -Visual Studio project configuration type. - -Sets the ``ConfigurationType`` attribute for a generated Visual Studio project. -The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -If this property is set, it overrides the default setting that is based on the -target type (e.g. ``StaticLibrary``, ``Application``, ...). - -Supported on :ref:`Visual Studio Generators` for VS 2010 and higher.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND.rst b/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND.rst deleted file mode 100644 index ba5fd0a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND.rst +++ /dev/null
@@ -1,11 +0,0 @@ -VS_DEBUGGER_COMMAND -------------------- - -Sets the local debugger command for Visual Studio C++ targets. -The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -This is defined in ``<LocalDebuggerCommand>`` in the Visual Studio -project file. - -This property only works for Visual Studio 2010 and above; -it is ignored on other generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.rst b/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.rst deleted file mode 100644 index 06ef5d5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -VS_DEBUGGER_COMMAND_ARGUMENTS ------------------------------ - -Sets the local debugger command line arguments for Visual Studio C++ targets. -The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -This is defined in ``<LocalDebuggerCommandArguments>`` in the Visual Studio -project file. - -This property only works for Visual Studio 2010 and above; -it is ignored on other generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_ENVIRONMENT.rst b/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_ENVIRONMENT.rst deleted file mode 100644 index f55ac7b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_ENVIRONMENT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -VS_DEBUGGER_ENVIRONMENT ------------------------ - -Sets the local debugger environment for Visual Studio C++ targets. -The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -This is defined in ``<LocalDebuggerEnvironment>`` in the Visual Studio -project file. - -This property only works for Visual Studio 2010 and above; -it is ignored on other generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_WORKING_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_WORKING_DIRECTORY.rst deleted file mode 100644 index 008bbf6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DEBUGGER_WORKING_DIRECTORY.rst +++ /dev/null
@@ -1,11 +0,0 @@ -VS_DEBUGGER_WORKING_DIRECTORY ------------------------------ - -Sets the local debugger working directory for Visual Studio C++ targets. -The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -This is defined in ``<LocalDebuggerWorkingDirectory>`` in the Visual Studio -project file. - -This property only works for Visual Studio 2010 and above; -it is ignored on other generators.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.rst deleted file mode 100644 index 19d1620..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_DESKTOP_EXTENSIONS_VERSION ------------------------------ - -Visual Studio Windows 10 Desktop Extensions Version - -Specifies the version of the Desktop Extensions that should be included in the -target. For example ``10.0.10240.0``. If the value is not specified, the Desktop -Extensions will not be included. To use the same version of the extensions as -the Windows 10 SDK that is being used, you can use the -:variable:`CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION` variable.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.rst b/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.rst deleted file mode 100644 index 1bc361c..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_DOTNET_DOCUMENTATION_FILE ----------------------------- - -Visual Studio managed project .NET documentation output - -Sets the target XML documentation file output.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.rst b/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.rst deleted file mode 100644 index ab311ea..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.rst +++ /dev/null
@@ -1,14 +0,0 @@ -VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname> ------------------------------------------------ - -Defines an XML property ``<tagname>`` for a .NET reference -``<refname>``. - -Reference properties can be set for .NET references which are -defined by the target properties :prop_tgt:`VS_DOTNET_REFERENCES`, -:prop_tgt:`VS_DOTNET_REFERENCE_<refname>` -and also for project references to other C# targets which are -established by :command:`target_link_libraries()`. - -This property is only applicable to C# targets and Visual Studio -generators 2010 and later.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.rst b/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.rst deleted file mode 100644 index 7641ba5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.rst +++ /dev/null
@@ -1,7 +0,0 @@ -VS_DOTNET_REFERENCES_COPY_LOCAL -------------------------------- - -Sets the **Copy Local** property for all .NET hint references in the target - -Boolean property to enable/disable copying of .NET hint references to -output directory. The default is ``ON``.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCE_refname.rst b/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCE_refname.rst deleted file mode 100644 index 5814005..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DOTNET_REFERENCE_refname.rst +++ /dev/null
@@ -1,12 +0,0 @@ -VS_DOTNET_REFERENCE_<refname> ------------------------------ - -Visual Studio managed project .NET reference with name ``<refname>`` -and hint path. - -Adds one .NET reference to generated Visual Studio project. The -reference will have the name ``<refname>`` and will point to the -assembly given as value of the property. - -See also :prop_tgt:`VS_DOTNET_REFERENCES` and -:prop_tgt:`VS_DOTNET_REFERENCES_COPY_LOCAL`
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_DPI_AWARE.rst b/share/cmake-3.18/Help/prop_tgt/VS_DPI_AWARE.rst deleted file mode 100644 index 82640cc..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_DPI_AWARE.rst +++ /dev/null
@@ -1,14 +0,0 @@ -VS_DPI_AWARE ------------- - -Set the Manifest Tool -> Input and Output -> DPI Awareness in the Visual Studio -target project properties. - -Valid values are ``PerMonitor``, ``ON``, or ``OFF``. - -For example: - -.. code-block:: cmake - - add_executable(myproject myproject.cpp) - set_property(TARGET myproject PROPERTY VS_DPI_AWARE "PerMonitor")
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_IOT_EXTENSIONS_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/VS_IOT_EXTENSIONS_VERSION.rst deleted file mode 100644 index 27c8a3d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_IOT_EXTENSIONS_VERSION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_IOT_EXTENSIONS_VERSION -------------------------- - -Visual Studio Windows 10 IoT Extensions Version - -Specifies the version of the IoT Extensions that should be included in the -target. For example ``10.0.10240.0``. If the value is not specified, the IoT -Extensions will not be included. To use the same version of the extensions as -the Windows 10 SDK that is being used, you can use the -:variable:`CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION` variable.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_IOT_STARTUP_TASK.rst b/share/cmake-3.18/Help/prop_tgt/VS_IOT_STARTUP_TASK.rst deleted file mode 100644 index add50cb..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_IOT_STARTUP_TASK.rst +++ /dev/null
@@ -1,6 +0,0 @@ -VS_IOT_STARTUP_TASK -------------------- - -Visual Studio Windows 10 IoT Continuous Background Task - -Specifies that the target should be compiled as a Continuous Background Task library.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.rst b/share/cmake-3.18/Help/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.rst deleted file mode 100644 index 42fb8ad..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_JUST_MY_CODE_DEBUGGING -------------------------- - -Enable Just My Code with Visual Studio debugger. - -Supported on :ref:`Visual Studio Generators` for VS 2010 and higher, -:ref:`Makefile Generators` and the :generator:`Ninja` generators. - -This property is initialized by the :variable:`CMAKE_VS_JUST_MY_CODE_DEBUGGING` -variable if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.rst deleted file mode 100644 index be3c9a0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_MOBILE_EXTENSIONS_VERSION ----------------------------- - -Visual Studio Windows 10 Mobile Extensions Version - -Specifies the version of the Mobile Extensions that should be included in the -target. For example ``10.0.10240.0``. If the value is not specified, the Mobile -Extensions will not be included. To use the same version of the extensions as -the Windows 10 SDK that is being used, you can use the -:variable:`CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION` variable.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_NO_SOLUTION_DEPLOY.rst b/share/cmake-3.18/Help/prop_tgt/VS_NO_SOLUTION_DEPLOY.rst deleted file mode 100644 index ffcbde5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_NO_SOLUTION_DEPLOY.rst +++ /dev/null
@@ -1,46 +0,0 @@ -VS_NO_SOLUTION_DEPLOY ---------------------- - -Specify that the target should not be marked for deployment to a Windows CE -or Windows Phone device in the generated Visual Studio solution. - -Be default, all EXE and shared library (DLL) targets are marked to deploy to -the target device in the generated Visual Studio solution. - -Generator expressions are supported. - -There are reasons one might want to exclude a target / generated project from -deployment: - -- The library or executable may not be necessary in the primary deploy/debug - scenario, and excluding from deployment saves time in the - develop/download/debug cycle. -- There may be insufficient space on the target device to accommodate all of - the build products. -- Visual Studio 2013 requires a target device IP address be entered for each - target marked for deployment. For large numbers of targets, this can be - tedious. - NOTE: Visual Studio *will* deploy all project dependencies of a project - tagged for deployment to the IP address configured for that project even - if those dependencies are not tagged for deployment. - - -Example 1 -^^^^^^^^^ - -This shows setting the variable for the target foo. - -.. code-block:: cmake - - add_library(foo SHARED foo.cpp) - set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY ON) - -Example 2 -^^^^^^^^^ - -This shows setting the variable for the Release configuration only. - -.. code-block:: cmake - - add_library(foo SHARED foo.cpp) - set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY "$<CONFIG:Release>")
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_PACKAGE_REFERENCES.rst b/share/cmake-3.18/Help/prop_tgt/VS_PACKAGE_REFERENCES.rst deleted file mode 100644 index 5a0465b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_PACKAGE_REFERENCES.rst +++ /dev/null
@@ -1,13 +0,0 @@ -VS_PACKAGE_REFERENCES ---------------------- - -Visual Studio package references for nuget. - -Adds one or more semicolon-delimited package references to a generated -Visual Studio project. The version of the package will be -underscore delimited. For example, ``boost_1.7.0;nunit_3.12.*``. - -.. code-block:: cmake - - set_property(TARGET ${TARGET_NAME} PROPERTY - VS_PACKAGE_REFERENCES "boost_1.7.0")
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_PLATFORM_TOOLSET.rst b/share/cmake-3.18/Help/prop_tgt/VS_PLATFORM_TOOLSET.rst deleted file mode 100644 index f8f2e8e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_PLATFORM_TOOLSET.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_PLATFORM_TOOLSET -------------------- - -Overrides the platform toolset used to build a target. - -Only supported when the compiler used by the given toolset is the -same as the compiler used to build the whole source tree. - -This is especially useful to create driver projects with the toolsets -"WindowsUserModeDriver10.0" or "WindowsKernelModeDriver10.0".
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_PROJECT_IMPORT.rst b/share/cmake-3.18/Help/prop_tgt/VS_PROJECT_IMPORT.rst deleted file mode 100644 index 569c8ea..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_PROJECT_IMPORT.rst +++ /dev/null
@@ -1,8 +0,0 @@ -VS_PROJECT_IMPORT ------------------ - -Visual Studio managed project imports - -Adds to a generated Visual Studio project one or more semicolon-delimited paths -to .props files needed when building projects from some NuGet packages. -For example, ``my_packages_path/MyPackage.1.0.0/build/MyPackage.props``.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_SDK_REFERENCES.rst b/share/cmake-3.18/Help/prop_tgt/VS_SDK_REFERENCES.rst deleted file mode 100644 index 99987f5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_SDK_REFERENCES.rst +++ /dev/null
@@ -1,7 +0,0 @@ -VS_SDK_REFERENCES ------------------ - -Visual Studio project SDK references. -Specify a :ref:`semicolon-separated list <CMake Language Lists>` of SDK references -to be added to a generated Visual Studio project, e.g. -``Microsoft.AdMediatorWindows81, Version=1.0``.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_SOLUTION_DEPLOY.rst b/share/cmake-3.18/Help/prop_tgt/VS_SOLUTION_DEPLOY.rst deleted file mode 100644 index eef848f..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_SOLUTION_DEPLOY.rst +++ /dev/null
@@ -1,27 +0,0 @@ -VS_SOLUTION_DEPLOY ------------------- - -Specify that the target should be marked for deployment when not targeting -Windows CE, Windows Phone or a Windows Store application. - -If the target platform doesn't support deployment, this property won't have -any effect. - -:manual:`Generator expressions <cmake-generator-expressions(7)>` are supported. - -Examples -^^^^^^^^ - -Always deploy target ``foo``: - -.. code-block:: cmake - - add_executable(foo SHARED foo.cpp) - set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY ON) - -Deploy target ``foo`` for all configurations except ``Release``: - -.. code-block:: cmake - - add_executable(foo SHARED foo.cpp) - set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY "$<NOT:$<CONFIG:Release>>")
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_SOURCE_SETTINGS_tool.rst b/share/cmake-3.18/Help/prop_tgt/VS_SOURCE_SETTINGS_tool.rst deleted file mode 100644 index 738a912..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_SOURCE_SETTINGS_tool.rst +++ /dev/null
@@ -1,19 +0,0 @@ -VS_SOURCE_SETTINGS_<tool> -------------------------- - -Set any item metadata on all non-built files that use <tool>. - -Takes a list of ``Key=Value`` pairs. Tells the Visual Studio generator -to set ``Key`` to ``Value`` as item metadata on all non-built files -that use ``<tool>``. - -For example: - -.. code-block:: cmake - - set_property(TARGET main PROPERTY VS_SOURCE_SETTINGS_FXCompile "Key=Value" "Key2=Value2") - -will set ``Key`` to ``Value`` and ``Key2`` to ``Value2`` for all -non-built files that use ``FXCompile``. - -:manual:`Generator expressions <cmake-generator-expressions(7)>` are supported.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_USER_PROPS.rst b/share/cmake-3.18/Help/prop_tgt/VS_USER_PROPS.rst deleted file mode 100644 index 1be222b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_USER_PROPS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -VS_USER_PROPS -------------- - -Sets the user props file to be included in the visual studio -C++ project file. The standard path is -``$(UserRootDir)\\Microsoft.Cpp.$(Platform).user.props``, which is -in most cases the same as -``%LOCALAPPDATA%\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.Win32.user.props`` -or ``%LOCALAPPDATA%\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.x64.user.props``. - -The ``*.user.props`` files can be used for Visual Studio wide -configuration which is independent from cmake.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.rst b/share/cmake-3.18/Help/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.rst deleted file mode 100644 index 1ad7a71..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION --------------------------------------- - -Visual Studio Windows Target Platform Minimum Version - -For Windows 10. Specifies the minimum version of the OS that is being -targeted. For example ``10.0.10240.0``. If the value is not specified, the -value of :variable:`CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION` will be used on -WindowsStore projects otherwise the target platform minimum version will not -be specified for the project.
diff --git a/share/cmake-3.18/Help/prop_tgt/VS_WINRT_COMPONENT.rst b/share/cmake-3.18/Help/prop_tgt/VS_WINRT_COMPONENT.rst deleted file mode 100644 index e160bd6..0000000 --- a/share/cmake-3.18/Help/prop_tgt/VS_WINRT_COMPONENT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -VS_WINRT_COMPONENT ------------------- - -Mark a target as a Windows Runtime component for the Visual Studio generator. -Compile the target with ``C++/CX`` language extensions for Windows Runtime. -For ``SHARED`` and ``MODULE`` libraries, this also defines the -``_WINRT_DLL`` preprocessor macro. - -.. note:: - Currently this is implemented only by Visual Studio generators. - Support may be added to other generators in the future.
diff --git a/share/cmake-3.18/Help/prop_tgt/WIN32_EXECUTABLE.rst b/share/cmake-3.18/Help/prop_tgt/WIN32_EXECUTABLE.rst deleted file mode 100644 index 060d166..0000000 --- a/share/cmake-3.18/Help/prop_tgt/WIN32_EXECUTABLE.rst +++ /dev/null
@@ -1,13 +0,0 @@ -WIN32_EXECUTABLE ----------------- - -Build an executable with a WinMain entry point on windows. - -When this property is set to true the executable when linked on -Windows will be created with a WinMain() entry point instead of just -main(). This makes it a GUI executable instead of a console application. -See the :variable:`CMAKE_MFC_FLAG` variable documentation to -configure use of the Microsoft Foundation Classes (MFC) for WinMain -executables. This property is initialized by the value of the -:variable:`CMAKE_WIN32_EXECUTABLE` variable if it is set when -a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.rst b/share/cmake-3.18/Help/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.rst deleted file mode 100644 index 86711bf..0000000 --- a/share/cmake-3.18/Help/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.rst +++ /dev/null
@@ -1,26 +0,0 @@ -WINDOWS_EXPORT_ALL_SYMBOLS --------------------------- - -This property is implemented only for MS-compatible tools on Windows. - -Enable this boolean property to automatically create a module definition -(``.def``) file with all global symbols found in the input ``.obj`` files -for a ``SHARED`` library (or executable with :prop_tgt:`ENABLE_EXPORTS`) -on Windows. The module definition file will be passed to the linker -causing all symbols to be exported from the ``.dll``. -For global *data* symbols, ``__declspec(dllimport)`` must still be used when -compiling against the code in the ``.dll``. All other function symbols will -be automatically exported and imported by callers. This simplifies porting -projects to Windows by reducing the need for explicit ``dllexport`` markup, -even in ``C++`` classes. - -When this property is enabled, zero or more ``.def`` files may also be -specified as source files of the target. The exports named by these files -will be merged with those detected from the object files to generate a -single module definition file to be passed to the linker. This can be -used to export symbols from a ``.dll`` that are not in any of its object -files but are added by the linker from dependencies (e.g. ``msvcrt.lib``). - -This property is initialized by the value of -the :variable:`CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS` variable if it is set -when a target is created.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_ATTRIBUTE_an-attribute.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_ATTRIBUTE_an-attribute.rst deleted file mode 100644 index 71858c5..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_ATTRIBUTE_an-attribute.rst +++ /dev/null
@@ -1,16 +0,0 @@ -XCODE_ATTRIBUTE_<an-attribute> ------------------------------- - -Set Xcode target attributes directly. - -Tell the :generator:`Xcode` generator to set '<an-attribute>' to a given -value in the generated Xcode project. Ignored on other generators. - -See the :variable:`CMAKE_XCODE_ATTRIBUTE_<an-attribute>` variable -to set attributes on all targets in a directory tree. - -Contents of ``XCODE_ATTRIBUTE_<an-attribute>`` may use -"generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available -expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_EXPLICIT_FILE_TYPE.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_EXPLICIT_FILE_TYPE.rst deleted file mode 100644 index dc92902..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_EXPLICIT_FILE_TYPE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -XCODE_EXPLICIT_FILE_TYPE ------------------------- - -Set the Xcode ``explicitFileType`` attribute on its reference to a -target. CMake computes a default based on target type but -can be told explicitly with this property. - -See also :prop_tgt:`XCODE_PRODUCT_TYPE`.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_GENERATE_SCHEME.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_GENERATE_SCHEME.rst deleted file mode 100644 index c32b4de..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_GENERATE_SCHEME.rst +++ /dev/null
@@ -1,41 +0,0 @@ -XCODE_GENERATE_SCHEME ---------------------- - -If enabled, the :generator:`Xcode` generator will generate schema files. These -are useful to invoke analyze, archive, build-for-testing and test -actions from the command line. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_GENERATE_SCHEME` if it is set when a target -is created. - -The following target properties overwrite the default of the -corresponding settings on the "Diagnostic" tab for each schema file. -Each of those is initialized by the respective ``CMAKE_`` variable -at target creation time. - -- :prop_tgt:`XCODE_SCHEME_ADDRESS_SANITIZER` -- :prop_tgt:`XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN` -- :prop_tgt:`XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER` -- :prop_tgt:`XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS` -- :prop_tgt:`XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE` -- :prop_tgt:`XCODE_SCHEME_GUARD_MALLOC` -- :prop_tgt:`XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP` -- :prop_tgt:`XCODE_SCHEME_MALLOC_GUARD_EDGES` -- :prop_tgt:`XCODE_SCHEME_MALLOC_SCRIBBLE` -- :prop_tgt:`XCODE_SCHEME_MALLOC_STACK` -- :prop_tgt:`XCODE_SCHEME_THREAD_SANITIZER` -- :prop_tgt:`XCODE_SCHEME_THREAD_SANITIZER_STOP` -- :prop_tgt:`XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER` -- :prop_tgt:`XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP` -- :prop_tgt:`XCODE_SCHEME_ZOMBIE_OBJECTS` - -The following target properties will be applied on the -"Info", "Arguments", and "Options" tab: - -- :prop_tgt:`XCODE_SCHEME_ARGUMENTS` -- :prop_tgt:`XCODE_SCHEME_DEBUG_AS_ROOT` -- :prop_tgt:`XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING` -- :prop_tgt:`XCODE_SCHEME_ENVIRONMENT` -- :prop_tgt:`XCODE_SCHEME_EXECUTABLE` -- :prop_tgt:`XCODE_SCHEME_WORKING_DIRECTORY`
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_PRODUCT_TYPE.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_PRODUCT_TYPE.rst deleted file mode 100644 index f4ef5c0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_PRODUCT_TYPE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -XCODE_PRODUCT_TYPE ------------------- - -Set the Xcode ``productType`` attribute on its reference to a -target. CMake computes a default based on target type but -can be told explicitly with this property. - -See also :prop_tgt:`XCODE_EXPLICIT_FILE_TYPE`.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.rst deleted file mode 100644 index cc9bac2..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_ADDRESS_SANITIZER ------------------------------- - -Whether to enable ``Address Sanitizer`` in the Diagnostics -section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst deleted file mode 100644 index 37a043a..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN ------------------------------------------------ - -Whether to enable ``Detect use of stack after return`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN` -if it is set when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ARGUMENTS.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ARGUMENTS.rst deleted file mode 100644 index 1f228e3..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ARGUMENTS.rst +++ /dev/null
@@ -1,10 +0,0 @@ -XCODE_SCHEME_ARGUMENTS ----------------------- - -Specify command line arguments that should be added to the Arguments -section of the generated Xcode scheme. - -If set to a list of arguments those will be added to the scheme. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.rst deleted file mode 100644 index 5407e80..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.rst +++ /dev/null
@@ -1,7 +0,0 @@ -XCODE_SCHEME_DEBUG_AS_ROOT --------------------------- - -Whether to debug the target as 'root'. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst deleted file mode 100644 index 9afeedd..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst +++ /dev/null
@@ -1,13 +0,0 @@ -XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING --------------------------------------- - -Whether to enable -``Allow debugging when using document Versions Browser`` -in the Options section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING` -if it is set when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst deleted file mode 100644 index 1a6fcfd..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER ----------------------------------------- - -Whether to disable the ``Main Thread Checker`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER` -if it is set when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst deleted file mode 100644 index 9224022..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS ----------------------------------- - -Whether to enable ``Dynamic Library Loads`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst deleted file mode 100644 index 203c803..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE -------------------------------------- - -Whether to enable ``Dynamic Linker API usage`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ENVIRONMENT.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ENVIRONMENT.rst deleted file mode 100644 index c6d875e..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ENVIRONMENT.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_ENVIRONMENT ------------------------- - -Specify environment variables that should be added to the Arguments -section of the generated Xcode scheme. - -If set to a list of environment variables and values of the form -``MYVAR=value`` those environment variables will be added to the -scheme. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_EXECUTABLE.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_EXECUTABLE.rst deleted file mode 100644 index 104841b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_EXECUTABLE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -XCODE_SCHEME_EXECUTABLE ------------------------ - -Specify path to executable in the Info section of the generated -Xcode scheme. If not set the schema generator will select the -current target if it is actually executable. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_GUARD_MALLOC.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_GUARD_MALLOC.rst deleted file mode 100644 index c4e83da..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_GUARD_MALLOC.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_GUARD_MALLOC ------------------------------- - -Whether to enable ``Guard Malloc`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_GUARD_MALLOC` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst deleted file mode 100644 index 73992c3..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst +++ /dev/null
@@ -1,13 +0,0 @@ -XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP -------------------------------------- - -Whether to enable the ``Main Thread Checker`` option -``Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.rst deleted file mode 100644 index ca761c0..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_MALLOC_GUARD_EDGES -------------------------------- - -Whether to enable ``Malloc Guard Edges`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.rst deleted file mode 100644 index c5ddb95..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_MALLOC_SCRIBBLE ------------------------------- - -Whether to enable ``Malloc Scribble`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_STACK.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_STACK.rst deleted file mode 100644 index 170f33d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_MALLOC_STACK.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_MALLOC_STACK -------------------------- - -Whether to enable ``Malloc Stack`` in the Diagnostics -section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_MALLOC_STACK` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.rst deleted file mode 100644 index bb70141..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_THREAD_SANITIZER ------------------------------ - -Whether to enable ``Thread Sanitizer`` in the Diagnostics -section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_THREAD_SANITIZER` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.rst deleted file mode 100644 index 5deadb1..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_THREAD_SANITIZER_STOP ----------------------------------- - -Whether to enable ``Thread Sanitizer - Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst deleted file mode 100644 index 0cd823d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER ------------------------------------------- - -Whether to enable ``Undefined Behavior Sanitizer`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER` -if it is set when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst deleted file mode 100644 index d1a9bca..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst +++ /dev/null
@@ -1,13 +0,0 @@ -XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP ------------------------------------------------ - -Whether to enable ``Undefined Behavior Sanitizer`` option -``Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP` -if it is set when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.rst deleted file mode 100644 index f538f1d..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.rst +++ /dev/null
@@ -1,13 +0,0 @@ -XCODE_SCHEME_WORKING_DIRECTORY ------------------------------- - -Specify the ``Working Directory`` of the *Run* and *Profile* -actions in the generated Xcode scheme. In case the value contains -generator expressions those are evaluated. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_WORKING_DIRECTORY` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.rst b/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.rst deleted file mode 100644 index 6e70e8b..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -XCODE_SCHEME_ZOMBIE_OBJECTS ------------------------------- - -Whether to enable ``Zombie Objects`` -in the Diagnostics section of the generated Xcode scheme. - -This property is initialized by the value of the variable -:variable:`CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS` if it is set -when a target is created. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/prop_tgt/XCTEST.rst b/share/cmake-3.18/Help/prop_tgt/XCTEST.rst deleted file mode 100644 index eb47e60..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XCTEST.rst +++ /dev/null
@@ -1,13 +0,0 @@ -XCTEST ------- - -This target is a XCTest CFBundle on the Mac. - -This property will usually get set via the :command:`xctest_add_bundle` -macro in :module:`FindXCTest` module. - -If a module library target has this property set to true it will be -built as a CFBundle when built on the Mac. It will have the directory -structure required for a CFBundle. - -This property depends on :prop_tgt:`BUNDLE` to be effective.
diff --git a/share/cmake-3.18/Help/prop_tgt/XXX_OUTPUT_DIRECTORY.txt b/share/cmake-3.18/Help/prop_tgt/XXX_OUTPUT_DIRECTORY.txt deleted file mode 100644 index 3ae5448..0000000 --- a/share/cmake-3.18/Help/prop_tgt/XXX_OUTPUT_DIRECTORY.txt +++ /dev/null
@@ -1,11 +0,0 @@ -Output directory in which to build |XXX| target files. - -This property specifies the directory into which |xxx| target files -should be built. The property value may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. -Multi-configuration generators (VS, Xcode) append a per-configuration -subdirectory to the specified directory unless a generator expression -is used. - -This property is initialized by the value of the variable -|CMAKE_XXX_OUTPUT_DIRECTORY| if it is set when a target is created.
diff --git a/share/cmake-3.18/Help/release/3.1.rst b/share/cmake-3.18/Help/release/3.1.rst deleted file mode 100644 index 8bea28f..0000000 --- a/share/cmake-3.18/Help/release/3.1.rst +++ /dev/null
@@ -1,425 +0,0 @@ -CMake 3.1 Release Notes -*********************** - -.. only:: html - - .. contents:: - -Changes made since CMake 3.0 include the following. - -Documentation Changes -===================== - -* A new :manual:`cmake-compile-features(7)` manual was added. - -New Features -============ - -Generators ----------- - -* The :generator:`Visual Studio 14 2015` generator was added. - -Windows Phone and Windows Store -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -* Generators for Visual Studio 11 (2012) and above learned to generate - projects for Windows Phone and Windows Store. One may set the - :variable:`CMAKE_SYSTEM_NAME` variable to ``WindowsPhone`` - or ``WindowsStore`` on the :manual:`cmake(1)` command-line - or in a :variable:`CMAKE_TOOLCHAIN_FILE` to activate these platforms. - Also set :variable:`CMAKE_SYSTEM_VERSION` to ``8.0`` or ``8.1`` to - specify the version of Windows to be targeted. - -NVIDIA Nsight Tegra -^^^^^^^^^^^^^^^^^^^ - -* Generators for Visual Studio 10 (2010) and above learned to generate - projects for NVIDIA Nsight Tegra Visual Studio Edition. One may set - the :variable:`CMAKE_SYSTEM_NAME` variable to ``Android`` on the - :manual:`cmake(1)` command-line or in a :variable:`CMAKE_TOOLCHAIN_FILE` - to activate this platform. - -Syntax ------- - -* The :manual:`cmake-language(7)` syntax for :ref:`Variable References` and - :ref:`Escape Sequences` was simplified in order to allow a much faster - implementation. See policy :policy:`CMP0053`. - -* The :command:`if` command no longer automatically dereferences - variables named in quoted or bracket arguments. See policy - :policy:`CMP0054`. - -Commands --------- - -* The :command:`add_custom_command` command learned to interpret - :manual:`cmake-generator-expressions(7)` in arguments to ``DEPENDS``. - -* The :command:`export(PACKAGE)` command learned to check the - :variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` variable to skip - exporting the package. - -* The :command:`file(STRINGS)` command gained a new ``ENCODING`` - option to enable extraction of ``UTF-8`` strings. - -* The :command:`find_package` command learned to check the - :variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` and - :variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` - variables to skip searching the package registries. - -* The :command:`get_property` command learned a new ``INSTALL`` scope - for properties. - -* The :command:`install` command learned a ``MESSAGE_NEVER`` option - to avoid output during installation. - -* The :command:`set_property` command learned a new ``INSTALL`` scope - for properties. - -* The :command:`string` command learned a new ``GENEX_STRIP`` subcommand - which removes - :manual:`generator expression <cmake-generator-expressions(7)>`. - -* The :command:`string` command learned a new ``UUID`` subcommand - to generate a univerally unique identifier. - -* New :command:`target_compile_features` command allows populating the - :prop_tgt:`COMPILE_FEATURES` target property, just like any other - build variable. - -* The :command:`target_sources` command was added to add to the - :prop_tgt:`SOURCES` target property. - -Variables ---------- - -* The Visual Studio generators for versions 8 (2005) and above - learned to read the target platform name from a new - :variable:`CMAKE_GENERATOR_PLATFORM` variable when it is - not specified as part of the generator name. The platform - name may be specified on the :manual:`cmake(1)` command line - with the ``-A`` option, e.g. ``-G "Visual Studio 12 2013" -A x64``. - -* The :variable:`CMAKE_GENERATOR_TOOLSET` variable may now be - initialized in a toolchain file specified by the - :variable:`CMAKE_TOOLCHAIN_FILE` variable. This is useful - when cross-compiling with the Xcode or Visual Studio - generators. - -* The :variable:`CMAKE_INSTALL_MESSAGE` variable was introduced to - optionally reduce output installation. - -Properties ----------- - -* New :prop_tgt:`CXX_STANDARD` and :prop_tgt:`CXX_EXTENSIONS` target - properties may specify values which CMake uses to compute required - compile options such as ``-std=c++11`` or ``-std=gnu++11``. The - :variable:`CMAKE_CXX_STANDARD` and :variable:`CMAKE_CXX_EXTENSIONS` - variables may be set to initialize the target properties. - -* New :prop_tgt:`C_STANDARD` and :prop_tgt:`C_EXTENSIONS` target - properties may specify values which CMake uses to compute required - compile options such as ``-std=c11`` or ``-std=gnu11``. The - :variable:`CMAKE_C_STANDARD` and :variable:`CMAKE_C_EXTENSIONS` - variables may be set to initialize the target properties. - -* New :prop_tgt:`COMPILE_FEATURES` target property may contain a list - of features required to compile a target. CMake uses this - information to ensure that the compiler in use is capable of building - the target, and to add any necessary compile flags to support language - features. - -* New :prop_tgt:`COMPILE_PDB_NAME` and - :prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY` target properties - were introduced to specify the MSVC compiler program database - file location (``cl /Fd``). This complements the existing - :prop_tgt:`PDB_NAME` and :prop_tgt:`PDB_OUTPUT_DIRECTORY` - target properties that specify the linker program database - file location (``link /pdb``). - -* The :prop_tgt:`INTERFACE_LINK_LIBRARIES` target property now supports - a ``$<LINK_ONLY:...>`` - :manual:`generator expression <cmake-generator-expressions(7)>`. - -* A new :prop_tgt:`INTERFACE_SOURCES` target property was introduced. This is - consumed by dependent targets, which compile and link the listed sources. - -* The :prop_tgt:`SOURCES` target property now contains - :manual:`generator expression <cmake-generator-expressions(7)>` - such as ``TARGET_OBJECTS`` when read at configure time, if - policy :policy:`CMP0051` is ``NEW``. - -* The :prop_tgt:`SOURCES` target property now generally supports - :manual:`generator expression <cmake-generator-expressions(7)>`. The - generator expressions may be used in the :command:`add_library` and - :command:`add_executable` commands. - -* It is now possible to write and append to the :prop_tgt:`SOURCES` target - property. The :variable:`CMAKE_DEBUG_TARGET_PROPERTIES` variable may be - used to trace the origin of sources. - -* A :prop_sf:`VS_DEPLOYMENT_CONTENT` source file property was added - to tell the Visual Studio generators to mark content for deployment - in Windows Phone and Windows Store projects. - -* A :prop_sf:`VS_DEPLOYMENT_LOCATION` source file property was added - to tell the Visual Studio generators the relative location of content - marked for deployment in Windows Phone and Windows Store projects. - -* The :prop_tgt:`VS_WINRT_COMPONENT` target property was created to - tell Visual Studio generators to compile a shared library as a - Windows Runtime (WinRT) component. - -* The :generator:`Xcode` generator learned to check source - file properties :prop_sf:`XCODE_EXPLICIT_FILE_TYPE` and - :prop_sf:`XCODE_LAST_KNOWN_FILE_TYPE` for a custom Xcode - file reference type. - -Modules -------- - -* The :module:`BundleUtilities` module learned to resolve and replace - ``@rpath`` placeholders on OS X to correctly bundle applications - using them. - -* The :module:`CMakePackageConfigHelpers` module - :command:`configure_package_config_file` command learned a new - ``INSTALL_PREFIX`` option to generate package configuration files - meant for a prefix other than :variable:`CMAKE_INSTALL_PREFIX`. - -* The :module:`CheckFortranSourceCompiles` module was added to - provide a ``CHECK_Fortran_SOURCE_COMPILES`` macro. - -* The :module:`ExternalData` module learned to tolerate a ``DATA{}`` - reference to a missing source file with a warning instead of - rejecting it with an error. This helps developers write new - ``DATA{}`` references to test reference outputs that have not - yet been created. - -* The :module:`ExternalProject` module learned to support lzma-compressed - source tarballs with ``.7z``, ``.tar.xz``, and ``.txz`` extensions. - -* The :module:`ExternalProject` module ``ExternalProject_Add`` command - learned a new ``BUILD_ALWAYS`` option to cause the external project - build step to run every time the host project is built. - -* The :module:`ExternalProject` module ``ExternalProject_Add`` command - learned a new ``EXCLUDE_FROM_ALL`` option to cause the external - project target to have the :prop_tgt:`EXCLUDE_FROM_ALL` target - property set. - -* The :module:`ExternalProject` module ``ExternalProject_Add_Step`` command - learned a new ``EXCLUDE_FROM_MAIN`` option to cause the step to not be - a direct dependency of the main external project target. - -* The :module:`ExternalProject` module ``ExternalProject_Add`` command - learned a new ``DOWNLOAD_NO_PROGRESS`` option to disable progress - output while downloading the source tarball. - -* The :module:`FeatureSummary` module ``feature_summary`` API - learned to accept multiple values for the ``WHAT`` option and - combine them appropriately. - -* The :module:`FindCUDA` module learned to support ``fatbin`` and ``cubin`` - modules. - -* The :module:`FindGTest` module ``gtest_add_tests`` macro learned - a new ``AUTO`` option to automatically read the :prop_tgt:`SOURCES` - target property of the test executable and scan the source files - for tests to be added. - -* The :module:`FindGLEW` module now provides imported targets. - -* The :module:`FindGLUT` module now provides imported targets. - -* The :module:`FindHg` module gained a new ``Hg_WC_INFO`` macro to - help run ``hg`` to extract information about a Mercurial work copy. - -* The :module:`FindOpenCL` module was introduced. - -* The :module:`FindOpenMP` module learned to support Fortran. - -* The :module:`FindPkgConfig` module learned to use the ``PKG_CONFIG`` - environment variable value as the ``pkg-config`` executable, if set. - -* The :module:`FindXercesC` module was introduced. - -* The :module:`FindZLIB` module now provides imported targets. - -* The :module:`GenerateExportHeader` module ``generate_export_header`` - function learned to allow use with :ref:`Object Libraries`. - -* The :module:`InstallRequiredSystemLibraries` module gained a new - ``CMAKE_INSTALL_OPENMP_LIBRARIES`` option to install MSVC OpenMP - runtime libraries. - -* The :module:`UseSWIG` module learned to detect the module name - from ``.i`` source files if possible to avoid the need to set - the ``SWIG_MODULE_NAME`` source file property explicitly. - -* The :module:`WriteCompilerDetectionHeader` module was added to allow - creation of a portable header file for compiler optional feature detection. - -Generator Expressions ---------------------- - -* New ``COMPILE_FEATURES`` - :manual:`generator expression <cmake-generator-expressions(7)>` allows - setting build properties based on available compiler features. - -CTest ------ - -* The :command:`ctest_coverage` command learned to read variable - ``CTEST_COVERAGE_EXTRA_FLAGS`` to set ``CoverageExtraFlags``. - -* The :command:`ctest_coverage` command learned to support - Intel coverage files with the ``codecov`` tool. - -* The :command:`ctest_memcheck` command learned to support sanitizer - modes, including ``AddressSanitizer``, ``MemorySanitizer``, - ``ThreadSanitizer``, and ``UndefinedBehaviorSanitizer``. - Options may be set using the new - :variable:`CTEST_MEMORYCHECK_SANITIZER_OPTIONS` variable. - -CPack ------ - -* :manual:`cpack(1)` gained an ``IFW`` generator to package using - Qt Framework Installer tools. See the :cpack_gen:`CPack IFW Generator`. - -* :manual:`cpack(1)` gained ``7Z`` and ``TXZ`` generators supporting - lzma-compressed archives. - -* The :cpack_gen:`CPack DEB Generator` learned a new - :variable:`CPACK_DEBIAN_COMPRESSION_TYPE` variable to set the - tarball compression type. - -* The :cpack_gen:`CPack WIX Generator` learned to support - a :prop_inst:`CPACK_WIX_ACL` installed file property to - specify an Access Control List. - -Other ------ - -* The :manual:`cmake(1)` ``-E`` option learned a new ``env`` command. - -* The :manual:`cmake(1)` ``-E tar`` command learned to support - lzma-compressed files. - -* :ref:`Object Libraries` may now have extra sources that do not - compile to object files so long as they would not affect linking - of a normal library (e.g. ``.dat`` is okay but not ``.def``). - -* Visual Studio generators for VS 8 and later learned to support - the ``ASM_MASM`` language. - -* The Visual Studio generators learned to treat ``.hlsl`` source - files as High Level Shading Language sources (using ``FXCompile`` - in ``.vcxproj`` files). Source file properties - :prop_sf:`VS_SHADER_TYPE`, :prop_sf:`VS_SHADER_MODEL`, and - :prop_sf:`VS_SHADER_ENTRYPOINT` were added added to specify the - shader type, model, and entry point name. - -New Diagnostics -=============== - -* Policy :policy:`CMP0052` introduced to control directories in the - :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` of exported targets. - -Deprecated and Removed Features -=============================== - -* In CMake 3.0 the :command:`target_link_libraries` command - accidentally began allowing unquoted arguments to use - :manual:`generator expressions <cmake-generator-expressions(7)>` - containing a (``;`` separated) list within them. For example:: - - set(libs B C) - target_link_libraries(A PUBLIC $<BUILD_INTERFACE:${libs}>) - - This is equivalent to writing:: - - target_link_libraries(A PUBLIC $<BUILD_INTERFACE:B C>) - - and was never intended to work. It did not work in CMake 2.8.12. - Such generator expressions should be in quoted arguments:: - - set(libs B C) - target_link_libraries(A PUBLIC "$<BUILD_INTERFACE:${libs}>") - - CMake 3.1 again requires the quotes for this to work correctly. - -* Prior to CMake 3.1 the Makefile generators did not escape ``#`` - correctly inside make variable assignments used in generated - makefiles, causing them to be treated as comments. This made - code like:: - - add_compile_options(-Wno-#pragma-messages) - - not work in Makefile generators, but work in other generators. - Now it is escaped correctly, making the behavior consistent - across generators. However, some projects may have tried to - workaround the original bug with code like:: - - set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-\\#pragma-messages") - - This added the needed escape for Makefile generators but also - caused other generators to pass ``-Wno-\#pragma-messages`` to - the shell, which would work only in POSIX shells. - Unfortunately the escaping fix could not be made in a compatible - way so this platform- and generator-specific workaround no - longer works. Project code may test the :variable:`CMAKE_VERSION` - variable value to make the workaround version-specific too. - -* Callbacks established by the :command:`variable_watch` command will no - longer receive the ``ALLOWED_UNKNOWN_READ_ACCESS`` access type when - the undocumented ``CMAKE_ALLOW_UNKNOWN_VARIABLE_READ_ACCESS`` variable is - set. Uninitialized variable accesses will always be reported as - ``UNKNOWN_READ_ACCESS``. - -* The :module:`CMakeDetermineVSServicePack` module now warns that - it is deprecated and should not longer be used. Use the - :variable:`CMAKE_<LANG>_COMPILER_VERSION` variable instead. - -* The :module:`FindITK` module has been removed altogether. - It was a thin-wrapper around ``find_package(ITK ... NO_MODULE)``. - This produces much clearer error messages when ITK is not found. - -* The :module:`FindVTK` module has been removed altogether. - It was a thin-wrapper around ``find_package(VTK ... NO_MODULE)``. - This produces much clearer error messages when VTK is not found. - - The module also provided compatibility support for finding VTK 4.0. - This capability has been dropped. - -Other Changes -============= - -* The :manual:`cmake-gui(1)` learned to capture output from child - processes started by the :command:`execute_process` command - and display it in the output window. - -* The :manual:`cmake-language(7)` internal implementation of generator - expression and list expansion parsers have been optimized and shows - non-trivial speedup on large projects. - -* The Makefile generators learned to use response files with GNU tools - on Windows to pass library directories and names to the linker. - -* When generating linker command-lines, CMake now avoids repeating - items corresponding to SHARED library targets. - -* Support for the Open Watcom compiler has been overhauled. - The :variable:`CMAKE_<LANG>_COMPILER_ID` is now ``OpenWatcom``, - and the :variable:`CMAKE_<LANG>_COMPILER_VERSION` now uses - the Open Watcom external version numbering. The external - version numbers are lower than the internal version number - by 11. - -* The ``cmake-mode.el`` major Emacs editing mode no longer - treats ``_`` as part of words, making it more consistent - with other major modes.
diff --git a/share/cmake-3.18/Help/release/3.15.rst b/share/cmake-3.18/Help/release/3.15.rst deleted file mode 100644 index e68e7d3..0000000 --- a/share/cmake-3.18/Help/release/3.15.rst +++ /dev/null
@@ -1,396 +0,0 @@ -CMake 3.15 Release Notes -************************ - -.. only:: html - - .. contents:: - -Changes made since CMake 3.14 include the following. - -New Features -============ - -Generators ----------- - -* The :generator:`Xcode` generator now supports per-target schemes. - See the :variable:`CMAKE_XCODE_GENERATE_SCHEME` variable and - :prop_tgt:`XCODE_GENERATE_SCHEME` target property. - -* The :generator:`Green Hills MULTI` generator has been updated: - - * It now supports the :command:`add_custom_command` and - :command:`add_custom_target` commands. - - * It is now available on Linux. - -Languages ---------- - -* Preliminary support for the ``Swift`` language was added to the - :generator:`Ninja` generator: - - * Use the :envvar:`SWIFTC` environment variable to specify a compiler. - - * The :prop_tgt:`Swift_DEPENDENCIES_FILE` target property and - :prop_sf:`Swift_DEPENDENCIES_FILE` source file property were added - to customize dependency files. - - * The :prop_tgt:`Swift_MODULE_NAME` target property was added to - customize the Swift module name. - - * The :prop_sf:`Swift_DIAGNOSTICS_FILE` source property was added to - indicate where to write the serialised Swift diagnostics. - - The Swift support is experimental, not considered stable, and may change - in future releases of CMake. - -Compilers ---------- - -* The ``Clang`` compiler variant on Windows that targets the MSVC ABI - but has a GNU-like command line is now supported. - -* Support for the Clang-based ARM compiler was added with compiler id - ``ARMClang``. - -* Support was added for the IAR compiler architectures Renesas RX, - RL78, RH850 and Texas Instruments MSP430. - -* Support was added for the IAR compilers built for Linux (IAR BuildLx). - -Command-Line ------------- - -* The :envvar:`CMAKE_GENERATOR` environment variable was added - to specify a default generator to use when :manual:`cmake(1)` is - run without a ``-G`` option. Additionally, environment variables - :envvar:`CMAKE_GENERATOR_PLATFORM`, :envvar:`CMAKE_GENERATOR_TOOLSET`, - and :envvar:`CMAKE_GENERATOR_INSTANCE` were created to configure - the generator. - -* The :manual:`cmake(1)` ``--build`` tool ``--target`` parameter gained support - for multiple targets, e.g. ``cmake --build . --target Library1 Library2``. - It now also has a short form ``-t`` alias, e.g. - ``cmake --build . -t Library1 Library2``. - -* The :manual:`cmake(1)` command gained a new ``--install`` option. - This may be used after building a project to run installation without - using the generated build system or the native build tool. - -* The :manual:`cmake(1)` command learned a new CLI option ``--loglevel``. - -* The :manual:`cmake(1)` ``-E remove_directory`` command-line tool learned - to support removing multiple directories. - -* The :manual:`cmake(1)` ``-E tar`` tool has been improved: - - * It now continues adding files to an archive even if some of the files - are not readable. This behavior is more consistent with the - classic ``tar`` tool. - - * It now parses all flags, and if an invalid flag was provided, a - warning is issued. - - * It now displays an error if no action flag was specified, along with a - list of possible actions: ``t`` (list), ``c`` (create) or ``x`` (extract). - - * It now supports extracting (``-x``) or listing (``-t``) only specific - files or directories. - - * It now supports Zstandard compression with a ``--zstd`` option. - Zstandard was designed to give a compression ratio comparable to that - of the DEFLATE (zip) algorithm, but faster, especially for decompression. - -Commands --------- - -* The :command:`add_custom_command` and :command:`add_custom_target` commands - gained a new ``JOB_POOL`` option that works with the :generator:`Ninja` - generator to set the pool variable on the build statement. - -* The :command:`add_library` command ``ALIAS`` option learned to support - import libraries of the ``UNKNOWN`` type. - -* The :command:`cmake_parse_arguments` command gained an additional - ``<prefix>_KEYWORDS_MISSING_VALUES`` output variable to report - keyword arguments that were given by the caller with no values. - -* The :command:`execute_process` command gained a ``COMMAND_ECHO`` option - and supporting :variable:`CMAKE_EXECUTE_PROCESS_COMMAND_ECHO` variable - to enable echoing of the command-line string before execution. - -* The :command:`file(INSTALL)` command learned a new argument, - ``FOLLOW_SYMLINK_CHAIN``, which can be used to recursively resolve and - install symlinks. - -* :command:`list` learned new sub-commands: - ``PREPEND``, ``POP_FRONT`` and ``POP_BACK``. - -* The :command:`message` command learned new types: - ``NOTICE``, ``VERBOSE``, ``DEBUG`` and ``TRACE``. - -* The :command:`string` learned a new sub-command ``REPEAT``. - -Variables ---------- - -* The :variable:`CMAKE_CROSSCOMPILING_EMULATOR` variable and corresponding - :prop_tgt:`CROSSCOMPILING_EMULATOR` target property learned to support - arguments to the emulator. - -* The :variable:`CMAKE_FIND_PACKAGE_PREFER_CONFIG` variable was added to tell - :command:`find_package` calls to look for a package configuration - file first even if a find module is available. - -* The :variable:`CMAKE_FRAMEWORK` variable was added to initialize the - :prop_tgt:`FRAMEWORK` property on all targets. - -* The :variable:`CMAKE_VS_JUST_MY_CODE_DEBUGGING` variable and - :prop_tgt:`VS_JUST_MY_CODE_DEBUGGING` target property were added to - enable the Just My Code feature of the Visual Studio Debugger when - compiling with MSVC cl 19.05 and higher. - -* The :variable:`CMAKE_MSVC_RUNTIME_LIBRARY` variable and - :prop_tgt:`MSVC_RUNTIME_LIBRARY` target property were introduced to - select the runtime library used by compilers targeting the MSVC ABI. - See policy :policy:`CMP0091`. - -* The :variable:`CMAKE_PROJECT_INCLUDE` and - :variable:`CMAKE_PROJECT_INCLUDE_BEFORE` variables were added to allow - injection of custom code at the sites of :command:`project` calls - without knowing the project name a priori. - -Properties ----------- - -* The :prop_tgt:`ADDITIONAL_CLEAN_FILES` target property and - :prop_dir:`ADDITIONAL_CLEAN_FILES` directory property were added. - They allow to register additional files that should be removed during - the clean stage. - -* The :prop_tgt:`PUBLIC_HEADER` and :prop_tgt:`PRIVATE_HEADER` properties - may now be set on :ref:`Interface Libraries`. The headers specified by those - properties can be installed using the :command:`install(TARGETS)` command by - passing the ``PUBLIC_HEADER`` and ``PRIVATE_HEADER`` arguments respectively. - -* The :prop_tgt:`VS_PACKAGE_REFERENCES` target property was added to - tell :ref:`Visual Studio Generators` to add references to ``nuget`` - packages. - -* The :prop_tgt:`VS_PROJECT_IMPORT` target property was added to allow - managed Visual Studio project files to import external ``.props`` files. - -* The :prop_tgt:`VS_NO_SOLUTION_DEPLOY` target property was added to - tell :ref:`Visual Studio Generators` whether to deploy an artifact - to the WinCE or Windows Phone target device. - -Modules -------- - -* The :module:`FindBoost` module was reworked to expose a more consistent - user experience between its "Config" and "Module" modes and with other - find modules in general. - - * A new imported target ``Boost::headers`` is now defined (same - as ``Boost::boost``). - - * New output variables ``Boost_VERSION_MACRO``, - ``Boost_VERSION_MAJOR``, ``Boost_VERSION_MINOR``, - ``Boost_VERSION_PATCH``, and ``Boost_VERSION_COUNT`` - were added. - - * The ``QUIET`` argument passed to :command:`find_package` is no - longer ignored in config mode. Note that the CMake package shipped with - Boost ``1.70.0`` ignores the ``QUIET`` argument passed to - :command:`find_package`. This is fixed in the next Boost release. - - * The input switch ``Boost_DETAILED_FAILURE_MSG`` was removed. - - * ``Boost_VERSION`` now reports the version in ``x.y.z`` - format in module mode. See policy :policy:`CMP0093`. - -* The :module:`FindCups` module now provides imported targets. - -* The :module:`FindEnvModules` module was added to use Lua- and TCL-based - environment modules in :ref:`CTest Scripts <CTest Script>`. - -* The :module:`FindGLEW` module now provides an interface more consistent - with what upstream GLEW provides in its own CMake package files. - -* The :module:`FindPkgConfig` now populates :prop_tgt:`INTERFACE_LINK_OPTIONS` - property of imported targets with other (non-library) linker flags. - -* The :module:`FindPostgreSQL` module learned to find debug and release - variants separately. - -* Modules :module:`FindPython3`, :module:`FindPython2` and :module:`FindPython` - gained additional lookup strategies and controls, and a new default. - See policy :policy:`CMP0094`. - -* Modules :module:`FindPython`, :module:`FindPython2` and :module:`FindPython3` - gain a new target (respectively ``Python::Module``, ``Python2::Module`` - and ``Python3::Module``) which can be used to develop Python modules. - -* Modules :module:`FindPython3`, :module:`FindPython2` and :module:`FindPython` - gain capability to control how virtual environments are handled. - -* The :module:`UseSWIG` module learned to manage alternate library names - by passing ``-interface <library_name>`` for ``python`` language or - ``-dllimport <library_name>`` for ``CSharp`` language to the ``SWIG`` - compiler. - -Generator Expressions ---------------------- - -* The :manual:`generator expressions <cmake-generator-expressions(7)>` - ``C_COMPILER_ID``, ``CXX_COMPILER_ID``, ``CUDA_COMPILER_ID``, - ``Fortran_COMPILER_ID``, ``COMPILE_LANGUAGE``, ``COMPILE_LANG_AND_ID``, and - ``PLATFORM_ID`` learned to support matching one value from a comma-separated - list. - -* The ``$<CUDA_COMPILER_ID:...>`` and ``$<CUDA_COMPILER_VERSION:...>`` - :manual:`generator expressions <cmake-generator-expressions(7)>` were added. - -* The ``$<COMPILE_LANG_AND_ID:...>`` generator expression was introduced to - allow specification of compile options for target files based on the - :variable:`CMAKE_<LANG>_COMPILER_ID` and :prop_sf:`LANGUAGE` of - each source file. - -* A ``$<FILTER:list,INCLUDE|EXCLUDE,regex>`` - :manual:`generator expression <cmake-generator-expressions(7)>` - has been added. - -* A ``$<REMOVE_DUPLICATES:list>`` - :manual:`generator expression <cmake-generator-expressions(7)>` - has been added. - -* The ``$<SHELL_PATH:...>`` :manual:`generator expression - <cmake-generator-expressions(7)>` gained support for a list of paths. - -* New ``$<TARGET_FILE*>`` :manual:`generator expressions - <cmake-generator-expressions(7)>` were added to retrieve the prefix, base - name, and suffix of the file names of various artifacts: - - * ``$<TARGET_FILE_PREFIX:...>`` - * ``$<TARGET_FILE_BASE_NAME:...>`` - * ``$<TARGET_FILE_SUFFIX:...>`` - * ``$<TARGET_LINKER_FILE_PREFIX:...>`` - * ``$<TARGET_LINKER_FILE_BASE_NAME:...>`` - * ``$<TARGET_LINKER_FILE_SUFFIX:...>`` - * ``$<TARGET_PDB_FILE_BASE_NAME:...>`` - -* The ``$<TARGET_OBJECTS:...>`` :manual:`generator expression - <cmake-generator-expressions(7)>` is now supported on ``SHARED``, - ``STATIC``, ``MODULE`` libraries and executables. - -CTest ------ - -* The :command:`ctest_submit` command learned a new option: ``BUILD_ID``. - This can be used to store the ID assigned to this build by CDash to a - variable. - -* The :command:`ctest_update` command learned to honor a new variable: - :variable:`CTEST_UPDATE_VERSION_OVERRIDE`. This can be used to specify - the current version of your source tree rather than using the update - command to discover the current version that is checked out. - -CPack ------ - -* The :cpack_gen:`CPack IFW Generator` gained a new - :variable:`CPACK_IFW_PACKAGE_STYLE_SHEET` variable to customize the - installer stylesheet. - -Deprecated and Removed Features -=============================== - -* The :manual:`cmake-server(7)` mode has been deprecated and will be - removed from a future version of CMake. Please port clients to use - the :manual:`cmake-file-api(7)` instead. - -* The :prop_dir:`ADDITIONAL_MAKE_CLEAN_FILES` directory property is now - deprecated. Use the :prop_dir:`ADDITIONAL_CLEAN_FILES` directory property - instead. - -* The variable :variable:`CMAKE_AUTOMOC_RELAXED_MODE` is considered - deprecated. Support still exists but will be removed in future versions. - -* The :command:`export(PACKAGE)` command now does nothing unless - enabled via :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY`. - See policy :policy:`CMP0090`. - -* The :generator:`Xcode` generator now requires at least Xcode 5. - -* An explicit deprecation diagnostic was added for policy ``CMP0066`` - (``CMP0065`` and below were already deprecated). - The :manual:`cmake-policies(7)` manual explains that the OLD behaviors - of all policies are deprecated and that projects should port to the - NEW behaviors. - -Other Changes -============= - -* If a feature specified by :command:`target_compile_features` is available - in the compiler's default standard level, CMake 3.14 and below incorrectly - added unnecessary ``-std=`` flags that could lower the standard level. - This bug has been fixed in CMake 3.15. This behavior change may expose - bugs in existing projects that were relying on undocumented implementation - details. Specifying compile features only ensures that the compiler runs - in a mode that has those features, not that any specific standard level is - used or explicit ``-std=`` flag passed. - -* CMake learned how to compile C++14 with the IBM AIX XL compiler - and the SunPro compiler and to compile C++20 with the AppleClang compiler. - -* With MSVC-like compilers the value of :variable:`CMAKE_<LANG>_FLAGS` - no longer contains warning flags like ``/W3`` by default. - See policy :policy:`CMP0092`. - -* IBM Clang-based XL compilers that define ``__ibmxl__`` now use the - compiler id ``XLClang`` instead of ``XL``. See policy :policy:`CMP0089`. - -* The :command:`file(REMOVE)` and :command:`file(REMOVE_RECURSE)` commands - were changed to ignore empty arguments with a warning instead of treating - them as a relative path and removing the contents of the current directory. - -Updates -======= - -Changes made since CMake 3.15.0 include the following. - -3.15.1 ------- - -* In CMake 3.15.0 support for the GNU-like ``Clang`` compiler targeting the - MSVC ABI implemented :variable:`CMAKE_CXX_STANDARD` values 98 and 11 using - the corresponding ``-std=`` flags. However, these modes do not work with - the MSVC standard library. Therefore CMake 3.15.1 passes C++14 standard - flags even for C++98 and C++11. This is consistent with MSVC itself which - always runs in a mode aware of C++14. - -* Preliminary Swift support added in 3.15.0 has been updated. - -3.15.2 ------- - -* In CMake 3.15.0 and 3.15.1 the :variable:`CMAKE_FIND_PACKAGE_PREFER_CONFIG` - variable caused the :command:`find_package` command to fail on a missing - package even without the ``REQUIRED`` option. This has been fixed. - -3.15.3 ------- - -* ``CrayPrgEnv`` compiler wrapper support has been updated for the 19.06 - release of the Cray Programming Environment for which the default linking - mode on XC Cray systems is now dynamic instead of static. - -3.15.4 ------- - -* In CMake 3.15.0 through 3.15.3, the :prop_dir:`EXCLUDE_FROM_ALL` - directory property was regressed from pre-3.14 behavior and caused - targets within the directory to be excluded even from its own "all". - This has been fixed. - The bug also existed in 3.14.0 through 3.14.6 and is fixed in 3.14.7.
diff --git a/share/cmake-3.18/Help/release/3.16.rst b/share/cmake-3.18/Help/release/3.16.rst deleted file mode 100644 index f3fdb08..0000000 --- a/share/cmake-3.18/Help/release/3.16.rst +++ /dev/null
@@ -1,318 +0,0 @@ -CMake 3.16 Release Notes -************************ - -.. only:: html - - .. contents:: - -Changes made since CMake 3.15 include the following. - -New Features -============ - -Languages ---------- - -* CMake learned to support the Objective C (``OBJC``) and Objective C++ - (``OBJCXX``) languages. They may be enabled via the :command:`project` - and :command:`enable_language` commands. When ``OBJC`` or ``OBJCXX`` - is enabled, source files with the ``.m`` or ``.mm``, respectively, - will be compiled as Objective C or C++. Otherwise they will be treated - as plain C++ sources as they were before. - -Compilers ---------- - -* The ``Clang`` compiler is now supported on ``Solaris``. - -Platforms ---------- - -* On AIX, executables using the :prop_tgt:`ENABLE_EXPORTS` target property - now produce a linker import file with a ``.imp`` extension in addition - to the executable file. Plugins (created via :command:`add_library` with - the ``MODULE`` option) that use :command:`target_link_libraries` to link - to the executable for its symbols are now linked using the import file. - The :command:`install(TARGETS)` command now installs the import file as - an ``ARCHIVE`` artifact. - -* On AIX, runtime linking is no longer enabled by default. CMake provides - the linker enough information to resolve all symbols up front. - One may manually enable runtime linking for shared libraries and/or - loadable modules by adding ``-Wl,-G`` to their link flags - (e.g. in the :variable:`CMAKE_SHARED_LINKER_FLAGS` or - :variable:`CMAKE_MODULE_LINKER_FLAGS` variable). - One may manually enable runtime linking for executables by adding - ``-Wl,-brtl`` to their link flags (e.g. in the - :variable:`CMAKE_EXE_LINKER_FLAGS` variable). - -Command-Line ------------- - -* :manual:`cmake(1)` ``-E`` now supports ``true`` and ``false`` commands, - which do nothing while returning exit codes of 0 and 1, respectively. - -* :manual:`cmake(1)` gained a ``--trace-redirect=<file>`` command line - option that can be used to redirect ``--trace`` output to a file instead - of ``stderr``. - -* The :manual:`cmake(1)` ``--loglevel`` command line option has been - renamed to ``--log-level`` to make it consistent with the naming of other - command line options. The ``--loglevel`` option is still supported to - preserve backward compatibility. - -Commands --------- - -* The :command:`add_test` command learned the option ``COMMAND_EXPAND_LISTS`` - which causes lists in the ``COMMAND`` argument to be expanded, including - lists created by generator expressions. - -* The :command:`file` command learned a new sub-command, - ``GET_RUNTIME_DEPENDENCIES``, which allows you to recursively get the list of - libraries linked by an executable or library. This sub-command is intended as - a replacement for :module:`GetPrerequisites`. - -* The :command:`find_file`, :command:`find_library`, :command:`find_path`, - :command:`find_package`, and :command:`find_program` commands have learned to - check the following variables to control the default behavior for groups of - search locations: - - * :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` - Controls the default - behavior of searching the :variable:`<PackageName>_ROOT` variables. - - * :variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH` - Controls the default - behavior of searching the CMake-specific environment variables. - - * :variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH` - Controls the default - behavior of searching the standard system environment variables. - - * :variable:`CMAKE_FIND_USE_CMAKE_PATH` - Controls the default behavior of - searching the CMake-specific cache variables. - - * :variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH` - Controls the default - behavior of searching the platform-specific CMake variables. - -* The :command:`find_package` command has learned to check the - :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` variable to control the default - behavior of searching the CMake user package registry and to check the - :variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` variable to control - the default behavior of searching the CMake system package registry. - -* The :command:`message` command learned indentation control with the new - :variable:`CMAKE_MESSAGE_INDENT` variable. - -* The :command:`target_precompile_headers` command was added to specify - a list of headers to precompile for faster compilation times. - -Variables ---------- - -* The :variable:`CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS` variable has been - introduced to optionally initialize the - :prop_tgt:`CUDA_RESOLVE_DEVICE_SYMBOLS` target property. - -* The :variable:`CMAKE_ECLIPSE_RESOURCE_ENCODING` variable was added to - specify the resource encoding for the the :generator:`Eclipse CDT4` extra - generator. - -* The :variable:`CMAKE_UNITY_BUILD` variable was added to initialize the - :prop_tgt:`UNITY_BUILD` target property to tell generators to batch - include source files for faster compilation times. - -Properties ----------- - -* The :prop_tgt:`BUILD_RPATH` and :prop_tgt:`INSTALL_RPATH` target properties - now support :manual:`generator expressions <cmake-generator-expressions(7)>`. - -* The :prop_tgt:`INSTALL_REMOVE_ENVIRONMENT_RPATH` target property was - added to remove compiler-defined ``RPATH`` entries from a target. - This property is initialized by the - :variable:`CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH` variable. - -* The :prop_tgt:`PRECOMPILE_HEADERS` target property was added to specify - a list of headers to precompile for faster compilation times. - Set it using the :command:`target_precompile_headers` command. - -* The :prop_tgt:`UNITY_BUILD` target property was added to tell - generators to batch include source files for faster compilation - times. - -* The :prop_tgt:`VS_CONFIGURATION_TYPE` target property now supports - :manual:`generator expressions <cmake-generator-expressions(7)>`. - -* The :prop_tgt:`VS_DPI_AWARE` target property was added to tell - :ref:`Visual Studio Generators` to set the ``EnableDpiAwareness`` - property in ``.vcxproj`` files. - -* The :prop_tgt:`XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING` target property was - added to tell the :generator:`Xcode` generator to set the value of the - ``Allow debugging when using document Versions Browser`` schema option. - -Modules -------- - -* The :module:`FindDoxygen` module :command:`doxygen_add_docs` command - gained a new ``USE_STAMP_FILE`` option. When this option present, - the custom target created by the command will only re-run Doxygen if - any of the source files have changed since the last successful run. - -* The :module:`FindGnuTLS` module now provides an imported target. - -* The :module:`FindPackageHandleStandardArgs` module - :command:`find_package_handle_standard_args` command gained - a new ``REASON_FAILURE_MESSAGE`` option to specify a message - giving the reason for the failure. - -* The :module:`FindPkgConfig` module :command:`pkg_search_module` macro - now defines a ``<prefix>_MODULE_NAME`` result variable containing the - first matching module name. - -* The :module:`FindPython3` and :module:`FindPython` modules gained - options to control which ``ABIs`` will be searched. - -* The :module:`FindPython3`, :module:`FindPython2`, and :module:`FindPython` - modules now support direct specification of artifacts via cache entries. - -Autogen -------- - -* When using :prop_tgt:`AUTOMOC`, CMake now generates the ``-p`` path prefix - option for ``moc``. This ensures that ``moc`` output files are identical - on different build setups (given, that the headers compiled by ``moc`` are - in an :command:`include directory <target_include_directories>`). - Also it ensures that ``moc`` output files will compile correctly when the - source and/or build directory is a symbolic link. - - The ``moc`` path prefix generation behavior can be configured by setting - the new :variable:`CMAKE_AUTOMOC_PATH_PREFIX` variable and/or - :prop_tgt:`AUTOMOC_PATH_PREFIX` target property. - -CTest ------ - -* :manual:`ctest(1)` now has the ability to schedule tests based on resource - requirements for each test. See :ref:`ctest-resource-allocation` for - details. - -* A new test property, :prop_test:`SKIP_REGULAR_EXPRESSION`, has been added. - This property is similar to :prop_test:`FAIL_REGULAR_EXPRESSION` and - :prop_test:`PASS_REGULAR_EXPRESSION`, but with the same meaning as - :prop_test:`SKIP_RETURN_CODE`. This is useful, for example, in cases where - the user has no control over the return code of the test. For example, in - Catch2, the return value is the number of assertion failed, therefore it is - impossible to use it for :prop_test:`SKIP_RETURN_CODE`. - -CPack ------ - -* :manual:`cpack(1)` learned support for multiple configurations for ``-C`` - option. - -* The :cpack_gen:`CPack DEB Generator` is now able to format generic text - (usually used as the description for multiple CPack generators) according - to the `Debian Policy Manual`_. See the - :variable:`CPACK_PACKAGE_DESCRIPTION_FILE` and - :variable:`CPACK_DEBIAN_<COMPONENT>_DESCRIPTION` variables. - -* The :cpack_gen:`CPack Archive Generator` learned to generate ``.tar.zst`` - packages with Zstandard compression. - -.. _`Debian Policy Manual`: https://www.debian.org/doc/debian-policy/ch-controlfields.html#description - -Deprecated and Removed Features -=============================== - -* An explicit deprecation diagnostic was added for policy ``CMP0067`` - (``CMP0066`` and below were already deprecated). - The :manual:`cmake-policies(7)` manual explains that the OLD behaviors - of all policies are deprecated and that projects should port to the - NEW behaviors. - -* The :variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` variable has been - deprecated. Use the :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` variable - instead. - -* The :module:`GetPrerequisites` module has been deprecated, as it has been - superceded by :command:`file(GET_RUNTIME_DEPENDENCIES)`. - -* The ``CPACK_INSTALL_SCRIPT`` variable has been deprecated in favor of the - new, more accurately named :variable:`CPACK_INSTALL_SCRIPTS` variable. - -Other Changes -============= - -* The :manual:`cmake(1)` ``-C <initial-cache>`` option now evaluates the - initial cache script with :variable:`CMAKE_SOURCE_DIR` and - :variable:`CMAKE_BINARY_DIR` set to the top-level source and build trees. - -* The :manual:`cmake(1)` ``-E remove_directory`` command-line tool, - when given the path to a symlink to a directory, now removes just - the symlink. It no longer removes content of the linked directory. - -* The :manual:`ctest(1)` ``--build-makeprogram`` command-line option now - specifies the make program used when configuring a project with the - :generator:`Ninja` generator or the :ref:`Makefile Generators`. - -* The :module:`ExternalProject` module :command:`ExternalProject_Add` command - has been updated so that ``GIT_SUBMODULES ""`` initializes no submodules. - See policy :policy:`CMP0097`. - -* The :module:`FindGTest` module has been updated to recognize - MSVC build trees generated by GTest 1.8.1. - -* The :command:`project` command no longer strips leading zeros in version - components. See policy :policy:`CMP0096`. - -* The Qt Compressed Help file is now named ``CMake.qch``, which no longer - contains the release version in the file name. When CMake is upgraded - in-place, the name and location of this file will remain constant. - Tools such as IDEs, help viewers, etc. should now be able to refer to this - file at a fixed location that remains valid across CMake upgrades. - -* ``RPATH`` entries are properly escaped in the generated CMake scripts - used for installation. See policy :policy:`CMP0095`. - -* When using :variable:`CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS` on Windows the - auto-generated exports are now updated only when the object files - providing the symbols are updated. - -Updates -======= - -Changes made since CMake 3.16.0 include the following. - -3.16.2 ------- - -* CMake 3.16.0 and 3.16.1 processed ``.hh`` files with :prop_tgt:`AUTOMOC`. - This was a behavior change from CMake 3.15 and below that can break - existing projects, so it has been reverted as of 3.16.2. - -3.16.5 ------- - -* The :module:`FindPython`, :module:`FindPython2`, and :module:`FindPython3` - modules no longer create cache entries for ``Python{,2,3}_LIBRARY_RELEASE`` - and ``Python{,2,3}_LIBRARY_DEBUG``. Those values are always computed from - other results and so should not be cached. The entries were created by - CMake 3.16.0 through 3.16.4 but were always ``FORCE``-set and could not - be meaningfully edited by users. - - Additionally, the modules no longer expose their internal ``_Python*`` - cache entries publicly. CMake 3.16.0 through 3.16.4 accidentally - made them visible as advanced cache entries. - -3.16.7 ------- - -* Selection of the Objective C or C++ compiler now considers the - :envvar:`CC` or :envvar:`CXX` environment variable if the - :envvar:`OBJC` or :envvar:`OBJCXX` environment variable is not set. - -* The :module:`FindPkgConfig` module now extracts include directories - prefixed with ``-isystem`` into the ``*_INCLUDE_DIRS`` variables and - :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` target properties. - Previously they would be places in ``*_CFLAGS_OTHER`` variables and - :prop_tgt:`INTERFACE_COMPILE_OPTIONS` target properties.
diff --git a/share/cmake-3.18/Help/release/3.17.rst b/share/cmake-3.18/Help/release/3.17.rst deleted file mode 100644 index b7c66d8..0000000 --- a/share/cmake-3.18/Help/release/3.17.rst +++ /dev/null
@@ -1,348 +0,0 @@ -CMake 3.17 Release Notes -************************ - -.. only:: html - - .. contents:: - -Changes made since CMake 3.16 include the following. - -New Features -============ - -Generators ----------- - -* :manual:`cmake(1)` gained a :generator:`Ninja Multi-Config` generator, - which is similar to the :generator:`Ninja` generator but can be used to build - multiple configurations at once. - -* :ref:`Visual Studio Generators` learned to support per-config sources. - Previously only :ref:`Command-Line Build Tool Generators` supported them. - -* :ref:`Visual Studio Generators` for VS 2010 and above now support - specifying the ``VCTargetsPath`` value for project files in - :variable:`CMAKE_GENERATOR_TOOLSET` setting. - -* :ref:`Visual Studio Generators` for VS 2010 and above learned to - support .NET Standard and .NET Core. See the - :prop_tgt:`DOTNET_TARGET_FRAMEWORK` target property and - associated :variable:`CMAKE_DOTNET_TARGET_FRAMEWORK` variable. - -Languages ---------- - -* The :manual:`Compile Features <cmake-compile-features(7)>` functionality - now offers meta-features for the CUDA language standard levels - (e.g. ``cuda_std_03``, ``cuda_std_14``). See - :prop_gbl:`CMAKE_CUDA_KNOWN_FEATURES`. - -Compilers ---------- - -* The IBM XL Fortran compiler is now supported by the :generator:`Ninja` - generator. - -Command-Line ------------- - -* :manual:`cmake(1)` gained a ``--debug-find`` command-line option to - enable additional human-readable output on where ``find_*`` commands search. - -* :manual:`cmake(1)` gained a ``--trace-format`` command-line option that - can be used to set the ``--trace`` output format. Currently, the old - human readable and the new JSON format are supported. The new JSON format - is easier to parse automatically than the existing format. - -* :manual:`cmake(1)` gained a ``-E rm`` command-line tool that can be - used to remove directories and files. This supersedes the existing - ``-E remove`` and ``-E remove_directory`` tools and has better semantics. - -Commands --------- - -* The :command:`add_custom_command` command learned to interpret paths in - ``DEPENDS`` arguments that are specified relative to the current - binary directory. - -* The :command:`foreach` command learned a new ``ZIP_LISTS`` option to iterate - over multiple lists simultaneously. - -* The :command:`load_cache(READ_WITH_PREFIX)` command mode is now allowed - when using ``cmake -P`` to :ref:`Run a Script <Script Processing Mode>`. - -* The :command:`message` command learned to output context provided in - the :variable:`CMAKE_MESSAGE_CONTEXT` variable for log levels - ``NOTICE`` and below. Enable this output with the new ``--log-context`` - command-line option or :variable:`CMAKE_MESSAGE_CONTEXT_SHOW` variable. - -* The :command:`message` command gained new keywords ``CHECK_START``, - ``CHECK_PASS`` and ``CHECK_FAIL``. - -* The :command:`target_compile_options` command now honors the ``BEFORE`` - keyword more consistently. See policy :policy:`CMP0101`. - -Variables ---------- - -* A :variable:`CMAKE_CTEST_ARGUMENTS` variable was added to specify a list - of command-line arguments passed to CTest when running through the - ``test`` (or ``RUN_TESTS``) target of the generated build system. - -* The following variables are now defined inside a :command:`function`: - - - :variable:`CMAKE_CURRENT_FUNCTION` - - :variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR` - - :variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE` - - :variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE` - -* The :variable:`CMAKE_CUDA_RUNTIME_LIBRARY` variable and - :prop_tgt:`CUDA_RUNTIME_LIBRARY` target property were introduced to - select the CUDA runtime library used when linking targets that - use CUDA. - -* The :variable:`CMAKE_FIND_DEBUG_MODE` variable was introduced to - print extra ``find_*`` call information during the cmake run to standard - error. Output is designed for human consumption and not for parsing. - -* The :variable:`CMAKE_EXPORT_COMPILE_COMMANDS` variable now takes its - initial value from the :envvar:`CMAKE_EXPORT_COMPILE_COMMANDS` environment - variable if no explicit configuration is given. - -* The :variable:`CMAKE_<LANG>_COMPILER_LAUNCHER` variable, if not set - explicitly, now takes its initial value from the - :envvar:`CMAKE_<LANG>_COMPILER_LAUNCHER` environment variable. - -* The :variable:`CMAKE_MESSAGE_LOG_LEVEL` variable can now be used - to persist a log level between CMake runs, unlike the ``--log-level`` - command line option which only applies to that particular run. - -* The :variable:`CMAKE_XCODE_SCHEME_ENVIRONMENT` variable was added - to initialize the :prop_tgt:`XCODE_SCHEME_ENVIRONMENT` target property. - -* The :variable:`CMAKE_XCODE_SCHEME_WORKING_DIRECTORY` variable and - associated :prop_tgt:`XCODE_SCHEME_WORKING_DIRECTORY` target property - were added to tell the :generator:`Xcode` generator to set the value of - the ``Custom Working Directory`` schema option. - -Properties ----------- - -* The :prop_tgt:`AIX_EXPORT_ALL_SYMBOLS` target property and associated - :variable:`CMAKE_AIX_EXPORT_ALL_SYMBOLS` variable were created to - optionally explicitly disable automatic export of symbols from shared - libraries on AIX. - -* The :prop_tgt:`DEPRECATION` target property was added to mark - a target as deprecated. If a linked target is marked as - deprecated, a warning with the deprecation message is issued - at generate time. - -* The :prop_tgt:`INSTALL_NAME_DIR` target property now supports - :manual:`generator expressions <cmake-generator-expressions(7)>`. - In particular, the ``$<INSTALL_PREFIX>`` generator expression can - be used to set the directory relative to the install-time prefix. - -* Target properties :prop_tgt:`MACHO_COMPATIBILITY_VERSION` and - :prop_tgt:`MACHO_CURRENT_VERSION` were added to set the - ``compatibility_version`` and ``curent_version``, respectively, - for Mach-O binaries. For backwards compatibility, if these properties - are not set, :prop_tgt:`SOVERSION` and :prop_tgt:`VERSION` - are used respectively as fallbacks. - -* The :prop_tgt:`VS_DOTNET_DOCUMENTATION_FILE` target property was added - to tell :ref:`Visual Studio Generators` to generate a ``DocumentationFile`` - reference in ``.csproj`` files. - -Modules -------- - -* The :module:`ExternalProject` module :command:`ExternalProject_Add` - command gained a ``GIT_SUBMODULES_RECURSE`` option to specify whether - Git submodules should be updated recursively. The default is on to - preserve existing behavior. - -* The :module:`FindCUDAToolkit` module was added to find the - CUDA Toolkit without enabling CUDA as a language. - -* The :module:`FindCURL` module learned to find CURL using - the ``CURLConfig.cmake`` package configuration file generated by - CURL's cmake buildsystem. It also gained a new ``CURL_NO_CURL_CMAKE`` - option to disable this behavior. - -* The :module:`FindFLEX` module's ``FLEX_TARGET`` command now runs ``flex`` - with :variable:`CMAKE_CURRENT_BINARY_DIR` as the working directory. - See policy :policy:`CMP0098`. - -* The :module:`FindLibArchive` module now provides an imported target - for libarchive. - -* The :module:`FindPython` module has learned to find Python components - in active virtual environments managed by ``conda``. - -* The :module:`FindPython3` and :module:`FindPython` modules gained, - respectively, variable ``Python3_SOABI`` and ``Python_SOABI`` giving - the standard extension suffix for modules. Moreover, commands - ``Python3_add_library()`` and ``Python_add_library()`` gained the option - ``WITH_SOABI`` to prefix the library suffix with the value of ``SOABI``. - -* The :module:`FindLibXml2` module now provides an imported target for the - ``xmllint`` executable. - -Autogen -------- - -* :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` learned to process headers - with a ``.hh`` extension. See policy :policy:`CMP0100`. - -CTest ------ - -* The :variable:`CTEST_CONFIGURATION_TYPE` variable is now set from the - command line when :manual:`ctest(1)` is invoked with ``-C <cfg>``. - -* The :manual:`ctest(1)` tool gained support for Dr. Memory to run - memcheck runs. - -* The :manual:`ctest(1)` tool gained a ``--no-tests=<[error|ignore]>`` option - to explicitly set and unify the behavior between direct invocation and - script mode if no tests were found. - -* The :manual:`ctest(1)` tool gained a ``--repeat <mode>:<n>`` option - to specify conditions in which to repeat tests. This generalizes - the existing ``--repeat-until-fail <n>`` option to add modes for - ``until-pass`` and ``after-timeout``. - -* The :command:`ctest_test` command gained a ``REPEAT <mode>:<n>`` option - to specify conditions in which to repeat tests. - -CPack ------ - -* The :cpack_gen:`CPack DragNDrop Generator` learned to use - the :variable:`CPACK_DMG_<component>_FILE_NAME` variable - to set a custom filename when packaging components into - their own DMGs. - -* The :cpack_gen:`CPack DragNDrop Generator` learned to handle - RTF formatted license files. When :variable:`CPACK_DMG_SLA_DIR` - variable is set, ``<language>.license.rtf`` is considered, but - only as a fallback when the plaintext (``.txt``) file is not found - in order to maintain backwards compatibility. - -* The :cpack_gen:`CPack NSIS Generator` gained a new variable - :variable:`CPACK_NSIS_MUI_HEADERIMAGE` to set the header image. - To not break existing setups, it still defaults to - :variable:`CPACK_PACKAGE_ICON` if the new variable is not set. - -* The :cpack_gen:`CPack NSIS Generator` now supports - :variable:`CPACK_NSIS_UNINSTALL_NAME`. - This can be used to specify the name of the Uninstall program. - -* The :cpack_gen:`CPack NSIS Generator` now supports - :variable:`CPACK_NSIS_WELCOME_TITLE` and - :variable:`CPACK_NSIS_WELCOME_TITLE_3LINES`. - These can be used to specify the welcome page title and display it in 3 lines. - -* The :cpack_gen:`CPack NSIS Generator` now supports - :variable:`CPACK_NSIS_FINISH_TITLE` and - :variable:`CPACK_NSIS_FINISH_TITLE_3LINES`. - These can be used to specify the finish page title and display it in 3 lines. - -* The :cpack_gen:`CPack productbuild Generator` gained support for a - :variable:`CPACK_PRODUCTBUILD_BACKGROUND` variable to specify a background - image for the macOS installer. - -Other ------ - -* :manual:`ccmake(1)` now displays cache values using colors - based on the entry type if the terminal supports color. - -* :manual:`ccmake(1)` now displays messages and a progress bar during - configure and generate. It will keep the output displayed if any - errors or warnings occurred. - -Deprecated and Removed Features -=============================== - -* An explicit deprecation diagnostic was added for policy ``CMP0068`` - and policy ``CMP0069`` (``CMP0067`` and below were already deprecated). - The :manual:`cmake-policies(7)` manual explains that the OLD behaviors - of all policies are deprecated and that projects should port to the - NEW behaviors. - -* The :cpack_gen:`CPack PackageMaker Generator` generator has been - deprecated because Xcode no longer distributes the PackageMaker tools. - The undocumented ``OSXX11`` generator has also been deprecated. - -* The :manual:`cmake(1)` command-line ``-E remove`` and ``-E remove_directory`` - tools are deprecated in favor of the new ``-E rm`` tool. The older tools - always returned 0 if a named path did not exist even without the force - option and cannot be fixed without breaking compatibility, and so have - been superseded. - -* The :cpack_gen:`CPack NSIS Generator` now requires NSIS 3.0 or later. - -Other Changes -============= - -* The :manual:`file API <cmake-file-api(7)>` index file now emits a - ``multiConfig`` flag specifying whether or not the generator supports - multiple output configurations. - -* Target link properties :prop_tgt:`INTERFACE_LINK_OPTIONS`, - :prop_tgt:`INTERFACE_LINK_DIRECTORIES` and - :prop_tgt:`INTERFACE_LINK_DEPENDS` are now transitive over private - dependencies on static libraries. - See policy :policy:`CMP0099`. - -* When using MinGW tools, the :command:`find_library` command no longer - finds ``.dll`` files by default. Instead, it expects ``.dll.a`` import - libraries to be available. - -* The :generator:`MinGW Makefiles` generator no longer issues an error if - ``sh.exe`` is present in the environment's ``PATH``. - -* The :generator:`Ninja` generator now prefers the first ninja build - tool to appear in the ``PATH`` no matter whether it is called - ``ninja-build``, ``ninja``, or ``samu``. Previously the first - of those names to appear anywhere in the ``PATH`` would be preferred. - -* With SDCC the ``sdar`` tool is now preferred over ``sdcclib`` as librarian. - The latter was deprecated by SDCC 3.2.0 and removed in SDCC 3.8.6. - -* With SDCC the default flags no longer include any target-specific flags. - Previously the default flags were hard-coded for 8051. - -* The :variable:`CMAKE_VS_GLOBALS` variable value now applies during - compiler identification and in targets created by the - :command:`add_custom_target` command. - -* The :generator:`Xcode` generator no longer hard-codes ``-Wmost``, - ``-Wno-four-char-constants``, and ``-Wno-unknown-pragmas`` warning flags. - -Updates -======= - -Changes made since CMake 3.17.0 include the following. - -3.17.1 ------- - -* CMake 3.17.0 updated the :cpack_gen:`CPack NSIS Generator` with changes - that require NSIS 3.0 or later. CMake 3.17.1 now enforces the use - of a sufficiently new version. - -3.17.3 ------- - -* Selection of the Objective C or C++ compiler now considers the - :envvar:`CC` or :envvar:`CXX` environment variable if the - :envvar:`OBJC` or :envvar:`OBJCXX` environment variable is not set. - -* The :module:`FindPkgConfig` module now extracts include directories - prefixed with ``-isystem`` into the ``*_INCLUDE_DIRS`` variables and - :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` target properties. - Previously they would be places in ``*_CFLAGS_OTHER`` variables and - :prop_tgt:`INTERFACE_COMPILE_OPTIONS` target properties.
diff --git a/share/cmake-3.18/Help/release/3.18.rst b/share/cmake-3.18/Help/release/3.18.rst deleted file mode 100644 index ba80d2b..0000000 --- a/share/cmake-3.18/Help/release/3.18.rst +++ /dev/null
@@ -1,341 +0,0 @@ -CMake 3.18 Release Notes -************************ - -.. only:: html - - .. contents:: - -Changes made since CMake 3.17 include the following. - -New Features -============ - -Languages ---------- - -* The ``CUDA`` language can now be compiled using Clang on non-Windows - platforms. Separable compilation is not yet supported on any platform. - -Command-Line ------------- - -* :manual:`cmake(1)` gained support for profiling of CMake scripts through - the parameters ``--profiling-output`` and ``--profiling-format``. - -* :manual:`cmake(1)` gained a ``cat`` command line - option that can be used to concatenate files and print them - on standard output. - -Commands --------- - -* The :command:`add_library` and :command:`add_executable` commands - learned to create :ref:`Alias Targets` referencing non-``GLOBAL`` - :ref:`Imported Targets`. - -* The :command:`cmake_language()` command was added for meta-operations on - scripted or built-in commands, starting with a mode to ``CALL`` other - commands, and ``EVAL CODE`` to inplace evaluate a CMake script. - -* The :command:`execute_process` command gained the ``ECHO_OUTPUT_VARIABLE`` - and ``ECHO_ERROR_VARIABLE`` options. - -* The :command:`export` command now raise an error if used multiple times with - same ``FILE`` without ``APPEND``. See policy :policy:`CMP0103`. - -* The :command:`file` command gained the ``ARCHIVE_CREATE`` and - ``ARCHIVE_EXTRACT`` subcommands to expose the :manual:`cmake(1)` ``-E tar`` - functionality to CMake scripting code. - -* The :command:`file(CONFIGURE)` subcommand was created in order to replicate - the :command:`configure_file` functionality without resorting to a - pre-existing file on disk as input. The content is instead passed as a - string. - -* The :command:`file(UPLOAD)` command gained ``TLS_VERIFY`` and ``TLS_CAINFO`` - options to control server certificate verification. - -* The :command:`find_program`, :command:`find_library`, :command:`find_path` - and :command:`find_file` commands gained a new ``REQUIRED`` option that will - stop processing with an error message if nothing is found. - -* The :command:`get_property` command with ``SOURCE`` scope gained the - ``DIRECTORY`` and ``TARGET_DIRECTORY`` options to get a property - from the provided directory scope. - -* The :command:`get_source_file_property` command gained the ``DIRECTORY`` - and ``TARGET_DIRECTORY`` options to get a property from the - provided directory scope. - -* The :command:`list` operation ``SORT`` gained the ``NATURAL`` sort - option to sort using natural order (see ``strverscmp(3)`` manual). - -* The :command:`set_property` command with the ``SOURCE`` scope gained the - ``DIRECTORY`` and ``TARGET_DIRECTORY`` options to set properties - in the provided directory scopes. - -* The :command:`set_source_files_properties` command gained the ``DIRECTORY`` - and ``TARGET_DIRECTORY`` options to set properties in the provided - directory scopes. - -* The :command:`string` command learned a new ``HEX`` sub-command, which - converts strings into their hexadecimal representation. - -Variables ---------- - -* A :variable:`CMAKE_CUDA_ARCHITECTURES` variable was added to specify - CUDA output architectures. Users are encouraged to use this instead of - specifying options manually, as this approach is compiler-agnostic. - The variable is initialized automatically when - :variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` is ``NVIDIA``. - The variable is used to initialize the new :prop_tgt:`CUDA_ARCHITECTURES` - target property. See policy :policy:`CMP0104`. - -* The :variable:`CMAKE_PCH_WARN_INVALID` variable was added to initialize the - :prop_tgt:`PCH_WARN_INVALID` target property to allow the removal of the - precompiled header invalid warning. - -Properties ----------- - -* The :prop_tgt:`CUDA_ARCHITECTURES` target property was added to specify - CUDA output architectures. Users are encouraged to use this instead of - specifying options manually, as this approach is compiler-agnostic. - The property is initialized by the new :variable:`CMAKE_CUDA_ARCHITECTURES` - variable. See policy :policy:`CMP0104`. - -* The :prop_tgt:`Fortran_PREPROCESS` target property and - :prop_sf:`Fortran_PREPROCESS` source-file property were added to - control preprocessing of Fortran source files. - -* The :prop_tgt:`FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>` target property - and associated :variable:`CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>` - variable were created to allow adding a postfix to the name of a - framework file name when using a multi-config generator. - -* The :prop_sf:`OBJECT_OUTPUTS` source file property now supports - :manual:`generator expressions <cmake-generator-expressions(7)>`. - -* The :prop_tgt:`PCH_WARN_INVALID` target property was added to allow the - removal of the precompiled header invalid warning. - -* The :prop_tgt:`UNITY_BUILD_MODE` target property was added to tell - generators which algorithm to use for grouping included source - files. - -* The :prop_tgt:`VS_SOURCE_SETTINGS_<tool>` target property was added - to tell :ref:`Visual Studio Generators` for VS 2010 and above to add - metadata to non-built source files using ``<tool>``. - -* The :prop_sf:`VS_SETTINGS` source file property was added to tell - :ref:`Visual Studio Generators` for VS 2010 and above to add - metadata to a non-built source file. - -* The :prop_tgt:`VS_PLATFORM_TOOLSET` target property was added to tell - :ref:`Visual Studio Generators` for VS 2010 and above to override - the platform toolset. - -* The :prop_tgt:`VS_SOLUTION_DEPLOY` target property was added to tell - :ref:`Visual Studio Generators` for VS 2010 and above to mark a - target for deployment even when not building for Windows Phone/Store/CE. - -Modules -------- - -* The :module:`CheckLinkerFlag` module has been added to provide a - facility to check validity of link flags. - -* The :module:`ExternalProject` module :command:`ExternalProject_Add` command - gained a new ``GIT_REMOTE_UPDATE_STRATEGY`` keyword. This can be used to - specify how failed rebase operations during a git update should be handled. - The ``CMAKE_EP_GIT_REMOTE_UPDATE_STRATEGY`` variable was also added as a - global default and is honored by both the :module:`ExternalProject` and - :module:`FetchContent` modules. - -* The :module:`FetchContent` module :command:`FetchContent_Declare` command - now supports a ``SOURCE_SUBDIR`` option. It can be used to direct - :command:`FetchContent_MakeAvailable` to look in a different location - for the ``CMakeLists.txt`` file. - -* The :module:`FindBLAS` module now provides an imported target. - -* The :module:`FindCUDAToolkit` module: - - * gained the variable - ``CUDAToolkit_LIBRARY_ROOT``, which is the directory containing the - ``nvvm`` directory and ``version.txt``. - - * uses toolkit and library root found during ``CUDA`` compiler detection. - -* The :module:`FindLAPACK` module now provides an imported target. - -* The :module:`FindPython3`, :module:`FindPython2` and :module:`FindPython` - modules: - - * gained the possibility to create per-artifact cache variables for - interactive editing in :manual:`cmake-gui(1)` and :manual:`ccmake(1)`. - - * gained sub-components ``Development.Module`` and - ``Development.Embed`` under the ``Development`` component. - - * gained the capability to specify which Python implementations to find, - including ``IronPython`` and ``PyPy``. - -* The :module:`FindRuby` module input and output variables were all renamed - from ``RUBY_`` to ``Ruby_`` for consistency with other find modules. - Input variables of the old case will be honored if provided, and output - variables of the old case are always provided. - -* The :module:`FindSWIG` module now accepts target languages as ``COMPONENTS`` - and ``OPTIONAL_COMPONENTS`` arguments to ``find_package``. - -* The :module:`GoogleTest` module :command:`gtest_discover_tests` command: - - * gained a new ``DISCOVERY_MODE`` option to control when the test - discovery step is run. It offers a new ``PRE_TEST`` setting to - run the discovery at test time instead of build time. A new - ``CMAKE_GTEST_DISCOVER_TESTS_DISCOVERY_MODE`` variable can be used - to change the default globally. - - * gained a new optional parameter ``XML_OUTPUT_DIR``. When set the - JUnit XML test results are stored in that directory. - -* The :module:`FindLibXslt` module now provides imported targets. - -* The :module:`UseSWIG` module now supports Fortran as a target language if - the ``SWIG_EXECUTABLE`` is SWIG-Fortran_. - -.. _`SWIG-Fortran`: https://github.com/swig-fortran/swig - -Generator Expressions ---------------------- - -* The ``$<DEVICE_LINK:...>`` and ``$<HOST_LINK:...>`` - :manual:`generator expressions <cmake-generator-expressions(7)>` were added - to manage device and host link steps. - -* The ``$<LINK_LANGUAGE:...>`` and ``$<LINK_LANG_AND_ID:...>`` - :manual:`generator expressions <cmake-generator-expressions(7)>` were added. - -CTest ------ - -* :manual:`ctest(1)` gained a new :variable:`CTEST_RESOURCE_SPEC_FILE` - variable, which can be used to specify a - :ref:`resource specification file <ctest-resource-specification-file>`. - -* :manual:`ctest(1)` gained a ``--stop-on-failure`` option, - which can be used to stop running the tests once one has failed. - -* The :command:`ctest_test` command gained a ``STOP_ON_FAILURE`` option - which can be used to stop running the tests once one has failed. - -* The :module:`CTestCoverageCollectGCOV` module - :command:`ctest_coverage_collect_gcov` command gained a - ``TARBALL_COMPRESSION`` option to control compression of the - tarball of collected results. - -CPack ------ - -* The :cpack_gen:`CPack Archive Generator`'s ``TXZ`` format learned the - :variable:`CPACK_ARCHIVE_THREADS` variable to enable parallel compression. - Requires support in the ``liblzma`` used by CMake. - -* The :cpack_gen:`CPack NSIS Generator` gained a new variable - :variable:`CPACK_NSIS_MANIFEST_DPI_AWARE` to declare that the - installer is DPI-aware. - -* The :cpack_gen:`CPack RPM Generator` gained - :variable:`CPACK_RPM_PRE_TRANS_SCRIPT_FILE` and - :variable:`CPACK_RPM_POST_TRANS_SCRIPT_FILE` - variables to specify pre- and post-transaction scripts. - -Other ------ - -* :manual:`cmake-gui(1)` now populates its generator selection - widget default value from the :envvar:`CMAKE_GENERATOR` environment - variable. Additionally, environment variables - :envvar:`CMAKE_GENERATOR_PLATFORM` and :envvar:`CMAKE_GENERATOR_TOOLSET` - are used to populate their respective widget defaults. - -* :manual:`ccmake(1)` learned to read a :envvar:`CCMAKE_COLORS` - environment variable to customize colors. - -Deprecated and Removed Features -=============================== - -* The :module:`Documentation` module has been deprecated via - :policy:`CMP0106`. This module was essentially VTK code that CMake should - not be shipping anymore. - -* An explicit deprecation diagnostic was added for policy ``CMP0070`` - and policy ``CMP0071`` (``CMP0069`` and below were already deprecated). - The :manual:`cmake-policies(7)` manual explains that the OLD behaviors - of all policies are deprecated and that projects should port to the - NEW behaviors. - -Other Changes -============= - -* On Windows, the :generator:`Ninja` and :generator:`Ninja Multi-Config` - generators, when a compiler is not explicitly specified, now select - the first compiler (of any name) found in directories listed by the - ``PATH`` environment variable. - -* The :prop_tgt:`LINK_OPTIONS` and :prop_tgt:`INTERFACE_LINK_OPTIONS` target - properties are now used for the device link step. - See policy :policy:`CMP0105`. - -* Creation of an ``ALIAS`` target overwriting an existing target now raises an - error. See policy :policy:`CMP0107`. - -* Linking a target to itself through an alias now raises an error. - See policy :policy:`CMP0108`. - -* The :module:`FindPackageHandleStandardArgs` module option ``REQUIRED_VARS`` - is now optional if ``HANDLE_COMPONENTS`` is specified. - -* The :command:`source_group` command now also recognizes forward slashes - as subgroup delimiters, not just backslashes. - -* :manual:`ctest(1)` now logs environment variables that it sets for each test, - either due to the :prop_test:`ENVIRONMENT` property or the - :ref:`resource allocation <ctest-resource-allocation>` feature, and submits - this log to CDash. It does not log environment variables that were set - outside of CTest. - -* When building CMake itself from source and not using a system-provided - libcurl, HTTP/2 support is now enabled for commands supporting - network communication via ``http(s)``, such as :command:`file(DOWNLOAD)`, - :command:`file(UPLOAD)`, and :command:`ctest_submit`. - The precompiled binaries provided on ``cmake.org`` now support HTTP/2. - -* The :manual:`cmake-file-api(7)` "codemodel" version 2 ``version`` field has - been updated to 2.1. - -* The :manual:`cmake-file-api(7)` "codemodel" version 2 "target" object gained - a new ``precompileHeaders`` field in the ``compileGroups`` objects. - -Updates -======= - -Changes made since CMake 3.18.0 include the following. - -3.18.1 ------- - -* The :generator:`Xcode` generator, when :variable:`CMAKE_OSX_ARCHITECTURES` - is not defined, now selects ``$(NATIVE_ARCH_ACTUAL)`` as the default - architecture (the Xcode ``ARCHS`` setting). This is needed for Xcode 12 - to select the host's architecture, which older versions of Xcode did - by default. - -* In CMake 3.18.0 the :command:`add_test` command learned to support - special characters in test names. This was accidentally left out of - its release notes. Unfortunately the fix breaks existing projects - that were using manual quoting or escaping to work around the prior - limitation. This fix has been reverted in 3.18.1, but may be - re-introduced in future versions of CMake with a policy for compatibility.
diff --git a/share/cmake-3.18/Help/release/3.3.rst b/share/cmake-3.18/Help/release/3.3.rst deleted file mode 100644 index 6657e8d..0000000 --- a/share/cmake-3.18/Help/release/3.3.rst +++ /dev/null
@@ -1,287 +0,0 @@ -CMake 3.3 Release Notes -*********************** - -.. only:: html - - .. contents:: - -Changes made since CMake 3.2 include the following. - -New Features -============ - -Generators ----------- - -* The :ref:`Makefile Generators` now add ``.DELETE_ON_ERROR`` to the - makefiles that contain the actual build rules for files on disk. - This tells GNU make to remove rule outputs when their recipe - modifies an output but fails. - -* The :ref:`Visual Studio Generators` learned to support ``.xaml`` - source files and automatically associate them with corresponding - ``.h`` and ``.cpp`` sources. - -* A new experimental :generator:`Green Hills MULTI` generator was - added on Windows. `Green Hills MULTI`_ is an IDE for embedded - real-time systems. - -.. _`Green Hills MULTI`: http://www.ghs.com/products/MULTI_IDE.html - -Commands --------- - -* The :command:`add_dependencies` command learned to allow dependencies - to be added to :ref:`interface libraries <Interface Libraries>`. - Dependencies added to an interface library are followed transitively - in its place since the target itself does not build. - -* The :command:`execute_process` command learned to support specifying - the same file for ``OUTPUT_FILE`` and ``ERROR_FILE``. - -* The :command:`file(GLOB)` and :command:`file(GLOB_RECURSE)` commands - learned a new ``LIST_DIRECTORIES <bool>`` option to specify whether - the glob result should include directories. - -* The :command:`find_library`, :command:`find_path`, and :command:`find_file` - commands now search in installation prefixes derived from the ``PATH`` - environment variable. - -* The :command:`if` command learned a new ``IN_LIST`` operator that - evaluates to true if a given element is contained in a named list. - -* The :command:`install(EXPORT)` and :command:`export()` commands - learned to export targets that populate the :prop_tgt:`INTERFACE_SOURCES` - target property. - -* The :command:`install(TARGETS)` command learned to support - generator expressions in the ``DESTINATION`` value. - -Variables ---------- - -* The version of some Fortran compilers is now detected and stored in the - :variable:`CMAKE_Fortran_COMPILER_VERSION <CMAKE_<LANG>_COMPILER_VERSION>` - variable. - -* The :ref:`Visual Studio Generators` learned a new - :variable:`CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD` option - to put the ``INSTALL`` target in the default build of a - solution (``.sln``) file. - -Properties ----------- - -* A :prop_tgt:`CROSSCOMPILING_EMULATOR` target property and supporting - :variable:`CMAKE_CROSSCOMPILING_EMULATOR` variable were introduced - to allow target platform binaries to run on the host during cross - compiling. - -* A :prop_tgt:`<LANG>_INCLUDE_WHAT_YOU_USE` target property and supporting - :variable:`CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE` variable were introduced - to tell the :ref:`Makefile Generators` and the :generator:`Ninja` generator - to run ``include-what-you-use`` along with the compiler for ``C`` and - ``CXX`` languages. - -* The :prop_tgt:`<LANG>_VISIBILITY_PRESET` and - :prop_tgt:`VISIBILITY_INLINES_HIDDEN` target properties now - affect compilation in sources of all target types. See - policy :policy:`CMP0063`. - -* The :prop_tgt:`XCODE_ATTRIBUTE_<an-attribute>` target property learned - to support generator expressions. - -Modules -------- - -* The :module:`CheckFortranCompilerFlag` module was introduced - to check ``Fortran`` compiler flags, much like the - :module:`CheckCCompilerFlag` module already does for ``C``. - -* The :module:`ExternalData` module learned a new - :variable:`ExternalData_NO_SYMLINKS` option to disable use of - symbolic links to populate the real data files and use copies - instead. - -* The :module:`ExternalData` module learned a new ``RECURSE:`` - option in ``DATA{}`` references specifying directories. - This allows an entire directory tree of associated files - to be matched. - -* The :module:`ExternalData` module learned a new URL template - placeholder ``%(algo:<key>)`` to allow custom mapping from - algorithm name to URL component through configuration of new - :variable:`ExternalData_URL_ALGO_<algo>_<key>` variables. - This allows more flexibility in remote URLs. - -* The :module:`ExternalProject` module learned to replace tokens - like ``<BINARY_DIR>`` in the ``BYPRODUCTS`` of each step. - -* The :module:`ExternalProject` module APIs learned to support - :manual:`generator expressions <cmake-generator-expressions(7)>` - when using ``LOG_*`` options and in CMake initial cache options. - -* The :module:`FindBoost` module now tracks the directories containing - libraries separately for RELEASE and DEBUG configurations. - -* The :module:`FindCUDA` module now defaults to using the static - CUDA runtime library if it is available. A new - ``CUDA_USE_STATIC_CUDA_RUNTIME`` option is offered to control - this behavior. - -* The :module:`FindMatlab` module was completely rewritten. It learned - about versions and components and to find Matlab in a more precise and - multiplatform way. The module now offers APIs to create mex extensions, - documentation, and unit tests. - -* The :module:`FindPackageHandleStandardArgs` module - ``FIND_PACKAGE_HANDLE_STANDARD_ARGS`` function now - always populates both the ``<PackageName>_FOUND`` - and ``<UPPERCASE_NAME>_FOUND`` variables (the latter - for backwards compatibility). The ``FOUND_VAR`` - option is now ignored except to enforce its allowed - values. - -* The :module:`InstallRequiredSystemLibraries` module learned a new - ``CMAKE_INSTALL_SYSTEM_RUNTIME_COMPONENT`` option to specify the - installation component. - -Generator Expressions ---------------------- - -* A new ``COMPILE_LANGUAGE`` generator expression was introduced to - allow specification of compile options for target files based on the - :prop_sf:`LANGUAGE` of each source file. Due to limitations of the - underlying native build tools, this feature has varying support across - generators. See the :manual:`cmake-generator-expressions(7)` manual - for details. - -CTest ------ - -* The :manual:`ctest(1)` tool learned a new ``--repeat-until-fail <n>`` - option to help find sporadic test failures. - -* The :module:`CTestCoverageCollectGCOV` module learned to support - the same ``CTEST_CUSTOM_COVERAGE_EXCLUDE`` option as the - :command:`ctest_coverage` command. - -CPack ------ - -* The :cpack_gen:`CPack IFW Generator` learned to support - Qt Framework Installer 2.0 tools. - -* The :cpack_gen:`CPack DEB Generator` learned a new - :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_SHLIBDEPS` - variable to specify per-component use of ``dpkg-shlibdeps``. - -* The :cpack_gen:`CPack DEB Generator` learned a new - :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_DEPENDS` - option to specify per-component dependencies. - -* The :cpack_gen:`CPack RPM Generator` learned to package symbolic links - more cleanly and now supports directory symlinks with recent - ``rpmbuild`` versions. - -* The :cpack_gen:`CPack RPM Generator` learned a new - :variable:`CPACK_RPM_ADDITIONAL_MAN_DIRS` variable to specify - directories containing man pages for the brp-compress RPM macro. - -* The :cpack_gen:`CPack RPM Generator` learned a new - :variable:`CPACK_RPM_<component>_PACKAGE_ARCHITECTURE` variable - to specify a component-specific package architecture. - -* The CPack WIX generator learned the new - :prop_inst:`CPACK_START_MENU_SHORTCUTS`, - :prop_inst:`CPACK_DESKTOP_SHORTCUTS` and - :prop_inst:`CPACK_STARTUP_SHORTCUTS` installed file properties which can - be used to install shorcuts in the Start Menu, on the Desktop and - in the Startup Folder respectively. - -Other ------ - -* The :manual:`Compile Features <cmake-compile-features(7)>` functionality - is now aware of features supported by GNU compilers on Windows, versions - 4.4 through 5.0. - -* The :manual:`cmake(1)` ``-E tar`` command learned a new - ``--format<format>`` option to specify the archive format to - be written. - -* On OS X, CMake learned to create XCTest bundles to test Frameworks - and App Bundles within Xcode. The :module:`FindXCTest` module - provides convenience functions to handle :prop_tgt:`XCTEST` bundles. - -Deprecated and Removed Features -=============================== - -* On OS X the :manual:`cmake-gui(1)` no longer has the - ``Install For Command Line Use`` menu item. Instead there - is a ``How to Install For Command Line Use`` menu item - that shows an informational dialog box explaining how to - make the command line tools available. For example:: - - /Applications/CMake.app/Contents/bin/cmake-gui --install - -* The :command:`ctest_build` and :command:`build_command` commands - no longer tell ``make`` tools to ignore errors with the ``-i`` option. - Previously this was done for :ref:`Makefile Generators` but not others. - See policy :policy:`CMP0061`. - -* The :generator:`Visual Studio 10 2010` generator no longer checks - for running VS IDEs with the project open or asks them to reload. - This was originally done for VS 10 because it had been done for - VS 7 through 9 to avoid prompting for every project in a solution. - Since VS >= 10 allow the whole solution to reload at once they - do not need CMake to help them. - -* The :generator:`Visual Studio 7` generator (.NET 2002) is now - deprecated and will be removed in a future version of CMake. - -* The :generator:`Visual Studio 6` generator is now deprecated - and will be removed in a future version of CMake. - -* The :command:`find_package` command no longer considers project - build trees recently configured in a :manual:`cmake-gui(1)`. - This was previously done only on Windows and is now never done. - The ``NO_CMAKE_BUILDS_PATH`` option is now ignored if given - and effectively always on. - Projects may populate the :ref:`User Package Registry` to aid - users building multiple dependent projects one after another. - -* The :command:`add_definitions()` command no longer causes a - :prop_dir:`DEFINITIONS` directory property to be populated. See policy - :policy:`CMP0059`. - -* With Visual Studio 7, 8, and 9 generators the value of the ``$(OutDir)`` - placeholder no longer evaluates to the configuration name. Projects - should use ``$(ConfigurationName)`` for that instead. - -* Using the output of :command:`export()` with the :command:`install(FILES)` - command is no longer allowed. See policy :policy:`CMP0062` for details. - -Other Changes -============= - -* The :generator:`Ninja` generator now requires that calls to the - :command:`add_custom_command` and :command:`add_custom_target` - commands use the ``BYPRODUCTS`` option to explicitly specify any - files generated by the custom commands that are not listed as - outputs (perhaps because their timestamps are allowed to be older - than the inputs). See policy :policy:`CMP0058`. - -* Build-time progress output of :ref:`Makefile Generators` has been improved. - It no longer mixes progress and build rule messages during parallel builds. - The link rule messages now have progress and are displayed as bold green - instead of bold red (since red is often associated with an error message). - -* The :variable:`CMAKE_CFG_INTDIR` variable value for Visual Studio - 7, 8, and 9 is now ``$(ConfigurationName)`` instead of ``$(OutDir)``. - This should have no effect on the intended use cases of the variable. - -* Linking to library files by a full path in an implicit linker search - directory (e.g. ``/usr/lib/libfoo.a``) no longer asks the linker to - search for the library (e.g. ``-lfoo``) and now links by full path. - See policy :policy:`CMP0060`.
diff --git a/share/cmake-3.18/Help/release/3.6.rst b/share/cmake-3.18/Help/release/3.6.rst deleted file mode 100644 index f0add07..0000000 --- a/share/cmake-3.18/Help/release/3.6.rst +++ /dev/null
@@ -1,318 +0,0 @@ -CMake 3.6 Release Notes -*********************** - -.. only:: html - - .. contents:: - -Changes made since CMake 3.5 include the following. - -New Features -============ - -Generators ----------- - -* The :generator:`Ninja` generator learned to produce phony targets - of the form ``sub/dir/all`` to drive the build of a subdirectory. - This is equivalent to ``cd sub/dir; make all`` with - :ref:`Makefile Generators`. - -* The :generator:`Ninja` generator now includes system header files in build - dependencies to ensure correct re-builds when system packages are updated. - -* The :generator:`Visual Studio 14 2015` generator learned to support the - Clang/C2 toolsets, e.g. with the ``-T v140_clang_3_7`` option. - This feature is experimental. - -Commands --------- - -* The :command:`add_custom_command` and :command:`add_custom_target` commands - learned how to use the :prop_tgt:`CROSSCOMPILING_EMULATOR` executable - target property. - -* The :command:`install` command learned a new ``EXCLUDE_FROM_ALL`` option - to leave installation rules out of the default installation. - -* The :command:`list` command gained a ``FILTER`` sub-command to filter - list elements by regular expression. - -* The :command:`string(TIMESTAMP)` and :command:`file(TIMESTAMP)` - commands gained support for the ``%s`` placeholder. This is - the number of seconds since the UNIX Epoch. - -Variables ---------- - -* A :variable:`CMAKE_DEPENDS_IN_PROJECT_ONLY` variable was introduced - to tell :ref:`Makefile Generators` to limit dependency scanning only - to files in the project source and build trees. - -* A new :variable:`CMAKE_HOST_SOLARIS` variable was introduced to - indicate when CMake is running on an Oracle Solaris host. - -* A :variable:`CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES` variable was - added for use by toolchain files to specify system include directories - to be appended to all compiler command lines. - -* The :variable:`CMAKE_<LANG>_STANDARD_LIBRARIES` variable is now documented. - It is intended for use by toolchain files to specify system libraries to be - added to all linker command lines. - -* A :variable:`CMAKE_NINJA_OUTPUT_PATH_PREFIX` variable was introduced - to tell the :generator:`Ninja` generator to configure the generated - ``build.ninja`` file for use as a ``subninja``. - -* A :variable:`CMAKE_TRY_COMPILE_PLATFORM_VARIABLES` variable was - added for use by toolchain files to specify platform-specific - variables that must be propagated by the :command:`try_compile` - command into test projects. - -* A :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` variable was added - to optionally tell the :command:`try_compile` command to build - a static library instead of an executable. This is useful for - cross-compiling toolchains that cannot link binaries without - custom flags or scripts. - -Properties ----------- - -* A :prop_tgt:`DEPLOYMENT_REMOTE_DIRECTORY` target property was introduced - to tell the :generator:`Visual Studio 9 2008` and - :generator:`Visual Studio 8 2005` generators to generate the "remote - directory" for WinCE project deployment and debugger settings. - -* A :prop_tgt:`<LANG>_CLANG_TIDY` target property and supporting - :variable:`CMAKE_<LANG>_CLANG_TIDY` variable were introduced to tell the - :ref:`Makefile Generators` and the :generator:`Ninja` generator to run - ``clang-tidy`` along with the compiler for ``C`` and ``CXX`` languages. - -* A :prop_test:`TIMEOUT_AFTER_MATCH` test property was introduced to - optionally tell CTest to enforce a secondary timeout after matching - certain output from a test. - -* A :prop_tgt:`VS_CONFIGURATION_TYPE` target property was introduced - to specify a custom project file type for :ref:`Visual Studio Generators` - supporting VS 2010 and above. - -* A :prop_dir:`VS_STARTUP_PROJECT` directory property was introduced - to specify for :ref:`Visual Studio Generators` the default startup - project for generated solutions (``.sln`` files). - -Modules -------- - -* The :module:`CMakePushCheckState` module now pushes/pops/resets the variable - ``CMAKE_EXTRA_INCLUDE_FILE`` used in :module:`CheckTypeSize`. - -* The :module:`ExternalProject` module leared the ``GIT_SHALLOW 1`` - option to perform a shallow clone of a Git repository. - -* The :module:`ExternalProject` module learned to initialize Git submodules - recursively and also to initialize new submodules on updates. Use the - ``GIT_SUBMODULES`` option to restrict which submodules are initialized and - updated. - -* The :module:`ExternalProject` module leared the ``DOWNLOAD_NO_EXTRACT 1`` - argument to skip extracting the file that is downloaded (e.g., for - self-extracting shell installers or ``.msi`` files). - -* The :module:`ExternalProject` module now uses ``TLS_VERIFY`` when fetching - from git repositories. - -* The :module:`FindBLAS` and :module:`FindLAPACK` modules learned to - support `OpenBLAS <http://www.openblas.net>`__. - -* The :module:`FindCUDA` module learned to find the ``cublas_device`` library. - -* The :module:`FindGTest` module ``gtest_add_tests`` function now causes - CMake to automatically re-run when test sources change so that they - can be re-scanned. - -* The :module:`FindLTTngUST` module was introduced to find the LTTng-UST - library. - -* The :module:`FindPkgConfig` module learned to optionally create imported - targets for the libraries it has found. - -* The :module:`FindProtobuf` module learned to provide a ``Protobuf_VERSION`` - variable and check the version number requested in a :command:`find_package` - call. - -* The :module:`InstallRequiredSystemLibraries` module learned a new - ``CMAKE_INSTALL_UCRT_LIBRARIES`` option to enable app-local deployment - of the Windows Universal CRT libraries with Visual Studio 2015. - -Platforms ---------- - -* The Clang compiler is now supported on CYGWIN. - -* Support was added for the Bruce C Compiler with compiler id ``Bruce``. - -CTest ------ - -* The :command:`ctest_update` command now looks at the - :variable:`CTEST_GIT_INIT_SUBMODULES` variable to determine whether - submodules should be updated or not before updating. - -* The :command:`ctest_update` command will now synchronize submodules on an - update. Updates which add submodules or change a submodule's URL will now be - pulled properly. - -CPack ------ - -* The :cpack_gen:`CPack DEB Generator` learned how to handle ``$ORIGIN`` - in ``CMAKE_INSTALL_RPATH`` when :variable:`CPACK_DEBIAN_PACKAGE_SHLIBDEPS` - is used for dependency auto detection. - -* The :cpack_gen:`CPack DEB Generator` learned how to generate - ``DEBIAN/shlibs`` contorl file when package contains shared libraries. - -* The :cpack_gen:`CPack DEB Generator` learned how to generate - ``DEBIAN/postinst`` and ``DEBIAN/postrm`` files if the package installs - libraries in ldconfig-controlled locations (e.g. ``/lib/``, ``/usr/lib/``). - -* The :cpack_gen:`CPack DEB Generator` learned how to generate dependencies - between Debian packages if multi-component setup is used and - :variable:`CPACK_COMPONENT_<compName>_DEPENDS` variables are set. - For backward compatibility this feature is disabled by default. - See :variable:`CPACK_DEBIAN_ENABLE_COMPONENT_DEPENDS`. - -* The :cpack_gen:`CPack DEB Generator` learned how to set custom package - file names including how to generate properly-named Debian packages:: - - <PackageName>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb - - For backward compatibility this feature is disabled by default. See - :variable:`CPACK_DEBIAN_FILE_NAME` and - :variable:`CPACK_DEBIAN_<COMPONENT>_FILE_NAME`. - -* The :cpack_gen:`CPack DEB Generator` learned how to set the package - release number (``DebianRevisionNumber`` in package file name when - used in combination with ``DEB-DEFAULT`` value set by - :variable:`CPACK_DEBIAN_FILE_NAME`). - See :variable:`CPACK_DEBIAN_PACKAGE_RELEASE`. - -* The :cpack_gen:`CPack DEB Generator` learned how to set the package - architecture per-component. - See :variable:`CPACK_DEBIAN_<COMPONENT>_PACKAGE_ARCHITECTURE`. - -* The :cpack_gen:`CPack DragNDrop Generator` learned a new option to skip the - ``/Applications`` symlink. - See the :variable:`CPACK_DMG_DISABLE_APPLICATIONS_SYMLINK` variable. - -* The :module:`CPackIFW` module gained a new - :command:`cpack_ifw_update_repository` command to update a QtIFW-specific - repository from a remote repository. - -* The :cpack_gen:`CPack RPM Generator` learned how to set RPM ``dist`` tag - as part of RPM ``Release:`` tag when enabled (mandatory on some Linux - distributions for e.g. on Fedora). - See :variable:`CPACK_RPM_PACKAGE_RELEASE_DIST`. - -* The :cpack_gen:`CPack RPM Generator` learned how to set default values - for owning user/group and file/directory permissions of package content. - See :variable:`CPACK_RPM_DEFAULT_USER`, :variable:`CPACK_RPM_DEFAULT_GROUP`, - :variable:`CPACK_RPM_DEFAULT_FILE_PERMISSIONS`, - :variable:`CPACK_RPM_DEFAULT_DIR_PERMISSIONS` and their per component - counterparts. - -* The :cpack_gen:`CPack RPM Generator` learned how to set user defined - package file names, how to specify that rpmbuild should decide on file - name format as well as handling of multiple rpm packages generated by a - single user defined spec file. - See :variable:`CPACK_RPM_PACKAGE_NAME` and - :variable:`CPACK_RPM_<component>_PACKAGE_NAME`. - -* The :cpack_gen:`CPack RPM Generator` learned how to correctly handle symlinks - that are pointing outside generated packages. - -Other ------ - -* The :manual:`Compile Features <cmake-compile-features(7)>` functionality - is now aware of features supported by Intel C++ compilers versions 12.1 - through 16.0 on UNIX platforms. - -Deprecated and Removed Features -=============================== - -* The :module:`CMakeForceCompiler` module and its macros are now deprecated. - See module documentation for an explanation. - -* The :command:`find_library`, :command:`find_path`, and :command:`find_file` - commands no longer search in installation prefixes derived from the ``PATH`` - environment variable on non-Windows platforms. This behavior was added in - CMake 3.3 to support Windows hosts but has proven problematic on UNIX hosts. - Users that keep some ``<prefix>/bin`` directories in the ``PATH`` just for - their tools do not necessarily want any supporting ``<prefix>/lib`` - directories searched. One may set the ``CMAKE_PREFIX_PATH`` environment - variable with a :ref:`semicolon-separated list <CMake Language Lists>` of prefixes that are - to be searched. - -* The :generator:`Visual Studio 7 .NET 2003` generator is now - deprecated and will be removed in a future version of CMake. - -* The :generator:`Visual Studio 7` generator (for VS .NET 2002) has been - removed. It had been deprecated since CMake 3.3. - -* The :generator:`Visual Studio 6` generator has been removed. - It had been deprecated since CMake 3.3. - -Other Changes -============= - -* The precompiled OS X binary provided on ``cmake.org`` now requires - OS X 10.7 or newer. - -* On Linux and FreeBSD platforms, when building CMake itself from source and - not using a system-provided libcurl, OpenSSL is now used by default if it is - found on the system. This enables SSL/TLS support for commands supporting - network communication via ``https``, such as :command:`file(DOWNLOAD)`, - :command:`file(UPLOAD)`, and :command:`ctest_submit`. - -* The :manual:`cmake(1)` ``--build`` command-line tool now rejects multiple - ``--target`` options with an error instead of silently ignoring all but the - last one. - -* :prop_tgt:`AUTOMOC` now diagnoses name collisions when multiple source - files in different directories use ``#include <moc_foo.cpp>`` with the - same name (because the generated ``moc_foo.cpp`` files would collide). - -* The :module:`FindBISON` module ``BISON_TARGET`` macro now supports - special characters by passing the ``VERBATIM`` option to internal - :command:`add_custom_command` calls. This may break clients that - added escaping manually to work around the bug. - -* The :module:`FindFLEX` module ``FLEX_TARGET`` macro now supports - special characters by passing the ``VERBATIM`` option to internal - :command:`add_custom_command` calls. This may break clients that - added escaping manually to work around the bug. - -* The :module:`FindProtobuf` module input and output variables were all renamed - from ``PROTOBUF_`` to ``Protobuf_`` for consistency with other find modules. - Input variables of the old case will be honored if provided, and output - variables of the old case are always provided. - -* The :cpack_gen:`CPack RPM Generator` now supports upper cased component - names in per component CPackRPM specific variables. - E.g. component named ``foo`` now expects component specific - variable to be ``CPACK_RPM_FOO_PACKAGE_NAME`` while before - it expected ``CPACK_RPM_foo_PACKAGE_NAME``. - Upper cased component name part in variables is compatible - with convention used for other CPack variables. - For back compatibility old format of variables is still valid - and preferred if both versions of variable are set, but the - preferred future use is upper cased component names in variables. - New variables that will be added to CPackRPM in later versions - will only support upper cased component variable format. - -* The CPack NSIS generator's configuration file template was fixed to - quote the path to the uninstaller tool used by the - :variable:`CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL` option. - This avoids depending on an insecure Windows feature to run an - uninstaller tool with a space in the path.
diff --git a/share/cmake-3.18/Help/release/index.rst b/share/cmake-3.18/Help/release/index.rst deleted file mode 100644 index 4578b3a..0000000 --- a/share/cmake-3.18/Help/release/index.rst +++ /dev/null
@@ -1,34 +0,0 @@ -:orphan: - -CMake Release Notes -******************* - -.. - This file should include the adjacent "dev.txt" file - in development versions but not in release versions. - -Releases -======== - -.. toctree:: - :maxdepth: 1 - - 3.18 <3.18> - 3.17 <3.17> - 3.16 <3.16> - 3.15 <3.15> - 3.14 <3.14> - 3.13 <3.13> - 3.12 <3.12> - 3.11 <3.11> - 3.10 <3.10> - 3.9 <3.9> - 3.8 <3.8> - 3.7 <3.7> - 3.6 <3.6> - 3.5 <3.5> - 3.4 <3.4> - 3.3 <3.3> - 3.2 <3.2> - 3.1 <3.1> - 3.0 <3.0>
diff --git a/share/cmake-3.18/Help/variable/ANDROID.rst b/share/cmake-3.18/Help/variable/ANDROID.rst deleted file mode 100644 index fede4ca..0000000 --- a/share/cmake-3.18/Help/variable/ANDROID.rst +++ /dev/null
@@ -1,5 +0,0 @@ -ANDROID -------- - -Set to ``1`` when the target system (:variable:`CMAKE_SYSTEM_NAME`) is -``Android``.
diff --git a/share/cmake-3.18/Help/variable/CACHE.rst b/share/cmake-3.18/Help/variable/CACHE.rst deleted file mode 100644 index 2cef27e..0000000 --- a/share/cmake-3.18/Help/variable/CACHE.rst +++ /dev/null
@@ -1,18 +0,0 @@ -CACHE ------ - -Operator to read cache variables. - -Use the syntax ``$CACHE{VAR}`` to read cache entry ``VAR``. -See the :ref:`cmake-language(7) variables <CMake Language Variables>` -documentation for more complete documentation of the interaction of -normal variables and cache entries. - -When evaluating :ref:`Variable References` of the form ``${VAR}``, -CMake first searches for a normal variable with that name, and if not -found CMake will search for a cache entry with that name. -The ``$CACHE{VAR}`` syntax can be used to do direct cache lookup and -ignore any existing normal variable. - -See the :command:`set` and :command:`unset` commands to see how to -write or remove cache variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.rst b/share/cmake-3.18/Help/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.rst deleted file mode 100644 index c64dd48..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_AIX_EXPORT_ALL_SYMBOLS ----------------------------- - -Default value for :prop_tgt:`AIX_EXPORT_ALL_SYMBOLS` target property. -This variable is used to initialize the property on each target as it is -created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.rst deleted file mode 100644 index 8862ba9..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS ------------------------------------- - -Default value for the :prop_tgt:`ANDROID_ANT_ADDITIONAL_OPTIONS` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API.rst deleted file mode 100644 index c07a05a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_ANDROID_API ------------------ - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this variable may be set to specify the default value for the -:prop_tgt:`ANDROID_API` target property. See that target property for -additional information. - -Otherwise, when :ref:`Cross Compiling for Android`, this variable provides -the Android API version number targeted. This will be the same value as -the :variable:`CMAKE_SYSTEM_VERSION` variable for ``Android`` platforms.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API_MIN.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API_MIN.rst deleted file mode 100644 index 0246c75..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_API_MIN.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_API_MIN ---------------------- - -Default value for the :prop_tgt:`ANDROID_API_MIN` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH.rst deleted file mode 100644 index b91ca57..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMAKE_ANDROID_ARCH ------------------- - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this variable may be set to specify the default value for the -:prop_tgt:`ANDROID_ARCH` target property. See that target property for -additional information. - -Otherwise, when :ref:`Cross Compiling for Android`, this variable provides -the name of the Android architecture corresponding to the value of the -:variable:`CMAKE_ANDROID_ARCH_ABI` variable. The architecture name -may be one of: - -* ``arm`` -* ``arm64`` -* ``mips`` -* ``mips64`` -* ``x86`` -* ``x86_64``
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH_ABI.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH_ABI.rst deleted file mode 100644 index 0a3ed3c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARCH_ABI.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_ANDROID_ARCH_ABI ----------------------- - -When :ref:`Cross Compiling for Android`, this variable specifies the -target architecture and ABI to be used. Valid values are: - -* ``arm64-v8a`` -* ``armeabi-v7a`` -* ``armeabi-v6`` -* ``armeabi`` -* ``mips`` -* ``mips64`` -* ``x86`` -* ``x86_64`` - -See also the :variable:`CMAKE_ANDROID_ARM_MODE` and -:variable:`CMAKE_ANDROID_ARM_NEON` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_MODE.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_MODE.rst deleted file mode 100644 index ad3c37c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_MODE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_ANDROID_ARM_MODE ----------------------- - -When :ref:`Cross Compiling for Android` and :variable:`CMAKE_ANDROID_ARCH_ABI` -is set to one of the ``armeabi`` architectures, set ``CMAKE_ANDROID_ARM_MODE`` -to ``ON`` to target 32-bit ARM processors (``-marm``). Otherwise, the -default is to target the 16-bit Thumb processors (``-mthumb``).
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_NEON.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_NEON.rst deleted file mode 100644 index 4b7ae03..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ARM_NEON.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_ANDROID_ARM_NEON ----------------------- - -When :ref:`Cross Compiling for Android` and :variable:`CMAKE_ANDROID_ARCH_ABI` -is set to ``armeabi-v7a`` set ``CMAKE_ANDROID_ARM_NEON`` to ``ON`` to target -ARM NEON devices.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ASSETS_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ASSETS_DIRECTORIES.rst deleted file mode 100644 index c372fe4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_ASSETS_DIRECTORIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_ASSETS_DIRECTORIES --------------------------------- - -Default value for the :prop_tgt:`ANDROID_ASSETS_DIRECTORIES` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_GUI.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_GUI.rst deleted file mode 100644 index 1755375..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_GUI.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_GUI ------------------ - -Default value for the :prop_tgt:`ANDROID_GUI` target property of -executables. See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DEPENDENCIES.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DEPENDENCIES.rst deleted file mode 100644 index 451a929..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DEPENDENCIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_JAR_DEPENDENCIES ------------------------------- - -Default value for the :prop_tgt:`ANDROID_JAR_DEPENDENCIES` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DIRECTORIES.rst deleted file mode 100644 index af83e34..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAR_DIRECTORIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_JAR_DIRECTORIES ------------------------------ - -Default value for the :prop_tgt:`ANDROID_JAR_DIRECTORIES` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.rst deleted file mode 100644 index 3dc05e0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_JAVA_SOURCE_DIR ------------------------------ - -Default value for the :prop_tgt:`ANDROID_JAVA_SOURCE_DIR` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.rst deleted file mode 100644 index 4191907..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES -------------------------------------- - -Default value for the :prop_tgt:`ANDROID_NATIVE_LIB_DEPENDENCIES` target -property. See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.rst deleted file mode 100644 index 7cb9527..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES ------------------------------------- - -Default value for the :prop_tgt:`ANDROID_NATIVE_LIB_DIRECTORIES` target -property. See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK.rst deleted file mode 100644 index d241dd0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_ANDROID_NDK ------------------ - -When :ref:`Cross Compiling for Android with the NDK`, this variable holds -the absolute path to the root directory of the NDK. The directory must -contain a ``platforms`` subdirectory holding the ``android-<api>`` -directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.rst deleted file mode 100644 index 8ea1257..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_ANDROID_NDK_DEPRECATED_HEADERS ------------------------------------- - -When :ref:`Cross Compiling for Android with the NDK`, this variable -may be set to specify whether to use the deprecated per-api-level -headers instead of the unified headers. - -If not specified, the default will be *false* if using a NDK version -that provides the unified headers and *true* otherwise.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG.rst deleted file mode 100644 index 207019a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG ------------------------------------- - -When :ref:`Cross Compiling for Android with the NDK`, this variable -provides the NDK's "host tag" used to construct the path to prebuilt -toolchains that run on the host.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION.rst deleted file mode 100644 index 22808e3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION ------------------------------------ - -When :ref:`Cross Compiling for Android with the NDK`, this variable -may be set to specify the version of the toolchain to be used -as the compiler. - -On NDK r19 or above, this variable must be unset or set to ``clang``. - -On NDK r18 or below, this variable must be set to one of these forms: - -* ``<major>.<minor>``: GCC of specified version -* ``clang<major>.<minor>``: Clang of specified version -* ``clang``: Clang of most recent available version - -A toolchain of the requested version will be selected automatically to -match the ABI named in the :variable:`CMAKE_ANDROID_ARCH_ABI` variable. - -If not specified, the default will be a value that selects the latest -available GCC toolchain.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROCESS_MAX.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROCESS_MAX.rst deleted file mode 100644 index 19fb527..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROCESS_MAX.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_PROCESS_MAX -------------------------- - -Default value for the :prop_tgt:`ANDROID_PROCESS_MAX` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD.rst deleted file mode 100644 index b8fdd46..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_PROGUARD ----------------------- - -Default value for the :prop_tgt:`ANDROID_PROGUARD` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.rst deleted file mode 100644 index 8dea009..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_PROGUARD_CONFIG_PATH ----------------------------------- - -Default value for the :prop_tgt:`ANDROID_PROGUARD_CONFIG_PATH` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.rst deleted file mode 100644 index 69a4d0b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_SECURE_PROPS_PATH -------------------------------- - -Default value for the :prop_tgt:`ANDROID_SECURE_PROPS_PATH` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SKIP_ANT_STEP.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SKIP_ANT_STEP.rst deleted file mode 100644 index 0a96df9..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_SKIP_ANT_STEP.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_ANDROID_SKIP_ANT_STEP ---------------------------- - -Default value for the :prop_tgt:`ANDROID_SKIP_ANT_STEP` target property. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.rst deleted file mode 100644 index ea62cab..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_ANDROID_STANDALONE_TOOLCHAIN ----------------------------------- - -When :ref:`Cross Compiling for Android with a Standalone Toolchain`, this -variable holds the absolute path to the root directory of the toolchain. -The specified directory must contain a ``sysroot`` subdirectory.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STL_TYPE.rst b/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STL_TYPE.rst deleted file mode 100644 index d174575..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ANDROID_STL_TYPE.rst +++ /dev/null
@@ -1,37 +0,0 @@ -CMAKE_ANDROID_STL_TYPE ----------------------- - -When :ref:`Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio -Edition`, this variable may be set to specify the default value for the -:prop_tgt:`ANDROID_STL_TYPE` target property. See that target property -for additional information. - -When :ref:`Cross Compiling for Android with the NDK`, this variable may be -set to specify the STL variant to be used. The value may be one of: - -``none`` - No C++ Support -``system`` - Minimal C++ without STL -``gabi++_static`` - GAbi++ Static -``gabi++_shared`` - GAbi++ Shared -``gnustl_static`` - GNU libstdc++ Static -``gnustl_shared`` - GNU libstdc++ Shared -``c++_static`` - LLVM libc++ Static -``c++_shared`` - LLVM libc++ Shared -``stlport_static`` - STLport Static -``stlport_shared`` - STLport Shared - -The default value is ``gnustl_static`` on NDK versions that provide it -and otherwise ``c++_static``. Note that this default differs from -the native NDK build system because CMake may be used to build projects for -Android that are not natively implemented for it and use the C++ standard -library.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.rst deleted file mode 100644 index 94c2b6e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> ---------------------------------------- - -Where to put all the :ref:`ARCHIVE <Archive Output Artifacts>` -target files when built for a specific configuration. - -This variable is used to initialize the -:prop_tgt:`ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>` property on all the targets. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_ORIGIN_DEPENDS.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_ORIGIN_DEPENDS.rst deleted file mode 100644 index 1398e78..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_ORIGIN_DEPENDS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_AUTOGEN_ORIGIN_DEPENDS ----------------------------- - -Switch for forwarding origin target dependencies to the corresponding -``_autogen`` targets. - -This variable is used to initialize the :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` -property on all the targets. See that target property for additional -information. - -By default :variable:`CMAKE_AUTOGEN_ORIGIN_DEPENDS` is ``ON``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_PARALLEL.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_PARALLEL.rst deleted file mode 100644 index dd9499a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_PARALLEL.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_AUTOGEN_PARALLEL ----------------------- - -Number of parallel ``moc`` or ``uic`` processes to start when using -:prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`. - -This variable is used to initialize the :prop_tgt:`AUTOGEN_PARALLEL` property -on all the targets. See that target property for additional information. - -By default :variable:`CMAKE_AUTOGEN_PARALLEL` is unset.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_VERBOSE.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_VERBOSE.rst deleted file mode 100644 index bad9cf2..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOGEN_VERBOSE.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_AUTOGEN_VERBOSE ---------------------- - -Sets the verbosity of :prop_tgt:`AUTOMOC`, :prop_tgt:`AUTOUIC` and -:prop_tgt:`AUTORCC`. A positive integer value or a true boolean value -lets the ``AUTO*`` generators output additional processing information. - -Setting :variable:`CMAKE_AUTOGEN_VERBOSE` has the same effect -as setting the ``VERBOSE`` environment variable during -generation (e.g. by calling ``make VERBOSE=1``). -The extra verbosity is limited to the ``AUTO*`` generators though. - -By default :variable:`CMAKE_AUTOGEN_VERBOSE` is unset.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.rst deleted file mode 100644 index 7e1c53d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_AUTOMOC_COMPILER_PREDEFINES ---------------------------------- - -This variable is used to initialize the :prop_tgt:`AUTOMOC_COMPILER_PREDEFINES` -property on all the targets. See that target property for additional -information. - -By default it is ON.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_DEPEND_FILTERS.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_DEPEND_FILTERS.rst deleted file mode 100644 index 5c3662d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_DEPEND_FILTERS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_AUTOMOC_DEPEND_FILTERS ----------------------------- - -Filter definitions used by :variable:`CMAKE_AUTOMOC` -to extract file names from source code as additional dependencies -for the ``moc`` file. - -This variable is used to initialize the :prop_tgt:`AUTOMOC_DEPEND_FILTERS` -property on all the targets. See that target property for additional -information. - -By default it is empty.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_MACRO_NAMES.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_MACRO_NAMES.rst deleted file mode 100644 index ba1b9d2..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_MACRO_NAMES.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_AUTOMOC_MACRO_NAMES ----------------------------- - -:ref:`Semicolon-separated list <CMake Language Lists>` list of macro names used by -:variable:`CMAKE_AUTOMOC` to determine if a C++ file needs to be -processed by ``moc``. - -This variable is used to initialize the :prop_tgt:`AUTOMOC_MACRO_NAMES` -property on all the targets. See that target property for additional -information. - -The default value is ``Q_OBJECT;Q_GADGET;Q_NAMESPACE``. - -Example -^^^^^^^ -Let CMake know that source files that contain ``CUSTOM_MACRO`` must be ``moc`` -processed as well:: - - set(CMAKE_AUTOMOC ON) - list(APPEND CMAKE_AUTOMOC_MACRO_NAMES "CUSTOM_MACRO")
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_PATH_PREFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_PATH_PREFIX.rst deleted file mode 100644 index dca0b06..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_PATH_PREFIX.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_AUTOMOC_PATH_PREFIX -------------------------- - -Whether to generate the ``-p`` path prefix option for ``moc`` on -:prop_tgt:`AUTOMOC` enabled Qt targets. - -This variable is used to initialize the :prop_tgt:`AUTOMOC_PATH_PREFIX` -property on all the targets. See that target property for additional -information. - -The default value is ``ON``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_RELAXED_MODE.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_RELAXED_MODE.rst deleted file mode 100644 index 6c0c61b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOMOC_RELAXED_MODE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_AUTOMOC_RELAXED_MODE --------------------------- - -.. deprecated:: 3.15 - -Switch between strict and relaxed automoc mode. - -By default, :prop_tgt:`AUTOMOC` behaves exactly as described in the -documentation of the :prop_tgt:`AUTOMOC` target property. When set to -``TRUE``, it accepts more input and tries to find the correct input file for -``moc`` even if it differs from the documented behaviour. In this mode it -e.g. also checks whether a header file is intended to be processed by moc -when a ``"foo.moc"`` file has been included. - -Relaxed mode has to be enabled for KDE4 compatibility.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_AUTOUIC_SEARCH_PATHS.rst b/share/cmake-3.18/Help/variable/CMAKE_AUTOUIC_SEARCH_PATHS.rst deleted file mode 100644 index aa132bf..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_AUTOUIC_SEARCH_PATHS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_AUTOUIC_SEARCH_PATHS --------------------------- - -Search path list used by :variable:`CMAKE_AUTOUIC` to find included -``.ui`` files. - -This variable is used to initialize the :prop_tgt:`AUTOUIC_SEARCH_PATHS` -property on all the targets. See that target property for additional -information. - -By default it is empty.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH.rst b/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH.rst deleted file mode 100644 index f5d53b8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_BUILD_RPATH ------------------ - -:ref:`Semicolon-separated list <CMake Language Lists>` specifying runtime path (``RPATH``) -entries to add to binaries linked in the build tree (for platforms that -support it). The entries will *not* be used for binaries in the install -tree. See also the :variable:`CMAKE_INSTALL_RPATH` variable. - -This is used to initialize the :prop_tgt:`BUILD_RPATH` target property -for all targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.rst b/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.rst deleted file mode 100644 index e34ede6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_BUILD_RPATH_USE_ORIGIN ----------------------------- - -Whether to use relative paths for the build ``RPATH``. - -This is used to initialize the :prop_tgt:`BUILD_RPATH_USE_ORIGIN` target -property for all targets, see that property for more details.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_BUILD_TYPE.rst b/share/cmake-3.18/Help/variable/CMAKE_BUILD_TYPE.rst deleted file mode 100644 index 2d35635..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_BUILD_TYPE.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_BUILD_TYPE ----------------- - -Specifies the build type on single-configuration generators. - -This statically specifies what build type (configuration) will be -built in this build tree. Possible values are empty, ``Debug``, ``Release``, -``RelWithDebInfo``, ``MinSizeRel``, ... This variable is only meaningful to -single-configuration generators (such as :ref:`Makefile Generators` and -:generator:`Ninja`) i.e. those which choose a single configuration when CMake -runs to generate a build tree as opposed to multi-configuration generators -which offer selection of the build configuration within the generated build -environment. There are many per-config properties and variables -(usually following clean ``SOME_VAR_<CONFIG>`` order conventions), such as -``CMAKE_C_FLAGS_<CONFIG>``, specified as uppercase: -``CMAKE_C_FLAGS_[DEBUG|RELEASE|RELWITHDEBINFO|MINSIZEREL|...]``. For example, -in a build tree configured to build type ``Debug``, CMake will see to -having :variable:`CMAKE_C_FLAGS_DEBUG <CMAKE_<LANG>_FLAGS_DEBUG>` settings get -added to the :variable:`CMAKE_C_FLAGS <CMAKE_<LANG>_FLAGS>` settings. See -also :variable:`CMAKE_CONFIGURATION_TYPES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.rst b/share/cmake-3.18/Help/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.rst deleted file mode 100644 index 30d5d3b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_BUILD_WITH_INSTALL_NAME_DIR ---------------------------------- - -Whether to use :prop_tgt:`INSTALL_NAME_DIR` on targets in the build tree. - -This variable is used to initialize the :prop_tgt:`BUILD_WITH_INSTALL_NAME_DIR` -property on all targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CFG_INTDIR.rst b/share/cmake-3.18/Help/variable/CMAKE_CFG_INTDIR.rst deleted file mode 100644 index 842654e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CFG_INTDIR.rst +++ /dev/null
@@ -1,52 +0,0 @@ -CMAKE_CFG_INTDIR ----------------- - -Build-time reference to per-configuration output subdirectory. - -For native build systems supporting multiple configurations in the -build tree (such as :ref:`Visual Studio Generators` and :generator:`Xcode`), -the value is a reference to a build-time variable specifying the name -of the per-configuration output subdirectory. On :ref:`Makefile Generators` -this evaluates to `.` because there is only one configuration in a build tree. -Example values: - -:: - - $(ConfigurationName) = Visual Studio 9 - $(Configuration) = Visual Studio 10 - $(CONFIGURATION) = Xcode - . = Make-based tools - . = Ninja - ${CONFIGURATION} = Ninja Multi-Config - -Note that this variable only has limited support on -:generator:`Ninja Multi-Config`. It is recommended that you use the -``$<CONFIG>`` :manual:`generator expression <cmake-generator-expressions(7)>` -instead. - -Since these values are evaluated by the native build system, this -variable is suitable only for use in command lines that will be -evaluated at build time. Example of intended usage: - -:: - - add_executable(mytool mytool.c) - add_custom_command( - OUTPUT out.txt - COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool - ${CMAKE_CURRENT_SOURCE_DIR}/in.txt out.txt - DEPENDS mytool in.txt - ) - add_custom_target(drive ALL DEPENDS out.txt) - -Note that ``CMAKE_CFG_INTDIR`` is no longer necessary for this purpose but -has been left for compatibility with existing projects. Instead -:command:`add_custom_command` recognizes executable target names in its -``COMMAND`` option, so -``${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool`` can be replaced -by just ``mytool``. - -This variable is read-only. Setting it is undefined behavior. In -multi-configuration build systems the value of this variable is passed -as the value of preprocessor symbol ``CMAKE_INTDIR`` to the compilation -of all source files.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_COMPILER_ID.rst b/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_COMPILER_ID.rst deleted file mode 100644 index ad2709d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_COMPILER_ID.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_CODEBLOCKS_COMPILER_ID ----------------------------- - -Change the compiler id in the generated CodeBlocks project files. - -CodeBlocks uses its own compiler id string which differs from -:variable:`CMAKE_<LANG>_COMPILER_ID`. If this variable is left empty, -CMake tries to recognize the CodeBlocks compiler id automatically. -Otherwise the specified string is used in the CodeBlocks project file. -See the CodeBlocks documentation for valid compiler id strings. - -Other IDEs like QtCreator that also use the CodeBlocks generator may ignore -this setting.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.rst b/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.rst deleted file mode 100644 index 80ffce3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES ---------------------------------------- - -Change the way the CodeBlocks generator creates project files. - -If this variable evaluates to ``ON`` the generator excludes from -the project file any files that are located outside the project root.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CODELITE_USE_TARGETS.rst b/share/cmake-3.18/Help/variable/CMAKE_CODELITE_USE_TARGETS.rst deleted file mode 100644 index 33cdf6c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CODELITE_USE_TARGETS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_CODELITE_USE_TARGETS --------------------------- - -Change the way the CodeLite generator creates projectfiles. - -If this variable evaluates to ``ON`` at the end of the top-level -``CMakeLists.txt`` file, the generator creates projectfiles based on targets -rather than projects.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCC.rst b/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCC.rst deleted file mode 100644 index a40667e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCC.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_COMPILER_IS_GNUCC ------------------------ - -True if the ``C`` compiler is GNU. -Use :variable:`CMAKE_C_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCXX.rst b/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCXX.rst deleted file mode 100644 index f1f5cf7..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUCXX.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_COMPILER_IS_GNUCXX ------------------------- - -True if the C++ (``CXX``) compiler is GNU. -Use :variable:`CMAKE_CXX_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUG77.rst b/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUG77.rst deleted file mode 100644 index 3d6dab4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_COMPILER_IS_GNUG77.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_COMPILER_IS_GNUG77 ------------------------- - -True if the ``Fortran`` compiler is GNU. -Use :variable:`CMAKE_Fortran_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>` instead.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY.rst b/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY.rst deleted file mode 100644 index ea33c7d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY ----------------------------------- - -Output directory for MS debug symbol ``.pdb`` files -generated by the compiler while building source files. - -This variable is used to initialize the -:prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY` property on all the targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst deleted file mode 100644 index fdeb9ab..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> -------------------------------------------- - -Per-configuration output directory for MS debug symbol ``.pdb`` files -generated by the compiler while building source files. - -This is a per-configuration version of -:variable:`CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY`. -This variable is used to initialize the -:prop_tgt:`COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>` -property on all the targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CONFIGURATION_TYPES.rst b/share/cmake-3.18/Help/variable/CMAKE_CONFIGURATION_TYPES.rst deleted file mode 100644 index 34e99eb..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CONFIGURATION_TYPES.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_CONFIGURATION_TYPES -------------------------- - -Specifies the available build types on multi-config generators. - -This specifies what build types (configurations) will be available -such as ``Debug``, ``Release``, ``RelWithDebInfo`` etc. This has reasonable -defaults on most platforms, but can be extended to provide other build -types. See also :variable:`CMAKE_BUILD_TYPE` for details of managing -configuration data, and :variable:`CMAKE_CFG_INTDIR`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CPACK_COMMAND.rst b/share/cmake-3.18/Help/variable/CMAKE_CPACK_COMMAND.rst deleted file mode 100644 index 559108a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CPACK_COMMAND.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_CPACK_COMMAND -------------------- - -Full path to :manual:`cpack(1)` command installed with CMake. - -This is the full path to the CPack executable :manual:`cpack(1)` which is -useful from custom commands that want to use the :manual:`cmake(1)` ``-E`` -option for portable system commands.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CROSSCOMPILING_EMULATOR.rst b/share/cmake-3.18/Help/variable/CMAKE_CROSSCOMPILING_EMULATOR.rst deleted file mode 100644 index 1d013b7..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CROSSCOMPILING_EMULATOR.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_CROSSCOMPILING_EMULATOR ------------------------------ - -This variable is only used when :variable:`CMAKE_CROSSCOMPILING` is on. It -should point to a command on the host system that can run executable built -for the target system. - -If this variable contains a :ref:`semicolon-separated list <CMake Language -Lists>`, then the first value is the command and remaining values are its -arguments. - -The command will be used to run :command:`try_run` generated executables, -which avoids manual population of the ``TryRunResults.cmake`` file. - -It is also used as the default value for the -:prop_tgt:`CROSSCOMPILING_EMULATOR` target property of executables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CROSS_CONFIGS.rst b/share/cmake-3.18/Help/variable/CMAKE_CROSS_CONFIGS.rst deleted file mode 100644 index 94157f3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CROSS_CONFIGS.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_CROSS_CONFIGS -------------------- - -Specifies a :ref:`semicolon-separated list <CMake Language Lists>` of -configurations available from all ``build-<Config>.ninja`` files in the -:generator:`Ninja Multi-Config` generator. This variable activates -cross-config mode. Targets from each config specified in this variable can be -built from any ``build-<Config>.ninja`` file. Custom commands will use the -configuration native to ``build-<Config>.ninja``. If it is set to ``all``, all -configurations from :variable:`CMAKE_CONFIGURATION_TYPES` are cross-configs. If -it is not specified, or empty, each ``build-<Config>.ninja`` file will only -contain build rules for its own configuration. - -The value of this variable must be a subset of -:variable:`CMAKE_CONFIGURATION_TYPES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CTEST_ARGUMENTS.rst b/share/cmake-3.18/Help/variable/CMAKE_CTEST_ARGUMENTS.rst deleted file mode 100644 index 0940b46..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CTEST_ARGUMENTS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_CTEST_ARGUMENTS ---------------------- - -Set this to a :ref:`semicolon-separated list <CMake Language Lists>` of -command-line arguments to pass to :manual:`ctest(1)` when running tests -through the ``test`` (or ``RUN_TESTS``) target of the generated build system.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_ARCHITECTURES.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_ARCHITECTURES.rst deleted file mode 100644 index 149bffa..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_ARCHITECTURES.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_CUDA_ARCHITECTURES ------------------------- - -Default value for :prop_tgt:`CUDA_ARCHITECTURES` property of targets. - -This is initialized as follows depending on :variable:`CMAKE_CUDA_COMPILER_ID <CMAKE_<LANG>_COMPILER_ID>`: - -- For ``Clang``: the oldest architecture that works. - -- For ``NVIDIA``: the default architecture chosen by the compiler. - See policy :policy:`CMP0104`. - -Users are encouraged to override this, as the default varies across compilers -and compiler versions. - -This variable is used to initialize the :prop_tgt:`CUDA_ARCHITECTURES` property -on all targets. See the target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_COMPILE_FEATURES.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_COMPILE_FEATURES.rst deleted file mode 100644 index 2cd2650..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_COMPILE_FEATURES.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CUDA_COMPILE_FEATURES ---------------------------- - -List of features known to the CUDA compiler - -These features are known to be available for use with the CUDA compiler. This -list is a subset of the features listed in the -:prop_gbl:`CMAKE_CUDA_KNOWN_FEATURES` global property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_EXTENSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_EXTENSIONS.rst deleted file mode 100644 index 4fe758e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_EXTENSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CUDA_EXTENSIONS ---------------------- - -Default value for :prop_tgt:`CUDA_EXTENSIONS` property of targets. - -This variable is used to initialize the :prop_tgt:`CUDA_EXTENSIONS` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_HOST_COMPILER.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_HOST_COMPILER.rst deleted file mode 100644 index 6d34c5c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_HOST_COMPILER.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_CUDA_HOST_COMPILER ------------------------- - -Executable to use when compiling host code when compiling ``CUDA`` language -files. Maps to the ``nvcc -ccbin`` option. Will only be used by CMake on the first -configuration to determine a valid host compiler for ``CUDA``. After a valid -host compiler has been found, this value is read-only. This variable takes -priority over the :envvar:`CUDAHOSTCXX` environment variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS.rst deleted file mode 100644 index fc835cd..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS ---------------------------------- - -Default value for :prop_tgt:`CUDA_RESOLVE_DEVICE_SYMBOLS` target -property. This variable is used to initialize the property on each target as -it is created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_RUNTIME_LIBRARY.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_RUNTIME_LIBRARY.rst deleted file mode 100644 index e3205d3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_RUNTIME_LIBRARY.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMAKE_CUDA_RUNTIME_LIBRARY --------------------------- - -Select the CUDA runtime library for use when compiling and linking CUDA. -This variable is used to initialize the :prop_tgt:`CUDA_RUNTIME_LIBRARY` -property on all targets as they are created. - -The allowed case insensitive values are: - -.. include:: ../prop_tgt/CUDA_RUNTIME_LIBRARY-VALUES.txt - -Contents of ``CMAKE_CUDA_RUNTIME_LIBRARY`` may use -:manual:`generator expressions <cmake-generator-expressions(7)>`. - -If this variable is not set then the :prop_tgt:`CUDA_RUNTIME_LIBRARY` target -property will not be set automatically. If that property is not set then -CMake uses an appropriate default value based on the compiler to select the -CUDA runtime library. - -.. note:: - - This property has effect only when the ``CUDA`` language is enabled. To - control the CUDA runtime linking when only using the CUDA SDK with the - ``C`` or ``C++`` language we recommend using the :module:`FindCUDAToolkit` - module.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.rst deleted file mode 100644 index eef92fb..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_CUDA_SEPARABLE_COMPILATION --------------------------------- - -Default value for :prop_tgt:`CUDA_SEPARABLE_COMPILATION` target property. -This variable is used to initialize the property on each target as it is -created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD.rst deleted file mode 100644 index 6c23031..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CUDA_STANDARD -------------------- - -Default value for :prop_tgt:`CUDA_STANDARD` property of targets. - -This variable is used to initialize the :prop_tgt:`CUDA_STANDARD` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD_REQUIRED.rst deleted file mode 100644 index 935d605..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CUDA_STANDARD_REQUIRED ----------------------------- - -Default value for :prop_tgt:`CUDA_STANDARD_REQUIRED` property of targets. - -This variable is used to initialize the :prop_tgt:`CUDA_STANDARD_REQUIRED` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES.rst deleted file mode 100644 index 7de50a5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES --------------------------------------- - -When the ``CUDA`` language has been enabled, this provides a -:ref:`semicolon-separated list <CMake Language Lists>` of include directories provided -by the CUDA Toolkit. The value may be useful for C++ source files -to include CUDA headers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION.rst b/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION.rst deleted file mode 100644 index fb7f610..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_CURRENT_FUNCTION ----------------------- - -When executing code inside a :command:`function`, this variable -contains the name of the current function. It can be useful for -diagnostic or debug messages. - -See also :variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE` and -:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_DIR.rst b/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_DIR.rst deleted file mode 100644 index 44ae1e5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_DIR.rst +++ /dev/null
@@ -1,41 +0,0 @@ -CMAKE_CURRENT_FUNCTION_LIST_DIR -------------------------------- - -When executing code inside a :command:`function`, this variable -contains the full directory of the listfile that defined the current function. - -It is quite common practice in CMake for modules to use some additional files, -such as templates to be copied in after substituting CMake variables. -In such cases, a function needs to know where to locate those files in a way -that doesn't depend on where the function is called. Without -``CMAKE_CURRENT_FUNCTION_LIST_DIR``, the code to do that would typically use -the following pattern: - -.. code-block:: cmake - - set(_THIS_MODULE_BASE_DIR "${CMAKE_CURRENT_LIST_DIR}") - - function(foo) - configure_file( - "${_THIS_MODULE_BASE_DIR}/some.template.in" - some.output - ) - endfunction() - -Using ``CMAKE_CURRENT_FUNCTION_LIST_DIR`` inside the function instead -eliminates the need for the extra variable which would otherwise be visible -outside the function's scope. -The above example can be written in the more concise and more robust form: - -.. code-block:: cmake - - function(foo) - configure_file( - "${CMAKE_CURRENT_FUNCTION_LIST_DIR}/some.template.in" - some.output - ) - endfunction() - -See also :variable:`CMAKE_CURRENT_FUNCTION`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE` and -:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.rst b/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.rst deleted file mode 100644 index c737af9..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_CURRENT_FUNCTION_LIST_FILE --------------------------------- - -When executing code inside a :command:`function`, this variable -contains the full path to the listfile that defined the current function. - -See also :variable:`CMAKE_CURRENT_FUNCTION`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR` and -:variable:`CMAKE_CURRENT_FUNCTION_LIST_LINE`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.rst b/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.rst deleted file mode 100644 index ad6282e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_CURRENT_FUNCTION_LIST_LINE --------------------------------- - -When executing code inside a :command:`function`, this variable -contains the line number in the listfile where the current function -was defined. - -See also :variable:`CMAKE_CURRENT_FUNCTION`, -:variable:`CMAKE_CURRENT_FUNCTION_LIST_DIR` and -:variable:`CMAKE_CURRENT_FUNCTION_LIST_FILE`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_LIST_LINE.rst b/share/cmake-3.18/Help/variable/CMAKE_CURRENT_LIST_LINE.rst deleted file mode 100644 index 60e8e26..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CURRENT_LIST_LINE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_CURRENT_LIST_LINE ------------------------ - -The line number of the current file being processed. - -This is the line number of the file currently being processed by -cmake.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CXX_COMPILE_FEATURES.rst b/share/cmake-3.18/Help/variable/CMAKE_CXX_COMPILE_FEATURES.rst deleted file mode 100644 index 5c59f95..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CXX_COMPILE_FEATURES.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CXX_COMPILE_FEATURES --------------------------- - -List of features known to the C++ compiler - -These features are known to be available for use with the C++ compiler. This -list is a subset of the features listed in the -:prop_gbl:`CMAKE_CXX_KNOWN_FEATURES` global property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CXX_EXTENSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_CXX_EXTENSIONS.rst deleted file mode 100644 index 4a92425..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CXX_EXTENSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CXX_EXTENSIONS --------------------- - -Default value for :prop_tgt:`CXX_EXTENSIONS` property of targets. - -This variable is used to initialize the :prop_tgt:`CXX_EXTENSIONS` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD.rst b/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD.rst deleted file mode 100644 index 8a8bdff..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CXX_STANDARD ------------------- - -Default value for :prop_tgt:`CXX_STANDARD` property of targets. - -This variable is used to initialize the :prop_tgt:`CXX_STANDARD` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD_REQUIRED.rst deleted file mode 100644 index 4c71058..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_CXX_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_CXX_STANDARD_REQUIRED ---------------------------- - -Default value for :prop_tgt:`CXX_STANDARD_REQUIRED` property of targets. - -This variable is used to initialize the :prop_tgt:`CXX_STANDARD_REQUIRED` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_C_COMPILE_FEATURES.rst b/share/cmake-3.18/Help/variable/CMAKE_C_COMPILE_FEATURES.rst deleted file mode 100644 index 8d1eca0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_C_COMPILE_FEATURES.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_C_COMPILE_FEATURES ------------------------- - -List of features known to the C compiler - -These features are known to be available for use with the C compiler. This -list is a subset of the features listed in the -:prop_gbl:`CMAKE_C_KNOWN_FEATURES` global property. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_C_EXTENSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_C_EXTENSIONS.rst deleted file mode 100644 index fa510d4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_C_EXTENSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_C_EXTENSIONS ------------------- - -Default value for :prop_tgt:`C_EXTENSIONS` property of targets. - -This variable is used to initialize the :prop_tgt:`C_EXTENSIONS` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD.rst b/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD.rst deleted file mode 100644 index b55e00c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_C_STANDARD ----------------- - -Default value for :prop_tgt:`C_STANDARD` property of targets. - -This variable is used to initialize the :prop_tgt:`C_STANDARD` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD_REQUIRED.rst deleted file mode 100644 index 7f70f6e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_C_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_C_STANDARD_REQUIRED -------------------------- - -Default value for :prop_tgt:`C_STANDARD_REQUIRED` property of targets. - -This variable is used to initialize the :prop_tgt:`C_STANDARD_REQUIRED` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_BUILD_TYPE.rst b/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_BUILD_TYPE.rst deleted file mode 100644 index aa4f82d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_BUILD_TYPE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_DEFAULT_BUILD_TYPE ------------------------- - -Specifies the configuration to use by default in a ``build.ninja`` file in the -:generator:`Ninja Multi-Config` generator. If this variable is specified, -``build.ninja`` uses build rules from ``build-<Config>.ninja`` by default. All -custom commands are executed with this configuration. If the variable is not -specified, the first item from :variable:`CMAKE_CONFIGURATION_TYPES` is used -instead. - -The value of this variable must be one of the items from -:variable:`CMAKE_CONFIGURATION_TYPES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_CONFIGS.rst b/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_CONFIGS.rst deleted file mode 100644 index 84c642a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DEFAULT_CONFIGS.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMAKE_DEFAULT_CONFIGS ---------------------- - -Specifies a :ref:`semicolon-separated list <CMake Language Lists>` of configurations -to build for a target in ``build.ninja`` if no ``:<Config>`` suffix is specified in -the :generator:`Ninja Multi-Config` generator. If it is set to ``all``, all -configurations from :variable:`CMAKE_CROSS_CONFIGS` are used. If it is not -specified, it defaults to :variable:`CMAKE_DEFAULT_BUILD_TYPE`. - -For example, if you set :variable:`CMAKE_DEFAULT_BUILD_TYPE` to ``Release``, -but set :variable:`CMAKE_DEFAULT_CONFIGS` to ``Debug`` or ``all``, all -``<target>`` aliases in ``build.ninja`` will resolve to ``<target>:Debug`` or -``<target>:all``, but custom commands will still use the ``Release`` -configuration. - -The value of this variable must be a subset of :variable:`CMAKE_CROSS_CONFIGS` -or be the same as :variable:`CMAKE_DEFAULT_BUILD_TYPE`. It must not be -specified if :variable:`CMAKE_DEFAULT_BUILD_TYPE` or -:variable:`CMAKE_CROSS_CONFIGS` is not used.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DEPENDS_IN_PROJECT_ONLY.rst b/share/cmake-3.18/Help/variable/CMAKE_DEPENDS_IN_PROJECT_ONLY.rst deleted file mode 100644 index 7179071..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DEPENDS_IN_PROJECT_ONLY.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_DEPENDS_IN_PROJECT_ONLY ------------------------------ - -When set to ``TRUE`` in a directory, the build system produced by the -:ref:`Makefile Generators` is set up to only consider dependencies on source -files that appear either in the source or in the binary directories. Changes -to source files outside of these directories will not cause rebuilds. - -This should be used carefully in cases where some source files are picked up -through external headers during the build.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DIRECTORY_LABELS.rst b/share/cmake-3.18/Help/variable/CMAKE_DIRECTORY_LABELS.rst deleted file mode 100644 index 2a6c410..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DIRECTORY_LABELS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_DIRECTORY_LABELS ------------------------ - -Specify labels for the current directory. - -This is used to initialize the :prop_dir:`LABELS` directory property.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.rst b/share/cmake-3.18/Help/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.rst deleted file mode 100644 index ed60020..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_DISABLE_FIND_PACKAGE_<PackageName> ----------------------------------------- - -Variable for disabling :command:`find_package` calls. - -Every non-``REQUIRED`` :command:`find_package` call in a project can be -disabled by setting the variable -``CMAKE_DISABLE_FIND_PACKAGE_<PackageName>`` to ``TRUE``. -This can be used to build a project without an optional package, -although that package is installed. - -This switch should be used during the initial CMake run. Otherwise if -the package has already been found in a previous CMake run, the -variables which have been stored in the cache will still be there. In -that case it is recommended to remove the cache variables for this -package from the cache using the cache editor or :manual:`cmake(1)` ``-U``
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DISABLE_PRECOMPILE_HEADERS.rst b/share/cmake-3.18/Help/variable/CMAKE_DISABLE_PRECOMPILE_HEADERS.rst deleted file mode 100644 index 7c30ede..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DISABLE_PRECOMPILE_HEADERS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_DISABLE_PRECOMPILE_HEADERS --------------------------------- - -Default value for :prop_tgt:`DISABLE_PRECOMPILE_HEADERS` of targets. - -By default ``CMAKE_DISABLE_PRECOMPILE_HEADERS`` is ``OFF``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK.rst b/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK.rst deleted file mode 100644 index 8edcd1e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_DOTNET_TARGET_FRAMEWORK ------------------------------ - -Default value for :prop_tgt:`DOTNET_TARGET_FRAMEWORK` property of -targets. - -This variable is used to initialize the -:prop_tgt:`DOTNET_TARGET_FRAMEWORK` property on all targets. See that -target property for additional information. - -Setting ``CMAKE_DOTNET_TARGET_FRAMEWORK`` may be necessary -when working with ``C#`` and newer .NET framework versions to -avoid referencing errors with the ``ALL_BUILD`` CMake target. - -This variable is only evaluated for :ref:`Visual Studio Generators` -VS 2010 and above.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.rst deleted file mode 100644 index c2eef9e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION -------------------------------------- - -Default value for :prop_tgt:`DOTNET_TARGET_FRAMEWORK_VERSION` -property of targets. - -This variable is used to initialize the -:prop_tgt:`DOTNET_TARGET_FRAMEWORK_VERSION` property on all -targets. See that target property for additional information. When set, -:variable:`CMAKE_DOTNET_TARGET_FRAMEWORK` takes precednece over this -variable. See that variable or the associated target property -:prop_tgt:`DOTNET_TARGET_FRAMEWORK` for additional information. - - -Setting ``CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION`` may be necessary -when working with ``C#`` and newer .NET framework versions to -avoid referencing errors with the ``ALL_BUILD`` CMake target. - -This variable is only evaluated for :ref:`Visual Studio Generators` -VS 2010 and above.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES.rst b/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES.rst deleted file mode 100644 index 331aae8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES ---------------------------------------- - -This cache variable is used by the Eclipse project generator. See -:manual:`cmake-generators(7)`. - -The Eclipse project generator generates so-called linked resources -e.g. to the subproject root dirs in the source tree or to the source files -of targets. -This can be disabled by setting this variable to FALSE.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.rst b/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.rst deleted file mode 100644 index 7b4367d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT -------------------------------------- - -This cache variable is used by the Eclipse project generator. See -:manual:`cmake-generators(7)`. - -If this variable is set to TRUE, the Eclipse project generator will generate -an Eclipse project in :variable:`CMAKE_SOURCE_DIR` . This project can then -be used in Eclipse e.g. for the version control functionality. -:variable:`CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT` defaults to FALSE; so -nothing is written into the source directory.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.rst b/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.rst deleted file mode 100644 index 6e8a408..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_ECLIPSE_MAKE_ARGUMENTS ----------------------------- - -This cache variable is used by the Eclipse project generator. See -:manual:`cmake-generators(7)`. - -This variable holds arguments which are used when Eclipse invokes the make -tool. By default it is initialized to hold flags to enable parallel builds -(using -j typically).
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_RESOURCE_ENCODING.rst b/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_RESOURCE_ENCODING.rst deleted file mode 100644 index 314efe5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_RESOURCE_ENCODING.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_ECLIPSE_RESOURCE_ENCODING -------------------------------- - -This cache variable tells the :generator:`Eclipse CDT4` project generator -to set the resource encoding to the given value in generated project files. -If no value is given, no encoding will be set.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_VERSION.rst deleted file mode 100644 index 8cc7882..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ECLIPSE_VERSION.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_ECLIPSE_VERSION ---------------------- - -This cache variable is used by the Eclipse project generator. See -:manual:`cmake-generators(7)`. - -When using the Eclipse project generator, CMake tries to find the Eclipse -executable and detect the version of it. Depending on the version it finds, -some features are enabled or disabled. If CMake doesn't find -Eclipse, it assumes the oldest supported version, Eclipse Callisto (3.2).
diff --git a/share/cmake-3.18/Help/variable/CMAKE_ENABLE_EXPORTS.rst b/share/cmake-3.18/Help/variable/CMAKE_ENABLE_EXPORTS.rst deleted file mode 100644 index 8848da1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_ENABLE_EXPORTS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_ENABLE_EXPORTS --------------------- - -Specify whether executables export symbols for loadable modules. - -This variable is used to initialize the :prop_tgt:`ENABLE_EXPORTS` target -property for executable targets when they are created by calls to the -:command:`add_executable` command. See the property documentation for details.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXECUTABLE_SUFFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_EXECUTABLE_SUFFIX.rst deleted file mode 100644 index 356590f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXECUTABLE_SUFFIX.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_EXECUTABLE_SUFFIX ------------------------ - -The suffix for executables on this platform. - -The suffix to use for the end of an executable filename if any, ``.exe`` -on Windows. - -``CMAKE_EXECUTABLE_SUFFIX_<LANG>`` overrides this for language ``<LANG>``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.rst b/share/cmake-3.18/Help/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.rst deleted file mode 100644 index 76561d8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_EXECUTE_PROCESS_COMMAND_ECHO ----------------------------------- - -If this variable is set to ``STDERR``, ``STDOUT`` or ``NONE`` then commands -in :command:`execute_process` calls will be printed to either stderr or -stdout or not at all.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.rst deleted file mode 100644 index 592a369..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_EXE_LINKER_FLAGS_<CONFIG>_INIT ------------------------------------- - -Value used to initialize the :variable:`CMAKE_EXE_LINKER_FLAGS_<CONFIG>` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also :variable:`CMAKE_EXE_LINKER_FLAGS_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_INIT.rst deleted file mode 100644 index 0b8afe4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXE_LINKER_FLAGS_INIT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_EXE_LINKER_FLAGS_INIT ---------------------------- - -Value used to initialize the :variable:`CMAKE_EXE_LINKER_FLAGS` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also the configuration-specific variable -:variable:`CMAKE_EXE_LINKER_FLAGS_<CONFIG>_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_COMPILE_COMMANDS.rst b/share/cmake-3.18/Help/variable/CMAKE_EXPORT_COMPILE_COMMANDS.rst deleted file mode 100644 index 6d2450b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_COMPILE_COMMANDS.rst +++ /dev/null
@@ -1,37 +0,0 @@ -CMAKE_EXPORT_COMPILE_COMMANDS ------------------------------ - -Enable/Disable output of compile commands during generation. - -If enabled, generates a ``compile_commands.json`` file containing the exact -compiler calls for all translation units of the project in machine-readable -form. The format of the JSON file looks like: - -.. code-block:: javascript - - [ - { - "directory": "/home/user/development/project", - "command": "/usr/bin/c++ ... -c ../foo/foo.cc", - "file": "../foo/foo.cc" - }, - - ... - - { - "directory": "/home/user/development/project", - "command": "/usr/bin/c++ ... -c ../foo/bar.cc", - "file": "../foo/bar.cc" - } - ] - -This is initialized by the :envvar:`CMAKE_EXPORT_COMPILE_COMMANDS` environment -variable. - -.. note:: - This option is implemented only by :ref:`Makefile Generators` - and the :generator:`Ninja`. It is ignored on other generators. - - This option currently does not work well in combination with - the :prop_tgt:`UNITY_BUILD` target property or the - :variable:`CMAKE_UNITY_BUILD` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.rst deleted file mode 100644 index 768ed64..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_EXPORT_NO_PACKAGE_REGISTRY --------------------------------- - -Disable the :command:`export(PACKAGE)` command when :policy:`CMP0090` -is not set to ``NEW``. - -In some cases, for example for packaging and for system wide -installations, it is not desirable to write the user package registry. -If the ``CMAKE_EXPORT_NO_PACKAGE_REGISTRY`` variable is enabled, -the :command:`export(PACKAGE)` command will do nothing. - -If :policy:`CMP0090` is set to ``NEW`` this variable does nothing, and the -:variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` variable controls the behavior -instead. - -See also :ref:`Disabling the Package Registry`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.rst deleted file mode 100644 index 3476a19..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_EXPORT_PACKAGE_REGISTRY ------------------------------ - -Enables the :command:`export(PACKAGE)` command when :policy:`CMP0090` -is set to ``NEW``. - -The :command:`export(PACKAGE)` command does nothing by default. In some cases -it is desirable to write to the user package registry, so the -``CMAKE_EXPORT_PACKAGE_REGISTRY`` variable may be set to enable it. - -If :policy:`CMP0090` is *not* set to ``NEW`` this variable does nothing, and -the :variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` variable controls the behavior -instead. - -See also :ref:`Disabling the Package Registry`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_APPBUNDLE.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_APPBUNDLE.rst deleted file mode 100644 index 7a05fac..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_APPBUNDLE.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMAKE_FIND_APPBUNDLE --------------------- - -This variable affects how ``find_*`` commands choose between -macOS Application Bundles and unix-style package components. - -On Darwin or systems supporting macOS Application Bundles, the -``CMAKE_FIND_APPBUNDLE`` variable can be set to empty or -one of the following: - -``FIRST`` - Try to find application bundles before standard programs. - This is the default on Darwin. - -``LAST`` - Try to find application bundles after standard programs. - -``ONLY`` - Only try to find application bundles. - -``NEVER`` - Never try to find application bundles.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_DEBUG_MODE.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_DEBUG_MODE.rst deleted file mode 100644 index f5fd8ce..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_DEBUG_MODE.rst +++ /dev/null
@@ -1,23 +0,0 @@ -CMAKE_FIND_DEBUG_MODE ---------------------- - -Print extra find call information for the following commands to standard -error: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -Output is designed for human consumption and not for parsing. -Enabling this variable is equivalent to using :manual:`cmake <cmake(1)>` ``--debug-find`` -with the added ability to enable debugging for a subset of find calls. - -.. code-block:: cmake - - set(CMAKE_FIND_DEBUG_MODE TRUE) - find_program(...) - set(CMAKE_FIND_DEBUG_MODE FALSE) - -Default is unset.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_FRAMEWORK.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_FRAMEWORK.rst deleted file mode 100644 index 4d5078f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_FRAMEWORK.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMAKE_FIND_FRAMEWORK --------------------- - -This variable affects how ``find_*`` commands choose between -macOS Frameworks and unix-style package components. - -On Darwin or systems supporting macOS Frameworks, the -``CMAKE_FIND_FRAMEWORK`` variable can be set to empty or -one of the following: - -``FIRST`` - Try to find frameworks before standard libraries or headers. - This is the default on Darwin. - -``LAST`` - Try to find frameworks after standard libraries or headers. - -``ONLY`` - Only try to find frameworks. - -``NEVER`` - Never try to find frameworks.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.rst deleted file mode 100644 index ada8955..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX ------------------------------------- - -Specify a ``<suffix>`` to tell the :command:`find_library` command to -search in a ``lib<suffix>`` directory before each ``lib`` directory that -would normally be searched. - -This overrides the behavior of related global properties: - -* :prop_gbl:`FIND_LIBRARY_USE_LIB32_PATHS` -* :prop_gbl:`FIND_LIBRARY_USE_LIB64_PATHS` -* :prop_gbl:`FIND_LIBRARY_USE_LIBX32_PATHS`
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_SUFFIXES.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_SUFFIXES.rst deleted file mode 100644 index 4a64e33..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_LIBRARY_SUFFIXES.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_FIND_LIBRARY_SUFFIXES ---------------------------- - -Suffixes to append when looking for libraries. - -This specifies what suffixes to add to library names when the -:command:`find_library` command looks for libraries. On Windows systems this -is typically ``.lib`` and ``.dll``, meaning that when trying to find the -``foo`` library it will look for ``foo.dll`` etc.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NAME.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NAME.rst deleted file mode 100644 index bd1a30f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NAME.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_FIND_PACKAGE_NAME ------------------------ - -Defined by the :command:`find_package` command while loading -a find module to record the caller-specified package name. -See command documentation for details.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.rst deleted file mode 100644 index 4ee9d8b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY --------------------------------------- - -.. deprecated:: 3.16 - - Use the :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` variable instead. - -By default this variable is not set. If neither -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` nor -``CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY`` is set, then -:command:`find_package()` will use the :ref:`User Package Registry` -unless the ``NO_CMAKE_PACKAGE_REGISTRY`` option is provided. - -``CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY`` is ignored if -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` is set. - -In some cases, for example to locate only system wide installations, it -is not desirable to use the :ref:`User Package Registry` when searching -for packages. If the :variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` -variable is ``TRUE``, all the :command:`find_package` commands will skip -the :ref:`User Package Registry` as if they were called with the -``NO_CMAKE_PACKAGE_REGISTRY`` argument. - -See also :ref:`Disabling the Package Registry`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY.rst deleted file mode 100644 index 107c183..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY ---------------------------------------------- - -.. deprecated:: 3.16 - - Use the :variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` variable instead. - -By default this variable is not set. If neither -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` nor -``CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY`` is set, then -:command:`find_package()` will use the :ref:`System Package Registry` -unless the ``NO_CMAKE_SYSTEM_PACKAGE_REGISTRY`` option is provided. - -``CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY`` is ignored if -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` is set. - -In some cases, it is not desirable to use the -:ref:`System Package Registry` when searching for packages. If the -:variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` variable is -``TRUE``, all the :command:`find_package` commands will skip -the :ref:`System Package Registry` as if they were called with the -``NO_CMAKE_SYSTEM_PACKAGE_REGISTRY`` argument. - -See also :ref:`Disabling the Package Registry`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.rst deleted file mode 100644 index db658a1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMAKE_FIND_PACKAGE_PREFER_CONFIG ---------------------------------- - -Tell :command:`find_package` to try "Config" mode before "Module" mode if no -mode was specified. - -The command :command:`find_package` operates without an explicit mode when -the reduced signature is used without the ``MODULE`` option. In this case, -by default, CMake first tries Module mode by searching for a -``Find<pkg>.cmake`` module. If it fails, CMake then searches for the package -using Config mode. - -Set ``CMAKE_FIND_PACKAGE_PREFER_CONFIG`` to ``TRUE`` to tell -:command:`find_package` to first search using Config mode before falling back -to Module mode. - -This variable may be useful when a developer has compiled a custom version of -a common library and wishes to link it to a dependent project. If this -variable is set to ``TRUE``, it would prevent a dependent project's call -to :command:`find_package` from selecting the default library located by the -system's ``Find<pkg>.cmake`` module before finding the developer's custom -built library. - -Once this variable is set, it is the responsibility of the exported -``<pkg>Config.cmake`` files to provide the same result variables as the -``Find<pkg>.cmake`` modules so that dependent projects can use them -interchangeably.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS.rst deleted file mode 100644 index dfbde20..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS ------------------------------------ - -Set to ``TRUE`` to tell :command:`find_package` calls to resolve symbolic -links in the value of ``<PackageName>_DIR``. - -This is helpful in use cases where the package search path points at a -proxy directory in which symlinks to the real package locations appear. -This is not enabled by default because there are also common use cases -in which the symlinks should be preserved.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_DIRECTION.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_DIRECTION.rst deleted file mode 100644 index 99e4ec1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_DIRECTION.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_FIND_PACKAGE_SORT_DIRECTION ---------------------------------- - -The sorting direction used by :variable:`CMAKE_FIND_PACKAGE_SORT_ORDER`. -It can assume one of the following values: - -``DEC`` - Default. Ordering is done in descending mode. - The highest folder found will be tested first. - -``ASC`` - Ordering is done in ascending mode. - The lowest folder found will be tested first. - -If :variable:`CMAKE_FIND_PACKAGE_SORT_ORDER` is not set or is set to ``NONE`` -this variable has no effect.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_ORDER.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_ORDER.rst deleted file mode 100644 index ba5f3a8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_PACKAGE_SORT_ORDER.rst +++ /dev/null
@@ -1,36 +0,0 @@ -CMAKE_FIND_PACKAGE_SORT_ORDER ------------------------------ - -The default order for sorting packages found using :command:`find_package`. -It can assume one of the following values: - -``NONE`` - Default. No attempt is done to sort packages. - The first valid package found will be selected. - -``NAME`` - Sort packages lexicographically before selecting one. - -``NATURAL`` - Sort packages using natural order (see ``strverscmp(3)`` manual), - i.e. such that contiguous digits are compared as whole numbers. - -Natural sorting can be employed to return the highest version when multiple -versions of the same library are found by :command:`find_package`. For -example suppose that the following libraries have been found: - -* libX-1.1.0 -* libX-1.2.9 -* libX-1.2.10 - -By setting ``NATURAL`` order we can select the one with the highest -version number ``libX-1.2.10``. - -.. code-block:: cmake - - set(CMAKE_FIND_PACKAGE_SORT_ORDER NATURAL) - find_package(libX CONFIG) - -The sort direction can be controlled using the -:variable:`CMAKE_FIND_PACKAGE_SORT_DIRECTION` variable -(by default decrescent, e.g. lib-B will be tested before lib-A).
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH.rst deleted file mode 100644 index 957e956..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH -------------------------------------- - -Controls the default behavior of the following commands for whether or not to -search paths provided by cmake-specific environment variables: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -This is useful in cross-compiling environments. - -By default this variable is not set, which is equivalent to it having -a value of ``TRUE``. Explicit options given to the above commands -take precedence over this variable. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`, -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_PATH.rst deleted file mode 100644 index d2bdb09..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_PATH.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_USE_CMAKE_PATH -------------------------- - -Controls the default behavior of the following commands for whether or not to -search paths provided by cmake-specific cache variables: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -This is useful in cross-compiling environments. - -By default this variable is not set, which is equivalent to it having -a value of ``TRUE``. Explicit options given to the above commands -take precedence over this variable. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`, -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.rst deleted file mode 100644 index b99081d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_USE_CMAKE_SYSTEM_PATH --------------------------------- - -Controls the default behavior of the following commands for whether or not to -search paths provided by platform-specific cmake variables: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -This is useful in cross-compiling environments. - -By default this variable is not set, which is equivalent to it having -a value of ``TRUE``. Explicit options given to the above commands -take precedence over this variable. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`, -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.rst deleted file mode 100644 index 7c7ca36..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMAKE_FIND_USE_PACKAGE_REGISTRY -------------------------------- - -Controls the default behavior of the :command:`find_package` command for -whether or not to search paths provided by the :ref:`User Package Registry`. - -By default this variable is not set and the behavior will fall back -to that determined by the deprecated -:variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` variable. If that is -also not set, then :command:`find_package` will use the -:ref:`User Package Registry` unless the ``NO_CMAKE_PACKAGE_REGISTRY`` option -is provided. - -This variable takes precedence over -:variable:`CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY` when both are set. - -In some cases, for example to locate only system wide installations, it -is not desirable to use the :ref:`User Package Registry` when searching -for packages. If the :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` -variable is ``FALSE``, all the :command:`find_package` commands will skip -the :ref:`User Package Registry` as if they were called with the -``NO_CMAKE_PACKAGE_REGISTRY`` argument. - -See also :ref:`Disabling the Package Registry` and the -:variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_ROOT_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_ROOT_PATH.rst deleted file mode 100644 index e7f5b0f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_PACKAGE_ROOT_PATH.rst +++ /dev/null
@@ -1,22 +0,0 @@ -CMAKE_FIND_USE_PACKAGE_ROOT_PATH --------------------------------- - -Controls the default behavior of the following commands for whether or not to -search paths provided by :variable:`<PackageName>_ROOT` variables: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -By default this variable is not set, which is equivalent to it having -a value of ``TRUE``. Explicit options given to the above commands -take precedence over this variable. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.rst deleted file mode 100644 index fbaba5a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.rst +++ /dev/null
@@ -1,24 +0,0 @@ -CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH --------------------------------------- - -Controls the default behavior of the following commands for whether or not to -search paths provided by standard system environment variables: - -* :command:`find_program` -* :command:`find_library` -* :command:`find_file` -* :command:`find_path` -* :command:`find_package` - -This is useful in cross-compiling environments. - -By default this variable is not set, which is equivalent to it having -a value of ``TRUE``. Explicit options given to the above commands -take precedence over this variable. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY`, -:variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH`, -and :variable:`CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY.rst b/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY.rst deleted file mode 100644 index cb4eec5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY.rst +++ /dev/null
@@ -1,31 +0,0 @@ -CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY --------------------------------------- - -Controls searching the :ref:`System Package Registry` by the -:command:`find_package` command. - -By default this variable is not set and the behavior will fall back -to that determined by the deprecated -:variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` variable. -If that is also not set, then :command:`find_package()` will use the -:ref:`System Package Registry` unless the ``NO_CMAKE_SYSTEM_PACKAGE_REGISTRY`` -option is provided. - -This variable takes precedence over -:variable:`CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY` when both are set. - -In some cases, for example to locate only user specific installations, it -is not desirable to use the :ref:`System Package Registry` when searching -for packages. If the ``CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY`` -variable is ``FALSE``, all the :command:`find_package` commands will skip -the :ref:`System Package Registry` as if they were called with the -``NO_CMAKE_SYSTEM_PACKAGE_REGISTRY`` argument. - -See also :ref:`Disabling the Package Registry`. - -See also the :variable:`CMAKE_FIND_USE_CMAKE_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_CMAKE_SYSTEM_PATH`, -:variable:`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`, -:variable:`CMAKE_FIND_USE_PACKAGE_REGISTRY`, -and :variable:`CMAKE_FIND_USE_PACKAGE_ROOT_PATH` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FOLDER.rst b/share/cmake-3.18/Help/variable/CMAKE_FOLDER.rst deleted file mode 100644 index 50a2b88..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FOLDER.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_FOLDER ------------- - -Set the folder name. Use to organize targets in an IDE. - -This variable is used to initialize the :prop_tgt:`FOLDER` property on all the -targets. See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK.rst b/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK.rst deleted file mode 100644 index 591041c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_FRAMEWORK ---------------- - -Default value for :prop_tgt:`FRAMEWORK` of targets. - -This variable is used to initialize the :prop_tgt:`FRAMEWORK` property on -all the targets. See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst deleted file mode 100644 index 5c7cd23..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> ---------------------------------------------- - -Default framework filename postfix under configuration ``<CONFIG>`` when -using a multi-config generator. - -When a framework target is created its :prop_tgt:`FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>` -target property is initialized with the value of this variable if it is set.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_Fortran_PREPROCESS.rst b/share/cmake-3.18/Help/variable/CMAKE_Fortran_PREPROCESS.rst deleted file mode 100644 index 74b2d8b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_Fortran_PREPROCESS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_Fortran_PREPROCESS ------------------------- - -Default value for :prop_tgt:`Fortran_PREPROCESS` of targets. - -This variable is used to initialize the :prop_tgt:`Fortran_PREPROCESS` -property on all the targets. See that target property for additional -information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_INSTANCE.rst b/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_INSTANCE.rst deleted file mode 100644 index 3657ed4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_INSTANCE.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMAKE_GENERATOR_INSTANCE ------------------------- - -Generator-specific instance specification provided by user. - -Some CMake generators support selection of an instance of the native build -system when multiple instances are available. If the user specifies an -instance (e.g. by setting this cache entry or via the -:envvar:`CMAKE_GENERATOR_INSTANCE` environment variable), or after a default -instance is chosen when a build tree is first configured, the value will be -available in this variable. - -The value of this variable should never be modified by project code. -A toolchain file specified by the :variable:`CMAKE_TOOLCHAIN_FILE` -variable may initialize ``CMAKE_GENERATOR_INSTANCE`` as a cache entry. -Once a given build tree has been initialized with a particular value -for this variable, changing the value has undefined behavior. - -Instance specification is supported only on specific generators: - -* For the :generator:`Visual Studio 15 2017` generator (and above) - this specifies the absolute path to the VS installation directory - of the selected VS instance. - -See native build system documentation for allowed instance values.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_PLATFORM.rst b/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_PLATFORM.rst deleted file mode 100644 index 2c115a3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_PLATFORM.rst +++ /dev/null
@@ -1,31 +0,0 @@ -CMAKE_GENERATOR_PLATFORM ------------------------- - -Generator-specific target platform specification provided by user. - -Some CMake generators support a target platform name to be given -to the native build system to choose a compiler toolchain. -If the user specifies a platform name (e.g. via the :manual:`cmake(1)` ``-A`` -option or via the :envvar:`CMAKE_GENERATOR_PLATFORM` environment variable) -the value will be available in this variable. - -The value of this variable should never be modified by project code. -A toolchain file specified by the :variable:`CMAKE_TOOLCHAIN_FILE` -variable may initialize ``CMAKE_GENERATOR_PLATFORM``. Once a given -build tree has been initialized with a particular value for this -variable, changing the value has undefined behavior. - -Platform specification is supported only on specific generators: - -* For :ref:`Visual Studio Generators` with VS 2005 and above this - specifies the target architecture. - -* For :generator:`Green Hills MULTI` this specifies the target architecture. - -See native build system documentation for allowed platform names. - -Visual Studio Platform Selection -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -On :ref:`Visual Studio Generators` the selected platform name -is provided in the :variable:`CMAKE_VS_PLATFORM_NAME` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_TOOLSET.rst b/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_TOOLSET.rst deleted file mode 100644 index 53ad2f3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GENERATOR_TOOLSET.rst +++ /dev/null
@@ -1,65 +0,0 @@ -CMAKE_GENERATOR_TOOLSET ------------------------ - -Native build system toolset specification provided by user. - -Some CMake generators support a toolset specification to tell the -native build system how to choose a compiler. If the user specifies -a toolset (e.g. via the :manual:`cmake(1)` ``-T`` option or via -the :envvar:`CMAKE_GENERATOR_TOOLSET` environment variable) the value -will be available in this variable. - -The value of this variable should never be modified by project code. -A toolchain file specified by the :variable:`CMAKE_TOOLCHAIN_FILE` -variable may initialize ``CMAKE_GENERATOR_TOOLSET``. Once a given -build tree has been initialized with a particular value for this -variable, changing the value has undefined behavior. - -Toolset specification is supported only on specific generators: - -* :ref:`Visual Studio Generators` for VS 2010 and above -* The :generator:`Xcode` generator for Xcode 3.0 and above -* The :generator:`Green Hills MULTI` generator - -See native build system documentation for allowed toolset names. - -Visual Studio Toolset Selection -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The :ref:`Visual Studio Generators` support toolset specification -using one of these forms: - -* ``toolset`` -* ``toolset[,key=value]*`` -* ``key=value[,key=value]*`` - -The ``toolset`` specifies the toolset name. The selected toolset name -is provided in the :variable:`CMAKE_VS_PLATFORM_TOOLSET` variable. - -The ``key=value`` pairs form a comma-separated list of options to -specify generator-specific details of the toolset selection. -Supported pairs are: - -``cuda=<version>|<path>`` - Specify the CUDA toolkit version to use or the path to a - standalone CUDA toolkit directory. Supported by VS 2010 - and above. The version can only be used with the CUDA - toolkit VS integration globally installed. - See the :variable:`CMAKE_VS_PLATFORM_TOOLSET_CUDA` and - :variable:`CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR` variables. - -``host=<arch>`` - Specify the host tools architecture as ``x64`` or ``x86``. - Supported by VS 2013 and above. - See the :variable:`CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE` - variable. - -``version=<version>`` - Specify the toolset version to use. Supported by VS 2017 - and above with the specified toolset installed. - See the :variable:`CMAKE_VS_PLATFORM_TOOLSET_VERSION` variable. - -``VCTargetsPath=<path>`` - Specify an alternative ``VCTargetsPath`` value for Visual Studio - project files. This allows use of VS platform extension configuration - files (``.props`` and ``.targets``) that are not installed with VS.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GHS_NO_SOURCE_GROUP_FILE.rst b/share/cmake-3.18/Help/variable/CMAKE_GHS_NO_SOURCE_GROUP_FILE.rst deleted file mode 100644 index b6768a1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GHS_NO_SOURCE_GROUP_FILE.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_GHS_NO_SOURCE_GROUP_FILE ------------------------------- - -``ON`` / ``OFF`` boolean to control if the project file for a target should -be one single file or multiple files. Refer to -:prop_tgt:`GHS_NO_SOURCE_GROUP_FILE` for further details.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.rst b/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.rst deleted file mode 100644 index 8587742..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMAKE_GLOBAL_AUTOGEN_TARGET ---------------------------- - -Switch to enable generation of a global ``autogen`` target. - -When :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET` is enabled, a custom target -``autogen`` is generated. This target depends on all :prop_tgt:`AUTOMOC` and -:prop_tgt:`AUTOUIC` generated ``<ORIGIN>_autogen`` targets in the project. -By building the global ``autogen`` target, all :prop_tgt:`AUTOMOC` and -:prop_tgt:`AUTOUIC` files in the project will be generated. - -The name of the global ``autogen`` target can be changed by setting -:variable:`CMAKE_GLOBAL_AUTOGEN_TARGET_NAME`. - -By default :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET` is unset. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt. - -Note -^^^^ - -``<ORIGIN>_autogen`` targets by default inherit their origin target's -dependencies. This might result in unintended dependency target -builds when only ``<ORIGIN>_autogen`` targets are built. A solution is to -disable :prop_tgt:`AUTOGEN_ORIGIN_DEPENDS` on the respective origin targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET_NAME.rst b/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET_NAME.rst deleted file mode 100644 index c86a5d0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTOGEN_TARGET_NAME.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_GLOBAL_AUTOGEN_TARGET_NAME --------------------------------- - -Change the name of the global ``autogen`` target. - -When :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET` is enabled, a global custom target -named ``autogen`` is created. :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET_NAME` -allows to set a different name for that target. - -By default :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET_NAME` is unset. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET.rst b/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET.rst deleted file mode 100644 index f92128c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET.rst +++ /dev/null
@@ -1,18 +0,0 @@ -CMAKE_GLOBAL_AUTORCC_TARGET ---------------------------- - -Switch to enable generation of a global ``autorcc`` target. - -When :variable:`CMAKE_GLOBAL_AUTORCC_TARGET` is enabled, a custom target -``autorcc`` is generated. This target depends on all :prop_tgt:`AUTORCC` -generated ``<ORIGIN>_arcc_<QRC>`` targets in the project. -By building the global ``autorcc`` target, all :prop_tgt:`AUTORCC` -files in the project will be generated. - -The name of the global ``autorcc`` target can be changed by setting -:variable:`CMAKE_GLOBAL_AUTORCC_TARGET_NAME`. - -By default :variable:`CMAKE_GLOBAL_AUTORCC_TARGET` is unset. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.rst b/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.rst deleted file mode 100644 index c6e05de..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_GLOBAL_AUTORCC_TARGET_NAME --------------------------------- - -Change the name of the global ``autorcc`` target. - -When :variable:`CMAKE_GLOBAL_AUTORCC_TARGET` is enabled, a global custom target -named ``autorcc`` is created. :variable:`CMAKE_GLOBAL_AUTORCC_TARGET_NAME` -allows to set a different name for that target. - -By default :variable:`CMAKE_GLOBAL_AUTOGEN_TARGET_NAME` is unset. - -See the :manual:`cmake-qt(7)` manual for more information on using CMake -with Qt.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_HOST_SOLARIS.rst b/share/cmake-3.18/Help/variable/CMAKE_HOST_SOLARIS.rst deleted file mode 100644 index 82b5d69..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_HOST_SOLARIS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_HOST_SOLARIS ------------------- - -``True`` for Oracle Solaris operating systems. - -Set to ``true`` when the host system is Oracle Solaris.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_HOST_SYSTEM_PROCESSOR.rst b/share/cmake-3.18/Help/variable/CMAKE_HOST_SYSTEM_PROCESSOR.rst deleted file mode 100644 index 5f08728..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_HOST_SYSTEM_PROCESSOR.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_HOST_SYSTEM_PROCESSOR ---------------------------- - -The name of the CPU CMake is running on. - -On Windows, this variable is set to the value of the environment variable -``PROCESSOR_ARCHITECTURE``. On systems that support ``uname``, this variable is -set to the output of: - -- ``uname -m`` on GNU, Linux, Cygwin, Darwin, Android, or -- ``arch`` on OpenBSD, or -- on other systems, - - * ``uname -p`` if its exit code is nonzero, or - * ``uname -m`` otherwise.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst deleted file mode 100644 index f994fbe..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst +++ /dev/null
@@ -1,29 +0,0 @@ -CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS -------------------------------------------- - -Default permissions for directories created implicitly during installation -of files by :command:`install` and :command:`file(INSTALL)`. - -If ``make install`` is invoked and directories are implicitly created they -get permissions set by :variable:`CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS` -variable or platform specific default permissions if the variable is not set. - -Implicitly created directories are created if they are not explicitly installed -by :command:`install` command but are needed to install a file on a certain -path. Example of such locations are directories created due to the setting of -:variable:`CMAKE_INSTALL_PREFIX`. - -Expected content of the :variable:`CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS` -variable is a list of permissions that can be used by :command:`install` command -`PERMISSIONS` section. - -Example usage: - -:: - - set(CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS - OWNER_READ - OWNER_WRITE - OWNER_EXECUTE - GROUP_READ - )
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_MESSAGE.rst b/share/cmake-3.18/Help/variable/CMAKE_INSTALL_MESSAGE.rst deleted file mode 100644 index 304df26..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_MESSAGE.rst +++ /dev/null
@@ -1,30 +0,0 @@ -CMAKE_INSTALL_MESSAGE ---------------------- - -Specify verbosity of installation script code generated by the -:command:`install` command (using the :command:`file(INSTALL)` command). -For paths that are newly installed or updated, installation -may print lines like:: - - -- Installing: /some/destination/path - -For paths that are already up to date, installation may print -lines like:: - - -- Up-to-date: /some/destination/path - -The ``CMAKE_INSTALL_MESSAGE`` variable may be set to control -which messages are printed: - -``ALWAYS`` - Print both ``Installing`` and ``Up-to-date`` messages. - -``LAZY`` - Print ``Installing`` but not ``Up-to-date`` messages. - -``NEVER`` - Print neither ``Installing`` nor ``Up-to-date`` messages. - -Other values have undefined behavior and may not be diagnosed. - -If this variable is not set, the default behavior is ``ALWAYS``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_NAME_DIR.rst b/share/cmake-3.18/Help/variable/CMAKE_INSTALL_NAME_DIR.rst deleted file mode 100644 index 5ba4c04..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_NAME_DIR.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_INSTALL_NAME_DIR ----------------------- - -macOS directory name for installed targets. - -``CMAKE_INSTALL_NAME_DIR`` is used to initialize the -:prop_tgt:`INSTALL_NAME_DIR` property on all targets. See that target -property for more information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.rst b/share/cmake-3.18/Help/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.rst deleted file mode 100644 index 2a5842d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.rst +++ /dev/null
@@ -1,14 +0,0 @@ -CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT -------------------------------------------- - -CMake sets this variable to a ``TRUE`` value when the -:variable:`CMAKE_INSTALL_PREFIX` has just been initialized to -its default value, typically on the first run of CMake within -a new build tree. This can be used by project code to change -the default without overriding a user-provided value: - -.. code-block:: cmake - - if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) - set(CMAKE_INSTALL_PREFIX "/my/default" CACHE PATH "..." FORCE) - endif()
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH.rst b/share/cmake-3.18/Help/variable/CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH.rst deleted file mode 100644 index 76ca3da..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH --------------------------------------- - -Sets the default for whether toolchain-defined rpaths should be removed during -installation. - -``CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH`` is a boolean that provides the -default value for the :prop_tgt:`INSTALL_REMOVE_ENVIRONMENT_RPATH` property -of all subsequently created targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION.rst b/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION.rst deleted file mode 100644 index b0cbb62..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_INTERPROCEDURAL_OPTIMIZATION ----------------------------------- - -Default value for :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` of targets. - -This variable is used to initialize the :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` -property on all the targets. See that target property for additional -information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION_CONFIG.rst deleted file mode 100644 index b291102..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_INTERPROCEDURAL_OPTIMIZATION_CONFIG.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_INTERPROCEDURAL_OPTIMIZATION_<CONFIG> -------------------------------------------- - -Default value for :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION_<CONFIG>` of targets. - -This variable is used to initialize the :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION_<CONFIG>` -property on all the targets. See that target property for additional -information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_IOS_INSTALL_COMBINED.rst b/share/cmake-3.18/Help/variable/CMAKE_IOS_INSTALL_COMBINED.rst deleted file mode 100644 index c5cb9b6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_IOS_INSTALL_COMBINED.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_IOS_INSTALL_COMBINED --------------------------- - -Default value for :prop_tgt:`IOS_INSTALL_COMBINED` of targets. - -This variable is used to initialize the :prop_tgt:`IOS_INSTALL_COMBINED` -property on all the targets. See that target property for additional -information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_JOB_POOLS.rst b/share/cmake-3.18/Help/variable/CMAKE_JOB_POOLS.rst deleted file mode 100644 index 72b50b4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_JOB_POOLS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_JOB_POOLS ---------------- - -If the :prop_gbl:`JOB_POOLS` global property is not set, the value -of this variable is used in its place. See :prop_gbl:`JOB_POOLS` -for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_JOB_POOL_PRECOMPILE_HEADER.rst b/share/cmake-3.18/Help/variable/CMAKE_JOB_POOL_PRECOMPILE_HEADER.rst deleted file mode 100644 index f9467b3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_JOB_POOL_PRECOMPILE_HEADER.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_JOB_POOL_PRECOMPILE_HEADER --------------------------------- - -This variable is used to initialize the :prop_tgt:`JOB_POOL_PRECOMPILE_HEADER` -property on all the targets. See :prop_tgt:`JOB_POOL_PRECOMPILE_HEADER` -for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.rst deleted file mode 100644 index d336364..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE --------------------------------------- - -When :ref:`Cross Compiling for Android` this variable contains the -toolchain binutils machine name (e.g. ``gcc -dumpmachine``). The -binutils typically have a ``<machine>-`` prefix on their name. - -See also :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX` -and :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.rst deleted file mode 100644 index db04af3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX -------------------------------------- - -When :ref:`Cross Compiling for Android` this variable contains the absolute -path prefixing the toolchain GNU compiler and its binutils. - -See also :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX` -and :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE`. - -For example, the path to the linker is:: - - ${CMAKE_CXX_ANDROID_TOOLCHAIN_PREFIX}ld${CMAKE_CXX_ANDROID_TOOLCHAIN_SUFFIX}
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.rst deleted file mode 100644 index 159eb22..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX -------------------------------------- - -When :ref:`Cross Compiling for Android` this variable contains the -host platform suffix of the toolchain GNU compiler and its binutils. - -See also :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX` -and :variable:`CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_CLANG_TIDY.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_CLANG_TIDY.rst deleted file mode 100644 index bd49de3..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_CLANG_TIDY.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_<LANG>_CLANG_TIDY ------------------------ - -Default value for :prop_tgt:`<LANG>_CLANG_TIDY` target property -when ``<LANG>`` is ``C`` or ``CXX``. - -This variable is used to initialize the property on each target as it is -created. For example: - -.. code-block:: cmake - - set(CMAKE_CXX_CLANG_TIDY clang-tidy -checks=-*,readability-*) - add_executable(foo foo.cxx)
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER.rst deleted file mode 100644 index 89df495..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_<LANG>_COMPILER ---------------------- - -The full path to the compiler for ``LANG``. - -This is the command that will be used as the ``<LANG>`` compiler. Once -set, you can not change this variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_AR.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_AR.rst deleted file mode 100644 index b83a1d4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_AR.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_<LANG>_COMPILER_AR ------------------------- - -A wrapper around ``ar`` adding the appropriate ``--plugin`` option for the -compiler. - -See also :variable:`CMAKE_AR`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.rst deleted file mode 100644 index 054c648..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID -------------------------------------- - -An internal variable subject to change. - -This is used to identify the variant of a compiler based on its target -architecture. For some compilers this is needed to determine the correct -usage.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ID.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ID.rst deleted file mode 100644 index 8eb4fb6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_ID.rst +++ /dev/null
@@ -1,41 +0,0 @@ -CMAKE_<LANG>_COMPILER_ID ------------------------- - -Compiler identification string. - -A short string unique to the compiler vendor. Possible values -include: - -:: - - Absoft = Absoft Fortran (absoft.com) - ADSP = Analog VisualDSP++ (analog.com) - AppleClang = Apple Clang (apple.com) - ARMCC = ARM Compiler (arm.com) - ARMClang = ARM Compiler based on Clang (arm.com) - Bruce = Bruce C Compiler - CCur = Concurrent Fortran (ccur.com) - Clang = LLVM Clang (clang.llvm.org) - Cray = Cray Compiler (cray.com) - Embarcadero, Borland = Embarcadero (embarcadero.com) - Flang = Flang LLVM Fortran Compiler - G95 = G95 Fortran (g95.org) - GNU = GNU Compiler Collection (gcc.gnu.org) - GHS = Green Hills Software (www.ghs.com) - HP = Hewlett-Packard Compiler (hp.com) - IAR = IAR Systems (iar.com) - Intel = Intel Compiler (intel.com) - MSVC = Microsoft Visual Studio (microsoft.com) - NVIDIA = NVIDIA CUDA Compiler (nvidia.com) - OpenWatcom = Open Watcom (openwatcom.org) - PGI = The Portland Group (pgroup.com) - PathScale = PathScale (pathscale.com) - SDCC = Small Device C Compiler (sdcc.sourceforge.net) - SunPro = Oracle Solaris Studio (oracle.com) - TI = Texas Instruments (ti.com) - TinyCC = Tiny C Compiler (tinycc.org) - XL, VisualAge, zOS = IBM XL (ibm.com) - XLClang = IBM Clang-based XL (ibm.com) - -This variable is not guaranteed to be defined for all compilers or -languages.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_LAUNCHER.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_LAUNCHER.rst deleted file mode 100644 index c76e2d0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_LAUNCHER.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_<LANG>_COMPILER_LAUNCHER ------------------------------- - -Default value for :prop_tgt:`<LANG>_COMPILER_LAUNCHER` target property. -This variable is used to initialize the property on each target as it is -created. This is done only when ``<LANG>`` is ``C``, ``CXX``, ``Fortran``, -``OBJC``, ``OBJCXX``, or ``CUDA``. - -This variable is initialized to the :envvar:`CMAKE_<LANG>_COMPILER_LAUNCHER` -environment variable if it is set.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.rst deleted file mode 100644 index e050f43..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND ----------------------------------------- - -Command that outputs the compiler pre definitions. - -See :prop_tgt:`AUTOMOC` which uses -:variable:`CMAKE_CXX_COMPILER_PREDEFINES_COMMAND <CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND>` -to generate the :prop_tgt:`AUTOMOC_COMPILER_PREDEFINES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_RANLIB.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_RANLIB.rst deleted file mode 100644 index 945160b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_RANLIB.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_<LANG>_COMPILER_RANLIB ----------------------------- - -A wrapper around ``ranlib`` adding the appropriate ``--plugin`` option for the -compiler. - -See also :variable:`CMAKE_RANLIB`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_VERSION_INTERNAL.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_VERSION_INTERNAL.rst deleted file mode 100644 index c3cd980..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_COMPILER_VERSION_INTERNAL.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_<LANG>_COMPILER_VERSION_INTERNAL --------------------------------------- - -An internal variable subject to change. - -This is used to identify the variant of a compiler based on an internal -version number. For some compilers this is needed to determine the -correct usage.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPCHECK.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPCHECK.rst deleted file mode 100644 index 50b478f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPCHECK.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_<LANG>_CPPCHECK ---------------------- - -Default value for :prop_tgt:`<LANG>_CPPCHECK` target property. This variable -is used to initialize the property on each target as it is created. This -is done only when ``<LANG>`` is ``C`` or ``CXX``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPLINT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPLINT.rst deleted file mode 100644 index 3b6f452..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_CPPLINT.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_<LANG>_CPPLINT --------------------- - -Default value for :prop_tgt:`<LANG>_CPPLINT` target property. This variable -is used to initialize the property on each target as it is created. This -is done only when ``<LANG>`` is ``C`` or ``CXX``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS.rst deleted file mode 100644 index 14b2694..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_<LANG>_FLAGS ------------------- - -Flags for all build types. - -``<LANG>`` flags used regardless of the value of :variable:`CMAKE_BUILD_TYPE`. - -This is initialized for each language from environment variables: - -* ``CMAKE_C_FLAGS``: - Initialized by the :envvar:`CFLAGS` environment variable. -* ``CMAKE_CXX_FLAGS``: - Initialized by the :envvar:`CXXFLAGS` environment variable. -* ``CMAKE_CUDA_FLAGS``: - Initialized by the :envvar:`CUDAFLAGS` environment variable. -* ``CMAKE_Fortran_FLAGS``: - Initialized by the :envvar:`FFLAGS` environment variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG.rst deleted file mode 100644 index 1dbd036..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_<LANG>_FLAGS_<CONFIG> ---------------------------- - -Flags for language ``<LANG>`` when building for the ``<CONFIG>`` configuration.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.rst deleted file mode 100644 index 1eb5b3f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_<LANG>_FLAGS_<CONFIG>_INIT --------------------------------- - -Value used to initialize the :variable:`CMAKE_<LANG>_FLAGS_<CONFIG>` cache -entry the first time a build tree is configured for language ``<LANG>``. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also :variable:`CMAKE_<LANG>_FLAGS_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.rst deleted file mode 100644 index de7fcfc..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_<LANG>_FLAGS_DEBUG_INIT ------------------------------ - -This variable is the ``Debug`` variant of the -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>_INIT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_INIT.rst deleted file mode 100644 index 4a034e8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_INIT.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_<LANG>_FLAGS_INIT ------------------------ - -Value used to initialize the :variable:`CMAKE_<LANG>_FLAGS` cache entry -the first time a build tree is configured for language ``<LANG>``. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. For example, -the contents of a ``xxxFLAGS`` environment variable will be prepended, -where ``xxx`` will be language-specific but not necessarily the same as -``<LANG>`` (e.g. :envvar:`CXXFLAGS` for ``CXX``, :envvar:`FFLAGS` for -``Fortran``, and so on). - -See also the configuration-specific -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>_INIT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_MINSIZEREL_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_MINSIZEREL_INIT.rst deleted file mode 100644 index 1e7003c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_MINSIZEREL_INIT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_<LANG>_FLAGS_MINSIZEREL_INIT ----------------------------------- - -This variable is the ``MinSizeRel`` variant of the -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>_INIT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.rst deleted file mode 100644 index e7c73fe..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_<LANG>_FLAGS_RELEASE_INIT -------------------------------- - -This variable is the ``Release`` variant of the -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>_INIT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO_INIT.rst deleted file mode 100644 index 3ab3975..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO_INIT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_<LANG>_FLAGS_RELWITHDEBINFO_INIT --------------------------------------- - -This variable is the ``RelWithDebInfo`` variant of the -:variable:`CMAKE_<LANG>_FLAGS_<CONFIG>_INIT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.rst deleted file mode 100644 index e9e04be..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_<LANG>_IMPLICIT_LINK_DIRECTORIES --------------------------------------- - -Implicit linker search path detected for language ``<LANG>``. - -Compilers typically pass directories containing language runtime -libraries and default library search paths when they invoke a linker. -These paths are implicit linker search directories for the compiler's -language. CMake automatically detects these directories for each -language and reports the results in this variable. - -Some toolchains read implicit directories from an environment variable such as -``LIBRARY_PATH``. If using such an environment variable, keep its value -consistent when operating in a given build tree because CMake saves the value -detected when first creating a build tree. - -If policy :policy:`CMP0060` is not set to ``NEW``, then when a library in one -of these directories is given by full path to :command:`target_link_libraries` -CMake will generate the ``-l<name>`` form on link lines for historical -purposes.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.rst deleted file mode 100644 index ec16477..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_<LANG>_IMPLICIT_LINK_LIBRARIES ------------------------------------- - -Implicit link libraries and flags detected for language ``<LANG>``. - -Compilers typically pass language runtime library names and other -flags when they invoke a linker. These flags are implicit link -options for the compiler's language. CMake automatically detects -these libraries and flags for each language and reports the results in -this variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.rst deleted file mode 100644 index 2c8028a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE ---------------------------------- - -Default value for :prop_tgt:`<LANG>_INCLUDE_WHAT_YOU_USE` target property. -This variable is used to initialize the property on each target as it is -created. This is done only when ``<LANG>`` is ``C`` or ``CXX``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.rst deleted file mode 100644 index df51407..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.rst +++ /dev/null
@@ -1,39 +0,0 @@ -CMAKE_<LANG>_LINKER_WRAPPER_FLAG --------------------------------- - -Defines the syntax of compiler driver option to pass options to the linker -tool. It will be used to translate the ``LINKER:`` prefix in the link options -(see :command:`add_link_options` and :command:`target_link_options`). - -This variable holds a :ref:`semicolon-separated list <CMake Language Lists>` of tokens. -If a space (i.e. " ") is specified as last token, flag and ``LINKER:`` -arguments will be specified as separate arguments to the compiler driver. -The :variable:`CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP` variable can be specified -to manage concatenation of arguments. - -For example, for ``Clang`` we have: - -.. code-block:: cmake - - set (CMAKE_C_LINKER_WRAPPER_FLAG "-Xlinker" " ") - -Specifying ``"LINKER:-z,defs"`` will be transformed in -``-Xlinker -z -Xlinker defs``. - -For ``GNU GCC``: - -.. code-block:: cmake - - set (CMAKE_C_LINKER_WRAPPER_FLAG "-Wl,") - set (CMAKE_C_LINKER_WRAPPER_FLAG_SEP ",") - -Specifying ``"LINKER:-z,defs"`` will be transformed in ``-Wl,-z,defs``. - -And for ``SunPro``: - -.. code-block:: cmake - - set (CMAKE_C_LINKER_WRAPPER_FLAG "-Qoption" "ld" " ") - set (CMAKE_C_LINKER_WRAPPER_FLAG_SEP ",") - -Specifying ``"LINKER:-z,defs"`` will be transformed in ``-Qoption ld -z,defs``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.rst deleted file mode 100644 index faf1481..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP ------------------------------------- - -This variable is used with :variable:`CMAKE_<LANG>_LINKER_WRAPPER_FLAG` -variable to format ``LINKER:`` prefix in the link options -(see :command:`add_link_options` and :command:`target_link_options`). - -When specified, arguments of the ``LINKER:`` prefix will be concatenated using -this value as separator.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FILE_FLAG.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FILE_FLAG.rst deleted file mode 100644 index d54f080..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FILE_FLAG.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_<LANG>_LINK_LIBRARY_FILE_FLAG ------------------------------------ - -Language-specific flag to be used to link a library specified by -a path to its file. - -The flag will be used before a library file path is given to the -linker. This is needed only on very few platforms.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FLAG.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FLAG.rst deleted file mode 100644 index d7bb0d8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_FLAG.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_<LANG>_LINK_LIBRARY_FLAG ------------------------------- - -Flag to be used to link a library into a shared library or executable. - -This flag will be used to specify a library to link to a shared library or an -executable for the specific language. On most compilers this is ``-l``.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.rst deleted file mode 100644 index a378657..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_<LANG>_LINK_LIBRARY_SUFFIX --------------------------------- - -Language-specific suffix for libraries that you link to. - -The suffix to use for the end of a library filename, ``.lib`` on Windows.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_SIMULATE_ID.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_SIMULATE_ID.rst deleted file mode 100644 index 15c87a1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_SIMULATE_ID.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_<LANG>_SIMULATE_ID ------------------------- - -Identification string of "simulated" compiler. - -Some compilers simulate other compilers to serve as drop-in -replacements. When CMake detects such a compiler it sets this -variable to what would have been the :variable:`CMAKE_<LANG>_COMPILER_ID` for -the simulated compiler.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.rst deleted file mode 100644 index c8e3d57..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.rst +++ /dev/null
@@ -1,14 +0,0 @@ -CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES ------------------------------------------ - -Include directories to be used for every source file compiled with -the ``<LANG>`` compiler. This is meant for specification of system -include directories needed by the language for the current platform. -The directories always appear at the end of the include path passed -to the compiler. - -This variable should not be set by project code. It is meant to be set by -CMake's platform information modules for the current toolchain, or by a -toolchain file when used with :variable:`CMAKE_TOOLCHAIN_FILE`. - -See also :variable:`CMAKE_<LANG>_STANDARD_LIBRARIES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_LIBRARIES.rst b/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_LIBRARIES.rst deleted file mode 100644 index ba6df93..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LANG_STANDARD_LIBRARIES.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_<LANG>_STANDARD_LIBRARIES -------------------------------- - -Libraries linked into every executable and shared library linked -for language ``<LANG>``. This is meant for specification of system -libraries needed by the language for the current platform. - -This variable should not be set by project code. It is meant to be set by -CMake's platform information modules for the current toolchain, or by a -toolchain file when used with :variable:`CMAKE_TOOLCHAIN_FILE`. - -See also :variable:`CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.rst deleted file mode 100644 index e069cdd..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_LIBRARY_OUTPUT_DIRECTORY_<CONFIG> ---------------------------------------- - -Where to put all the :ref:`LIBRARY <Library Output Artifacts>` -target files when built for a specific configuration. - -This variable is used to initialize the -:prop_tgt:`LIBRARY_OUTPUT_DIRECTORY_<CONFIG>` property on all the targets. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LINK_DIRECTORIES_BEFORE.rst b/share/cmake-3.18/Help/variable/CMAKE_LINK_DIRECTORIES_BEFORE.rst deleted file mode 100644 index 026ca35..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LINK_DIRECTORIES_BEFORE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_LINK_DIRECTORIES_BEFORE ------------------------------ - -Whether to append or prepend directories by default in -:command:`link_directories`. - -This variable affects the default behavior of the :command:`link_directories` -command. Setting this variable to ``ON`` is equivalent to using the ``BEFORE`` -option in all uses of that command.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_END_STATIC.rst b/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_END_STATIC.rst deleted file mode 100644 index 54cdaaa..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_END_STATIC.rst +++ /dev/null
@@ -1,19 +0,0 @@ -CMAKE_LINK_SEARCH_END_STATIC ----------------------------- - -End a link line such that static system libraries are used. - -Some linkers support switches such as ``-Bstatic`` and ``-Bdynamic`` to -determine whether to use static or shared libraries for ``-lXXX`` options. -CMake uses these options to set the link type for libraries whose full -paths are not known or (in some cases) are in implicit link -directories for the platform. By default CMake adds an option at the -end of the library list (if necessary) to set the linker search type -back to its starting type. This property switches the final linker -search type to ``-Bstatic`` regardless of how it started. - -This variable is used to initialize the target property -:prop_tgt:`LINK_SEARCH_END_STATIC` for all targets. If set, it's -value is also used by the :command:`try_compile` command. - -See also :variable:`CMAKE_LINK_SEARCH_START_STATIC`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_START_STATIC.rst b/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_START_STATIC.rst deleted file mode 100644 index 0d52a31..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LINK_SEARCH_START_STATIC.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_LINK_SEARCH_START_STATIC ------------------------------- - -Assume the linker looks for static libraries by default. - -Some linkers support switches such as ``-Bstatic`` and ``-Bdynamic`` to -determine whether to use static or shared libraries for ``-lXXX`` options. -CMake uses these options to set the link type for libraries whose full -paths are not known or (in some cases) are in implicit link -directories for the platform. By default the linker search type is -assumed to be ``-Bdynamic`` at the beginning of the library list. This -property switches the assumption to ``-Bstatic``. It is intended for use -when linking an executable statically (e.g. with the GNU ``-static`` -option). - -This variable is used to initialize the target property -:prop_tgt:`LINK_SEARCH_START_STATIC` for all targets. If set, it's -value is also used by the :command:`try_compile` command. - -See also :variable:`CMAKE_LINK_SEARCH_END_STATIC`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst b/share/cmake-3.18/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst deleted file mode 100644 index 90c4d3f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_LINK_WHAT_YOU_USE.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_LINK_WHAT_YOU_USE ---------------------------------- - -Default value for :prop_tgt:`LINK_WHAT_YOU_USE` target property. -This variable is used to initialize the property on each target as it is -created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MATCH_COUNT.rst b/share/cmake-3.18/Help/variable/CMAKE_MATCH_COUNT.rst deleted file mode 100644 index 355e834..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MATCH_COUNT.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_MATCH_COUNT ------------------ - -The number of matches with the last regular expression. - -When a regular expression match is used, CMake fills in -:variable:`CMAKE_MATCH_<n>` variables with the match contents. -The ``CMAKE_MATCH_COUNT`` variable holds the number of match -expressions when these are filled.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MATCH_n.rst b/share/cmake-3.18/Help/variable/CMAKE_MATCH_n.rst deleted file mode 100644 index c7dd623..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MATCH_n.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_MATCH_<n> ---------------- - -Capture group ``<n>`` matched by the last regular expression, for groups -0 through 9. Group 0 is the entire match. Groups 1 through 9 are the -subexpressions captured by ``()`` syntax. - -When a regular expression match is used, CMake fills in ``CMAKE_MATCH_<n>`` -variables with the match contents. The :variable:`CMAKE_MATCH_COUNT` -variable holds the number of match expressions when these are filled.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.rst b/share/cmake-3.18/Help/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.rst deleted file mode 100644 index 7110b16..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.rst +++ /dev/null
@@ -1,33 +0,0 @@ -CMAKE_MAXIMUM_RECURSION_DEPTH ------------------------------ - -Maximum recursion depth for CMake scripts. It is intended to be set on the -command line with ``-DCMAKE_MAXIMUM_RECURSION_DEPTH=<x>``, or within -``CMakeLists.txt`` by projects that require a large recursion depth. Projects -that set this variable should provide the user with a way to override it. For -example: - -.. code-block:: cmake - - # About to perform deeply recursive actions - if(NOT CMAKE_MAXIMUM_RECURSION_DEPTH) - set(CMAKE_MAXIMUM_RECURSION_DEPTH 2000) - endif() - -If it is not set, or is set to a non-integer value, a sensible default limit is -used. If the recursion limit is reached, the script terminates immediately with -a fatal error. - -Calling any of the following commands increases the recursion depth: - -* :command:`include` -* :command:`find_package` -* :command:`add_subdirectory` -* :command:`try_compile` -* :command:`ctest_read_custom_files` -* :command:`ctest_run_script` (unless ``NEW_PROCESS`` is specified) -* User-defined :command:`function`'s and :command:`macro`'s (note that - :command:`function` and :command:`macro` themselves don't increase recursion - depth) -* Reading or writing variables that are being watched by a - :command:`variable_watch`
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT.rst b/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT.rst deleted file mode 100644 index 6b4ca40..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT.rst +++ /dev/null
@@ -1,62 +0,0 @@ -CMAKE_MESSAGE_CONTEXT ---------------------- - -When enabled by the :manual:`cmake <cmake(1)>` ``--log-context`` command line -option or the :variable:`CMAKE_MESSAGE_CONTEXT_SHOW` variable, the -:command:`message` command converts the ``CMAKE_MESSAGE_CONTEXT`` list into a -dot-separated string surrounded by square brackets and prepends it to each line -for messages of log levels ``NOTICE`` and below. - -For logging contexts to work effectively, projects should generally -``APPEND`` and ``POP_BACK`` an item to the current value of -``CMAKE_MESSAGE_CONTEXT`` rather than replace it. -Projects should not assume the message context at the top of the source tree -is empty, as there are scenarios where the context might have already been set -(e.g. hierarchical projects). - -.. warning:: - - Valid context names are restricted to anything that could be used - as a CMake variable name. All names that begin with an underscore - or the string ``cmake_`` are also reserved for use by CMake and - should not be used by projects. - -Example: - -.. code-block:: cmake - - function(bar) - list(APPEND CMAKE_MESSAGE_CONTEXT "bar") - message(VERBOSE "bar VERBOSE message") - endfunction() - - function(baz) - list(APPEND CMAKE_MESSAGE_CONTEXT "baz") - message(DEBUG "baz DEBUG message") - endfunction() - - function(foo) - list(APPEND CMAKE_MESSAGE_CONTEXT "foo") - bar() - message(TRACE "foo TRACE message") - baz() - endfunction() - - list(APPEND CMAKE_MESSAGE_CONTEXT "top") - - message(VERBOSE "Before `foo`") - foo() - message(VERBOSE "After `foo`") - - list(POP_BACK CMAKE_MESSAGE_CONTEXT) - - -Which results in the following output: - -.. code-block:: none - - -- [top] Before `foo` - -- [top.foo.bar] bar VERBOSE message - -- [top.foo] foo TRACE message - -- [top.foo.baz] baz DEBUG message - -- [top] After `foo`
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT_SHOW.rst b/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT_SHOW.rst deleted file mode 100644 index 7ec218e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_CONTEXT_SHOW.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_MESSAGE_CONTEXT_SHOW --------------------------- - -Setting this variable to true enables showing a context with each line -logged by the :command:`message` command (see :variable:`CMAKE_MESSAGE_CONTEXT` -for how the context itself is specified). - -This variable is an alternative to providing the ``--log-context`` option -on the :manual:`cmake <cmake(1)>` command line. Whereas the command line -option will apply only to that one CMake run, setting -``CMAKE_MESSAGE_CONTEXT_SHOW`` to true as a cache variable will ensure that -subsequent CMake runs will continue to show the message context. - -Projects should not set ``CMAKE_MESSAGE_CONTEXT_SHOW``. It is intended for -users so that they may control whether or not to include context with messages.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_INDENT.rst b/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_INDENT.rst deleted file mode 100644 index 7e44a4c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_INDENT.rst +++ /dev/null
@@ -1,32 +0,0 @@ -CMAKE_MESSAGE_INDENT --------------------- - -The :command:`message` command joins the strings from this list and for -log levels of ``NOTICE`` and below, it prepends the resultant string to -each line of the message. - -Example: - -.. code-block:: cmake - - list(APPEND listVar one two three) - - message(VERBOSE [[Collected items in the "listVar":]]) - list(APPEND CMAKE_MESSAGE_INDENT " ") - - foreach(item IN LISTS listVar) - message(VERBOSE ${item}) - endforeach() - - list(POP_BACK CMAKE_MESSAGE_INDENT) - message(VERBOSE "No more indent") - -Which results in the following output: - -.. code-block:: none - - -- Collected items in the "listVar": - -- one - -- two - -- three - -- No more indent
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_LOG_LEVEL.rst b/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_LOG_LEVEL.rst deleted file mode 100644 index 1d4cfe6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MESSAGE_LOG_LEVEL.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_MESSAGE_LOG_LEVEL ------------------------ - -When set, this variable specifies the logging level used by the -:command:`message` command. Valid values are the same as those for the -``--log-level`` command line option of the :manual:`cmake(1)` program. -If this variable is set and the ``--log-level`` command line option is -given, the command line option takes precedence. - -The main advantage to using this variable is to make a log level persist -between CMake runs. Setting it as a cache variable will ensure that -subsequent CMake runs will continue to use the chosen log level. - -Projects should not set this variable, it is intended for users so that -they may control the log level according to their own needs.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MFC_FLAG.rst b/share/cmake-3.18/Help/variable/CMAKE_MFC_FLAG.rst deleted file mode 100644 index 2c4d1c5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MFC_FLAG.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_MFC_FLAG --------------- - -Use the MFC library for an executable or dll. - -Enables the use of the Microsoft Foundation Classes (MFC). -It should be set to ``1`` for the static MFC library, and -``2`` for the shared MFC library. This is used in Visual Studio -project files. - -Usage example: - -.. code-block:: cmake - - add_definitions(-D_AFXDLL) - set(CMAKE_MFC_FLAG 2) - add_executable(CMakeSetup WIN32 ${SRCS})
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MINIMUM_REQUIRED_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_MINIMUM_REQUIRED_VERSION.rst deleted file mode 100644 index f466468..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MINIMUM_REQUIRED_VERSION.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_MINIMUM_REQUIRED_VERSION ------------------------------- - -The ``<min>`` version of CMake given to the most recent call to the -:command:`cmake_minimum_required(VERSION)` command.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.rst deleted file mode 100644 index 3279014..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_MODULE_LINKER_FLAGS_<CONFIG>_INIT ---------------------------------------- - -Value used to initialize the :variable:`CMAKE_MODULE_LINKER_FLAGS_<CONFIG>` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also :variable:`CMAKE_MODULE_LINKER_FLAGS_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.rst deleted file mode 100644 index 91b39f6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_MODULE_LINKER_FLAGS_INIT ------------------------------- - -Value used to initialize the :variable:`CMAKE_MODULE_LINKER_FLAGS` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also the configuration-specific variable -:variable:`CMAKE_MODULE_LINKER_FLAGS_<CONFIG>_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MSVCIDE_RUN_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_MSVCIDE_RUN_PATH.rst deleted file mode 100644 index 22e727f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MSVCIDE_RUN_PATH.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_MSVCIDE_RUN_PATH ----------------------- - -Extra PATH locations that should be used when executing -:command:`add_custom_command` or :command:`add_custom_target` when using the -:generator:`Visual Studio 9 2008` (or above) generator. This allows -for running commands and using dll's that the IDE environment is not aware of. - -If not set explicitly the value is initialized by the ``CMAKE_MSVCIDE_RUN_PATH`` -environment variable, if set, and otherwise left empty.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_MSVC_RUNTIME_LIBRARY.rst b/share/cmake-3.18/Help/variable/CMAKE_MSVC_RUNTIME_LIBRARY.rst deleted file mode 100644 index 8b54e7e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_MSVC_RUNTIME_LIBRARY.rst +++ /dev/null
@@ -1,32 +0,0 @@ -CMAKE_MSVC_RUNTIME_LIBRARY --------------------------- - -Select the MSVC runtime library for use by compilers targeting the MSVC ABI. -This variable is used to initialize the :prop_tgt:`MSVC_RUNTIME_LIBRARY` -property on all targets as they are created. It is also propagated by -calls to the :command:`try_compile` command into the test project. - -The allowed values are: - -.. include:: ../prop_tgt/MSVC_RUNTIME_LIBRARY-VALUES.txt - -Use :manual:`generator expressions <cmake-generator-expressions(7)>` to -support per-configuration specification. For example, the code: - -.. code-block:: cmake - - set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>") - -selects for all following targets a multi-threaded statically-linked runtime -library with or without debug information depending on the configuration. - -If this variable is not set then the :prop_tgt:`MSVC_RUNTIME_LIBRARY` target -property will not be set automatically. If that property is not set then -CMake uses the default value ``MultiThreaded$<$<CONFIG:Debug>:Debug>DLL`` -to select a MSVC runtime library. - -.. note:: - - This variable has effect only when policy :policy:`CMP0091` is set to ``NEW`` - prior to the first :command:`project` or :command:`enable_language` command - that enables a language using a compiler targeting the MSVC ABI.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_NETRC.rst b/share/cmake-3.18/Help/variable/CMAKE_NETRC.rst deleted file mode 100644 index 903ec31..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_NETRC.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_NETRC ------------ - -This variable is used to initialize the ``NETRC`` option for -:command:`file(DOWNLOAD)` and :command:`file(UPLOAD)` commands and the -module :module:`ExternalProject`. See those commands for additional -information. - -The local option takes precedence over this variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_NETRC_FILE.rst b/share/cmake-3.18/Help/variable/CMAKE_NETRC_FILE.rst deleted file mode 100644 index 0f09afe..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_NETRC_FILE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_NETRC_FILE ----------------- - -This variable is used to initialize the ``NETRC_FILE`` option for -:command:`file(DOWNLOAD)` and :command:`file(UPLOAD)` commands and the -module :module:`ExternalProject`. See those commands for additional -information. - -The local option takes precedence over this variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.rst b/share/cmake-3.18/Help/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.rst deleted file mode 100644 index 64091aa..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.rst +++ /dev/null
@@ -1,27 +0,0 @@ -CMAKE_NINJA_OUTPUT_PATH_PREFIX ------------------------------- - -Set output files path prefix for the :generator:`Ninja` generator. - -Every output files listed in the generated ``build.ninja`` will be -prefixed by the contents of this variable (a trailing slash is -appended if missing). This is useful when the generated ninja file is -meant to be embedded as a ``subninja`` file into a *super* ninja -project. For example, a ninja build file generated with a command -like:: - - cd top-build-dir/sub && - cmake -G Ninja -DCMAKE_NINJA_OUTPUT_PATH_PREFIX=sub/ path/to/source - -can be embedded in ``top-build-dir/build.ninja`` with a directive like -this:: - - subninja sub/build.ninja - -The ``auto-regeneration`` rule in ``top-build-dir/build.ninja`` must have an -order-only dependency on ``sub/build.ninja``. - -.. note:: - When ``CMAKE_NINJA_OUTPUT_PATH_PREFIX`` is set, the project generated - by CMake cannot be used as a standalone project. No default targets - are specified.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_NO_BUILTIN_CHRPATH.rst b/share/cmake-3.18/Help/variable/CMAKE_NO_BUILTIN_CHRPATH.rst deleted file mode 100644 index 189f59f..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_NO_BUILTIN_CHRPATH.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_NO_BUILTIN_CHRPATH ------------------------- - -Do not use the builtin ELF editor to fix RPATHs on installation. - -When an ELF binary needs to have a different RPATH after installation -than it does in the build tree, CMake uses a builtin editor to change -the RPATH in the installed copy. If this variable is set to true then -CMake will relink the binary before installation instead of using its -builtin editor.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_EXTENSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_EXTENSIONS.rst deleted file mode 100644 index 8afa6f2..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_EXTENSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJCXX_EXTENSIONS ------------------------ - -Default value for :prop_tgt:`OBJCXX_EXTENSIONS` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJCXX_EXTENSIONS` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD.rst deleted file mode 100644 index 4e5016a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJCXX_STANDARD ---------------------- - -Default value for :prop_tgt:`OBJCXX_STANDARD` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJCXX_STANDARD` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.rst deleted file mode 100644 index 3a0602a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJCXX_STANDARD_REQUIRED ------------------------------- - -Default value for :prop_tgt:`OBJCXX_STANDARD_REQUIRED` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJCXX_STANDARD_REQUIRED` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJC_EXTENSIONS.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJC_EXTENSIONS.rst deleted file mode 100644 index d9619d8..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJC_EXTENSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJC_EXTENSIONS ---------------------- - -Default value for :prop_tgt:`OBJC_EXTENSIONS` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJC_EXTENSIONS` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD.rst deleted file mode 100644 index 976c441..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJC_STANDARD -------------------- - -Default value for :prop_tgt:`OBJC_STANDARD` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJC_STANDARD` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD_REQUIRED.rst b/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD_REQUIRED.rst deleted file mode 100644 index 5c02096..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_OBJC_STANDARD_REQUIRED.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_OBJC_STANDARD_REQUIRED ----------------------------- - -Default value for :prop_tgt:`OBJC_STANDARD_REQUIRED` property of targets. - -This variable is used to initialize the :prop_tgt:`OBJC_STANDARD_REQUIRED` -property on all targets. See that target property for additional -information. - -See the :manual:`cmake-compile-features(7)` manual for information on -compile features and a list of supported compilers.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PCH_WARN_INVALID.rst b/share/cmake-3.18/Help/variable/CMAKE_PCH_WARN_INVALID.rst deleted file mode 100644 index e152abd..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PCH_WARN_INVALID.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_PCH_WARN_INVALID ----------------------- - -This variable is used to initialize the :prop_tgt:`PCH_WARN_INVALID` -property of targets when they are created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.rst b/share/cmake-3.18/Help/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.rst deleted file mode 100644 index 43582be..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_POLICY_DEFAULT_CMP<NNNN> ------------------------------- - -Default for CMake Policy ``CMP<NNNN>`` when it is otherwise left unset. - -Commands :command:`cmake_minimum_required(VERSION)` and -:command:`cmake_policy(VERSION)` by default leave policies introduced after -the given version unset. Set ``CMAKE_POLICY_DEFAULT_CMP<NNNN>`` to ``OLD`` -or ``NEW`` to specify the default for policy ``CMP<NNNN>``, where ``<NNNN>`` -is the policy number. - -This variable should not be set by a project in CMake code; use -:command:`cmake_policy(SET)` instead. Users running CMake may set this -variable in the cache (e.g. ``-DCMAKE_POLICY_DEFAULT_CMP<NNNN>=<OLD|NEW>``) -to set a policy not otherwise set by the project. Set to ``OLD`` to quiet a -policy warning while using old behavior or to ``NEW`` to try building the -project with new behavior.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_POLICY_WARNING_CMPNNNN.rst b/share/cmake-3.18/Help/variable/CMAKE_POLICY_WARNING_CMPNNNN.rst deleted file mode 100644 index de71d0e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_POLICY_WARNING_CMPNNNN.rst +++ /dev/null
@@ -1,33 +0,0 @@ -CMAKE_POLICY_WARNING_CMP<NNNN> ------------------------------- - -Explicitly enable or disable the warning when CMake Policy ``CMP<NNNN>`` -is not set. This is meaningful only for the few policies that do not -warn by default: - -* ``CMAKE_POLICY_WARNING_CMP0025`` controls the warning for - policy :policy:`CMP0025`. -* ``CMAKE_POLICY_WARNING_CMP0047`` controls the warning for - policy :policy:`CMP0047`. -* ``CMAKE_POLICY_WARNING_CMP0056`` controls the warning for - policy :policy:`CMP0056`. -* ``CMAKE_POLICY_WARNING_CMP0060`` controls the warning for - policy :policy:`CMP0060`. -* ``CMAKE_POLICY_WARNING_CMP0065`` controls the warning for - policy :policy:`CMP0065`. -* ``CMAKE_POLICY_WARNING_CMP0066`` controls the warning for - policy :policy:`CMP0066`. -* ``CMAKE_POLICY_WARNING_CMP0067`` controls the warning for - policy :policy:`CMP0067`. -* ``CMAKE_POLICY_WARNING_CMP0082`` controls the warning for - policy :policy:`CMP0082`. -* ``CMAKE_POLICY_WARNING_CMP0089`` controls the warning for - policy :policy:`CMP0089`. -* ``CMAKE_POLICY_WARNING_CMP0102`` controls the warning for - policy :policy:`CMP0102`. - -This variable should not be set by a project in CMake code. Project -developers running CMake may set this variable in their cache to -enable the warning (e.g. ``-DCMAKE_POLICY_WARNING_CMP<NNNN>=ON``). -Alternatively, running :manual:`cmake(1)` with the ``--debug-output``, -``--trace``, or ``--trace-expand`` option will also enable the warning.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_POSITION_INDEPENDENT_CODE.rst b/share/cmake-3.18/Help/variable/CMAKE_POSITION_INDEPENDENT_CODE.rst deleted file mode 100644 index 43b1397..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_POSITION_INDEPENDENT_CODE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_POSITION_INDEPENDENT_CODE -------------------------------- - -Default value for :prop_tgt:`POSITION_INDEPENDENT_CODE` of targets. - -This variable is used to initialize the -:prop_tgt:`POSITION_INDEPENDENT_CODE` property on all the targets. -See that target property for additional information. If set, it's -value is also used by the :command:`try_compile` command.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_DESCRIPTION.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_DESCRIPTION.rst deleted file mode 100644 index 51b0592..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_DESCRIPTION.rst +++ /dev/null
@@ -1,35 +0,0 @@ -CMAKE_PROJECT_DESCRIPTION -------------------------- - -The description of the top level project. - -This variable holds the description of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. In the event that -the top level CMakeLists.txt contains multiple :command:`project` calls, -the most recently called one from that top level CMakeLists.txt will determine -the value that ``CMAKE_PROJECT_DESCRIPTION`` contains. For example, consider -the following top level CMakeLists.txt: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.0) - project(First DESCRIPTION "I am First") - project(Second DESCRIPTION "I am Second") - add_subdirectory(sub) - project(Third DESCRIPTION "I am Third") - -And ``sub/CMakeLists.txt`` with the following contents: - -.. code-block:: cmake - - project(SubProj DESCRIPTION "I am SubProj") - message("CMAKE_PROJECT_DESCRIPTION = ${CMAKE_PROJECT_DESCRIPTION}") - -The most recently seen :command:`project` command from the top level -CMakeLists.txt would be ``project(Second ...)``, so this will print:: - - CMAKE_PROJECT_DESCRIPTION = I am Second - -To obtain the description from the most recent call to :command:`project` in -the current directory scope or above, see the :variable:`PROJECT_DESCRIPTION` -variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_HOMEPAGE_URL.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_HOMEPAGE_URL.rst deleted file mode 100644 index ee0bf7c..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_HOMEPAGE_URL.rst +++ /dev/null
@@ -1,35 +0,0 @@ -CMAKE_PROJECT_HOMEPAGE_URL --------------------------- - -The homepage URL of the top level project. - -This variable holds the homepage URL of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. In the event that -the top level CMakeLists.txt contains multiple :command:`project` calls, -the most recently called one from that top level CMakeLists.txt will determine -the value that ``CMAKE_PROJECT_HOMEPAGE_URL`` contains. For example, consider -the following top level CMakeLists.txt: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.0) - project(First HOMEPAGE_URL "http://first.example.com") - project(Second HOMEPAGE_URL "http://second.example.com") - add_subdirectory(sub) - project(Third HOMEPAGE_URL "http://third.example.com") - -And ``sub/CMakeLists.txt`` with the following contents: - -.. code-block:: cmake - - project(SubProj HOMEPAGE_URL "http://subproj.example.com") - message("CMAKE_PROJECT_HOMEPAGE_URL = ${CMAKE_PROJECT_HOMEPAGE_URL}") - -The most recently seen :command:`project` command from the top level -CMakeLists.txt would be ``project(Second ...)``, so this will print:: - - CMAKE_PROJECT_HOMEPAGE_URL = http://second.example.com - -To obtain the homepage URL from the most recent call to :command:`project` in -the current directory scope or above, see the :variable:`PROJECT_HOMEPAGE_URL` -variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE.rst deleted file mode 100644 index 5835264..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_PROJECT_INCLUDE ---------------------- - -A CMake language file or module to be included as the last step of all -:command:`project` command calls. This is intended for injecting custom code -into project builds without modifying their source. - -See also the :variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE`, -:variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE` and -:variable:`CMAKE_PROJECT_INCLUDE_BEFORE` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE_BEFORE.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE_BEFORE.rst deleted file mode 100644 index 280c14a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_INCLUDE_BEFORE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_PROJECT_INCLUDE_BEFORE ----------------------------- - -A CMake language file or module to be included as the first step of all -:command:`project` command calls. This is intended for injecting custom code -into project builds without modifying their source. - -See also the :variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE`, -:variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE` and -:variable:`CMAKE_PROJECT_INCLUDE` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.rst deleted file mode 100644 index db1432d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE -------------------------------------------- - -A CMake language file or module to be included as the first step of any -:command:`project` command calls that specify ``<PROJECT-NAME>`` as the project -name. This is intended for injecting custom code into project builds without -modifying their source. - -See also the :variable:`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE`, -:variable:`CMAKE_PROJECT_INCLUDE` and -:variable:`CMAKE_PROJECT_INCLUDE_BEFORE` variables.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION.rst deleted file mode 100644 index 4f8f556..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION.rst +++ /dev/null
@@ -1,35 +0,0 @@ -CMAKE_PROJECT_VERSION ---------------------- - -The version of the top level project. - -This variable holds the version of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. In the event that -the top level CMakeLists.txt contains multiple :command:`project` calls, -the most recently called one from that top level CMakeLists.txt will determine -the value that ``CMAKE_PROJECT_VERSION`` contains. For example, consider -the following top level CMakeLists.txt: - -.. code-block:: cmake - - cmake_minimum_required(VERSION 3.0) - project(First VERSION 1.2.3) - project(Second VERSION 3.4.5) - add_subdirectory(sub) - project(Third VERSION 6.7.8) - -And ``sub/CMakeLists.txt`` with the following contents: - -.. code-block:: cmake - - project(SubProj VERSION 1) - message("CMAKE_PROJECT_VERSION = ${CMAKE_PROJECT_VERSION}") - -The most recently seen :command:`project` command from the top level -CMakeLists.txt would be ``project(Second ...)``, so this will print:: - - CMAKE_PROJECT_VERSION = 3.4.5 - -To obtain the version from the most recent call to :command:`project` in -the current directory scope or above, see the :variable:`PROJECT_VERSION` -variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MAJOR.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MAJOR.rst deleted file mode 100644 index f1001ac..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MAJOR.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_PROJECT_VERSION_MAJOR ---------------------------- - -The major version of the top level project. - -This variable holds the major version of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. Please see -:variable:`CMAKE_PROJECT_VERSION` documentation for the behavior when -multiple :command:`project` commands are used in the sources.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MINOR.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MINOR.rst deleted file mode 100644 index 13202be..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_MINOR.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_PROJECT_VERSION_MINOR ---------------------------- - -The minor version of the top level project. - -This variable holds the minor version of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. Please see -:variable:`CMAKE_PROJECT_VERSION` documentation for the behavior when -multiple :command:`project` commands are used in the sources.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_PATCH.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_PATCH.rst deleted file mode 100644 index b8570d9..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_PATCH.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_PROJECT_VERSION_PATCH ---------------------------- - -The patch version of the top level project. - -This variable holds the patch version of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. Please see -:variable:`CMAKE_PROJECT_VERSION` documentation for the behavior when -multiple :command:`project` commands are used in the sources.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_TWEAK.rst b/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_TWEAK.rst deleted file mode 100644 index e1ad4be..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_PROJECT_VERSION_TWEAK.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_PROJECT_VERSION_TWEAK ---------------------------- - -The tweak version of the top level project. - -This variable holds the tweak version of the project as specified in the top -level CMakeLists.txt file by a :command:`project` command. Please see -:variable:`CMAKE_PROJECT_VERSION` documentation for the behavior when -multiple :command:`project` commands are used in the sources.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_RULE_MESSAGES.rst b/share/cmake-3.18/Help/variable/CMAKE_RULE_MESSAGES.rst deleted file mode 100644 index 7460a81..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_RULE_MESSAGES.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_RULE_MESSAGES -------------------- - -Specify whether to report a message for each make rule. - -If set in the cache it is used to initialize the value of the :prop_gbl:`RULE_MESSAGES` property. -Users may disable the option in their local build tree to disable granular messages -and report only as each target completes in Makefile builds.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.rst b/share/cmake-3.18/Help/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.rst deleted file mode 100644 index 080dea6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_RUNTIME_OUTPUT_DIRECTORY_<CONFIG> ---------------------------------------- - -Where to put all the :ref:`RUNTIME <Runtime Output Artifacts>` -target files when built for a specific configuration. - -This variable is used to initialize the -:prop_tgt:`RUNTIME_OUTPUT_DIRECTORY_<CONFIG>` property on all the targets. -See that target property for additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.rst deleted file mode 100644 index 185df38..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_SHARED_LINKER_FLAGS_<CONFIG>_INIT ---------------------------------------- - -Value used to initialize the :variable:`CMAKE_SHARED_LINKER_FLAGS_<CONFIG>` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also :variable:`CMAKE_SHARED_LINKER_FLAGS_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.rst deleted file mode 100644 index cb819a7..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_SHARED_LINKER_FLAGS_INIT ------------------------------- - -Value used to initialize the :variable:`CMAKE_SHARED_LINKER_FLAGS` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also the configuration-specific variable -:variable:`CMAKE_SHARED_LINKER_FLAGS_<CONFIG>_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.rst deleted file mode 100644 index a49d1cb..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_STATIC_LINKER_FLAGS_<CONFIG>_INIT ---------------------------------------- - -Value used to initialize the :variable:`CMAKE_STATIC_LINKER_FLAGS_<CONFIG>` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also :variable:`CMAKE_STATIC_LINKER_FLAGS_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.rst b/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.rst deleted file mode 100644 index 113ca71..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_STATIC_LINKER_FLAGS_INIT ------------------------------- - -Value used to initialize the :variable:`CMAKE_STATIC_LINKER_FLAGS` -cache entry the first time a build tree is configured. -This variable is meant to be set by a :variable:`toolchain file -<CMAKE_TOOLCHAIN_FILE>`. CMake may prepend or append content to -the value based on the environment and target platform. - -See also the configuration-specific variable -:variable:`CMAKE_STATIC_LINKER_FLAGS_<CONFIG>_INIT`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.rst b/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.rst deleted file mode 100644 index 02c8663..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.rst +++ /dev/null
@@ -1,25 +0,0 @@ -CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS ---------------------------------- - -This variable contains a list of env vars as a list of tokens with the -syntax ``var=value``. - -Example: - -.. code-block:: cmake - - set(CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS - "FOO=FOO1\;FOO2\;FOON" - "BAR=BAR1\;BAR2\;BARN" - "BAZ=BAZ1\;BAZ2\;BAZN" - "FOOBAR=FOOBAR1\;FOOBAR2\;FOOBARN" - "VALID=" - ) - -In case of malformed variables CMake will fail: - -.. code-block:: cmake - - set(CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS - "THIS_IS_NOT_VALID" - )
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE.rst b/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE.rst deleted file mode 100644 index d654425..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE ---------------------------------------- - -If this variable evaluates to ``ON`` at the end of the top-level -``CMakeLists.txt`` file, the :generator:`Sublime Text 2` extra generator -excludes the build tree from the ``.sublime-project`` if it is inside the -source tree.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SUPPRESS_REGENERATION.rst b/share/cmake-3.18/Help/variable/CMAKE_SUPPRESS_REGENERATION.rst deleted file mode 100644 index 96184dd..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SUPPRESS_REGENERATION.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_SUPPRESS_REGENERATION ---------------------------- - -If ``CMAKE_SUPPRESS_REGENERATION`` is ``OFF``, which is default, then CMake -adds a special target on which all other targets depend that checks the build -system and optionally re-runs CMake to regenerate the build system when -the target specification source changes. - -If this variable evaluates to ``ON`` at the end of the top-level -``CMakeLists.txt`` file, CMake will not add the regeneration target to the -build system or perform any build system checks.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_COMPILE.rst b/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_COMPILE.rst deleted file mode 100644 index e96c62b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_COMPILE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_SYSROOT_COMPILE ---------------------- - -Path to pass to the compiler in the ``--sysroot`` flag when compiling source -files. This is the same as :variable:`CMAKE_SYSROOT` but is used only for -compiling sources and not linking. - -This variable may only be set in a toolchain file specified by -the :variable:`CMAKE_TOOLCHAIN_FILE` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_LINK.rst b/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_LINK.rst deleted file mode 100644 index 88b48ef..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SYSROOT_LINK.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_SYSROOT_LINK ------------------- - -Path to pass to the compiler in the ``--sysroot`` flag when linking. This is -the same as :variable:`CMAKE_SYSROOT` but is used only for linking and not -compiling sources. - -This variable may only be set in a toolchain file specified by -the :variable:`CMAKE_TOOLCHAIN_FILE` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.rst deleted file mode 100644 index 666af46..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_SYSTEM_APPBUNDLE_PATH ---------------------------- - -Search path for macOS application bundles used by the :command:`find_program`, -and :command:`find_package` commands. By default it contains the standard -directories for the current system. It is *not* intended to be modified by -the project, use :variable:`CMAKE_APPBUNDLE_PATH` for this.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.rst b/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.rst deleted file mode 100644 index 14ba18e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_SYSTEM_FRAMEWORK_PATH ---------------------------- - -Search path for macOS frameworks used by the :command:`find_library`, -:command:`find_package`, :command:`find_path`, and :command:`find_file` -commands. By default it contains the standard directories for the -current system. It is *not* intended to be modified by the project, -use :variable:`CMAKE_FRAMEWORK_PATH` for this.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_PROCESSOR.rst b/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_PROCESSOR.rst deleted file mode 100644 index 8ad89f1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_SYSTEM_PROCESSOR.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_SYSTEM_PROCESSOR ----------------------- - -The name of the CPU CMake is building for. - -This variable is the same as :variable:`CMAKE_HOST_SYSTEM_PROCESSOR` if -you build for the host system instead of the target system when -cross compiling.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_Swift_LANGUAGE_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_Swift_LANGUAGE_VERSION.rst deleted file mode 100644 index b4a74eb..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_Swift_LANGUAGE_VERSION.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_Swift_LANGUAGE_VERSION ----------------------------- - -Set to the Swift language version number. If not set, the oldest legacy -version known to be available in the host Xcode version is assumed: - -* Swift ``4.0`` for Xcode 10.2 and above. -* Swift ``3.0`` for Xcode 8.3 and above. -* Swift ``2.3`` for Xcode 8.2 and below.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_Swift_MODULE_DIRECTORY.rst b/share/cmake-3.18/Help/variable/CMAKE_Swift_MODULE_DIRECTORY.rst deleted file mode 100644 index b11253b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_Swift_MODULE_DIRECTORY.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_Swift_MODULE_DIRECTORY ----------------------------- - -Swift module output directory. - -This variable is used to initialise the :prop_tgt:`Swift_MODULE_DIRECTORY` -property on all the targets. See the target property for additional -information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_Swift_NUM_THREADS.rst b/share/cmake-3.18/Help/variable/CMAKE_Swift_NUM_THREADS.rst deleted file mode 100644 index cb33678..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_Swift_NUM_THREADS.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_Swift_NUM_THREADS ------------------------ - -Number of threads for parallel compilation for Swift targets. - -This variable controls the number of parallel jobs that the swift driver creates -for building targets. If not specified, it will default to the number of -logical CPUs on the host.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_TOOLCHAIN_FILE.rst b/share/cmake-3.18/Help/variable/CMAKE_TOOLCHAIN_FILE.rst deleted file mode 100644 index 168ee74..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_TOOLCHAIN_FILE.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_TOOLCHAIN_FILE --------------------- - -Path to toolchain file supplied to :manual:`cmake(1)`. - -This variable is specified on the command line when cross-compiling with CMake. -It is the path to a file which is read early in the CMake run and which -specifies locations for compilers and toolchain utilities, and other target -platform and compiler related information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.rst b/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.rst deleted file mode 100644 index 0f96787..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.rst +++ /dev/null
@@ -1,26 +0,0 @@ -CMAKE_TRY_COMPILE_PLATFORM_VARIABLES ------------------------------------- - -List of variables that the :command:`try_compile` command source file signature -must propagate into the test project in order to target the same platform as -the host project. - -This variable should not be set by project code. It is meant to be set by -CMake's platform information modules for the current toolchain, or by a -toolchain file when used with :variable:`CMAKE_TOOLCHAIN_FILE`. - -Variables meaningful to CMake, such as :variable:`CMAKE_<LANG>_FLAGS`, are -propagated automatically. The ``CMAKE_TRY_COMPILE_PLATFORM_VARIABLES`` -variable may be set to pass custom variables meaningful to a toolchain file. -For example, a toolchain file may contain: - -.. code-block:: cmake - - set(CMAKE_SYSTEM_NAME ...) - set(CMAKE_TRY_COMPILE_PLATFORM_VARIABLES MY_CUSTOM_VARIABLE) - # ... use MY_CUSTOM_VARIABLE ... - -If a user passes ``-DMY_CUSTOM_VARIABLE=SomeValue`` to CMake then this -setting will be made visible to the toolchain file both for the main -project and for test projects generated by the :command:`try_compile` -command source file signature.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.rst b/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.rst deleted file mode 100644 index 5fa8dfc..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_TRY_COMPILE_TARGET_TYPE ------------------------------ - -Type of target generated for :command:`try_compile` calls using the -source file signature. Valid values are: - -``EXECUTABLE`` - Use :command:`add_executable` to name the source file in the - generated project. This is the default if no value is given. - -``STATIC_LIBRARY`` - Use :command:`add_library` with the ``STATIC`` option to name the - source file in the generated project. This avoids running the - linker and is intended for use with cross-compiling toolchains - that cannot link without custom flags or linker scripts.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD.rst b/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD.rst deleted file mode 100644 index a86cd67..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD.rst +++ /dev/null
@@ -1,20 +0,0 @@ -CMAKE_UNITY_BUILD ------------------ - -This variable is used to initialize the :prop_tgt:`UNITY_BUILD` -property of targets when they are created. Setting it to true -enables batch compilation of multiple sources within each target. -This feature is known as a *Unity* or *Jumbo* build. - -Projects should not set this variable, it is intended as a developer -control to be set on the :manual:`cmake(1)` command line or other -equivalent methods. The developer must have the ability to enable or -disable unity builds according to the capabilities of their own machine -and compiler. - -By default, this variable is not set, which will result in unity builds -being disabled. - -.. note:: - This option currently does not work well in combination with - the :variable:`CMAKE_EXPORT_COMPILE_COMMANDS` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.rst b/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.rst deleted file mode 100644 index 7988d4b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_UNITY_BUILD_BATCH_SIZE ----------------------------- - -This variable is used to initialize the :prop_tgt:`UNITY_BUILD_BATCH_SIZE` -property of targets when they are created. It specifies the default upper -limit on the number of source files that may be combined in any one unity -source file when unity builds are enabled for a target.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_GLOBALS.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_GLOBALS.rst deleted file mode 100644 index 83777b6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_GLOBALS.rst +++ /dev/null
@@ -1,21 +0,0 @@ -CMAKE_VS_GLOBALS ----------------- - -List of ``Key=Value`` records to be set per target as target properties -:prop_tgt:`VS_GLOBAL_<variable>` with ``variable=Key`` and value ``Value``. - -For example: - -.. code-block:: cmake - - set(CMAKE_VS_GLOBALS - "DefaultLanguage=en-US" - "MinimumVisualStudioVersion=14.0" - ) - -will set properties ``VS_GLOBAL_DefaultLanguage`` to ``en-US`` and -``VS_GLOBAL_MinimumVisualStudioVersion`` to ``14.0`` for all targets -(except for ``INTERFACE`` libraries). - -This variable is meant to be set by a -:variable:`toolchain file <CMAKE_TOOLCHAIN_FILE>`.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.rst deleted file mode 100644 index f54472a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD ------------------------------------------ - -Include ``INSTALL`` target to default build. - -In Visual Studio solution, by default the ``INSTALL`` target will not be part -of the default build. Setting this variable will enable the ``INSTALL`` target -to be part of the default build.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD.rst deleted file mode 100644 index 693ba45..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD ------------------------------------------ - -Include ``PACKAGE`` target to default build. - -In Visual Studio solution, by default the ``PACKAGE`` target will not be part -of the default build. Setting this variable will enable the ``PACKAGE`` target -to be part of the default build.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.rst deleted file mode 100644 index 546cdf4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CMAKE_VS_JUST_MY_CODE_DEBUGGING -------------------------------- - -Enable Just My Code with Visual Studio debugger. - -This variable is used to initialize the :prop_tgt:`VS_JUST_MY_CODE_DEBUGGING` -property on all targets when they are created. See that target property for -additional information.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_NsightTegra_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_NsightTegra_VERSION.rst deleted file mode 100644 index 386c3a9..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_NsightTegra_VERSION.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CMAKE_VS_NsightTegra_VERSION ----------------------------- - -When using a Visual Studio generator with the -:variable:`CMAKE_SYSTEM_NAME` variable set to ``Android``, -this variable contains the version number of the -installed NVIDIA Nsight Tegra Visual Studio Edition.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME.rst deleted file mode 100644 index 7a4642a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_VS_PLATFORM_NAME ----------------------- - -Visual Studio target platform name used by the current generator. - -VS 8 and above allow project files to specify a target platform. -CMake provides the name of the chosen platform in this variable. -See the :variable:`CMAKE_GENERATOR_PLATFORM` variable for details. - -See also the :variable:`CMAKE_VS_PLATFORM_NAME_DEFAULT` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME_DEFAULT.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME_DEFAULT.rst deleted file mode 100644 index c18e6fd..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_NAME_DEFAULT.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_VS_PLATFORM_NAME_DEFAULT ------------------------------- - -Default for the Visual Studio target platform name for the current generator -without considering the value of the :variable:`CMAKE_GENERATOR_PLATFORM` -variable. For :ref:`Visual Studio Generators` for VS 2017 and below this is -always ``Win32``. For VS 2019 and above this is based on the host platform. - -See also the :variable:`CMAKE_VS_PLATFORM_NAME` variable.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA.rst deleted file mode 100644 index 67b7f74..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA.rst +++ /dev/null
@@ -1,14 +0,0 @@ -CMAKE_VS_PLATFORM_TOOLSET_CUDA ------------------------------- - -NVIDIA CUDA Toolkit version whose Visual Studio toolset to use. - -The :ref:`Visual Studio Generators` for VS 2010 and above support using -a CUDA toolset provided by a CUDA Toolkit. The toolset version number -may be specified by a field in :variable:`CMAKE_GENERATOR_TOOLSET` of -the form ``cuda=8.0``. Or it is automatically detected if a path to -a standalone CUDA directory is specified in the form ``cuda=C:\path\to\cuda``. -If none is specified CMake will choose a default version. -CMake provides the selected CUDA toolset version in this variable. -The value may be empty if no CUDA Toolkit with Visual Studio integration -is installed.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR.rst deleted file mode 100644 index 060648a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR ------------------------------------------ - -Path to standalone NVIDIA CUDA Toolkit (eg. extracted from installer). - -The :ref:`Visual Studio Generators` for VS 2010 and above support using -a standalone (non-installed) NVIDIA CUDA toolkit. The path -may be specified by a field in :variable:`CMAKE_GENERATOR_TOOLSET` of -the form ``cuda=C:\path\to\cuda``. The given directory must at least -contain a folder ``.\nvcc`` and must provide Visual Studio integration -files in path ``.\CUDAVisualStudioIntegration\extras\ -visual_studio_integration\MSBuildExtensions\``. One can create a standalone -CUDA toolkit directory by either opening a installer with 7zip or -copying the files that are extracted by the running installer. -The value may be empty if no path to a standalone CUDA Toolkit was -specified.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.rst deleted file mode 100644 index 99ac90d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE -------------------------------------------- - -Visual Studio preferred tool architecture. - -The :ref:`Visual Studio Generators` for VS 2013 and above support using -either the 32-bit or 64-bit host toolchains by specifying a ``host=x86`` -or ``host=x64`` value in the :variable:`CMAKE_GENERATOR_TOOLSET` option. -CMake provides the selected toolchain architecture preference in this -variable (``x86``, ``x64``, or empty).
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_VERSION.rst deleted file mode 100644 index 4d9b978..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_PLATFORM_TOOLSET_VERSION.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CMAKE_VS_PLATFORM_TOOLSET_VERSION ---------------------------------- - -Visual Studio Platform Toolset version. - -The :ref:`Visual Studio Generators` for VS 2017 and above allow to -select minor versions of the same toolset. The toolset version number -may be specified by a field in :variable:`CMAKE_GENERATOR_TOOLSET` of -the form ``version=14.11``. If none is specified CMake will choose a default -toolset. The value may be empty if no minor version was selected and the -default is used.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXCLUDE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXCLUDE_DIRECTORIES.rst deleted file mode 100644 index 36c4dcc..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXCLUDE_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_EXCLUDE_DIRECTORIES --------------------------------- - -This variable allows to override Visual Studio default Exclude Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXECUTABLE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXECUTABLE_DIRECTORIES.rst deleted file mode 100644 index 3ec755b..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_EXECUTABLE_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_EXECUTABLE_DIRECTORIES ------------------------------------ - -This variable allows to override Visual Studio default Executable Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.rst deleted file mode 100644 index da10bde..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_INCLUDE_DIRECTORIES --------------------------------- - -This variable allows to override Visual Studio default Include Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_DIRECTORIES.rst deleted file mode 100644 index b33754a..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_LIBRARY_DIRECTORIES --------------------------------- - -This variable allows to override Visual Studio default Library Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.rst deleted file mode 100644 index b022215..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES --------------------------------------- - -This variable allows to override Visual Studio default Library WinRT -Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.rst deleted file mode 100644 index c03f0ae..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_REFERENCE_DIRECTORIES ----------------------------------- - -This variable allows to override Visual Studio default Reference Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_SOURCE_DIRECTORIES.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_SOURCE_DIRECTORIES.rst deleted file mode 100644 index 0c73f06..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_SDK_SOURCE_DIRECTORIES.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CMAKE_VS_SDK_SOURCE_DIRECTORIES -------------------------------- - -This variable allows to override Visual Studio default Source Directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.rst deleted file mode 100644 index 83b9bc1..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.rst +++ /dev/null
@@ -1,17 +0,0 @@ -CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION ----------------------------------------- - -Visual Studio Windows Target Platform Version. - -When targeting Windows 10 and above Visual Studio 2015 and above support -specification of a target Windows version to select a corresponding SDK. -The :variable:`CMAKE_SYSTEM_VERSION` variable may be set to specify a -version. Otherwise CMake computes a default version based on the Windows -SDK versions available. The chosen Windows target version number is provided -in ``CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION``. If no Windows 10 SDK -is available this value will be empty. - -One may set a ``CMAKE_WINDOWS_KITS_10_DIR`` *environment variable* -to an absolute path to tell CMake to look for Windows 10 SDKs in -a custom location. The specified directory is expected to contain -``Include/10.0.*`` directories.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_VS_WINRT_BY_DEFAULT.rst b/share/cmake-3.18/Help/variable/CMAKE_VS_WINRT_BY_DEFAULT.rst deleted file mode 100644 index 2eea424..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_VS_WINRT_BY_DEFAULT.rst +++ /dev/null
@@ -1,18 +0,0 @@ -CMAKE_VS_WINRT_BY_DEFAULT -------------------------- - -Inform :ref:`Visual Studio Generators` for VS 2010 and above that the -target platform enables WinRT compilation by default and it needs to -be explicitly disabled if ``/ZW`` or :prop_tgt:`VS_WINRT_COMPONENT` is -omitted (as opposed to enabling it when either of those options is -present) - -This makes cmake configuration consistent in terms of WinRT among -platforms - if you did not enable the WinRT compilation explicitly, it -will be disabled (by either not enabling it or explicitly disabling it) - -Note: WinRT compilation is always explicitly disabled for C language -source files, even if it is expliclty enabled for a project - -This variable is meant to be set by a -:variable:`toolchain file <CMAKE_TOOLCHAIN_FILE>` for such platforms.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.rst b/share/cmake-3.18/Help/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.rst deleted file mode 100644 index 1636842..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.rst +++ /dev/null
@@ -1,6 +0,0 @@ -CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS --------------------------------- - -Default value for :prop_tgt:`WINDOWS_EXPORT_ALL_SYMBOLS` target property. -This variable is used to initialize the property on each target as it is -created.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.rst deleted file mode 100644 index be683d6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.rst +++ /dev/null
@@ -1,16 +0,0 @@ -CMAKE_XCODE_ATTRIBUTE_<an-attribute> ------------------------------------- - -Set Xcode target attributes directly. - -Tell the :generator:`Xcode` generator to set '<an-attribute>' to a given value -in the generated Xcode project. Ignored on other generators. - -See the :prop_tgt:`XCODE_ATTRIBUTE_<an-attribute>` target property -to set attributes on a specific target. - -Contents of ``CMAKE_XCODE_ATTRIBUTE_<an-attribute>`` may use -"generator expressions" with the syntax ``$<...>``. See the -:manual:`cmake-generator-expressions(7)` manual for available -expressions. See the :manual:`cmake-buildsystem(7)` manual -for more on defining buildsystem properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_SCHEME.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_SCHEME.rst deleted file mode 100644 index 5b1a003..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_SCHEME.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CMAKE_XCODE_GENERATE_SCHEME ---------------------------- - -If enabled, the :generator:`Xcode` generator will generate schema files. These -are useful to invoke analyze, archive, build-for-testing and test -actions from the command line. - -This variable initializes the -:prop_tgt:`XCODE_GENERATE_SCHEME` -target property on all targets.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.rst deleted file mode 100644 index ea3e240..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY -------------------------------------------- - -If enabled, the :generator:`Xcode` generator will generate only a -single Xcode project file for the topmost :command:`project()` command -instead of generating one for every ``project()`` command. - -This could be useful to speed up the CMake generation step for -large projects and to work-around a bug in the ``ZERO_CHECK`` logic.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.rst deleted file mode 100644 index b972ba5..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER ------------------------------------- - -Whether to enable ``Address Sanitizer`` in the Diagnostics -section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_ADDRESS_SANITIZER` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst deleted file mode 100644 index 59eb32d..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN ------------------------------------------------------ - -Whether to enable ``Detect use of stack after return`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst deleted file mode 100644 index a264d36..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING --------------------------------------------- - -Whether to enable -``Allow debugging when using document Versions Browser`` -in the Options section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst deleted file mode 100644 index 71bcf42..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER ----------------------------------------------- - -Whether to disable the ``Main Thread Checker`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst deleted file mode 100644 index 53f55e6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS ----------------------------------------- - -Whether to enable ``Dynamic Library Loads`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst deleted file mode 100644 index 784ceb6..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE -------------------------------------------- - -Whether to enable ``Dynamic Linker API usage`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst deleted file mode 100644 index 4832659..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst +++ /dev/null
@@ -1,15 +0,0 @@ -CMAKE_XCODE_SCHEME_ENVIRONMENT ------------------------------- - -Specify environment variables that should be added to the Arguments -section of the generated Xcode scheme. - -If set to a list of environment variables and values of the form -``MYVAR=value`` those environment variables will be added to the -scheme. - -This variable initializes the :prop_tgt:`XCODE_SCHEME_ENVIRONMENT` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.rst deleted file mode 100644 index 9350244..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_GUARD_MALLOC -------------------------------- - -Whether to enable ``Guard Malloc`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_GUARD_MALLOC` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst deleted file mode 100644 index 45a2dad..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP -------------------------------------------- - -Whether to enable the ``Main Thread Checker`` option -``Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES.rst deleted file mode 100644 index 94d1c61..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES -------------------------------------- - -Whether to enable ``Malloc Guard Edges`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_MALLOC_GUARD_EDGES` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.rst deleted file mode 100644 index 9bf0eb4..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE ----------------------------------- - -Whether to enable ``Malloc Scribble`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_MALLOC_SCRIBBLE` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.rst deleted file mode 100644 index 4cc21ee..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_MALLOC_STACK -------------------------------- - -Whether to enable ``Malloc Stack`` in the Diagnostics -section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_MALLOC_STACK` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.rst deleted file mode 100644 index 6d1b56e..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_THREAD_SANITIZER ------------------------------------ - -Whether to enable ``Thread Sanitizer`` in the Diagnostics -section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_THREAD_SANITIZER` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP.rst deleted file mode 100644 index de40478..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP ----------------------------------------- - -Whether to enable ``Thread Sanitizer - Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_THREAD_SANITIZER_STOP` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst deleted file mode 100644 index ec5df66..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER ------------------------------------------------- - -Whether to enable ``Undefined Behavior Sanitizer`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst deleted file mode 100644 index dcec9b0..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.rst +++ /dev/null
@@ -1,13 +0,0 @@ -CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP ------------------------------------------------------ - -Whether to enable ``Undefined Behavior Sanitizer`` option -``Pause on issues`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.rst deleted file mode 100644 index 5bb7907..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_WORKING_DIRECTORY ------------------------------------- - -Specify the ``Working Directory`` of the *Run* and *Profile* -actions in the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_WORKING_DIRECTORY` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS.rst b/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS.rst deleted file mode 100644 index 82e9d76..0000000 --- a/share/cmake-3.18/Help/variable/CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS.rst +++ /dev/null
@@ -1,12 +0,0 @@ -CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS ---------------------------------- - -Whether to enable ``Zombie Objects`` -in the Diagnostics section of the generated Xcode scheme. - -This variable initializes the -:prop_tgt:`XCODE_SCHEME_ZOMBIE_OBJECTS` -property on all targets. - -Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property -documentation to see all Xcode schema related properties.
diff --git a/share/cmake-3.18/Help/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst b/share/cmake-3.18/Help/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst deleted file mode 100644 index 83d5ce7..0000000 --- a/share/cmake-3.18/Help/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.rst +++ /dev/null
@@ -1,11 +0,0 @@ -CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS -------------------------------------------- - -Default permissions for implicitly created directories during packaging. - -This variable serves the same purpose during packaging as the -:variable:`CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS` variable -serves during installation (e.g. ``make install``). - -If `include(CPack)` is used then by default this variable is set to the content -of :variable:`CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS`.
diff --git a/share/cmake-3.18/Help/variable/CTEST_BINARY_DIRECTORY.rst b/share/cmake-3.18/Help/variable/CTEST_BINARY_DIRECTORY.rst deleted file mode 100644 index fd8461f..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_BINARY_DIRECTORY.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_BINARY_DIRECTORY ----------------------- - -Specify the CTest ``BuildDirectory`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_BUILD_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_BUILD_COMMAND.rst deleted file mode 100644 index 7b13ba0..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_BUILD_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_BUILD_COMMAND -------------------- - -Specify the CTest ``MakeCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_BUILD_NAME.rst b/share/cmake-3.18/Help/variable/CTEST_BUILD_NAME.rst deleted file mode 100644 index d25d84c..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_BUILD_NAME.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_BUILD_NAME ----------------- - -Specify the CTest ``BuildName`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_BZR_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_BZR_COMMAND.rst deleted file mode 100644 index 474d621..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_BZR_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_BZR_COMMAND ------------------ - -Specify the CTest ``BZRCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_BZR_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_BZR_UPDATE_OPTIONS.rst deleted file mode 100644 index d0f9579..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_BZR_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_BZR_UPDATE_OPTIONS ------------------------- - -Specify the CTest ``BZRUpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CHANGE_ID.rst b/share/cmake-3.18/Help/variable/CTEST_CHANGE_ID.rst deleted file mode 100644 index a423f49..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CHANGE_ID.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CTEST_CHANGE_ID ---------------- - -Specify the CTest ``ChangeId`` setting -in a :manual:`ctest(1)` dashboard client script. - -This setting allows CTest to pass arbitrary information about this -build up to CDash. One use of this feature is to allow CDash to -post comments on your pull request if anything goes wrong with your build.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CHECKOUT_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_CHECKOUT_COMMAND.rst deleted file mode 100644 index da256f2..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CHECKOUT_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_CHECKOUT_COMMAND ----------------------- - -Tell the :command:`ctest_start` command how to checkout or initialize -the source directory in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CONFIGURATION_TYPE.rst b/share/cmake-3.18/Help/variable/CTEST_CONFIGURATION_TYPE.rst deleted file mode 100644 index 9e277fa..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CONFIGURATION_TYPE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CTEST_CONFIGURATION_TYPE ------------------------- - -Specify the CTest ``DefaultCTestConfigurationType`` setting -in a :manual:`ctest(1)` dashboard client script. - -If the configuration type is set via ``-C <cfg>`` from the command line -then this variable is populated accordingly.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CONFIGURE_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_CONFIGURE_COMMAND.rst deleted file mode 100644 index 5561b6d..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CONFIGURE_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_CONFIGURE_COMMAND ------------------------ - -Specify the CTest ``ConfigureCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_COVERAGE_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_COVERAGE_COMMAND.rst deleted file mode 100644 index a78792e..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_COVERAGE_COMMAND.rst +++ /dev/null
@@ -1,60 +0,0 @@ -CTEST_COVERAGE_COMMAND ----------------------- - -Specify the CTest ``CoverageCommand`` setting -in a :manual:`ctest(1)` dashboard client script. - -Cobertura -''''''''' - -Using `Cobertura`_ as the coverage generation within your multi-module -Java project can generate a series of XML files. - -The Cobertura Coverage parser expects to read the coverage data from a -single XML file which contains the coverage data for all modules. -Cobertura has a program with the ability to merge given ``cobertura.ser`` files -and then another program to generate a combined XML file from the previous -merged file. For command line testing, this can be done by hand prior to -CTest looking for the coverage files. For script builds, -set the ``CTEST_COVERAGE_COMMAND`` variable to point to a file which will -perform these same steps, such as a ``.sh`` or ``.bat`` file. - -.. code-block:: cmake - - set(CTEST_COVERAGE_COMMAND .../run-coverage-and-consolidate.sh) - -where the ``run-coverage-and-consolidate.sh`` script is perhaps created by -the :command:`configure_file` command and might contain the following code: - -.. code-block:: bash - - #!/usr/bin/env bash - CoberturaFiles="$(find "/path/to/source" -name "cobertura.ser")" - SourceDirs="$(find "/path/to/source" -name "java" -type d)" - cobertura-merge --datafile coberturamerge.ser $CoberturaFiles - cobertura-report --datafile coberturamerge.ser --destination . \ - --format xml $SourceDirs - -The script uses ``find`` to capture the paths to all of the ``cobertura.ser`` -files found below the project's source directory. It keeps the list of files -and supplies it as an argument to the ``cobertura-merge`` program. The -``--datafile`` argument signifies where the result of the merge will be kept. - -The combined ``coberturamerge.ser`` file is then used to generate the XML report -using the ``cobertura-report`` program. The call to the cobertura-report -program requires some named arguments. - -``--datafila`` - path to the merged ``.ser`` file - -``--destination`` - path to put the output files(s) - -``--format`` - file format to write output in: xml or html - -The rest of the supplied arguments consist of the full paths to the -``/src/main/java`` directories of each module within the source tree. These -directories are needed and should not be forgotten. - -.. _`Cobertura`: http://cobertura.github.io/cobertura/
diff --git a/share/cmake-3.18/Help/variable/CTEST_COVERAGE_EXTRA_FLAGS.rst b/share/cmake-3.18/Help/variable/CTEST_COVERAGE_EXTRA_FLAGS.rst deleted file mode 100644 index 2981955..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_COVERAGE_EXTRA_FLAGS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_COVERAGE_EXTRA_FLAGS --------------------------- - -Specify the CTest ``CoverageExtraFlags`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CURL_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_CURL_OPTIONS.rst deleted file mode 100644 index fc5dfc4..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CURL_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_CURL_OPTIONS ------------------- - -Specify the CTest ``CurlOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst b/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst deleted file mode 100644 index 5aeae88..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE --------------------------------------------- - -When saving a failing test's output, this is the maximum size, in bytes, that -will be collected by the :command:`ctest_test` command. Defaults to 307200 -(300 KiB). - -.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.rst b/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.rst deleted file mode 100644 index 1fbb8c5..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE --------------------------------------------- - -When saving a passing test's output, this is the maximum size, in bytes, that -will be collected by the :command:`ctest_test` command. Defaults to 1024 -(1 KiB). - -.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/share/cmake-3.18/Help/variable/CTEST_CVS_CHECKOUT.rst b/share/cmake-3.18/Help/variable/CTEST_CVS_CHECKOUT.rst deleted file mode 100644 index 6431c02..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CVS_CHECKOUT.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CTEST_CVS_CHECKOUT ------------------- - -Deprecated. Use :variable:`CTEST_CHECKOUT_COMMAND` instead.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CVS_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_CVS_COMMAND.rst deleted file mode 100644 index 049700b..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CVS_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_CVS_COMMAND ------------------ - -Specify the CTest ``CVSCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_CVS_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_CVS_UPDATE_OPTIONS.rst deleted file mode 100644 index d7f2f7c..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_CVS_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_CVS_UPDATE_OPTIONS ------------------------- - -Specify the CTest ``CVSUpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_LOCATION.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_LOCATION.rst deleted file mode 100644 index c0f2215..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_LOCATION.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_LOCATION -------------------- - -Specify the CTest ``DropLocation`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_METHOD.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_METHOD.rst deleted file mode 100644 index 50fbd4d..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_METHOD.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_METHOD ------------------ - -Specify the CTest ``DropMethod`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_SITE.rst deleted file mode 100644 index d15d99b..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_SITE ---------------- - -Specify the CTest ``DropSite`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_CDASH.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_CDASH.rst deleted file mode 100644 index 22b9776..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_CDASH.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_SITE_CDASH ---------------------- - -Specify the CTest ``IsCDash`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_PASSWORD.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_PASSWORD.rst deleted file mode 100644 index 904d2c8..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_PASSWORD.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_SITE_PASSWORD ------------------------- - -Specify the CTest ``DropSitePassword`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_USER.rst b/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_USER.rst deleted file mode 100644 index a860a03..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_DROP_SITE_USER.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_DROP_SITE_USER --------------------- - -Specify the CTest ``DropSiteUser`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_EXTRA_COVERAGE_GLOB.rst b/share/cmake-3.18/Help/variable/CTEST_EXTRA_COVERAGE_GLOB.rst deleted file mode 100644 index 286f7df..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_EXTRA_COVERAGE_GLOB.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CTEST_EXTRA_COVERAGE_GLOB -------------------------- - -A list of regular expressions which will be used to find files which should be -covered by the :command:`ctest_coverage` command. - -.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/share/cmake-3.18/Help/variable/CTEST_GIT_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_GIT_COMMAND.rst deleted file mode 100644 index eb83792..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_GIT_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_GIT_COMMAND ------------------ - -Specify the CTest ``GITCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_GIT_INIT_SUBMODULES.rst b/share/cmake-3.18/Help/variable/CTEST_GIT_INIT_SUBMODULES.rst deleted file mode 100644 index fd27003..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_GIT_INIT_SUBMODULES.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_GIT_INIT_SUBMODULES -------------------------- - -Specify the CTest ``GITInitSubmodules`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_CUSTOM.rst b/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_CUSTOM.rst deleted file mode 100644 index 0c479e6..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_CUSTOM.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_GIT_UPDATE_CUSTOM ------------------------ - -Specify the CTest ``GITUpdateCustom`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_OPTIONS.rst deleted file mode 100644 index 4590a78..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_GIT_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_GIT_UPDATE_OPTIONS ------------------------- - -Specify the CTest ``GITUpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_HG_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_HG_COMMAND.rst deleted file mode 100644 index 3854950..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_HG_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_HG_COMMAND ----------------- - -Specify the CTest ``HGCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_HG_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_HG_UPDATE_OPTIONS.rst deleted file mode 100644 index 9049c1f..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_HG_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_HG_UPDATE_OPTIONS ------------------------ - -Specify the CTest ``HGUpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_LABELS_FOR_SUBPROJECTS.rst b/share/cmake-3.18/Help/variable/CTEST_LABELS_FOR_SUBPROJECTS.rst deleted file mode 100644 index 959596b..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_LABELS_FOR_SUBPROJECTS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_LABELS_FOR_SUBPROJECTS ----------------------------- - -Specify the CTest ``LabelsForSubprojects`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND.rst deleted file mode 100644 index 8c199ba..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_MEMORYCHECK_COMMAND -------------------------- - -Specify the CTest ``MemoryCheckCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.rst deleted file mode 100644 index 3e26ab5..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_MEMORYCHECK_COMMAND_OPTIONS ---------------------------------- - -Specify the CTest ``MemoryCheckCommandOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst deleted file mode 100644 index 2de5fb6..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_MEMORYCHECK_SANITIZER_OPTIONS ------------------------------------ - -Specify the CTest ``MemoryCheckSanitizerOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.rst b/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.rst deleted file mode 100644 index 1147ee8..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_MEMORYCHECK_SUPPRESSIONS_FILE ------------------------------------ - -Specify the CTest ``MemoryCheckSuppressionFile`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_TYPE.rst b/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_TYPE.rst deleted file mode 100644 index 4e7d5c0..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_MEMORYCHECK_TYPE.rst +++ /dev/null
@@ -1,8 +0,0 @@ -CTEST_MEMORYCHECK_TYPE ----------------------- - -Specify the CTest ``MemoryCheckType`` setting -in a :manual:`ctest(1)` dashboard client script. -Valid values are ``Valgrind``, ``Purify``, ``BoundsChecker``, ``DrMemory`` and -``ThreadSanitizer``, ``AddressSanitizer``, ``LeakSanitizer``, ``MemorySanitizer``, and -``UndefinedBehaviorSanitizer``.
diff --git a/share/cmake-3.18/Help/variable/CTEST_NIGHTLY_START_TIME.rst b/share/cmake-3.18/Help/variable/CTEST_NIGHTLY_START_TIME.rst deleted file mode 100644 index 90841f9..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_NIGHTLY_START_TIME.rst +++ /dev/null
@@ -1,9 +0,0 @@ -CTEST_NIGHTLY_START_TIME ------------------------- - -Specify the CTest ``NightlyStartTime`` setting in a :manual:`ctest(1)` -dashboard client script. - -Note that this variable must always be set for a nightly build in a -dashboard script. It is needed so that nightly builds can be properly grouped -together in CDash.
diff --git a/share/cmake-3.18/Help/variable/CTEST_P4_CLIENT.rst b/share/cmake-3.18/Help/variable/CTEST_P4_CLIENT.rst deleted file mode 100644 index 347ea54..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_P4_CLIENT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_P4_CLIENT ---------------- - -Specify the CTest ``P4Client`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_P4_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_P4_COMMAND.rst deleted file mode 100644 index defab12..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_P4_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_P4_COMMAND ----------------- - -Specify the CTest ``P4Command`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_P4_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_P4_OPTIONS.rst deleted file mode 100644 index fee4ce2..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_P4_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_P4_OPTIONS ----------------- - -Specify the CTest ``P4Options`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_P4_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_P4_UPDATE_OPTIONS.rst deleted file mode 100644 index 0e2790f..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_P4_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_P4_UPDATE_OPTIONS ------------------------ - -Specify the CTest ``P4UpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_RESOURCE_SPEC_FILE.rst b/share/cmake-3.18/Help/variable/CTEST_RESOURCE_SPEC_FILE.rst deleted file mode 100644 index a6fdbc9..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_RESOURCE_SPEC_FILE.rst +++ /dev/null
@@ -1,10 +0,0 @@ -CTEST_RESOURCE_SPEC_FILE ------------------------- - -Specify the CTest ``ResourceSpecFile`` setting in a :manual:`ctest(1)` -dashboard client script. - -This can also be used to specify the resource spec file from a CMake build. If -no ``RESOURCE_SPEC_FILE`` is passed to :command:`ctest_test`, and -``CTEST_RESOURCE_SPEC_FILE`` is not specified in the dashboard script, the -value of this variable from the build is used.
diff --git a/share/cmake-3.18/Help/variable/CTEST_RUN_CURRENT_SCRIPT.rst b/share/cmake-3.18/Help/variable/CTEST_RUN_CURRENT_SCRIPT.rst deleted file mode 100644 index abc123c..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_RUN_CURRENT_SCRIPT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_RUN_CURRENT_SCRIPT ------------------------- - -Setting this to 0 prevents :manual:`ctest(1)` from being run again when it -reaches the end of a script run by calling ``ctest -S``.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SCP_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_SCP_COMMAND.rst deleted file mode 100644 index 19ea8b3..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SCP_COMMAND.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CTEST_SCP_COMMAND ------------------ - -Legacy option. Not used.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SITE.rst b/share/cmake-3.18/Help/variable/CTEST_SITE.rst deleted file mode 100644 index 8a5ec25..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SITE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SITE ----------- - -Specify the CTest ``Site`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SOURCE_DIRECTORY.rst b/share/cmake-3.18/Help/variable/CTEST_SOURCE_DIRECTORY.rst deleted file mode 100644 index b6837d1..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SOURCE_DIRECTORY.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SOURCE_DIRECTORY ----------------------- - -Specify the CTest ``SourceDirectory`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SUBMIT_URL.rst b/share/cmake-3.18/Help/variable/CTEST_SUBMIT_URL.rst deleted file mode 100644 index 7d84da4..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SUBMIT_URL.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SUBMIT_URL ----------------- - -Specify the CTest ``SubmitURL`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SVN_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_SVN_COMMAND.rst deleted file mode 100644 index af90143..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SVN_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SVN_COMMAND ------------------ - -Specify the CTest ``SVNCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SVN_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_SVN_OPTIONS.rst deleted file mode 100644 index 76551dc..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SVN_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SVN_OPTIONS ------------------ - -Specify the CTest ``SVNOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_SVN_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_SVN_UPDATE_OPTIONS.rst deleted file mode 100644 index 5f01a19..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_SVN_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_SVN_UPDATE_OPTIONS ------------------------- - -Specify the CTest ``SVNUpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_TEST_LOAD.rst b/share/cmake-3.18/Help/variable/CTEST_TEST_LOAD.rst deleted file mode 100644 index 80823fe..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_TEST_LOAD.rst +++ /dev/null
@@ -1,7 +0,0 @@ -CTEST_TEST_LOAD ---------------- - -Specify the ``TestLoad`` setting in the :ref:`CTest Test Step` -of a :manual:`ctest(1)` dashboard client script. This sets the -default value for the ``TEST_LOAD`` option of the :command:`ctest_test` -command.
diff --git a/share/cmake-3.18/Help/variable/CTEST_TEST_TIMEOUT.rst b/share/cmake-3.18/Help/variable/CTEST_TEST_TIMEOUT.rst deleted file mode 100644 index c031437..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_TEST_TIMEOUT.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_TEST_TIMEOUT ------------------- - -Specify the CTest ``TimeOut`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_TRIGGER_SITE.rst b/share/cmake-3.18/Help/variable/CTEST_TRIGGER_SITE.rst deleted file mode 100644 index a50e405..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_TRIGGER_SITE.rst +++ /dev/null
@@ -1,4 +0,0 @@ -CTEST_TRIGGER_SITE ------------------- - -Legacy option. Not used.
diff --git a/share/cmake-3.18/Help/variable/CTEST_UPDATE_COMMAND.rst b/share/cmake-3.18/Help/variable/CTEST_UPDATE_COMMAND.rst deleted file mode 100644 index 90155d0..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_UPDATE_COMMAND.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_UPDATE_COMMAND --------------------- - -Specify the CTest ``UpdateCommand`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_UPDATE_OPTIONS.rst b/share/cmake-3.18/Help/variable/CTEST_UPDATE_OPTIONS.rst deleted file mode 100644 index e43d61d..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_UPDATE_OPTIONS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_UPDATE_OPTIONS --------------------- - -Specify the CTest ``UpdateOptions`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_ONLY.rst b/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_ONLY.rst deleted file mode 100644 index a862baa..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_ONLY.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_UPDATE_VERSION_ONLY -------------------------- - -Specify the CTest :ref:`UpdateVersionOnly <UpdateVersionOnly>` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_OVERRIDE.rst b/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_OVERRIDE.rst deleted file mode 100644 index 39fbaba..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_UPDATE_VERSION_OVERRIDE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_UPDATE_VERSION_OVERRIDE ------------------------------ - -Specify the CTest :ref:`UpdateVersionOverride <UpdateVersionOverride>` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/CTEST_USE_LAUNCHERS.rst b/share/cmake-3.18/Help/variable/CTEST_USE_LAUNCHERS.rst deleted file mode 100644 index 9f48a2e..0000000 --- a/share/cmake-3.18/Help/variable/CTEST_USE_LAUNCHERS.rst +++ /dev/null
@@ -1,5 +0,0 @@ -CTEST_USE_LAUNCHERS -------------------- - -Specify the CTest ``UseLaunchers`` setting -in a :manual:`ctest(1)` dashboard client script.
diff --git a/share/cmake-3.18/Help/variable/EXECUTABLE_OUTPUT_PATH.rst b/share/cmake-3.18/Help/variable/EXECUTABLE_OUTPUT_PATH.rst deleted file mode 100644 index 26d3e92..0000000 --- a/share/cmake-3.18/Help/variable/EXECUTABLE_OUTPUT_PATH.rst +++ /dev/null
@@ -1,8 +0,0 @@ -EXECUTABLE_OUTPUT_PATH ----------------------- - -Old executable location variable. - -The target property :prop_tgt:`RUNTIME_OUTPUT_DIRECTORY` supercedes this -variable for a target if it is set. Executable targets are otherwise placed in -this directory.
diff --git a/share/cmake-3.18/Help/variable/GHS-MULTI.rst b/share/cmake-3.18/Help/variable/GHS-MULTI.rst deleted file mode 100644 index fe3b17e..0000000 --- a/share/cmake-3.18/Help/variable/GHS-MULTI.rst +++ /dev/null
@@ -1,4 +0,0 @@ -GHS-MULTI ---------- - -``True`` when using :generator:`Green Hills MULTI` generator.
diff --git a/share/cmake-3.18/Help/variable/IOS.rst b/share/cmake-3.18/Help/variable/IOS.rst deleted file mode 100644 index e5cc3f6..0000000 --- a/share/cmake-3.18/Help/variable/IOS.rst +++ /dev/null
@@ -1,4 +0,0 @@ -IOS ---- - -Set to ``1`` when the target system (:variable:`CMAKE_SYSTEM_NAME`) is ``iOS``.
diff --git a/share/cmake-3.18/Help/variable/MINGW.rst b/share/cmake-3.18/Help/variable/MINGW.rst deleted file mode 100644 index 6d29be4..0000000 --- a/share/cmake-3.18/Help/variable/MINGW.rst +++ /dev/null
@@ -1,6 +0,0 @@ -MINGW ------ - -``True`` when using MinGW - -Set to ``true`` when the compiler is some version of MinGW.
diff --git a/share/cmake-3.18/Help/variable/MSVC.rst b/share/cmake-3.18/Help/variable/MSVC.rst deleted file mode 100644 index ca8775c..0000000 --- a/share/cmake-3.18/Help/variable/MSVC.rst +++ /dev/null
@@ -1,8 +0,0 @@ -MSVC ----- - -Set to ``true`` when the compiler is some version of Microsoft Visual -C++ or another compiler simulating Visual C++. Any compiler defining -``_MSC_VER`` is considered simulating Visual C++. - -See also the :variable:`MSVC_VERSION` variable.
diff --git a/share/cmake-3.18/Help/variable/MSVC14.rst b/share/cmake-3.18/Help/variable/MSVC14.rst deleted file mode 100644 index 79e0c10..0000000 --- a/share/cmake-3.18/Help/variable/MSVC14.rst +++ /dev/null
@@ -1,7 +0,0 @@ -MSVC14 ------- - -Discouraged. Use the :variable:`MSVC_VERSION` variable instead. - -``True`` when using the Microsoft Visual Studio ``v140`` or ``v141`` -toolset (``cl`` version 19) or another compiler that simulates it.
diff --git a/share/cmake-3.18/Help/variable/MSVC_IDE.rst b/share/cmake-3.18/Help/variable/MSVC_IDE.rst deleted file mode 100644 index 027d1bc..0000000 --- a/share/cmake-3.18/Help/variable/MSVC_IDE.rst +++ /dev/null
@@ -1,7 +0,0 @@ -MSVC_IDE --------- - -``True`` when using the Microsoft Visual C++ IDE. - -Set to ``true`` when the target platform is the Microsoft Visual C++ IDE, as -opposed to the command line compiler.
diff --git a/share/cmake-3.18/Help/variable/MSVC_TOOLSET_VERSION.rst b/share/cmake-3.18/Help/variable/MSVC_TOOLSET_VERSION.rst deleted file mode 100644 index f4a33e2..0000000 --- a/share/cmake-3.18/Help/variable/MSVC_TOOLSET_VERSION.rst +++ /dev/null
@@ -1,22 +0,0 @@ -MSVC_TOOLSET_VERSION --------------------- - -The toolset version of Microsoft Visual C/C++ being used if any. -If MSVC-like is being used, this variable is set based on the version -of the compiler as given by the :variable:`MSVC_VERSION` variable. - -Known toolset version numbers are:: - - 80 = VS 2005 (8.0) - 90 = VS 2008 (9.0) - 100 = VS 2010 (10.0) - 110 = VS 2012 (11.0) - 120 = VS 2013 (12.0) - 140 = VS 2015 (14.0) - 141 = VS 2017 (15.0) - 142 = VS 2019 (16.0) - -Compiler versions newer than those known to CMake will be reported -as the latest known toolset version. - -See also the :variable:`MSVC_VERSION` variable.
diff --git a/share/cmake-3.18/Help/variable/MSVC_VERSION.rst b/share/cmake-3.18/Help/variable/MSVC_VERSION.rst deleted file mode 100644 index 45df37f..0000000 --- a/share/cmake-3.18/Help/variable/MSVC_VERSION.rst +++ /dev/null
@@ -1,24 +0,0 @@ -MSVC_VERSION ------------- - -The version of Microsoft Visual C/C++ being used if any. -If a compiler simulating Visual C++ is being used, this variable is set -to the toolset version simulated as given by the ``_MSC_VER`` -preprocessor definition. - -Known version numbers are:: - - 1200 = VS 6.0 - 1300 = VS 7.0 - 1310 = VS 7.1 - 1400 = VS 8.0 (v80 toolset) - 1500 = VS 9.0 (v90 toolset) - 1600 = VS 10.0 (v100 toolset) - 1700 = VS 11.0 (v110 toolset) - 1800 = VS 12.0 (v120 toolset) - 1900 = VS 14.0 (v140 toolset) - 1910-1919 = VS 15.0 (v141 toolset) - 1920-1929 = VS 16.0 (v142 toolset) - -See also the :variable:`CMAKE_<LANG>_COMPILER_VERSION` and -:variable:`MSVC_TOOLSET_VERSION` variable.
diff --git a/share/cmake-3.18/Help/variable/MSYS.rst b/share/cmake-3.18/Help/variable/MSYS.rst deleted file mode 100644 index 25ddc7f..0000000 --- a/share/cmake-3.18/Help/variable/MSYS.rst +++ /dev/null
@@ -1,4 +0,0 @@ -MSYS ----- - -``True`` when using the :generator:`MSYS Makefiles` generator.
diff --git a/share/cmake-3.18/Help/variable/PROJECT-NAME_DESCRIPTION.rst b/share/cmake-3.18/Help/variable/PROJECT-NAME_DESCRIPTION.rst deleted file mode 100644 index 2b88b1a..0000000 --- a/share/cmake-3.18/Help/variable/PROJECT-NAME_DESCRIPTION.rst +++ /dev/null
@@ -1,5 +0,0 @@ -<PROJECT-NAME>_DESCRIPTION --------------------------- - -Value given to the ``DESCRIPTION`` option of the most recent call to the -:command:`project` command with project name ``<PROJECT-NAME>``, if any.
diff --git a/share/cmake-3.18/Help/variable/PROJECT-NAME_HOMEPAGE_URL.rst b/share/cmake-3.18/Help/variable/PROJECT-NAME_HOMEPAGE_URL.rst deleted file mode 100644 index 22cc304..0000000 --- a/share/cmake-3.18/Help/variable/PROJECT-NAME_HOMEPAGE_URL.rst +++ /dev/null
@@ -1,5 +0,0 @@ -<PROJECT-NAME>_HOMEPAGE_URL ---------------------------- - -Value given to the ``HOMEPAGE_URL`` option of the most recent call to the -:command:`project` command with project name ``<PROJECT-NAME>``, if any.
diff --git a/share/cmake-3.18/Help/variable/PROJECT_DESCRIPTION.rst b/share/cmake-3.18/Help/variable/PROJECT_DESCRIPTION.rst deleted file mode 100644 index 2833e11..0000000 --- a/share/cmake-3.18/Help/variable/PROJECT_DESCRIPTION.rst +++ /dev/null
@@ -1,9 +0,0 @@ -PROJECT_DESCRIPTION -------------------- - -Short project description given to the project command. - -This is the description given to the most recently called :command:`project` -command in the current directory scope or above. To obtain the description -of the top level project, see the :variable:`CMAKE_PROJECT_DESCRIPTION` -variable.
diff --git a/share/cmake-3.18/Help/variable/PROJECT_HOMEPAGE_URL.rst b/share/cmake-3.18/Help/variable/PROJECT_HOMEPAGE_URL.rst deleted file mode 100644 index 754c9e8..0000000 --- a/share/cmake-3.18/Help/variable/PROJECT_HOMEPAGE_URL.rst +++ /dev/null
@@ -1,9 +0,0 @@ -PROJECT_HOMEPAGE_URL --------------------- - -The homepage URL of the project. - -This is the homepage URL given to the most recently called :command:`project` -command in the current directory scope or above. To obtain the homepage URL -of the top level project, see the :variable:`CMAKE_PROJECT_HOMEPAGE_URL` -variable.
diff --git a/share/cmake-3.18/Help/variable/PackageName_ROOT.rst b/share/cmake-3.18/Help/variable/PackageName_ROOT.rst deleted file mode 100644 index 1c2fd34..0000000 --- a/share/cmake-3.18/Help/variable/PackageName_ROOT.rst +++ /dev/null
@@ -1,14 +0,0 @@ -<PackageName>_ROOT ------------------- - -Calls to :command:`find_package(<PackageName>)` will search in prefixes -specified by the ``<PackageName>_ROOT`` CMake variable, where -``<PackageName>`` is the name given to the :command:`find_package` call -and ``_ROOT`` is literal. For example, ``find_package(Foo)`` will search -prefixes specified in the ``Foo_ROOT`` CMake variable (if set). -See policy :policy:`CMP0074`. - -This variable may hold a single prefix or a -:ref:`semicolon-separated list <CMake Language Lists>` of multiple prefixes. - -See also the :envvar:`<PackageName>_ROOT` environment variable.
diff --git a/share/cmake-3.18/Help/variable/WINCE.rst b/share/cmake-3.18/Help/variable/WINCE.rst deleted file mode 100644 index 54ff7de..0000000 --- a/share/cmake-3.18/Help/variable/WINCE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -WINCE ------ - -True when the :variable:`CMAKE_SYSTEM_NAME` variable is set -to ``WindowsCE``.
diff --git a/share/cmake-3.18/Help/variable/WINDOWS_PHONE.rst b/share/cmake-3.18/Help/variable/WINDOWS_PHONE.rst deleted file mode 100644 index 61d91b0..0000000 --- a/share/cmake-3.18/Help/variable/WINDOWS_PHONE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -WINDOWS_PHONE -------------- - -True when the :variable:`CMAKE_SYSTEM_NAME` variable is set -to ``WindowsPhone``.
diff --git a/share/cmake-3.18/Help/variable/WINDOWS_STORE.rst b/share/cmake-3.18/Help/variable/WINDOWS_STORE.rst deleted file mode 100644 index dae3b53..0000000 --- a/share/cmake-3.18/Help/variable/WINDOWS_STORE.rst +++ /dev/null
@@ -1,5 +0,0 @@ -WINDOWS_STORE -------------- - -True when the :variable:`CMAKE_SYSTEM_NAME` variable is set -to ``WindowsStore``.
diff --git a/share/cmake-3.18/Help/variable/XCODE.rst b/share/cmake-3.18/Help/variable/XCODE.rst deleted file mode 100644 index 99f20fb..0000000 --- a/share/cmake-3.18/Help/variable/XCODE.rst +++ /dev/null
@@ -1,4 +0,0 @@ -XCODE ------ - -``True`` when using :generator:`Xcode` generator.
diff --git a/share/cmake-3.18/Modules/AddFileDependencies.cmake b/share/cmake-3.18/Modules/AddFileDependencies.cmake deleted file mode 100644 index 598a52f..0000000 --- a/share/cmake-3.18/Modules/AddFileDependencies.cmake +++ /dev/null
@@ -1,28 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -AddFileDependencies -------------------- - -Add dependencies to a source file. - -.. code-block:: cmake - - ADD_FILE_DEPENDENCIES(<source> <files>) - -Adds the given ``<files>`` to the dependencies of file ``<source>``. -#]=======================================================================] - -macro(ADD_FILE_DEPENDENCIES _file) - - get_source_file_property(_deps ${_file} OBJECT_DEPENDS) - if (_deps) - set(_deps ${_deps} ${ARGN}) - else () - set(_deps ${ARGN}) - endif () - - set_source_files_properties(${_file} PROPERTIES OBJECT_DEPENDS "${_deps}") - -endmacro()
diff --git a/share/cmake-3.18/Modules/AndroidTestUtilities.cmake b/share/cmake-3.18/Modules/AndroidTestUtilities.cmake deleted file mode 100644 index 95e2ef7..0000000 --- a/share/cmake-3.18/Modules/AndroidTestUtilities.cmake +++ /dev/null
@@ -1,162 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[======================================================================[.rst: -AndroidTestUtilities ------------------------- - -Create a test that automatically loads specified data onto an Android device. - -Introduction -^^^^^^^^^^^^ - -Use this module to push data needed for testing an Android device behavior -onto a connected Android device. The module will accept files and libraries as -well as separate destinations for each. It will create a test that loads the -files into a device object store and link to them from the specified -destination. The files are only uploaded if they are not already in the object -store. - -For example: - -.. code-block:: cmake - - include(AndroidTestUtilities) - android_add_test_data( - example_setup_test - FILES <files>... - LIBS <libs>... - DEVICE_TEST_DIR "/data/local/tests/example" - DEVICE_OBJECT_STORE "/sdcard/.ExternalData/SHA" - ) - - -At build time a test named "example_setup_test" will be created. Run this test -on the command line with :manual:`ctest(1)` to load the data onto the Android -device. - -Module Functions -^^^^^^^^^^^^^^^^ - -.. command:: android_add_test_data - - .. code-block:: cmake - - android_add_test_data(<test-name> - [FILES <files>...] [FILES_DEST <device-dir>] - [LIBS <libs>...] [LIBS_DEST <device-dir>] - [DEVICE_OBJECT_STORE <device-dir>] - [DEVICE_TEST_DIR <device-dir>] - [NO_LINK_REGEX <strings>...] - ) - - The ``android_add_test_data`` function is used to copy files and libraries - needed to run project-specific tests. On the host operating system, this is - done at build time. For on-device testing, the files are loaded onto the - device by the manufactured test at run time. - - This function accepts the following named parameters: - - ``FILES <files>...`` - zero or more files needed for testing - ``LIBS <libs>...`` - zero or more libraries needed for testing - ``FILES_DEST <device-dir>`` - absolute path where the data files are expected to be - ``LIBS_DEST <device-dir>`` - absolute path where the libraries are expected to be - ``DEVICE_OBJECT_STORE <device-dir>`` - absolute path to the location where the data is stored on-device - ``DEVICE_TEST_DIR <device-dir>`` - absolute path to the root directory of the on-device test location - ``NO_LINK_REGEX <strings>...`` - list of regex strings matching the names of files that should be - copied from the object store to the testing directory -#]======================================================================] - -include(${CMAKE_CURRENT_LIST_DIR}/ExternalData.cmake) - -# The parameters to this function should be set to the list of directories, -# files, and libraries that need to be installed prior to testing. -function(android_add_test_data test_name) - # As the names suggest, oneValueArgs lists the arguments that specify a - # single value, while multiValueArgs can contain one or more values. - set(keywordArgs) - set(oneValueArgs FILES_DEST LIBS_DEST DEVICE_OBJECT_STORE DEVICE_TEST_DIR) - set(multiValueArgs FILES LIBS NO_LINK_REGEX) - - # For example, if you called this function with FILES </path/to/file> - # then this path would be stored in the variable AST_FILES. - # The AST prefix stands for the name of this function (android_add_test_data). - cmake_parse_arguments(AST "${keywordArgs}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN}) - if(NOT AST_DEVICE_TEST_DIR) - message(FATAL_ERROR "-- You must specify the location of the on device test directory.") - endif() - if(NOT AST_DEVICE_OBJECT_STORE) - message(FATAL_ERROR "-- You must specify the location of the on device object store.") - endif() - if(${AST_DEVICE_TEST_DIR} STREQUAL "/") - message(FATAL_ERROR "-- The device test directory cannot be '/'") - endif() - - # Copy all test data files into the binary directory, where tests are run. - # ExternalData will handle fetching DATA{...} references. - string(REPLACE "|" ";" hash_algs "${_ExternalData_REGEX_EXT}") - # Convert ExternalData placeholder file names to DATA{} syntax. - foreach(alg ${hash_algs}) - string(REGEX REPLACE "([^ ;]+)\\.${alg}" "DATA{\\1}" AST_FILES "${AST_FILES}") - endforeach() - - set(DATA_TARGET_NAME "${test_name}") - string(FIND "${AST_FILES}" "DATA{" data_files_found) - if(${data_files_found} GREATER "-1") - # Use ExternalData if any DATA{} files were found. - ExternalData_Expand_Arguments( - ${DATA_TARGET_NAME} - extern_data_output - ${AST_FILES}) - ExternalData_Add_Target(${DATA_TARGET_NAME}) - else() - add_custom_target(${DATA_TARGET_NAME} ALL) - set(extern_data_output ${AST_FILES}) - endif() - - # For regular files on Linux, just copy them directly. - foreach(path ${AST_FILES}) - foreach(output ${extern_data_output}) - if(${output} STREQUAL ${path}) - # Check if a destination was specified. If not, we copy by default - # into this project's binary directory, preserving its relative path. - if(AST_${VAR}_DEST) - set(DEST ${CMAKE_BINARY_DIR}/${parent_dir}/${AST_${VAR}_DEST}) - else() - get_filename_component(parent_dir ${path} DIRECTORY) - set(DEST "${CMAKE_BINARY_DIR}/${parent_dir}") - endif() - get_filename_component(extern_data_source ${output} REALPATH) - get_filename_component(extern_data_basename ${output} NAME) - add_custom_command( - TARGET ${DATA_TARGET_NAME} POST_BUILD - DEPENDS ${extern_data_source} - COMMAND ${CMAKE_COMMAND} -E copy_if_different ${extern_data_source} ${DEST}/${extern_data_basename} - ) - endif() - endforeach() - endforeach() - - if(ANDROID) - string(REGEX REPLACE "DATA{([^ ;]+)}" "\\1" processed_FILES "${AST_FILES}") - add_test( - NAME ${test_name} - COMMAND ${CMAKE_COMMAND} - "-Darg_files_dest=${AST_FILES_DEST}" - "-Darg_libs_dest=${AST_LIBS_DEST}" - "-Darg_dev_test_dir=${AST_DEVICE_TEST_DIR}" - "-Darg_dev_obj_store=${AST_DEVICE_OBJECT_STORE}" - "-Darg_no_link_regex=${AST_NO_LINK_REGEX}" - "-Darg_files=${processed_FILES}" - "-Darg_libs=${AST_LIBS}" - "-Darg_src_dir=${CMAKE_CURRENT_SOURCE_DIR}" - -P ${CMAKE_CURRENT_FUNCTION_LIST_DIR}/AndroidTestUtilities/PushToAndroidDevice.cmake) - endif() -endfunction()
diff --git a/share/cmake-3.18/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in b/share/cmake-3.18/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in deleted file mode 100644 index a6e5fda..0000000 --- a/share/cmake-3.18/Modules/BasicConfigVersion-AnyNewerVersion.cmake.in +++ /dev/null
@@ -1,37 +0,0 @@ -# This is a basic version file for the Config-mode of find_package(). -# It is used by write_basic_package_version_file() as input file for configure_file() -# to create a version-file which can be installed along a config.cmake file. -# -# The created file sets PACKAGE_VERSION_EXACT if the current version string and -# the requested version string are exactly the same and it sets -# PACKAGE_VERSION_COMPATIBLE if the current version is >= requested version. -# The variable CVF_VERSION must be set before calling configure_file(). - -set(PACKAGE_VERSION "@CVF_VERSION@") - -if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION) - set(PACKAGE_VERSION_COMPATIBLE FALSE) -else() - set(PACKAGE_VERSION_COMPATIBLE TRUE) - if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION) - set(PACKAGE_VERSION_EXACT TRUE) - endif() -endif() - - -# if the installed project requested no architecture check, don't perform the check -if("@CVF_ARCH_INDEPENDENT@") - return() -endif() - -# if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, ignore it: -if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "") - return() -endif() - -# check that the installed version has the same 32/64bit-ness as the one which is currently searching: -if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@") - math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8") - set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") - set(PACKAGE_VERSION_UNSUITABLE TRUE) -endif()
diff --git a/share/cmake-3.18/Modules/BasicConfigVersion-ExactVersion.cmake.in b/share/cmake-3.18/Modules/BasicConfigVersion-ExactVersion.cmake.in deleted file mode 100644 index 43fc4d0..0000000 --- a/share/cmake-3.18/Modules/BasicConfigVersion-ExactVersion.cmake.in +++ /dev/null
@@ -1,52 +0,0 @@ -# This is a basic version file for the Config-mode of find_package(). -# It is used by write_basic_package_version_file() as input file for configure_file() -# to create a version-file which can be installed along a config.cmake file. -# -# The created file sets PACKAGE_VERSION_EXACT if the current version string and -# the requested version string are exactly the same and it sets -# PACKAGE_VERSION_COMPATIBLE if the current version is equal to the requested version. -# The tweak version component is ignored. -# The variable CVF_VERSION must be set before calling configure_file(). - - -set(PACKAGE_VERSION "@CVF_VERSION@") - -if("@CVF_VERSION@" MATCHES "^([0-9]+\\.[0-9]+\\.[0-9]+)\\.") # strip the tweak version - set(CVF_VERSION_NO_TWEAK "${CMAKE_MATCH_1}") -else() - set(CVF_VERSION_NO_TWEAK "@CVF_VERSION@") -endif() - -if(PACKAGE_FIND_VERSION MATCHES "^([0-9]+\\.[0-9]+\\.[0-9]+)\\.") # strip the tweak version - set(REQUESTED_VERSION_NO_TWEAK "${CMAKE_MATCH_1}") -else() - set(REQUESTED_VERSION_NO_TWEAK "${PACKAGE_FIND_VERSION}") -endif() - -if(REQUESTED_VERSION_NO_TWEAK STREQUAL CVF_VERSION_NO_TWEAK) - set(PACKAGE_VERSION_COMPATIBLE TRUE) -else() - set(PACKAGE_VERSION_COMPATIBLE FALSE) -endif() - -if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION) - set(PACKAGE_VERSION_EXACT TRUE) -endif() - - -# if the installed project requested no architecture check, don't perform the check -if("@CVF_ARCH_INDEPENDENT@") - return() -endif() - -# if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, ignore it: -if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "") - return() -endif() - -# check that the installed version has the same 32/64bit-ness as the one which is currently searching: -if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@") - math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8") - set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") - set(PACKAGE_VERSION_UNSUITABLE TRUE) -endif()
diff --git a/share/cmake-3.18/Modules/BasicConfigVersion-SameMajorVersion.cmake.in b/share/cmake-3.18/Modules/BasicConfigVersion-SameMajorVersion.cmake.in deleted file mode 100644 index 8c3b6a2..0000000 --- a/share/cmake-3.18/Modules/BasicConfigVersion-SameMajorVersion.cmake.in +++ /dev/null
@@ -1,51 +0,0 @@ -# This is a basic version file for the Config-mode of find_package(). -# It is used by write_basic_package_version_file() as input file for configure_file() -# to create a version-file which can be installed along a config.cmake file. -# -# The created file sets PACKAGE_VERSION_EXACT if the current version string and -# the requested version string are exactly the same and it sets -# PACKAGE_VERSION_COMPATIBLE if the current version is >= requested version, -# but only if the requested major version is the same as the current one. -# The variable CVF_VERSION must be set before calling configure_file(). - - -set(PACKAGE_VERSION "@CVF_VERSION@") - -if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION) - set(PACKAGE_VERSION_COMPATIBLE FALSE) -else() - - if("@CVF_VERSION@" MATCHES "^([0-9]+)\\.") - set(CVF_VERSION_MAJOR "${CMAKE_MATCH_1}") - else() - set(CVF_VERSION_MAJOR "@CVF_VERSION@") - endif() - - if(PACKAGE_FIND_VERSION_MAJOR STREQUAL CVF_VERSION_MAJOR) - set(PACKAGE_VERSION_COMPATIBLE TRUE) - else() - set(PACKAGE_VERSION_COMPATIBLE FALSE) - endif() - - if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION) - set(PACKAGE_VERSION_EXACT TRUE) - endif() -endif() - - -# if the installed project requested no architecture check, don't perform the check -if("@CVF_ARCH_INDEPENDENT@") - return() -endif() - -# if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, ignore it: -if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "") - return() -endif() - -# check that the installed version has the same 32/64bit-ness as the one which is currently searching: -if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@") - math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8") - set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") - set(PACKAGE_VERSION_UNSUITABLE TRUE) -endif()
diff --git a/share/cmake-3.18/Modules/BasicConfigVersion-SameMinorVersion.cmake.in b/share/cmake-3.18/Modules/BasicConfigVersion-SameMinorVersion.cmake.in deleted file mode 100644 index e2030d2..0000000 --- a/share/cmake-3.18/Modules/BasicConfigVersion-SameMinorVersion.cmake.in +++ /dev/null
@@ -1,55 +0,0 @@ -# This is a basic version file for the Config-mode of find_package(). -# It is used by write_basic_package_version_file() as input file for configure_file() -# to create a version-file which can be installed along a config.cmake file. -# -# The created file sets PACKAGE_VERSION_EXACT if the current version string and -# the requested version string are exactly the same and it sets -# PACKAGE_VERSION_COMPATIBLE if the current version is >= requested version, -# but only if the requested major and minor versions are the same as the current -# one. -# The variable CVF_VERSION must be set before calling configure_file(). - - -set(PACKAGE_VERSION "@CVF_VERSION@") - -if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION) - set(PACKAGE_VERSION_COMPATIBLE FALSE) -else() - - if("@CVF_VERSION@" MATCHES "^([0-9]+)\\.([0-9]+)") - set(CVF_VERSION_MAJOR "${CMAKE_MATCH_1}") - set(CVF_VERSION_MINOR "${CMAKE_MATCH_2}") - else() - set(CVF_VERSION_MAJOR "@CVF_VERSION@") - set(CVF_VERSION_MINOR "") - endif() - - if((PACKAGE_FIND_VERSION_MAJOR STREQUAL CVF_VERSION_MAJOR) AND - (PACKAGE_FIND_VERSION_MINOR STREQUAL CVF_VERSION_MINOR)) - set(PACKAGE_VERSION_COMPATIBLE TRUE) - else() - set(PACKAGE_VERSION_COMPATIBLE FALSE) - endif() - - if(PACKAGE_FIND_VERSION STREQUAL PACKAGE_VERSION) - set(PACKAGE_VERSION_EXACT TRUE) - endif() -endif() - - -# if the installed project requested no architecture check, don't perform the check -if("@CVF_ARCH_INDEPENDENT@") - return() -endif() - -# if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, ignore it: -if("${CMAKE_SIZEOF_VOID_P}" STREQUAL "" OR "@CMAKE_SIZEOF_VOID_P@" STREQUAL "") - return() -endif() - -# check that the installed version has the same 32/64bit-ness as the one which is currently searching: -if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "@CMAKE_SIZEOF_VOID_P@") - math(EXPR installedBits "@CMAKE_SIZEOF_VOID_P@ * 8") - set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") - set(PACKAGE_VERSION_UNSUITABLE TRUE) -endif()
diff --git a/share/cmake-3.18/Modules/BundleUtilities.cmake b/share/cmake-3.18/Modules/BundleUtilities.cmake deleted file mode 100644 index 2f3b9e1..0000000 --- a/share/cmake-3.18/Modules/BundleUtilities.cmake +++ /dev/null
@@ -1,1123 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -BundleUtilities ---------------- - -Functions to help assemble a standalone bundle application. - -A collection of CMake utility functions useful for dealing with ``.app`` -bundles on the Mac and bundle-like directories on any OS. - -The following functions are provided by this module: - -.. code-block:: cmake - - fixup_bundle - copy_and_fixup_bundle - verify_app - get_bundle_main_executable - get_dotapp_dir - get_bundle_and_executable - get_bundle_all_executables - get_item_key - get_item_rpaths - clear_bundle_keys - set_bundle_key_values - get_bundle_keys - copy_resolved_item_into_bundle - copy_resolved_framework_into_bundle - fixup_bundle_item - verify_bundle_prerequisites - verify_bundle_symlinks - -Requires CMake 2.6 or greater because it uses function, break and -``PARENT_SCOPE``. Also depends on ``GetPrerequisites.cmake``. - -DO NOT USE THESE FUNCTIONS AT CONFIGURE TIME (from ``CMakeLists.txt``)! -Instead, invoke them from an :command:`install(CODE)` or -:command:`install(SCRIPT)` rule. - -.. code-block:: cmake - - fixup_bundle(<app> <libs> <dirs>) - -Fix up ``<app>`` bundle in-place and make it standalone, such that it can be -drag-n-drop copied to another machine and run on that machine as long -as all of the system libraries are compatible. - -If you pass plugins to ``fixup_bundle`` as the libs parameter, you should -install them or copy them into the bundle before calling ``fixup_bundle``. -The ``<libs>`` parameter is a list of libraries that must be fixed up, but -that cannot be determined by ``otool`` output analysis (i.e. ``plugins``). - -Gather all the keys for all the executables and libraries in a bundle, -and then, for each key, copy each prerequisite into the bundle. Then -fix each one up according to its own list of prerequisites. - -Then clear all the keys and call ``verify_app`` on the final bundle to -ensure that it is truly standalone. - -As an optional parameter (``IGNORE_ITEM``) a list of file names can be passed, -which are then ignored -(e.g. ``IGNORE_ITEM "vcredist_x86.exe;vcredist_x64.exe"``). - -.. code-block:: cmake - - copy_and_fixup_bundle(<src> <dst> <libs> <dirs>) - -Makes a copy of the bundle ``<src>`` at location ``<dst>`` and then fixes up -the new copied bundle in-place at ``<dst>``. - -.. code-block:: cmake - - verify_app(<app>) - -Verifies that an application ``<app>`` appears valid based on running -analysis tools on it. Calls :command:`message(FATAL_ERROR)` if the application -is not verified. - -As an optional parameter (``IGNORE_ITEM``) a list of file names can be passed, -which are then ignored -(e.g. ``IGNORE_ITEM "vcredist_x86.exe;vcredist_x64.exe"``) - -.. code-block:: cmake - - get_bundle_main_executable(<bundle> <result_var>) - -The result will be the full path name of the bundle's main executable -file or an ``error:`` prefixed string if it could not be determined. - -.. code-block:: cmake - - get_dotapp_dir(<exe> <dotapp_dir_var>) - -Returns the nearest parent dir whose name ends with ``.app`` given the -full path to an executable. If there is no such parent dir, then -simply return the dir containing the executable. - -The returned directory may or may not exist. - -.. code-block:: cmake - - get_bundle_and_executable(<app> <bundle_var> <executable_var> <valid_var>) - -Takes either a ``.app`` directory name or the name of an executable -nested inside a ``.app`` directory and returns the path to the ``.app`` -directory in ``<bundle_var>`` and the path to its main executable in -``<executable_var>``. - -.. code-block:: cmake - - get_bundle_all_executables(<bundle> <exes_var>) - -Scans ``<bundle>`` bundle recursively for all ``<exes_var>`` executable -files and accumulates them into a variable. - -.. code-block:: cmake - - get_item_key(<item> <key_var>) - -Given ``<item>`` file name, generate ``<key_var>`` key that should be unique -considering the set of libraries that need copying or fixing up to -make a bundle standalone. This is essentially the file name including -extension with ``.`` replaced by ``_`` - -This key is used as a prefix for CMake variables so that we can -associate a set of variables with a given item based on its key. - -.. code-block:: cmake - - clear_bundle_keys(<keys_var>) - -Loop over the ``<keys_var>`` list of keys, clearing all the variables -associated with each key. After the loop, clear the list of keys itself. - -Caller of ``get_bundle_keys`` should call ``clear_bundle_keys`` when done with -list of keys. - -.. code-block:: cmake - - set_bundle_key_values(<keys_var> <context> <item> <exepath> <dirs> - <copyflag> [<rpaths>]) - -Add ``<keys_var>`` key to the list (if necessary) for the given item. -If added, also set all the variables associated with that key. - -.. code-block:: cmake - - get_bundle_keys(<app> <libs> <dirs> <keys_var>) - -Loop over all the executable and library files within ``<app>`` bundle (and -given as extra ``<libs>``) and accumulate a list of keys representing -them. Set values associated with each key such that we can loop over -all of them and copy prerequisite libs into the bundle and then do -appropriate ``install_name_tool`` fixups. - -As an optional parameter (``IGNORE_ITEM``) a list of file names can be passed, -which are then ignored -(e.g. ``IGNORE_ITEM "vcredist_x86.exe;vcredist_x64.exe"``) - -.. code-block:: cmake - - copy_resolved_item_into_bundle(<resolved_item> <resolved_embedded_item>) - -Copy a resolved item into the bundle if necessary. -Copy is not necessary, if the ``<resolved_item>`` is "the same as" the -``<resolved_embedded_item>``. - -.. code-block:: cmake - - copy_resolved_framework_into_bundle(<resolved_item> <resolved_embedded_item>) - -Copy a resolved framework into the bundle if necessary. -Copy is not necessary, if the ``<resolved_item>`` is "the same as" the -``<resolved_embedded_item>``. - -By default, ``BU_COPY_FULL_FRAMEWORK_CONTENTS`` is not set. If you want -full frameworks embedded in your bundles, set -``BU_COPY_FULL_FRAMEWORK_CONTENTS`` to ``ON`` before calling fixup_bundle. By -default, ``COPY_RESOLVED_FRAMEWORK_INTO_BUNDLE`` copies the framework -dylib itself plus the framework ``Resources`` directory. - -.. code-block:: cmake - - fixup_bundle_item(<resolved_embedded_item> <exepath> <dirs>) - -Get the direct/non-system prerequisites of the ``<resolved_embedded_item>``. -For each prerequisite, change the way it is referenced to the value of -the ``_EMBEDDED_ITEM`` keyed variable for that prerequisite. (Most likely -changing to an ``@executable_path`` style reference.) - -This function requires that the ``<resolved_embedded_item>`` be ``inside`` -the bundle already. In other words, if you pass plugins to ``fixup_bundle`` -as the libs parameter, you should install them or copy them into the -bundle before calling ``fixup_bundle``. The ``libs`` parameter is a list of -libraries that must be fixed up, but that cannot be determined by -otool output analysis. (i.e., ``plugins``) - -Also, change the id of the item being fixed up to its own -``_EMBEDDED_ITEM`` value. - -Accumulate changes in a local variable and make *one* call to -``install_name_tool`` at the end of the function with all the changes at -once. - -If the ``BU_CHMOD_BUNDLE_ITEMS`` variable is set then bundle items will be -marked writable before ``install_name_tool`` tries to change them. - -.. code-block:: cmake - - verify_bundle_prerequisites(<bundle> <result_var> <info_var>) - -Verifies that the sum of all prerequisites of all files inside the -bundle are contained within the bundle or are ``system`` libraries, -presumed to exist everywhere. - -As an optional parameter (``IGNORE_ITEM``) a list of file names can be passed, -which are then ignored -(e.g. ``IGNORE_ITEM "vcredist_x86.exe;vcredist_x64.exe"``) - -.. code-block:: cmake - - verify_bundle_symlinks(<bundle> <result_var> <info_var>) - -Verifies that any symlinks found in the ``<bundle>`` bundle point to other files -that are already also in the bundle... Anything that points to an -external file causes this function to fail the verification. -#]=======================================================================] - -function(_warn_cmp0080) - cmake_policy(GET_WARNING CMP0080 _cmp0080_warning) - message(AUTHOR_WARNING "${_cmp0080_warning}\n") -endfunction() - -# Do not include this module at configure time! -if(DEFINED CMAKE_GENERATOR) - cmake_policy(GET CMP0080 _BundleUtilities_CMP0080) - if(_BundleUtilities_CMP0080 STREQUAL "NEW") - message(FATAL_ERROR "BundleUtilities cannot be included at configure time!") - elseif(NOT _BundleUtilities_CMP0080 STREQUAL "OLD" AND NOT _CMP0080_SUPPRESS_WARNING) - _warn_cmp0080() - endif() -endif() - -cmake_policy(PUSH) -cmake_policy(SET CMP0057 NEW) # if IN_LIST - -# The functions defined in this file depend on the get_prerequisites function -# (and possibly others) found in: -# -include("${CMAKE_CURRENT_LIST_DIR}/GetPrerequisites.cmake") - - -function(get_bundle_main_executable bundle result_var) - set(result "error: '${bundle}/Contents/Info.plist' file does not exist") - - if(EXISTS "${bundle}/Contents/Info.plist") - set(result "error: no CFBundleExecutable in '${bundle}/Contents/Info.plist' file") - set(line_is_main_executable 0) - set(bundle_executable "") - - # Read Info.plist as a list of lines: - # - set(eol_char "E") - file(READ "${bundle}/Contents/Info.plist" info_plist) - string(REPLACE ";" "\\;" info_plist "${info_plist}") - string(REPLACE "\n" "${eol_char};" info_plist "${info_plist}") - string(REPLACE "\r" "${eol_char};" info_plist "${info_plist}") - - # Scan the lines for "<key>CFBundleExecutable</key>" - the line after that - # is the name of the main executable. - # - foreach(line ${info_plist}) - if(line_is_main_executable) - string(REGEX REPLACE "^.*<string>(.*)</string>.*$" "\\1" bundle_executable "${line}") - break() - endif() - - if(line MATCHES "<key>CFBundleExecutable</key>") - set(line_is_main_executable 1) - endif() - endforeach() - - if(NOT bundle_executable STREQUAL "") - if(EXISTS "${bundle}/Contents/MacOS/${bundle_executable}") - set(result "${bundle}/Contents/MacOS/${bundle_executable}") - else() - - # Ultimate goal: - # If not in "Contents/MacOS" then scan the bundle for matching files. If - # there is only one executable file that matches, then use it, otherwise - # it's an error... - # - #file(GLOB_RECURSE file_list "${bundle}/${bundle_executable}") - - # But for now, pragmatically, it's an error. Expect the main executable - # for the bundle to be in Contents/MacOS, it's an error if it's not: - # - set(result "error: '${bundle}/Contents/MacOS/${bundle_executable}' does not exist") - endif() - endif() - else() - # - # More inclusive technique... (This one would work on Windows and Linux - # too, if a developer followed the typical Mac bundle naming convention...) - # - # If there is no Info.plist file, try to find an executable with the same - # base name as the .app directory: - # - endif() - - set(${result_var} "${result}" PARENT_SCOPE) -endfunction() - - -function(get_dotapp_dir exe dotapp_dir_var) - set(s "${exe}") - - if(s MATCHES "/.*\\.app/") - # If there is a ".app" parent directory, - # ascend until we hit it: - # (typical of a Mac bundle executable) - # - set(done 0) - while(NOT ${done}) - get_filename_component(snamewe "${s}" NAME_WE) - get_filename_component(sname "${s}" NAME) - get_filename_component(sdir "${s}" PATH) - set(s "${sdir}") - if(sname MATCHES "\\.app$") - set(done 1) - set(dotapp_dir "${sdir}/${sname}") - endif() - endwhile() - else() - # Otherwise use a directory containing the exe - # (typical of a non-bundle executable on Mac, Windows or Linux) - # - is_file_executable("${s}" is_executable) - if(is_executable) - get_filename_component(sdir "${s}" PATH) - set(dotapp_dir "${sdir}") - else() - set(dotapp_dir "${s}") - endif() - endif() - - - set(${dotapp_dir_var} "${dotapp_dir}" PARENT_SCOPE) -endfunction() - - -function(get_bundle_and_executable app bundle_var executable_var valid_var) - set(valid 0) - - if(EXISTS "${app}") - # Is it a directory ending in .app? - if(IS_DIRECTORY "${app}") - if(app MATCHES "\\.app$") - get_bundle_main_executable("${app}" executable) - if(EXISTS "${app}" AND EXISTS "${executable}") - set(${bundle_var} "${app}" PARENT_SCOPE) - set(${executable_var} "${executable}" PARENT_SCOPE) - set(valid 1) - #message(STATUS "info: handled .app directory case...") - else() - message(STATUS "warning: *NOT* handled - .app directory case...") - endif() - else() - message(STATUS "warning: *NOT* handled - directory but not .app case...") - endif() - else() - # Is it an executable file? - is_file_executable("${app}" is_executable) - if(is_executable) - get_dotapp_dir("${app}" dotapp_dir) - if(EXISTS "${dotapp_dir}") - set(${bundle_var} "${dotapp_dir}" PARENT_SCOPE) - set(${executable_var} "${app}" PARENT_SCOPE) - set(valid 1) - #message(STATUS "info: handled executable file in .app dir case...") - else() - get_filename_component(app_dir "${app}" PATH) - set(${bundle_var} "${app_dir}" PARENT_SCOPE) - set(${executable_var} "${app}" PARENT_SCOPE) - set(valid 1) - #message(STATUS "info: handled executable file in any dir case...") - endif() - else() - message(STATUS "warning: *NOT* handled - not .app dir, not executable file...") - endif() - endif() - else() - message(STATUS "warning: *NOT* handled - directory/file does not exist...") - endif() - - if(NOT valid) - set(${bundle_var} "error: not a bundle" PARENT_SCOPE) - set(${executable_var} "error: not a bundle" PARENT_SCOPE) - endif() - - set(${valid_var} ${valid} PARENT_SCOPE) -endfunction() - - -function(get_bundle_all_executables bundle exes_var) - set(exes "") - - if(UNIX) - find_program(find_cmd "find") - mark_as_advanced(find_cmd) - endif() - - # find command is much quicker than checking every file one by one on Unix - # which can take long time for large bundles, and since anyway we expect - # executable to have execute flag set we can narrow the list much quicker. - if(find_cmd) - execute_process(COMMAND "${find_cmd}" "${bundle}" - -type f \( -perm -0100 -o -perm -0010 -o -perm -0001 \) - OUTPUT_VARIABLE file_list - OUTPUT_STRIP_TRAILING_WHITESPACE - ) - string(REPLACE "\n" ";" file_list "${file_list}") - else() - file(GLOB_RECURSE file_list "${bundle}/*") - endif() - - foreach(f ${file_list}) - is_file_executable("${f}" is_executable) - if(is_executable) - set(exes ${exes} "${f}") - endif() - endforeach() - - set(${exes_var} "${exes}" PARENT_SCOPE) -endfunction() - - -function(get_item_rpaths item rpaths_var) - if(APPLE) - find_program(otool_cmd "otool") - mark_as_advanced(otool_cmd) - endif() - - if(otool_cmd) - execute_process( - COMMAND "${otool_cmd}" -l "${item}" - OUTPUT_VARIABLE load_cmds_ov - RESULT_VARIABLE otool_rv - ERROR_VARIABLE otool_ev - ) - if(NOT otool_rv STREQUAL "0") - message(FATAL_ERROR "otool -l failed: ${otool_rv}\n${otool_ev}") - endif() - string(REGEX REPLACE "[^\n]+cmd LC_RPATH\n[^\n]+\n[^\n]+path ([^\n]+) \\(offset[^\n]+\n" "rpath \\1\n" load_cmds_ov "${load_cmds_ov}") - string(REGEX MATCHALL "rpath [^\n]+" load_cmds_ov "${load_cmds_ov}") - string(REGEX REPLACE "rpath " "" load_cmds_ov "${load_cmds_ov}") - if(load_cmds_ov) - foreach(rpath ${load_cmds_ov}) - gp_append_unique(${rpaths_var} "${rpath}") - endforeach() - endif() - endif() - - if(UNIX AND NOT APPLE) - file(READ_ELF ${item} RPATH rpath_var RUNPATH runpath_var CAPTURE_ERROR error_var) - get_filename_component(item_dir ${item} DIRECTORY) - foreach(rpath ${rpath_var} ${runpath_var}) - # Substitute $ORIGIN with the exepath and add to the found rpaths - string(REPLACE "$ORIGIN" "${item_dir}" rpath "${rpath}") - gp_append_unique(${rpaths_var} "${rpath}") - endforeach() - endif() - - set(${rpaths_var} ${${rpaths_var}} PARENT_SCOPE) -endfunction() - - -function(get_item_key item key_var) - get_filename_component(item_name "${item}" NAME) - if(WIN32) - string(TOLOWER "${item_name}" item_name) - endif() - string(REPLACE "." "_" ${key_var} "${item_name}") - set(${key_var} ${${key_var}} PARENT_SCOPE) -endfunction() - - -function(clear_bundle_keys keys_var) - foreach(key ${${keys_var}}) - set(${key}_ITEM PARENT_SCOPE) - set(${key}_RESOLVED_ITEM PARENT_SCOPE) - set(${key}_DEFAULT_EMBEDDED_PATH PARENT_SCOPE) - set(${key}_EMBEDDED_ITEM PARENT_SCOPE) - set(${key}_RESOLVED_EMBEDDED_ITEM PARENT_SCOPE) - set(${key}_COPYFLAG PARENT_SCOPE) - set(${key}_RPATHS PARENT_SCOPE) - endforeach() - set(${keys_var} PARENT_SCOPE) -endfunction() - - -function(set_bundle_key_values keys_var context item exepath dirs copyflag) - if(ARGC GREATER 6) - set(rpaths "${ARGV6}") - else() - set(rpaths "") - endif() - get_filename_component(item_name "${item}" NAME) - - get_item_key("${item}" key) - - list(LENGTH ${keys_var} length_before) - gp_append_unique(${keys_var} "${key}") - list(LENGTH ${keys_var} length_after) - - if(NOT length_before EQUAL length_after) - gp_resolve_item("${context}" "${item}" "${exepath}" "${dirs}" resolved_item "${rpaths}") - - gp_item_default_embedded_path("${item}" default_embedded_path) - - get_item_rpaths("${resolved_item}" item_rpaths) - - if((NOT item MATCHES "\\.dylib$") AND (item MATCHES "[^/]+\\.framework/")) - # For frameworks, construct the name under the embedded path from the - # opening "${item_name}.framework/" to the closing "/${item_name}": - # - string(REGEX REPLACE "^.*(${item_name}.framework/.*/?${item_name}).*$" "${default_embedded_path}/\\1" embedded_item "${item}") - else() - # For other items, just use the same name as the original, but in the - # embedded path: - # - set(embedded_item "${default_embedded_path}/${item_name}") - endif() - - # Replace @executable_path and resolve ".." references: - # - string(REPLACE "@executable_path" "${exepath}" resolved_embedded_item "${embedded_item}") - get_filename_component(resolved_embedded_item "${resolved_embedded_item}" ABSOLUTE) - - # *But* -- if we are not copying, then force resolved_embedded_item to be - # the same as resolved_item. In the case of multiple executables in the - # original bundle, using the default_embedded_path results in looking for - # the resolved executable next to the main bundle executable. This is here - # so that exes in the other sibling directories (like "bin") get fixed up - # properly... - # - if(NOT copyflag) - set(resolved_embedded_item "${resolved_item}") - endif() - - set(${keys_var} ${${keys_var}} PARENT_SCOPE) - set(${key}_ITEM "${item}" PARENT_SCOPE) - set(${key}_RESOLVED_ITEM "${resolved_item}" PARENT_SCOPE) - set(${key}_DEFAULT_EMBEDDED_PATH "${default_embedded_path}" PARENT_SCOPE) - set(${key}_EMBEDDED_ITEM "${embedded_item}" PARENT_SCOPE) - set(${key}_RESOLVED_EMBEDDED_ITEM "${resolved_embedded_item}" PARENT_SCOPE) - set(${key}_COPYFLAG "${copyflag}" PARENT_SCOPE) - set(${key}_RPATHS "${item_rpaths}" PARENT_SCOPE) - set(${key}_RDEP_RPATHS "${rpaths}" PARENT_SCOPE) - else() - #message("warning: item key '${key}' already in the list, subsequent references assumed identical to first") - endif() -endfunction() - - -function(get_bundle_keys app libs dirs keys_var) - set(${keys_var} PARENT_SCOPE) - - set(options) - set(oneValueArgs) - set(multiValueArgs IGNORE_ITEM) - cmake_parse_arguments(CFG "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN} ) - - get_bundle_and_executable("${app}" bundle executable valid) - if(valid) - # Always use the exepath of the main bundle executable for @executable_path - # replacements: - # - get_filename_component(exepath "${executable}" PATH) - - # But do fixups on all executables in the bundle: - # - get_bundle_all_executables("${bundle}" exes) - - # Set keys for main executable first: - # - set_bundle_key_values(${keys_var} "${executable}" "${executable}" "${exepath}" "${dirs}" 0) - - # Get rpaths specified by main executable: - # - get_item_key("${executable}" executable_key) - set(main_rpaths "${${executable_key}_RPATHS}") - - # For each extra lib, accumulate a key as well and then also accumulate - # any of its prerequisites. (Extra libs are typically dynamically loaded - # plugins: libraries that are prerequisites for full runtime functionality - # but that do not show up in otool -L output...) - # - foreach(lib ${libs}) - set_bundle_key_values(${keys_var} "${lib}" "${lib}" "${exepath}" "${dirs}" 0 "${main_rpaths}") - - set(prereqs "") - get_filename_component(prereq_filename ${lib} NAME) - - if(NOT prereq_filename IN_LIST CFG_IGNORE_ITEM) - get_prerequisites("${lib}" prereqs 1 1 "${exepath}" "${dirs}" "${main_rpaths}") - foreach(pr ${prereqs}) - set_bundle_key_values(${keys_var} "${lib}" "${pr}" "${exepath}" "${dirs}" 1 "${main_rpaths}") - endforeach() - else() - message(STATUS "Ignoring file: ${prereq_filename}") - endif() - endforeach() - - # For each executable found in the bundle, accumulate keys as we go. - # The list of keys should be complete when all prerequisites of all - # binaries in the bundle have been analyzed. - # - foreach(exe ${exes}) - # Main executable is scanned first above: - # - if(NOT exe STREQUAL executable) - # Add the exe itself to the keys: - # - set_bundle_key_values(${keys_var} "${exe}" "${exe}" "${exepath}" "${dirs}" 0 "${main_rpaths}") - - # Get rpaths specified by executable: - # - get_item_key("${exe}" exe_key) - set(exe_rpaths "${main_rpaths}" "${${exe_key}_RPATHS}") - else() - set(exe_rpaths "${main_rpaths}") - endif() - - # Add each prerequisite to the keys: - # - set(prereqs "") - get_filename_component(prereq_filename ${exe} NAME) - - if(NOT prereq_filename IN_LIST CFG_IGNORE_ITEM) - get_prerequisites("${exe}" prereqs 1 1 "${exepath}" "${dirs}" "${exe_rpaths}") - foreach(pr ${prereqs}) - set_bundle_key_values(${keys_var} "${exe}" "${pr}" "${exepath}" "${dirs}" 1 "${exe_rpaths}") - endforeach() - else() - message(STATUS "Ignoring file: ${prereq_filename}") - endif() - endforeach() - - # preserve library symlink structure - foreach(key ${${keys_var}}) - if("${${key}_COPYFLAG}" STREQUAL "1") - if(IS_SYMLINK "${${key}_RESOLVED_ITEM}") - get_filename_component(target "${${key}_RESOLVED_ITEM}" REALPATH) - set_bundle_key_values(${keys_var} "${exe}" "${target}" "${exepath}" "${dirs}" 1 "${exe_rpaths}") - get_item_key("${target}" targetkey) - - if(WIN32) - # ignore case on Windows - string(TOLOWER "${${key}_RESOLVED_ITEM}" resolved_item_compare) - string(TOLOWER "${${targetkey}_RESOLVED_EMBEDDED_ITEM}" resolved_embedded_item_compare) - else() - set(resolved_item_compare "${${key}_RESOLVED_ITEM}") - set(resolved_embedded_item_compare "${${targetkey}_RESOLVED_EMBEDDED_ITEM}") - endif() - get_filename_component(resolved_item_compare "${resolved_item_compare}" NAME) - get_filename_component(resolved_embedded_item_compare "${resolved_embedded_item_compare}" NAME) - - if(NOT resolved_item_compare STREQUAL resolved_embedded_item_compare) - set(${key}_COPYFLAG "2") - set(${key}_RESOLVED_ITEM "${${targetkey}_RESOLVED_EMBEDDED_ITEM}") - endif() - - endif() - endif() - endforeach() - # Propagate values to caller's scope: - # - set(${keys_var} ${${keys_var}} PARENT_SCOPE) - foreach(key ${${keys_var}}) - set(${key}_ITEM "${${key}_ITEM}" PARENT_SCOPE) - set(${key}_RESOLVED_ITEM "${${key}_RESOLVED_ITEM}" PARENT_SCOPE) - set(${key}_DEFAULT_EMBEDDED_PATH "${${key}_DEFAULT_EMBEDDED_PATH}" PARENT_SCOPE) - set(${key}_EMBEDDED_ITEM "${${key}_EMBEDDED_ITEM}" PARENT_SCOPE) - set(${key}_RESOLVED_EMBEDDED_ITEM "${${key}_RESOLVED_EMBEDDED_ITEM}" PARENT_SCOPE) - set(${key}_COPYFLAG "${${key}_COPYFLAG}" PARENT_SCOPE) - set(${key}_RPATHS "${${key}_RPATHS}" PARENT_SCOPE) - set(${key}_RDEP_RPATHS "${${key}_RDEP_RPATHS}" PARENT_SCOPE) - endforeach() - endif() -endfunction() - -function(link_resolved_item_into_bundle resolved_item resolved_embedded_item) - if(WIN32) - # ignore case on Windows - string(TOLOWER "${resolved_item}" resolved_item_compare) - string(TOLOWER "${resolved_embedded_item}" resolved_embedded_item_compare) - else() - set(resolved_item_compare "${resolved_item}") - set(resolved_embedded_item_compare "${resolved_embedded_item}") - endif() - - if(resolved_item_compare STREQUAL resolved_embedded_item_compare) - message(STATUS "warning: resolved_item == resolved_embedded_item - not linking...") - else() - get_filename_component(target_dir "${resolved_embedded_item}" DIRECTORY) - file(RELATIVE_PATH symlink_target "${target_dir}" "${resolved_item}") - if (NOT EXISTS "${target_dir}") - file(MAKE_DIRECTORY "${target_dir}") - endif() - execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "${symlink_target}" "${resolved_embedded_item}") - endif() -endfunction() - -function(copy_resolved_item_into_bundle resolved_item resolved_embedded_item) - if(WIN32) - # ignore case on Windows - string(TOLOWER "${resolved_item}" resolved_item_compare) - string(TOLOWER "${resolved_embedded_item}" resolved_embedded_item_compare) - else() - set(resolved_item_compare "${resolved_item}") - set(resolved_embedded_item_compare "${resolved_embedded_item}") - endif() - - if(resolved_item_compare STREQUAL resolved_embedded_item_compare) - message(STATUS "warning: resolved_item == resolved_embedded_item - not copying...") - else() - #message(STATUS "copying COMMAND ${CMAKE_COMMAND} -E copy ${resolved_item} ${resolved_embedded_item}") - execute_process(COMMAND ${CMAKE_COMMAND} -E copy "${resolved_item}" "${resolved_embedded_item}") - if(UNIX AND NOT APPLE) - file(RPATH_REMOVE FILE "${resolved_embedded_item}") - endif() - endif() - -endfunction() - - -function(copy_resolved_framework_into_bundle resolved_item resolved_embedded_item) - if(WIN32) - # ignore case on Windows - string(TOLOWER "${resolved_item}" resolved_item_compare) - string(TOLOWER "${resolved_embedded_item}" resolved_embedded_item_compare) - else() - set(resolved_item_compare "${resolved_item}") - set(resolved_embedded_item_compare "${resolved_embedded_item}") - endif() - - if(resolved_item_compare STREQUAL resolved_embedded_item_compare) - message(STATUS "warning: resolved_item == resolved_embedded_item - not copying...") - else() - if(BU_COPY_FULL_FRAMEWORK_CONTENTS) - # Full Framework (everything): - get_filename_component(resolved_dir "${resolved_item}" PATH) - get_filename_component(resolved_dir "${resolved_dir}/../.." ABSOLUTE) - get_filename_component(resolved_embedded_dir "${resolved_embedded_item}" PATH) - get_filename_component(resolved_embedded_dir "${resolved_embedded_dir}/../.." ABSOLUTE) - #message(STATUS "copying COMMAND ${CMAKE_COMMAND} -E copy_directory '${resolved_dir}' '${resolved_embedded_dir}'") - execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory "${resolved_dir}" "${resolved_embedded_dir}") - else() - # Framework lib itself: - #message(STATUS "copying COMMAND ${CMAKE_COMMAND} -E copy ${resolved_item} ${resolved_embedded_item}") - execute_process(COMMAND ${CMAKE_COMMAND} -E copy "${resolved_item}" "${resolved_embedded_item}") - - # Plus Resources, if they exist: - string(REGEX REPLACE "^(.*)/[^/]+$" "\\1/Resources" resolved_resources "${resolved_item}") - string(REGEX REPLACE "^(.*)/[^/]+$" "\\1/Resources" resolved_embedded_resources "${resolved_embedded_item}") - if(EXISTS "${resolved_resources}") - #message(STATUS "copying COMMAND ${CMAKE_COMMAND} -E copy_directory '${resolved_resources}' '${resolved_embedded_resources}'") - execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory "${resolved_resources}" "${resolved_embedded_resources}") - endif() - - # Some frameworks e.g. Qt put Info.plist in wrong place, so when it is - # missing in resources, copy it from other well known incorrect locations: - if(NOT EXISTS "${resolved_resources}/Info.plist") - # Check for Contents/Info.plist in framework root (older Qt SDK): - string(REGEX REPLACE "^(.*)/[^/]+/[^/]+/[^/]+$" "\\1/Contents/Info.plist" resolved_info_plist "${resolved_item}") - string(REGEX REPLACE "^(.*)/[^/]+$" "\\1/Resources/Info.plist" resolved_embedded_info_plist "${resolved_embedded_item}") - if(EXISTS "${resolved_info_plist}") - #message(STATUS "copying COMMAND ${CMAKE_COMMAND} -E copy_directory '${resolved_info_plist}' '${resolved_embedded_info_plist}'") - execute_process(COMMAND ${CMAKE_COMMAND} -E copy "${resolved_info_plist}" "${resolved_embedded_info_plist}") - endif() - endif() - - # Check if framework is versioned and fix it layout - string(REGEX REPLACE "^.*/([^/]+)/[^/]+$" "\\1" resolved_embedded_version "${resolved_embedded_item}") - string(REGEX REPLACE "^(.*)/[^/]+/[^/]+$" "\\1" resolved_embedded_versions "${resolved_embedded_item}") - string(REGEX REPLACE "^.*/([^/]+)/[^/]+/[^/]+$" "\\1" resolved_embedded_versions_basename "${resolved_embedded_item}") - if(resolved_embedded_versions_basename STREQUAL "Versions") - # Ensure Current symlink points to the framework version - if(NOT EXISTS "${resolved_embedded_versions}/Current") - execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "${resolved_embedded_version}" "${resolved_embedded_versions}/Current") - endif() - # Restore symlinks in framework root pointing to current framework - # binary and resources: - string(REGEX REPLACE "^(.*)/[^/]+/[^/]+/[^/]+$" "\\1" resolved_embedded_root "${resolved_embedded_item}") - string(REGEX REPLACE "^.*/([^/]+)$" "\\1" resolved_embedded_item_basename "${resolved_embedded_item}") - if(NOT EXISTS "${resolved_embedded_root}/${resolved_embedded_item_basename}") - execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "Versions/Current/${resolved_embedded_item_basename}" "${resolved_embedded_root}/${resolved_embedded_item_basename}") - endif() - if(NOT EXISTS "${resolved_embedded_root}/Resources") - execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "Versions/Current/Resources" "${resolved_embedded_root}/Resources") - endif() - endif() - endif() - if(UNIX AND NOT APPLE) - file(RPATH_REMOVE FILE "${resolved_embedded_item}") - endif() - endif() - -endfunction() - - -function(fixup_bundle_item resolved_embedded_item exepath dirs) - # This item's key is "ikey": - # - get_item_key("${resolved_embedded_item}" ikey) - - # Ensure the item is "inside the .app bundle" -- it should not be fixed up if - # it is not in the .app bundle... Otherwise, we'll modify files in the build - # tree, or in other varied locations around the file system, with our call to - # install_name_tool. Make sure that doesn't happen here: - # - get_dotapp_dir("${exepath}" exe_dotapp_dir) - string(LENGTH "${exe_dotapp_dir}/" exe_dotapp_dir_length) - string(LENGTH "${resolved_embedded_item}" resolved_embedded_item_length) - set(path_too_short 0) - set(is_embedded 0) - if(resolved_embedded_item_length LESS exe_dotapp_dir_length) - set(path_too_short 1) - endif() - if(NOT path_too_short) - string(SUBSTRING "${resolved_embedded_item}" 0 ${exe_dotapp_dir_length} item_substring) - if("${exe_dotapp_dir}/" STREQUAL item_substring) - set(is_embedded 1) - endif() - endif() - if(NOT is_embedded) - message(" exe_dotapp_dir/='${exe_dotapp_dir}/'") - message(" item_substring='${item_substring}'") - message(" resolved_embedded_item='${resolved_embedded_item}'") - message("") - message("Install or copy the item into the bundle before calling fixup_bundle.") - message("Or maybe there's a typo or incorrect path in one of the args to fixup_bundle?") - message("") - message(FATAL_ERROR "cannot fixup an item that is not in the bundle...") - endif() - - set(rpaths "${${ikey}_RPATHS}" "${${ikey}_RDEP_RPATHS}") - - set(prereqs "") - get_prerequisites("${resolved_embedded_item}" prereqs 1 0 "${exepath}" "${dirs}" "${rpaths}") - - set(changes "") - - foreach(pr ${prereqs}) - # Each referenced item's key is "rkey" in the loop: - # - get_item_key("${pr}" rkey) - - if(NOT "${${rkey}_EMBEDDED_ITEM}" STREQUAL "") - set(changes ${changes} "-change" "${pr}" "${${rkey}_EMBEDDED_ITEM}") - else() - message("warning: unexpected reference to '${pr}'") - endif() - endforeach() - - if(BU_CHMOD_BUNDLE_ITEMS) - execute_process(COMMAND chmod u+w "${resolved_embedded_item}") - endif() - - # CMAKE_INSTALL_NAME_TOOL may not be set if executed in script mode - # Duplicated from CMakeFindBinUtils.cmake - find_program(CMAKE_INSTALL_NAME_TOOL NAMES install_name_tool HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - - # Only if install_name_tool supports -delete_rpath: - # - execute_process(COMMAND ${CMAKE_INSTALL_NAME_TOOL} - OUTPUT_VARIABLE install_name_tool_usage - ERROR_VARIABLE install_name_tool_usage - ) - if(install_name_tool_usage MATCHES ".*-delete_rpath.*") - foreach(rpath ${${ikey}_RPATHS}) - set(changes ${changes} -delete_rpath "${rpath}") - endforeach() - endif() - - if(${ikey}_EMBEDDED_ITEM) - set(changes ${changes} -id "${${ikey}_EMBEDDED_ITEM}") - endif() - - # Change this item's id and all of its references in one call - # to install_name_tool: - # - if(changes) - set(cmd ${CMAKE_INSTALL_NAME_TOOL} ${changes} "${resolved_embedded_item}") - execute_process(COMMAND ${cmd} RESULT_VARIABLE install_name_tool_result) - if(NOT install_name_tool_result EQUAL 0) - string(REPLACE ";" "' '" msg "'${cmd}'") - message(FATAL_ERROR "Command failed:\n ${msg}") - endif() - endif() -endfunction() - - -function(fixup_bundle app libs dirs) - message(STATUS "fixup_bundle") - message(STATUS " app='${app}'") - message(STATUS " libs='${libs}'") - message(STATUS " dirs='${dirs}'") - - set(options) - set(oneValueArgs) - set(multiValueArgs IGNORE_ITEM) - cmake_parse_arguments(CFG "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN} ) - - message(STATUS " ignoreItems='${CFG_IGNORE_ITEM}'") - - get_bundle_and_executable("${app}" bundle executable valid) - if(valid) - get_filename_component(exepath "${executable}" PATH) - - message(STATUS "fixup_bundle: preparing...") - get_bundle_keys("${app}" "${libs}" "${dirs}" keys IGNORE_ITEM "${CFG_IGNORE_ITEM}") - - message(STATUS "fixup_bundle: copying...") - list(LENGTH keys n) - math(EXPR n ${n}*2) - - set(i 0) - foreach(key ${keys}) - math(EXPR i ${i}+1) - if("${${key}_COPYFLAG}" STREQUAL "2") - message(STATUS "${i}/${n}: linking '${${key}_RESOLVED_ITEM}' -> '${${key}_RESOLVED_EMBEDDED_ITEM}'") - elseif(${${key}_COPYFLAG}) - message(STATUS "${i}/${n}: copying '${${key}_RESOLVED_ITEM}'") - else() - message(STATUS "${i}/${n}: *NOT* copying '${${key}_RESOLVED_ITEM}'") - endif() - - set(show_status 0) - if(show_status) - message(STATUS "key='${key}'") - message(STATUS "item='${${key}_ITEM}'") - message(STATUS "resolved_item='${${key}_RESOLVED_ITEM}'") - message(STATUS "default_embedded_path='${${key}_DEFAULT_EMBEDDED_PATH}'") - message(STATUS "embedded_item='${${key}_EMBEDDED_ITEM}'") - message(STATUS "resolved_embedded_item='${${key}_RESOLVED_EMBEDDED_ITEM}'") - message(STATUS "copyflag='${${key}_COPYFLAG}'") - message(STATUS "") - endif() - - if("${${key}_COPYFLAG}" STREQUAL "2") - link_resolved_item_into_bundle("${${key}_RESOLVED_ITEM}" - "${${key}_RESOLVED_EMBEDDED_ITEM}") - elseif(${${key}_COPYFLAG}) - set(item "${${key}_ITEM}") - if(item MATCHES "[^/]+\\.framework/") - copy_resolved_framework_into_bundle("${${key}_RESOLVED_ITEM}" - "${${key}_RESOLVED_EMBEDDED_ITEM}") - else() - copy_resolved_item_into_bundle("${${key}_RESOLVED_ITEM}" - "${${key}_RESOLVED_EMBEDDED_ITEM}") - endif() - endif() - endforeach() - - message(STATUS "fixup_bundle: fixing...") - foreach(key ${keys}) - math(EXPR i ${i}+1) - if(APPLE) - message(STATUS "${i}/${n}: fixing up '${${key}_RESOLVED_EMBEDDED_ITEM}'") - if(NOT "${${key}_COPYFLAG}" STREQUAL "2") - fixup_bundle_item("${${key}_RESOLVED_EMBEDDED_ITEM}" "${exepath}" "${dirs}") - endif() - else() - message(STATUS "${i}/${n}: fix-up not required on this platform '${${key}_RESOLVED_EMBEDDED_ITEM}'") - endif() - endforeach() - - message(STATUS "fixup_bundle: cleaning up...") - clear_bundle_keys(keys) - - message(STATUS "fixup_bundle: verifying...") - verify_app("${app}" IGNORE_ITEM "${CFG_IGNORE_ITEM}") - else() - message(SEND_ERROR "error: fixup_bundle: not a valid bundle") - endif() - - message(STATUS "fixup_bundle: done") -endfunction() - - -function(copy_and_fixup_bundle src dst libs dirs) - execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory "${src}" "${dst}") - fixup_bundle("${dst}" "${libs}" "${dirs}") -endfunction() - - -function(verify_bundle_prerequisites bundle result_var info_var) - set(result 1) - set(info "") - set(count 0) - - set(options) - set(oneValueArgs) - set(multiValueArgs IGNORE_ITEM) - cmake_parse_arguments(CFG "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN} ) - - get_bundle_main_executable("${bundle}" main_bundle_exe) - - get_bundle_all_executables("${bundle}" file_list) - foreach(f ${file_list}) - get_filename_component(exepath "${f}" PATH) - math(EXPR count "${count} + 1") - - message(STATUS "executable file ${count}: ${f}") - - set(prereqs "") - get_filename_component(prereq_filename ${f} NAME) - - if(NOT prereq_filename IN_LIST CFG_IGNORE_ITEM) - get_item_rpaths(${f} _main_exe_rpaths) - get_prerequisites("${f}" prereqs 1 1 "${exepath}" "${_main_exe_rpaths}") - - # On the Mac, - # "embedded" and "system" prerequisites are fine... anything else means - # the bundle's prerequisites are not verified (i.e., the bundle is not - # really "standalone") - # - # On Windows (and others? Linux/Unix/...?) - # "local" and "system" prereqs are fine... - # - - set(external_prereqs "") - - foreach(p ${prereqs}) - set(p_type "") - gp_file_type("${f}" "${p}" p_type) - - if(APPLE) - if(NOT p_type STREQUAL "embedded" AND NOT p_type STREQUAL "system") - set(external_prereqs ${external_prereqs} "${p}") - endif() - else() - if(NOT p_type STREQUAL "local" AND NOT p_type STREQUAL "system") - set(external_prereqs ${external_prereqs} "${p}") - endif() - endif() - endforeach() - - if(external_prereqs) - # Found non-system/somehow-unacceptable prerequisites: - set(result 0) - set(info ${info} "external prerequisites found:\nf='${f}'\nexternal_prereqs='${external_prereqs}'\n") - endif() - else() - message(STATUS "Ignoring file: ${prereq_filename}") - endif() - endforeach() - - if(result) - set(info "Verified ${count} executable files in '${bundle}'") - endif() - - set(${result_var} "${result}" PARENT_SCOPE) - set(${info_var} "${info}" PARENT_SCOPE) -endfunction() - - -function(verify_bundle_symlinks bundle result_var info_var) - set(result 1) - set(info "") - set(count 0) - - # TODO: implement this function for real... - # Right now, it is just a stub that verifies unconditionally... - - set(${result_var} "${result}" PARENT_SCOPE) - set(${info_var} "${info}" PARENT_SCOPE) -endfunction() - - -function(verify_app app) - set(verified 0) - set(info "") - - set(options) - set(oneValueArgs) - set(multiValueArgs IGNORE_ITEM) - cmake_parse_arguments(CFG "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN} ) - - get_bundle_and_executable("${app}" bundle executable valid) - - message(STATUS "===========================================================================") - message(STATUS "Analyzing app='${app}'") - message(STATUS "bundle='${bundle}'") - message(STATUS "executable='${executable}'") - message(STATUS "valid='${valid}'") - - # Verify that the bundle does not have any "external" prerequisites: - # - verify_bundle_prerequisites("${bundle}" verified info IGNORE_ITEM "${CFG_IGNORE_ITEM}") - message(STATUS "verified='${verified}'") - message(STATUS "info='${info}'") - message(STATUS "") - - if(verified) - # Verify that the bundle does not have any symlinks to external files: - # - verify_bundle_symlinks("${bundle}" verified info) - message(STATUS "verified='${verified}'") - message(STATUS "info='${info}'") - message(STATUS "") - endif() - - if(NOT verified) - message(FATAL_ERROR "error: verify_app failed") - endif() -endfunction() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CMakeASMInformation.cmake b/share/cmake-3.18/Modules/CMakeASMInformation.cmake deleted file mode 100644 index 03195cc..0000000 --- a/share/cmake-3.18/Modules/CMakeASMInformation.cmake +++ /dev/null
@@ -1,110 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(UNIX) - set(CMAKE_ASM${ASM_DIALECT}_OUTPUT_EXTENSION .o) -else() - set(CMAKE_ASM${ASM_DIALECT}_OUTPUT_EXTENSION .obj) -endif() - -set(CMAKE_INCLUDE_FLAG_ASM${ASM_DIALECT} "-I") # -I -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_ASM${ASM_DIALECT}_COMPILER}" NAME_WE) - -if("${CMAKE_BASE_NAME}" STREQUAL "as") - set(CMAKE_BASE_NAME gas) -endif() - -# Load compiler-specific information. -set(_INCLUDED_FILE "") -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID) - include(Compiler/${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}-ASM${ASM_DIALECT} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if(NOT _INCLUDED_FILE) - if("ASM${ASM_DIALECT}" STREQUAL "ASM") - message(STATUS "Warning: Did not find file Compiler/${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}-ASM${ASM_DIALECT}") - endif() - include(Platform/${CMAKE_BASE_NAME} OPTIONAL) -endif() - -if(CMAKE_SYSTEM_PROCESSOR) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}-ASM${ASM_DIALECT}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) - if(NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif() -endif() - -include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}-ASM${ASM_DIALECT} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -if(NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} OPTIONAL) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_ASM) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_ASM} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_ASM "${_override}") -endif() - -# Set default assembler file extensions: -if(NOT CMAKE_ASM${ASM_DIALECT}_SOURCE_FILE_EXTENSIONS) - set(CMAKE_ASM${ASM_DIALECT}_SOURCE_FILE_EXTENSIONS s;S;asm) -endif() - - -# Support for CMAKE_ASM${ASM_DIALECT}_FLAGS_INIT and friends: -set(CMAKE_ASM${ASM_DIALECT}_FLAGS_INIT "$ENV{ASM${ASM_DIALECT}FLAGS} ${CMAKE_ASM${ASM_DIALECT}_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_ASM${ASM_DIALECT}_FLAGS "Flags used by the ASM${ASM_DIALECT} compiler") - -if(NOT CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT) - set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT "<CMAKE_ASM${ASM_DIALECT}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT> -c <SOURCE>") -endif() - -if(NOT CMAKE_ASM${ASM_DIALECT}_CREATE_STATIC_LIBRARY) - set(CMAKE_ASM${ASM_DIALECT}_CREATE_STATIC_LIBRARY - "<CMAKE_AR> cr <TARGET> <LINK_FLAGS> <OBJECTS> " - "<CMAKE_RANLIB> <TARGET>") -endif() - -if(NOT CMAKE_ASM${ASM_DIALECT}_LINK_EXECUTABLE) - set(CMAKE_ASM${ASM_DIALECT}_LINK_EXECUTABLE - "<CMAKE_ASM${ASM_DIALECT}_COMPILER> <FLAGS> <CMAKE_ASM${ASM_DIALECT}_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_ASM${ASM_DIALECT}_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_ASM${ASM_DIALECT}_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_ASM${ASM_DIALECT}_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_ASM${ASM_DIALECT}_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_ASM${ASM_DIALECT}_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_ASM${ASM_DIALECT}_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_ASM${ASM_DIALECT}_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_ASM${ASM_DIALECT}_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_ASM${ASM_DIALECT}_FLAG}) -endif() - -# to be done -if(NOT CMAKE_ASM${ASM_DIALECT}_CREATE_SHARED_LIBRARY) - set(CMAKE_ASM${ASM_DIALECT}_CREATE_SHARED_LIBRARY) -endif() - -if(NOT CMAKE_ASM${ASM_DIALECT}_CREATE_SHARED_MODULE) - set(CMAKE_ASM${ASM_DIALECT}_CREATE_SHARED_MODULE) -endif() - - -set(CMAKE_ASM${ASM_DIALECT}_INFOMATION_LOADED 1) -
diff --git a/share/cmake-3.18/Modules/CMakeASM_MASMInformation.cmake b/share/cmake-3.18/Modules/CMakeASM_MASMInformation.cmake deleted file mode 100644 index 6d1e174..0000000 --- a/share/cmake-3.18/Modules/CMakeASM_MASMInformation.cmake +++ /dev/null
@@ -1,20 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# support for the MS assembler, masm and masm64 - -set(ASM_DIALECT "_MASM") - -set(CMAKE_ASM${ASM_DIALECT}_SOURCE_FILE_EXTENSIONS asm) - -set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT "<CMAKE_ASM${ASM_DIALECT}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> /c /Fo <OBJECT> <SOURCE>") - -# The ASM_MASM compiler id for this compiler is "MSVC", so fill out the runtime library table. -set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreaded "") -set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDLL "") -set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDebug "") -set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDebugDLL "") - -include(CMakeASMInformation) -set(ASM_DIALECT)
diff --git a/share/cmake-3.18/Modules/CMakeASM_NASMInformation.cmake b/share/cmake-3.18/Modules/CMakeASM_NASMInformation.cmake deleted file mode 100644 index 97cb488..0000000 --- a/share/cmake-3.18/Modules/CMakeASM_NASMInformation.cmake +++ /dev/null
@@ -1,44 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# support for the nasm assembler - -set(CMAKE_ASM_NASM_SOURCE_FILE_EXTENSIONS nasm asm) - -if(NOT CMAKE_ASM_NASM_OBJECT_FORMAT) - if(WIN32) - if(DEFINED CMAKE_C_SIZEOF_DATA_PTR AND CMAKE_C_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT win64) - elseif(DEFINED CMAKE_CXX_SIZEOF_DATA_PTR AND CMAKE_CXX_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT win64) - else() - set(CMAKE_ASM_NASM_OBJECT_FORMAT win32) - endif() - elseif(APPLE) - if(DEFINED CMAKE_C_SIZEOF_DATA_PTR AND CMAKE_C_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT macho64) - elseif(DEFINED CMAKE_CXX_SIZEOF_DATA_PTR AND CMAKE_CXX_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT macho64) - else() - set(CMAKE_ASM_NASM_OBJECT_FORMAT macho) - endif() - else() - if(DEFINED CMAKE_C_SIZEOF_DATA_PTR AND CMAKE_C_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT elf64) - elseif(DEFINED CMAKE_CXX_SIZEOF_DATA_PTR AND CMAKE_CXX_SIZEOF_DATA_PTR EQUAL 8) - set(CMAKE_ASM_NASM_OBJECT_FORMAT elf64) - else() - set(CMAKE_ASM_NASM_OBJECT_FORMAT elf) - endif() - endif() -endif() - -if(NOT CMAKE_ASM_NASM_COMPILE_OBJECT) - set(CMAKE_ASM_NASM_COMPILE_OBJECT "<CMAKE_ASM_NASM_COMPILER> <INCLUDES> <FLAGS> -f ${CMAKE_ASM_NASM_OBJECT_FORMAT} -o <OBJECT> <SOURCE>") -endif() - -# Load the generic ASMInformation file: -set(ASM_DIALECT "_NASM") -include(CMakeASMInformation) -set(ASM_DIALECT)
diff --git a/share/cmake-3.18/Modules/CMakeCCompiler.cmake.in b/share/cmake-3.18/Modules/CMakeCCompiler.cmake.in deleted file mode 100644 index eea3f5d..0000000 --- a/share/cmake-3.18/Modules/CMakeCCompiler.cmake.in +++ /dev/null
@@ -1,77 +0,0 @@ -set(CMAKE_C_COMPILER "@CMAKE_C_COMPILER@") -set(CMAKE_C_COMPILER_ARG1 "@CMAKE_C_COMPILER_ARG1@") -set(CMAKE_C_COMPILER_ID "@CMAKE_C_COMPILER_ID@") -set(CMAKE_C_COMPILER_VERSION "@CMAKE_C_COMPILER_VERSION@") -set(CMAKE_C_COMPILER_VERSION_INTERNAL "@CMAKE_C_COMPILER_VERSION_INTERNAL@") -set(CMAKE_C_COMPILER_WRAPPER "@CMAKE_C_COMPILER_WRAPPER@") -set(CMAKE_C_STANDARD_COMPUTED_DEFAULT "@CMAKE_C_STANDARD_COMPUTED_DEFAULT@") -set(CMAKE_C_COMPILE_FEATURES "@CMAKE_C_COMPILE_FEATURES@") -set(CMAKE_C90_COMPILE_FEATURES "@CMAKE_C90_COMPILE_FEATURES@") -set(CMAKE_C99_COMPILE_FEATURES "@CMAKE_C99_COMPILE_FEATURES@") -set(CMAKE_C11_COMPILE_FEATURES "@CMAKE_C11_COMPILE_FEATURES@") - -set(CMAKE_C_PLATFORM_ID "@CMAKE_C_PLATFORM_ID@") -set(CMAKE_C_SIMULATE_ID "@CMAKE_C_SIMULATE_ID@") -set(CMAKE_C_COMPILER_FRONTEND_VARIANT "@CMAKE_C_COMPILER_FRONTEND_VARIANT@") -set(CMAKE_C_SIMULATE_VERSION "@CMAKE_C_SIMULATE_VERSION@") -@_SET_CMAKE_C_COMPILER_ARCHITECTURE_ID@ -@_SET_CMAKE_C_COMPILER_SYSROOT@ -@SET_MSVC_C_ARCHITECTURE_ID@ -@SET_CMAKE_XCODE_ARCHS@ -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_C_COMPILER_AR "@CMAKE_C_COMPILER_AR@") -set(CMAKE_RANLIB "@CMAKE_RANLIB@") -set(CMAKE_C_COMPILER_RANLIB "@CMAKE_C_COMPILER_RANLIB@") -set(CMAKE_LINKER "@CMAKE_LINKER@") -set(CMAKE_MT "@CMAKE_MT@") -set(CMAKE_COMPILER_IS_GNUCC @CMAKE_COMPILER_IS_GNUCC@) -set(CMAKE_C_COMPILER_LOADED 1) -set(CMAKE_C_COMPILER_WORKS @CMAKE_C_COMPILER_WORKS@) -set(CMAKE_C_ABI_COMPILED @CMAKE_C_ABI_COMPILED@) -set(CMAKE_COMPILER_IS_MINGW @CMAKE_COMPILER_IS_MINGW@) -set(CMAKE_COMPILER_IS_CYGWIN @CMAKE_COMPILER_IS_CYGWIN@) -if(CMAKE_COMPILER_IS_CYGWIN) - set(CYGWIN 1) - set(UNIX 1) -endif() - -set(CMAKE_C_COMPILER_ENV_VAR "CC") - -if(CMAKE_COMPILER_IS_MINGW) - set(MINGW 1) -endif() -set(CMAKE_C_COMPILER_ID_RUN 1) -set(CMAKE_C_SOURCE_FILE_EXTENSIONS c;m) -set(CMAKE_C_IGNORE_EXTENSIONS h;H;o;O;obj;OBJ;def;DEF;rc;RC) -set(CMAKE_C_LINKER_PREFERENCE 10) - -# Save compiler ABI information. -set(CMAKE_C_SIZEOF_DATA_PTR "@CMAKE_C_SIZEOF_DATA_PTR@") -set(CMAKE_C_COMPILER_ABI "@CMAKE_C_COMPILER_ABI@") -set(CMAKE_C_LIBRARY_ARCHITECTURE "@CMAKE_C_LIBRARY_ARCHITECTURE@") - -if(CMAKE_C_SIZEOF_DATA_PTR) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_C_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_C_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_C_COMPILER_ABI}") -endif() - -if(CMAKE_C_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_C_LIBRARY_ARCHITECTURE@") -endif() - -set(CMAKE_C_CL_SHOWINCLUDES_PREFIX "@CMAKE_C_CL_SHOWINCLUDES_PREFIX@") -if(CMAKE_C_CL_SHOWINCLUDES_PREFIX) - set(CMAKE_CL_SHOWINCLUDES_PREFIX "${CMAKE_C_CL_SHOWINCLUDES_PREFIX}") -endif() - -@CMAKE_C_COMPILER_CUSTOM_CODE@ -@CMAKE_C_SYSROOT_FLAG_CODE@ -@CMAKE_C_OSX_DEPLOYMENT_TARGET_FLAG_CODE@ - -set(CMAKE_C_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_C_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_C_IMPLICIT_LINK_LIBRARIES "@CMAKE_C_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_C_IMPLICIT_LINK_DIRECTORIES "@CMAKE_C_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_C_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_C_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@")
diff --git a/share/cmake-3.18/Modules/CMakeCCompilerABI.c b/share/cmake-3.18/Modules/CMakeCCompilerABI.c deleted file mode 100644 index 08cf39b..0000000 --- a/share/cmake-3.18/Modules/CMakeCCompilerABI.c +++ /dev/null
@@ -1,25 +0,0 @@ -#ifdef __cplusplus -# error "A C++ compiler has been selected for C." -#endif - -#ifdef __CLASSIC_C__ -# define const -#endif - -#include "CMakeCompilerABI.h" - -#ifdef __CLASSIC_C__ -int main(argc, argv) int argc; -char* argv[]; -#else -int main(int argc, char* argv[]) -#endif -{ - int require = 0; - require += info_sizeof_dptr[argc]; -#if defined(ABI_ID) - require += info_abi[argc]; -#endif - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeCCompilerId.c.in b/share/cmake-3.18/Modules/CMakeCCompilerId.c.in deleted file mode 100644 index 2f6bdb4..0000000 --- a/share/cmake-3.18/Modules/CMakeCCompilerId.c.in +++ /dev/null
@@ -1,87 +0,0 @@ -#ifdef __cplusplus -# error "A C++ compiler has been selected for C." -#endif - -#if defined(__18CXX) -# define ID_VOID_MAIN -#endif -#if defined(__CLASSIC_C__) -/* cv-qualifiers did not exist in K&R C */ -# define const -# define volatile -#endif - -@CMAKE_C_COMPILER_ID_CONTENT@ - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_compiler = "INFO" ":" "compiler[" COMPILER_ID "]"; -#ifdef SIMULATE_ID -char const* info_simulate = "INFO" ":" "simulate[" SIMULATE_ID "]"; -#endif - -#ifdef __QNXNTO__ -char const* qnxnto = "INFO" ":" "qnxnto[]"; -#endif - -#if defined(__CRAYXE) || defined(__CRAYXC) -char const *info_cray = "INFO" ":" "compiler_wrapper[CrayPrgEnv]"; -#endif - -@CMAKE_C_COMPILER_ID_PLATFORM_CONTENT@ -@CMAKE_C_COMPILER_ID_ERROR_FOR_TEST@ - -#if !defined(__STDC__) -# if (defined(_MSC_VER) && !defined(__clang__)) \ - || (defined(__ibmxl__) || defined(__IBMC__)) -# define C_DIALECT "90" -# else -# define C_DIALECT -# endif -#elif __STDC_VERSION__ >= 201000L -# define C_DIALECT "11" -#elif __STDC_VERSION__ >= 199901L -# define C_DIALECT "99" -#else -# define C_DIALECT "90" -#endif -const char* info_language_dialect_default = - "INFO" ":" "dialect_default[" C_DIALECT "]"; - -/*--------------------------------------------------------------------------*/ - -#ifdef ID_VOID_MAIN -void main() {} -#else -# if defined(__CLASSIC_C__) -int main(argc, argv) int argc; char *argv[]; -# else -int main(int argc, char* argv[]) -# endif -{ - int require = 0; - require += info_compiler[argc]; - require += info_platform[argc]; - require += info_arch[argc]; -#ifdef COMPILER_VERSION_MAJOR - require += info_version[argc]; -#endif -#ifdef COMPILER_VERSION_INTERNAL - require += info_version_internal[argc]; -#endif -#ifdef SIMULATE_ID - require += info_simulate[argc]; -#endif -#ifdef SIMULATE_VERSION_MAJOR - require += info_simulate_version[argc]; -#endif -#if defined(__CRAYXE) || defined(__CRAYXC) - require += info_cray[argc]; -#endif - require += info_language_dialect_default[argc]; - (void)argv; - return require; -} -#endif
diff --git a/share/cmake-3.18/Modules/CMakeCInformation.cmake b/share/cmake-3.18/Modules/CMakeCInformation.cmake deleted file mode 100644 index f6d620f..0000000 --- a/share/cmake-3.18/Modules/CMakeCInformation.cmake +++ /dev/null
@@ -1,195 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file sets the basic flags for the C language in CMake. -# It also loads the available platform file for the system-compiler -# if it exists. -# It also loads a system - compiler - processor (or target hardware) -# specific file, which is mainly useful for crosscompiling and embedded systems. - -include(CMakeLanguageInformation) - -# some compilers use different extensions (e.g. sdcc uses .rel) -# so set the extension here first so it can be overridden by the compiler specific file -if(UNIX) - set(CMAKE_C_OUTPUT_EXTENSION .o) -else() - set(CMAKE_C_OUTPUT_EXTENSION .obj) -endif() - -set(_INCLUDED_FILE 0) - -# Load compiler-specific information. -if(CMAKE_C_COMPILER_ID) - include(Compiler/${CMAKE_C_COMPILER_ID}-C OPTIONAL) -endif() - -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_C_COMPILER}" NAME_WE) -if(CMAKE_COMPILER_IS_GNUCC) - set(CMAKE_BASE_NAME gcc) -endif() - - -# load a hardware specific file, mostly useful for embedded compilers -if(CMAKE_SYSTEM_PROCESSOR) - if(CMAKE_C_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_C_COMPILER_ID}-C-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) - endif() - if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif () -endif() - - -# load the system- and compiler specific files -if(CMAKE_C_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_C_COMPILER_ID}-C - OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} - OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif () - -# load any compiler-wrapper specific information -if (CMAKE_C_COMPILER_WRAPPER) - __cmake_include_compiler_wrapper(C) -endif () - -# We specify the compiler information in the system file for some -# platforms, but this language may not have been enabled when the file -# was first included. Include it again to get the language info. -# Remove this when all compiler info is removed from system files. -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_SYSTEM_NAME} OPTIONAL) -endif () - -if(CMAKE_C_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_C_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_C_ABI_FILES) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_C) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_C} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_C "${_override}") -endif() - - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_C_FLAGS ${CMAKE_SHARED_LIBRARY_C_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_C_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS}) -endif() - -set(CMAKE_C_FLAGS_INIT "$ENV{CFLAGS} ${CMAKE_C_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_C_FLAGS "Flags used by the C compiler") - -if(CMAKE_C_STANDARD_LIBRARIES_INIT) - set(CMAKE_C_STANDARD_LIBRARIES "${CMAKE_C_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all C applications.") - mark_as_advanced(CMAKE_C_STANDARD_LIBRARIES) -endif() - -if(NOT CMAKE_C_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_C_COMPILER_LAUNCHER}) - set(CMAKE_C_COMPILER_LAUNCHER "$ENV{CMAKE_C_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for C.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rule variables - -# CMAKE_C_CREATE_SHARED_LIBRARY -# CMAKE_C_CREATE_SHARED_MODULE -# CMAKE_C_COMPILE_OBJECT -# CMAKE_C_LINK_EXECUTABLE - -# variables supplied by the generator at use time -# <TARGET> -# <TARGET_BASE> the target without the suffix -# <OBJECTS> -# <OBJECT> -# <LINK_LIBRARIES> -# <FLAGS> -# <LINK_FLAGS> - -# C compiler information -# <CMAKE_C_COMPILER> -# <CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS> -# <CMAKE_SHARED_MODULE_CREATE_C_FLAGS> -# <CMAKE_C_LINK_FLAGS> - -# Static library tools -# <CMAKE_AR> -# <CMAKE_RANLIB> - - -# create a C shared library -if(NOT CMAKE_C_CREATE_SHARED_LIBRARY) - set(CMAKE_C_CREATE_SHARED_LIBRARY - "<CMAKE_C_COMPILER> <CMAKE_SHARED_LIBRARY_C_FLAGS> <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>") -endif() - -# create a C shared module just copy the shared library rule -if(NOT CMAKE_C_CREATE_SHARED_MODULE) - set(CMAKE_C_CREATE_SHARED_MODULE ${CMAKE_C_CREATE_SHARED_LIBRARY}) -endif() - -# Create a static archive incrementally for large object file counts. -# If CMAKE_C_CREATE_STATIC_LIBRARY is set it will override these. -if(NOT DEFINED CMAKE_C_ARCHIVE_CREATE) - set(CMAKE_C_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_C_ARCHIVE_APPEND) - set(CMAKE_C_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_C_ARCHIVE_FINISH) - set(CMAKE_C_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -# compile a C file into an object file -if(NOT CMAKE_C_COMPILE_OBJECT) - set(CMAKE_C_COMPILE_OBJECT - "<CMAKE_C_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT> -c <SOURCE>") -endif() - -if(NOT CMAKE_C_LINK_EXECUTABLE) - set(CMAKE_C_LINK_EXECUTABLE - "<CMAKE_C_COMPILER> <FLAGS> <CMAKE_C_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_C_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_C_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_C_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_C_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_C_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_C_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_C_FLAG}) -endif() - -set(CMAKE_C_INFORMATION_LOADED 1) - -
diff --git a/share/cmake-3.18/Modules/CMakeCSharpCompilerId.cs.in b/share/cmake-3.18/Modules/CMakeCSharpCompilerId.cs.in deleted file mode 100644 index 987f63a..0000000 --- a/share/cmake-3.18/Modules/CMakeCSharpCompilerId.cs.in +++ /dev/null
@@ -1,63 +0,0 @@ -using System; - -namespace CSharp -{ - public class CSharpApp - { - const string InfoCompiler = "INFO:compiler[Microsoft " -#if PlatformToolsetv100 - + "Visual Studio" -#elif PlatformToolsetv110 - + "Visual Studio" -#elif PlatformToolsetv120 - + "Visual Studio" -#elif PlatformToolsetv140 - + "Visual Studio" -#elif PlatformToolsetv141 - + "Visual Studio" -#else - + "unknown" -#endif - + "]"; - - const string InfoPlatform = "INFO:platform[Windows]"; - - const string InfoArchitecture = "INFO:arch[" -#if Platformx64 - + "x64" -#elif Platformx86 - + "x86" -#elif PlatformxWin32 - + "Win32]" -#else - + "unknown" -#endif - + "]"; - - const string InfoCompilerVersion = "INFO:compiler_version[" -#if PlatformToolsetv100 - + "2010" -#elif PlatformToolsetv110 - + "2012" -#elif PlatformToolsetv120 - + "2013" -#elif PlatformToolsetv140 - + "2015" -#elif PlatformToolsetv141 - + "2017" -#else - + "9999" -#endif - + "]"; - - static void Main(string[] args) - { - // we have to print the lines to make sure - // the compiler does not optimize them away ... - System.Console.WriteLine(InfoCompiler); - System.Console.WriteLine(InfoPlatform); - System.Console.WriteLine(InfoArchitecture); - System.Console.WriteLine(InfoCompilerVersion); - } - } -}
diff --git a/share/cmake-3.18/Modules/CMakeCUDACompiler.cmake.in b/share/cmake-3.18/Modules/CMakeCUDACompiler.cmake.in deleted file mode 100644 index 704ad09..0000000 --- a/share/cmake-3.18/Modules/CMakeCUDACompiler.cmake.in +++ /dev/null
@@ -1,64 +0,0 @@ -set(CMAKE_CUDA_COMPILER "@CMAKE_CUDA_COMPILER@") -set(CMAKE_CUDA_HOST_COMPILER "@CMAKE_CUDA_HOST_COMPILER@") -set(CMAKE_CUDA_HOST_LINK_LAUNCHER "@CMAKE_CUDA_HOST_LINK_LAUNCHER@") -set(CMAKE_CUDA_COMPILER_ID "@CMAKE_CUDA_COMPILER_ID@") -set(CMAKE_CUDA_COMPILER_VERSION "@CMAKE_CUDA_COMPILER_VERSION@") -set(CMAKE_CUDA_STANDARD_COMPUTED_DEFAULT "@CMAKE_CUDA_STANDARD_COMPUTED_DEFAULT@") -set(CMAKE_CUDA_COMPILE_FEATURES "@CMAKE_CUDA_COMPILE_FEATURES@") -set(CMAKE_CUDA03_COMPILE_FEATURES "@CMAKE_CUDA03_COMPILE_FEATURES@") -set(CMAKE_CUDA11_COMPILE_FEATURES "@CMAKE_CUDA11_COMPILE_FEATURES@") -set(CMAKE_CUDA14_COMPILE_FEATURES "@CMAKE_CUDA14_COMPILE_FEATURES@") -set(CMAKE_CUDA17_COMPILE_FEATURES "@CMAKE_CUDA17_COMPILE_FEATURES@") -set(CMAKE_CUDA20_COMPILE_FEATURES "@CMAKE_CUDA20_COMPILE_FEATURES@") - -set(CMAKE_CUDA_PLATFORM_ID "@CMAKE_CUDA_PLATFORM_ID@") -set(CMAKE_CUDA_SIMULATE_ID "@CMAKE_CUDA_SIMULATE_ID@") -set(CMAKE_CUDA_COMPILER_FRONTEND_VARIANT "@CMAKE_CUDA_COMPILER_FRONTEND_VARIANT@") -set(CMAKE_CUDA_SIMULATE_VERSION "@CMAKE_CUDA_SIMULATE_VERSION@") -@SET_MSVC_CUDA_ARCHITECTURE_ID@ -@_SET_CMAKE_CUDA_COMPILER_SYSROOT@ - -set(CMAKE_CUDA_COMPILER_ENV_VAR "CUDACXX") -set(CMAKE_CUDA_HOST_COMPILER_ENV_VAR "CUDAHOSTCXX") - -set(CMAKE_CUDA_COMPILER_LOADED 1) -set(CMAKE_CUDA_COMPILER_ID_RUN 1) -set(CMAKE_CUDA_SOURCE_FILE_EXTENSIONS cu) -set(CMAKE_CUDA_LINKER_PREFERENCE 15) -set(CMAKE_CUDA_LINKER_PREFERENCE_PROPAGATES 1) - -set(CMAKE_CUDA_SIZEOF_DATA_PTR "@CMAKE_CUDA_SIZEOF_DATA_PTR@") -set(CMAKE_CUDA_COMPILER_ABI "@CMAKE_CUDA_COMPILER_ABI@") -set(CMAKE_CUDA_LIBRARY_ARCHITECTURE "@CMAKE_CUDA_LIBRARY_ARCHITECTURE@") - -if(CMAKE_CUDA_SIZEOF_DATA_PTR) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_CUDA_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_CUDA_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_CUDA_COMPILER_ABI}") -endif() - -if(CMAKE_CUDA_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_CUDA_LIBRARY_ARCHITECTURE@") -endif() - -set(CMAKE_CUDA_COMPILER_TOOLKIT_ROOT "@CMAKE_CUDA_COMPILER_TOOLKIT_ROOT@") -set(CMAKE_CUDA_COMPILER_LIBRARY_ROOT "@CMAKE_CUDA_COMPILER_LIBRARY_ROOT@") - -set(CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES "@CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES@") - -set(CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES "@CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES "@CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_CUDA_HOST_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_CUDA_HOST_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@") - -set(CMAKE_CUDA_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_CUDA_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES "@CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES "@CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_CUDA_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_CUDA_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@") - -@_SET_CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT@ - -set(CMAKE_LINKER "@CMAKE_LINKER@") -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_MT "@CMAKE_MT@")
diff --git a/share/cmake-3.18/Modules/CMakeCUDACompilerABI.cu b/share/cmake-3.18/Modules/CMakeCUDACompilerABI.cu deleted file mode 100644 index 702a7c5..0000000 --- a/share/cmake-3.18/Modules/CMakeCUDACompilerABI.cu +++ /dev/null
@@ -1,16 +0,0 @@ -#ifndef __CUDACC__ -# error "A C or C++ compiler has been selected for CUDA" -#endif - -#include "CMakeCompilerABI.h" - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_sizeof_dptr[argc]; -#if defined(ABI_ID) - require += info_abi[argc]; -#endif - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeCUDACompilerId.cu.in b/share/cmake-3.18/Modules/CMakeCUDACompilerId.cu.in deleted file mode 100644 index 2055de2..0000000 --- a/share/cmake-3.18/Modules/CMakeCUDACompilerId.cu.in +++ /dev/null
@@ -1,52 +0,0 @@ -#ifndef __CUDACC__ -# error "A C or C++ compiler has been selected for CUDA" -#endif - -@CMAKE_CUDA_COMPILER_ID_CONTENT@ - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_compiler = "INFO" ":" "compiler[" COMPILER_ID "]"; -#ifdef SIMULATE_ID -char const* info_simulate = "INFO" ":" "simulate[" SIMULATE_ID "]"; -#endif - -@CMAKE_CUDA_COMPILER_ID_PLATFORM_CONTENT@ -@CMAKE_CUDA_COMPILER_ID_ERROR_FOR_TEST@ - -const char* info_language_dialect_default = "INFO" ":" "dialect_default[" -#if __cplusplus > 201703L - "20" -#elif __cplusplus >= 201703L - "17" -#elif __cplusplus >= 201402L - "14" -#elif __cplusplus >= 201103L - "11" -#else - "03" -#endif -"]"; - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_compiler[argc]; - require += info_platform[argc]; -#ifdef COMPILER_VERSION_MAJOR - require += info_version[argc]; -#endif -#ifdef SIMULATE_ID - require += info_simulate[argc]; -#endif -#ifdef SIMULATE_VERSION_MAJOR - require += info_simulate_version[argc]; -#endif - require += info_language_dialect_default[argc]; - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeCUDAInformation.cmake b/share/cmake-3.18/Modules/CMakeCUDAInformation.cmake deleted file mode 100644 index f9f7574..0000000 --- a/share/cmake-3.18/Modules/CMakeCUDAInformation.cmake +++ /dev/null
@@ -1,205 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -if(UNIX) - set(CMAKE_CUDA_OUTPUT_EXTENSION .o) -else() - set(CMAKE_CUDA_OUTPUT_EXTENSION .obj) -endif() -set(CMAKE_INCLUDE_FLAG_CUDA "-I") - -# Set implicit links early so compiler-specific modules can use them. -set(__IMPLICT_LINKS ) -foreach(dir ${CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES}) - string(APPEND __IMPLICT_LINKS " -L\"${dir}\"") -endforeach() -foreach(lib ${CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES}) - if(${lib} MATCHES "/") - string(APPEND __IMPLICT_LINKS " \"${lib}\"") - else() - string(APPEND __IMPLICT_LINKS " -l${lib}") - endif() -endforeach() - -# Load compiler-specific information. -if(CMAKE_CUDA_COMPILER_ID) - include(Compiler/${CMAKE_CUDA_COMPILER_ID}-CUDA OPTIONAL) -endif() - -# load the system- and compiler specific files -if(CMAKE_CUDA_COMPILER_ID) - # load a hardware specific file, mostly useful for embedded compilers - if(CMAKE_SYSTEM_PROCESSOR) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_CUDA_COMPILER_ID}-CUDA-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif() - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_CUDA_COMPILER_ID}-CUDA OPTIONAL) -endif() - - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG) - set(CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG_SEP) - set(CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RPATH_LINK_CUDA_FLAG) - set(CMAKE_SHARED_LIBRARY_RPATH_LINK_CUDA_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_EXE_EXPORTS_CUDA_FLAG) - set(CMAKE_EXE_EXPORTS_CUDA_FLAG ${CMAKE_EXE_EXPORTS_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_SONAME_CUDA_FLAG) - set(CMAKE_SHARED_LIBRARY_SONAME_CUDA_FLAG ${CMAKE_SHARED_LIBRARY_SONAME_C_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_CUDA_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_CUDA_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_CUDA_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_CUDA_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_CUDA_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_CUDA_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_CUDA_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_CUDA_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_CUDA_WITH_RUNTIME_PATH) - set(CMAKE_SHARED_LIBRARY_LINK_CUDA_WITH_RUNTIME_PATH ${CMAKE_SHARED_LIBRARY_LINK_C_WITH_RUNTIME_PATH}) -endif() - - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_CUDA_FLAGS ${CMAKE_SHARED_LIBRARY_CUDA_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_CUDA_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_CUDA_FLAGS}) -endif() - -# add the flags to the cache based -# on the initial values computed in the platform/*.cmake files -# use _INIT variables so that this only happens the first time -# and you can set these flags in the cmake cache -set(CMAKE_CUDA_FLAGS_INIT "$ENV{CUDAFLAGS} ${CMAKE_CUDA_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_CUDA_FLAGS "Flags used by the CUDA compiler") - -if(CMAKE_CUDA_STANDARD_LIBRARIES_INIT) - set(CMAKE_CUDA_STANDARD_LIBRARIES "${CMAKE_CUDA_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all CUDA applications.") - mark_as_advanced(CMAKE_CUDA_STANDARD_LIBRARIES) -endif() - -if(NOT CMAKE_CUDA_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_CUDA_COMPILER_LAUNCHER}) - set(CMAKE_CUDA_COMPILER_LAUNCHER "$ENV{CMAKE_CUDA_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for CUDA.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rules: -# CMAKE_CUDA_CREATE_SHARED_LIBRARY -# CMAKE_CUDA_CREATE_SHARED_MODULE -# CMAKE_CUDA_COMPILE_WHOLE_COMPILATION -# CMAKE_CUDA_COMPILE_PTX_COMPILATION -# CMAKE_CUDA_COMPILE_SEPARABLE_COMPILATION -# CMAKE_CUDA_LINK_EXECUTABLE - -if(CMAKE_CUDA_HOST_COMPILER AND CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - string(APPEND _CMAKE_CUDA_EXTRA_FLAGS " -ccbin=<CMAKE_CUDA_HOST_COMPILER>") -endif() - -# create a shared library -if(NOT CMAKE_CUDA_CREATE_SHARED_LIBRARY) - set(CMAKE_CUDA_CREATE_SHARED_LIBRARY - "<CMAKE_CUDA_HOST_LINK_LAUNCHER> <CMAKE_SHARED_LIBRARY_CUDA_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_CUDA_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>${__IMPLICT_LINKS}") -endif() - -# create a shared module copy the shared library rule by default -if(NOT CMAKE_CUDA_CREATE_SHARED_MODULE) - set(CMAKE_CUDA_CREATE_SHARED_MODULE ${CMAKE_CUDA_CREATE_SHARED_LIBRARY}) -endif() - -# Create a static archive incrementally for large object file counts. -if(NOT DEFINED CMAKE_CUDA_ARCHIVE_CREATE) - set(CMAKE_CUDA_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_CUDA_ARCHIVE_APPEND) - set(CMAKE_CUDA_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_CUDA_ARCHIVE_FINISH) - set(CMAKE_CUDA_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -#Specify how to compile when ptx has been requested -if(NOT CMAKE_CUDA_COMPILE_PTX_COMPILATION) - set(CMAKE_CUDA_COMPILE_PTX_COMPILATION - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <DEFINES> <INCLUDES> <FLAGS> ${_CMAKE_COMPILE_AS_CUDA_FLAG} ${_CMAKE_CUDA_PTX_FLAG} <SOURCE> -o <OBJECT>") -endif() - -#Specify how to compile when separable compilation has been requested -if(NOT CMAKE_CUDA_COMPILE_SEPARABLE_COMPILATION) - set(CMAKE_CUDA_COMPILE_SEPARABLE_COMPILATION - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <DEFINES> <INCLUDES> <FLAGS> ${_CMAKE_COMPILE_AS_CUDA_FLAG} -dc <SOURCE> -o <OBJECT>") -endif() - -#Specify how to compile when whole compilation has been requested -if(NOT CMAKE_CUDA_COMPILE_WHOLE_COMPILATION) - set(CMAKE_CUDA_COMPILE_WHOLE_COMPILATION - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <DEFINES> <INCLUDES> <FLAGS> ${_CMAKE_COMPILE_AS_CUDA_FLAG} -c <SOURCE> -o <OBJECT>") -endif() - -if(CMAKE_GENERATOR STREQUAL "Ninja" AND NOT CMAKE_DEPFILE_FLAGS_CUDA) - set(CMAKE_CUDA_COMPILE_DEPENDENCY_DETECTION - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <DEFINES> <INCLUDES> <FLAGS> ${_CMAKE_COMPILE_AS_CUDA_FLAG} -M <SOURCE> -MT <OBJECT> -o $DEP_FILE") - #The Ninja generator uses the make file dependency files to determine what - #files need to be recompiled. Unfortunately, nvcc < 10.2 doesn't support building - #a source file and generating the dependencies of said file in a single - #invocation. Instead we have to state that you need to chain two commands. - # - #The makefile generators uses the custom CMake dependency scanner, and thus - #it is exempt from this logic. - list(APPEND CMAKE_CUDA_COMPILE_PTX_COMPILATION "${CMAKE_CUDA_COMPILE_DEPENDENCY_DETECTION}") - list(APPEND CMAKE_CUDA_COMPILE_SEPARABLE_COMPILATION "${CMAKE_CUDA_COMPILE_DEPENDENCY_DETECTION}") - list(APPEND CMAKE_CUDA_COMPILE_WHOLE_COMPILATION "${CMAKE_CUDA_COMPILE_DEPENDENCY_DETECTION}") -endif() - -# compile a cu file into an executable -if(NOT CMAKE_CUDA_LINK_EXECUTABLE) - set(CMAKE_CUDA_LINK_EXECUTABLE - "<CMAKE_CUDA_HOST_LINK_LAUNCHER> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>${__IMPLICT_LINKS}") -endif() - -# Add implicit host link directories that contain device libraries -# to the device link line. -set(__IMPLICT_DLINK_DIRS ${CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES}) -if(__IMPLICT_DLINK_DIRS) - list(REMOVE_ITEM __IMPLICT_DLINK_DIRS ${CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES}) -endif() -set(__IMPLICT_DLINK_FLAGS ) -foreach(dir ${__IMPLICT_DLINK_DIRS}) - if(EXISTS "${dir}/libcurand_static.a") - string(APPEND __IMPLICT_DLINK_FLAGS " -L\"${dir}\"") - endif() -endforeach() -unset(__IMPLICT_DLINK_DIRS) - - -#These are used when linking relocatable (dc) cuda code -if(NOT CMAKE_CUDA_DEVICE_LINK_LIBRARY) - set(CMAKE_CUDA_DEVICE_LINK_LIBRARY - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> ${CMAKE_CUDA_COMPILE_OPTIONS_PIC} ${_CMAKE_CUDA_EXTRA_DEVICE_LINK_FLAGS} -shared -dlink <OBJECTS> -o <TARGET> <LINK_LIBRARIES>${__IMPLICT_DLINK_FLAGS}") -endif() -if(NOT CMAKE_CUDA_DEVICE_LINK_EXECUTABLE) - set(CMAKE_CUDA_DEVICE_LINK_EXECUTABLE - "<CMAKE_CUDA_COMPILER> ${_CMAKE_CUDA_EXTRA_FLAGS} <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> ${CMAKE_CUDA_COMPILE_OPTIONS_PIC} ${_CMAKE_CUDA_EXTRA_DEVICE_LINK_FLAGS} -shared -dlink <OBJECTS> -o <TARGET> <LINK_LIBRARIES>${__IMPLICT_DLINK_FLAGS}") -endif() - -unset(__IMPLICT_DLINK_FLAGS) - -set(CMAKE_CUDA_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeCXXCompiler.cmake.in b/share/cmake-3.18/Modules/CMakeCXXCompiler.cmake.in deleted file mode 100644 index 09bdc23..0000000 --- a/share/cmake-3.18/Modules/CMakeCXXCompiler.cmake.in +++ /dev/null
@@ -1,89 +0,0 @@ -set(CMAKE_CXX_COMPILER "@CMAKE_CXX_COMPILER@") -set(CMAKE_CXX_COMPILER_ARG1 "@CMAKE_CXX_COMPILER_ARG1@") -set(CMAKE_CXX_COMPILER_ID "@CMAKE_CXX_COMPILER_ID@") -set(CMAKE_CXX_COMPILER_VERSION "@CMAKE_CXX_COMPILER_VERSION@") -set(CMAKE_CXX_COMPILER_VERSION_INTERNAL "@CMAKE_CXX_COMPILER_VERSION_INTERNAL@") -set(CMAKE_CXX_COMPILER_WRAPPER "@CMAKE_CXX_COMPILER_WRAPPER@") -set(CMAKE_CXX_STANDARD_COMPUTED_DEFAULT "@CMAKE_CXX_STANDARD_COMPUTED_DEFAULT@") -set(CMAKE_CXX_COMPILE_FEATURES "@CMAKE_CXX_COMPILE_FEATURES@") -set(CMAKE_CXX98_COMPILE_FEATURES "@CMAKE_CXX98_COMPILE_FEATURES@") -set(CMAKE_CXX11_COMPILE_FEATURES "@CMAKE_CXX11_COMPILE_FEATURES@") -set(CMAKE_CXX14_COMPILE_FEATURES "@CMAKE_CXX14_COMPILE_FEATURES@") -set(CMAKE_CXX17_COMPILE_FEATURES "@CMAKE_CXX17_COMPILE_FEATURES@") -set(CMAKE_CXX20_COMPILE_FEATURES "@CMAKE_CXX20_COMPILE_FEATURES@") - -set(CMAKE_CXX_PLATFORM_ID "@CMAKE_CXX_PLATFORM_ID@") -set(CMAKE_CXX_SIMULATE_ID "@CMAKE_CXX_SIMULATE_ID@") -set(CMAKE_CXX_COMPILER_FRONTEND_VARIANT "@CMAKE_CXX_COMPILER_FRONTEND_VARIANT@") -set(CMAKE_CXX_SIMULATE_VERSION "@CMAKE_CXX_SIMULATE_VERSION@") -@_SET_CMAKE_CXX_COMPILER_ARCHITECTURE_ID@ -@_SET_CMAKE_CXX_COMPILER_SYSROOT@ -@SET_MSVC_CXX_ARCHITECTURE_ID@ -@SET_CMAKE_XCODE_ARCHS@ -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_CXX_COMPILER_AR "@CMAKE_CXX_COMPILER_AR@") -set(CMAKE_RANLIB "@CMAKE_RANLIB@") -set(CMAKE_CXX_COMPILER_RANLIB "@CMAKE_CXX_COMPILER_RANLIB@") -set(CMAKE_LINKER "@CMAKE_LINKER@") -set(CMAKE_MT "@CMAKE_MT@") -set(CMAKE_COMPILER_IS_GNUCXX @CMAKE_COMPILER_IS_GNUCXX@) -set(CMAKE_CXX_COMPILER_LOADED 1) -set(CMAKE_CXX_COMPILER_WORKS @CMAKE_CXX_COMPILER_WORKS@) -set(CMAKE_CXX_ABI_COMPILED @CMAKE_CXX_ABI_COMPILED@) -set(CMAKE_COMPILER_IS_MINGW @CMAKE_COMPILER_IS_MINGW@) -set(CMAKE_COMPILER_IS_CYGWIN @CMAKE_COMPILER_IS_CYGWIN@) -if(CMAKE_COMPILER_IS_CYGWIN) - set(CYGWIN 1) - set(UNIX 1) -endif() - -set(CMAKE_CXX_COMPILER_ENV_VAR "CXX") - -if(CMAKE_COMPILER_IS_MINGW) - set(MINGW 1) -endif() -set(CMAKE_CXX_COMPILER_ID_RUN 1) -set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS C;M;c++;cc;cpp;cxx;m;mm;CPP) -set(CMAKE_CXX_IGNORE_EXTENSIONS inl;h;hpp;HPP;H;o;O;obj;OBJ;def;DEF;rc;RC) - -foreach (lang C OBJC OBJCXX) - if (CMAKE_${lang}_COMPILER_ID_RUN) - foreach(extension IN LISTS CMAKE_${lang}_SOURCE_FILE_EXTENSIONS) - list(REMOVE_ITEM CMAKE_CXX_SOURCE_FILE_EXTENSIONS ${extension}) - endforeach() - endif() -endforeach() - -set(CMAKE_CXX_LINKER_PREFERENCE 30) -set(CMAKE_CXX_LINKER_PREFERENCE_PROPAGATES 1) - -# Save compiler ABI information. -set(CMAKE_CXX_SIZEOF_DATA_PTR "@CMAKE_CXX_SIZEOF_DATA_PTR@") -set(CMAKE_CXX_COMPILER_ABI "@CMAKE_CXX_COMPILER_ABI@") -set(CMAKE_CXX_LIBRARY_ARCHITECTURE "@CMAKE_CXX_LIBRARY_ARCHITECTURE@") - -if(CMAKE_CXX_SIZEOF_DATA_PTR) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_CXX_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_CXX_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_CXX_COMPILER_ABI}") -endif() - -if(CMAKE_CXX_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_CXX_LIBRARY_ARCHITECTURE@") -endif() - -set(CMAKE_CXX_CL_SHOWINCLUDES_PREFIX "@CMAKE_CXX_CL_SHOWINCLUDES_PREFIX@") -if(CMAKE_CXX_CL_SHOWINCLUDES_PREFIX) - set(CMAKE_CL_SHOWINCLUDES_PREFIX "${CMAKE_CXX_CL_SHOWINCLUDES_PREFIX}") -endif() - -@CMAKE_CXX_COMPILER_CUSTOM_CODE@ -@CMAKE_CXX_SYSROOT_FLAG_CODE@ -@CMAKE_CXX_OSX_DEPLOYMENT_TARGET_FLAG_CODE@ - -set(CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_CXX_IMPLICIT_LINK_LIBRARIES "@CMAKE_CXX_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_CXX_IMPLICIT_LINK_DIRECTORIES "@CMAKE_CXX_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_CXX_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_CXX_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@")
diff --git a/share/cmake-3.18/Modules/CMakeCXXCompilerABI.cpp b/share/cmake-3.18/Modules/CMakeCXXCompilerABI.cpp deleted file mode 100644 index 2360534..0000000 --- a/share/cmake-3.18/Modules/CMakeCXXCompilerABI.cpp +++ /dev/null
@@ -1,16 +0,0 @@ -#ifndef __cplusplus -# error "A C compiler has been selected for C++." -#endif - -#include "CMakeCompilerABI.h" - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_sizeof_dptr[argc]; -#if defined(ABI_ID) - require += info_abi[argc]; -#endif - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeCXXCompilerId.cpp.in b/share/cmake-3.18/Modules/CMakeCXXCompilerId.cpp.in deleted file mode 100644 index a743ce7..0000000 --- a/share/cmake-3.18/Modules/CMakeCXXCompilerId.cpp.in +++ /dev/null
@@ -1,85 +0,0 @@ -/* This source file must have a .cpp extension so that all C++ compilers - recognize the extension without flags. Borland does not know .cxx for - example. */ -#ifndef __cplusplus -# error "A C compiler has been selected for C++." -#endif - -@CMAKE_CXX_COMPILER_ID_CONTENT@ - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_compiler = "INFO" ":" "compiler[" COMPILER_ID "]"; -#ifdef SIMULATE_ID -char const* info_simulate = "INFO" ":" "simulate[" SIMULATE_ID "]"; -#endif - -#ifdef __QNXNTO__ -char const* qnxnto = "INFO" ":" "qnxnto[]"; -#endif - -#if defined(__CRAYXE) || defined(__CRAYXC) -char const *info_cray = "INFO" ":" "compiler_wrapper[CrayPrgEnv]"; -#endif - -@CMAKE_CXX_COMPILER_ID_PLATFORM_CONTENT@ -@CMAKE_CXX_COMPILER_ID_ERROR_FOR_TEST@ - -#if defined(__INTEL_COMPILER) && defined(_MSVC_LANG) && _MSVC_LANG < 201403L -# if defined(__INTEL_CXX11_MODE__) -# if defined(__cpp_aggregate_nsdmi) -# define CXX_STD 201402L -# else -# define CXX_STD 201103L -# endif -# else -# define CXX_STD 199711L -# endif -#elif defined(_MSC_VER) && defined(_MSVC_LANG) -# define CXX_STD _MSVC_LANG -#else -# define CXX_STD __cplusplus -#endif - -const char* info_language_dialect_default = "INFO" ":" "dialect_default[" -#if CXX_STD > 201703L - "20" -#elif CXX_STD >= 201703L - "17" -#elif CXX_STD >= 201402L - "14" -#elif CXX_STD >= 201103L - "11" -#else - "98" -#endif -"]"; - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_compiler[argc]; - require += info_platform[argc]; -#ifdef COMPILER_VERSION_MAJOR - require += info_version[argc]; -#endif -#ifdef COMPILER_VERSION_INTERNAL - require += info_version_internal[argc]; -#endif -#ifdef SIMULATE_ID - require += info_simulate[argc]; -#endif -#ifdef SIMULATE_VERSION_MAJOR - require += info_simulate_version[argc]; -#endif -#if defined(__CRAYXE) || defined(__CRAYXC) - require += info_cray[argc]; -#endif - require += info_language_dialect_default[argc]; - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeCXXInformation.cmake b/share/cmake-3.18/Modules/CMakeCXXInformation.cmake deleted file mode 100644 index dbb4366..0000000 --- a/share/cmake-3.18/Modules/CMakeCXXInformation.cmake +++ /dev/null
@@ -1,282 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file sets the basic flags for the C++ language in CMake. -# It also loads the available platform file for the system-compiler -# if it exists. -# It also loads a system - compiler - processor (or target hardware) -# specific file, which is mainly useful for crosscompiling and embedded systems. - -include(CMakeLanguageInformation) - -# some compilers use different extensions (e.g. sdcc uses .rel) -# so set the extension here first so it can be overridden by the compiler specific file -if(UNIX) - set(CMAKE_CXX_OUTPUT_EXTENSION .o) -else() - set(CMAKE_CXX_OUTPUT_EXTENSION .obj) -endif() - -set(_INCLUDED_FILE 0) - -# Load compiler-specific information. -if(CMAKE_CXX_COMPILER_ID) - include(Compiler/${CMAKE_CXX_COMPILER_ID}-CXX OPTIONAL) -endif() - -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_CXX_COMPILER}" NAME_WE) -# since the gnu compiler has several names force g++ -if(CMAKE_COMPILER_IS_GNUCXX) - set(CMAKE_BASE_NAME g++) -endif() - - -# load a hardware specific file, mostly useful for embedded compilers -if(CMAKE_SYSTEM_PROCESSOR) - if(CMAKE_CXX_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_CXX_COMPILER_ID}-CXX-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) - endif() - if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif () -endif() - -# load the system- and compiler specific files -if(CMAKE_CXX_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_CXX_COMPILER_ID}-CXX OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} OPTIONAL - RESULT_VARIABLE _INCLUDED_FILE) -endif () - -# load any compiler-wrapper specific information -if (CMAKE_CXX_COMPILER_WRAPPER) - __cmake_include_compiler_wrapper(CXX) -endif () - -# We specify the compiler information in the system file for some -# platforms, but this language may not have been enabled when the file -# was first included. Include it again to get the language info. -# Remove this when all compiler info is removed from system files. -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_SYSTEM_NAME} OPTIONAL) -endif () - -if(CMAKE_CXX_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_CXX_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_CXX_ABI_FILES) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_CXX) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_CXX} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_CXX "${_override}") -endif() - - -# Create a set of shared library variable specific to C++ -# For 90% of the systems, these are the same flags as the C versions -# so if these are not set just copy the flags from the c version -if(NOT CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS}) -endif() - -if(NOT CMAKE_CXX_COMPILE_OPTIONS_PIC) - set(CMAKE_CXX_COMPILE_OPTIONS_PIC ${CMAKE_C_COMPILE_OPTIONS_PIC}) -endif() - -if(NOT CMAKE_CXX_COMPILE_OPTIONS_PIE) - set(CMAKE_CXX_COMPILE_OPTIONS_PIE ${CMAKE_C_COMPILE_OPTIONS_PIE}) -endif() -if(NOT CMAKE_CXX_LINK_OPTIONS_PIE) - set(CMAKE_CXX_LINK_OPTIONS_PIE ${CMAKE_C_LINK_OPTIONS_PIE}) -endif() -if(NOT CMAKE_CXX_LINK_OPTIONS_NO_PIE) - set(CMAKE_CXX_LINK_OPTIONS_NO_PIE ${CMAKE_C_LINK_OPTIONS_NO_PIE}) -endif() - -if(NOT CMAKE_CXX_COMPILE_OPTIONS_DLL) - set(CMAKE_CXX_COMPILE_OPTIONS_DLL ${CMAKE_C_COMPILE_OPTIONS_DLL}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_CXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_CXX_FLAGS ${CMAKE_SHARED_LIBRARY_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS ${CMAKE_SHARED_LIBRARY_LINK_C_FLAGS}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG) - set(CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG_SEP) - set(CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RPATH_LINK_CXX_FLAG) - set(CMAKE_SHARED_LIBRARY_RPATH_LINK_CXX_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_EXE_EXPORTS_CXX_FLAG) - set(CMAKE_EXE_EXPORTS_CXX_FLAG ${CMAKE_EXE_EXPORTS_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_SONAME_CXX_FLAG) - set(CMAKE_SHARED_LIBRARY_SONAME_CXX_FLAG ${CMAKE_SHARED_LIBRARY_SONAME_C_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_CXX_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_CXX_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_CXX_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_CXX_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_CXX_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_CXX_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_CXX_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_CXX_WITH_RUNTIME_PATH) - set(CMAKE_SHARED_LIBRARY_LINK_CXX_WITH_RUNTIME_PATH ${CMAKE_SHARED_LIBRARY_LINK_C_WITH_RUNTIME_PATH}) -endif() - -if(NOT CMAKE_INCLUDE_FLAG_CXX) - set(CMAKE_INCLUDE_FLAG_CXX ${CMAKE_INCLUDE_FLAG_C}) -endif() - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_CXX_FLAGS ${CMAKE_SHARED_LIBRARY_CXX_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS}) -endif() - -# repeat for modules -if(NOT CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS) - set(CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS ${CMAKE_SHARED_MODULE_CREATE_C_FLAGS}) -endif() - -if(NOT CMAKE_SHARED_MODULE_CXX_FLAGS) - set(CMAKE_SHARED_MODULE_CXX_FLAGS ${CMAKE_SHARED_MODULE_C_FLAGS}) -endif() - -# Initialize CXX link type selection flags from C versions. -foreach(type SHARED_LIBRARY SHARED_MODULE EXE) - if(NOT CMAKE_${type}_LINK_STATIC_CXX_FLAGS) - set(CMAKE_${type}_LINK_STATIC_CXX_FLAGS - ${CMAKE_${type}_LINK_STATIC_C_FLAGS}) - endif() - if(NOT CMAKE_${type}_LINK_DYNAMIC_CXX_FLAGS) - set(CMAKE_${type}_LINK_DYNAMIC_CXX_FLAGS - ${CMAKE_${type}_LINK_DYNAMIC_C_FLAGS}) - endif() -endforeach() - -# add the flags to the cache based -# on the initial values computed in the platform/*.cmake files -# use _INIT variables so that this only happens the first time -# and you can set these flags in the cmake cache -set(CMAKE_CXX_FLAGS_INIT "$ENV{CXXFLAGS} ${CMAKE_CXX_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_CXX_FLAGS "Flags used by the CXX compiler") - -if(CMAKE_CXX_STANDARD_LIBRARIES_INIT) - set(CMAKE_CXX_STANDARD_LIBRARIES "${CMAKE_CXX_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all C++ applications.") - mark_as_advanced(CMAKE_CXX_STANDARD_LIBRARIES) -endif() - -if(NOT CMAKE_CXX_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_CXX_COMPILER_LAUNCHER}) - set(CMAKE_CXX_COMPILER_LAUNCHER "$ENV{CMAKE_CXX_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for CXX.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rules: -# CMAKE_CXX_CREATE_SHARED_LIBRARY -# CMAKE_CXX_CREATE_SHARED_MODULE -# CMAKE_CXX_COMPILE_OBJECT -# CMAKE_CXX_LINK_EXECUTABLE - -# variables supplied by the generator at use time -# <TARGET> -# <TARGET_BASE> the target without the suffix -# <OBJECTS> -# <OBJECT> -# <LINK_LIBRARIES> -# <FLAGS> -# <LINK_FLAGS> - -# CXX compiler information -# <CMAKE_CXX_COMPILER> -# <CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS> -# <CMAKE_CXX_SHARED_MODULE_CREATE_FLAGS> -# <CMAKE_CXX_LINK_FLAGS> - -# Static library tools -# <CMAKE_AR> -# <CMAKE_RANLIB> - - -# create a shared C++ library -if(NOT CMAKE_CXX_CREATE_SHARED_LIBRARY) - set(CMAKE_CXX_CREATE_SHARED_LIBRARY - "<CMAKE_CXX_COMPILER> <CMAKE_SHARED_LIBRARY_CXX_FLAGS> <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>") -endif() - -# create a c++ shared module copy the shared library rule by default -if(NOT CMAKE_CXX_CREATE_SHARED_MODULE) - set(CMAKE_CXX_CREATE_SHARED_MODULE ${CMAKE_CXX_CREATE_SHARED_LIBRARY}) -endif() - - -# Create a static archive incrementally for large object file counts. -# If CMAKE_CXX_CREATE_STATIC_LIBRARY is set it will override these. -if(NOT DEFINED CMAKE_CXX_ARCHIVE_CREATE) - set(CMAKE_CXX_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_CXX_ARCHIVE_APPEND) - set(CMAKE_CXX_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_CXX_ARCHIVE_FINISH) - set(CMAKE_CXX_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -# compile a C++ file into an object file -if(NOT CMAKE_CXX_COMPILE_OBJECT) - set(CMAKE_CXX_COMPILE_OBJECT - "<CMAKE_CXX_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT> -c <SOURCE>") -endif() - -if(NOT CMAKE_CXX_LINK_EXECUTABLE) - set(CMAKE_CXX_LINK_EXECUTABLE - "<CMAKE_CXX_COMPILER> <FLAGS> <CMAKE_CXX_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -mark_as_advanced( -CMAKE_VERBOSE_MAKEFILE -) - -set(CMAKE_CXX_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeCheckCompilerFlagCommonPatterns.cmake b/share/cmake-3.18/Modules/CMakeCheckCompilerFlagCommonPatterns.cmake deleted file mode 100644 index 2dc75d6..0000000 --- a/share/cmake-3.18/Modules/CMakeCheckCompilerFlagCommonPatterns.cmake +++ /dev/null
@@ -1,36 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# Do NOT include this module directly into any of your code. It is meant as -# a library for Check*CompilerFlag.cmake modules. It's content may change in -# any way between releases. - -macro (CHECK_COMPILER_FLAG_COMMON_PATTERNS _VAR) - set(${_VAR} - FAIL_REGEX "[Uu]nrecogni[sz]ed .*option" # GNU, NAG - FAIL_REGEX "switch .* is no longer supported" # GNU - FAIL_REGEX "unknown .*option" # Clang - FAIL_REGEX "optimization flag .* not supported" # Clang - FAIL_REGEX "unknown argument ignored" # Clang (cl) - FAIL_REGEX "ignoring unknown option" # MSVC, Intel - FAIL_REGEX "warning D9002" # MSVC, any lang - FAIL_REGEX "option.*not supported" # Intel - FAIL_REGEX "invalid argument .*option" # Intel - FAIL_REGEX "ignoring option .*argument required" # Intel - FAIL_REGEX "ignoring option .*argument is of wrong type" # Intel - FAIL_REGEX "[Uu]nknown option" # HP - FAIL_REGEX "[Ww]arning: [Oo]ption" # SunPro - FAIL_REGEX "command option .* is not recognized" # XL - FAIL_REGEX "command option .* contains an incorrect subargument" # XL - FAIL_REGEX "Option .* is not recognized. Option will be ignored." # XL - FAIL_REGEX "not supported in this configuration. ignored" # AIX - FAIL_REGEX "File with unknown suffix passed to linker" # PGI - FAIL_REGEX "[Uu]nknown switch" # PGI - FAIL_REGEX "WARNING: unknown flag:" # Open64 - FAIL_REGEX "Incorrect command line option:" # Borland - FAIL_REGEX "Warning: illegal option" # SunStudio 12 - FAIL_REGEX "[Ww]arning: Invalid suboption" # Fujitsu - FAIL_REGEX "An invalid option .* appears on the command line" # Cray - ) -endmacro ()
diff --git a/share/cmake-3.18/Modules/CMakeCompilerABI.h b/share/cmake-3.18/Modules/CMakeCompilerABI.h deleted file mode 100644 index 45532af..0000000 --- a/share/cmake-3.18/Modules/CMakeCompilerABI.h +++ /dev/null
@@ -1,33 +0,0 @@ - -/* Size of a pointer-to-data in bytes. */ -#define SIZEOF_DPTR (sizeof(void*)) -const char info_sizeof_dptr[] = { - /* clang-format off */ - 'I', 'N', 'F', 'O', ':', 's', 'i', 'z', 'e', 'o', 'f', '_', 'd', 'p', 't', - 'r', '[', ('0' + ((SIZEOF_DPTR / 10) % 10)), ('0' + (SIZEOF_DPTR % 10)), ']', - '\0' - /* clang-format on */ -}; - -/* Application Binary Interface. */ - -/* Check for (some) ARM ABIs. - * See e.g. http://wiki.debian.org/ArmEabiPort for some information on this. */ -#if defined(__GNU__) && defined(__ELF__) && defined(__ARM_EABI__) -# define ABI_ID "ELF ARMEABI" -#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEB__) -# define ABI_ID "ELF ARM" -#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__) -# define ABI_ID "ELF ARM" - -#elif defined(__linux__) && defined(__ELF__) && defined(__amd64__) && \ - defined(__ILP32__) -# define ABI_ID "ELF X32" - -#elif defined(__ELF__) -# define ABI_ID "ELF" -#endif - -#if defined(ABI_ID) -static char const info_abi[] = "INFO:abi[" ABI_ID "]"; -#endif
diff --git a/share/cmake-3.18/Modules/CMakeCompilerIdDetection.cmake b/share/cmake-3.18/Modules/CMakeCompilerIdDetection.cmake deleted file mode 100644 index acd15df..0000000 --- a/share/cmake-3.18/Modules/CMakeCompilerIdDetection.cmake +++ /dev/null
@@ -1,151 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -function(_readFile file) - include(${file}) - get_filename_component(name ${file} NAME_WE) - string(REGEX REPLACE "-.*" "" CompilerId ${name}) - set(_compiler_id_version_compute_${CompilerId} ${_compiler_id_version_compute} PARENT_SCOPE) - set(_compiler_id_simulate_${CompilerId} ${_compiler_id_simulate} PARENT_SCOPE) - set(_compiler_id_pp_test_${CompilerId} ${_compiler_id_pp_test} PARENT_SCOPE) -endfunction() - -function(compiler_id_detection outvar lang) - - if (NOT lang STREQUAL Fortran AND NOT lang STREQUAL CSharp) - file(GLOB lang_files - "${CMAKE_ROOT}/Modules/Compiler/*-DetermineCompiler.cmake") - set(nonlang CXX) - if (lang STREQUAL CXX) - set(nonlang C) - endif() - - file(GLOB nonlang_files - "${CMAKE_ROOT}/Modules/Compiler/*-${nonlang}-DetermineCompiler.cmake") - list(REMOVE_ITEM lang_files ${nonlang_files}) - endif() - - set(files ${lang_files}) - if (files) - foreach(file ${files}) - _readFile(${file}) - endforeach() - - set(options ID_STRING VERSION_STRINGS ID_DEFINE PLATFORM_DEFAULT_COMPILER) - set(oneValueArgs PREFIX) - cmake_parse_arguments(CID "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN}) - if (CID_UNPARSED_ARGUMENTS) - message(FATAL_ERROR "Unrecognized arguments: \"${CID_UNPARSED_ARGUMENTS}\"") - endif() - - # Order is relevant here. For example, compilers which pretend to be - # GCC must appear before the actual GCC. - if (lang STREQUAL CXX) - list(APPEND ordered_compilers - Comeau - ) - endif() - list(APPEND ordered_compilers - Intel - PathScale - Embarcadero - Borland - Watcom - OpenWatcom - SunPro - HP - Compaq - zOS - XLClang - XL - VisualAge - PGI - Cray - TI - Fujitsu - GHS - ) - if (lang STREQUAL C) - list(APPEND ordered_compilers - TinyCC - Bruce - ) - endif() - list(APPEND ordered_compilers - SCO - ARMCC - AppleClang - ARMClang - Clang - GNU - MSVC - ADSP - IAR - ) - if (lang STREQUAL C) - list(APPEND ordered_compilers - SDCC - ) - endif() - - if(lang STREQUAL CUDA) - set(ordered_compilers NVIDIA Clang) - endif() - - if(CID_ID_DEFINE) - foreach(Id ${ordered_compilers}) - string(APPEND CMAKE_${lang}_COMPILER_ID_CONTENT "# define ${CID_PREFIX}COMPILER_IS_${Id} 0\n") - endforeach() - # Hard-code definitions for compilers that are no longer supported. - string(APPEND CMAKE_${lang}_COMPILER_ID_CONTENT "# define ${CID_PREFIX}COMPILER_IS_MIPSpro 0\n") - endif() - - set(pp_if "#if") - if (CID_VERSION_STRINGS) - string(APPEND CMAKE_${lang}_COMPILER_ID_CONTENT "\n/* Version number components: V=Version, R=Revision, P=Patch - Version date components: YYYY=Year, MM=Month, DD=Day */\n") - endif() - - foreach(Id ${ordered_compilers}) - if (NOT _compiler_id_pp_test_${Id}) - message(FATAL_ERROR "No preprocessor test for \"${Id}\"") - endif() - set(id_content "${pp_if} ${_compiler_id_pp_test_${Id}}\n") - if (CID_ID_STRING) - set(PREFIX ${CID_PREFIX}) - string(CONFIGURE "${_compiler_id_simulate_${Id}}" SIMULATE_BLOCK @ONLY) - string(APPEND id_content "# define ${CID_PREFIX}COMPILER_ID \"${Id}\"${SIMULATE_BLOCK}") - endif() - if (CID_ID_DEFINE) - string(APPEND id_content "# undef ${CID_PREFIX}COMPILER_IS_${Id}\n") - string(APPEND id_content "# define ${CID_PREFIX}COMPILER_IS_${Id} 1\n") - endif() - if (CID_VERSION_STRINGS) - set(PREFIX ${CID_PREFIX}) - set(MACRO_DEC DEC) - set(MACRO_HEX HEX) - string(CONFIGURE "${_compiler_id_version_compute_${Id}}" VERSION_BLOCK @ONLY) - string(APPEND id_content "${VERSION_BLOCK}\n") - endif() - string(APPEND CMAKE_${lang}_COMPILER_ID_CONTENT "\n${id_content}") - set(pp_if "#elif") - endforeach() - - if (CID_PLATFORM_DEFAULT_COMPILER) - set(platform_compiler_detection " -/* These compilers are either not known or too old to define an - identification macro. Try to identify the platform and guess that - it is the native compiler. */ -#elif defined(__hpux) || defined(__hpua) -# define ${CID_PREFIX}COMPILER_ID \"HP\" - -#else /* unknown compiler */ -# define ${CID_PREFIX}COMPILER_ID \"\"") - endif() - - string(APPEND CMAKE_${lang}_COMPILER_ID_CONTENT "\n${platform_compiler_detection}\n#endif") - endif() - - set(${outvar} ${CMAKE_${lang}_COMPILER_ID_CONTENT} PARENT_SCOPE) -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeDependentOption.cmake b/share/cmake-3.18/Modules/CMakeDependentOption.cmake deleted file mode 100644 index 99d5070..0000000 --- a/share/cmake-3.18/Modules/CMakeDependentOption.cmake +++ /dev/null
@@ -1,51 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CMakeDependentOption --------------------- - -Macro to provide an option dependent on other options. - -This macro presents an option to the user only if a set of other -conditions are true. When the option is not presented a default value -is used, but any value set by the user is preserved for when the -option is presented again. Example invocation: - -.. code-block:: cmake - - CMAKE_DEPENDENT_OPTION(USE_FOO "Use Foo" ON - "USE_BAR;NOT USE_ZOT" OFF) - -If USE_BAR is true and USE_ZOT is false, this provides an option -called USE_FOO that defaults to ON. Otherwise, it sets USE_FOO to -OFF. If the status of USE_BAR or USE_ZOT ever changes, any value for -the USE_FOO option is saved so that when the option is re-enabled it -retains its old value. Each element in the fourth parameter is -evaluated as an if-condition, so :ref:`Condition Syntax` can be used. -#]=======================================================================] - -macro(CMAKE_DEPENDENT_OPTION option doc default depends force) - if(${option}_ISSET MATCHES "^${option}_ISSET$") - set(${option}_AVAILABLE 1) - foreach(d ${depends}) - string(REGEX REPLACE " +" ";" CMAKE_DEPENDENT_OPTION_DEP "${d}") - if(${CMAKE_DEPENDENT_OPTION_DEP}) - else() - set(${option}_AVAILABLE 0) - endif() - endforeach() - if(${option}_AVAILABLE) - option(${option} "${doc}" "${default}") - set(${option} "${${option}}" CACHE BOOL "${doc}" FORCE) - else() - if(${option} MATCHES "^${option}$") - else() - set(${option} "${${option}}" CACHE INTERNAL "${doc}") - endif() - set(${option} ${force}) - endif() - else() - set(${option} "${${option}_ISSET}") - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineASMCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineASMCompiler.cmake deleted file mode 100644 index bc8b86b..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineASMCompiler.cmake +++ /dev/null
@@ -1,253 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for ASM programs - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -if(NOT CMAKE_ASM${ASM_DIALECT}_COMPILER) - # prefer the environment variable ASM - if(NOT $ENV{ASM${ASM_DIALECT}} STREQUAL "") - get_filename_component(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT $ENV{ASM${ASM_DIALECT}} PROGRAM PROGRAM_ARGS CMAKE_ASM${ASM_DIALECT}_FLAGS_ENV_INIT) - if(CMAKE_ASM${ASM_DIALECT}_FLAGS_ENV_INIT) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ARG1 "${CMAKE_ASM${ASM_DIALECT}_FLAGS_ENV_INIT}" CACHE STRING "First argument to ASM${ASM_DIALECT} compiler") - endif() - if(NOT EXISTS ${CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable ASM${ASM_DIALECT}:\n$ENV{ASM${ASM_DIALECT}}.") - endif() - endif() - - # finally list compilers to try - if("ASM${ASM_DIALECT}" STREQUAL "ASM") # the generic assembler support - if(NOT CMAKE_ASM_COMPILER_INIT) - if(CMAKE_C_COMPILER) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_LIST ${CMAKE_C_COMPILER}) - elseif(CMAKE_CXX_COMPILER) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_LIST ${CMAKE_CXX_COMPILER}) - else() - # List all default C and CXX compilers - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_LIST - ${_CMAKE_TOOLCHAIN_PREFIX}cc ${_CMAKE_TOOLCHAIN_PREFIX}gcc cl bcc xlc - CC ${_CMAKE_TOOLCHAIN_PREFIX}c++ ${_CMAKE_TOOLCHAIN_PREFIX}g++ aCC cl bcc xlC) - endif() - endif() - else() # some specific assembler "dialect" - if(NOT CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT AND NOT CMAKE_ASM${ASM_DIALECT}_COMPILER_LIST) - message(FATAL_ERROR "CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT or CMAKE_ASM${ASM_DIALECT}_COMPILER_LIST must be preset !") - endif() - endif() - - # Find the compiler. - _cmake_find_compiler(ASM${ASM_DIALECT}) - -else() - _cmake_find_compiler_path(ASM${ASM_DIALECT}) -endif() -mark_as_advanced(CMAKE_ASM${ASM_DIALECT}_COMPILER) - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_ASM${ASM_DIALECT}_COMPILER}" PATH) -endif () - - -if(NOT CMAKE_ASM${ASM_DIALECT}_COMPILER_ID) - - # Table of per-vendor compiler id flags with expected output. - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS GNU ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_GNU "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_GNU "(GNU assembler)|(GCC)|(Free Software Foundation)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS Clang ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_Clang "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_Clang "(clang version)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS AppleClang ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_AppleClang "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_AppleClang "(Apple LLVM version)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS ARMClang ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_ARMClang "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_ARMClang "armclang") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS HP ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_HP "-V") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_HP "HP C") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS Intel ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_Intel "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_Intel "(ICC)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS SunPro ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_SunPro "-V") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_SunPro "Sun C") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS XL ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_XL "-qversion") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_XL "XL C") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS MSVC ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_MSVC "-?") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_MSVC "Microsoft") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS TI ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_TI "-h") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_TI "Texas Instruments") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS IAR) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_IAR ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_IAR "IAR Assembler") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS ARMCC) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_ARMCC ) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_ARMCC "(ARM Compiler)|(ARM Assembler)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS NASM) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_NASM "-v") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_NASM "(NASM version)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS YASM) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_YASM "--version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_YASM "(yasm)") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS ADSP) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_ADSP "-version") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_ADSP "Analog Devices") - - list(APPEND CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDORS QCC) - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_FLAGS_QCC "-V") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_REGEX_QCC "gcc_nto") - - include(CMakeDetermineCompilerId) - set(userflags) - CMAKE_DETERMINE_COMPILER_ID_VENDOR(ASM${ASM_DIALECT} "${userflags}") - if("x${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}" STREQUAL "xIAR") - # primary necessary to detect architecture, so the right archiver and linker can be picked - # eg. "IAR Assembler V8.10.1.12857/W32 for ARM" or "IAR Assembler V4.11.1.4666 for Renesas RX" - # Cut out identification first, newline handling is a pain - string(REGEX MATCH "IAR Assembler[^\r\n]*" _compileid "${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_OUTPUT}") - if("${_compileid}" MATCHES "V([0-9]+\\.[0-9]+\\.[0-9]+)") - set(CMAKE_ASM${ASM_DIALECT}_COMPILER_VERSION ${CMAKE_MATCH_1}) - endif() - string(REGEX MATCHALL "([A-Za-z0-9-]+)" _all_compileid_matches "${_compileid}") - if(_all_compileid_matches) - list(GET _all_compileid_matches "-1" CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID) - endif() - endif() - - _cmake_find_compiler_sysroot(ASM${ASM_DIALECT}) - - unset(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_OUTPUT) - unset(_all_compileid_matches) - unset(_compileid) -endif() - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID) - if(CMAKE_ASM${ASM_DIALECT}_COMPILER_VERSION) - set(_version " ${CMAKE_ASM${ASM_DIALECT}_COMPILER_VERSION}") - else() - set(_version "") - endif() - if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID AND "x${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}" STREQUAL "xIAR") - set(_archid " ${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}") - else() - set(_archid "") - endif() - message(STATUS "The ASM${ASM_DIALECT} compiler identification is ${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}${_archid}${_version}") - unset(_archid) - unset(_version) -else() - message(STATUS "The ASM${ASM_DIALECT} compiler identification is unknown") -endif() - -# If we have a gas/as cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-gas, arm-elf-gas or i586-mingw32msvc-gas , optionally -# with a 3-component version number at the end -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gas.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - get_filename_component(COMPILER_BASENAME "${CMAKE_ASM${ASM_DIALECT}_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)g?as(-[0-9]+\\.[0-9]+\\.[0-9]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () -endif () - -# Now try the C compiler regexp: -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - if (COMPILER_BASENAME MATCHES "^(.+-)g?cc(-[0-9]+\\.[0-9]+\\.[0-9]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () -endif () - -# Finally try the CXX compiler regexp: -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - if (COMPILER_BASENAME MATCHES "^(.+-)[gc]\\+\\+(-[0-9]+\\.[0-9]+\\.[0-9]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () -endif () - - -set(_CMAKE_PROCESSING_LANGUAGE "ASM") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ENV_VAR "ASM${ASM_DIALECT}") - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER) - message(STATUS "Found assembler: ${CMAKE_ASM${ASM_DIALECT}_COMPILER}") -else() - message(STATUS "Didn't find assembler") -endif() - -foreach(_var - COMPILER - COMPILER_ID - COMPILER_ARG1 - COMPILER_ENV_VAR - COMPILER_AR - COMPILER_RANLIB - COMPILER_VERSION - ) - set(_CMAKE_ASM_${_var} "${CMAKE_ASM${ASM_DIALECT}_${_var}}") -endforeach() - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_SYSROOT) - string(CONCAT _SET_CMAKE_ASM_COMPILER_SYSROOT - "set(CMAKE_ASM${ASM_DIALECT}_COMPILER_SYSROOT \"${CMAKE_ASM${ASM_DIALECT}_COMPILER_SYSROOT}\")\n" - "set(CMAKE_COMPILER_SYSROOT \"${CMAKE_ASM${ASM_DIALECT}_COMPILER_SYSROOT}\")") -else() - set(_SET_CMAKE_ASM_COMPILER_SYSROOT "") -endif() - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_MATCH) - set(_SET_CMAKE_ASM_COMPILER_ID_VENDOR_MATCH - "set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_MATCH [==[${CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_MATCH}]==])") -else() - set(_SET_CMAKE_ASM_COMPILER_ID_VENDOR_MATCH "") -endif() - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_ASM_COMPILER_ARCHITECTURE_ID - "set(CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID ${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_ASM_COMPILER_ARCHITECTURE_ID "") -endif() - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeASMCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeASM${ASM_DIALECT}Compiler.cmake @ONLY) - -foreach(_var - COMPILER - COMPILER_ID - COMPILER_ARG1 - COMPILER_ENV_VAR - COMPILER_AR - COMPILER_RANLIB - COMPILER_VERSION - ) - unset(_CMAKE_ASM_${_var}) -endforeach()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineCCompiler.cmake deleted file mode 100644 index 86683d1..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCCompiler.cmake +++ /dev/null
@@ -1,226 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for C programs -# NOTE, a generator may set CMAKE_C_COMPILER before -# loading this file to force a compiler. -# use environment variable CC first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_CC which can be defined by a generator -# as a default compiler -# If the internal cmake variable _CMAKE_TOOLCHAIN_PREFIX is set, this is used -# as prefix for the tools (e.g. arm-elf-gcc, arm-elf-ar etc.). This works -# currently with the GNU crosscompilers. -# -# Sets the following variables: -# CMAKE_C_COMPILER -# CMAKE_AR -# CMAKE_RANLIB -# CMAKE_COMPILER_IS_GNUCC -# -# If not already set before, it also sets -# _CMAKE_TOOLCHAIN_PREFIX - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -# Load system-specific compiler preferences for this language. -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-C OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-C OPTIONAL) -if(NOT CMAKE_C_COMPILER_NAMES) - set(CMAKE_C_COMPILER_NAMES cc) -endif() - -if(${CMAKE_GENERATOR} MATCHES "Visual Studio") -elseif("${CMAKE_GENERATOR}" MATCHES "Green Hills MULTI") -elseif("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(CMAKE_C_COMPILER_XCODE_TYPE sourcecode.c.c) - _cmake_find_compiler_path(C) -else() - if(NOT CMAKE_C_COMPILER) - set(CMAKE_C_COMPILER_INIT NOTFOUND) - - # prefer the environment variable CC - if(NOT $ENV{CC} STREQUAL "") - get_filename_component(CMAKE_C_COMPILER_INIT $ENV{CC} PROGRAM PROGRAM_ARGS CMAKE_C_FLAGS_ENV_INIT) - if(CMAKE_C_FLAGS_ENV_INIT) - set(CMAKE_C_COMPILER_ARG1 "${CMAKE_C_FLAGS_ENV_INIT}" CACHE STRING "First argument to C compiler") - endif() - if(NOT EXISTS ${CMAKE_C_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable CC:\n$ENV{CC}.") - endif() - endif() - - # next try prefer the compiler specified by the generator - if(CMAKE_GENERATOR_CC) - if(NOT CMAKE_C_COMPILER_INIT) - set(CMAKE_C_COMPILER_INIT ${CMAKE_GENERATOR_CC}) - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_C_COMPILER_INIT) - set(CMAKE_C_COMPILER_LIST ${_CMAKE_TOOLCHAIN_PREFIX}cc ${_CMAKE_TOOLCHAIN_PREFIX}gcc cl bcc xlc clang) - endif() - - _cmake_find_compiler(C) - - else() - _cmake_find_compiler_path(C) - endif() - mark_as_advanced(CMAKE_C_COMPILER) - - # Each entry in this list is a set of extra flags to try - # adding to the compile line to see if it helps produce - # a valid identification file. - set(CMAKE_C_COMPILER_ID_TEST_FLAGS_FIRST) - set(CMAKE_C_COMPILER_ID_TEST_FLAGS - # Try compiling to an object file only. - "-c" - - # Try enabling ANSI mode on HP. - "-Aa" - - # Try compiling K&R-compatible code (needed by Bruce C Compiler). - "-D__CLASSIC_C__" - - # ARMClang need target options - "--target=arm-arm-none-eabi -mcpu=cortex-m3" - ) -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_C_COMPILER_ID_RUN) - set(CMAKE_C_COMPILER_ID_RUN 1) - - # Try to identify the compiler. - set(CMAKE_C_COMPILER_ID) - set(CMAKE_C_PLATFORM_ID) - file(READ ${CMAKE_ROOT}/Modules/CMakePlatformId.h.in - CMAKE_C_COMPILER_ID_PLATFORM_CONTENT) - - # The IAR compiler produces weird output. - # See https://gitlab.kitware.com/cmake/cmake/-/issues/10176#note_153591 - list(APPEND CMAKE_C_COMPILER_ID_VENDORS IAR) - set(CMAKE_C_COMPILER_ID_VENDOR_FLAGS_IAR ) - set(CMAKE_C_COMPILER_ID_VENDOR_REGEX_IAR "IAR .+ Compiler") - - # Match the link line from xcodebuild output of the form - # Ld ... - # ... - # /path/to/cc ...CompilerIdC/... - # to extract the compiler front-end for the language. - set(CMAKE_C_COMPILER_ID_TOOL_MATCH_REGEX "\nLd[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]*-o[^\r\n]*CompilerIdC/(\\./)?(CompilerIdC.(framework|xctest)/)?CompilerIdC[ \t\n\\\"]") - set(CMAKE_C_COMPILER_ID_TOOL_MATCH_INDEX 2) - - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(C CFLAGS CMakeCCompilerId.c) - - _cmake_find_compiler_sysroot(C) - - # Set old compiler and platform id variables. - if(CMAKE_C_COMPILER_ID STREQUAL "GNU") - set(CMAKE_COMPILER_IS_GNUCC 1) - endif() - if(CMAKE_C_PLATFORM_ID MATCHES "MinGW") - set(CMAKE_COMPILER_IS_MINGW 1) - elseif(CMAKE_C_PLATFORM_ID MATCHES "Cygwin") - set(CMAKE_COMPILER_IS_CYGWIN 1) - endif() -else() - if(NOT DEFINED CMAKE_C_COMPILER_FRONTEND_VARIANT) - # Some toolchain files set our internal CMAKE_C_COMPILER_ID_RUN - # variable but are not aware of CMAKE_C_COMPILER_FRONTEND_VARIANT. - # They pre-date our support for the GNU-like variant targeting the - # MSVC ABI so we do not consider that here. - if(CMAKE_C_COMPILER_ID STREQUAL "Clang") - if("x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_C_COMPILER_FRONTEND_VARIANT "MSVC") - else() - set(CMAKE_C_COMPILER_FRONTEND_VARIANT "GNU") - endif() - else() - set(CMAKE_C_COMPILER_FRONTEND_VARIANT "") - endif() - endif() -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_C_COMPILER}" PATH) -endif () - -# If we have a gcc cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-gcc, arm-elf-gcc or i586-mingw32msvc-gcc, optionally -# with a 3-component version number at the end (e.g. arm-eabi-gcc-4.5.2). -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gcc.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - - if(CMAKE_C_COMPILER_ID MATCHES "GNU|Clang|QCC") - get_filename_component(COMPILER_BASENAME "${CMAKE_C_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)(clang|g?cc)(-[0-9]+(\\.[0-9]+)*)?(-[^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - set(_CMAKE_COMPILER_SUFFIX ${CMAKE_MATCH_5}) - elseif(CMAKE_C_COMPILER_ID MATCHES "Clang") - if(CMAKE_C_COMPILER_TARGET) - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_C_COMPILER_TARGET}-) - endif() - elseif(COMPILER_BASENAME MATCHES "qcc(\\.exe)?$") - if(CMAKE_C_COMPILER_TARGET MATCHES "gcc_nto([a-z0-9]+_[0-9]+|[^_le]+)(le)?") - set(_CMAKE_TOOLCHAIN_PREFIX nto${CMAKE_MATCH_1}-) - endif() - endif () - - # if "llvm-" is part of the prefix, remove it, since llvm doesn't have its own binutils - # but uses the regular ar, objcopy, etc. (instead of llvm-objcopy etc.) - if ("${_CMAKE_TOOLCHAIN_PREFIX}" MATCHES "(.+-)?llvm-$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - elseif(CMAKE_C_COMPILER_ID MATCHES "TI") - # TI compilers are named e.g. cl6x, cl470 or armcl.exe - get_filename_component(COMPILER_BASENAME "${CMAKE_C_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+)?cl([^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX "${CMAKE_MATCH_1}") - set(_CMAKE_TOOLCHAIN_SUFFIX "${CMAKE_MATCH_2}") - endif () - endif() - -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "C") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_C_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(CMAKE_C_COMPILER_SYSROOT) - string(CONCAT _SET_CMAKE_C_COMPILER_SYSROOT - "set(CMAKE_C_COMPILER_SYSROOT \"${CMAKE_C_COMPILER_SYSROOT}\")\n" - "set(CMAKE_COMPILER_SYSROOT \"${CMAKE_C_COMPILER_SYSROOT}\")") -else() - set(_SET_CMAKE_C_COMPILER_SYSROOT "") -endif() - -if(CMAKE_C_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_C_COMPILER_ARCHITECTURE_ID - "set(CMAKE_C_COMPILER_ARCHITECTURE_ID ${CMAKE_C_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_C_COMPILER_ARCHITECTURE_ID "") -endif() - -if(MSVC_C_ARCHITECTURE_ID) - set(SET_MSVC_C_ARCHITECTURE_ID - "set(MSVC_C_ARCHITECTURE_ID ${MSVC_C_ARCHITECTURE_ID})") -endif() - -if(CMAKE_C_XCODE_ARCHS) - set(SET_CMAKE_XCODE_ARCHS - "set(CMAKE_XCODE_ARCHS \"${CMAKE_C_XCODE_ARCHS}\")") -endif() - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeCCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCCompiler.cmake - @ONLY - ) -set(CMAKE_C_COMPILER_ENV_VAR "CC")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCUDACompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineCUDACompiler.cmake deleted file mode 100644 index fa497cd..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCUDACompiler.cmake +++ /dev/null
@@ -1,575 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) -include(${CMAKE_ROOT}/Modules/CMakeParseImplicitLinkInfo.cmake) - -if( NOT ( ("${CMAKE_GENERATOR}" MATCHES "Make") OR - ("${CMAKE_GENERATOR}" MATCHES "Ninja") OR - ("${CMAKE_GENERATOR}" MATCHES "Visual Studio (1|[9][0-9])") ) ) - message(FATAL_ERROR "CUDA language not currently supported by \"${CMAKE_GENERATOR}\" generator") -endif() - -if(${CMAKE_GENERATOR} MATCHES "Visual Studio") -else() - if(NOT CMAKE_CUDA_COMPILER) - set(CMAKE_CUDA_COMPILER_INIT NOTFOUND) - - # prefer the environment variable CUDACXX - if(NOT $ENV{CUDACXX} STREQUAL "") - get_filename_component(CMAKE_CUDA_COMPILER_INIT $ENV{CUDACXX} PROGRAM PROGRAM_ARGS CMAKE_CUDA_FLAGS_ENV_INIT) - if(CMAKE_CUDA_FLAGS_ENV_INIT) - set(CMAKE_CUDA_COMPILER_ARG1 "${CMAKE_CUDA_FLAGS_ENV_INIT}" CACHE STRING "First argument to CXX compiler") - endif() - if(NOT EXISTS ${CMAKE_CUDA_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable CUDACXX:\n$ENV{CUDACXX}.\n${CMAKE_CUDA_COMPILER_INIT}") - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_CUDA_COMPILER_INIT) - set(CMAKE_CUDA_COMPILER_LIST nvcc) - endif() - - _cmake_find_compiler(CUDA) - else() - _cmake_find_compiler_path(CUDA) - endif() - - mark_as_advanced(CMAKE_CUDA_COMPILER) -endif() - -#Allow the user to specify a host compiler -if(NOT $ENV{CUDAHOSTCXX} STREQUAL "") - get_filename_component(CMAKE_CUDA_HOST_COMPILER $ENV{CUDAHOSTCXX} PROGRAM) - if(NOT EXISTS ${CMAKE_CUDA_HOST_COMPILER}) - message(FATAL_ERROR "Could not find compiler set in environment variable CUDAHOSTCXX:\n$ENV{CUDAHOSTCXX}.\n${CMAKE_CUDA_HOST_COMPILER}") - endif() -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_CUDA_COMPILER_ID_RUN) - set(CMAKE_CUDA_COMPILER_ID_RUN 1) - - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - - if(${CMAKE_GENERATOR} MATCHES "Visual Studio") - # We will not know CMAKE_CUDA_COMPILER until the main compiler id step - # below extracts it, but we do know that the compiler id will be NVIDIA. - set(CMAKE_CUDA_COMPILER_ID "NVIDIA") - else() - # We determine the vendor to help with find the toolkit and use the right flags for detection right away. - # The main compiler identification is still needed below to extract other information. - list(APPEND CMAKE_CUDA_COMPILER_ID_VENDORS NVIDIA Clang) - set(CMAKE_CUDA_COMPILER_ID_VENDOR_REGEX_NVIDIA "nvcc: NVIDIA \\(R\\) Cuda compiler driver") - set(CMAKE_CUDA_COMPILER_ID_VENDOR_REGEX_Clang "(clang version)") - CMAKE_DETERMINE_COMPILER_ID_VENDOR(CUDA "--version") - - # Find the CUDA toolkit. We store the CMAKE_CUDA_COMPILER_TOOLKIT_ROOT and CMAKE_CUDA_COMPILER_LIBRARY_ROOT - # in CMakeCUDACompiler.cmake, so FindCUDAToolkit can avoid searching on future runs and the toolkit stays the same. - # This is very similar to FindCUDAToolkit, but somewhat simplified since we can issue fatal errors - # if we fail to find things we need and we don't need to account for searching the libraries. - - # For NVCC we can easily deduce the SDK binary directory from the compiler path. - if(CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - set(_CUDA_NVCC_EXECUTABLE "${CMAKE_CUDA_COMPILER}") - else() - # Search using CUDAToolkit_ROOT and then CUDA_PATH for equivalence with FindCUDAToolkit. - # In FindCUDAToolkit CUDAToolkit_ROOT is searched automatically due to being in a find_package(). - # First we search candidate non-default paths to give them priority. - find_program(_CUDA_NVCC_EXECUTABLE - NAMES nvcc nvcc.exe - PATHS ${CUDAToolkit_ROOT} - ENV CUDAToolkit_ROOT - ENV CUDA_PATH - PATH_SUFFIXES bin - NO_DEFAULT_PATH - ) - - # If we didn't find NVCC, then try the default paths. - find_program(_CUDA_NVCC_EXECUTABLE - NAMES nvcc nvcc.exe - PATH_SUFFIXES bin - ) - - # If the user specified CUDAToolkit_ROOT but nvcc could not be found, this is an error. - if(NOT _CUDA_NVCC_EXECUTABLE AND (DEFINED CUDAToolkit_ROOT OR DEFINED ENV{CUDAToolkit_ROOT})) - set(fail_base "Could not find nvcc executable in path specified by") - - if(DEFINED CUDAToolkit_ROOT) - message(FATAL_ERROR "${fail_base} CUDAToolkit_ROOT=${CUDAToolkit_ROOT}") - elseif(DEFINED ENV{CUDAToolkit_ROOT}) - message(FATAL_ERROR "${fail_base} environment variable CUDAToolkit_ROOT=$ENV{CUDAToolkit_ROOT}") - endif() - endif() - - # CUDAToolkit_ROOT cmake/env variable not specified, try platform defaults. - # - # - Linux: /usr/local/cuda-X.Y - # - macOS: /Developer/NVIDIA/CUDA-X.Y - # - Windows: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vX.Y - # - # We will also search the default symlink location /usr/local/cuda first since - # if CUDAToolkit_ROOT is not specified, it is assumed that the symlinked - # directory is the desired location. - if(NOT _CUDA_NVCC_EXECUTABLE) - if(UNIX) - if(NOT APPLE) - set(platform_base "/usr/local/cuda-") - else() - set(platform_base "/Developer/NVIDIA/CUDA-") - endif() - else() - set(platform_base "C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v") - endif() - - # Build out a descending list of possible cuda installations, e.g. - file(GLOB possible_paths "${platform_base}*") - # Iterate the glob results and create a descending list. - set(versions) - foreach(p ${possible_paths}) - # Extract version number from end of string - string(REGEX MATCH "[0-9][0-9]?\\.[0-9]$" p_version ${p}) - if(IS_DIRECTORY ${p} AND p_version) - list(APPEND versions ${p_version}) - endif() - endforeach() - - # Sort numerically in descending order, so we try the newest versions first. - list(SORT versions COMPARE NATURAL ORDER DESCENDING) - - # With a descending list of versions, populate possible paths to search. - set(search_paths) - foreach(v ${versions}) - list(APPEND search_paths "${platform_base}${v}") - endforeach() - - # Force the global default /usr/local/cuda to the front on Unix. - if(UNIX) - list(INSERT search_paths 0 "/usr/local/cuda") - endif() - - # Now search for nvcc again using the platform default search paths. - find_program(_CUDA_NVCC_EXECUTABLE - NAMES nvcc nvcc.exe - PATHS ${search_paths} - PATH_SUFFIXES bin - ) - - # We are done with these variables now, cleanup. - unset(platform_base) - unset(possible_paths) - unset(versions) - unset(search_paths) - - if(NOT _CUDA_NVCC_EXECUTABLE) - message(FATAL_ERROR "Could not find nvcc, please set CUDAToolkit_ROOT.") - endif() - endif() - endif() - - get_filename_component(CMAKE_CUDA_COMPILER_TOOLKIT_ROOT "${_CUDA_NVCC_EXECUTABLE}" DIRECTORY) - get_filename_component(CMAKE_CUDA_COMPILER_TOOLKIT_ROOT "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}" DIRECTORY) - - # CMAKE_CUDA_COMPILER_LIBRARY_ROOT contains the device library and version file. - # In a non-scattered installation this is equivalent to CMAKE_CUDA_COMPILER_TOOLKIT_ROOT. - # We first check for a non-scattered installation to prefer it over a scattered installation. - if(EXISTS "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}/version.txt") - set(CMAKE_CUDA_COMPILER_LIBRARY_ROOT "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}") - elseif(CMAKE_SYSROOT_LINK AND EXISTS "${CMAKE_SYSROOT_LINK}/usr/lib/cuda/version.txt") - set(CMAKE_CUDA_COMPILER_LIBRARY_ROOT "${CMAKE_SYSROOT_LINK}/usr/lib/cuda") - elseif(EXISTS "${CMAKE_SYSROOT}/usr/lib/cuda/version.txt") - set(CMAKE_CUDA_COMPILER_LIBRARY_ROOT "${CMAKE_SYSROOT}/usr/lib/cuda") - endif() - endif() - - set(CMAKE_CUDA_COMPILER_ID_FLAGS_ALWAYS "-v") - - if(CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - set(nvcc_test_flags "--keep --keep-dir tmp") - if(CMAKE_CUDA_HOST_COMPILER) - string(APPEND nvcc_test_flags " -ccbin=\"${CMAKE_CUDA_HOST_COMPILER}\"") - endif() - elseif(CMAKE_CUDA_COMPILER_ID STREQUAL "Clang") - if(WIN32) - message(FATAL_ERROR "Clang with CUDA is not yet supported on Windows. See CMake issue #20776.") - endif() - - set(clang_test_flags "--cuda-path=\"${CMAKE_CUDA_COMPILER_LIBRARY_ROOT}\"") - if(CMAKE_CROSSCOMPILING) - # Need to pass the host target and include directories if we're crosscompiling. - string(APPEND clang_test_flags " --sysroot=\"${CMAKE_SYSROOT}\" --target=${CMAKE_CUDA_COMPILER_TARGET}") - endif() - endif() - - # First try with the user-specified architectures. - if(CMAKE_CUDA_ARCHITECTURES) - set(clang_archs "${clang_test_flags}") - set(nvcc_archs "${nvcc_test_flags}") - - foreach(arch ${CMAKE_CUDA_ARCHITECTURES}) - # Strip specifiers as PTX vs binary doesn't matter. - string(REGEX MATCH "[0-9]+" arch_name "${arch}") - string(APPEND clang_archs " --cuda-gpu-arch=sm_${arch_name}") - string(APPEND nvcc_archs " -gencode=arch=compute_${arch_name},code=sm_${arch_name}") - list(APPEND tested_architectures "${arch_name}") - endforeach() - - list(APPEND CMAKE_CUDA_COMPILER_ID_TEST_FLAGS_FIRST "${clang_archs}") - list(APPEND CMAKE_CUDA_COMPILER_ID_TEST_FLAGS_FIRST "${nvcc_archs}") - endif() - - # Fallback default NVCC flags. - list(APPEND CMAKE_CUDA_COMPILER_ID_TEST_FLAGS_FIRST ${nvcc_test_flags}) - - # Clang doesn't automatically select an architecture supported by the SDK. - # Try in reverse order of deprecation with the most recent at front (i.e. the most likely to work for new setups). - foreach(arch "20" "30" "52") - list(APPEND CMAKE_CUDA_COMPILER_ID_TEST_FLAGS_FIRST "${clang_test_flags} --cuda-gpu-arch=sm_${arch}") - endforeach() - - # Finally also try the default. - list(APPEND CMAKE_CUDA_COMPILER_ID_TEST_FLAGS_FIRST "${clang_test_flags}") - - # We perform compiler identification for a second time to extract implicit linking info and host compiler for NVCC. - # We also use it to verify that CMAKE_CUDA_ARCHITECTURES and additionaly on Clang that CUDA toolkit path works. - # The latter could be done during compiler testing in the future to avoid doing this for Clang. - # We need to unset the compiler ID otherwise CMAKE_DETERMINE_COMPILER_ID() doesn't work. - set(CMAKE_CUDA_COMPILER_ID) - set(CMAKE_CUDA_PLATFORM_ID) - file(READ ${CMAKE_ROOT}/Modules/CMakePlatformId.h.in - CMAKE_CUDA_COMPILER_ID_PLATFORM_CONTENT) - - CMAKE_DETERMINE_COMPILER_ID(CUDA CUDAFLAGS CMakeCUDACompilerId.cu) - - if(${CMAKE_GENERATOR} MATCHES "Visual Studio") - # Now that we have the path to nvcc, we can compute the toolkit root. - get_filename_component(CMAKE_CUDA_COMPILER_TOOLKIT_ROOT "${CMAKE_CUDA_COMPILER}" DIRECTORY) - get_filename_component(CMAKE_CUDA_COMPILER_TOOLKIT_ROOT "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}" DIRECTORY) - set(CMAKE_CUDA_COMPILER_LIBRARY_ROOT "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}") - endif() - - _cmake_find_compiler_sysroot(CUDA) -endif() - -set(_CMAKE_PROCESSING_LANGUAGE "CUDA") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_CUDA_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(MSVC_CUDA_ARCHITECTURE_ID) - set(SET_MSVC_CUDA_ARCHITECTURE_ID - "set(MSVC_CUDA_ARCHITECTURE_ID ${MSVC_CUDA_ARCHITECTURE_ID})") -endif() - -if(${CMAKE_GENERATOR} MATCHES "Visual Studio") - set(CMAKE_CUDA_HOST_LINK_LAUNCHER "${CMAKE_LINKER}") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES "") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES "") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "") - - # We do not currently detect CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES but we - # do need to detect CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT from the compiler by - # looking at which cudart library exists in the implicit link libraries passed - # to the host linker. - if(CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT MATCHES "link\\.exe [^\n]*cudart_static\\.lib") - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "STATIC") - elseif(CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT MATCHES "link\\.exe [^\n]*cudart\\.lib") - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "SHARED") - else() - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "NONE") - endif() - set(_SET_CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT - "set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT \"${CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT}\")") -elseif(CMAKE_CUDA_COMPILER_ID STREQUAL "Clang") - if(NOT CMAKE_CUDA_ARCHITECTURES) - # Find the architecture that we successfully compiled using and set it as the default. - string(REGEX MATCH "-target-cpu sm_([0-9]+)" dont_care "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - set(detected_architecture "${CMAKE_MATCH_1}") - else() - string(REGEX MATCHALL "-target-cpu sm_([0-9]+)" target_cpus "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - - foreach(cpu ${target_cpus}) - string(REGEX MATCH "-target-cpu sm_([0-9]+)" dont_care "${cpu}") - list(APPEND architectures "${CMAKE_MATCH_1}") - endforeach() - endif() - - # Find target directory. Account for crosscompiling. - if(CMAKE_CROSSCOMPILING) - if(CMAKE_SYSTEM_PROCESSOR STREQUAL "armv7-a") - # Support for NVPACK - set(_CUDA_TARGET_NAME "armv7-linux-androideabi") - elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "arm") - set(_CUDA_TARGET_NAME "armv7-linux-gnueabihf") - elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "aarch64") - if(ANDROID_ARCH_NAME STREQUAL "arm64") - set(_CUDA_TARGET_NAME "aarch64-linux-androideabi") - else() - set(_CUDA_TARGET_NAME "aarch64-linux") - endif() - elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL "x86_64") - set(_CUDA_TARGET_NAME "x86_64-linux") - endif() - - if(EXISTS "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}/targets/${_CUDA_TARGET_NAME}") - set(_CUDA_TARGET_DIR "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}/targets/${_CUDA_TARGET_NAME}") - endif() - else() - set(_CUDA_TARGET_DIR "${CMAKE_CUDA_COMPILER_TOOLKIT_ROOT}") - endif() - - # We can't use find_library() yet at this point, so try a few guesses. - if(EXISTS "${_CUDA_TARGET_DIR}/lib64") - set(_CUDA_LIBRARY_DIR "${_CUDA_TARGET_DIR}/lib64") - elseif(EXISTS "${_CUDA_TARGET_DIR}/lib/x64") - set(_CUDA_LIBRARY_DIR "${_CUDA_TARGET_DIR}/lib/x64") - elseif(EXISTS "${_CUDA_TARGET_DIR}/lib") - set(_CUDA_LIBRARY_DIR "${_CUDA_TARGET_DIR}/lib") - else() - message(FATAL_ERROR "Unable to find _CUDA_LIBRARY_DIR based on _CUDA_TARGET_DIR=${_CUDA_TARGET_DIR}") - endif() - - # _CUDA_TARGET_DIR always points to the directory containing the include directory. - # On a scattered installation /usr, on a non-scattered something like /usr/local/cuda or /usr/local/cuda-10.2/targets/aarch64-linux. - if(EXISTS "${_CUDA_TARGET_DIR}/include/cuda_runtime.h") - set(_CUDA_INCLUDE_DIR "${_CUDA_TARGET_DIR}/include") - else() - message(FATAL_ERROR "Unable to find cuda_runtime.h in \"${_CUDA_TARGET_DIR}/include\" for _CUDA_INCLUDE_DIR.") - endif() - - # Clang does not add any CUDA SDK libraries or directories when invoking the host linker. - # Add the CUDA toolkit library directory ourselves so that linking works. - # The CUDA runtime libraries are handled elsewhere by CMAKE_CUDA_RUNTIME_LIBRARY. - set(CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES "${_CUDA_INCLUDE_DIR}") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES "${_CUDA_LIBRARY_DIR}") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES "") - set(CMAKE_CUDA_HOST_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "") -elseif(CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - set(_nvcc_log "") - string(REPLACE "\r" "" _nvcc_output_orig "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - if(_nvcc_output_orig MATCHES "#\\\$ +PATH= *([^\n]*)\n") - set(_nvcc_path "${CMAKE_MATCH_1}") - string(APPEND _nvcc_log " found 'PATH=' string: [${_nvcc_path}]\n") - string(REPLACE ":" ";" _nvcc_path "${_nvcc_path}") - else() - set(_nvcc_path "") - string(REPLACE "\n" "\n " _nvcc_output_log "\n${_nvcc_output_orig}") - string(APPEND _nvcc_log " no 'PATH=' string found in nvcc output:${_nvcc_output_log}\n") - endif() - if(_nvcc_output_orig MATCHES "#\\\$ +LIBRARIES= *([^\n]*)\n") - set(_nvcc_libraries "${CMAKE_MATCH_1}") - string(APPEND _nvcc_log " found 'LIBRARIES=' string: [${_nvcc_libraries}]\n") - else() - set(_nvcc_libraries "") - string(REPLACE "\n" "\n " _nvcc_output_log "\n${_nvcc_output_orig}") - string(APPEND _nvcc_log " no 'LIBRARIES=' string found in nvcc output:${_nvcc_output_log}\n") - endif() - - set(_nvcc_link_line "") - if(_nvcc_libraries) - # Remove variable assignments. - string(REGEX REPLACE "#\\\$ *[^= ]+=[^\n]*\n" "" _nvcc_output "${_nvcc_output_orig}") - # Encode [] characters that break list expansion. - string(REPLACE "[" "{==={" _nvcc_output "${_nvcc_output}") - string(REPLACE "]" "}===}" _nvcc_output "${_nvcc_output}") - # Split lines. - string(REGEX REPLACE "\n+(#\\\$ )?" ";" _nvcc_output "${_nvcc_output}") - foreach(line IN LISTS _nvcc_output) - set(_nvcc_output_line "${line}") - string(REPLACE "{==={" "[" _nvcc_output_line "${_nvcc_output_line}") - string(REPLACE "}===}" "]" _nvcc_output_line "${_nvcc_output_line}") - string(APPEND _nvcc_log " considering line: [${_nvcc_output_line}]\n") - if("${_nvcc_output_line}" MATCHES "^ *nvlink") - string(APPEND _nvcc_log " ignoring nvlink line\n") - elseif(_nvcc_libraries) - if("${_nvcc_output_line}" MATCHES "(@\"?tmp/a\\.exe\\.res\"?)") - set(_nvcc_link_res_arg "${CMAKE_MATCH_1}") - set(_nvcc_link_res "${CMAKE_PLATFORM_INFO_DIR}/CompilerIdCUDA/tmp/a.exe.res") - if(EXISTS "${_nvcc_link_res}") - file(READ "${_nvcc_link_res}" _nvcc_link_res_content) - string(REPLACE "${_nvcc_link_res_arg}" "${_nvcc_link_res_content}" _nvcc_output_line "${_nvcc_output_line}") - endif() - endif() - string(FIND "${_nvcc_output_line}" "${_nvcc_libraries}" _nvcc_libraries_pos) - if(NOT _nvcc_libraries_pos EQUAL -1) - set(_nvcc_link_line "${_nvcc_output_line}") - string(APPEND _nvcc_log " extracted link line: [${_nvcc_link_line}]\n") - endif() - endif() - endforeach() - endif() - - if(_nvcc_link_line) - if("x${CMAKE_CUDA_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CUDA_HOST_LINK_LAUNCHER "${CMAKE_LINKER}") - else() - #extract the compiler that is being used for linking - separate_arguments(_nvcc_link_line_args UNIX_COMMAND "${_nvcc_link_line}") - list(GET _nvcc_link_line_args 0 _nvcc_host_link_launcher) - if(IS_ABSOLUTE "${_nvcc_host_link_launcher}") - string(APPEND _nvcc_log " extracted link launcher absolute path: [${_nvcc_host_link_launcher}]\n") - set(CMAKE_CUDA_HOST_LINK_LAUNCHER "${_nvcc_host_link_launcher}") - else() - string(APPEND _nvcc_log " extracted link launcher name: [${_nvcc_host_link_launcher}]\n") - find_program(_nvcc_find_host_link_launcher - NAMES ${_nvcc_host_link_launcher} - PATHS ${_nvcc_path} NO_DEFAULT_PATH) - find_program(_nvcc_find_host_link_launcher - NAMES ${_nvcc_host_link_launcher}) - if(_nvcc_find_host_link_launcher) - string(APPEND _nvcc_log " found link launcher absolute path: [${_nvcc_find_host_link_launcher}]\n") - set(CMAKE_CUDA_HOST_LINK_LAUNCHER "${_nvcc_find_host_link_launcher}") - else() - string(APPEND _nvcc_log " could not find link launcher absolute path\n") - set(CMAKE_CUDA_HOST_LINK_LAUNCHER "${_nvcc_host_link_launcher}") - endif() - unset(_nvcc_find_host_link_launcher CACHE) - endif() - endif() - - #prefix the line with cuda-fake-ld so that implicit link info believes it is - #a link line - set(_nvcc_link_line "cuda-fake-ld ${_nvcc_link_line}") - CMAKE_PARSE_IMPLICIT_LINK_INFO("${_nvcc_link_line}" - CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES - CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES - CMAKE_CUDA_HOST_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES - log - "${CMAKE_CUDA_IMPLICIT_OBJECT_REGEX}") - - # Detect CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT from the compiler by looking at which - # cudart library exists in the implicit link libraries passed to the host linker. - # This is required when a project sets the cuda runtime library as part of the - # initial flags. - if(";${CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES};" MATCHES [[;cudart_static(\.lib)?;]]) - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "STATIC") - elseif(";${CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES};" MATCHES [[;cudart(\.lib)?;]]) - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "SHARED") - else() - set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "NONE") - endif() - set(_SET_CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT - "set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT \"${CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT}\")") - - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Parsed CUDA nvcc implicit link information from above output:\n${_nvcc_log}\n${log}\n\n") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Failed to parse CUDA nvcc implicit link information:\n${_nvcc_log}\n\n") - message(FATAL_ERROR "Failed to extract nvcc implicit link line.") - endif() -endif() - -# CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES is detected above as the list of -# libraries that the CUDA compiler implicitly passes to the host linker. -# CMake invokes the host linker directly and so needs to pass these libraries. -# We filter out those that should not be passed unconditionally both here -# and from CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES in CMakeTestCUDACompiler. -set(CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES_EXCLUDE - # The CUDA runtime libraries are controlled by CMAKE_CUDA_RUNTIME_LIBRARY. - cudart cudart.lib - cudart_static cudart_static.lib - cudadevrt cudadevrt.lib - - # Dependencies of the CUDA static runtime library on Linux hosts. - rt - pthread - dl - ) -list(REMOVE_ITEM CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES ${CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES_EXCLUDE}) - -if(CMAKE_CUDA_COMPILER_SYSROOT) - string(CONCAT _SET_CMAKE_CUDA_COMPILER_SYSROOT - "set(CMAKE_CUDA_COMPILER_SYSROOT \"${CMAKE_CUDA_COMPILER_SYSROOT}\")\n" - "set(CMAKE_COMPILER_SYSROOT \"${CMAKE_CUDA_COMPILER_SYSROOT}\")") -else() - set(_SET_CMAKE_CUDA_COMPILER_SYSROOT "") -endif() - -# Determine CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES -if(CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - set(CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES) - string(REPLACE "\r" "" _nvcc_output_orig "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - if(_nvcc_output_orig MATCHES "#\\\$ +INCLUDES= *([^\n]*)\n") - set(_nvcc_includes "${CMAKE_MATCH_1}") - string(APPEND _nvcc_log " found 'INCLUDES=' string: [${_nvcc_includes}]\n") - else() - set(_nvcc_includes "") - string(REPLACE "\n" "\n " _nvcc_output_log "\n${_nvcc_output_orig}") - string(APPEND _nvcc_log " no 'INCLUDES=' string found in nvcc output:${_nvcc_output_log}\n") - endif() - if(_nvcc_includes) - # across all operating system each include directory is prefixed with -I - separate_arguments(_nvcc_output NATIVE_COMMAND "${_nvcc_includes}") - foreach(line IN LISTS _nvcc_output) - string(REGEX REPLACE "^-I" "" line "${line}") - get_filename_component(line "${line}" ABSOLUTE) - list(APPEND CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES "${line}") - endforeach() - - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Parsed CUDA nvcc include information from above output:\n${_nvcc_log}\n${log}\n\n") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Failed to detect CUDA nvcc include information:\n${_nvcc_log}\n\n") - endif() - - # Parse default CUDA architecture. - cmake_policy(GET CMP0104 _CUDA_CMP0104) - if(NOT CMAKE_CUDA_ARCHITECTURES AND _CUDA_CMP0104 STREQUAL "NEW") - string(REGEX MATCH "arch[ =]compute_([0-9]+)" dont_care "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - set(detected_architecture "${CMAKE_MATCH_1}") - elseif(CMAKE_CUDA_ARCHITECTURES) - string(REGEX MATCHALL "-arch compute_([0-9]+)" target_cpus "${CMAKE_CUDA_COMPILER_PRODUCED_OUTPUT}") - - foreach(cpu ${target_cpus}) - string(REGEX MATCH "-arch compute_([0-9]+)" dont_care "${cpu}") - list(APPEND architectures "${CMAKE_MATCH_1}") - endforeach() - endif() -endif() - -# If the user didn't set the architectures, then set them to a default. -# If the user did, then make sure those architectures worked. -if(DEFINED detected_architecture AND "${CMAKE_CUDA_ARCHITECTURES}" STREQUAL "") - set(CMAKE_CUDA_ARCHITECTURES "${detected_architecture}" CACHE STRING "CUDA architectures") - - if(NOT CMAKE_CUDA_ARCHITECTURES) - message(FATAL_ERROR "Failed to find a working CUDA architecture.") - endif() -elseif(architectures) - # Sort since order mustn't matter. - list(SORT architectures) - list(SORT tested_architectures) - - # We don't distinguish real/virtual architectures during testing. - # For "70-real;70-virtual" we detect "70" as working and tested_architectures is "70;70". - # Thus we need to remove duplicates before checking if they're equal. - list(REMOVE_DUPLICATES tested_architectures) - - if(NOT "${architectures}" STREQUAL "${tested_architectures}") - message(FATAL_ERROR - "The CMAKE_CUDA_ARCHITECTURES:\n" - " ${CMAKE_CUDA_ARCHITECTURES}\n" - "do not all work with this compiler. Try:\n" - " ${architectures}\n" - "instead.") - endif() -endif() - -# configure all variables set in this file -configure_file(${CMAKE_ROOT}/Modules/CMakeCUDACompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCUDACompiler.cmake - @ONLY -) - -# Don't leak variables unnecessarily to user code. -unset(_CUDA_INCLUDE_DIR CACHE) -unset(_CUDA_NVCC_EXECUTABLE CACHE) -unset(_CUDA_LIBRARY_DIR) -unset(_CUDA_TARGET_DIR) -unset(_CUDA_TARGET_NAME) - -set(CMAKE_CUDA_COMPILER_ENV_VAR "CUDACXX") -set(CMAKE_CUDA_HOST_COMPILER_ENV_VAR "CUDAHOSTCXX")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCXXCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineCXXCompiler.cmake deleted file mode 100644 index 662b831..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCXXCompiler.cmake +++ /dev/null
@@ -1,225 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for C++ programs -# NOTE, a generator may set CMAKE_CXX_COMPILER before -# loading this file to force a compiler. -# use environment variable CXX first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_CXX which can be defined by a generator -# as a default compiler -# If the internal cmake variable _CMAKE_TOOLCHAIN_PREFIX is set, this is used -# as prefix for the tools (e.g. arm-elf-g++, arm-elf-ar etc.) -# -# Sets the following variables: -# CMAKE_CXX_COMPILER -# CMAKE_COMPILER_IS_GNUCXX -# CMAKE_AR -# CMAKE_RANLIB -# -# If not already set before, it also sets -# _CMAKE_TOOLCHAIN_PREFIX - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -# Load system-specific compiler preferences for this language. -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-CXX OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-CXX OPTIONAL) -if(NOT CMAKE_CXX_COMPILER_NAMES) - set(CMAKE_CXX_COMPILER_NAMES CC) -endif() - -if(${CMAKE_GENERATOR} MATCHES "Visual Studio") -elseif("${CMAKE_GENERATOR}" MATCHES "Green Hills MULTI") -elseif("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(CMAKE_CXX_COMPILER_XCODE_TYPE sourcecode.cpp.cpp) - _cmake_find_compiler_path(CXX) -else() - if(NOT CMAKE_CXX_COMPILER) - set(CMAKE_CXX_COMPILER_INIT NOTFOUND) - - # prefer the environment variable CXX - if(NOT $ENV{CXX} STREQUAL "") - get_filename_component(CMAKE_CXX_COMPILER_INIT $ENV{CXX} PROGRAM PROGRAM_ARGS CMAKE_CXX_FLAGS_ENV_INIT) - if(CMAKE_CXX_FLAGS_ENV_INIT) - set(CMAKE_CXX_COMPILER_ARG1 "${CMAKE_CXX_FLAGS_ENV_INIT}" CACHE STRING "First argument to CXX compiler") - endif() - if(NOT EXISTS ${CMAKE_CXX_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable CXX:\n$ENV{CXX}.\n${CMAKE_CXX_COMPILER_INIT}") - endif() - endif() - - # next prefer the generator specified compiler - if(CMAKE_GENERATOR_CXX) - if(NOT CMAKE_CXX_COMPILER_INIT) - set(CMAKE_CXX_COMPILER_INIT ${CMAKE_GENERATOR_CXX}) - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_CXX_COMPILER_INIT) - set(CMAKE_CXX_COMPILER_LIST CC ${_CMAKE_TOOLCHAIN_PREFIX}c++ ${_CMAKE_TOOLCHAIN_PREFIX}g++ aCC cl bcc xlC clang++) - endif() - - _cmake_find_compiler(CXX) - else() - _cmake_find_compiler_path(CXX) - endif() - mark_as_advanced(CMAKE_CXX_COMPILER) - - # Each entry in this list is a set of extra flags to try - # adding to the compile line to see if it helps produce - # a valid identification file. - set(CMAKE_CXX_COMPILER_ID_TEST_FLAGS_FIRST) - set(CMAKE_CXX_COMPILER_ID_TEST_FLAGS - # Try compiling to an object file only. - "-c" - # IAR does not detect language automatically - "--c++" - "--ec++" - - # ARMClang need target options - "--target=arm-arm-none-eabi -mcpu=cortex-m3" - ) -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_CXX_COMPILER_ID_RUN) - set(CMAKE_CXX_COMPILER_ID_RUN 1) - - # Try to identify the compiler. - set(CMAKE_CXX_COMPILER_ID) - set(CMAKE_CXX_PLATFORM_ID) - file(READ ${CMAKE_ROOT}/Modules/CMakePlatformId.h.in - CMAKE_CXX_COMPILER_ID_PLATFORM_CONTENT) - - # The IAR compiler produces weird output. - # See https://gitlab.kitware.com/cmake/cmake/-/issues/10176#note_153591 - list(APPEND CMAKE_CXX_COMPILER_ID_VENDORS IAR) - set(CMAKE_CXX_COMPILER_ID_VENDOR_FLAGS_IAR ) - set(CMAKE_CXX_COMPILER_ID_VENDOR_REGEX_IAR "IAR .+ Compiler") - - # Match the link line from xcodebuild output of the form - # Ld ... - # ... - # /path/to/cc ...CompilerIdCXX/... - # to extract the compiler front-end for the language. - set(CMAKE_CXX_COMPILER_ID_TOOL_MATCH_REGEX "\nLd[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]*-o[^\r\n]*CompilerIdCXX/(\\./)?(CompilerIdCXX.(framework|xctest)/)?CompilerIdCXX[ \t\n\\\"]") - set(CMAKE_CXX_COMPILER_ID_TOOL_MATCH_INDEX 2) - - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(CXX CXXFLAGS CMakeCXXCompilerId.cpp) - - _cmake_find_compiler_sysroot(CXX) - - # Set old compiler and platform id variables. - if(CMAKE_CXX_COMPILER_ID STREQUAL "GNU") - set(CMAKE_COMPILER_IS_GNUCXX 1) - endif() - if(CMAKE_CXX_PLATFORM_ID MATCHES "MinGW") - set(CMAKE_COMPILER_IS_MINGW 1) - elseif(CMAKE_CXX_PLATFORM_ID MATCHES "Cygwin") - set(CMAKE_COMPILER_IS_CYGWIN 1) - endif() -else() - if(NOT DEFINED CMAKE_CXX_COMPILER_FRONTEND_VARIANT) - # Some toolchain files set our internal CMAKE_CXX_COMPILER_ID_RUN - # variable but are not aware of CMAKE_CXX_COMPILER_FRONTEND_VARIANT. - # They pre-date our support for the GNU-like variant targeting the - # MSVC ABI so we do not consider that here. - if(CMAKE_CXX_COMPILER_ID STREQUAL "Clang") - if("x${CMAKE_CXX_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CXX_COMPILER_FRONTEND_VARIANT "MSVC") - else() - set(CMAKE_CXX_COMPILER_FRONTEND_VARIANT "GNU") - endif() - else() - set(CMAKE_CXX_COMPILER_FRONTEND_VARIANT "") - endif() - endif() -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_CXX_COMPILER}" PATH) -endif () - -# if we have a g++ cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-g++, arm-elf-g++ or i586-mingw32msvc-g++ , optionally -# with a 3-component version number at the end (e.g. arm-eabi-gcc-4.5.2). -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gcc.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" - - -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - - if("${CMAKE_CXX_COMPILER_ID}" MATCHES "GNU|Clang|QCC") - get_filename_component(COMPILER_BASENAME "${CMAKE_CXX_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)(clan)?[gc]\\+\\+(-[0-9]+(\\.[0-9]+)*)?(-[^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - set(_CMAKE_COMPILER_SUFFIX ${CMAKE_MATCH_5}) - elseif("${CMAKE_CXX_COMPILER_ID}" MATCHES "Clang") - if(CMAKE_CXX_COMPILER_TARGET) - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_CXX_COMPILER_TARGET}-) - endif() - elseif(COMPILER_BASENAME MATCHES "QCC(\\.exe)?$") - if(CMAKE_CXX_COMPILER_TARGET MATCHES "gcc_nto([a-z0-9]+_[0-9]+|[^_le]+)(le)") - set(_CMAKE_TOOLCHAIN_PREFIX nto${CMAKE_MATCH_1}-) - endif() - endif () - - # if "llvm-" is part of the prefix, remove it, since llvm doesn't have its own binutils - # but uses the regular ar, objcopy, etc. (instead of llvm-objcopy etc.) - if ("${_CMAKE_TOOLCHAIN_PREFIX}" MATCHES "(.+-)?llvm-$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - elseif("${CMAKE_CXX_COMPILER_ID}" MATCHES "TI") - # TI compilers are named e.g. cl6x, cl470 or armcl.exe - get_filename_component(COMPILER_BASENAME "${CMAKE_CXX_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+)?cl([^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX "${CMAKE_MATCH_1}") - set(_CMAKE_TOOLCHAIN_SUFFIX "${CMAKE_MATCH_2}") - endif () - - endif() - -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "CXX") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_CXX_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(CMAKE_CXX_COMPILER_SYSROOT) - string(CONCAT _SET_CMAKE_CXX_COMPILER_SYSROOT - "set(CMAKE_CXX_COMPILER_SYSROOT \"${CMAKE_CXX_COMPILER_SYSROOT}\")\n" - "set(CMAKE_COMPILER_SYSROOT \"${CMAKE_CXX_COMPILER_SYSROOT}\")") -else() - set(_SET_CMAKE_CXX_COMPILER_SYSROOT "") -endif() - -if(CMAKE_CXX_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_CXX_COMPILER_ARCHITECTURE_ID - "set(CMAKE_CXX_COMPILER_ARCHITECTURE_ID ${CMAKE_CXX_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_CXX_COMPILER_ARCHITECTURE_ID "") -endif() - -if(MSVC_CXX_ARCHITECTURE_ID) - set(SET_MSVC_CXX_ARCHITECTURE_ID - "set(MSVC_CXX_ARCHITECTURE_ID ${MSVC_CXX_ARCHITECTURE_ID})") -endif() - -if(CMAKE_CXX_XCODE_ARCHS) - set(SET_CMAKE_XCODE_ARCHS - "set(CMAKE_XCODE_ARCHS \"${CMAKE_CXX_XCODE_ARCHS}\")") -endif() - -# configure all variables set in this file -configure_file(${CMAKE_ROOT}/Modules/CMakeCXXCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCXXCompiler.cmake - @ONLY - ) - -set(CMAKE_CXX_COMPILER_ENV_VAR "CXX")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCompileFeatures.cmake b/share/cmake-3.18/Modules/CMakeDetermineCompileFeatures.cmake deleted file mode 100644 index b50e5f1..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCompileFeatures.cmake +++ /dev/null
@@ -1,147 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -function(cmake_determine_compile_features lang) - - if(lang STREQUAL C AND COMMAND cmake_record_c_compile_features) - message(CHECK_START "Detecting ${lang} compile features") - - set(CMAKE_C90_COMPILE_FEATURES) - set(CMAKE_C99_COMPILE_FEATURES) - set(CMAKE_C11_COMPILE_FEATURES) - - include("${CMAKE_ROOT}/Modules/Internal/FeatureTesting.cmake") - - cmake_record_c_compile_features() - - if(NOT _result EQUAL 0) - message(CHECK_FAIL "failed") - return() - endif() - - if (CMAKE_C99_COMPILE_FEATURES AND CMAKE_C11_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_C11_COMPILE_FEATURES ${CMAKE_C99_COMPILE_FEATURES}) - endif() - if (CMAKE_C90_COMPILE_FEATURES AND CMAKE_C99_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_C99_COMPILE_FEATURES ${CMAKE_C90_COMPILE_FEATURES}) - endif() - - if(NOT CMAKE_C_COMPILE_FEATURES) - set(CMAKE_C_COMPILE_FEATURES - ${CMAKE_C90_COMPILE_FEATURES} - ${CMAKE_C99_COMPILE_FEATURES} - ${CMAKE_C11_COMPILE_FEATURES} - ) - endif() - - set(CMAKE_C_COMPILE_FEATURES ${CMAKE_C_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_C90_COMPILE_FEATURES ${CMAKE_C90_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_C99_COMPILE_FEATURES ${CMAKE_C99_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_C11_COMPILE_FEATURES ${CMAKE_C11_COMPILE_FEATURES} PARENT_SCOPE) - - message(CHECK_PASS "done") - - elseif(lang STREQUAL CXX AND COMMAND cmake_record_cxx_compile_features) - message(CHECK_START "Detecting ${lang} compile features") - - set(CMAKE_CXX98_COMPILE_FEATURES) - set(CMAKE_CXX11_COMPILE_FEATURES) - set(CMAKE_CXX14_COMPILE_FEATURES) - set(CMAKE_CXX17_COMPILE_FEATURES) - set(CMAKE_CXX20_COMPILE_FEATURES) - - include("${CMAKE_ROOT}/Modules/Internal/FeatureTesting.cmake") - - cmake_record_cxx_compile_features() - - if(NOT _result EQUAL 0) - message(CHECK_FAIL "failed") - return() - endif() - - if (CMAKE_CXX17_COMPILE_FEATURES AND CMAKE_CXX20_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CXX20_COMPILE_FEATURES ${CMAKE_CXX17_COMPILE_FEATURES}) - endif() - if (CMAKE_CXX14_COMPILE_FEATURES AND CMAKE_CXX17_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CXX17_COMPILE_FEATURES ${CMAKE_CXX14_COMPILE_FEATURES}) - endif() - if (CMAKE_CXX11_COMPILE_FEATURES AND CMAKE_CXX14_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CXX14_COMPILE_FEATURES ${CMAKE_CXX11_COMPILE_FEATURES}) - endif() - if (CMAKE_CXX98_COMPILE_FEATURES AND CMAKE_CXX11_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CXX11_COMPILE_FEATURES ${CMAKE_CXX98_COMPILE_FEATURES}) - endif() - - if(NOT CMAKE_CXX_COMPILE_FEATURES) - set(CMAKE_CXX_COMPILE_FEATURES - ${CMAKE_CXX98_COMPILE_FEATURES} - ${CMAKE_CXX11_COMPILE_FEATURES} - ${CMAKE_CXX14_COMPILE_FEATURES} - ${CMAKE_CXX17_COMPILE_FEATURES} - ${CMAKE_CXX20_COMPILE_FEATURES} - ) - endif() - - set(CMAKE_CXX_COMPILE_FEATURES ${CMAKE_CXX_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CXX98_COMPILE_FEATURES ${CMAKE_CXX98_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CXX11_COMPILE_FEATURES ${CMAKE_CXX11_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CXX14_COMPILE_FEATURES ${CMAKE_CXX14_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CXX17_COMPILE_FEATURES ${CMAKE_CXX17_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CXX20_COMPILE_FEATURES ${CMAKE_CXX20_COMPILE_FEATURES} PARENT_SCOPE) - - message(CHECK_PASS "done") - - elseif(lang STREQUAL CUDA AND COMMAND cmake_record_cuda_compile_features) - message(CHECK_START "Detecting ${lang} compile features") - - set(CMAKE_CUDA03_COMPILE_FEATURES) - set(CMAKE_CUDA11_COMPILE_FEATURES) - set(CMAKE_CUDA14_COMPILE_FEATURES) - set(CMAKE_CUDA17_COMPILE_FEATURES) - set(CMAKE_CUDA20_COMPILE_FEATURES) - - include("${CMAKE_ROOT}/Modules/Internal/FeatureTesting.cmake") - - cmake_record_cuda_compile_features() - - if(NOT _result EQUAL 0) - message(CHECK_FAIL "failed") - return() - endif() - - if (CMAKE_CUDA17_COMPILE_FEATURES AND CMAKE_CUDA20_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CUDA20_COMPILE_FEATURES ${CMAKE_CUDA17_COMPILE_FEATURES}) - endif() - if (CMAKE_CUDA14_COMPILE_FEATURES AND CMAKE_CUDA17_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CUDA17_COMPILE_FEATURES ${CMAKE_CUDA14_COMPILE_FEATURES}) - endif() - if (CMAKE_CUDA11_COMPILE_FEATURES AND CMAKE_CUDA14_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CUDA14_COMPILE_FEATURES ${CMAKE_CUDA11_COMPILE_FEATURES}) - endif() - if (CMAKE_CUDA03_COMPILE_FEATURES AND CMAKE_CUDA11_COMPILE_FEATURES) - list(REMOVE_ITEM CMAKE_CUDA11_COMPILE_FEATURES ${CMAKE_CUDA03_COMPILE_FEATURES}) - endif() - - if(NOT CMAKE_CUDA_COMPILE_FEATURES) - set(CMAKE_CUDA_COMPILE_FEATURES - ${CMAKE_CUDA03_COMPILE_FEATURES} - ${CMAKE_CUDA11_COMPILE_FEATURES} - ${CMAKE_CUDA14_COMPILE_FEATURES} - ${CMAKE_CUDA17_COMPILE_FEATURES} - ${CMAKE_CUDA20_COMPILE_FEATURES} - ) - endif() - - set(CMAKE_CUDA_COMPILE_FEATURES ${CMAKE_CUDA_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CUDA03_COMPILE_FEATURES ${CMAKE_CUDA03_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CUDA11_COMPILE_FEATURES ${CMAKE_CUDA11_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CUDA14_COMPILE_FEATURES ${CMAKE_CUDA14_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CUDA17_COMPILE_FEATURES ${CMAKE_CUDA17_COMPILE_FEATURES} PARENT_SCOPE) - set(CMAKE_CUDA20_COMPILE_FEATURES ${CMAKE_CUDA20_COMPILE_FEATURES} PARENT_SCOPE) - - message(CHECK_PASS "done") - - endif() - -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineCompiler.cmake deleted file mode 100644 index cb1ab1d..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCompiler.cmake +++ /dev/null
@@ -1,152 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -macro(_cmake_find_compiler lang) - # Use already-enabled languages for reference. - get_property(_languages GLOBAL PROPERTY ENABLED_LANGUAGES) - list(REMOVE_ITEM _languages "${lang}") - - if(CMAKE_${lang}_COMPILER_INIT) - # Search only for the specified compiler. - set(CMAKE_${lang}_COMPILER_LIST "${CMAKE_${lang}_COMPILER_INIT}") - else() - # Re-order the compiler list with preferred vendors first. - set(_${lang}_COMPILER_LIST "${CMAKE_${lang}_COMPILER_LIST}") - set(CMAKE_${lang}_COMPILER_LIST "") - # Prefer vendors of compilers from reference languages. - foreach(l ${_languages}) - list(APPEND CMAKE_${lang}_COMPILER_LIST - ${_${lang}_COMPILER_NAMES_${CMAKE_${l}_COMPILER_ID}}) - endforeach() - # Prefer vendors based on the platform. - list(APPEND CMAKE_${lang}_COMPILER_LIST ${CMAKE_${lang}_COMPILER_NAMES}) - # Append the rest of the list and remove duplicates. - list(APPEND CMAKE_${lang}_COMPILER_LIST ${_${lang}_COMPILER_LIST}) - unset(_${lang}_COMPILER_LIST) - list(REMOVE_DUPLICATES CMAKE_${lang}_COMPILER_LIST) - if(CMAKE_${lang}_COMPILER_EXCLUDE) - list(REMOVE_ITEM CMAKE_${lang}_COMPILER_LIST - ${CMAKE_${lang}_COMPILER_EXCLUDE}) - endif() - endif() - - # Look for directories containing compilers of reference languages. - set(_${lang}_COMPILER_HINTS) - foreach(l ${_languages}) - if(CMAKE_${l}_COMPILER AND IS_ABSOLUTE "${CMAKE_${l}_COMPILER}") - get_filename_component(_hint "${CMAKE_${l}_COMPILER}" PATH) - if(IS_DIRECTORY "${_hint}") - list(APPEND _${lang}_COMPILER_HINTS "${_hint}") - endif() - unset(_hint) - endif() - endforeach() - - # Find the compiler. - if(_${lang}_COMPILER_HINTS) - # Prefer directories containing compilers of reference languages. - list(REMOVE_DUPLICATES _${lang}_COMPILER_HINTS) - find_program(CMAKE_${lang}_COMPILER - NAMES ${CMAKE_${lang}_COMPILER_LIST} - PATHS ${_${lang}_COMPILER_HINTS} - NO_DEFAULT_PATH - DOC "${lang} compiler") - endif() - if(CMAKE_HOST_WIN32 AND CMAKE_GENERATOR MATCHES "Ninja") - # On Windows command-line builds, the Makefile generators each imply - # a preferred compiler tool. The Ninja generator does not imply a - # compiler tool, so use the compiler that occurs first in PATH. - find_program(CMAKE_${lang}_COMPILER - NAMES ${CMAKE_${lang}_COMPILER_LIST} - NAMES_PER_DIR - DOC "${lang} compiler" - NO_PACKAGE_ROOT_PATH - NO_CMAKE_PATH - NO_CMAKE_ENVIRONMENT_PATH - NO_CMAKE_SYSTEM_PATH - ) - endif() - find_program(CMAKE_${lang}_COMPILER NAMES ${CMAKE_${lang}_COMPILER_LIST} DOC "${lang} compiler") - if(CMAKE_${lang}_COMPILER_INIT AND NOT CMAKE_${lang}_COMPILER) - set_property(CACHE CMAKE_${lang}_COMPILER PROPERTY VALUE "${CMAKE_${lang}_COMPILER_INIT}") - endif() - unset(_${lang}_COMPILER_HINTS) - unset(_languages) - - # Look for a make tool provided by Xcode - if(CMAKE_HOST_APPLE) - macro(_query_xcrun compiler_name result_var_keyword result_var) - if(NOT "x${result_var_keyword}" STREQUAL "xRESULT_VAR") - message(FATAL_ERROR "Bad arguments to macro") - endif() - execute_process(COMMAND xcrun --find ${compiler_name} - OUTPUT_VARIABLE _xcrun_out OUTPUT_STRIP_TRAILING_WHITESPACE - ERROR_VARIABLE _xcrun_err) - set("${result_var}" "${_xcrun_out}") - endmacro() - - set(xcrun_result) - if (CMAKE_${lang}_COMPILER MATCHES "^/usr/bin/(.+)$") - _query_xcrun("${CMAKE_MATCH_1}" RESULT_VAR xcrun_result) - elseif (CMAKE_${lang}_COMPILER STREQUAL "CMAKE_${lang}_COMPILER-NOTFOUND") - foreach(comp ${CMAKE_${lang}_COMPILER_LIST}) - _query_xcrun("${comp}" RESULT_VAR xcrun_result) - if(xcrun_result) - break() - endif() - endforeach() - endif() - if (xcrun_result) - set_property(CACHE CMAKE_${lang}_COMPILER PROPERTY VALUE "${xcrun_result}") - endif() - endif() -endmacro() - -macro(_cmake_find_compiler_path lang) - if(CMAKE_${lang}_COMPILER) - # we only get here if CMAKE_${lang}_COMPILER was specified using -D or a pre-made CMakeCache.txt - # (e.g. via ctest) or set in CMAKE_TOOLCHAIN_FILE - # if CMAKE_${lang}_COMPILER is a list of length 2, use the first item as - # CMAKE_${lang}_COMPILER and the 2nd one as CMAKE_${lang}_COMPILER_ARG1 - list(LENGTH CMAKE_${lang}_COMPILER _CMAKE_${lang}_COMPILER_LIST_LENGTH) - if("${_CMAKE_${lang}_COMPILER_LIST_LENGTH}" EQUAL 2) - list(GET CMAKE_${lang}_COMPILER 1 CMAKE_${lang}_COMPILER_ARG1) - list(GET CMAKE_${lang}_COMPILER 0 CMAKE_${lang}_COMPILER) - endif() - unset(_CMAKE_${lang}_COMPILER_LIST_LENGTH) - - # find the compiler in the PATH if necessary - get_filename_component(_CMAKE_USER_${lang}_COMPILER_PATH "${CMAKE_${lang}_COMPILER}" PATH) - if(NOT _CMAKE_USER_${lang}_COMPILER_PATH) - find_program(CMAKE_${lang}_COMPILER_WITH_PATH NAMES ${CMAKE_${lang}_COMPILER}) - if(CMAKE_${lang}_COMPILER_WITH_PATH) - set(CMAKE_${lang}_COMPILER ${CMAKE_${lang}_COMPILER_WITH_PATH}) - get_property(_CMAKE_${lang}_COMPILER_CACHED CACHE CMAKE_${lang}_COMPILER PROPERTY TYPE) - if(_CMAKE_${lang}_COMPILER_CACHED) - set(CMAKE_${lang}_COMPILER "${CMAKE_${lang}_COMPILER}" CACHE STRING "${lang} compiler" FORCE) - endif() - unset(_CMAKE_${lang}_COMPILER_CACHED) - endif() - unset(CMAKE_${lang}_COMPILER_WITH_PATH CACHE) - endif() - endif() -endmacro() - -function(_cmake_find_compiler_sysroot lang) - if(CMAKE_${lang}_COMPILER_ID STREQUAL "GNU") - execute_process(COMMAND "${CMAKE_${lang}_COMPILER}" -print-sysroot - OUTPUT_STRIP_TRAILING_WHITESPACE - OUTPUT_VARIABLE _cmake_sysroot_run_out - ERROR_VARIABLE _cmake_sysroot_run_err) - - if(_cmake_sysroot_run_out AND NOT _cmake_sysroot_run_err - AND NOT _cmake_sysroot_run_out STREQUAL "/" - AND IS_DIRECTORY "${_cmake_sysroot_run_out}/usr") - file(TO_CMAKE_PATH "${_cmake_sysroot_run_out}/usr" _cmake_sysroot_run_out_usr) - set(CMAKE_${lang}_COMPILER_SYSROOT "${_cmake_sysroot_run_out_usr}" PARENT_SCOPE) - else() - set(CMAKE_${lang}_COMPILER_SYSROOT "" PARENT_SCOPE) - endif() - endif() -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCompilerABI.cmake b/share/cmake-3.18/Modules/CMakeDetermineCompilerABI.cmake deleted file mode 100644 index 50d5cd1..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCompilerABI.cmake +++ /dev/null
@@ -1,190 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# Function to compile a source file to identify the compiler ABI. -# This is used internally by CMake and should not be included by user -# code. - -include(${CMAKE_ROOT}/Modules/CMakeParseImplicitIncludeInfo.cmake) -include(${CMAKE_ROOT}/Modules/CMakeParseImplicitLinkInfo.cmake) -include(CMakeTestCompilerCommon) - -function(CMAKE_DETERMINE_COMPILER_ABI lang src) - if(NOT DEFINED CMAKE_${lang}_ABI_COMPILED) - message(CHECK_START "Detecting ${lang} compiler ABI info") - - # Compile the ABI identification source. - set(BIN "${CMAKE_PLATFORM_INFO_DIR}/CMakeDetermineCompilerABI_${lang}.bin") - set(CMAKE_FLAGS ) - set(COMPILE_DEFINITIONS ) - if(DEFINED CMAKE_${lang}_VERBOSE_FLAG) - set(CMAKE_FLAGS "-DEXE_LINKER_FLAGS=${CMAKE_${lang}_VERBOSE_FLAG}") - set(COMPILE_DEFINITIONS "${CMAKE_${lang}_VERBOSE_FLAG}") - endif() - if(DEFINED CMAKE_${lang}_VERBOSE_COMPILE_FLAG) - set(COMPILE_DEFINITIONS "${CMAKE_${lang}_VERBOSE_COMPILE_FLAG}") - endif() - if(NOT "x${CMAKE_${lang}_COMPILER_ID}" STREQUAL "xMSVC") - # Avoid adding our own platform standard libraries for compilers - # from which we might detect implicit link libraries. - list(APPEND CMAKE_FLAGS "-DCMAKE_${lang}_STANDARD_LIBRARIES=") - endif() - __TestCompiler_setTryCompileTargetType() - - # Avoid failing ABI detection on warnings. - string(REGEX REPLACE "(^| )-Werror(=[^ ]*)?( |$)" " " CMAKE_${lang}_FLAGS "${CMAKE_${lang}_FLAGS}") - - # Save the current LC_ALL, LC_MESSAGES, and LANG environment variables - # and set them to "C" that way GCC's "search starts here" text is in - # English and we can grok it. - set(_orig_lc_all $ENV{LC_ALL}) - set(_orig_lc_messages $ENV{LC_MESSAGES}) - set(_orig_lang $ENV{LANG}) - set(ENV{LC_ALL} C) - set(ENV{LC_MESSAGES} C) - set(ENV{LANG} C) - - try_compile(CMAKE_${lang}_ABI_COMPILED - ${CMAKE_BINARY_DIR} ${src} - CMAKE_FLAGS ${CMAKE_FLAGS} - # Ignore unused flags when we are just determining the ABI. - "--no-warn-unused-cli" - COMPILE_DEFINITIONS ${COMPILE_DEFINITIONS} - OUTPUT_VARIABLE OUTPUT - COPY_FILE "${BIN}" - COPY_FILE_ERROR _copy_error - __CMAKE_INTERNAL ABI - ) - - # Restore original LC_ALL, LC_MESSAGES, and LANG - set(ENV{LC_ALL} ${_orig_lc_all}) - set(ENV{LC_MESSAGES} ${_orig_lc_messages}) - set(ENV{LANG} ${_orig_lang}) - - # Move result from cache to normal variable. - set(CMAKE_${lang}_ABI_COMPILED ${CMAKE_${lang}_ABI_COMPILED}) - unset(CMAKE_${lang}_ABI_COMPILED CACHE) - if(CMAKE_${lang}_ABI_COMPILED AND _copy_error) - set(CMAKE_${lang}_ABI_COMPILED 0) - endif() - set(CMAKE_${lang}_ABI_COMPILED ${CMAKE_${lang}_ABI_COMPILED} PARENT_SCOPE) - - # Load the resulting information strings. - if(CMAKE_${lang}_ABI_COMPILED) - message(CHECK_PASS "done") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Detecting ${lang} compiler ABI info compiled with the following output:\n${OUTPUT}\n\n") - file(STRINGS "${BIN}" ABI_STRINGS LIMIT_COUNT 2 REGEX "INFO:[A-Za-z0-9_]+\\[[^]]*\\]") - foreach(info ${ABI_STRINGS}) - if("${info}" MATCHES "INFO:sizeof_dptr\\[0*([^]]*)\\]") - set(ABI_SIZEOF_DPTR "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:abi\\[([^]]*)\\]") - set(ABI_NAME "${CMAKE_MATCH_1}") - endif() - endforeach() - - if(ABI_SIZEOF_DPTR) - set(CMAKE_${lang}_SIZEOF_DATA_PTR "${ABI_SIZEOF_DPTR}" PARENT_SCOPE) - elseif(CMAKE_${lang}_SIZEOF_DATA_PTR_DEFAULT) - set(CMAKE_${lang}_SIZEOF_DATA_PTR "${CMAKE_${lang}_SIZEOF_DATA_PTR_DEFAULT}" PARENT_SCOPE) - endif() - - if(ABI_NAME) - set(CMAKE_${lang}_COMPILER_ABI "${ABI_NAME}" PARENT_SCOPE) - endif() - - # Parse implicit include directory for this language, if available. - if(CMAKE_${lang}_VERBOSE_FLAG) - set (implicit_incdirs "") - cmake_parse_implicit_include_info("${OUTPUT}" "${lang}" - implicit_incdirs log rv) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Parsed ${lang} implicit include dir info from above output: rv=${rv}\n${log}\n\n") - if("${rv}" STREQUAL "done") - # Entries that we have been told to explicitly pass as standard include - # directories will not be implicitly added by the compiler. - if(CMAKE_${lang}_STANDARD_INCLUDE_DIRECTORIES) - list(REMOVE_ITEM implicit_incdirs ${CMAKE_${lang}_STANDARD_INCLUDE_DIRECTORIES}) - endif() - - # We parsed implicit include directories, so override the default initializer. - set(_CMAKE_${lang}_IMPLICIT_INCLUDE_DIRECTORIES_INIT "${implicit_incdirs}") - endif() - endif() - set(CMAKE_${lang}_IMPLICIT_INCLUDE_DIRECTORIES "${_CMAKE_${lang}_IMPLICIT_INCLUDE_DIRECTORIES_INIT}" PARENT_SCOPE) - - # Parse implicit linker information for this language, if available. - set(implicit_dirs "") - set(implicit_libs "") - set(implicit_fwks "") - if(CMAKE_${lang}_VERBOSE_FLAG) - CMAKE_PARSE_IMPLICIT_LINK_INFO("${OUTPUT}" implicit_libs implicit_dirs implicit_fwks log - "${CMAKE_${lang}_IMPLICIT_OBJECT_REGEX}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Parsed ${lang} implicit link information from above output:\n${log}\n\n") - endif() - # for VS IDE Intel Fortran we have to figure out the - # implicit link path for the fortran run time using - # a try-compile - if("${lang}" MATCHES "Fortran" - AND "${CMAKE_GENERATOR}" MATCHES "Visual Studio") - message(CHECK_START "Determine Intel Fortran Compiler Implicit Link Path") - # Build a sample project which reports symbols. - try_compile(IFORT_LIB_PATH_COMPILED - ${CMAKE_BINARY_DIR}/CMakeFiles/IntelVSImplicitPath - ${CMAKE_ROOT}/Modules/IntelVSImplicitPath - IntelFortranImplicit - CMAKE_FLAGS - "-DCMAKE_Fortran_FLAGS:STRING=${CMAKE_Fortran_FLAGS}" - OUTPUT_VARIABLE _output) - file(WRITE - "${CMAKE_BINARY_DIR}/CMakeFiles/IntelVSImplicitPath/output.txt" - "${_output}") - include(${CMAKE_BINARY_DIR}/CMakeFiles/IntelVSImplicitPath/output.cmake OPTIONAL) - message(CHECK_PASS "done") - endif() - - # Implicit link libraries cannot be used explicitly for multiple - # OS X architectures, so we skip it. - if(DEFINED CMAKE_OSX_ARCHITECTURES) - if("${CMAKE_OSX_ARCHITECTURES}" MATCHES ";") - set(implicit_libs "") - endif() - endif() - - set(CMAKE_${lang}_IMPLICIT_LINK_LIBRARIES "${implicit_libs}" PARENT_SCOPE) - set(CMAKE_${lang}_IMPLICIT_LINK_DIRECTORIES "${implicit_dirs}" PARENT_SCOPE) - set(CMAKE_${lang}_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "${implicit_fwks}" PARENT_SCOPE) - - # Detect library architecture directory name. - if(CMAKE_LIBRARY_ARCHITECTURE_REGEX) - foreach(dir ${implicit_dirs}) - if("${dir}" MATCHES "/lib/${CMAKE_LIBRARY_ARCHITECTURE_REGEX}$") - get_filename_component(arch "${dir}" NAME) - set(CMAKE_${lang}_LIBRARY_ARCHITECTURE "${arch}" PARENT_SCOPE) - break() - endif() - endforeach() - elseif(CMAKE_CXX_COMPILER_ID STREQUAL QCC) - foreach(dir ${implicit_dirs}) - if (dir MATCHES "/lib$") - get_filename_component(assumedArchDir "${dir}" DIRECTORY) - get_filename_component(archParentDir "${assumedArchDir}" DIRECTORY) - if (archParentDir STREQUAL CMAKE_SYSROOT) - get_filename_component(archDirName "${assumedArchDir}" NAME) - set(CMAKE_${lang}_LIBRARY_ARCHITECTURE "${archDirName}" PARENT_SCOPE) - break() - endif() - endif() - endforeach() - endif() - - else() - message(CHECK_FAIL "failed") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Detecting ${lang} compiler ABI info failed to compile with the following output:\n${OUTPUT}\n${_copy_error}\n\n") - endif() - endif() -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineCompilerId.cmake b/share/cmake-3.18/Modules/CMakeDetermineCompilerId.cmake deleted file mode 100644 index 44332a6..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineCompilerId.cmake +++ /dev/null
@@ -1,956 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# Function to compile a source file to identify the compiler. This is -# used internally by CMake and should not be included by user code. -# If successful, sets CMAKE_<lang>_COMPILER_ID and CMAKE_<lang>_PLATFORM_ID - -function(CMAKE_DETERMINE_COMPILER_ID lang flagvar src) - # Make sure the compiler arguments are clean. - string(STRIP "${CMAKE_${lang}_COMPILER_ARG1}" CMAKE_${lang}_COMPILER_ID_ARG1) - string(REGEX REPLACE " +" ";" CMAKE_${lang}_COMPILER_ID_ARG1 "${CMAKE_${lang}_COMPILER_ID_ARG1}") - - # Make sure user-specified compiler flags are used. - if(CMAKE_${lang}_FLAGS) - set(CMAKE_${lang}_COMPILER_ID_FLAGS ${CMAKE_${lang}_FLAGS}) - else() - set(CMAKE_${lang}_COMPILER_ID_FLAGS $ENV{${flagvar}}) - endif() - string(REPLACE " " ";" CMAKE_${lang}_COMPILER_ID_FLAGS_LIST "${CMAKE_${lang}_COMPILER_ID_FLAGS}") - - # Compute the directory in which to run the test. - set(CMAKE_${lang}_COMPILER_ID_DIR ${CMAKE_PLATFORM_INFO_DIR}/CompilerId${lang}) - - # Try building with no extra flags and then try each set - # of helper flags. Stop when the compiler is identified. - foreach(userflags "${CMAKE_${lang}_COMPILER_ID_FLAGS_LIST}" "") - foreach(testflags ${CMAKE_${lang}_COMPILER_ID_TEST_FLAGS_FIRST} - "" - ${CMAKE_${lang}_COMPILER_ID_TEST_FLAGS}) - separate_arguments(testflags UNIX_COMMAND "${testflags}") - CMAKE_DETERMINE_COMPILER_ID_BUILD("${lang}" "${testflags}" "${userflags}" "${src}") - CMAKE_DETERMINE_COMPILER_ID_MATCH_VENDOR("${lang}" "${COMPILER_${lang}_PRODUCED_OUTPUT}") - if(CMAKE_${lang}_COMPILER_ID) - break() - endif() - foreach(file ${COMPILER_${lang}_PRODUCED_FILES}) - CMAKE_DETERMINE_COMPILER_ID_CHECK("${lang}" "${CMAKE_${lang}_COMPILER_ID_DIR}/${file}" "${src}") - endforeach() - if(CMAKE_${lang}_COMPILER_ID) - break() - endif() - endforeach() - if(CMAKE_${lang}_COMPILER_ID) - break() - endif() - endforeach() - - # Check if compiler id detection gave us the compiler tool. - if(CMAKE_${lang}_COMPILER_ID_TOOL) - set(CMAKE_${lang}_COMPILER "${CMAKE_${lang}_COMPILER_ID_TOOL}") - set(CMAKE_${lang}_COMPILER "${CMAKE_${lang}_COMPILER_ID_TOOL}" PARENT_SCOPE) - elseif(NOT CMAKE_${lang}_COMPILER) - set(CMAKE_${lang}_COMPILER "CMAKE_${lang}_COMPILER-NOTFOUND" PARENT_SCOPE) - endif() - - # If the compiler is still unknown, try to query its vendor. - if(CMAKE_${lang}_COMPILER AND NOT CMAKE_${lang}_COMPILER_ID) - foreach(userflags "${CMAKE_${lang}_COMPILER_ID_FLAGS_LIST}" "") - CMAKE_DETERMINE_COMPILER_ID_VENDOR(${lang} "${userflags}") - endforeach() - endif() - - # If the compiler is still unknown, fallback to GHS - if(NOT CMAKE_${lang}_COMPILER_ID AND "${CMAKE_GENERATOR}" MATCHES "Green Hills MULTI") - set(CMAKE_${lang}_COMPILER_ID GHS) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "The ${lang} compiler identification is falling back to GHS.\n\n") - endif() - - # CUDA < 7.5 is missing version macros - if(lang STREQUAL "CUDA" - AND CMAKE_${lang}_COMPILER_ID STREQUAL "NVIDIA" - AND NOT CMAKE_${lang}_COMPILER_VERSION) - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - --version - OUTPUT_VARIABLE output ERROR_VARIABLE output - RESULT_VARIABLE result - TIMEOUT 10 - ) - if(output MATCHES [=[ V([0-9]+)\.([0-9]+)\.([0-9]+)]=]) - set(CMAKE_${lang}_COMPILER_VERSION "${CMAKE_MATCH_1}.${CMAKE_MATCH_2}.${CMAKE_MATCH_3}") - endif() - endif() - - # For Swift we need to explicitly query the version. - if(lang STREQUAL "Swift" - AND CMAKE_${lang}_COMPILER - AND NOT CMAKE_${lang}_COMPILER_VERSION) - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - -version - OUTPUT_VARIABLE output ERROR_VARIABLE output - RESULT_VARIABLE result - TIMEOUT 10 - ) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Running the ${lang} compiler: \"${CMAKE_${lang}_COMPILER}\" -version\n" - "${output}\n" - ) - - if(output MATCHES [[Swift version ([0-9]+\.[0-9]+(\.[0-9]+)?)]]) - set(CMAKE_${lang}_COMPILER_VERSION "${CMAKE_MATCH_1}") - if(NOT CMAKE_${lang}_COMPILER_ID) - set(CMAKE_Swift_COMPILER_ID "Apple") - endif() - endif() - endif() - - if (COMPILER_QNXNTO AND CMAKE_${lang}_COMPILER_ID STREQUAL "GNU") - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - -V - OUTPUT_VARIABLE output ERROR_VARIABLE output - RESULT_VARIABLE result - TIMEOUT 10 - ) - if (output MATCHES "targets available") - set(CMAKE_${lang}_COMPILER_ID QCC) - # http://community.qnx.com/sf/discussion/do/listPosts/projects.community/discussion.qnx_momentics_community_support.topc3555?_pagenum=2 - # The qcc driver does not itself have a version. - endif() - endif() - - # if the format is unknown after all files have been checked, put "Unknown" in the cache - if(NOT CMAKE_EXECUTABLE_FORMAT) - set(CMAKE_EXECUTABLE_FORMAT "Unknown" CACHE INTERNAL "Executable file format") - endif() - - if(CMAKE_GENERATOR MATCHES "^Ninja" AND MSVC_${lang}_ARCHITECTURE_ID) - foreach(userflags "${CMAKE_${lang}_COMPILER_ID_FLAGS_LIST}" "") - CMAKE_DETERMINE_MSVC_SHOWINCLUDES_PREFIX(${lang} "${userflags}") - endforeach() - else() - set(CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX "") - endif() - - set(_variant "") - if("x${CMAKE_${lang}_COMPILER_ID}" STREQUAL "xClang") - if("x${CMAKE_${lang}_SIMULATE_ID}" STREQUAL "xMSVC") - if(CMAKE_GENERATOR MATCHES "Visual Studio") - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "MSVC") - else() - # Test whether an MSVC-like command-line option works. - execute_process(COMMAND "${CMAKE_${lang}_COMPILER}" -? - RESULT_VARIABLE _clang_result - OUTPUT_VARIABLE _clang_stdout - ERROR_VARIABLE _clang_stderr) - if(_clang_result EQUAL 0) - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "MSVC") - else() - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "GNU") - endif() - endif() - set(_variant " with ${CMAKE_${lang}_COMPILER_FRONTEND_VARIANT}-like command-line") - else() - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "GNU") - endif() - else() - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "") - endif() - - # Display the final identification result. - if(CMAKE_${lang}_COMPILER_ID) - if(CMAKE_${lang}_COMPILER_VERSION) - set(_version " ${CMAKE_${lang}_COMPILER_VERSION}") - else() - set(_version "") - endif() - if(CMAKE_${lang}_COMPILER_ARCHITECTURE_ID AND "x${CMAKE_${lang}_COMPILER_ID}" STREQUAL "xIAR") - set(_archid " ${CMAKE_${lang}_COMPILER_ARCHITECTURE_ID}") - else() - set(_archid "") - endif() - message(STATUS "The ${lang} compiler identification is " - "${CMAKE_${lang}_COMPILER_ID}${_archid}${_version}${_variant}") - unset(_archid) - unset(_version) - unset(_variant) - else() - message(STATUS "The ${lang} compiler identification is unknown") - endif() - - if(lang STREQUAL "Fortran" AND CMAKE_${lang}_COMPILER_ID STREQUAL "XL") - set(CMAKE_${lang}_XL_CPP "${CMAKE_${lang}_COMPILER_ID_CPP}" PARENT_SCOPE) - endif() - - set(CMAKE_${lang}_COMPILER_ID "${CMAKE_${lang}_COMPILER_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_PLATFORM_ID "${CMAKE_${lang}_PLATFORM_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_ARCHITECTURE_ID "${CMAKE_${lang}_COMPILER_ARCHITECTURE_ID}" PARENT_SCOPE) - set(MSVC_${lang}_ARCHITECTURE_ID "${MSVC_${lang}_ARCHITECTURE_ID}" - PARENT_SCOPE) - set(CMAKE_${lang}_XCODE_ARCHS "${CMAKE_${lang}_XCODE_ARCHS}" PARENT_SCOPE) - set(CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX "${CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_FRONTEND_VARIANT "${CMAKE_${lang}_COMPILER_FRONTEND_VARIANT}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_VERSION "${CMAKE_${lang}_COMPILER_VERSION}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_VERSION_INTERNAL "${CMAKE_${lang}_COMPILER_VERSION_INTERNAL}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_WRAPPER "${CMAKE_${lang}_COMPILER_WRAPPER}" PARENT_SCOPE) - set(CMAKE_${lang}_SIMULATE_ID "${CMAKE_${lang}_SIMULATE_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_SIMULATE_VERSION "${CMAKE_${lang}_SIMULATE_VERSION}" PARENT_SCOPE) - set(CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT "${CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_PRODUCED_OUTPUT "${COMPILER_${lang}_PRODUCED_OUTPUT}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_PRODUCED_FILES "${COMPILER_${lang}_PRODUCED_FILES}" PARENT_SCOPE) -endfunction() - -include(CMakeCompilerIdDetection) - -#----------------------------------------------------------------------------- -# Function to write the compiler id source file. -function(CMAKE_DETERMINE_COMPILER_ID_WRITE lang src) - find_file(src_in ${src}.in PATHS ${CMAKE_ROOT}/Modules ${CMAKE_MODULE_PATH} NO_DEFAULT_PATH NO_CMAKE_FIND_ROOT_PATH) - file(READ ${src_in} ID_CONTENT_IN) - - compiler_id_detection(CMAKE_${lang}_COMPILER_ID_CONTENT ${lang} - ID_STRING - VERSION_STRINGS - PLATFORM_DEFAULT_COMPILER - ) - - unset(src_in CACHE) - string(CONFIGURE "${ID_CONTENT_IN}" ID_CONTENT_OUT @ONLY) - file(WRITE ${CMAKE_${lang}_COMPILER_ID_DIR}/${src} "${ID_CONTENT_OUT}") -endfunction() - -#----------------------------------------------------------------------------- -# Function to build the compiler id source file and look for output -# files. -function(CMAKE_DETERMINE_COMPILER_ID_BUILD lang testflags userflags src) - # Create a clean working directory. - file(REMOVE_RECURSE ${CMAKE_${lang}_COMPILER_ID_DIR}) - file(MAKE_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR}) - file(MAKE_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR}/tmp) - CMAKE_DETERMINE_COMPILER_ID_WRITE("${lang}" "${src}") - - # Construct a description of this test case. - set(COMPILER_DESCRIPTION - "Compiler: ${CMAKE_${lang}_COMPILER} ${CMAKE_${lang}_COMPILER_ID_ARG1} -Build flags: ${userflags} -Id flags: ${testflags} ${CMAKE_${lang}_COMPILER_ID_FLAGS_ALWAYS} -") - - # Compile the compiler identification source. - if("${CMAKE_GENERATOR}" MATCHES "Visual Studio ([0-9]+)") - set(vs_version ${CMAKE_MATCH_1}) - set(id_platform ${CMAKE_VS_PLATFORM_NAME}) - set(id_lang "${lang}") - set(id_PostBuildEvent_Command "") - if(CMAKE_VS_PLATFORM_TOOLSET MATCHES "^[Ll][Ll][Vv][Mm](_v[0-9]+(_xp)?)?$") - set(id_cl_var "ClangClExecutable") - elseif(CMAKE_VS_PLATFORM_TOOLSET MATCHES "^[Cc][Ll][Aa][Nn][Gg][Cc][Ll]$") - set(id_cl "$(CLToolExe)") - elseif(CMAKE_VS_PLATFORM_TOOLSET MATCHES "v[0-9]+_clang_.*") - set(id_cl clang.exe) - else() - set(id_cl cl.exe) - endif() - if(CMAKE_VS_PLATFORM_NAME STREQUAL "Tegra-Android") - set(v NsightTegra) - set(ext vcxproj) - if(lang STREQUAL CXX) - set(id_gcc g++) - set(id_clang clang++) - else() - set(id_gcc gcc) - set(id_clang clang) - endif() - elseif(lang STREQUAL Fortran) - set(v Intel) - set(ext vfproj) - set(id_cl ifort.exe) - elseif(lang STREQUAL CSharp) - set(v 10) - set(ext csproj) - set(id_cl csc.exe) - elseif(NOT "${vs_version}" VERSION_LESS 10) - set(v 10) - set(ext vcxproj) - else() - set(id_version ${vs_version}.00) - set(v 7) - set(ext vcproj) - endif() - if(CMAKE_VS_PLATFORM_TOOLSET) - if(CMAKE_VS_PLATFORM_NAME STREQUAL "Tegra-Android") - set(id_toolset "<NdkToolchainVersion>${CMAKE_VS_PLATFORM_TOOLSET}</NdkToolchainVersion>") - else() - set(id_toolset "<PlatformToolset>${CMAKE_VS_PLATFORM_TOOLSET}</PlatformToolset>") - if(CMAKE_VS_PLATFORM_TOOLSET MATCHES "Intel") - set(id_cl icl.exe) - endif() - if(CMAKE_VS_PLATFORM_TOOLSET_VERSION) - set(id_sep "\\") - if(CMAKE_VS_PLATFORM_TOOLSET_VERSION VERSION_GREATER_EQUAL "14.20") - if(EXISTS "${CMAKE_GENERATOR_INSTANCE}/VC/Auxiliary/Build.${CMAKE_VS_PLATFORM_TOOLSET_VERSION}/Microsoft.VCToolsVersion.${CMAKE_VS_PLATFORM_TOOLSET_VERSION}.props") - set(id_sep ".") - endif() - endif() - set(id_toolset_version_props "<Import Project=\"${CMAKE_GENERATOR_INSTANCE}\\VC\\Auxiliary\\Build${id_sep}${CMAKE_VS_PLATFORM_TOOLSET_VERSION}\\Microsoft.VCToolsVersion.${CMAKE_VS_PLATFORM_TOOLSET_VERSION}.props\" />") - unset(id_sep) - endif() - endif() - else() - set(id_toolset "") - set(id_toolset_version_props "") - endif() - if(CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE) - set(id_PreferredToolArchitecture "<PreferredToolArchitecture>${CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE}</PreferredToolArchitecture>") - else() - set(id_PreferredToolArchitecture "") - endif() - if(CMAKE_SYSTEM_NAME STREQUAL "WindowsPhone") - set(id_system "<ApplicationType>Windows Phone</ApplicationType>") - elseif(CMAKE_SYSTEM_NAME STREQUAL "WindowsStore") - set(id_system "<ApplicationType>Windows Store</ApplicationType>") - else() - set(id_system "") - endif() - if(id_system AND CMAKE_SYSTEM_VERSION MATCHES "^([0-9]+\\.[0-9]+)") - set(id_system_version "<ApplicationTypeRevision>${CMAKE_MATCH_1}</ApplicationTypeRevision>") - else() - set(id_system_version "") - endif() - if(CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION) - set(id_WindowsTargetPlatformVersion "<WindowsTargetPlatformVersion>${CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION}</WindowsTargetPlatformVersion>") - endif() - if(CMAKE_VS_PLATFORM_TOOLSET_VCTARGETS_CUSTOM_DIR) - set(id_ToolsetVCTargetsDir "<VCTargetsPath>${CMAKE_VS_PLATFORM_TOOLSET_VCTARGETS_CUSTOM_DIR}</VCTargetsPath>") - endif() - set(id_CustomGlobals "") - foreach(pair IN LISTS CMAKE_VS_GLOBALS) - if("${pair}" MATCHES "([^=]+)=(.*)$") - string(APPEND id_CustomGlobals "<${CMAKE_MATCH_1}>${CMAKE_MATCH_2}</${CMAKE_MATCH_1}>\n ") - endif() - endforeach() - if(id_platform STREQUAL ARM64) - set(id_WindowsSDKDesktopARMSupport "<WindowsSDKDesktopARM64Support>true</WindowsSDKDesktopARM64Support>") - elseif(id_platform STREQUAL ARM) - set(id_WindowsSDKDesktopARMSupport "<WindowsSDKDesktopARMSupport>true</WindowsSDKDesktopARMSupport>") - else() - set(id_WindowsSDKDesktopARMSupport "") - endif() - if(CMAKE_VS_WINCE_VERSION) - set(id_entrypoint "mainACRTStartup") - if("${vs_version}" VERSION_LESS 9) - set(id_subsystem 9) - else() - set(id_subsystem 8) - endif() - else() - set(id_subsystem 1) - endif() - set(id_dir ${CMAKE_${lang}_COMPILER_ID_DIR}) - set(id_src "${src}") - set(id_compile "ClCompile") - if(id_cl_var) - set(id_PostBuildEvent_Command "echo CMAKE_${lang}_COMPILER=$(${id_cl_var})") - else() - set(id_PostBuildEvent_Command "for %%i in (${id_cl}) do %40echo CMAKE_${lang}_COMPILER=%%~$PATH:i") - endif() - set(id_Import_props "") - set(id_Import_targets "") - set(id_ItemDefinitionGroup_entry "") - set(id_Link_AdditionalDependencies "") - if(lang STREQUAL CUDA) - if(NOT CMAKE_VS_PLATFORM_TOOLSET_CUDA) - message(FATAL_ERROR "No CUDA toolset found.") - endif() - set(cuda_tools "CUDA ${CMAKE_VS_PLATFORM_TOOLSET_CUDA}") - set(id_compile "CudaCompile") - set(id_ItemDefinitionGroup_entry "<CudaCompile><AdditionalOptions>%(AdditionalOptions)-v</AdditionalOptions></CudaCompile>") - set(id_PostBuildEvent_Command [[echo CMAKE_CUDA_COMPILER=$(CudaToolkitBinDir)\nvcc.exe]]) - if(CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR) - set(id_CudaToolkitCustomDir "<CudaToolkitCustomDir>${CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR}nvcc</CudaToolkitCustomDir>") - string(CONCAT id_Import_props "<Import Project=\"${CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR}\\CUDAVisualStudioIntegration\\extras\\visual_studio_integration\\MSBuildExtensions\\${cuda_tools}.props\" />") - string(CONCAT id_Import_targets "<Import Project=\"${CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR}\\CUDAVisualStudioIntegration\\extras\\visual_studio_integration\\MSBuildExtensions\\${cuda_tools}.targets\" />") - else() - string(CONCAT id_Import_props [[<Import Project="$(VCTargetsPath)\BuildCustomizations\]] "${cuda_tools}" [[.props" />]]) - string(CONCAT id_Import_targets [[<Import Project="$(VCTargetsPath)\BuildCustomizations\]] "${cuda_tools}" [[.targets" />]]) - endif() - if(CMAKE_VS_PLATFORM_NAME STREQUAL x64) - set(id_ItemDefinitionGroup_entry "<CudaCompile><TargetMachinePlatform>64</TargetMachinePlatform><AdditionalOptions>%(AdditionalOptions)-v</AdditionalOptions></CudaCompile>") - endif() - if(CMAKE_CUDA_FLAGS MATCHES "(^| )-cudart +shared( |$)") - set(id_Link_AdditionalDependencies "<AdditionalDependencies>cudart.lib</AdditionalDependencies>") - else() - set(id_Link_AdditionalDependencies "<AdditionalDependencies>cudart_static.lib</AdditionalDependencies>") - endif() - endif() - configure_file(${CMAKE_ROOT}/Modules/CompilerId/VS-${v}.${ext}.in - ${id_dir}/CompilerId${lang}.${ext} @ONLY) - if(CMAKE_VS_MSBUILD_COMMAND AND NOT lang STREQUAL "Fortran") - set(command "${CMAKE_VS_MSBUILD_COMMAND}" "CompilerId${lang}.${ext}" - "/p:Configuration=Debug" "/p:Platform=${id_platform}" "/p:VisualStudioVersion=${vs_version}.0" - ) - elseif(CMAKE_VS_DEVENV_COMMAND) - set(command "${CMAKE_VS_DEVENV_COMMAND}" "CompilerId${lang}.${ext}" "/build" "Debug") - else() - set(command "") - endif() - if(command) - execute_process( - COMMAND ${command} - WORKING_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR} - OUTPUT_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - ERROR_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - RESULT_VARIABLE CMAKE_${lang}_COMPILER_ID_RESULT - ) - else() - set(CMAKE_${lang}_COMPILER_ID_RESULT 1) - set(CMAKE_${lang}_COMPILER_ID_OUTPUT "VS environment not known to support ${lang}") - endif() - # Match the compiler location line printed out. - if("${CMAKE_${lang}_COMPILER_ID_OUTPUT}" MATCHES "CMAKE_${lang}_COMPILER=([^%\r\n]+)[\r\n]") - # Strip VS diagnostic output from the end of the line. - string(REGEX REPLACE " \\(TaskId:[0-9]*\\)$" "" _comp "${CMAKE_MATCH_1}") - if(EXISTS "${_comp}") - file(TO_CMAKE_PATH "${_comp}" _comp) - set(CMAKE_${lang}_COMPILER_ID_TOOL "${_comp}" PARENT_SCOPE) - endif() - endif() - elseif("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(id_lang "${lang}") - set(id_type ${CMAKE_${lang}_COMPILER_XCODE_TYPE}) - set(id_dir ${CMAKE_${lang}_COMPILER_ID_DIR}) - set(id_src "${src}") - if(CMAKE_XCODE_PLATFORM_TOOLSET) - set(id_toolset "GCC_VERSION = ${CMAKE_XCODE_PLATFORM_TOOLSET};") - else() - set(id_toolset "") - endif() - if("${lang}" STREQUAL "Swift") - if(CMAKE_Swift_LANGUAGE_VERSION) - set(id_lang_version "SWIFT_VERSION = ${CMAKE_Swift_LANGUAGE_VERSION};") - elseif(XCODE_VERSION VERSION_GREATER_EQUAL 10.2) - set(id_lang_version "SWIFT_VERSION = 4.0;") - elseif(XCODE_VERSION VERSION_GREATER_EQUAL 8.3) - set(id_lang_version "SWIFT_VERSION = 3.0;") - else() - set(id_lang_version "SWIFT_VERSION = 2.3;") - endif() - else() - set(id_lang_version "") - endif() - if(CMAKE_OSX_DEPLOYMENT_TARGET) - set(id_deployment_target - "MACOSX_DEPLOYMENT_TARGET = \"${CMAKE_OSX_DEPLOYMENT_TARGET}\";") - else() - set(id_deployment_target "") - endif() - set(id_product_type "com.apple.product-type.tool") - if(CMAKE_OSX_SYSROOT) - set(id_sdkroot "SDKROOT = \"${CMAKE_OSX_SYSROOT}\";") - if(CMAKE_OSX_SYSROOT MATCHES "(^|/)[Ii][Pp][Hh][Oo][Nn][Ee]" OR - CMAKE_OSX_SYSROOT MATCHES "(^|/)[Aa][Pp][Pp][Ll][Ee][Tt][Vv]") - set(id_product_type "com.apple.product-type.bundle.unit-test") - elseif(CMAKE_OSX_SYSROOT MATCHES "(^|/)[Ww][Aa][Tt][Cc][Hh]") - set(id_product_type "com.apple.product-type.framework") - endif() - else() - set(id_sdkroot "") - endif() - set(id_clang_cxx_library "") - set(stdlib_regex "(^| )(-stdlib=)([^ ]+)( |$)") - string(REGEX MATCHALL "${stdlib_regex}" all_stdlib_matches "${CMAKE_CXX_FLAGS}") - if(all_stdlib_matches) - list(GET all_stdlib_matches "-1" last_stdlib_match) - if(last_stdlib_match MATCHES "${stdlib_regex}") - set(id_clang_cxx_library "CLANG_CXX_LIBRARY = \"${CMAKE_MATCH_3}\";") - endif() - endif() - if(CMAKE_SYSTEM_NAME STREQUAL "Darwin" AND CMAKE_OSX_SYSROOT MATCHES "^$|[Mm][Aa][Cc][Oo][Ss]") - # When targeting macOS, use only the host architecture. - set(id_archs [[ARCHS = "$(NATIVE_ARCH_ACTUAL)";]]) - else() - set(id_archs "") - endif() - configure_file(${CMAKE_ROOT}/Modules/CompilerId/Xcode-3.pbxproj.in - ${id_dir}/CompilerId${lang}.xcodeproj/project.pbxproj @ONLY) - unset(_ENV_MACOSX_DEPLOYMENT_TARGET) - if(DEFINED ENV{MACOSX_DEPLOYMENT_TARGET}) - set(_ENV_MACOSX_DEPLOYMENT_TARGET "$ENV{MACOSX_DEPLOYMENT_TARGET}") - set(ENV{MACOSX_DEPLOYMENT_TARGET} "") - endif() - execute_process(COMMAND xcodebuild - WORKING_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR} - OUTPUT_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - ERROR_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - RESULT_VARIABLE CMAKE_${lang}_COMPILER_ID_RESULT - ) - if(DEFINED _ENV_MACOSX_DEPLOYMENT_TARGET) - set(ENV{MACOSX_DEPLOYMENT_TARGET} "${_ENV_MACOSX_DEPLOYMENT_TARGET}") - endif() - - if(DEFINED CMAKE_${lang}_COMPILER_ID_TOOL_MATCH_REGEX) - if("${CMAKE_${lang}_COMPILER_ID_OUTPUT}" MATCHES "${CMAKE_${lang}_COMPILER_ID_TOOL_MATCH_REGEX}") - set(_comp "${CMAKE_MATCH_${CMAKE_${lang}_COMPILER_ID_TOOL_MATCH_INDEX}}") - if(EXISTS "${_comp}") - set(CMAKE_${lang}_COMPILER_ID_TOOL "${_comp}" PARENT_SCOPE) - endif() - endif() - endif() - if("${CMAKE_${lang}_COMPILER_ID_OUTPUT}" MATCHES "ARCHS=([^%\r\n]+)[\r\n]") - set(CMAKE_${lang}_XCODE_ARCHS "${CMAKE_MATCH_1}") - separate_arguments(CMAKE_${lang}_XCODE_ARCHS) - set(CMAKE_${lang}_XCODE_ARCHS "${CMAKE_${lang}_XCODE_ARCHS}" PARENT_SCOPE) - endif() - elseif("${CMAKE_GENERATOR}" MATCHES "Green Hills MULTI") - set(id_dir ${CMAKE_${lang}_COMPILER_ID_DIR}) - set(id_src "${src}") - if (GHS_PRIMARY_TARGET) - set(ghs_primary_target "${GHS_PRIMARY_TARGET}") - else() - set(ghs_primary_target "${CMAKE_GENERATOR_PLATFORM}_${GHS_TARGET_PLATFORM}.tgt") - endif() - if ("${GHS_TARGET_PLATFORM}" MATCHES "integrity") - set(bsp_name "macro GHS_BSP=${GHS_BSP_NAME}") - set(os_dir "macro GHS_OS=${GHS_OS_DIR}") - endif() - set(command "${CMAKE_MAKE_PROGRAM}" "-commands" "-top" "GHS_default.gpj") - configure_file(${CMAKE_ROOT}/Modules/CompilerId/GHS_default.gpj.in - ${id_dir}/GHS_default.gpj @ONLY) - configure_file(${CMAKE_ROOT}/Modules/CompilerId/GHS_lib.gpj.in - ${id_dir}/GHS_lib.gpj @ONLY) - execute_process(COMMAND ${command} - WORKING_DIRECTORY ${id_dir} - OUTPUT_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - ERROR_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - RESULT_VARIABLE CMAKE_${lang}_COMPILER_ID_RESULT - ) - # Match the compiler location line printed out. - set(ghs_toolpath "${CMAKE_MAKE_PROGRAM}") - if(CMAKE_HOST_UNIX) - string(REPLACE "/gbuild" "/" ghs_toolpath ${ghs_toolpath}) - else() - string(REPLACE "/gbuild.exe" "/" ghs_toolpath ${ghs_toolpath}) - string(REPLACE / "\\\\" ghs_toolpath ${ghs_toolpath}) - endif() - if("${CMAKE_${lang}_COMPILER_ID_OUTPUT}" MATCHES "(${ghs_toolpath}[^ ]*)") - if(CMAKE_HOST_UNIX) - set(_comp "${CMAKE_MATCH_1}") - else() - set(_comp "${CMAKE_MATCH_1}.exe") - endif() - if(EXISTS "${_comp}") - file(TO_CMAKE_PATH "${_comp}" _comp) - set(CMAKE_${lang}_COMPILER_ID_TOOL "${_comp}" PARENT_SCOPE) - endif() - endif() - else() - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - ${CMAKE_${lang}_COMPILER_ID_ARG1} - ${userflags} - ${testflags} - ${CMAKE_${lang}_COMPILER_ID_FLAGS_ALWAYS} - "${src}" - WORKING_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR} - OUTPUT_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - ERROR_VARIABLE CMAKE_${lang}_COMPILER_ID_OUTPUT - RESULT_VARIABLE CMAKE_${lang}_COMPILER_ID_RESULT - ) - if("${CMAKE_${lang}_COMPILER_ID_OUTPUT}" MATCHES "exec: [^\n]*\\((/[^,\n]*/cpp),CMakeFortranCompilerId.F") - set(_cpp "${CMAKE_MATCH_1}") - if(EXISTS "${_cpp}") - set(CMAKE_${lang}_COMPILER_ID_CPP "${_cpp}" PARENT_SCOPE) - endif() - endif() - endif() - - # Check the result of compilation. - if(CMAKE_${lang}_COMPILER_ID_RESULT - # Intel Fortran warns and ignores preprocessor lines without /fpp - OR CMAKE_${lang}_COMPILER_ID_OUTPUT MATCHES "Bad # preprocessor line" - ) - # Compilation failed. - set(MSG - "Compiling the ${lang} compiler identification source file \"${src}\" failed. -${COMPILER_DESCRIPTION} -The output was: -${CMAKE_${lang}_COMPILER_ID_RESULT} -${CMAKE_${lang}_COMPILER_ID_OUTPUT} - -") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log "${MSG}") - #if(NOT CMAKE_${lang}_COMPILER_ID_ALLOW_FAIL) - # message(FATAL_ERROR "${MSG}") - #endif() - - # No output files should be inspected. - set(COMPILER_${lang}_PRODUCED_FILES) - set(COMPILER_${lang}_PRODUCED_OUTPUT) - else() - # Compilation succeeded. - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Compiling the ${lang} compiler identification source file \"${src}\" succeeded. -${COMPILER_DESCRIPTION} -The output was: -${CMAKE_${lang}_COMPILER_ID_RESULT} -${CMAKE_${lang}_COMPILER_ID_OUTPUT} - -") - - # Find the executable produced by the compiler, try all files in the - # binary dir. - string(REGEX REPLACE "([][])" "[\\1]" _glob_id_dir "${CMAKE_${lang}_COMPILER_ID_DIR}") - file(GLOB files - RELATIVE ${CMAKE_${lang}_COMPILER_ID_DIR} - - # normal case - ${_glob_id_dir}/* - - # com.apple.package-type.bundle.unit-test - ${_glob_id_dir}/*.xctest/* - - # com.apple.product-type.framework - ${_glob_id_dir}/*.framework/* - ) - list(REMOVE_ITEM files "${src}") - set(COMPILER_${lang}_PRODUCED_FILES "") - foreach(file ${files}) - if(NOT IS_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR}/${file}) - list(APPEND COMPILER_${lang}_PRODUCED_FILES ${file}) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Compilation of the ${lang} compiler identification source \"" - "${src}\" produced \"${file}\"\n\n") - endif() - endforeach() - - if(NOT COMPILER_${lang}_PRODUCED_FILES) - # No executable was found. - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Compilation of the ${lang} compiler identification source \"" - "${src}\" did not produce an executable in \"" - "${CMAKE_${lang}_COMPILER_ID_DIR}\".\n\n") - endif() - - set(COMPILER_${lang}_PRODUCED_OUTPUT "${CMAKE_${lang}_COMPILER_ID_OUTPUT}") - endif() - - # Return the files produced by the compilation. - set(COMPILER_${lang}_PRODUCED_FILES "${COMPILER_${lang}_PRODUCED_FILES}" PARENT_SCOPE) - set(COMPILER_${lang}_PRODUCED_OUTPUT "${COMPILER_${lang}_PRODUCED_OUTPUT}" PARENT_SCOPE) - -endfunction() - -#----------------------------------------------------------------------------- -# Function to extract the compiler id from compiler output. -function(CMAKE_DETERMINE_COMPILER_ID_MATCH_VENDOR lang output) - foreach(vendor ${CMAKE_${lang}_COMPILER_ID_MATCH_VENDORS}) - if(output MATCHES "${CMAKE_${lang}_COMPILER_ID_MATCH_VENDOR_REGEX_${vendor}}") - set(CMAKE_${lang}_COMPILER_ID "${vendor}") - endif() - endforeach() - set(CMAKE_${lang}_COMPILER_ID "${CMAKE_${lang}_COMPILER_ID}" PARENT_SCOPE) -endfunction() - -#----------------------------------------------------------------------------- -# Function to extract the compiler id from an executable. -function(CMAKE_DETERMINE_COMPILER_ID_CHECK lang file) - # Look for a compiler id if not yet known. - if(NOT CMAKE_${lang}_COMPILER_ID) - # Read the compiler identification string from the executable file. - set(COMPILER_ID) - set(COMPILER_VERSION) - set(COMPILER_VERSION_MAJOR 0) - set(COMPILER_VERSION_MINOR 0) - set(COMPILER_VERSION_PATCH 0) - set(COMPILER_VERSION_TWEAK 0) - set(COMPILER_VERSION_INTERNAL "") - set(HAVE_COMPILER_VERSION_MAJOR 0) - set(HAVE_COMPILER_VERSION_MINOR 0) - set(HAVE_COMPILER_VERSION_PATCH 0) - set(HAVE_COMPILER_VERSION_TWEAK 0) - set(COMPILER_WRAPPER) - set(DIGIT_VALUE_1 1) - set(DIGIT_VALUE_2 10) - set(DIGIT_VALUE_3 100) - set(DIGIT_VALUE_4 1000) - set(DIGIT_VALUE_5 10000) - set(DIGIT_VALUE_6 100000) - set(DIGIT_VALUE_7 1000000) - set(DIGIT_VALUE_8 10000000) - set(PLATFORM_ID) - set(ARCHITECTURE_ID) - set(SIMULATE_ID) - set(SIMULATE_VERSION) - foreach(encoding "" "ENCODING;UTF-16LE" "ENCODING;UTF-16BE") - file(STRINGS "${file}" CMAKE_${lang}_COMPILER_ID_STRINGS - LIMIT_COUNT 38 ${encoding} - REGEX ".?I.?N.?F.?O.?:.?[A-Za-z0-9_]+\\[[^]]*\\]") - if(NOT CMAKE_${lang}_COMPILER_ID_STRINGS STREQUAL "") - break() - endif() - endforeach() - set(COMPILER_ID_TWICE) - # With the IAR Compiler, some strings are found twice, first time as incomplete - # list like "?<Constant "INFO:compiler[IAR]">". Remove the incomplete copies. - list(FILTER CMAKE_${lang}_COMPILER_ID_STRINGS EXCLUDE REGEX "\\?<Constant \\\"") - # In C# binaries, some strings are found more than once. - list(REMOVE_DUPLICATES CMAKE_${lang}_COMPILER_ID_STRINGS) - foreach(info ${CMAKE_${lang}_COMPILER_ID_STRINGS}) - # The IAR-AVR compiler uses a binary format that places a '6' - # character (0x34) before each character in the string. Strip - # out these characters without removing any legitamate characters. - if("${info}" MATCHES "(.)I.N.F.O.:.") - string(REGEX REPLACE "${CMAKE_MATCH_1}(.)" "\\1" info "${info}") - endif() - if("${info}" MATCHES "INFO:compiler\\[([^]\"]*)\\]") - if(COMPILER_ID) - set(COMPILER_ID_TWICE 1) - endif() - set(COMPILER_ID "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:platform\\[([^]\"]*)\\]") - set(PLATFORM_ID "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:arch\\[([^]\"]*)\\]") - set(ARCHITECTURE_ID "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:compiler_version\\[([^]\"]*)\\]") - string(REGEX REPLACE "^0+([0-9]+)" "\\1" COMPILER_VERSION "${CMAKE_MATCH_1}") - string(REGEX REPLACE "\\.0+([0-9])" ".\\1" COMPILER_VERSION "${COMPILER_VERSION}") - endif() - if("${info}" MATCHES "INFO:compiler_version_internal\\[([^]\"]*)\\]") - string(REGEX REPLACE "^0+([0-9])" "\\1" COMPILER_VERSION_INTERNAL "${CMAKE_MATCH_1}") - string(REGEX REPLACE "\\.0+([0-9])" ".\\1" COMPILER_VERSION_INTERNAL "${COMPILER_VERSION_INTERNAL}") - endif() - foreach(comp MAJOR MINOR PATCH TWEAK) - foreach(digit 1 2 3 4 5 6 7 8 9) - if("${info}" MATCHES "INFO:compiler_version_${comp}_digit_${digit}\\[([0-9])\\]") - set(value ${CMAKE_MATCH_1}) - math(EXPR COMPILER_VERSION_${comp} "${COMPILER_VERSION_${comp}} + ${value} * ${DIGIT_VALUE_${digit}}") - set(HAVE_COMPILER_VERSION_${comp} 1) - endif() - endforeach() - endforeach() - if("${info}" MATCHES "INFO:compiler_wrapper\\[([^]\"]*)\\]") - set(COMPILER_WRAPPER "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:simulate\\[([^]\"]*)\\]") - set(SIMULATE_ID "${CMAKE_MATCH_1}") - endif() - if("${info}" MATCHES "INFO:simulate_version\\[([^]\"]*)\\]") - string(REGEX REPLACE "^0+([0-9])" "\\1" SIMULATE_VERSION "${CMAKE_MATCH_1}") - string(REGEX REPLACE "\\.0+([0-9])" ".\\1" SIMULATE_VERSION "${SIMULATE_VERSION}") - endif() - if("${info}" MATCHES "INFO:qnxnto\\[\\]") - set(COMPILER_QNXNTO 1) - endif() - if("${info}" MATCHES "INFO:dialect_default\\[([^]\"]*)\\]") - set(CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT "${CMAKE_MATCH_1}") - endif() - endforeach() - - # Construct compiler version from components if needed. - if(NOT DEFINED COMPILER_VERSION AND HAVE_COMPILER_VERSION_MAJOR) - set(COMPILER_VERSION "${COMPILER_VERSION_MAJOR}") - if(HAVE_COMPILER_VERSION_MINOR) - string(APPEND COMPILER_VERSION ".${COMPILER_VERSION_MINOR}") - if(HAVE_COMPILER_VERSION_PATCH) - string(APPEND COMPILER_VERSION ".${COMPILER_VERSION_PATCH}") - if(HAVE_COMPILER_VERSION_TWEAK) - string(APPEND COMPILER_VERSION ".${COMPILER_VERSION_TWEAK}") - endif() - endif() - endif() - endif() - - # Detect the exact architecture from the PE header. - if(WIN32) - # The offset to the PE signature is stored at 0x3c. - file(READ ${file} peoffsethex LIMIT 1 OFFSET 60 HEX) - if(NOT peoffsethex STREQUAL "") - string(SUBSTRING "${peoffsethex}" 0 1 peoffsethex1) - string(SUBSTRING "${peoffsethex}" 1 1 peoffsethex2) - set(peoffsetexpression "${peoffsethex1} * 16 + ${peoffsethex2}") - string(REPLACE "a" "10" peoffsetexpression "${peoffsetexpression}") - string(REPLACE "b" "11" peoffsetexpression "${peoffsetexpression}") - string(REPLACE "c" "12" peoffsetexpression "${peoffsetexpression}") - string(REPLACE "d" "13" peoffsetexpression "${peoffsetexpression}") - string(REPLACE "e" "14" peoffsetexpression "${peoffsetexpression}") - string(REPLACE "f" "15" peoffsetexpression "${peoffsetexpression}") - math(EXPR peoffset "${peoffsetexpression}") - - file(READ ${file} peheader LIMIT 6 OFFSET ${peoffset} HEX) - if(peheader STREQUAL "50450000a201") - set(ARCHITECTURE_ID "SH3") - elseif(peheader STREQUAL "50450000a301") - set(ARCHITECTURE_ID "SH3DSP") - elseif(peheader STREQUAL "50450000a601") - set(ARCHITECTURE_ID "SH4") - elseif(peheader STREQUAL "50450000a801") - set(ARCHITECTURE_ID "SH5") - endif() - endif() - endif() - - # Check if a valid compiler and platform were found. - if(COMPILER_ID AND NOT COMPILER_ID_TWICE) - set(CMAKE_${lang}_COMPILER_ID "${COMPILER_ID}") - set(CMAKE_${lang}_PLATFORM_ID "${PLATFORM_ID}") - set(CMAKE_${lang}_COMPILER_ARCHITECTURE_ID "${ARCHITECTURE_ID}") - set(MSVC_${lang}_ARCHITECTURE_ID "${ARCHITECTURE_ID}") - set(CMAKE_${lang}_COMPILER_VERSION "${COMPILER_VERSION}") - set(CMAKE_${lang}_COMPILER_VERSION_INTERNAL "${COMPILER_VERSION_INTERNAL}") - set(CMAKE_${lang}_SIMULATE_ID "${SIMULATE_ID}") - set(CMAKE_${lang}_SIMULATE_VERSION "${SIMULATE_VERSION}") - endif() - - # Check the compiler identification string. - if(CMAKE_${lang}_COMPILER_ID) - # The compiler identification was found. - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "The ${lang} compiler identification is ${CMAKE_${lang}_COMPILER_ID}, found in \"" - "${file}\"\n\n") - else() - # The compiler identification could not be found. - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "The ${lang} compiler identification could not be found in \"" - "${file}\"\n\n") - endif() - endif() - - # try to figure out the executable format: ELF, COFF, Mach-O - if(NOT CMAKE_EXECUTABLE_FORMAT) - file(READ ${file} CMAKE_EXECUTABLE_MAGIC LIMIT 4 HEX) - - # ELF files start with 0x7f"ELF" - if("${CMAKE_EXECUTABLE_MAGIC}" STREQUAL "7f454c46") - set(CMAKE_EXECUTABLE_FORMAT "ELF" CACHE INTERNAL "Executable file format") - endif() - -# # COFF (.exe) files start with "MZ" -# if("${CMAKE_EXECUTABLE_MAGIC}" MATCHES "4d5a....") -# set(CMAKE_EXECUTABLE_FORMAT "COFF" CACHE STRING "Executable file format") -# endif() -# - # Mach-O files start with MH_MAGIC or MH_CIGAM - if("${CMAKE_EXECUTABLE_MAGIC}" MATCHES "feedface|cefaedfe|feedfacf|cffaedfe") - set(CMAKE_EXECUTABLE_FORMAT "MACHO" CACHE STRING "Executable file format") - endif() - - endif() - if(NOT DEFINED CMAKE_EXECUTABLE_FORMAT) - set(CMAKE_EXECUTABLE_FORMAT) - endif() - # Return the information extracted. - set(CMAKE_${lang}_COMPILER_ID "${CMAKE_${lang}_COMPILER_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_PLATFORM_ID "${CMAKE_${lang}_PLATFORM_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_ARCHITECTURE_ID "${CMAKE_${lang}_COMPILER_ARCHITECTURE_ID}" PARENT_SCOPE) - set(MSVC_${lang}_ARCHITECTURE_ID "${MSVC_${lang}_ARCHITECTURE_ID}" - PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_VERSION "${CMAKE_${lang}_COMPILER_VERSION}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_VERSION_INTERNAL "${CMAKE_${lang}_COMPILER_VERSION_INTERNAL}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_WRAPPER "${COMPILER_WRAPPER}" PARENT_SCOPE) - set(CMAKE_${lang}_SIMULATE_ID "${CMAKE_${lang}_SIMULATE_ID}" PARENT_SCOPE) - set(CMAKE_${lang}_SIMULATE_VERSION "${CMAKE_${lang}_SIMULATE_VERSION}" PARENT_SCOPE) - set(CMAKE_EXECUTABLE_FORMAT "${CMAKE_EXECUTABLE_FORMAT}" PARENT_SCOPE) - set(COMPILER_QNXNTO "${COMPILER_QNXNTO}" PARENT_SCOPE) - set(CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT "${CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT}" PARENT_SCOPE) -endfunction() - -#----------------------------------------------------------------------------- -# Function to query the compiler vendor. -# This uses a table with entries of the form -# list(APPEND CMAKE_${lang}_COMPILER_ID_VENDORS ${vendor}) -# set(CMAKE_${lang}_COMPILER_ID_VENDOR_FLAGS_${vendor} -some-vendor-flag) -# set(CMAKE_${lang}_COMPILER_ID_VENDOR_REGEX_${vendor} "Some Vendor Output") -# We try running the compiler with the flag for each vendor and -# matching its regular expression in the output. -function(CMAKE_DETERMINE_COMPILER_ID_VENDOR lang userflags) - - if(NOT CMAKE_${lang}_COMPILER_ID_DIR) - # We get here when this function is called not from within CMAKE_DETERMINE_COMPILER_ID() - # This is done e.g. for detecting the compiler ID for assemblers. - # Compute the directory in which to run the test and Create a clean working directory. - set(CMAKE_${lang}_COMPILER_ID_DIR ${CMAKE_PLATFORM_INFO_DIR}/CompilerId${lang}) - file(REMOVE_RECURSE ${CMAKE_${lang}_COMPILER_ID_DIR}) - file(MAKE_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR}) - endif() - - # Save the current LC_ALL, LC_MESSAGES, and LANG environment variables - # and set them to "C" so we get the expected output to match. - set(_orig_lc_all $ENV{LC_ALL}) - set(_orig_lc_messages $ENV{LC_MESSAGES}) - set(_orig_lang $ENV{LANG}) - set(ENV{LC_ALL} C) - set(ENV{LC_MESSAGES} C) - set(ENV{LANG} C) - - foreach(vendor ${CMAKE_${lang}_COMPILER_ID_VENDORS}) - set(flags ${CMAKE_${lang}_COMPILER_ID_VENDOR_FLAGS_${vendor}}) - set(regex ${CMAKE_${lang}_COMPILER_ID_VENDOR_REGEX_${vendor}}) - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - ${CMAKE_${lang}_COMPILER_ID_ARG1} - ${userflags} - ${flags} - WORKING_DIRECTORY ${CMAKE_${lang}_COMPILER_ID_DIR} - OUTPUT_VARIABLE output ERROR_VARIABLE output - RESULT_VARIABLE result - TIMEOUT 10 - ) - - if("${output}" MATCHES "${regex}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Checking whether the ${lang} compiler is ${vendor} using \"${flags}\" " - "matched \"${regex}\":\n${output}") - set(CMAKE_${lang}_COMPILER_ID "${vendor}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_ID_OUTPUT "${output}" PARENT_SCOPE) - set(CMAKE_${lang}_COMPILER_ID_VENDOR_MATCH "${CMAKE_MATCH_1}" PARENT_SCOPE) - break() - else() - if("${result}" MATCHES "timeout") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Checking whether the ${lang} compiler is ${vendor} using \"${flags}\" " - "terminated after 10 s due to timeout.") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Checking whether the ${lang} compiler is ${vendor} using \"${flags}\" " - "did not match \"${regex}\":\n${output}") - endif() - endif() - endforeach() - - # Restore original LC_ALL, LC_MESSAGES, and LANG - set(ENV{LC_ALL} ${_orig_lc_all}) - set(ENV{LC_MESSAGES} ${_orig_lc_messages}) - set(ENV{LANG} ${_orig_lang}) -endfunction() - -function(CMAKE_DETERMINE_MSVC_SHOWINCLUDES_PREFIX lang userflags) - # Run this MSVC-compatible compiler to detect what the /showIncludes - # option displays. We can use a C source even with the C++ compiler - # because MSVC-compatible compilers handle both and show the same output. - set(showdir ${CMAKE_BINARY_DIR}/CMakeFiles/ShowIncludes) - file(WRITE ${showdir}/foo.h "\n") - file(WRITE ${showdir}/main.c "#include \"foo.h\" \nint main(){}\n") - execute_process( - COMMAND "${CMAKE_${lang}_COMPILER}" - ${CMAKE_${lang}_COMPILER_ID_ARG1} - ${userflags} - /nologo /showIncludes /c main.c - WORKING_DIRECTORY ${showdir} - OUTPUT_VARIABLE out - ERROR_VARIABLE err - RESULT_VARIABLE res - ENCODING AUTO # cl prints in current code page - ) - if(res EQUAL 0 AND "${out}" MATCHES "(^|\n)([^:\n]*:[^:\n]*:[ \t]*)") - set(CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX "${CMAKE_MATCH_2}" PARENT_SCOPE) - else() - set(CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX "" PARENT_SCOPE) - endif() -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeDetermineFortranCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineFortranCompiler.cmake deleted file mode 100644 index 5f5a70a..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineFortranCompiler.cmake +++ /dev/null
@@ -1,305 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for Fortran programs -# NOTE, a generator may set CMAKE_Fortran_COMPILER before -# loading this file to force a compiler. -# use environment variable FC first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_FC which can be defined by a generator -# as a default compiler - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-Fortran OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-Fortran OPTIONAL) -if(NOT CMAKE_Fortran_COMPILER_NAMES) - set(CMAKE_Fortran_COMPILER_NAMES f95) -endif() - -if(${CMAKE_GENERATOR} MATCHES "Visual Studio") -elseif("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(CMAKE_Fortran_COMPILER_XCODE_TYPE sourcecode.fortran.f90) - _cmake_find_compiler_path(Fortran) -else() - if(NOT CMAKE_Fortran_COMPILER) - # prefer the environment variable CC - if(NOT $ENV{FC} STREQUAL "") - get_filename_component(CMAKE_Fortran_COMPILER_INIT $ENV{FC} PROGRAM PROGRAM_ARGS CMAKE_Fortran_FLAGS_ENV_INIT) - if(CMAKE_Fortran_FLAGS_ENV_INIT) - set(CMAKE_Fortran_COMPILER_ARG1 "${CMAKE_Fortran_FLAGS_ENV_INIT}" CACHE STRING "First argument to Fortran compiler") - endif() - if(EXISTS ${CMAKE_Fortran_COMPILER_INIT}) - else() - message(FATAL_ERROR "Could not find compiler set in environment variable FC:\n$ENV{FC}.") - endif() - endif() - - # next try prefer the compiler specified by the generator - if(CMAKE_GENERATOR_FC) - if(NOT CMAKE_Fortran_COMPILER_INIT) - set(CMAKE_Fortran_COMPILER_INIT ${CMAKE_GENERATOR_FC}) - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_Fortran_COMPILER_INIT) - # Known compilers: - # f77/f90/f95: generic compiler names - # ftn: Cray fortran compiler wrapper - # g77: GNU Fortran 77 compiler - # gfortran: putative GNU Fortran 95+ compiler (in progress) - # fort77: native F77 compiler under HP-UX (and some older Crays) - # frt: Fujitsu F77 compiler - # pathf90/pathf95/pathf2003: PathScale Fortran compiler - # pgf77/pgf90/pgf95/pgfortran: Portland Group F77/F90/F95 compilers - # flang: Flang Fortran compiler - # xlf/xlf90/xlf95: IBM (AIX) F77/F90/F95 compilers - # lf95: Lahey-Fujitsu F95 compiler - # fl32: Microsoft Fortran 77 "PowerStation" compiler - # af77: Apogee F77 compiler for Intergraph hardware running CLIX - # epcf90: "Edinburgh Portable Compiler" F90 - # fort: Compaq (now HP) Fortran 90/95 compiler for Tru64 and Linux/Alpha - # ifc: Intel Fortran 95 compiler for Linux/x86 - # efc: Intel Fortran 95 compiler for IA64 - # nagfor: NAG Fortran compiler - # - # The order is 95 or newer compilers first, then 90, - # then 77 or older compilers, gnu is always last in the group, - # so if you paid for a compiler it is picked by default. - if(CMAKE_HOST_WIN32) - set(CMAKE_Fortran_COMPILER_LIST - ifort pgf95 pgfortran lf95 fort - flang gfortran gfortran-4 g95 f90 pgf90 - pgf77 g77 f77 nag - ) - else() - set(CMAKE_Fortran_COMPILER_LIST - ftn - ifort ifc efc pgf95 pgfortran lf95 xlf95 fort - flang gfortran gfortran-4 g95 f90 pgf90 - frt pgf77 xlf g77 f77 nag - ) - endif() - - # Vendor-specific compiler names. - set(_Fortran_COMPILER_NAMES_GNU gfortran gfortran-4 g95 g77) - set(_Fortran_COMPILER_NAMES_Intel ifort ifc efc) - set(_Fortran_COMPILER_NAMES_Absoft af95 af90 af77) - set(_Fortran_COMPILER_NAMES_PGI pgf95 pgfortran pgf90 pgf77) - set(_Fortran_COMPILER_NAMES_Flang flang) - set(_Fortran_COMPILER_NAMES_PathScale pathf2003 pathf95 pathf90) - set(_Fortran_COMPILER_NAMES_XL xlf) - set(_Fortran_COMPILER_NAMES_VisualAge xlf95 xlf90 xlf) - set(_Fortran_COMPILER_NAMES_NAG nagfor) - endif() - - _cmake_find_compiler(Fortran) - - else() - _cmake_find_compiler_path(Fortran) - endif() - mark_as_advanced(CMAKE_Fortran_COMPILER) - - # Each entry in this list is a set of extra flags to try - # adding to the compile line to see if it helps produce - # a valid identification executable. - set(CMAKE_Fortran_COMPILER_ID_TEST_FLAGS_FIRST - # Get verbose output to help distinguish compilers. - "-v" - ) - set(CMAKE_Fortran_COMPILER_ID_TEST_FLAGS - # Try compiling to an object file only. - "-c" - - # Intel on windows does not preprocess by default. - "-fpp" - ) -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_Fortran_COMPILER_ID_RUN) - set(CMAKE_Fortran_COMPILER_ID_RUN 1) - - # Table of per-vendor compiler output regular expressions. - list(APPEND CMAKE_Fortran_COMPILER_ID_MATCH_VENDORS CCur) - set(CMAKE_Fortran_COMPILER_ID_MATCH_VENDOR_REGEX_CCur "Concurrent Fortran [0-9]+ Compiler") - - # Table of per-vendor compiler id flags with expected output. - list(APPEND CMAKE_Fortran_COMPILER_ID_VENDORS Compaq) - set(CMAKE_Fortran_COMPILER_ID_VENDOR_FLAGS_Compaq "-what") - set(CMAKE_Fortran_COMPILER_ID_VENDOR_REGEX_Compaq "Compaq Visual Fortran") - list(APPEND CMAKE_Fortran_COMPILER_ID_VENDORS NAG) # Numerical Algorithms Group - set(CMAKE_Fortran_COMPILER_ID_VENDOR_FLAGS_NAG "-V") - set(CMAKE_Fortran_COMPILER_ID_VENDOR_REGEX_NAG "NAG Fortran Compiler") - - # Match the link line from xcodebuild output of the form - # Ld ... - # ... - # /path/to/cc ...CompilerIdFortran/... - # to extract the compiler front-end for the language. - set(CMAKE_Fortran_COMPILER_ID_TOOL_MATCH_REGEX "\nLd[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]*-o[^\r\n]*CompilerIdFortran/(\\./)?(CompilerIdFortran.xctest/)?CompilerIdFortran[ \t\n\\\"]") - set(CMAKE_Fortran_COMPILER_ID_TOOL_MATCH_INDEX 2) - - set(_version_info "") - foreach(m MAJOR MINOR PATCH TWEAK) - set(_COMP "_${m}") - string(APPEND _version_info " -#if defined(COMPILER_VERSION${_COMP})") - foreach(d 1 2 3 4 5 6 7 8) - string(APPEND _version_info " -# undef DEC -# undef HEX -# define DEC(n) DEC_${d}(n) -# define HEX(n) HEX_${d}(n) -# if COMPILER_VERSION${_COMP} == 0 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[0]' -# elif COMPILER_VERSION${_COMP} == 1 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[1]' -# elif COMPILER_VERSION${_COMP} == 2 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[2]' -# elif COMPILER_VERSION${_COMP} == 3 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[3]' -# elif COMPILER_VERSION${_COMP} == 4 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[4]' -# elif COMPILER_VERSION${_COMP} == 5 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[5]' -# elif COMPILER_VERSION${_COMP} == 6 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[6]' -# elif COMPILER_VERSION${_COMP} == 7 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[7]' -# elif COMPILER_VERSION${_COMP} == 8 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[8]' -# elif COMPILER_VERSION${_COMP} == 9 - PRINT *, 'INFO:compiler_version${_COMP}_digit_${d}[9]' -# endif -") - endforeach() - string(APPEND _version_info " -#endif") - endforeach() - set(CMAKE_Fortran_COMPILER_ID_VERSION_INFO "${_version_info}") - unset(_version_info) - unset(_COMP) - - # Try to identify the compiler. - set(CMAKE_Fortran_COMPILER_ID) - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(Fortran FFLAGS CMakeFortranCompilerId.F) - - _cmake_find_compiler_sysroot(Fortran) - - # Fall back to old is-GNU test. - if(NOT CMAKE_Fortran_COMPILER_ID) - execute_process(COMMAND ${CMAKE_Fortran_COMPILER} ${CMAKE_Fortran_COMPILER_ID_FLAGS_LIST} -E "${CMAKE_ROOT}/Modules/CMakeTestGNU.c" - OUTPUT_VARIABLE CMAKE_COMPILER_OUTPUT RESULT_VARIABLE CMAKE_COMPILER_RETURN) - if(NOT CMAKE_COMPILER_RETURN) - if(CMAKE_COMPILER_OUTPUT MATCHES "THIS_IS_GNU") - set(CMAKE_Fortran_COMPILER_ID "GNU") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Fortran compiler is GNU succeeded with " - "the following output:\n${CMAKE_COMPILER_OUTPUT}\n\n") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Fortran compiler is GNU failed with " - "the following output:\n${CMAKE_COMPILER_OUTPUT}\n\n") - endif() - if(NOT CMAKE_Fortran_PLATFORM_ID) - if(CMAKE_COMPILER_OUTPUT MATCHES "THIS_IS_MINGW") - set(CMAKE_Fortran_PLATFORM_ID "MinGW") - endif() - if(CMAKE_COMPILER_OUTPUT MATCHES "THIS_IS_CYGWIN") - set(CMAKE_Fortran_PLATFORM_ID "Cygwin") - endif() - endif() - endif() - endif() - - # Fall back for GNU MINGW, which is not always detected correctly - # (__MINGW32__ is defined for the C language, but perhaps not for Fortran!) - if(CMAKE_Fortran_COMPILER_ID MATCHES "GNU" AND NOT CMAKE_Fortran_PLATFORM_ID) - execute_process(COMMAND ${CMAKE_Fortran_COMPILER} ${CMAKE_Fortran_COMPILER_ID_FLAGS_LIST} -E "${CMAKE_ROOT}/Modules/CMakeTestGNU.c" - OUTPUT_VARIABLE CMAKE_COMPILER_OUTPUT RESULT_VARIABLE CMAKE_COMPILER_RETURN) - if(NOT CMAKE_COMPILER_RETURN) - if(CMAKE_COMPILER_OUTPUT MATCHES "THIS_IS_MINGW") - set(CMAKE_Fortran_PLATFORM_ID "MinGW") - endif() - if(CMAKE_COMPILER_OUTPUT MATCHES "THIS_IS_CYGWIN") - set(CMAKE_Fortran_PLATFORM_ID "Cygwin") - endif() - endif() - endif() - - # Set old compiler and platform id variables. - if(CMAKE_Fortran_COMPILER_ID MATCHES "GNU") - set(CMAKE_COMPILER_IS_GNUG77 1) - endif() - if(CMAKE_Fortran_PLATFORM_ID MATCHES "MinGW") - set(CMAKE_COMPILER_IS_MINGW 1) - elseif(CMAKE_Fortran_PLATFORM_ID MATCHES "Cygwin") - set(CMAKE_COMPILER_IS_CYGWIN 1) - endif() -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_Fortran_COMPILER}" PATH) -endif () - -# if we have a fortran cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-gfortran, arm-elf-gfortran or i586-mingw32msvc-gfortran , optionally -# with a 3-component version number at the end (e.g. arm-eabi-gcc-4.5.2). -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gcc.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - - if(CMAKE_Fortran_COMPILER_ID MATCHES "GNU") - get_filename_component(COMPILER_BASENAME "${CMAKE_Fortran_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)g?fortran(-[0-9]+\\.[0-9]+\\.[0-9]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - - # if "llvm-" is part of the prefix, remove it, since llvm doesn't have its own binutils - # but uses the regular ar, objcopy, etc. (instead of llvm-objcopy etc.) - if ("${_CMAKE_TOOLCHAIN_PREFIX}" MATCHES "(.+-)?llvm-$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - endif() - -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "Fortran") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_Fortran_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(CMAKE_Fortran_XL_CPP) - set(_SET_CMAKE_Fortran_XL_CPP - "set(CMAKE_Fortran_XL_CPP \"${CMAKE_Fortran_XL_CPP}\")") -endif() - -if(CMAKE_Fortran_COMPILER_SYSROOT) - string(CONCAT _SET_CMAKE_Fortran_COMPILER_SYSROOT - "set(CMAKE_Fortran_COMPILER_SYSROOT \"${CMAKE_Fortran_COMPILER_SYSROOT}\")\n" - "set(CMAKE_COMPILER_SYSROOT \"${CMAKE_Fortran_COMPILER_SYSROOT}\")") -else() - set(_SET_CMAKE_Fortran_COMPILER_SYSROOT "") -endif() - -if(CMAKE_Fortran_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_Fortran_COMPILER_ARCHITECTURE_ID - "set(CMAKE_Fortran_COMPILER_ARCHITECTURE_ID ${CMAKE_Fortran_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_Fortran_COMPILER_ARCHITECTURE_ID "") -endif() - -if(MSVC_Fortran_ARCHITECTURE_ID) - set(SET_MSVC_Fortran_ARCHITECTURE_ID - "set(MSVC_Fortran_ARCHITECTURE_ID ${MSVC_Fortran_ARCHITECTURE_ID})") -endif() -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeFortranCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeFortranCompiler.cmake - @ONLY - ) -set(CMAKE_Fortran_COMPILER_ENV_VAR "FC")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineJavaCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineJavaCompiler.cmake deleted file mode 100644 index 3092bb5..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineJavaCompiler.cmake +++ /dev/null
@@ -1,94 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for Java programs -# NOTE, a generator may set CMAKE_Java_COMPILER before -# loading this file to force a compiler. - -if(NOT CMAKE_Java_COMPILER) - # prefer the environment variable CC - if(NOT $ENV{JAVA_COMPILER} STREQUAL "") - get_filename_component(CMAKE_Java_COMPILER_INIT $ENV{JAVA_COMPILER} PROGRAM PROGRAM_ARGS CMAKE_Java_FLAGS_ENV_INIT) - if(CMAKE_Java_FLAGS_ENV_INIT) - set(CMAKE_Java_COMPILER_ARG1 "${CMAKE_Java_FLAGS_ENV_INIT}" CACHE STRING "First argument to Java compiler") - endif() - if(NOT EXISTS ${CMAKE_Java_COMPILER_INIT}) - message(SEND_ERROR "Could not find compiler set in environment variable JAVA_COMPILER:\n$ENV{JAVA_COMPILER}.") - endif() - endif() - - if(NOT $ENV{JAVA_RUNTIME} STREQUAL "") - get_filename_component(CMAKE_Java_RUNTIME_INIT $ENV{JAVA_RUNTIME} PROGRAM PROGRAM_ARGS CMAKE_Java_FLAGS_ENV_INIT) - if(NOT EXISTS ${CMAKE_Java_RUNTIME_INIT}) - message(SEND_ERROR "Could not find compiler set in environment variable JAVA_RUNTIME:\n$ENV{JAVA_RUNTIME}.") - endif() - endif() - - if(NOT $ENV{JAVA_ARCHIVE} STREQUAL "") - get_filename_component(CMAKE_Java_ARCHIVE_INIT $ENV{JAVA_ARCHIVE} PROGRAM PROGRAM_ARGS CMAKE_Java_FLAGS_ENV_INIT) - if(NOT EXISTS ${CMAKE_Java_ARCHIVE_INIT}) - message(SEND_ERROR "Could not find compiler set in environment variable JAVA_ARCHIVE:\n$ENV{JAVA_ARCHIVE}.") - endif() - endif() - - set(Java_BIN_PATH - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\2.0;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.9;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.8;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.7;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.6;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.5;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.4;JavaHome]/bin" - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Development Kit\\1.3;JavaHome]/bin" - $ENV{JAVA_HOME}/bin - /usr/bin - /usr/lib/java/bin - /usr/share/java/bin - /usr/local/bin - /usr/local/java/bin - /usr/local/java/share/bin - /usr/java/j2sdk1.4.2_04 - /usr/lib/j2sdk1.4-sun/bin - /usr/java/j2sdk1.4.2_09/bin - /usr/lib/j2sdk1.5-sun/bin - /opt/sun-jdk-1.5.0.04/bin - /usr/local/jdk-1.7.0/bin - /usr/local/jdk-1.6.0/bin - ) - # if no compiler has been specified yet, then look for one - if(CMAKE_Java_COMPILER_INIT) - set(CMAKE_Java_COMPILER ${CMAKE_Java_COMPILER_INIT} CACHE PATH "Java Compiler") - else() - find_program(CMAKE_Java_COMPILER - NAMES javac - PATHS ${Java_BIN_PATH} - ) - endif() - - # if no runtime has been specified yet, then look for one - if(CMAKE_Java_RUNTIME_INIT) - set(CMAKE_Java_RUNTIME ${CMAKE_Java_RUNTIME_INIT} CACHE PATH "Java Compiler") - else() - find_program(CMAKE_Java_RUNTIME - NAMES java - PATHS ${Java_BIN_PATH} - ) - endif() - - # if no archive has been specified yet, then look for one - if(CMAKE_Java_ARCHIVE_INIT) - set(CMAKE_Java_ARCHIVE ${CMAKE_Java_ARCHIVE_INIT} CACHE PATH "Java Compiler") - else() - find_program(CMAKE_Java_ARCHIVE - NAMES jar - PATHS ${Java_BIN_PATH} - ) - endif() -endif() -mark_as_advanced(CMAKE_Java_COMPILER) - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeJavaCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeJavaCompiler.cmake @ONLY) -set(CMAKE_Java_COMPILER_ENV_VAR "JAVA_COMPILER")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineOBJCCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineOBJCCompiler.cmake deleted file mode 100644 index 11b47fd..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineOBJCCompiler.cmake +++ /dev/null
@@ -1,192 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for Objective-C programs -# NOTE, a generator may set CMAKE_OBJC_COMPILER before -# loading this file to force a compiler. -# use environment variable OBJC first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_OBJC which can be defined by a generator -# as a default compiler -# -# Sets the following variables: -# CMAKE_OBJC_COMPILER -# CMAKE_AR -# CMAKE_RANLIB -# CMAKE_COMPILER_IS_GNUOBJC -# CMAKE_COMPILER_IS_CLANGOBJC -# -# If not already set before, it also sets -# _CMAKE_TOOLCHAIN_PREFIX - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -# Load system-specific compiler preferences for this language. -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-OBJC OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-OBJC OPTIONAL) -if(NOT CMAKE_OBJC_COMPILER_NAMES) - set(CMAKE_OBJC_COMPILER_NAMES clang) -endif() - -if("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(CMAKE_OBJC_COMPILER_XCODE_TYPE sourcecode.c.objc) -else() - if(NOT CMAKE_OBJC_COMPILER) - set(CMAKE_OBJC_COMPILER_INIT NOTFOUND) - - # prefer the environment variable OBJC or CC - foreach(var OBJC CC) - if($ENV{${var}} MATCHES ".+") - get_filename_component(CMAKE_OBJC_COMPILER_INIT $ENV{${var}} PROGRAM PROGRAM_ARGS CMAKE_OBJC_FLAGS_ENV_INIT) - if(CMAKE_OBJC_FLAGS_ENV_INIT) - set(CMAKE_OBJC_COMPILER_ARG1 "${CMAKE_OBJC_FLAGS_ENV_INIT}" CACHE STRING "First argument to Objective-C compiler") - endif() - if(NOT EXISTS ${CMAKE_OBJC_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable ${var}:\n $ENV{${var}}") - endif() - break() - endif() - endforeach() - - # next try prefer the compiler specified by the generator - if(CMAKE_GENERATOR_OBJC) - if(NOT CMAKE_OBJC_COMPILER_INIT) - set(CMAKE_OBJC_COMPILER_INIT ${CMAKE_GENERATOR_OBJC}) - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_OBJC_COMPILER_INIT) - set(CMAKE_OBJC_COMPILER_LIST ${_CMAKE_TOOLCHAIN_PREFIX}cc ${_CMAKE_TOOLCHAIN_PREFIX}gcc clang) - endif() - - _cmake_find_compiler(OBJC) - - else() - # we only get here if CMAKE_OBJC_COMPILER was specified using -D or a pre-made CMakeCache.txt - # (e.g. via ctest) or set in CMAKE_TOOLCHAIN_FILE - # if CMAKE_OBJC_COMPILER is a list of length 2, use the first item as - # CMAKE_OBJC_COMPILER and the 2nd one as CMAKE_OBJC_COMPILER_ARG1 - - list(LENGTH CMAKE_OBJC_COMPILER _CMAKE_OBJC_COMPILER_LIST_LENGTH) - if("${_CMAKE_OBJC_COMPILER_LIST_LENGTH}" EQUAL 2) - list(GET CMAKE_OBJC_COMPILER 1 CMAKE_OBJC_COMPILER_ARG1) - list(GET CMAKE_OBJC_COMPILER 0 CMAKE_OBJC_COMPILER) - endif() - - # if a compiler was specified by the user but without path, - # now try to find it with the full path - # if it is found, force it into the cache, - # if not, don't overwrite the setting (which was given by the user) with "NOTFOUND" - # if the C compiler already had a path, reuse it for searching the CXX compiler - get_filename_component(_CMAKE_USER_OBJC_COMPILER_PATH "${CMAKE_OBJC_COMPILER}" PATH) - if(NOT _CMAKE_USER_OBJC_COMPILER_PATH) - find_program(CMAKE_OBJC_COMPILER_WITH_PATH NAMES ${CMAKE_OBJC_COMPILER}) - if(CMAKE_OBJC_COMPILER_WITH_PATH) - set(CMAKE_OBJC_COMPILER ${CMAKE_OBJC_COMPILER_WITH_PATH} CACHE STRING "Objective-C compiler" FORCE) - endif() - unset(CMAKE_OBJC_COMPILER_WITH_PATH CACHE) - endif() - endif() - mark_as_advanced(CMAKE_OBJC_COMPILER) - - # Each entry in this list is a set of extra flags to try - # adding to the compile line to see if it helps produce - # a valid identification file. - set(CMAKE_OBJC_COMPILER_ID_TEST_FLAGS_FIRST) - set(CMAKE_OBJC_COMPILER_ID_TEST_FLAGS - # Try compiling to an object file only. - "-c" - - ) -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_OBJC_COMPILER_ID_RUN) - set(CMAKE_OBJC_COMPILER_ID_RUN 1) - - # Try to identify the compiler. - set(CMAKE_OBJC_COMPILER_ID) - file(READ ${CMAKE_ROOT}/Modules/CMakePlatformId.h.in - CMAKE_OBJC_COMPILER_ID_PLATFORM_CONTENT) - - # Match the link line from xcodebuild output of the form - # Ld ... - # ... - # /path/to/cc ...CompilerIdOBJC/... - # to extract the compiler front-end for the language. - set(CMAKE_OBJC_COMPILER_ID_TOOL_MATCH_REGEX "\nLd[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]*-o[^\r\n]*CompilerIdOBJC/(\\./)?(CompilerIdOBJC.(framework|xctest)/)?CompilerIdOBJC[ \t\n\\\"]") - set(CMAKE_OBJC_COMPILER_ID_TOOL_MATCH_INDEX 2) - - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(OBJC OBJCCFLAGS CMakeOBJCCompilerId.m) - - # Set old compiler and platform id variables. - if(CMAKE_OBJC_COMPILER_ID STREQUAL "GNU") - set(CMAKE_COMPILER_IS_GNUOBJC 1) - endif() - if(CMAKE_OBJC_COMPILER_ID STREQUAL "Clang") - set(CMAKE_COMPILER_IS_CLANGOBJC 1) - endif() -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_OBJC_COMPILER}" PATH) -endif () - -# If we have a gcc cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-gcc, arm-elf-gcc or i586-mingw32msvc-gcc, optionally -# with a 3-component version number at the end (e.g. arm-eabi-gcc-4.5.2). -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gcc.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" -if (CMAKE_CROSSCOMPILING AND NOT _CMAKE_TOOLCHAIN_PREFIX) - - if(CMAKE_OBJC_COMPILER_ID MATCHES "GNU|Clang|QCC") - get_filename_component(COMPILER_BASENAME "${CMAKE_OBJC_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)(clang|g?cc)(-[0-9]+(\\.[0-9]+)*)?(-[^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - set(_CMAKE_COMPILER_SUFFIX ${CMAKE_MATCH_5}) - elseif(CMAKE_OBJC_COMPILER_ID MATCHES "Clang") - if(CMAKE_OBJC_COMPILER_TARGET) - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_OBJC_COMPILER_TARGET}-) - endif() - elseif(COMPILER_BASENAME MATCHES "qcc(\\.exe)?$") - if(CMAKE_OBJC_COMPILER_TARGET MATCHES "gcc_nto([a-z0-9]+_[0-9]+|[^_le]+)(le)?") - set(_CMAKE_TOOLCHAIN_PREFIX nto${CMAKE_MATCH_1}-) - endif() - endif () - - # if "llvm-" is part of the prefix, remove it, since llvm doesn't have its own binutils - # but uses the regular ar, objcopy, etc. (instead of llvm-objcopy etc.) - if ("${_CMAKE_TOOLCHAIN_PREFIX}" MATCHES "(.+-)?llvm-$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - endif() - -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "OBJC") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_OBJC_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(CMAKE_OBJC_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_OBJC_COMPILER_ARCHITECTURE_ID - "set(CMAKE_OBJC_COMPILER_ARCHITECTURE_ID ${CMAKE_OBJC_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_OBJC_COMPILER_ARCHITECTURE_ID "") -endif() - -if(CMAKE_OBJC_XCODE_ARCHS) - set(SET_CMAKE_XCODE_ARCHS - "set(CMAKE_XCODE_ARCHS \"${CMAKE_OBJC_XCODE_ARCHS}\")") -endif() - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeOBJCCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCCompiler.cmake - @ONLY - ) -set(CMAKE_OBJC_COMPILER_ENV_VAR "OBJC")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineOBJCXXCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineOBJCXXCompiler.cmake deleted file mode 100644 index 99ad6c3..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineOBJCXXCompiler.cmake +++ /dev/null
@@ -1,200 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for Objective-C++ programs -# NOTE, a generator may set CMAKE_OBJCXX_COMPILER before -# loading this file to force a compiler. -# use environment variable OBJCXX first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_OBJCXX which can be defined by a generator -# as a default compiler -# If the internal cmake variable _CMAKE_TOOLCHAIN_PREFIX is set, this is used -# as prefix for the tools (e.g. arm-elf-g++, arm-elf-ar etc.) -# -# Sets the following variables: -# CMAKE_OBJCXX_COMPILER -# CMAKE_COMPILER_IS_GNUOBJCXX -# CMAKE_COMPILER_IS_CLANGOBJCXX -# CMAKE_AR -# CMAKE_RANLIB -# -# If not already set before, it also sets -# _CMAKE_TOOLCHAIN_PREFIX - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -# Load system-specific compiler preferences for this language. -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-OBJCXX OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-OBJCXX OPTIONAL) -if(NOT CMAKE_OBJCXX_COMPILER_NAMES) - set(CMAKE_OBJCXX_COMPILER_NAMES clang++) -endif() - -if("${CMAKE_GENERATOR}" MATCHES "Xcode") - set(CMAKE_OBJCXX_COMPILER_XCODE_TYPE sourcecode.cpp.objcpp) -else() - if(NOT CMAKE_OBJCXX_COMPILER) - set(CMAKE_OBJCXX_COMPILER_INIT NOTFOUND) - - # prefer the environment variable OBJCXX or CXX - foreach(var OBJCXX CXX) - if($ENV{${var}} MATCHES ".+") - get_filename_component(CMAKE_OBJCXX_COMPILER_INIT $ENV{${var}} PROGRAM PROGRAM_ARGS CMAKE_OBJCXX_FLAGS_ENV_INIT) - if(CMAKE_OBJCXX_FLAGS_ENV_INIT) - set(CMAKE_OBJCXX_COMPILER_ARG1 "${CMAKE_OBJCXX_FLAGS_ENV_INIT}" CACHE STRING "First argument to Objective-C++ compiler") - endif() - if(NOT EXISTS ${CMAKE_OBJCXX_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable ${var}:\n $ENV{${var}}") - endif() - break() - endif() - endforeach() - - # next prefer the generator specified compiler - if(CMAKE_GENERATOR_OBJCXX) - if(NOT CMAKE_OBJCXX_COMPILER_INIT) - set(CMAKE_OBJCXX_COMPILER_INIT ${CMAKE_GENERATOR_OBJCXX}) - endif() - endif() - - # finally list compilers to try - if(NOT CMAKE_OBJCXX_COMPILER_INIT) - set(CMAKE_OBJCXX_COMPILER_LIST ${_CMAKE_TOOLCHAIN_PREFIX}c++ ${_CMAKE_TOOLCHAIN_PREFIX}g++ clang++) - endif() - - _cmake_find_compiler(OBJCXX) - - else() - # we only get here if CMAKE_OBJCXX_COMPILER was specified using -D or a pre-made CMakeCache.txt - # (e.g. via ctest) or set in CMAKE_TOOLCHAIN_FILE - # if CMAKE_OBJCXX_COMPILER is a list of length 2, use the first item as - # CMAKE_OBJCXX_COMPILER and the 2nd one as CMAKE_OBJCXX_COMPILER_ARG1 - - list(LENGTH CMAKE_OBJCXX_COMPILER _CMAKE_OBJCXX_COMPILER_LIST_LENGTH) - if("${_CMAKE_OBJCXX_COMPILER_LIST_LENGTH}" EQUAL 2) - list(GET CMAKE_OBJCXX_COMPILER 1 CMAKE_OBJCXX_COMPILER_ARG1) - list(GET CMAKE_OBJCXX_COMPILER 0 CMAKE_OBJCXX_COMPILER) - endif() - - # if a compiler was specified by the user but without path, - # now try to find it with the full path - # if it is found, force it into the cache, - # if not, don't overwrite the setting (which was given by the user) with "NOTFOUND" - # if the C compiler already had a path, reuse it for searching the CXX compiler - get_filename_component(_CMAKE_USER_OBJCXX_COMPILER_PATH "${CMAKE_OBJCXX_COMPILER}" PATH) - if(NOT _CMAKE_USER_OBJCXX_COMPILER_PATH) - find_program(CMAKE_OBJCXX_COMPILER_WITH_PATH NAMES ${CMAKE_OBJCXX_COMPILER}) - if(CMAKE_OBJCXX_COMPILER_WITH_PATH) - set(CMAKE_OBJCXX_COMPILER ${CMAKE_OBJCXX_COMPILER_WITH_PATH} CACHE STRING "Objective-C++ compiler" FORCE) - endif() - unset(CMAKE_OBJCXX_COMPILER_WITH_PATH CACHE) - endif() - - endif() - mark_as_advanced(CMAKE_OBJCXX_COMPILER) - - # Each entry in this list is a set of extra flags to try - # adding to the compile line to see if it helps produce - # a valid identification file. - set(CMAKE_OBJCXX_COMPILER_ID_TEST_FLAGS_FIRST) - set(CMAKE_OBJCXX_COMPILER_ID_TEST_FLAGS - # Try compiling to an object file only. - "-c" - - # ARMClang need target options - "--target=arm-arm-none-eabi -mcpu=cortex-m3" - ) -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_OBJCXX_COMPILER_ID_RUN) - set(CMAKE_OBJCXX_COMPILER_ID_RUN 1) - - # Try to identify the compiler. - set(CMAKE_OBJCXX_COMPILER_ID) - file(READ ${CMAKE_ROOT}/Modules/CMakePlatformId.h.in - CMAKE_OBJCXX_COMPILER_ID_PLATFORM_CONTENT) - - # Match the link line from xcodebuild output of the form - # Ld ... - # ... - # /path/to/cc ...CompilerIdOBJCXX/... - # to extract the compiler front-end for the language. - set(CMAKE_OBJCXX_COMPILER_ID_TOOL_MATCH_REGEX "\nLd[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]*-o[^\r\n]*CompilerIdOBJCXX/(\\./)?(CompilerIdOBJCXX.(framework|xctest)/)?CompilerIdOBJCXX[ \t\n\\\"]") - set(CMAKE_OBJCXX_COMPILER_ID_TOOL_MATCH_INDEX 2) - - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(OBJCXX OBJCXXFLAGS CMakeOBJCXXCompilerId.mm) - - # Set old compiler and platform id variables. - if(CMAKE_OBJCXX_COMPILER_ID MATCHES "GNU") - set(CMAKE_COMPILER_IS_GNUOBJCXX 1) - endif() - if(CMAKE_OBJCXX_COMPILER_ID MATCHES "Clang") - set(CMAKE_COMPILER_IS_CLANGOBJCXX 1) - endif() -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_OBJCXX_COMPILER}" PATH) -endif () - -# if we have a g++ cross compiler, they have usually some prefix, like -# e.g. powerpc-linux-g++, arm-elf-g++ or i586-mingw32msvc-g++ , optionally -# with a 3-component version number at the end (e.g. arm-eabi-gcc-4.5.2). -# The other tools of the toolchain usually have the same prefix -# NAME_WE cannot be used since then this test will fail for names like -# "arm-unknown-nto-qnx6.3.0-gcc.exe", where BASENAME would be -# "arm-unknown-nto-qnx6" instead of the correct "arm-unknown-nto-qnx6.3.0-" - - -if (NOT _CMAKE_TOOLCHAIN_PREFIX) - - if("${CMAKE_OBJCXX_COMPILER_ID}" MATCHES "GNU|Clang|QCC") - get_filename_component(COMPILER_BASENAME "${CMAKE_OBJCXX_COMPILER}" NAME) - if (COMPILER_BASENAME MATCHES "^(.+-)(clan)?[gc]\\+\\+(-[0-9]+(\\.[0-9]+)*)?(-[^.]+)?(\\.exe)?$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - set(_CMAKE_COMPILER_SUFFIX ${CMAKE_MATCH_5}) - elseif("${CMAKE_OBJCXX_COMPILER_ID}" MATCHES "Clang") - if(CMAKE_OBJCXX_COMPILER_TARGET) - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_OBJCXX_COMPILER_TARGET}-) - endif() - elseif(COMPILER_BASENAME MATCHES "QCC(\\.exe)?$") - if(CMAKE_OBJCXX_COMPILER_TARGET MATCHES "gcc_nto([a-z0-9]+_[0-9]+|[^_le]+)(le)") - set(_CMAKE_TOOLCHAIN_PREFIX nto${CMAKE_MATCH_1}-) - endif() - endif () - - # if "llvm-" is part of the prefix, remove it, since llvm doesn't have its own binutils - # but uses the regular ar, objcopy, etc. (instead of llvm-objcopy etc.) - if ("${_CMAKE_TOOLCHAIN_PREFIX}" MATCHES "(.+-)?llvm-$") - set(_CMAKE_TOOLCHAIN_PREFIX ${CMAKE_MATCH_1}) - endif () - endif() - -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "OBJCXX") -include(CMakeFindBinUtils) -include(Compiler/${CMAKE_OBJCXX_COMPILER_ID}-FindBinUtils OPTIONAL) -unset(_CMAKE_PROCESSING_LANGUAGE) - -if(CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID) - set(_SET_CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID - "set(CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID ${CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID})") -else() - set(_SET_CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID "") -endif() - -if(CMAKE_OBJCXX_XCODE_ARCHS) - set(SET_CMAKE_XCODE_ARCHS - "set(CMAKE_XCODE_ARCHS \"${CMAKE_OBJCXX_XCODE_ARCHS}\")") -endif() - -# configure all variables set in this file -configure_file(${CMAKE_ROOT}/Modules/CMakeOBJCXXCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCXXCompiler.cmake - @ONLY - ) - -set(CMAKE_OBJCXX_COMPILER_ENV_VAR "OBJCXX")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineRCCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineRCCompiler.cmake deleted file mode 100644 index 8801e16..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineRCCompiler.cmake +++ /dev/null
@@ -1,57 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# determine the compiler to use for RC programs -# NOTE, a generator may set CMAKE_RC_COMPILER before -# loading this file to force a compiler. -# use environment variable RC first if defined by user, next use -# the cmake variable CMAKE_GENERATOR_RC which can be defined by a generator -# as a default compiler -if(NOT CMAKE_RC_COMPILER) - # prefer the environment variable RC - if(NOT $ENV{RC} STREQUAL "") - get_filename_component(CMAKE_RC_COMPILER_INIT $ENV{RC} PROGRAM PROGRAM_ARGS CMAKE_RC_FLAGS_ENV_INIT) - if(CMAKE_RC_FLAGS_ENV_INIT) - set(CMAKE_RC_COMPILER_ARG1 "${CMAKE_RC_FLAGS_ENV_INIT}" CACHE STRING "First argument to RC compiler") - endif() - if(EXISTS ${CMAKE_RC_COMPILER_INIT}) - else() - message(FATAL_ERROR "Could not find compiler set in environment variable RC:\n$ENV{RC}.") - endif() - endif() - - # next try prefer the compiler specified by the generator - if(CMAKE_GENERATOR_RC) - if(NOT CMAKE_RC_COMPILER_INIT) - set(CMAKE_RC_COMPILER_INIT ${CMAKE_GENERATOR_RC}) - endif() - endif() - - # finally list compilers to try - if(CMAKE_RC_COMPILER_INIT) - set(CMAKE_RC_COMPILER_LIST ${CMAKE_RC_COMPILER_INIT}) - else() - set(CMAKE_RC_COMPILER_LIST rc) - endif() - - # Find the compiler. - find_program(CMAKE_RC_COMPILER NAMES ${CMAKE_RC_COMPILER_LIST} DOC "RC compiler") - if(CMAKE_RC_COMPILER_INIT AND NOT CMAKE_RC_COMPILER) - set(CMAKE_RC_COMPILER "${CMAKE_RC_COMPILER_INIT}" CACHE FILEPATH "RC compiler" FORCE) - endif() -endif() - -mark_as_advanced(CMAKE_RC_COMPILER) - -get_filename_component(_CMAKE_RC_COMPILER_NAME_WE ${CMAKE_RC_COMPILER} NAME_WE) -if(_CMAKE_RC_COMPILER_NAME_WE STREQUAL "windres") - set(CMAKE_RC_OUTPUT_EXTENSION .obj) -else() - set(CMAKE_RC_OUTPUT_EXTENSION .res) -endif() - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeRCCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeRCCompiler.cmake) -set(CMAKE_RC_COMPILER_ENV_VAR "RC")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineSwiftCompiler.cmake b/share/cmake-3.18/Modules/CMakeDetermineSwiftCompiler.cmake deleted file mode 100644 index 688133f..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineSwiftCompiler.cmake +++ /dev/null
@@ -1,78 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompiler.cmake) - -# Local system-specific compiler preferences for this language. -include(Platform/${CMAKE_SYSTEM_NAME}-Determine-Swift OPTIONAL) -include(Platform/${CMAKE_SYSTEM_NAME}-Swift OPTIONAL) -if(NOT CMAKE_Swift_COMPILER_NAMES) - set(CMAKE_Swift_COMPILER_NAMES swiftc) -endif() - -if("${CMAKE_GENERATOR}" STREQUAL "Xcode") - if(XCODE_VERSION VERSION_LESS 6.1) - message(FATAL_ERROR "Swift language not supported by Xcode ${XCODE_VERSION}") - endif() - set(CMAKE_Swift_COMPILER_XCODE_TYPE sourcecode.swift) - _cmake_find_compiler_path(Swift) -elseif("${CMAKE_GENERATOR}" MATCHES "^Ninja") - if(CMAKE_Swift_COMPILER) - _cmake_find_compiler_path(Swift) - else() - set(CMAKE_Swift_COMPILER_INIT NOTFOUND) - - if(NOT $ENV{SWIFTC} STREQUAL "") - get_filename_component(CMAKE_Swift_COMPILER_INIT $ENV{SWIFTC} PROGRAM - PROGRAM_ARGS CMAKE_Swift_FLAGS_ENV_INIT) - if(CMAKE_Swift_FLAGS_ENV_INIT) - set(CMAKE_Swift_COMPILER_ARG1 "${CMAKE_Swift_FLAGS_ENV_INIT}" CACHE - STRING "First argument to the Swift compiler") - endif() - if(NOT EXISTS ${CMAKE_Swift_COMPILER_INIT}) - message(FATAL_ERROR "Could not find compiler set in environment variable SWIFTC\n$ENV{SWIFTC}.\n${CMAKE_Swift_COMPILER_INIT}") - endif() - endif() - - if(NOT CMAKE_Swift_COMPILER_INIT) - set(CMAKE_Swift_COMPILER_LIST swiftc ${_CMAKE_TOOLCHAIN_PREFIX}swiftc) - endif() - - _cmake_find_compiler(Swift) - endif() - mark_as_advanced(CMAKE_Swift_COMPILER) -else() - message(FATAL_ERROR "Swift language not supported by \"${CMAKE_GENERATOR}\" generator") -endif() - -# Build a small source file to identify the compiler. -if(NOT CMAKE_Swift_COMPILER_ID_RUN) - set(CMAKE_Swift_COMPILER_ID_RUN 1) - - if("${CMAKE_GENERATOR}" STREQUAL "Xcode") - list(APPEND CMAKE_Swift_COMPILER_ID_MATCH_VENDORS Apple) - set(CMAKE_Swift_COMPILER_ID_MATCH_VENDOR_REGEX_Apple "com.apple.xcode.tools.swift.compiler") - - set(CMAKE_Swift_COMPILER_ID_TOOL_MATCH_REGEX "\nCompileSwift[^\n]*(\n[ \t]+[^\n]*)*\n[ \t]+([^ \t\r\n]+)[^\r\n]* -c[^\r\n]*CompilerIdSwift/CompilerId/main.swift") - set(CMAKE_Swift_COMPILER_ID_TOOL_MATCH_INDEX 2) - endif() - - # Try to identify the compiler. - set(CMAKE_Swift_COMPILER_ID) - include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerId.cmake) - CMAKE_DETERMINE_COMPILER_ID(Swift "" CompilerId/main.swift) -endif() - -if (NOT _CMAKE_TOOLCHAIN_LOCATION) - get_filename_component(_CMAKE_TOOLCHAIN_LOCATION "${CMAKE_Swift_COMPILER}" PATH) -endif () - -set(_CMAKE_PROCESSING_LANGUAGE "Swift") -include(CMakeFindBinUtils) -unset(_CMAKE_PROCESSING_LANGUAGE) - -# configure variables set in this file for fast reload later on -configure_file(${CMAKE_ROOT}/Modules/CMakeSwiftCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeSwiftCompiler.cmake @ONLY) - -set(CMAKE_Swift_COMPILER_ENV_VAR "SWIFTC")
diff --git a/share/cmake-3.18/Modules/CMakeDetermineSystem.cmake b/share/cmake-3.18/Modules/CMakeDetermineSystem.cmake deleted file mode 100644 index f3ec4da..0000000 --- a/share/cmake-3.18/Modules/CMakeDetermineSystem.cmake +++ /dev/null
@@ -1,189 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This module is used by the Makefile generator to determine the following variables: -# CMAKE_SYSTEM_NAME - on unix this is uname -s, for windows it is Windows -# CMAKE_SYSTEM_VERSION - on unix this is uname -r, for windows it is empty -# CMAKE_SYSTEM - ${CMAKE_SYSTEM}-${CMAKE_SYSTEM_VERSION}, for windows: ${CMAKE_SYSTEM} -# -# Expected uname -s output: -# -# AIX AIX -# BSD/OS BSD/OS -# FreeBSD FreeBSD -# HP-UX HP-UX -# Linux Linux -# GNU/kFreeBSD GNU/kFreeBSD -# NetBSD NetBSD -# OpenBSD OpenBSD -# OFS/1 (Digital Unix) OSF1 -# SCO OpenServer 5 SCO_SV -# SCO UnixWare 7 UnixWare -# SCO UnixWare (pre release 7) UNIX_SV -# SCO XENIX Xenix -# Solaris SunOS -# SunOS SunOS -# Tru64 Tru64 -# Ultrix ULTRIX -# cygwin CYGWIN_NT-5.1 -# MacOSX Darwin - - -# find out on which system cmake runs -if(CMAKE_HOST_UNIX) - find_program(CMAKE_UNAME uname /bin /usr/bin /usr/local/bin ) - if(CMAKE_UNAME) - if(CMAKE_HOST_SYSTEM_NAME STREQUAL "AIX") - exec_program(${CMAKE_UNAME} ARGS -v OUTPUT_VARIABLE _CMAKE_HOST_SYSTEM_MAJOR_VERSION) - exec_program(${CMAKE_UNAME} ARGS -r OUTPUT_VARIABLE _CMAKE_HOST_SYSTEM_MINOR_VERSION) - set(CMAKE_HOST_SYSTEM_VERSION "${_CMAKE_HOST_SYSTEM_MAJOR_VERSION}.${_CMAKE_HOST_SYSTEM_MINOR_VERSION}") - unset(_CMAKE_HOST_SYSTEM_MAJOR_VERSION) - unset(_CMAKE_HOST_SYSTEM_MINOR_VERSION) - else() - exec_program(${CMAKE_UNAME} ARGS -r OUTPUT_VARIABLE CMAKE_HOST_SYSTEM_VERSION) - endif() - if(CMAKE_HOST_SYSTEM_NAME MATCHES "Linux|CYGWIN.*|Darwin|^GNU$|Android") - exec_program(${CMAKE_UNAME} ARGS -m OUTPUT_VARIABLE CMAKE_HOST_SYSTEM_PROCESSOR - RETURN_VALUE val) - if(CMAKE_HOST_SYSTEM_NAME STREQUAL "Darwin" AND - CMAKE_HOST_SYSTEM_PROCESSOR STREQUAL "Power Macintosh") - # OS X ppc 'uname -m' may report 'Power Macintosh' instead of 'powerpc' - set(CMAKE_HOST_SYSTEM_PROCESSOR "powerpc") - endif() - elseif(CMAKE_HOST_SYSTEM_NAME MATCHES "OpenBSD") - exec_program(arch ARGS -s OUTPUT_VARIABLE CMAKE_HOST_SYSTEM_PROCESSOR - RETURN_VALUE val) - else() - exec_program(${CMAKE_UNAME} ARGS -p OUTPUT_VARIABLE CMAKE_HOST_SYSTEM_PROCESSOR - RETURN_VALUE val) - if("${val}" GREATER 0) - exec_program(${CMAKE_UNAME} ARGS -m OUTPUT_VARIABLE CMAKE_HOST_SYSTEM_PROCESSOR - RETURN_VALUE val) - endif() - endif() - # check the return of the last uname -m or -p - if("${val}" GREATER 0) - set(CMAKE_HOST_SYSTEM_PROCESSOR "unknown") - endif() - set(CMAKE_UNAME ${CMAKE_UNAME} CACHE INTERNAL "uname command") - # processor may have double quote in the name, and that needs to be removed - string(REPLACE "\"" "" CMAKE_HOST_SYSTEM_PROCESSOR "${CMAKE_HOST_SYSTEM_PROCESSOR}") - string(REPLACE "/" "_" CMAKE_HOST_SYSTEM_PROCESSOR "${CMAKE_HOST_SYSTEM_PROCESSOR}") - endif() -else() - if(CMAKE_HOST_WIN32) - if (DEFINED ENV{PROCESSOR_ARCHITEW6432}) - set (CMAKE_HOST_SYSTEM_PROCESSOR "$ENV{PROCESSOR_ARCHITEW6432}") - else() - set (CMAKE_HOST_SYSTEM_PROCESSOR "$ENV{PROCESSOR_ARCHITECTURE}") - endif() - endif() -endif() - -# if a toolchain file is used, the user wants to cross compile. -# in this case read the toolchain file and keep the CMAKE_HOST_SYSTEM_* -# variables around so they can be used in CMakeLists.txt. -# In all other cases, the host and target platform are the same. -if(CMAKE_TOOLCHAIN_FILE) - # at first try to load it as path relative to the directory from which cmake has been run - include("${CMAKE_BINARY_DIR}/${CMAKE_TOOLCHAIN_FILE}" OPTIONAL RESULT_VARIABLE _INCLUDED_TOOLCHAIN_FILE) - if(NOT _INCLUDED_TOOLCHAIN_FILE) - # if the file isn't found there, check the default locations - include("${CMAKE_TOOLCHAIN_FILE}" OPTIONAL RESULT_VARIABLE _INCLUDED_TOOLCHAIN_FILE) - endif() - - if(_INCLUDED_TOOLCHAIN_FILE) - set(CMAKE_TOOLCHAIN_FILE "${_INCLUDED_TOOLCHAIN_FILE}" CACHE FILEPATH "The CMake toolchain file" FORCE) - else() - message(FATAL_ERROR "Could not find toolchain file: ${CMAKE_TOOLCHAIN_FILE}") - set(CMAKE_TOOLCHAIN_FILE "NOTFOUND" CACHE FILEPATH "The CMake toolchain file" FORCE) - endif() -endif() - - -# if CMAKE_SYSTEM_NAME is here already set, either it comes from a toolchain file -# or it was set via -DCMAKE_SYSTEM_NAME=... -# if that's the case, assume we are crosscompiling -if(CMAKE_SYSTEM_NAME) - if(NOT DEFINED CMAKE_CROSSCOMPILING) - set(CMAKE_CROSSCOMPILING TRUE) - endif() - set(PRESET_CMAKE_SYSTEM_NAME TRUE) -elseif(CMAKE_VS_WINCE_VERSION) - set(CMAKE_SYSTEM_NAME "WindowsCE") - set(CMAKE_SYSTEM_VERSION "${CMAKE_VS_WINCE_VERSION}") - set(CMAKE_SYSTEM_PROCESSOR "${MSVC_C_ARCHITECTURE_ID}") - set(CMAKE_CROSSCOMPILING TRUE) - set(PRESET_CMAKE_SYSTEM_NAME TRUE) -else() - set(CMAKE_SYSTEM_NAME "${CMAKE_HOST_SYSTEM_NAME}") - if(NOT DEFINED CMAKE_SYSTEM_VERSION) - set(CMAKE_SYSTEM_VERSION "${CMAKE_HOST_SYSTEM_VERSION}") - endif() - set(CMAKE_SYSTEM_PROCESSOR "${CMAKE_HOST_SYSTEM_PROCESSOR}") - set(CMAKE_CROSSCOMPILING FALSE) - set(PRESET_CMAKE_SYSTEM_NAME FALSE) -endif() - -include(Platform/${CMAKE_SYSTEM_NAME}-Determine OPTIONAL) - -macro(ADJUST_CMAKE_SYSTEM_VARIABLES _PREFIX) - if(NOT ${_PREFIX}_NAME) - set(${_PREFIX}_NAME "UnknownOS") - endif() - - # fix for BSD/OS , remove the / - if(${_PREFIX}_NAME MATCHES BSD.OS) - set(${_PREFIX}_NAME BSDOS) - endif() - - # fix for GNU/kFreeBSD, remove the GNU/ - if(${_PREFIX}_NAME MATCHES kFreeBSD) - set(${_PREFIX}_NAME kFreeBSD) - endif() - - # fix for CYGWIN which has windows version in it - if(${_PREFIX}_NAME MATCHES CYGWIN) - set(${_PREFIX}_NAME CYGWIN) - endif() - - # set CMAKE_SYSTEM to the CMAKE_SYSTEM_NAME - set(${_PREFIX} ${${_PREFIX}_NAME}) - # if there is a CMAKE_SYSTEM_VERSION then add a -${CMAKE_SYSTEM_VERSION} - if(${_PREFIX}_VERSION) - set(${_PREFIX} ${${_PREFIX}}-${${_PREFIX}_VERSION}) - endif() - -endmacro() - -ADJUST_CMAKE_SYSTEM_VARIABLES(CMAKE_SYSTEM) -ADJUST_CMAKE_SYSTEM_VARIABLES(CMAKE_HOST_SYSTEM) - -# this file is also executed from cpack, then we don't need to generate these files -# in this case there is no CMAKE_BINARY_DIR -if(CMAKE_BINARY_DIR) - # write entry to the log file - if(PRESET_CMAKE_SYSTEM_NAME) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "The target system is: ${CMAKE_SYSTEM_NAME} - ${CMAKE_SYSTEM_VERSION} - ${CMAKE_SYSTEM_PROCESSOR}\n") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "The host system is: ${CMAKE_HOST_SYSTEM_NAME} - ${CMAKE_HOST_SYSTEM_VERSION} - ${CMAKE_HOST_SYSTEM_PROCESSOR}\n") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "The system is: ${CMAKE_SYSTEM_NAME} - ${CMAKE_SYSTEM_VERSION} - ${CMAKE_SYSTEM_PROCESSOR}\n") - endif() - - # if a toolchain file is used, it needs to be included in the configured file, - # so settings done there are also available if they don't go in the cache and in try_compile() - set(INCLUDE_CMAKE_TOOLCHAIN_FILE_IF_REQUIRED) - if(CMAKE_TOOLCHAIN_FILE) - set(INCLUDE_CMAKE_TOOLCHAIN_FILE_IF_REQUIRED "include(\"${CMAKE_TOOLCHAIN_FILE}\")") - endif() - - # configure variables set in this file for fast reload, the template file is defined at the top of this file - configure_file(${CMAKE_ROOT}/Modules/CMakeSystem.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeSystem.cmake - @ONLY) - -endif()
diff --git a/share/cmake-3.18/Modules/CMakeExtraGeneratorDetermineCompilerMacrosAndIncludeDirs.cmake b/share/cmake-3.18/Modules/CMakeExtraGeneratorDetermineCompilerMacrosAndIncludeDirs.cmake deleted file mode 100644 index 11f4a29..0000000 --- a/share/cmake-3.18/Modules/CMakeExtraGeneratorDetermineCompilerMacrosAndIncludeDirs.cmake +++ /dev/null
@@ -1,114 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file is included by CMakeFindEclipseCDT4.cmake and CMakeFindCodeBlocks.cmake - -# The Eclipse and the CodeBlocks generators need to know the standard include path -# so that they can find the headers at runtime and parsing etc. works better -# This is done here by actually running gcc with the options so it prints its -# system include directories, which are parsed then and stored in the cache. -macro(_DETERMINE_GCC_SYSTEM_INCLUDE_DIRS _lang _resultIncludeDirs _resultDefines) - set(${_resultIncludeDirs}) - set(_gccOutput) - file(WRITE "${CMAKE_BINARY_DIR}/CMakeFiles/dummy" "\n" ) - - if (${_lang} STREQUAL "c++") - set(_compilerExecutable "${CMAKE_CXX_COMPILER}") - set(_arg1 "${CMAKE_CXX_COMPILER_ARG1}") - - if (CMAKE_CXX_FLAGS MATCHES "(-stdlib=[^ ]+)") - set(_stdlib "${CMAKE_MATCH_1}") - endif () - if (CMAKE_CXX_FLAGS MATCHES "(-std=[^ ]+)") - set(_stdver "${CMAKE_MATCH_1}") - endif () - else () - set(_compilerExecutable "${CMAKE_C_COMPILER}") - set(_arg1 "${CMAKE_C_COMPILER_ARG1}") - endif () - separate_arguments(_arg1 NATIVE_COMMAND "${_arg1}") - execute_process(COMMAND ${_compilerExecutable} ${_arg1} ${_stdver} ${_stdlib} -v -E -x ${_lang} -dD dummy - WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/CMakeFiles - ERROR_VARIABLE _gccOutput - OUTPUT_VARIABLE _gccStdout ) - file(REMOVE "${CMAKE_BINARY_DIR}/CMakeFiles/dummy") - - # First find the system include dirs: - if( "${_gccOutput}" MATCHES "> search starts here[^\n]+\n *(.+ *\n) *End of (search) list" ) - - # split the output into lines and then remove leading and trailing spaces from each of them: - string(REGEX MATCHALL "[^\n]+\n" _includeLines "${CMAKE_MATCH_1}") - foreach(nextLine ${_includeLines}) - # on OSX, gcc says things like this: "/System/Library/Frameworks (framework directory)", strip the last part - string(REGEX REPLACE "\\(framework directory\\)" "" nextLineNoFramework "${nextLine}") - # strip spaces at the beginning and the end - string(STRIP "${nextLineNoFramework}" _includePath) - list(APPEND ${_resultIncludeDirs} "${_includePath}") - endforeach() - - endif() - - - # now find the builtin macros: - string(REGEX MATCHALL "#define[^\n]+\n" _defineLines "${_gccStdout}") -# A few example lines which the regexp below has to match properly: -# #define MAX(a,b) ((a) > (b) ? (a) : (b)) -# #define __fastcall __attribute__((__fastcall__)) -# #define FOO (23) -# #define __UINTMAX_TYPE__ long long unsigned int -# #define __UINTMAX_TYPE__ long long unsigned int -# #define __i386__ 1 - - foreach(nextLine ${_defineLines}) - string(REGEX MATCH "^#define +([A-Za-z_][A-Za-z0-9_]*)(\\([^\\)]+\\))? +(.+) *$" _dummy "${nextLine}") - set(_name "${CMAKE_MATCH_1}${CMAKE_MATCH_2}") - string(STRIP "${CMAKE_MATCH_3}" _value) - #message(STATUS "m1: -${CMAKE_MATCH_1}- m2: -${CMAKE_MATCH_2}- m3: -${CMAKE_MATCH_3}-") - - list(APPEND ${_resultDefines} "${_name}") - if ("${_value}" STREQUAL "") - list(APPEND ${_resultDefines} " ") - else() - list(APPEND ${_resultDefines} "${_value}") - endif() - endforeach() - -endmacro() - -# Save the current LC_ALL, LC_MESSAGES, and LANG environment variables and set them -# to "C" that way GCC's "search starts here" text is in English and we can grok it. -set(_orig_lc_all $ENV{LC_ALL}) -set(_orig_lc_messages $ENV{LC_MESSAGES}) -set(_orig_lang $ENV{LANG}) - -set(ENV{LC_ALL} C) -set(ENV{LC_MESSAGES} C) -set(ENV{LANG} C) - -# Now check for C, works for gcc and Intel compiler at least -if (NOT CMAKE_EXTRA_GENERATOR_C_SYSTEM_INCLUDE_DIRS) - if (CMAKE_C_COMPILER_ID MATCHES GNU OR CMAKE_C_COMPILER_ID MATCHES Intel OR CMAKE_C_COMPILER_ID MATCHES Clang) - _DETERMINE_GCC_SYSTEM_INCLUDE_DIRS(c _dirs _defines) - set(CMAKE_EXTRA_GENERATOR_C_SYSTEM_INCLUDE_DIRS "${_dirs}" CACHE INTERNAL "C compiler system include directories") - set(CMAKE_EXTRA_GENERATOR_C_SYSTEM_DEFINED_MACROS "${_defines}" CACHE INTERNAL "C compiler system defined macros") - elseif ("${CMAKE_C_COMPILER_ID}" MATCHES MSVC) - set(CMAKE_EXTRA_GENERATOR_C_SYSTEM_INCLUDE_DIRS "$ENV{INCLUDE}" CACHE INTERNAL "C compiler system include directories") - endif () -endif () - -# And now the same for C++ -if (NOT CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_INCLUDE_DIRS) - if ("${CMAKE_CXX_COMPILER_ID}" MATCHES GNU OR "${CMAKE_CXX_COMPILER_ID}" MATCHES Intel OR "${CMAKE_CXX_COMPILER_ID}" MATCHES Clang) - _DETERMINE_GCC_SYSTEM_INCLUDE_DIRS(c++ _dirs _defines) - set(CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_INCLUDE_DIRS "${_dirs}" CACHE INTERNAL "CXX compiler system include directories") - set(CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_DEFINED_MACROS "${_defines}" CACHE INTERNAL "CXX compiler system defined macros") - elseif ("${CMAKE_CXX_COMPILER_ID}" MATCHES MSVC) - set(CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_INCLUDE_DIRS "$ENV{INCLUDE}" CACHE INTERNAL "CXX compiler system include directories") - endif () -endif () - -# Restore original LC_ALL, LC_MESSAGES, and LANG -set(ENV{LC_ALL} ${_orig_lc_all}) -set(ENV{LC_MESSAGES} ${_orig_lc_messages}) -set(ENV{LANG} ${_orig_lang})
diff --git a/share/cmake-3.18/Modules/CMakeFindBinUtils.cmake b/share/cmake-3.18/Modules/CMakeFindBinUtils.cmake deleted file mode 100644 index de9ef9a..0000000 --- a/share/cmake-3.18/Modules/CMakeFindBinUtils.cmake +++ /dev/null
@@ -1,144 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# search for additional tools required for C/C++ (and other languages ?) -# -# If the internal cmake variable _CMAKE_TOOLCHAIN_PREFIX is set, this is used -# as prefix for the tools (e.g. arm-elf-gcc etc.) -# If the cmake variable _CMAKE_TOOLCHAIN_LOCATION is set, the compiler is -# searched only there. The other tools are at first searched there, then -# also in the default locations. -# -# Sets the following variables: -# CMAKE_AR -# CMAKE_RANLIB -# CMAKE_LINKER -# CMAKE_MT -# CMAKE_STRIP -# CMAKE_INSTALL_NAME_TOOL - -# on UNIX, cygwin and mingw - -# Resolve full path of CMAKE_TOOL from user-defined name and SEARCH_PATH. -function(__resolve_tool_path CMAKE_TOOL SEARCH_PATH DOCSTRING) - - if(${CMAKE_TOOL}) - # We only get here if CMAKE_TOOL was - # specified using -D or a pre-made CMakeCache.txt (e.g. via ctest) - # or set in CMAKE_TOOLCHAIN_FILE. - - get_filename_component(_CMAKE_USER_TOOL_PATH "${${CMAKE_TOOL}}" DIRECTORY) - # Is CMAKE_TOOL a user-defined name instead of a full path? - if(NOT _CMAKE_USER_TOOL_PATH) - - # Find CMAKE_TOOL in the SEARCH_PATH directory by user-defined name. - find_program(_CMAKE_TOOL_WITH_PATH NAMES ${${CMAKE_TOOL}} HINTS ${SEARCH_PATH}) - if(_CMAKE_TOOL_WITH_PATH) - - # Overwrite CMAKE_TOOL with full path found in SEARCH_PATH. - set(${CMAKE_TOOL} ${_CMAKE_TOOL_WITH_PATH} PARENT_SCOPE) - - get_property(_CMAKE_TOOL_CACHED CACHE ${CMAKE_TOOL} PROPERTY TYPE) - # If CMAKE_TOOL is present in the CMake Cache, then overwrit it as well. - if(_CMAKE_TOOL_CACHED) - set(${CMAKE_TOOL} "${_CMAKE_TOOL_WITH_PATH}" CACHE STRING ${DOCSTRING} FORCE) - endif() - - endif() - unset(_CMAKE_TOOL_WITH_PATH CACHE) - - endif() - - endif() - -endfunction() - -__resolve_tool_path(CMAKE_LINKER "${_CMAKE_TOOLCHAIN_LOCATION}" "Default Linker") -__resolve_tool_path(CMAKE_MT "${_CMAKE_TOOLCHAIN_LOCATION}" "Default Manifest Tool") - -set(_CMAKE_TOOL_VARS "") - -# if it's the MS C/CXX compiler, search for link -if(("x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_SIMULATE_ID}" STREQUAL "xMSVC" AND - ("x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_FRONTEND_VARIANT}" STREQUAL "xMSVC" - OR NOT "x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL "xClang")) - OR "x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL "xMSVC" - OR (CMAKE_HOST_WIN32 AND "x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL "xPGI") - OR (CMAKE_HOST_WIN32 AND "x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL "xNVIDIA") - OR (CMAKE_GENERATOR MATCHES "Visual Studio" - AND NOT CMAKE_VS_PLATFORM_NAME STREQUAL "Tegra-Android")) - - if("x${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL "xClang") - find_program(CMAKE_NM NAMES ${_CMAKE_TOOLCHAIN_PREFIX}nm llvm-nm HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - set(_CMAKE_ADDITIONAL_LINKER_NAMES "lld-link") - endif() - - find_program(CMAKE_LINKER NAMES ${_CMAKE_ADDITIONAL_LINKER_NAMES} link HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_AR NAMES lib HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_MT NAMES mt HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - - list(APPEND _CMAKE_TOOL_VARS LINKER MT) - -# in all other cases search for ar, ranlib, etc. -else() - if(CMAKE_C_COMPILER_EXTERNAL_TOOLCHAIN) - set(_CMAKE_TOOLCHAIN_LOCATION ${_CMAKE_TOOLCHAIN_LOCATION} ${CMAKE_C_COMPILER_EXTERNAL_TOOLCHAIN}/bin) - endif() - if(CMAKE_CXX_COMPILER_EXTERNAL_TOOLCHAIN) - set(_CMAKE_TOOLCHAIN_LOCATION ${_CMAKE_TOOLCHAIN_LOCATION} ${CMAKE_CXX_COMPILER_EXTERNAL_TOOLCHAIN}/bin) - endif() - - if("${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ID}" STREQUAL Clang) - set(_CMAKE_ADDITIONAL_AR_NAMES "llvm-ar") - set(_CMAKE_ADDITIONAL_RANLIB_NAMES "llvm-ranlib") - set(_CMAKE_ADDITIONAL_STRIP_NAMES "llvm-strip") - set(_CMAKE_ADDITIONAL_LINKER_NAMES "ld.lld") - set(_CMAKE_ADDITIONAL_NM_NAMES "llvm-nm") - set(_CMAKE_ADDITIONAL_OBJDUMP_NAMES "llvm-objdump") - set(_CMAKE_ADDITIONAL_OBJCOPY_NAMES "llvm-objcopy") - set(_CMAKE_ADDITIONAL_READELF_NAMES "llvm-readelf") - set(_CMAKE_ADDITIONAL_DLLTOOL_NAMES "llvm-dlltool") - set(_CMAKE_ADDITIONAL_ADDR2LINE_NAMES "llvm-addr2line") - endif() - - find_program(CMAKE_AR NAMES ${_CMAKE_TOOLCHAIN_PREFIX}ar${_CMAKE_TOOLCHAIN_SUFFIX} ${_CMAKE_ADDITIONAL_AR_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - - find_program(CMAKE_RANLIB NAMES ${_CMAKE_TOOLCHAIN_PREFIX}ranlib ${_CMAKE_ADDITIONAL_RANLIB_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - if(NOT CMAKE_RANLIB) - set(CMAKE_RANLIB : CACHE INTERNAL "noop for ranlib") - endif() - - - find_program(CMAKE_STRIP NAMES ${_CMAKE_TOOLCHAIN_PREFIX}strip${_CMAKE_TOOLCHAIN_SUFFIX} ${_CMAKE_ADDITIONAL_STRIP_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_LINKER NAMES ${_CMAKE_TOOLCHAIN_PREFIX}ld ${_CMAKE_ADDITIONAL_LINKER_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_NM NAMES ${_CMAKE_TOOLCHAIN_PREFIX}nm ${_CMAKE_ADDITIONAL_NM_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_OBJDUMP NAMES ${_CMAKE_TOOLCHAIN_PREFIX}objdump ${_CMAKE_ADDITIONAL_OBJDUMP_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_OBJCOPY NAMES ${_CMAKE_TOOLCHAIN_PREFIX}objcopy ${_CMAKE_ADDITIONAL_OBJCOPY_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_READELF NAMES ${_CMAKE_TOOLCHAIN_PREFIX}readelf ${_CMAKE_ADDITIONAL_READELF_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_DLLTOOL NAMES ${_CMAKE_TOOLCHAIN_PREFIX}dlltool ${_CMAKE_ADDITIONAL_DLLTOOL_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - find_program(CMAKE_ADDR2LINE NAMES ${_CMAKE_TOOLCHAIN_PREFIX}addr2line ${_CMAKE_ADDITIONAL_ADDR2LINE_NAMES} HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - - list(APPEND _CMAKE_TOOL_VARS AR RANLIB STRIP LINKER NM OBJDUMP OBJCOPY READELF DLLTOOL ADDR2LINE) -endif() - -if(CMAKE_PLATFORM_HAS_INSTALLNAME) - find_program(CMAKE_INSTALL_NAME_TOOL NAMES ${_CMAKE_TOOLCHAIN_PREFIX}install_name_tool HINTS ${_CMAKE_TOOLCHAIN_LOCATION}) - - if(NOT CMAKE_INSTALL_NAME_TOOL) - message(FATAL_ERROR "Could not find install_name_tool, please check your installation.") - endif() - - list(APPEND _CMAKE_TOOL_VARS INSTALL_NAME_TOOL) -endif() - -# Mark any tool cache entries as advanced. -foreach(var IN LISTS _CMAKE_TOOL_VARS) - get_property(_CMAKE_TOOL_CACHED CACHE CMAKE_${var} PROPERTY TYPE) - if(_CMAKE_TOOL_CACHED) - mark_as_advanced(CMAKE_${var}) - endif() - unset(_CMAKE_ADDITIONAL_${var}_NAMES) -endforeach() -unset(_CMAKE_TOOL_VARS) -unset(_CMAKE_TOOL_CACHED)
diff --git a/share/cmake-3.18/Modules/CMakeFindPackageMode.cmake b/share/cmake-3.18/Modules/CMakeFindPackageMode.cmake deleted file mode 100644 index 815dfc9..0000000 --- a/share/cmake-3.18/Modules/CMakeFindPackageMode.cmake +++ /dev/null
@@ -1,204 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CMakeFindPackageMode --------------------- - - - -This file is executed by cmake when invoked with --find-package. It -expects that the following variables are set using -D: - -``NAME`` - name of the package -``COMPILER_ID`` - the CMake compiler ID for which the result is, - i.e. GNU/Intel/Clang/MSVC, etc. -``LANGUAGE`` - language for which the result will be used, - i.e. C/CXX/Fortran/ASM -``MODE`` - ``EXIST`` - only check for existence of the given package - ``COMPILE`` - print the flags needed for compiling an object file which uses - the given package - ``LINK`` - print the flags needed for linking when using the given package -``QUIET`` - if TRUE, don't print anything -#]=======================================================================] - -if(NOT NAME) - message(FATAL_ERROR "Name of the package to be searched not specified. Set the CMake variable NAME, e.g. -DNAME=JPEG .") -endif() - -if(NOT COMPILER_ID) - message(FATAL_ERROR "COMPILER_ID argument not specified. In doubt, use GNU.") -endif() - -if(NOT LANGUAGE) - message(FATAL_ERROR "LANGUAGE argument not specified. Use C, CXX or Fortran.") -endif() - -if(NOT MODE) - message(FATAL_ERROR "MODE argument not specified. Use either EXIST, COMPILE or LINK.") -endif() - -# require the current version. If we don't do this, Platforms/CYGWIN.cmake complains because -# it doesn't know whether it should set WIN32 or not: -cmake_minimum_required(VERSION ${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION}.${CMAKE_PATCH_VERSION} ) - -macro(ENABLE_LANGUAGE) - # disable the enable_language() command, otherwise --find-package breaks on Windows. - # On Windows, enable_language(RC) is called in the platform files unconditionally. - # But in --find-package mode, we don't want (and can't) enable any language. -endmacro() - -set(CMAKE_PLATFORM_INFO_DIR ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}) - -include(CMakeDetermineSystem) - -# short-cut some tests on Darwin, see Darwin-GNU.cmake: -if("${CMAKE_SYSTEM_NAME}" MATCHES Darwin AND "${COMPILER_ID}" MATCHES GNU) - set(CMAKE_${LANGUAGE}_SYSROOT_FLAG "") - set(CMAKE_${LANGUAGE}_OSX_DEPLOYMENT_TARGET_FLAG "") -endif() - -include(CMakeSystemSpecificInitialize) - -# Also load the system specific file, which sets up e.g. the search paths. -# This makes the FIND_XXX() calls work much better -include(CMakeSystemSpecificInformation) - -if(UNIX) - - # try to guess whether we have a 64bit system, if it has not been set - # from the outside - if(NOT CMAKE_SIZEOF_VOID_P) - set(CMAKE_SIZEOF_VOID_P 4) - if(EXISTS /usr/lib64) - set(CMAKE_SIZEOF_VOID_P 8) - else() - # use the file utility to check whether itself is 64 bit: - find_program(FILE_EXECUTABLE file) - if(FILE_EXECUTABLE) - get_filename_component(FILE_ABSPATH "${FILE_EXECUTABLE}" ABSOLUTE) - execute_process(COMMAND "${FILE_ABSPATH}" "${FILE_ABSPATH}" OUTPUT_VARIABLE fileOutput ERROR_QUIET) - if("${fileOutput}" MATCHES "64-bit") - set(CMAKE_SIZEOF_VOID_P 8) - endif() - endif() - endif() - endif() - - # guess Debian multiarch if it has not been set: - if(EXISTS /etc/debian_version) - if(NOT CMAKE_${LANGUAGE}_LIBRARY_ARCHITECTURE ) - file(GLOB filesInLib RELATIVE /lib /lib/*-linux-gnu* ) - foreach(file ${filesInLib}) - if("${file}" MATCHES "${CMAKE_LIBRARY_ARCHITECTURE_REGEX}") - set(CMAKE_${LANGUAGE}_LIBRARY_ARCHITECTURE ${file}) - break() - endif() - endforeach() - endif() - if(NOT CMAKE_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE ${CMAKE_${LANGUAGE}_LIBRARY_ARCHITECTURE}) - endif() - endif() - -endif() - -set(CMAKE_${LANGUAGE}_COMPILER "dummy") -set(CMAKE_${LANGUAGE}_COMPILER_ID "${COMPILER_ID}") -include(CMake${LANGUAGE}Information) - - -function(set_compile_flags_var _packageName) - string(TOUPPER "${_packageName}" PACKAGE_NAME) - # Check the following variables: - # FOO_INCLUDE_DIRS - # Foo_INCLUDE_DIRS - # FOO_INCLUDES - # Foo_INCLUDES - # FOO_INCLUDE_DIR - # Foo_INCLUDE_DIR - set(includes) - if(DEFINED ${_packageName}_INCLUDE_DIRS) - set(includes ${_packageName}_INCLUDE_DIRS) - elseif(DEFINED ${PACKAGE_NAME}_INCLUDE_DIRS) - set(includes ${PACKAGE_NAME}_INCLUDE_DIRS) - elseif(DEFINED ${_packageName}_INCLUDES) - set(includes ${_packageName}_INCLUDES) - elseif(DEFINED ${PACKAGE_NAME}_INCLUDES) - set(includes ${PACKAGE_NAME}_INCLUDES) - elseif(DEFINED ${_packageName}_INCLUDE_DIR) - set(includes ${_packageName}_INCLUDE_DIR) - elseif(DEFINED ${PACKAGE_NAME}_INCLUDE_DIR) - set(includes ${PACKAGE_NAME}_INCLUDE_DIR) - endif() - - set(PACKAGE_INCLUDE_DIRS "${${includes}}" PARENT_SCOPE) - - # Check the following variables: - # FOO_DEFINITIONS - # Foo_DEFINITIONS - set(definitions) - if(DEFINED ${_packageName}_DEFINITIONS) - set(definitions ${_packageName}_DEFINITIONS) - elseif(DEFINED ${PACKAGE_NAME}_DEFINITIONS) - set(definitions ${PACKAGE_NAME}_DEFINITIONS) - endif() - - set(PACKAGE_DEFINITIONS "${${definitions}}" ) - -endfunction() - - -function(set_link_flags_var _packageName) - string(TOUPPER "${_packageName}" PACKAGE_NAME) - # Check the following variables: - # FOO_LIBRARIES - # Foo_LIBRARIES - # FOO_LIBS - # Foo_LIBS - set(libs) - if(DEFINED ${_packageName}_LIBRARIES) - set(libs ${_packageName}_LIBRARIES) - elseif(DEFINED ${PACKAGE_NAME}_LIBRARIES) - set(libs ${PACKAGE_NAME}_LIBRARIES) - elseif(DEFINED ${_packageName}_LIBS) - set(libs ${_packageName}_LIBS) - elseif(DEFINED ${PACKAGE_NAME}_LIBS) - set(libs ${PACKAGE_NAME}_LIBS) - endif() - - set(PACKAGE_LIBRARIES "${${libs}}" PARENT_SCOPE ) - -endfunction() - - -find_package("${NAME}" QUIET) - -set(PACKAGE_FOUND FALSE) - -string(TOUPPER "${NAME}" UPPERCASE_NAME) - -if(${NAME}_FOUND OR ${UPPERCASE_NAME}_FOUND) - set(PACKAGE_FOUND TRUE) - - if("${MODE}" STREQUAL "EXIST") - # do nothing - elseif("${MODE}" STREQUAL "COMPILE") - set_compile_flags_var(${NAME}) - elseif("${MODE}" STREQUAL "LINK") - set_link_flags_var(${NAME}) - else() - message(FATAL_ERROR "Invalid mode argument ${MODE} given.") - endif() - -endif() - -set(PACKAGE_QUIET ${SILENT} )
diff --git a/share/cmake-3.18/Modules/CMakeFortranCompiler.cmake.in b/share/cmake-3.18/Modules/CMakeFortranCompiler.cmake.in deleted file mode 100644 index 06ee528..0000000 --- a/share/cmake-3.18/Modules/CMakeFortranCompiler.cmake.in +++ /dev/null
@@ -1,69 +0,0 @@ -set(CMAKE_Fortran_COMPILER "@CMAKE_Fortran_COMPILER@") -set(CMAKE_Fortran_COMPILER_ARG1 "@CMAKE_Fortran_COMPILER_ARG1@") -set(CMAKE_Fortran_COMPILER_ID "@CMAKE_Fortran_COMPILER_ID@") -set(CMAKE_Fortran_COMPILER_VERSION "@CMAKE_Fortran_COMPILER_VERSION@") -set(CMAKE_Fortran_COMPILER_WRAPPER "@CMAKE_Fortran_COMPILER_WRAPPER@") -set(CMAKE_Fortran_PLATFORM_ID "@CMAKE_Fortran_PLATFORM_ID@") -set(CMAKE_Fortran_SIMULATE_ID "@CMAKE_Fortran_SIMULATE_ID@") -set(CMAKE_Fortran_SIMULATE_VERSION "@CMAKE_Fortran_SIMULATE_VERSION@") -@_SET_CMAKE_Fortran_XL_CPP@ -@_SET_CMAKE_Fortran_COMPILER_ARCHITECTURE_ID@ -@_SET_CMAKE_Fortran_COMPILER_SYSROOT@ -@SET_MSVC_Fortran_ARCHITECTURE_ID@ -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_Fortran_COMPILER_AR "@CMAKE_Fortran_COMPILER_AR@") -set(CMAKE_RANLIB "@CMAKE_RANLIB@") -set(CMAKE_Fortran_COMPILER_RANLIB "@CMAKE_Fortran_COMPILER_RANLIB@") -set(CMAKE_COMPILER_IS_GNUG77 @CMAKE_COMPILER_IS_GNUG77@) -set(CMAKE_Fortran_COMPILER_LOADED 1) -set(CMAKE_Fortran_COMPILER_WORKS @CMAKE_Fortran_COMPILER_WORKS@) -set(CMAKE_Fortran_ABI_COMPILED @CMAKE_Fortran_ABI_COMPILED@) -set(CMAKE_COMPILER_IS_MINGW @CMAKE_COMPILER_IS_MINGW@) -set(CMAKE_COMPILER_IS_CYGWIN @CMAKE_COMPILER_IS_CYGWIN@) -if(CMAKE_COMPILER_IS_CYGWIN) - set(CYGWIN 1) - set(UNIX 1) -endif() - -set(CMAKE_Fortran_COMPILER_ENV_VAR "FC") - -set(CMAKE_Fortran_COMPILER_SUPPORTS_F90 @CMAKE_Fortran_COMPILER_SUPPORTS_F90@) - -if(CMAKE_COMPILER_IS_MINGW) - set(MINGW 1) -endif() -set(CMAKE_Fortran_COMPILER_ID_RUN 1) -set(CMAKE_Fortran_SOURCE_FILE_EXTENSIONS f;F;fpp;FPP;f77;F77;f90;F90;for;For;FOR;f95;F95) -set(CMAKE_Fortran_IGNORE_EXTENSIONS h;H;o;O;obj;OBJ;def;DEF;rc;RC) -set(CMAKE_Fortran_LINKER_PREFERENCE 20) -if(UNIX) - set(CMAKE_Fortran_OUTPUT_EXTENSION .o) -else() - set(CMAKE_Fortran_OUTPUT_EXTENSION .obj) -endif() - -# Save compiler ABI information. -set(CMAKE_Fortran_SIZEOF_DATA_PTR "@CMAKE_Fortran_SIZEOF_DATA_PTR@") -set(CMAKE_Fortran_COMPILER_ABI "@CMAKE_Fortran_COMPILER_ABI@") -set(CMAKE_Fortran_LIBRARY_ARCHITECTURE "@CMAKE_Fortran_LIBRARY_ARCHITECTURE@") - -if(CMAKE_Fortran_SIZEOF_DATA_PTR AND NOT CMAKE_SIZEOF_VOID_P) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_Fortran_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_Fortran_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_Fortran_COMPILER_ABI}") -endif() - -if(CMAKE_Fortran_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_Fortran_LIBRARY_ARCHITECTURE@") -endif() - -@CMAKE_Fortran_COMPILER_CUSTOM_CODE@ -@CMAKE_Fortran_SYSROOT_FLAG_CODE@ -@CMAKE_Fortran_OSX_DEPLOYMENT_TARGET_FLAG_CODE@ - -set(CMAKE_Fortran_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_Fortran_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES "@CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_Fortran_IMPLICIT_LINK_DIRECTORIES "@CMAKE_Fortran_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_Fortran_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_Fortran_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@")
diff --git a/share/cmake-3.18/Modules/CMakeFortranCompilerId.F.in b/share/cmake-3.18/Modules/CMakeFortranCompilerId.F.in deleted file mode 100644 index 30f8d4c..0000000 --- a/share/cmake-3.18/Modules/CMakeFortranCompilerId.F.in +++ /dev/null
@@ -1,200 +0,0 @@ - PROGRAM CMakeFortranCompilerId -#if 0 -! Identify the compiler -#endif -#if defined(_MSC_VER) - PRINT *, 'INFO:simulate[MSVC]' -# if _MSC_VER >= 1900 - PRINT *, 'INFO:simulate_version[019.00]' -# elif _MSC_VER >= 1800 - PRINT *, 'INFO:simulate_version[018.00]' -# elif _MSC_VER >= 1700 - PRINT *, 'INFO:simulate_version[017.00]' -# elif _MSC_VER >= 1600 - PRINT *, 'INFO:simulate_version[016.00]' -# elif _MSC_VER >= 1500 - PRINT *, 'INFO:simulate_version[015.00]' -# elif _MSC_VER >= 1400 - PRINT *, 'INFO:simulate_version[014.00]' -# elif _MSC_VER >= 1310 - PRINT *, 'INFO:simulate_version[013.01]' -# else - PRINT *, 'INFO:simulate_version[013.00]' -# endif -#endif -#if defined(__INTEL_COMPILER) || defined(__ICC) - PRINT *, 'INFO:compiler[Intel]' -# define COMPILER_VERSION_MAJOR DEC(__INTEL_COMPILER/100) -# define COMPILER_VERSION_MINOR DEC(__INTEL_COMPILER/10 % 10) -# if defined(__INTEL_COMPILER_UPDATE) -# define COMPILER_VERSION_PATCH DEC(__INTEL_COMPILER_UPDATE) -# else -# define COMPILER_VERSION_PATCH DEC(__INTEL_COMPILER % 10) -# endif -# if defined(__INTEL_COMPILER_BUILD_DATE) -# define COMPILER_VERSION_TWEAK DEC(__INTEL_COMPILER_BUILD_DATE) -# endif -#elif defined(__SUNPRO_F95) - PRINT *, 'INFO:compiler[SunPro]' -# define COMPILER_VERSION_MAJOR HEX(__SUNPRO_F95>>8) -# define COMPILER_VERSION_MINOR HEX(__SUNPRO_F95>>4 & 0xF) -# define COMPILER_VERSION_PATCH HEX(__SUNPRO_F95 & 0xF) -#elif defined(__SUNPRO_F90) - PRINT *, 'INFO:compiler[SunPro]' -# define COMPILER_VERSION_MAJOR HEX(__SUNPRO_F90>>8) -# define COMPILER_VERSION_MINOR HEX(__SUNPRO_F90>>4 & 0xF) -# define COMPILER_VERSION_PATCH HEX(__SUNPRO_F90 & 0xF) -#elif defined(_CRAYFTN) - PRINT *, 'INFO:compiler[Cray]' -# define COMPILER_VERSION_MAJOR DEC(_RELEASE_MAJOR) -# define COMPILER_VERSION_MINOR DEC(_RELEASE_MINOR) -#elif defined(__G95__) - PRINT *, 'INFO:compiler[G95]' -# define COMPILER_VERSION_MAJOR DEC(__G95__) -# define COMPILER_VERSION_MINOR DEC(__G95_MINOR__) -#elif defined(__PATHSCALE__) - PRINT *, 'INFO:compiler[PathScale]' -# define COMPILER_VERSION_MAJOR DEC(__PATHCC__) -# define COMPILER_VERSION_MINOR DEC(__PATHCC_MINOR__) -# if defined(__PATHCC_PATCHLEVEL__) -# define COMPILER_VERSION_PATCH DEC(__PATHCC_PATCHLEVEL__) -# endif -#elif defined(__ABSOFT__) - PRINT *, 'INFO:compiler[Absoft]' -#elif defined(__GNUC__) - PRINT *, 'INFO:compiler[GNU]' -# define COMPILER_VERSION_MAJOR DEC(__GNUC__) -# define COMPILER_VERSION_MINOR DEC(__GNUC_MINOR__) -# if defined(__GNUC_PATCHLEVEL__) -# define COMPILER_VERSION_PATCH DEC(__GNUC_PATCHLEVEL__) -# endif -#elif defined(__IBMC__) -# if defined(__COMPILER_VER__) - PRINT *, 'INFO:compiler[zOS]' -# elif __IBMC__ >= 800 - PRINT *, 'INFO:compiler[XL]' -# define COMPILER_VERSION_MAJOR DEC(__IBMC__/100) -# define COMPILER_VERSION_MINOR DEC(__IBMC__/10 % 10) -# define COMPILER_VERSION_PATCH DEC(__IBMC__ % 10) -# else - PRINT *, 'INFO:compiler[VisualAge]' -# define COMPILER_VERSION_MAJOR DEC(__IBMC__/100) -# define COMPILER_VERSION_MINOR DEC(__IBMC__/10 % 10) -# define COMPILER_VERSION_PATCH DEC(__IBMC__ % 10) -# endif -#elif defined(__PGI) - PRINT *, 'INFO:compiler[PGI]' -# define COMPILER_VERSION_MAJOR DEC(__PGIC__) -# define COMPILER_VERSION_MINOR DEC(__PGIC_MINOR__) -# if defined(__PGIC_PATCHLEVEL__) -# define COMPILER_VERSION_PATCH DEC(__PGIC_PATCHLEVEL__) -# endif -#elif defined(__FLANG) - PRINT *, 'INFO:compiler[Flang]' -# define COMPILER_VERSION_MAJOR DEC(__FLANG_MAJOR__) -# define COMPILER_VERSION_MINOR DEC(__FLANG_MINOR__) -# if defined(__FLANG_PATCHLEVEL__) -# define COMPILER_VERSION_PATCH DEC(__FLANG_PATCHLEVEL__) -# endif -#elif defined(_AIX) || defined(__AIX) || defined(__AIX__) || defined(__aix) || defined(__aix__) - PRINT *, 'INFO:compiler[VisualAge]' -#elif defined(__hpux) || defined(__hpux__) - PRINT *, 'INFO:compiler[HP]' -#elif defined(NAGFOR) - PRINT *, 'INFO:compiler[NAG]' -#define COMPILER_VERSION_MAJOR DEC(__NAG_COMPILER_RELEASE/10) -#define COMPILER_VERSION_MINOR DEC(__NAG_COMPILER_RELEASE % 10) -#define COMPILER_VERSION_PATCH DEC(__NAG_COMPILER_BUILD) -#else - PRINT *, 'INFO:compiler[]' -#endif -#if defined(__CRAYXE) || defined(__CRAYXC) - PRINT *, 'INFO:compiler_wrapper[CrayPrgEnv]' -#endif - -#if 0 -! Identify the platform -#endif -#if defined(__linux) || defined(__linux__) || defined(linux) - PRINT *, 'INFO:platform[Linux]' -#elif defined(__CYGWIN__) - PRINT *, 'INFO:platform[Cygwin]' -#elif defined(__MINGW32__) - PRINT *, 'INFO:platform[MinGW]' -#elif defined(__APPLE__) - PRINT *, 'INFO:platform[Darwin]' -#elif defined(_WIN32) || defined(__WIN32__) || defined(WIN32) - PRINT *, 'INFO:platform[Windows]' -#elif defined(__FreeBSD__) || defined(__FreeBSD) - PRINT *, 'INFO:platform[FreeBSD]' -#elif defined(__NetBSD__) || defined(__NetBSD) - PRINT *, 'INFO:platform[NetBSD]' -#elif defined(__OpenBSD__) || defined(__OPENBSD) - PRINT *, 'INFO:platform[OpenBSD]' -#elif defined(__sun) || defined(sun) - PRINT *, 'INFO:platform[SunOS]' -#elif defined(_AIX) || defined(__AIX) || defined(__AIX__) || defined(__aix) || defined(__aix__) - PRINT *, 'INFO:platform[AIX]' -#elif defined(__hpux) || defined(__hpux__) - PRINT *, 'INFO:platform[HP-UX]' -#elif defined(__HAIKU__) - PRINT *, 'INFO:platform[Haiku]' -#elif defined(__BeOS) || defined(__BEOS__) || defined(_BEOS) - PRINT *, 'INFO:platform[BeOS]' -#elif defined(__QNX__) || defined(__QNXNTO__) - PRINT *, 'INFO:platform[QNX]' -#elif defined(__tru64) || defined(_tru64) || defined(__TRU64__) - PRINT *, 'INFO:platform[Tru64]' -#elif defined(__riscos) || defined(__riscos__) - PRINT *, 'INFO:platform[RISCos]' -#elif defined(__sinix) || defined(__sinix__) || defined(__SINIX__) - PRINT *, 'INFO:platform[SINIX]' -#elif defined(__UNIX_SV__) - PRINT *, 'INFO:platform[UNIX_SV]' -#elif defined(__bsdos__) - PRINT *, 'INFO:platform[BSDOS]' -#elif defined(_MPRAS) || defined(MPRAS) - PRINT *, 'INFO:platform[MP-RAS]' -#elif defined(__osf) || defined(__osf__) - PRINT *, 'INFO:platform[OSF1]' -#elif defined(_SCO_SV) || defined(SCO_SV) || defined(sco_sv) - PRINT *, 'INFO:platform[SCO_SV]' -#elif defined(__ultrix) || defined(__ultrix__) || defined(_ULTRIX) - PRINT *, 'INFO:platform[ULTRIX]' -#elif defined(__XENIX__) || defined(_XENIX) || defined(XENIX) - PRINT *, 'INFO:platform[Xenix]' -#else - PRINT *, 'INFO:platform[]' -#endif -#if defined(_WIN32) && (defined(__INTEL_COMPILER) || defined(__ICC)) -# if defined(_M_IA64) - PRINT *, 'INFO:arch[IA64]' -# elif defined(_M_X64) || defined(_M_AMD64) - PRINT *, 'INFO:arch[x64]' -# elif defined(_M_IX86) - PRINT *, 'INFO:arch[X86]' -# endif -#endif - -#if 0 -! Encode compiler version digits -#endif -#define DEC_8(n) (((n) / 10000000) % 10) -#define DEC_7(n) (((n) / 1000000) % 10) -#define DEC_6(n) (((n) / 100000) % 10) -#define DEC_5(n) (((n) / 10000) % 10) -#define DEC_4(n) (((n) / 1000) % 10) -#define DEC_3(n) (((n) / 100) % 10) -#define DEC_2(n) (((n) / 10) % 10) -#define DEC_1(n) (((n) ) % 10) -#define HEX_8(n) ((n)>>28 & 0xF) -#define HEX_7(n) ((n)>>24 & 0xF) -#define HEX_6(n) ((n)>>20 & 0xF) -#define HEX_5(n) ((n)>>16 & 0xF) -#define HEX_4(n) ((n)>>12 & 0xF) -#define HEX_3(n) ((n)>>8 & 0xF) -#define HEX_2(n) ((n)>>4 & 0xF) -#define HEX_1(n) ((n) & 0xF) -@CMAKE_Fortran_COMPILER_ID_VERSION_INFO@ - - END
diff --git a/share/cmake-3.18/Modules/CMakeFortranInformation.cmake b/share/cmake-3.18/Modules/CMakeFortranInformation.cmake deleted file mode 100644 index 9a4ce63..0000000 --- a/share/cmake-3.18/Modules/CMakeFortranInformation.cmake +++ /dev/null
@@ -1,222 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -include(CMakeLanguageInformation) - -# This file sets the basic flags for the Fortran language in CMake. -# It also loads the available platform file for the system-compiler -# if it exists. - -set(_INCLUDED_FILE 0) - -# Load compiler-specific information. -if(CMAKE_Fortran_COMPILER_ID) - include(Compiler/${CMAKE_Fortran_COMPILER_ID}-Fortran OPTIONAL) -endif() - -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_Fortran_COMPILER}" NAME_WE) -# since the gnu compiler has several names force g++ -if(CMAKE_COMPILER_IS_GNUG77) - set(CMAKE_BASE_NAME g77) -endif() -if(CMAKE_Fortran_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_Fortran_COMPILER_ID}-Fortran OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} OPTIONAL - RESULT_VARIABLE _INCLUDED_FILE) -endif () - -# load any compiler-wrapper specific information -if (CMAKE_Fortran_COMPILER_WRAPPER) - __cmake_include_compiler_wrapper(Fortran) -endif () - -# We specify the compiler information in the system file for some -# platforms, but this language may not have been enabled when the file -# was first included. Include it again to get the language info. -# Remove this when all compiler info is removed from system files. -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_SYSTEM_NAME} OPTIONAL) -endif () - -if(CMAKE_Fortran_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_Fortran_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_Fortran_ABI_FILES) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_Fortran) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_Fortran} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_Fortran "${_override}") -endif() - -if(NOT CMAKE_Fortran_COMPILE_OPTIONS_PIC) - set(CMAKE_Fortran_COMPILE_OPTIONS_PIC ${CMAKE_C_COMPILE_OPTIONS_PIC}) -endif() - -if(NOT CMAKE_Fortran_COMPILE_OPTIONS_PIE) - set(CMAKE_Fortran_COMPILE_OPTIONS_PIE ${CMAKE_C_COMPILE_OPTIONS_PIE}) -endif() -if(NOT CMAKE_Fortran_LINK_OPTIONS_PIE) - set(CMAKE_Fortran_LINK_OPTIONS_PIE ${CMAKE_C_LINK_OPTIONS_PIE}) -endif() -if(NOT CMAKE_Fortran_LINK_OPTIONS_NO_PIE) - set(CMAKE_Fortran_LINK_OPTIONS_NO_PIE ${CMAKE_C_LINK_OPTIONS_NO_PIE}) -endif() - -if(NOT CMAKE_Fortran_COMPILE_OPTIONS_DLL) - set(CMAKE_Fortran_COMPILE_OPTIONS_DLL ${CMAKE_C_COMPILE_OPTIONS_DLL}) -endif() - -# Create a set of shared library variable specific to Fortran -# For 90% of the systems, these are the same flags as the C versions -# so if these are not set just copy the flags from the c version -if(NOT DEFINED CMAKE_SHARED_LIBRARY_CREATE_Fortran_FLAGS) - set(CMAKE_SHARED_LIBRARY_CREATE_Fortran_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_Fortran_FLAGS) - set(CMAKE_SHARED_LIBRARY_Fortran_FLAGS ${CMAKE_SHARED_LIBRARY_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_Fortran_FLAGS) - set(CMAKE_SHARED_LIBRARY_LINK_Fortran_FLAGS ${CMAKE_SHARED_LIBRARY_LINK_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG) - set(CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG_SEP) - set(CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_RPATH_LINK_Fortran_FLAG) - set(CMAKE_SHARED_LIBRARY_RPATH_LINK_Fortran_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_EXE_EXPORTS_Fortran_FLAG) - set(CMAKE_EXE_EXPORTS_Fortran_FLAG ${CMAKE_EXE_EXPORTS_C_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_SONAME_Fortran_FLAG) - set(CMAKE_SHARED_LIBRARY_SONAME_Fortran_FLAG ${CMAKE_SHARED_LIBRARY_SONAME_C_FLAG}) -endif() - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_Fortran_FLAGS ${CMAKE_SHARED_LIBRARY_Fortran_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_Fortran_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_Fortran_FLAGS}) -endif() - -# repeat for modules -if(NOT DEFINED CMAKE_SHARED_MODULE_CREATE_Fortran_FLAGS) - set(CMAKE_SHARED_MODULE_CREATE_Fortran_FLAGS ${CMAKE_SHARED_MODULE_CREATE_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_MODULE_Fortran_FLAGS) - set(CMAKE_SHARED_MODULE_Fortran_FLAGS ${CMAKE_SHARED_MODULE_C_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_EXECUTABLE_RUNTIME_Fortran_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_Fortran_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG}) -endif() - -if(NOT DEFINED CMAKE_EXECUTABLE_RUNTIME_Fortran_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_Fortran_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_Fortran_FLAG_SEP}) -endif() - -if(NOT DEFINED CMAKE_EXECUTABLE_RPATH_LINK_Fortran_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_Fortran_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_Fortran_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_Fortran_WITH_RUNTIME_PATH) - set(CMAKE_SHARED_LIBRARY_LINK_Fortran_WITH_RUNTIME_PATH ${CMAKE_SHARED_LIBRARY_LINK_C_WITH_RUNTIME_PATH}) -endif() - -if(NOT CMAKE_INCLUDE_FLAG_Fortran) - set(CMAKE_INCLUDE_FLAG_Fortran ${CMAKE_INCLUDE_FLAG_C}) -endif() - -set(CMAKE_VERBOSE_MAKEFILE FALSE CACHE BOOL "If this value is on, makefiles will be generated without the .SILENT directive, and all commands will be echoed to the console during the make. This is useful for debugging only. With Visual Studio IDE projects all commands are done without /nologo.") - -set(CMAKE_Fortran_FLAGS_INIT "$ENV{FFLAGS} ${CMAKE_Fortran_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_Fortran_FLAGS "Flags used by the Fortran compiler") - -if(NOT CMAKE_Fortran_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_Fortran_COMPILER_LAUNCHER}) - set(CMAKE_Fortran_COMPILER_LAUNCHER "$ENV{CMAKE_Fortran_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for Fortran.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rule variables -# CMAKE_Fortran_CREATE_SHARED_LIBRARY -# CMAKE_Fortran_CREATE_SHARED_MODULE -# CMAKE_Fortran_COMPILE_OBJECT -# CMAKE_Fortran_LINK_EXECUTABLE - -# create a Fortran shared library -if(NOT CMAKE_Fortran_CREATE_SHARED_LIBRARY) - set(CMAKE_Fortran_CREATE_SHARED_LIBRARY - "<CMAKE_Fortran_COMPILER> <CMAKE_SHARED_LIBRARY_Fortran_FLAGS> <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_Fortran_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>") -endif() - -# create a Fortran shared module just copy the shared library rule -if(NOT CMAKE_Fortran_CREATE_SHARED_MODULE) - set(CMAKE_Fortran_CREATE_SHARED_MODULE ${CMAKE_Fortran_CREATE_SHARED_LIBRARY}) -endif() - -# Create a static archive incrementally for large object file counts. -# If CMAKE_Fortran_CREATE_STATIC_LIBRARY is set it will override these. -if(NOT DEFINED CMAKE_Fortran_ARCHIVE_CREATE) - set(CMAKE_Fortran_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_Fortran_ARCHIVE_APPEND) - set(CMAKE_Fortran_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_Fortran_ARCHIVE_FINISH) - set(CMAKE_Fortran_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -# compile a Fortran file into an object file -# (put -o after -c to workaround bug in at least one mpif77 wrapper) -if(NOT CMAKE_Fortran_COMPILE_OBJECT) - set(CMAKE_Fortran_COMPILE_OBJECT - "<CMAKE_Fortran_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -c <SOURCE> -o <OBJECT>") -endif() - -# link a fortran program -if(NOT CMAKE_Fortran_LINK_EXECUTABLE) - set(CMAKE_Fortran_LINK_EXECUTABLE - "<CMAKE_Fortran_COMPILER> <CMAKE_Fortran_LINK_FLAGS> <LINK_FLAGS> <FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -if(CMAKE_Fortran_STANDARD_LIBRARIES_INIT) - set(CMAKE_Fortran_STANDARD_LIBRARIES "${CMAKE_Fortran_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all Fortran applications.") - mark_as_advanced(CMAKE_Fortran_STANDARD_LIBRARIES) -endif() - -# set this variable so we can avoid loading this more than once. -set(CMAKE_Fortran_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeGenericSystem.cmake b/share/cmake-3.18/Modules/CMakeGenericSystem.cmake deleted file mode 100644 index 000fba1..0000000 --- a/share/cmake-3.18/Modules/CMakeGenericSystem.cmake +++ /dev/null
@@ -1,181 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(CMakeInitializeConfigs) - -set(CMAKE_SHARED_LIBRARY_C_FLAGS "") # -pic -set(CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS "-shared") # -shared -set(CMAKE_SHARED_LIBRARY_LINK_C_FLAGS "") # +s, flag for exe link to use shared lib -set(CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG "") # -rpath -set(CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP "") # : or empty -set(CMAKE_INCLUDE_FLAG_C "-I") # -I -set(CMAKE_LIBRARY_PATH_FLAG "-L") -set(CMAKE_LIBRARY_PATH_TERMINATOR "") # for the Digital Mars D compiler the link paths have to be terminated with a "/" -set(CMAKE_LINK_LIBRARY_FLAG "-l") - -set(CMAKE_LINK_LIBRARY_SUFFIX "") -set(CMAKE_STATIC_LIBRARY_PREFIX "lib") -set(CMAKE_STATIC_LIBRARY_SUFFIX ".a") -set(CMAKE_SHARED_LIBRARY_PREFIX "lib") # lib -set(CMAKE_SHARED_LIBRARY_SUFFIX ".so") # .so -set(CMAKE_EXECUTABLE_SUFFIX "") # .exe -set(CMAKE_DL_LIBS "dl") - -set(CMAKE_FIND_LIBRARY_PREFIXES "lib") -set(CMAKE_FIND_LIBRARY_SUFFIXES ".so" ".a") - -set(CMAKE_AUTOGEN_ORIGIN_DEPENDS ON) -set(CMAKE_AUTOMOC_COMPILER_PREDEFINES ON) -set(CMAKE_AUTOMOC_PATH_PREFIX ON) -set(CMAKE_AUTOMOC_MACRO_NAMES "Q_OBJECT" "Q_GADGET" "Q_NAMESPACE" "Q_NAMESPACE_EXPORT") - -# basically all general purpose OSs support shared libs -set_property(GLOBAL PROPERTY TARGET_SUPPORTS_SHARED_LIBS TRUE) - -set (CMAKE_SKIP_RPATH "NO" CACHE BOOL - "If set, runtime paths are not added when using shared libraries.") -set (CMAKE_SKIP_INSTALL_RPATH "NO" CACHE BOOL - "If set, runtime paths are not added when installing shared libraries, but are added when building.") - -set(CMAKE_VERBOSE_MAKEFILE FALSE CACHE BOOL "If this value is on, makefiles will be generated without the .SILENT directive, and all commands will be echoed to the console during the make. This is useful for debugging only. With Visual Studio IDE projects all commands are done without /nologo.") - -if(CMAKE_GENERATOR MATCHES "Make") - set(CMAKE_COLOR_MAKEFILE ON CACHE BOOL - "Enable/Disable color output during build." - ) - mark_as_advanced(CMAKE_COLOR_MAKEFILE) - if(DEFINED CMAKE_RULE_MESSAGES) - set_property(GLOBAL PROPERTY RULE_MESSAGES ${CMAKE_RULE_MESSAGES}) - endif() - if(DEFINED CMAKE_TARGET_MESSAGES) - set_property(GLOBAL PROPERTY TARGET_MESSAGES ${CMAKE_TARGET_MESSAGES}) - endif() -endif() - -if(NOT DEFINED CMAKE_EXPORT_COMPILE_COMMANDS AND CMAKE_GENERATOR MATCHES "Ninja|Unix Makefiles") - set(CMAKE_EXPORT_COMPILE_COMMANDS "$ENV{CMAKE_EXPORT_COMPILE_COMMANDS}" - CACHE BOOL "Enable/Disable output of compile commands during generation." - ) - mark_as_advanced(CMAKE_EXPORT_COMPILE_COMMANDS) -endif() - -# GetDefaultWindowsPrefixBase -# -# Compute the base directory for CMAKE_INSTALL_PREFIX based on: -# - is this 32-bit or 64-bit Windows -# - is this 32-bit or 64-bit CMake running -# - what architecture targets will be built -# -function(GetDefaultWindowsPrefixBase var) - - # Try to guess what architecture targets will end up being built as, - # even if CMAKE_SIZEOF_VOID_P is not computed yet... We need to know - # the architecture of the targets being built to choose the right - # default value for CMAKE_INSTALL_PREFIX. - # - if("${CMAKE_GENERATOR}" MATCHES "(Win64|IA64)") - set(arch_hint "x64") - elseif("${CMAKE_GENERATOR_PLATFORM}" MATCHES "ARM64") - set(arch_hint "ARM64") - elseif("${CMAKE_GENERATOR}" MATCHES "ARM") - set(arch_hint "ARM") - elseif("${CMAKE_SIZEOF_VOID_P}" STREQUAL "8") - set(arch_hint "x64") - elseif("$ENV{LIB}" MATCHES "(amd64|ia64)") - set(arch_hint "x64") - endif() - - if(NOT arch_hint) - set(arch_hint "x86") - endif() - - # default env in a 64-bit app on Win64: - # ProgramFiles=C:\Program Files - # ProgramFiles(x86)=C:\Program Files (x86) - # ProgramW6432=C:\Program Files - # - # default env in a 32-bit app on Win64: - # ProgramFiles=C:\Program Files (x86) - # ProgramFiles(x86)=C:\Program Files (x86) - # ProgramW6432=C:\Program Files - # - # default env in a 32-bit app on Win32: - # ProgramFiles=C:\Program Files - # ProgramFiles(x86) NOT DEFINED - # ProgramW6432 NOT DEFINED - - # By default, use the ProgramFiles env var as the base value of - # CMAKE_INSTALL_PREFIX: - # - set(_PREFIX_ENV_VAR "ProgramFiles") - - if ("$ENV{ProgramW6432}" STREQUAL "") - # running on 32-bit Windows - # must be a 32-bit CMake, too... - #message("guess: this is a 32-bit CMake running on 32-bit Windows") - else() - # running on 64-bit Windows - if ("$ENV{ProgramW6432}" STREQUAL "$ENV{ProgramFiles}") - # 64-bit CMake - #message("guess: this is a 64-bit CMake running on 64-bit Windows") - if(NOT "${arch_hint}" STREQUAL "x64") - # building 32-bit targets - set(_PREFIX_ENV_VAR "ProgramFiles(x86)") - endif() - else() - # 32-bit CMake - #message("guess: this is a 32-bit CMake running on 64-bit Windows") - if("${arch_hint}" STREQUAL "x64") - # building 64-bit targets - set(_PREFIX_ENV_VAR "ProgramW6432") - endif() - endif() - endif() - - #if("${arch_hint}" STREQUAL "x64") - # message("guess: you are building a 64-bit app") - #else() - # message("guess: you are building a 32-bit app") - #endif() - - if(NOT "$ENV{${_PREFIX_ENV_VAR}}" STREQUAL "") - file(TO_CMAKE_PATH "$ENV{${_PREFIX_ENV_VAR}}" _base) - elseif(NOT "$ENV{SystemDrive}" STREQUAL "") - set(_base "$ENV{SystemDrive}/Program Files") - else() - set(_base "C:/Program Files") - endif() - - set(${var} "${_base}" PARENT_SCOPE) -endfunction() - - -# Set a variable to indicate whether the value of CMAKE_INSTALL_PREFIX -# was initialized by the block below. This is useful for user -# projects to change the default prefix while still allowing the -# command line to override it. -if(NOT DEFINED CMAKE_INSTALL_PREFIX) - set(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT 1) -endif() - -# Choose a default install prefix for this platform. -if(CMAKE_HOST_UNIX) - set(CMAKE_INSTALL_PREFIX "/usr/local" - CACHE PATH "Install path prefix, prepended onto install directories.") -else() - GetDefaultWindowsPrefixBase(CMAKE_GENERIC_PROGRAM_FILES) - set(CMAKE_INSTALL_PREFIX - "${CMAKE_GENERIC_PROGRAM_FILES}/${PROJECT_NAME}" - CACHE PATH "Install path prefix, prepended onto install directories.") - set(CMAKE_GENERIC_PROGRAM_FILES) -endif() - -# Set a variable which will be used as component name in install() commands -# where no COMPONENT has been given: -set(CMAKE_INSTALL_DEFAULT_COMPONENT_NAME "Unspecified") - -mark_as_advanced( - CMAKE_SKIP_RPATH - CMAKE_SKIP_INSTALL_RPATH - CMAKE_VERBOSE_MAKEFILE -)
diff --git a/share/cmake-3.18/Modules/CMakeGraphVizOptions.cmake b/share/cmake-3.18/Modules/CMakeGraphVizOptions.cmake deleted file mode 100644 index be4a3be..0000000 --- a/share/cmake-3.18/Modules/CMakeGraphVizOptions.cmake +++ /dev/null
@@ -1,149 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CMakeGraphVizOptions --------------------- - -The builtin Graphviz support of CMake. - -Generating Graphviz files -^^^^^^^^^^^^^^^^^^^^^^^^^ - -CMake can generate `Graphviz <https://www.graphviz.org/>`_ files showing the -dependencies between the targets in a project, as well as external libraries -which are linked against. - -When running CMake with the ``--graphviz=foo.dot`` option, it produces: - -* a ``foo.dot`` file, showing all dependencies in the project -* a ``foo.dot.<target>`` file for each target, showing on which other targets - it depends -* a ``foo.dot.<target>.dependers`` file for each target, showing which other - targets depend on it - -Those .dot files can be converted to images using the *dot* command from the -Graphviz package: - -.. code-block:: shell - - dot -Tpng -o foo.png foo.dot - -The different dependency types ``PUBLIC``, ``INTERFACE`` and ``PRIVATE`` -are represented as solid, dashed and dotted edges. - -Variables specific to the Graphviz support -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The resulting graphs can be huge. The look and content of the generated graphs -can be controlled using the file ``CMakeGraphVizOptions.cmake``. This file is -first searched in :variable:`CMAKE_BINARY_DIR`, and then in -:variable:`CMAKE_SOURCE_DIR`. If found, the variables set in it are used to -adjust options for the generated Graphviz files. - -.. variable:: GRAPHVIZ_GRAPH_NAME - - The graph name. - - * Mandatory: NO - * Default: value of :variable:`CMAKE_PROJECT_NAME` - -.. variable:: GRAPHVIZ_GRAPH_HEADER - - The header written at the top of the Graphviz files. - - * Mandatory: NO - * Default: "node [ fontsize = "12" ];" - -.. variable:: GRAPHVIZ_NODE_PREFIX - - The prefix for each node in the Graphviz files. - - * Mandatory: NO - * Default: "node" - -.. variable:: GRAPHVIZ_EXECUTABLES - - Set to FALSE to exclude executables from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_STATIC_LIBS - - Set to FALSE to exclude static libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_SHARED_LIBS - - Set to FALSE to exclude shared libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_MODULE_LIBS - - Set to FALSE to exclude module libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_INTERFACE_LIBS - - Set to FALSE to exclude interface libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_OBJECT_LIBS - - Set to FALSE to exclude object libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_UNKNOWN_LIBS - - Set to FALSE to exclude unknown libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_EXTERNAL_LIBS - - Set to FALSE to exclude external libraries from the generated graphs. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_CUSTOM_TARGETS - - Set to TRUE to include custom targets in the generated graphs. - - * Mandatory: NO - * Default: FALSE - -.. variable:: GRAPHVIZ_IGNORE_TARGETS - - A list of regular expressions for names of targets to exclude from the - generated graphs. - - * Mandatory: NO - * Default: empty - -.. variable:: GRAPHVIZ_GENERATE_PER_TARGET - - Set to FALSE to not generate per-target graphs ``foo.dot.<target>``. - - * Mandatory: NO - * Default: TRUE - -.. variable:: GRAPHVIZ_GENERATE_DEPENDERS - - Set to FALSE to not generate depender graphs ``foo.dot.<target>.dependers``. - - * Mandatory: NO - * Default: TRUE -#]=======================================================================]
diff --git a/share/cmake-3.18/Modules/CMakeIOSInstallCombined.cmake b/share/cmake-3.18/Modules/CMakeIOSInstallCombined.cmake deleted file mode 100644 index 418bafd..0000000 --- a/share/cmake-3.18/Modules/CMakeIOSInstallCombined.cmake +++ /dev/null
@@ -1,312 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -cmake_policy(PUSH) -cmake_policy(SET CMP0057 NEW) # if IN_LIST - -# Function to print messages of this module -function(_ios_install_combined_message) - message("[iOS combined] " ${ARGN}) -endfunction() - -# Get build settings for the current target/config/SDK by running -# `xcodebuild -sdk ... -showBuildSettings` and parsing it's output -function(_ios_install_combined_get_build_setting sdk variable resultvar) - if("${sdk}" STREQUAL "") - message(FATAL_ERROR "`sdk` is empty") - endif() - - if("${variable}" STREQUAL "") - message(FATAL_ERROR "`variable` is empty") - endif() - - if("${resultvar}" STREQUAL "") - message(FATAL_ERROR "`resultvar` is empty") - endif() - - set( - cmd - xcodebuild -showBuildSettings - -sdk "${sdk}" - -target "${CURRENT_TARGET}" - -config "${CURRENT_CONFIG}" - ) - - execute_process( - COMMAND ${cmd} - WORKING_DIRECTORY "${CMAKE_BINARY_DIR}" - RESULT_VARIABLE result - OUTPUT_VARIABLE output - ) - - if(NOT result EQUAL 0) - message(FATAL_ERROR "Command failed (${result}): ${cmd}") - endif() - - if(NOT output MATCHES " ${variable} = ([^\n]*)") - if("${variable}" STREQUAL "VALID_ARCHS") - # VALID_ARCHS may be unset by user for given SDK - # (e.g. for build without simulator). - set("${resultvar}" "" PARENT_SCOPE) - return() - else() - message(FATAL_ERROR "${variable} not found.") - endif() - endif() - - set("${resultvar}" "${CMAKE_MATCH_1}" PARENT_SCOPE) -endfunction() - -# Get architectures of given SDK (iphonesimulator/iphoneos) -function(_ios_install_combined_get_valid_archs sdk resultvar) - cmake_policy(PUSH) - cmake_policy(SET CMP0007 NEW) - - if("${resultvar}" STREQUAL "") - message(FATAL_ERROR "`resultvar` is empty") - endif() - - _ios_install_combined_get_build_setting("${sdk}" "VALID_ARCHS" valid_archs) - - separate_arguments(valid_archs) - list(REMOVE_ITEM valid_archs "") # remove empty elements - list(REMOVE_DUPLICATES valid_archs) - - string(REPLACE ";" " " printable "${valid_archs}") - _ios_install_combined_message("Architectures (${sdk}): ${printable}") - - set("${resultvar}" "${valid_archs}" PARENT_SCOPE) - - cmake_policy(POP) -endfunction() - -# Final target can contain more architectures that specified by SDK. This -# function will run 'lipo -info' and parse output. Result will be returned -# as a CMake list. -function(_ios_install_combined_get_real_archs filename resultvar) - set(cmd "${_lipo_path}" -info "${filename}") - execute_process( - COMMAND ${cmd} - RESULT_VARIABLE result - OUTPUT_VARIABLE output - ERROR_VARIABLE output - OUTPUT_STRIP_TRAILING_WHITESPACE - ERROR_STRIP_TRAILING_WHITESPACE - ) - if(NOT result EQUAL 0) - message( - FATAL_ERROR "Command failed (${result}): ${cmd}\n\nOutput:\n${output}" - ) - endif() - - if(NOT output MATCHES "(Architectures in the fat file: [^\n]+ are|Non-fat file: [^\n]+ is architecture): ([^\n]*)") - message(FATAL_ERROR "Could not detect architecture from: ${output}") - endif() - - separate_arguments(CMAKE_MATCH_2) - set(${resultvar} ${CMAKE_MATCH_2} PARENT_SCOPE) -endfunction() - -# Run build command for the given SDK -function(_ios_install_combined_build sdk) - if("${sdk}" STREQUAL "") - message(FATAL_ERROR "`sdk` is empty") - endif() - - _ios_install_combined_message("Build `${CURRENT_TARGET}` for `${sdk}`") - - execute_process( - COMMAND - "${CMAKE_COMMAND}" - --build - . - --target "${CURRENT_TARGET}" - --config ${CURRENT_CONFIG} - -- - -sdk "${sdk}" - WORKING_DIRECTORY "${CMAKE_BINARY_DIR}" - RESULT_VARIABLE result - ) - - if(NOT result EQUAL 0) - message(FATAL_ERROR "Build failed") - endif() -endfunction() - -# Remove given architecture from file. This step needed only in rare cases -# when target was built in "unusual" way. Emit warning message. -function(_ios_install_combined_remove_arch lib arch) - _ios_install_combined_message( - "Warning! Unexpected architecture `${arch}` detected and will be removed " - "from file `${lib}`") - set(cmd "${_lipo_path}" -remove ${arch} -output ${lib} ${lib}) - execute_process( - COMMAND ${cmd} - RESULT_VARIABLE result - OUTPUT_VARIABLE output - ERROR_VARIABLE output - OUTPUT_STRIP_TRAILING_WHITESPACE - ERROR_STRIP_TRAILING_WHITESPACE - ) - if(NOT result EQUAL 0) - message( - FATAL_ERROR "Command failed (${result}): ${cmd}\n\nOutput:\n${output}" - ) - endif() -endfunction() - -# Check that 'lib' contains only 'archs' architectures (remove others). -function(_ios_install_combined_keep_archs lib archs) - _ios_install_combined_get_real_archs("${lib}" real_archs) - set(archs_to_remove ${real_archs}) - list(REMOVE_ITEM archs_to_remove ${archs}) - foreach(x ${archs_to_remove}) - _ios_install_combined_remove_arch("${lib}" "${x}") - endforeach() -endfunction() - -function(_ios_install_combined_detect_sdks this_sdk_var corr_sdk_var) - set(this_sdk "$ENV{PLATFORM_NAME}") - if("${this_sdk}" STREQUAL "") - message(FATAL_ERROR "Environment variable PLATFORM_NAME is empty") - endif() - - set(all_platforms "$ENV{SUPPORTED_PLATFORMS}") - if("${all_platforms}" STREQUAL "") - message(FATAL_ERROR "Environment variable SUPPORTED_PLATFORMS is empty") - endif() - - separate_arguments(all_platforms) - if(NOT this_sdk IN_LIST all_platforms) - message(FATAL_ERROR "`${this_sdk}` not found in `${all_platforms}`") - endif() - - list(REMOVE_ITEM all_platforms "" "${this_sdk}") - list(LENGTH all_platforms all_platforms_length) - if(NOT all_platforms_length EQUAL 1) - message(FATAL_ERROR "Expected one element: ${all_platforms}") - endif() - - set(${this_sdk_var} "${this_sdk}" PARENT_SCOPE) - set(${corr_sdk_var} "${all_platforms}" PARENT_SCOPE) -endfunction() - -# Create combined binary for the given target. -# -# Preconditions: -# * Target already installed at ${destination} -# for the ${PLATFORM_NAME} platform -# -# This function will: -# * Run build for the lacking platform, i.e. opposite to the ${PLATFORM_NAME} -# * Fuse both libraries by running lipo -function(ios_install_combined target destination) - if("${target}" STREQUAL "") - message(FATAL_ERROR "`target` is empty") - endif() - - if("${destination}" STREQUAL "") - message(FATAL_ERROR "`destination` is empty") - endif() - - if(NOT IS_ABSOLUTE "${destination}") - message(FATAL_ERROR "`destination` is not absolute: ${destination}") - endif() - - if(IS_DIRECTORY "${destination}" OR IS_SYMLINK "${destination}") - message(FATAL_ERROR "`destination` is no regular file: ${destination}") - endif() - - if("${CMAKE_BINARY_DIR}" STREQUAL "") - message(FATAL_ERROR "`CMAKE_BINARY_DIR` is empty") - endif() - - if(NOT IS_DIRECTORY "${CMAKE_BINARY_DIR}") - message(FATAL_ERROR "Is not a directory: ${CMAKE_BINARY_DIR}") - endif() - - if("${CMAKE_INSTALL_CONFIG_NAME}" STREQUAL "") - message(FATAL_ERROR "CMAKE_INSTALL_CONFIG_NAME is empty") - endif() - - set(cmd xcrun -f lipo) - - # Do not merge OUTPUT_VARIABLE and ERROR_VARIABLE since latter may contain - # some diagnostic information even for the successful run. - execute_process( - COMMAND ${cmd} - RESULT_VARIABLE result - OUTPUT_VARIABLE output - ERROR_VARIABLE error_output - OUTPUT_STRIP_TRAILING_WHITESPACE - ERROR_STRIP_TRAILING_WHITESPACE - ) - if(NOT result EQUAL 0) - message( - FATAL_ERROR "Command failed (${result}): ${cmd}\n\nOutput:\n${output}\nOutput(error):\n${error_output}" - ) - endif() - set(_lipo_path ${output}) - list(LENGTH _lipo_path len) - if(NOT len EQUAL 1) - message(FATAL_ERROR "Unexpected xcrun output: ${_lipo_path}") - endif() - if(NOT EXISTS "${_lipo_path}") - message(FATAL_ERROR "File not found: ${_lipo_path}") - endif() - - set(CURRENT_CONFIG "${CMAKE_INSTALL_CONFIG_NAME}") - set(CURRENT_TARGET "${target}") - - _ios_install_combined_message("Target: ${CURRENT_TARGET}") - _ios_install_combined_message("Config: ${CURRENT_CONFIG}") - _ios_install_combined_message("Destination: ${destination}") - - # Get SDKs - _ios_install_combined_detect_sdks(this_sdk corr_sdk) - - # Get architectures of the target - _ios_install_combined_get_valid_archs("${corr_sdk}" corr_valid_archs) - _ios_install_combined_get_valid_archs("${this_sdk}" this_valid_archs) - - # Return if there are no valid architectures for the SDK. - # (note that library already installed) - if("${corr_valid_archs}" STREQUAL "") - _ios_install_combined_message( - "No architectures detected for `${corr_sdk}` (skip)" - ) - return() - endif() - - # Trigger build of corresponding target - _ios_install_combined_build("${corr_sdk}") - - # Get location of the library in build directory - _ios_install_combined_get_build_setting( - "${corr_sdk}" "CONFIGURATION_BUILD_DIR" corr_build_dir) - _ios_install_combined_get_build_setting( - "${corr_sdk}" "EXECUTABLE_PATH" corr_executable_path) - set(corr "${corr_build_dir}/${corr_executable_path}") - - _ios_install_combined_keep_archs("${corr}" "${corr_valid_archs}") - _ios_install_combined_keep_archs("${destination}" "${this_valid_archs}") - - _ios_install_combined_message("Current: ${destination}") - _ios_install_combined_message("Corresponding: ${corr}") - - set(cmd "${_lipo_path}" -create ${corr} ${destination} -output ${destination}) - - execute_process( - COMMAND ${cmd} - WORKING_DIRECTORY ${CMAKE_BINARY_DIR} - RESULT_VARIABLE result - ) - - if(NOT result EQUAL 0) - message(FATAL_ERROR "Command failed: ${cmd}") - endif() - - _ios_install_combined_message("Install done: ${destination}") -endfunction() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CMakeOBJCCompiler.cmake.in b/share/cmake-3.18/Modules/CMakeOBJCCompiler.cmake.in deleted file mode 100644 index 1555517..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCCompiler.cmake.in +++ /dev/null
@@ -1,69 +0,0 @@ -set(CMAKE_OBJC_COMPILER "@CMAKE_OBJC_COMPILER@") -set(CMAKE_OBJC_COMPILER_ARG1 "@CMAKE_OBJC_COMPILER_ARG1@") -set(CMAKE_OBJC_COMPILER_ID "@CMAKE_OBJC_COMPILER_ID@") -set(CMAKE_OBJC_COMPILER_VERSION "@CMAKE_OBJC_COMPILER_VERSION@") -set(CMAKE_OBJC_COMPILER_VERSION_INTERNAL "@CMAKE_OBJC_COMPILER_VERSION_INTERNAL@") -set(CMAKE_OBJC_COMPILER_WRAPPER "@CMAKE_OBJC_COMPILER_WRAPPER@") -set(CMAKE_OBJC_STANDARD_COMPUTED_DEFAULT "@CMAKE_OBJC_STANDARD_COMPUTED_DEFAULT@") -set(CMAKE_OBJC_COMPILE_FEATURES "@CMAKE_OBJC_COMPILE_FEATURES@") -set(CMAKE_OBJC90_COMPILE_FEATURES "@CMAKE_OBJC90_COMPILE_FEATURES@") -set(CMAKE_OBJC99_COMPILE_FEATURES "@CMAKE_OBJC99_COMPILE_FEATURES@") -set(CMAKE_OBJC11_COMPILE_FEATURES "@CMAKE_OBJC11_COMPILE_FEATURES@") - -set(CMAKE_OBJC_PLATFORM_ID "@CMAKE_OBJC_PLATFORM_ID@") -set(CMAKE_OBJC_SIMULATE_ID "@CMAKE_OBJC_SIMULATE_ID@") -set(CMAKE_OBJC_COMPILER_FRONTEND_VARIANT "@CMAKE_OBJC_COMPILER_FRONTEND_VARIANT@") -set(CMAKE_OBJC_SIMULATE_VERSION "@CMAKE_OBJC_SIMULATE_VERSION@") -@_SET_CMAKE_OBJC_COMPILER_ARCHITECTURE_ID@ -@SET_CMAKE_XCODE_ARCHS@ -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_OBJC_COMPILER_AR "@CMAKE_OBJC_COMPILER_AR@") -set(CMAKE_RANLIB "@CMAKE_RANLIB@") -set(CMAKE_OBJC_COMPILER_RANLIB "@CMAKE_OBJC_COMPILER_RANLIB@") -set(CMAKE_LINKER "@CMAKE_LINKER@") -set(CMAKE_MT "@CMAKE_MT@") -set(CMAKE_COMPILER_IS_GNUOBJC @CMAKE_COMPILER_IS_GNUOBJC@) -set(CMAKE_OBJC_COMPILER_LOADED 1) -set(CMAKE_OBJC_COMPILER_WORKS @CMAKE_OBJC_COMPILER_WORKS@) -set(CMAKE_OBJC_ABI_COMPILED @CMAKE_OBJC_ABI_COMPILED@) - -set(CMAKE_OBJC_COMPILER_ENV_VAR "OBJC") - -set(CMAKE_OBJC_COMPILER_ID_RUN 1) -set(CMAKE_OBJC_SOURCE_FILE_EXTENSIONS m) -set(CMAKE_OBJC_IGNORE_EXTENSIONS h;H;o;O) -set(CMAKE_OBJC_LINKER_PREFERENCE 5) - -foreach (lang C CXX OBJCXX) - foreach(extension IN LISTS CMAKE_OBJC_SOURCE_FILE_EXTENSIONS) - if (CMAKE_${lang}_COMPILER_ID_RUN) - list(REMOVE_ITEM CMAKE_${lang}_SOURCE_FILE_EXTENSIONS ${extension}) - endif() - endforeach() -endforeach() - -# Save compiler ABI information. -set(CMAKE_OBJC_SIZEOF_DATA_PTR "@CMAKE_OBJC_SIZEOF_DATA_PTR@") -set(CMAKE_OBJC_COMPILER_ABI "@CMAKE_OBJC_COMPILER_ABI@") -set(CMAKE_OBJC_LIBRARY_ARCHITECTURE "@CMAKE_OBJC_LIBRARY_ARCHITECTURE@") - -if(CMAKE_OBJC_SIZEOF_DATA_PTR) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_OBJC_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_OBJC_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_OBJC_COMPILER_ABI}") -endif() - -if(CMAKE_OBJC_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_OBJC_LIBRARY_ARCHITECTURE@") -endif() - -@CMAKE_OBJC_COMPILER_CUSTOM_CODE@ -@CMAKE_OBJC_SYSROOT_FLAG_CODE@ -@CMAKE_OBJC_OSX_DEPLOYMENT_TARGET_FLAG_CODE@ - -set(CMAKE_OBJC_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_OBJC_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_OBJC_IMPLICIT_LINK_LIBRARIES "@CMAKE_OBJC_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_OBJC_IMPLICIT_LINK_DIRECTORIES "@CMAKE_OBJC_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_OBJC_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_OBJC_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@")
diff --git a/share/cmake-3.18/Modules/CMakeOBJCCompilerABI.m b/share/cmake-3.18/Modules/CMakeOBJCCompilerABI.m deleted file mode 100644 index 8fa8511..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCCompilerABI.m +++ /dev/null
@@ -1,20 +0,0 @@ -#ifdef __cplusplus -# error "A C++ compiler has been selected for Objective-C." -#endif - -/*--------------------------------------------------------------------------*/ - -#include "CMakeCompilerABI.h" - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char *argv[]) -{ - int require = 0; - require += info_sizeof_dptr[argc]; -#if defined(ABI_ID) - require += info_abi[argc]; -#endif - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeOBJCCompilerId.m.in b/share/cmake-3.18/Modules/CMakeOBJCCompilerId.m.in deleted file mode 100644 index 2b8aa30..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCCompilerId.m.in +++ /dev/null
@@ -1,63 +0,0 @@ -#ifdef __cplusplus -# error "An Objective-C++ compiler has been selected for Objective-C." -#endif - -@CMAKE_OBJC_COMPILER_ID_CONTENT@ - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_compiler = "INFO" ":" "compiler[" COMPILER_ID "]"; -#ifdef SIMULATE_ID -char const* info_simulate = "INFO" ":" "simulate[" SIMULATE_ID "]"; -#endif - -#ifdef __QNXNTO__ -char const* qnxnto = "INFO" ":" "qnxnto[]"; -#endif - -@CMAKE_OBJC_COMPILER_ID_PLATFORM_CONTENT@ -@CMAKE_OBJC_COMPILER_ID_ERROR_FOR_TEST@ - -#if !defined(__STDC__) -# if (defined(_MSC_VER) && !defined(__clang__)) \ - || (defined(__ibmxl__) || defined(__IBMC__)) -# define C_DIALECT "90" -# else -# define C_DIALECT -# endif -#elif __STDC_VERSION__ >= 201000L -# define C_DIALECT "11" -#elif __STDC_VERSION__ >= 199901L -# define C_DIALECT "99" -#else -# define C_DIALECT "90" -#endif -const char* info_language_dialect_default = - "INFO" ":" "dialect_default[" C_DIALECT "]"; - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_compiler[argc]; - require += info_platform[argc]; - require += info_arch[argc]; -#ifdef COMPILER_VERSION_MAJOR - require += info_version[argc]; -#endif -#ifdef COMPILER_VERSION_INTERNAL - require += info_version_internal[argc]; -#endif -#ifdef SIMULATE_ID - require += info_simulate[argc]; -#endif -#ifdef SIMULATE_VERSION_MAJOR - require += info_simulate_version[argc]; -#endif - require += info_language_dialect_default[argc]; - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeOBJCInformation.cmake b/share/cmake-3.18/Modules/CMakeOBJCInformation.cmake deleted file mode 100644 index b3da82d..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCInformation.cmake +++ /dev/null
@@ -1,193 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file sets the basic flags for the Objective-C language in CMake. -# It also loads the available platform file for the system-compiler -# if it exists. -# It also loads a system - compiler - processor (or target hardware) -# specific file, which is mainly useful for crosscompiling and embedded systems. - -include(CMakeLanguageInformation) - -# some compilers use different extensions (e.g. sdcc uses .rel) -# so set the extension here first so it can be overridden by the compiler specific file -set(CMAKE_OBJC_OUTPUT_EXTENSION .o) - -if(NOT CMAKE_INCLUDE_FLAG_OBJC) - set(CMAKE_INCLUDE_FLAG_OBJC ${CMAKE_INCLUDE_FLAG_C}) -endif() - -set(_INCLUDED_FILE 0) - -# Load compiler-specific information. -if(CMAKE_OBJC_COMPILER_ID) - include(Compiler/${CMAKE_OBJC_COMPILER_ID}-OBJC OPTIONAL) -endif() - -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_OBJC_COMPILER}" NAME_WE) -if(CMAKE_COMPILER_IS_GNUOBJC) - set(CMAKE_BASE_NAME gcc) -endif() - - -# load a hardware specific file, mostly useful for embedded compilers -if(CMAKE_SYSTEM_PROCESSOR) - if(CMAKE_OBJC_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_OBJC_COMPILER_ID}-OBJC-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) - endif() - if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif () -endif() - - -# load the system- and compiler specific files -if(CMAKE_OBJC_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_OBJC_COMPILER_ID}-OBJC - OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} - OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif () - -# load any compiler-wrapper specific information -if (CMAKE_OBJC_COMPILER_WRAPPER) - __cmake_include_compiler_wrapper(OBJC) -endif () - -# We specify the compiler information in the system file for some -# platforms, but this language may not have been enabled when the file -# was first included. Include it again to get the language info. -# Remove this when all compiler info is removed from system files. -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_SYSTEM_NAME} OPTIONAL) -endif () - -if(CMAKE_OBJC_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_OBJC_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_OBJC_ABI_FILES) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_OBJC) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_OBJC} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_OBJC "${_override}") -endif() - - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_OBJC_FLAGS ${CMAKE_SHARED_LIBRARY_OBJC_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_OBJC_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_OBJC_FLAGS}) -endif() - -set(CMAKE_OBJC_FLAGS_INIT "$ENV{OBJCFLAGS} ${CMAKE_OBJC_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_OBJC_FLAGS "Flags used by the Objective-C compiler") - -if(CMAKE_OBJC_STANDARD_LIBRARIES_INIT) - set(CMAKE_OBJC_STANDARD_LIBRARIES "${CMAKE_OBJC_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all Objective-C applications.") - mark_as_advanced(CMAKE_OBJC_STANDARD_LIBRARIES) -endif() - -if(NOT CMAKE_OBJC_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_OBJC_COMPILER_LAUNCHER}) - set(CMAKE_OBJC_COMPILER_LAUNCHER "$ENV{CMAKE_OBJC_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for OBJC.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rule variables - -# CMAKE_OBJC_CREATE_SHARED_LIBRARY -# CMAKE_OBJC_CREATE_SHARED_MODULE -# CMAKE_OBJC_COMPILE_OBJECT -# CMAKE_OBJC_LINK_EXECUTABLE - -# variables supplied by the generator at use time -# <TARGET> -# <TARGET_BASE> the target without the suffix -# <OBJECTS> -# <OBJECT> -# <LINK_LIBRARIES> -# <FLAGS> -# <LINK_FLAGS> - -# Objective-C compiler information -# <CMAKE_OBJC_COMPILER> -# <CMAKE_SHARED_LIBRARY_CREATE_OBJC_FLAGS> -# <CMAKE_SHARED_MODULE_CREATE_OBJC_FLAGS> -# <CMAKE_OBJC_LINK_FLAGS> - -# Static library tools -# <CMAKE_AR> -# <CMAKE_RANLIB> - - -# create an Objective-C shared library -if(NOT CMAKE_OBJC_CREATE_SHARED_LIBRARY) - set(CMAKE_OBJC_CREATE_SHARED_LIBRARY - "<CMAKE_OBJC_COMPILER> <CMAKE_SHARED_LIBRARY_OBJC_FLAGS> <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_OBJC_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>") -endif() - -# create an Objective-C shared module just copy the shared library rule -if(NOT CMAKE_OBJC_CREATE_SHARED_MODULE) - set(CMAKE_OBJC_CREATE_SHARED_MODULE ${CMAKE_OBJC_CREATE_SHARED_LIBRARY}) -endif() - -# Create an static archive incrementally for large object file counts. -# If CMAKE_OBJC_CREATE_STATIC_LIBRARY is set it will override these. -if(NOT DEFINED CMAKE_OBJC_ARCHIVE_CREATE) - set(CMAKE_OBJC_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_OBJC_ARCHIVE_APPEND) - set(CMAKE_OBJC_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_OBJC_ARCHIVE_FINISH) - set(CMAKE_OBJC_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -# compile an Objective-C file into an object file -if(NOT CMAKE_OBJC_COMPILE_OBJECT) - set(CMAKE_OBJC_COMPILE_OBJECT - "<CMAKE_OBJC_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -x objective-c -o <OBJECT> -c <SOURCE>") -endif() - -if(NOT CMAKE_OBJC_LINK_EXECUTABLE) - set(CMAKE_OBJC_LINK_EXECUTABLE - "<CMAKE_OBJC_COMPILER> <FLAGS> <CMAKE_OBJC_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_OBJC_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_OBJC_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJC_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_OBJC_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_OBJC_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJC_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_OBJC_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_OBJC_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_OBJC_FLAG}) -endif() - -set(CMAKE_OBJC_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeOBJCXXCompiler.cmake.in b/share/cmake-3.18/Modules/CMakeOBJCXXCompiler.cmake.in deleted file mode 100644 index b6452c4..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCXXCompiler.cmake.in +++ /dev/null
@@ -1,79 +0,0 @@ -set(CMAKE_OBJCXX_COMPILER "@CMAKE_OBJCXX_COMPILER@") -set(CMAKE_OBJCXX_COMPILER_ARG1 "@CMAKE_OBJCXX_COMPILER_ARG1@") -set(CMAKE_OBJCXX_COMPILER_ID "@CMAKE_OBJCXX_COMPILER_ID@") -set(CMAKE_OBJCXX_COMPILER_VERSION "@CMAKE_OBJCXX_COMPILER_VERSION@") -set(CMAKE_OBJCXX_COMPILER_VERSION_INTERNAL "@CMAKE_OBJCXX_COMPILER_VERSION_INTERNAL@") -set(CMAKE_OBJCXX_COMPILER_WRAPPER "@CMAKE_OBJCXX_COMPILER_WRAPPER@") -set(CMAKE_OBJCXX_STANDARD_COMPUTED_DEFAULT "@CMAKE_OBJCXX_STANDARD_COMPUTED_DEFAULT@") -set(CMAKE_OBJCXX_COMPILE_FEATURES "@CMAKE_OBJCXX_COMPILE_FEATURES@") -set(CMAKE_OBJCXX98_COMPILE_FEATURES "@CMAKE_OBJCXX98_COMPILE_FEATURES@") -set(CMAKE_OBJCXX11_COMPILE_FEATURES "@CMAKE_OBJCXX11_COMPILE_FEATURES@") -set(CMAKE_OBJCXX14_COMPILE_FEATURES "@CMAKE_OBJCXX14_COMPILE_FEATURES@") -set(CMAKE_OBJCXX17_COMPILE_FEATURES "@CMAKE_OBJCXX17_COMPILE_FEATURES@") -set(CMAKE_OBJCXX20_COMPILE_FEATURES "@CMAKE_OBJCXX20_COMPILE_FEATURES@") - -set(CMAKE_OBJCXX_PLATFORM_ID "@CMAKE_OBJCXX_PLATFORM_ID@") -set(CMAKE_OBJCXX_SIMULATE_ID "@CMAKE_OBJCXX_SIMULATE_ID@") -set(CMAKE_OBJCXX_COMPILER_FRONTEND_VARIANT "@CMAKE_OBJCXX_COMPILER_FRONTEND_VARIANT@") -set(CMAKE_OBJCXX_SIMULATE_VERSION "@CMAKE_OBJCXX_SIMULATE_VERSION@") -@_SET_CMAKE_OBJCXX_COMPILER_ARCHITECTURE_ID@ -@SET_CMAKE_XCODE_ARCHS@ -set(CMAKE_AR "@CMAKE_AR@") -set(CMAKE_OBJCXX_COMPILER_AR "@CMAKE_OBJCXX_COMPILER_AR@") -set(CMAKE_RANLIB "@CMAKE_RANLIB@") -set(CMAKE_OBJCXX_COMPILER_RANLIB "@CMAKE_OBJCXX_COMPILER_RANLIB@") -set(CMAKE_LINKER "@CMAKE_LINKER@") -set(CMAKE_MT "@CMAKE_MT@") -set(CMAKE_COMPILER_IS_GNUOBJCXX @CMAKE_COMPILER_IS_GNUOBJCXX@) -set(CMAKE_OBJCXX_COMPILER_LOADED 1) -set(CMAKE_OBJCXX_COMPILER_WORKS @CMAKE_OBJCXX_COMPILER_WORKS@) -set(CMAKE_OBJCXX_ABI_COMPILED @CMAKE_OBJCXX_ABI_COMPILED@) - -set(CMAKE_OBJCXX_COMPILER_ENV_VAR "OBJCXX") - -set(CMAKE_OBJCXX_COMPILER_ID_RUN 1) -set(CMAKE_OBJCXX_SOURCE_FILE_EXTENSIONS M;m;mm) -set(CMAKE_OBJCXX_IGNORE_EXTENSIONS inl;h;hpp;HPP;H;o;O) - -if (CMAKE_OBJC_COMPILER_ID_RUN) - foreach(extension IN LISTS CMAKE_OBJC_SOURCE_FILE_EXTENSIONS) - list(REMOVE_ITEM CMAKE_OBJCXX_SOURCE_FILE_EXTENSIONS ${extension}) - endforeach() -endif() - -foreach (lang C CXX OBJC) - foreach(extension IN LISTS CMAKE_OBJCXX_SOURCE_FILE_EXTENSIONS) - if (CMAKE_${lang}_COMPILER_ID_RUN) - list(REMOVE_ITEM CMAKE_${lang}_SOURCE_FILE_EXTENSIONS ${extension}) - endif() - endforeach() -endforeach() - -set(CMAKE_OBJCXX_LINKER_PREFERENCE 25) -set(CMAKE_OBJCXX_LINKER_PREFERENCE_PROPAGATES 1) - -# Save compiler ABI information. -set(CMAKE_OBJCXX_SIZEOF_DATA_PTR "@CMAKE_OBJCXX_SIZEOF_DATA_PTR@") -set(CMAKE_OBJCXX_COMPILER_ABI "@CMAKE_OBJCXX_COMPILER_ABI@") -set(CMAKE_OBJCXX_LIBRARY_ARCHITECTURE "@CMAKE_OBJCXX_LIBRARY_ARCHITECTURE@") - -if(CMAKE_OBJCXX_SIZEOF_DATA_PTR) - set(CMAKE_SIZEOF_VOID_P "${CMAKE_OBJCXX_SIZEOF_DATA_PTR}") -endif() - -if(CMAKE_OBJCXX_COMPILER_ABI) - set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_OBJCXX_COMPILER_ABI}") -endif() - -if(CMAKE_OBJCXX_LIBRARY_ARCHITECTURE) - set(CMAKE_LIBRARY_ARCHITECTURE "@CMAKE_OBJCXX_LIBRARY_ARCHITECTURE@") -endif() - -@CMAKE_OBJCXX_COMPILER_CUSTOM_CODE@ -@CMAKE_OBJCXX_SYSROOT_FLAG_CODE@ -@CMAKE_OBJCXX_OSX_DEPLOYMENT_TARGET_FLAG_CODE@ - -set(CMAKE_OBJCXX_IMPLICIT_INCLUDE_DIRECTORIES "@CMAKE_OBJCXX_IMPLICIT_INCLUDE_DIRECTORIES@") -set(CMAKE_OBJCXX_IMPLICIT_LINK_LIBRARIES "@CMAKE_OBJCXX_IMPLICIT_LINK_LIBRARIES@") -set(CMAKE_OBJCXX_IMPLICIT_LINK_DIRECTORIES "@CMAKE_OBJCXX_IMPLICIT_LINK_DIRECTORIES@") -set(CMAKE_OBJCXX_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "@CMAKE_OBJCXX_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES@")
diff --git a/share/cmake-3.18/Modules/CMakeOBJCXXCompilerABI.mm b/share/cmake-3.18/Modules/CMakeOBJCXXCompilerABI.mm deleted file mode 100644 index 288a58c..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCXXCompilerABI.mm +++ /dev/null
@@ -1,20 +0,0 @@ -#ifndef __cplusplus -# error "A C compiler has been selected for Objective-C++." -#endif - -/*--------------------------------------------------------------------------*/ - -#include "CMakeCompilerABI.h" - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char *argv[]) -{ - int require = 0; - require += info_sizeof_dptr[argc]; -#if defined(ABI_ID) - require += info_abi[argc]; -#endif - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeOBJCXXCompilerId.mm.in b/share/cmake-3.18/Modules/CMakeOBJCXXCompilerId.mm.in deleted file mode 100644 index fe04de1..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCXXCompilerId.mm.in +++ /dev/null
@@ -1,68 +0,0 @@ -/* This source file must have a .cpp extension so that all C++ compilers - recognize the extension without flags. Borland does not know .cxx for - example. */ -#ifndef __cplusplus -# error "An Objective-C compiler has been selected for Objective-C++." -#endif - -@CMAKE_OBJCXX_COMPILER_ID_CONTENT@ - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_compiler = "INFO" ":" "compiler[" COMPILER_ID "]"; -#ifdef SIMULATE_ID -char const* info_simulate = "INFO" ":" "simulate[" SIMULATE_ID "]"; -#endif - -#ifdef __QNXNTO__ -char const* qnxnto = "INFO" ":" "qnxnto[]"; -#endif - -@CMAKE_OBJCXX_COMPILER_ID_PLATFORM_CONTENT@ -@CMAKE_OBJCXX_COMPILER_ID_ERROR_FOR_TEST@ - -#if defined(_MSC_VER) && defined(_MSVC_LANG) -#define CXX_STD _MSVC_LANG -#else -#define CXX_STD __cplusplus -#endif - -const char* info_language_dialect_default = "INFO" ":" "dialect_default[" -#if CXX_STD > 201703L - "20" -#elif CXX_STD >= 201703L - "17" -#elif CXX_STD >= 201402L - "14" -#elif CXX_STD >= 201103L - "11" -#else - "98" -#endif -"]"; - -/*--------------------------------------------------------------------------*/ - -int main(int argc, char* argv[]) -{ - int require = 0; - require += info_compiler[argc]; - require += info_platform[argc]; -#ifdef COMPILER_VERSION_MAJOR - require += info_version[argc]; -#endif -#ifdef COMPILER_VERSION_INTERNAL - require += info_version_internal[argc]; -#endif -#ifdef SIMULATE_ID - require += info_simulate[argc]; -#endif -#ifdef SIMULATE_VERSION_MAJOR - require += info_simulate_version[argc]; -#endif - require += info_language_dialect_default[argc]; - (void)argv; - return require; -}
diff --git a/share/cmake-3.18/Modules/CMakeOBJCXXInformation.cmake b/share/cmake-3.18/Modules/CMakeOBJCXXInformation.cmake deleted file mode 100644 index 71beb7f..0000000 --- a/share/cmake-3.18/Modules/CMakeOBJCXXInformation.cmake +++ /dev/null
@@ -1,278 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file sets the basic flags for the Objective-C++ language in CMake. -# It also loads the available platform file for the system-compiler -# if it exists. -# It also loads a system - compiler - processor (or target hardware) -# specific file, which is mainly useful for crosscompiling and embedded systems. - -include(CMakeLanguageInformation) - -# some compilers use different extensions (e.g. sdcc uses .rel) -# so set the extension here first so it can be overridden by the compiler specific file -set(CMAKE_OBJCXX_OUTPUT_EXTENSION .o) - -set(_INCLUDED_FILE 0) - -# Load compiler-specific information. -if(CMAKE_OBJCXX_COMPILER_ID) - include(Compiler/${CMAKE_OBJCXX_COMPILER_ID}-OBJCXX OPTIONAL) -endif() - -set(CMAKE_BASE_NAME) -get_filename_component(CMAKE_BASE_NAME "${CMAKE_OBJCXX_COMPILER}" NAME_WE) -# since the gnu compiler has several names force g++ -if(CMAKE_COMPILER_IS_GNUOBJCXX) - set(CMAKE_BASE_NAME g++) -endif() - - -# load a hardware specific file, mostly useful for embedded compilers -if(CMAKE_SYSTEM_PROCESSOR) - if(CMAKE_OBJCXX_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_OBJCXX_COMPILER_ID}-OBJCXX-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) - endif() - if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME}-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif () -endif() - -# load the system- and compiler specific files -if(CMAKE_OBJCXX_COMPILER_ID) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_OBJCXX_COMPILER_ID}-OBJCXX OPTIONAL RESULT_VARIABLE _INCLUDED_FILE) -endif() -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_BASE_NAME} OPTIONAL - RESULT_VARIABLE _INCLUDED_FILE) -endif () - -# load any compiler-wrapper specific information -if (CMAKE_OBJCXX_COMPILER_WRAPPER) - __cmake_include_compiler_wrapper(OBJCXX) -endif () - -# We specify the compiler information in the system file for some -# platforms, but this language may not have been enabled when the file -# was first included. Include it again to get the language info. -# Remove this when all compiler info is removed from system files. -if (NOT _INCLUDED_FILE) - include(Platform/${CMAKE_SYSTEM_NAME} OPTIONAL) -endif () - -if(CMAKE_OBJCXX_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_OBJCXX_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_OBJCXX_ABI_FILES) -endif() - -# This should be included before the _INIT variables are -# used to initialize the cache. Since the rule variables -# have if blocks on them, users can still define them here. -# But, it should still be after the platform file so changes can -# be made to those values. - -if(CMAKE_USER_MAKE_RULES_OVERRIDE) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE "${_override}") -endif() - -if(CMAKE_USER_MAKE_RULES_OVERRIDE_OBJCXX) - # Save the full path of the file so try_compile can use it. - include(${CMAKE_USER_MAKE_RULES_OVERRIDE_OBJCXX} RESULT_VARIABLE _override) - set(CMAKE_USER_MAKE_RULES_OVERRIDE_OBJCXX "${_override}") -endif() - - -# Create a set of shared library variable specific to Objective-C++ -# For 90% of the systems, these are the same flags as the Objective-C versions -# so if these are not set just copy the flags from the Objective-C version -if(NOT CMAKE_SHARED_LIBRARY_CREATE_OBJCXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_CREATE_OBJCXX_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_OBJC_FLAGS}) -endif() - -if(NOT CMAKE_OBJCXX_COMPILE_OPTIONS_PIC) - set(CMAKE_OBJCXX_COMPILE_OPTIONS_PIC ${CMAKE_OBJC_COMPILE_OPTIONS_PIC}) -endif() - -if(NOT CMAKE_OBJCXX_COMPILE_OPTIONS_PIE) - set(CMAKE_OBJCXX_COMPILE_OPTIONS_PIE ${CMAKE_OBJC_COMPILE_OPTIONS_PIE}) -endif() -if(NOT CMAKE_OBJCXX_LINK_OPTIONS_PIE) - set(CMAKE_OBJCXX_LINK_OPTIONS_PIE ${CMAKE_OBJC_LINK_OPTIONS_PIE}) -endif() -if(NOT CMAKE_OBJCXX_LINK_OPTIONS_NO_PIE) - set(CMAKE_OBJCXX_LINK_OPTIONS_NO_PIE ${CMAKE_OBJC_LINK_OPTIONS_NO_PIE}) -endif() - -if(NOT CMAKE_OBJCXX_COMPILE_OPTIONS_DLL) - set(CMAKE_OBJCXX_COMPILE_OPTIONS_DLL ${CMAKE_OBJC_COMPILE_OPTIONS_DLL}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_OBJCXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_OBJCXX_FLAGS ${CMAKE_SHARED_LIBRARY_OBJC_FLAGS}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_OBJCXX_FLAGS) - set(CMAKE_SHARED_LIBRARY_LINK_OBJCXX_FLAGS ${CMAKE_SHARED_LIBRARY_LINK_OBJC_FLAGS}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG) - set(CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJC_FLAG}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG_SEP) - set(CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJC_FLAG_SEP}) -endif() - -if(NOT CMAKE_SHARED_LIBRARY_RPATH_LINK_OBJCXX_FLAG) - set(CMAKE_SHARED_LIBRARY_RPATH_LINK_OBJCXX_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_OBJC_FLAG}) -endif() - -if(NOT DEFINED CMAKE_EXE_EXPORTS_OBJCXX_FLAG) - set(CMAKE_EXE_EXPORTS_OBJCXX_FLAG ${CMAKE_EXE_EXPORTS_OBJC_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_SONAME_OBJCXX_FLAG) - set(CMAKE_SHARED_LIBRARY_SONAME_OBJCXX_FLAG ${CMAKE_SHARED_LIBRARY_SONAME_OBJC_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_OBJCXX_FLAG) - set(CMAKE_EXECUTABLE_RUNTIME_OBJCXX_FLAG ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG}) -endif() - -if(NOT CMAKE_EXECUTABLE_RUNTIME_OBJCXX_FLAG_SEP) - set(CMAKE_EXECUTABLE_RUNTIME_OBJCXX_FLAG_SEP ${CMAKE_SHARED_LIBRARY_RUNTIME_OBJCXX_FLAG_SEP}) -endif() - -if(NOT CMAKE_EXECUTABLE_RPATH_LINK_OBJCXX_FLAG) - set(CMAKE_EXECUTABLE_RPATH_LINK_OBJCXX_FLAG ${CMAKE_SHARED_LIBRARY_RPATH_LINK_OBJCXX_FLAG}) -endif() - -if(NOT DEFINED CMAKE_SHARED_LIBRARY_LINK_OBJCXX_WITH_RUNTIME_PATH) - set(CMAKE_SHARED_LIBRARY_LINK_OBJCXX_WITH_RUNTIME_PATH ${CMAKE_SHARED_LIBRARY_LINK_OBJC_WITH_RUNTIME_PATH}) -endif() - -if(NOT CMAKE_INCLUDE_FLAG_OBJCXX) - set(CMAKE_INCLUDE_FLAG_OBJCXX ${CMAKE_INCLUDE_FLAG_C}) -endif() - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_OBJCXX_FLAGS ${CMAKE_SHARED_LIBRARY_OBJCXX_FLAGS}) - set(CMAKE_SHARED_MODULE_CREATE_OBJCXX_FLAGS ${CMAKE_SHARED_LIBRARY_CREATE_OBJCXX_FLAGS}) -endif() - -# repeat for modules -if(NOT CMAKE_SHARED_MODULE_CREATE_OBJCXX_FLAGS) - set(CMAKE_SHARED_MODULE_CREATE_OBJCXX_FLAGS ${CMAKE_SHARED_MODULE_CREATE_OBJC_FLAGS}) -endif() - -if(NOT CMAKE_SHARED_MODULE_OBJCXX_FLAGS) - set(CMAKE_SHARED_MODULE_OBJCXX_FLAGS ${CMAKE_SHARED_MODULE_OBJC_FLAGS}) -endif() - -# Initialize OBJCXX link type selection flags from OBJC versions. -foreach(type SHARED_LIBRARY SHARED_MODULE EXE) - if(NOT CMAKE_${type}_LINK_STATIC_OBJCXX_FLAGS) - set(CMAKE_${type}_LINK_STATIC_OBJCXX_FLAGS - ${CMAKE_${type}_LINK_STATIC_OBJC_FLAGS}) - endif() - if(NOT CMAKE_${type}_LINK_DYNAMIC_OBJCXX_FLAGS) - set(CMAKE_${type}_LINK_DYNAMIC_OBJCXX_FLAGS - ${CMAKE_${type}_LINK_DYNAMIC_OBJC_FLAGS}) - endif() -endforeach() - -# add the flags to the cache based -# on the initial values computed in the platform/*.cmake files -# use _INIT variables so that this only happens the first time -# and you can set these flags in the cmake cache -set(CMAKE_OBJCXX_FLAGS_INIT "$ENV{OBJCXXFLAGS} ${CMAKE_OBJCXX_FLAGS_INIT}") - -cmake_initialize_per_config_variable(CMAKE_OBJCXX_FLAGS "Flags used by the Objective-C++ compiler") - -if(CMAKE_OBJCXX_STANDARD_LIBRARIES_INIT) - set(CMAKE_OBJCXX_STANDARD_LIBRARIES "${CMAKE_OBJCXX_STANDARD_LIBRARIES_INIT}" - CACHE STRING "Libraries linked by default with all Objective-C++ applications.") - mark_as_advanced(CMAKE_OBJCXX_STANDARD_LIBRARIES) -endif() - -if(NOT CMAKE_OBJCXX_COMPILER_LAUNCHER AND DEFINED ENV{CMAKE_OBJCXX_COMPILER_LAUNCHER}) - set(CMAKE_OBJCXX_COMPILER_LAUNCHER "$ENV{CMAKE_OBJCXX_COMPILER_LAUNCHER}" - CACHE STRING "Compiler launcher for OBJCXX.") -endif() - -include(CMakeCommonLanguageInclude) - -# now define the following rules: -# CMAKE_OBJCXX_CREATE_SHARED_LIBRARY -# CMAKE_OBJCXX_CREATE_SHARED_MODULE -# CMAKE_OBJCXX_COMPILE_OBJECT -# CMAKE_OBJCXX_LINK_EXECUTABLE - -# variables supplied by the generator at use time -# <TARGET> -# <TARGET_BASE> the target without the suffix -# <OBJECTS> -# <OBJECT> -# <LINK_LIBRARIES> -# <FLAGS> -# <LINK_FLAGS> - -# Objective-C++ compiler information -# <CMAKE_OBJCXX_COMPILER> -# <CMAKE_SHARED_LIBRARY_CREATE_OBJCXX_FLAGS> -# <CMAKE_OBJCXX_SHARED_MODULE_CREATE_FLAGS> -# <CMAKE_OBJCXX_LINK_FLAGS> - -# Static library tools -# <CMAKE_AR> -# <CMAKE_RANLIB> - - -# create a shared Objective-C++ library -if(NOT CMAKE_OBJCXX_CREATE_SHARED_LIBRARY) - set(CMAKE_OBJCXX_CREATE_SHARED_LIBRARY - "<CMAKE_OBJCXX_COMPILER> <CMAKE_SHARED_LIBRARY_OBJCXX_FLAGS> <LANGUAGE_COMPILE_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_OBJCXX_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>") -endif() - -# create an Objective-C++ shared module copy the shared library rule by default -if(NOT CMAKE_OBJCXX_CREATE_SHARED_MODULE) - set(CMAKE_OBJCXX_CREATE_SHARED_MODULE ${CMAKE_OBJCXX_CREATE_SHARED_LIBRARY}) -endif() - - -# Create a static archive incrementally for large object file counts. -# If CMAKE_OBJCXX_CREATE_STATIC_LIBRARY is set it will override these. -if(NOT DEFINED CMAKE_OBJCXX_ARCHIVE_CREATE) - set(CMAKE_OBJCXX_ARCHIVE_CREATE "<CMAKE_AR> qc <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_OBJCXX_ARCHIVE_APPEND) - set(CMAKE_OBJCXX_ARCHIVE_APPEND "<CMAKE_AR> q <TARGET> <LINK_FLAGS> <OBJECTS>") -endif() -if(NOT DEFINED CMAKE_OBJCXX_ARCHIVE_FINISH) - set(CMAKE_OBJCXX_ARCHIVE_FINISH "<CMAKE_RANLIB> <TARGET>") -endif() - -# compile an Objective-C++ file into an object file -if(NOT CMAKE_OBJCXX_COMPILE_OBJECT) - set(CMAKE_OBJCXX_COMPILE_OBJECT - "<CMAKE_OBJCXX_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -x objective-c++ -o <OBJECT> -c <SOURCE>") -endif() - -if(NOT CMAKE_OBJCXX_LINK_EXECUTABLE) - set(CMAKE_OBJCXX_LINK_EXECUTABLE - "<CMAKE_OBJCXX_COMPILER> <FLAGS> <CMAKE_OBJCXX_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") -endif() - -mark_as_advanced( -CMAKE_VERBOSE_MAKEFILE -) - -set(CMAKE_OBJCXX_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakePackageConfigHelpers.cmake b/share/cmake-3.18/Modules/CMakePackageConfigHelpers.cmake deleted file mode 100644 index 22fc953..0000000 --- a/share/cmake-3.18/Modules/CMakePackageConfigHelpers.cmake +++ /dev/null
@@ -1,332 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CMakePackageConfigHelpers -------------------------- - -Helpers functions for creating config files that can be included by other -projects to find and use a package. - -Adds the :command:`configure_package_config_file()` and -:command:`write_basic_package_version_file()` commands. - -Generating a Package Configuration File -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. command:: configure_package_config_file - - Create a config file for a project:: - - configure_package_config_file(<input> <output> - INSTALL_DESTINATION <path> - [PATH_VARS <var1> <var2> ... <varN>] - [NO_SET_AND_CHECK_MACRO] - [NO_CHECK_REQUIRED_COMPONENTS_MACRO] - [INSTALL_PREFIX <path>] - ) - -``configure_package_config_file()`` should be used instead of the plain -:command:`configure_file()` command when creating the ``<PackageName>Config.cmake`` -or ``<PackageName>-config.cmake`` file for installing a project or library. -It helps making the resulting package relocatable by avoiding hardcoded paths -in the installed ``Config.cmake`` file. - -In a ``FooConfig.cmake`` file there may be code like this to make the install -destinations know to the using project: - -.. code-block:: cmake - - set(FOO_INCLUDE_DIR "@CMAKE_INSTALL_FULL_INCLUDEDIR@" ) - set(FOO_DATA_DIR "@CMAKE_INSTALL_PREFIX@/@RELATIVE_DATA_INSTALL_DIR@" ) - set(FOO_ICONS_DIR "@CMAKE_INSTALL_PREFIX@/share/icons" ) - #...logic to determine installedPrefix from the own location... - set(FOO_CONFIG_DIR "${installedPrefix}/@CONFIG_INSTALL_DIR@" ) - -All 4 options shown above are not sufficient, since the first 3 hardcode the -absolute directory locations, and the 4th case works only if the logic to -determine the ``installedPrefix`` is correct, and if ``CONFIG_INSTALL_DIR`` -contains a relative path, which in general cannot be guaranteed. This has the -effect that the resulting ``FooConfig.cmake`` file would work poorly under -Windows and OSX, where users are used to choose the install location of a -binary package at install time, independent from how -:variable:`CMAKE_INSTALL_PREFIX` was set at build/cmake time. - -Using ``configure_package_config_file`` helps. If used correctly, it makes -the resulting ``FooConfig.cmake`` file relocatable. Usage: - -1. write a ``FooConfig.cmake.in`` file as you are used to -2. insert a line containing only the string ``@PACKAGE_INIT@`` -3. instead of ``set(FOO_DIR "@SOME_INSTALL_DIR@")``, use - ``set(FOO_DIR "@PACKAGE_SOME_INSTALL_DIR@")`` (this must be after the - ``@PACKAGE_INIT@`` line) -4. instead of using the normal :command:`configure_file()`, use - ``configure_package_config_file()`` - - - -The ``<input>`` and ``<output>`` arguments are the input and output file, the -same way as in :command:`configure_file()`. - -The ``<path>`` given to ``INSTALL_DESTINATION`` must be the destination where -the ``FooConfig.cmake`` file will be installed to. This path can either be -absolute, or relative to the ``INSTALL_PREFIX`` path. - -The variables ``<var1>`` to ``<varN>`` given as ``PATH_VARS`` are the -variables which contain install destinations. For each of them the macro will -create a helper variable ``PACKAGE_<var...>``. These helper variables must be -used in the ``FooConfig.cmake.in`` file for setting the installed location. -They are calculated by ``configure_package_config_file`` so that they are -always relative to the installed location of the package. This works both for -relative and also for absolute locations. For absolute locations it works -only if the absolute location is a subdirectory of ``INSTALL_PREFIX``. - -If the ``INSTALL_PREFIX`` argument is passed, this is used as base path to -calculate all the relative paths. The ``<path>`` argument must be an absolute -path. If this argument is not passed, the :variable:`CMAKE_INSTALL_PREFIX` -variable will be used instead. The default value is good when generating a -FooConfig.cmake file to use your package from the install tree. When -generating a FooConfig.cmake file to use your package from the build tree this -option should be used. - -By default ``configure_package_config_file`` also generates two helper macros, -``set_and_check()`` and ``check_required_components()`` into the -``FooConfig.cmake`` file. - -``set_and_check()`` should be used instead of the normal ``set()`` command for -setting directories and file locations. Additionally to setting the variable -it also checks that the referenced file or directory actually exists and fails -with a ``FATAL_ERROR`` otherwise. This makes sure that the created -``FooConfig.cmake`` file does not contain wrong references. -When using the ``NO_SET_AND_CHECK_MACRO``, this macro is not generated -into the ``FooConfig.cmake`` file. - -``check_required_components(<PackageName>)`` should be called at the end of -the ``FooConfig.cmake`` file. This macro checks whether all requested, -non-optional components have been found, and if this is not the case, sets -the ``Foo_FOUND`` variable to ``FALSE``, so that the package is considered to -be not found. It does that by testing the ``Foo_<Component>_FOUND`` -variables for all requested required components. This macro should be -called even if the package doesn't provide any components to make sure -users are not specifying components erroneously. When using the -``NO_CHECK_REQUIRED_COMPONENTS_MACRO`` option, this macro is not generated -into the ``FooConfig.cmake`` file. - -For an example see below the documentation for -:command:`write_basic_package_version_file()`. - -Generating a Package Version File -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. command:: write_basic_package_version_file - - Create a version file for a project:: - - write_basic_package_version_file(<filename> - [VERSION <major.minor.patch>] - COMPATIBILITY <AnyNewerVersion|SameMajorVersion|SameMinorVersion|ExactVersion> - [ARCH_INDEPENDENT] ) - - -Writes a file for use as ``<PackageName>ConfigVersion.cmake`` file to -``<filename>``. See the documentation of :command:`find_package()` for -details on this. - -``<filename>`` is the output filename, it should be in the build tree. -``<major.minor.patch>`` is the version number of the project to be installed. - -If no ``VERSION`` is given, the :variable:`PROJECT_VERSION` variable is used. -If this hasn't been set, it errors out. - -The ``COMPATIBILITY`` mode ``AnyNewerVersion`` means that the installed -package version will be considered compatible if it is newer or exactly the -same as the requested version. This mode should be used for packages which -are fully backward compatible, also across major versions. -If ``SameMajorVersion`` is used instead, then the behaviour differs from -``AnyNewerVersion`` in that the major version number must be the same as -requested, e.g. version 2.0 will not be considered compatible if 1.0 is -requested. This mode should be used for packages which guarantee backward -compatibility within the same major version. -If ``SameMinorVersion`` is used, the behaviour is the same as -``SameMajorVersion``, but both major and minor version must be the same as -requested, e.g version 0.2 will not be compatible if 0.1 is requested. -If ``ExactVersion`` is used, then the package is only considered compatible if -the requested version matches exactly its own version number (not considering -the tweak version). For example, version 1.2.3 of a package is only -considered compatible to requested version 1.2.3. This mode is for packages -without compatibility guarantees. -If your project has more elaborated version matching rules, you will need to -write your own custom ``ConfigVersion.cmake`` file instead of using this -macro. - -If ``ARCH_INDEPENDENT`` is given, the installed package version will be -considered compatible even if it was built for a different architecture than -the requested architecture. Otherwise, an architecture check will be performed, -and the package will be considered compatible only if the architecture matches -exactly. For example, if the package is built for a 32-bit architecture, the -package is only considered compatible if it is used on a 32-bit architecture, -unless ``ARCH_INDEPENDENT`` is given, in which case the package is considered -compatible on any architecture. - -.. note:: ``ARCH_INDEPENDENT`` is intended for header-only libraries or similar - packages with no binaries. - -Internally, this macro executes :command:`configure_file()` to create the -resulting version file. Depending on the ``COMPATIBILITY``, the corresponding -``BasicConfigVersion-<COMPATIBILITY>.cmake.in`` file is used. -Please note that these files are internal to CMake and you should not call -:command:`configure_file()` on them yourself, but they can be used as starting -point to create more sophisticted custom ``ConfigVersion.cmake`` files. - -Example Generating Package Files -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Example using both :command:`configure_package_config_file` and -``write_basic_package_version_file()``: - -``CMakeLists.txt``: - -.. code-block:: cmake - - set(INCLUDE_INSTALL_DIR include/ ... CACHE ) - set(LIB_INSTALL_DIR lib/ ... CACHE ) - set(SYSCONFIG_INSTALL_DIR etc/foo/ ... CACHE ) - #... - include(CMakePackageConfigHelpers) - configure_package_config_file(FooConfig.cmake.in - ${CMAKE_CURRENT_BINARY_DIR}/FooConfig.cmake - INSTALL_DESTINATION ${LIB_INSTALL_DIR}/Foo/cmake - PATH_VARS INCLUDE_INSTALL_DIR SYSCONFIG_INSTALL_DIR) - write_basic_package_version_file( - ${CMAKE_CURRENT_BINARY_DIR}/FooConfigVersion.cmake - VERSION 1.2.3 - COMPATIBILITY SameMajorVersion ) - install(FILES ${CMAKE_CURRENT_BINARY_DIR}/FooConfig.cmake - ${CMAKE_CURRENT_BINARY_DIR}/FooConfigVersion.cmake - DESTINATION ${LIB_INSTALL_DIR}/Foo/cmake ) - -``FooConfig.cmake.in``: - -:: - - set(FOO_VERSION x.y.z) - ... - @PACKAGE_INIT@ - ... - set_and_check(FOO_INCLUDE_DIR "@PACKAGE_INCLUDE_INSTALL_DIR@") - set_and_check(FOO_SYSCONFIG_DIR "@PACKAGE_SYSCONFIG_INSTALL_DIR@") - - check_required_components(Foo) -#]=======================================================================] - -include(WriteBasicConfigVersionFile) - -macro(WRITE_BASIC_PACKAGE_VERSION_FILE) - write_basic_config_version_file(${ARGN}) -endmacro() - -function(CONFIGURE_PACKAGE_CONFIG_FILE _inputFile _outputFile) - set(options NO_SET_AND_CHECK_MACRO NO_CHECK_REQUIRED_COMPONENTS_MACRO) - set(oneValueArgs INSTALL_DESTINATION INSTALL_PREFIX) - set(multiValueArgs PATH_VARS ) - - cmake_parse_arguments(CCF "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN}) - - if(CCF_UNPARSED_ARGUMENTS) - message(FATAL_ERROR "Unknown keywords given to CONFIGURE_PACKAGE_CONFIG_FILE(): \"${CCF_UNPARSED_ARGUMENTS}\"") - endif() - - if(NOT CCF_INSTALL_DESTINATION) - message(FATAL_ERROR "No INSTALL_DESTINATION given to CONFIGURE_PACKAGE_CONFIG_FILE()") - endif() - - if(DEFINED CCF_INSTALL_PREFIX) - if(IS_ABSOLUTE "${CCF_INSTALL_PREFIX}") - set(installPrefix "${CCF_INSTALL_PREFIX}") - else() - message(FATAL_ERROR "INSTALL_PREFIX must be an absolute path") - endif() - elseif(IS_ABSOLUTE "${CMAKE_INSTALL_PREFIX}") - set(installPrefix "${CMAKE_INSTALL_PREFIX}") - else() - get_filename_component(installPrefix "${CMAKE_INSTALL_PREFIX}" ABSOLUTE) - endif() - - if(IS_ABSOLUTE "${CCF_INSTALL_DESTINATION}") - set(absInstallDir "${CCF_INSTALL_DESTINATION}") - else() - set(absInstallDir "${installPrefix}/${CCF_INSTALL_DESTINATION}") - endif() - - file(RELATIVE_PATH PACKAGE_RELATIVE_PATH "${absInstallDir}" "${installPrefix}" ) - - foreach(var ${CCF_PATH_VARS}) - if(NOT DEFINED ${var}) - message(FATAL_ERROR "Variable ${var} does not exist") - else() - if(IS_ABSOLUTE "${${var}}") - string(REPLACE "${installPrefix}" "\${PACKAGE_PREFIX_DIR}" - PACKAGE_${var} "${${var}}") - else() - set(PACKAGE_${var} "\${PACKAGE_PREFIX_DIR}/${${var}}") - endif() - endif() - endforeach() - - get_filename_component(inputFileName "${_inputFile}" NAME) - - set(PACKAGE_INIT " -####### Expanded from @PACKAGE_INIT@ by configure_package_config_file() ####### -####### Any changes to this file will be overwritten by the next CMake run #### -####### The input file was ${inputFileName} ######## - -get_filename_component(PACKAGE_PREFIX_DIR \"\${CMAKE_CURRENT_LIST_DIR}/${PACKAGE_RELATIVE_PATH}\" ABSOLUTE) -") - - if("${absInstallDir}" MATCHES "^(/usr)?/lib(64)?/.+") - # Handle "/usr move" symlinks created by some Linux distros. - string(APPEND PACKAGE_INIT " -# Use original install prefix when loaded through a \"/usr move\" -# cross-prefix symbolic link such as /lib -> /usr/lib. -get_filename_component(_realCurr \"\${CMAKE_CURRENT_LIST_DIR}\" REALPATH) -get_filename_component(_realOrig \"${absInstallDir}\" REALPATH) -if(_realCurr STREQUAL _realOrig) - set(PACKAGE_PREFIX_DIR \"${installPrefix}\") -endif() -unset(_realOrig) -unset(_realCurr) -") - endif() - - if(NOT CCF_NO_SET_AND_CHECK_MACRO) - string(APPEND PACKAGE_INIT " -macro(set_and_check _var _file) - set(\${_var} \"\${_file}\") - if(NOT EXISTS \"\${_file}\") - message(FATAL_ERROR \"File or directory \${_file} referenced by variable \${_var} does not exist !\") - endif() -endmacro() -") - endif() - - - if(NOT CCF_NO_CHECK_REQUIRED_COMPONENTS_MACRO) - string(APPEND PACKAGE_INIT " -macro(check_required_components _NAME) - foreach(comp \${\${_NAME}_FIND_COMPONENTS}) - if(NOT \${_NAME}_\${comp}_FOUND) - if(\${_NAME}_FIND_REQUIRED_\${comp}) - set(\${_NAME}_FOUND FALSE) - endif() - endif() - endforeach() -endmacro() -") - endif() - - string(APPEND PACKAGE_INIT " -####################################################################################") - - configure_file("${_inputFile}" "${_outputFile}" @ONLY) - -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeParseImplicitIncludeInfo.cmake b/share/cmake-3.18/Modules/CMakeParseImplicitIncludeInfo.cmake deleted file mode 100644 index ff4c325..0000000 --- a/share/cmake-3.18/Modules/CMakeParseImplicitIncludeInfo.cmake +++ /dev/null
@@ -1,247 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -# This is used internally by CMake and should not be included by user code. - -# helper function that parses implicit include dirs from a single line -# for compilers that report them that way. on success we return the -# list of dirs in id_var and set state_var to the 'done' state. -function(cmake_parse_implicit_include_line line lang id_var log_var state_var) - # clear variables we append to (avoids possible polution from parent scopes) - unset(rv) - set(log "") - - # Cray compiler (from cray wrapper, via PrgEnv-cray) - if("${CMAKE_${lang}_COMPILER_ID}" STREQUAL "Cray" AND - "${line}" MATCHES "^/" AND "${line}" MATCHES "/ccfe |/ftnfe " AND - "${line}" MATCHES " -isystem| -I") - string(REGEX MATCHALL " (-I ?|-isystem )(\"[^\"]+\"|[^ \"]+)" incs "${line}") - foreach(inc IN LISTS incs) - string(REGEX REPLACE " (-I ?|-isystem )(\"[^\"]+\"|[^ \"]+)" "\\2" idir "${inc}") - list(APPEND rv "${idir}") - endforeach() - if(rv) - string(APPEND log " got implicit includes via cray ccfe parser!\n") - else() - string(APPEND log " warning: cray ccfe parse failed!\n") - endif() - endif() - - # PGI compiler - if("${CMAKE_${lang}_COMPILER_ID}" STREQUAL "PGI") - # pgc++ verbose output differs - if(("${lang}" STREQUAL "C" OR "${lang}" STREQUAL "Fortran") AND - "${line}" MATCHES "^/" AND - "${line}" MATCHES "/pgc |/pgf901 |/pgftnc " AND - "${line}" MATCHES " -cmdline ") - # cmdline has unparsed cmdline, remove it - string(REGEX REPLACE "-cmdline .*" "" line "${line}") - if("${line}" MATCHES " -nostdinc ") - set(rv "") # defined, but empty - else() - string(REGEX MATCHALL " -stdinc ([^ ]*)" incs "${line}") - foreach(inc IN LISTS incs) - string(REGEX REPLACE " -stdinc ([^ ]*)" "\\1" idir "${inc}") - string(REPLACE ":" ";" idir "${idir}") - list(APPEND rv ${idir}) - endforeach() - endif() - if(DEFINED rv) - string(APPEND log " got implicit includes via PGI C/F parser!\n") - else() - string(APPEND log " warning: PGI C/F parse failed!\n") - endif() - elseif("${lang}" STREQUAL "CXX" AND "${line}" MATCHES "^/" AND - "${line}" MATCHES "/pggpp1 " AND "${line}" MATCHES " -I") - # oddly, -Mnostdinc does not get rid of system -I's, at least in - # PGI 18.10.1 ... - string(REGEX MATCHALL " (-I ?)([^ ]*)" incs "${line}") - foreach(inc IN LISTS incs) - string(REGEX REPLACE " (-I ?)([^ ]*)" "\\2" idir "${inc}") - if(NOT "${idir}" STREQUAL "-") # filter out "-I-" - list(APPEND rv "${idir}") - endif() - endforeach() - if(DEFINED rv) - string(APPEND log " got implicit includes via PGI CXX parser!\n") - else() - string(APPEND log " warning: PGI CXX parse failed!\n") - endif() - endif() - endif() - - # SunPro compiler - if("${CMAKE_${lang}_COMPILER_ID}" STREQUAL "SunPro" AND - ("${line}" MATCHES "-D__SUNPRO_C" OR "${line}" MATCHES "-D__SUNPRO_F") ) - string(REGEX MATCHALL " (-I ?)([^ ]*)" incs "${line}") - foreach(inc IN LISTS incs) - string(REGEX REPLACE " (-I ?)([^ ]*)" "\\2" idir "${inc}") - if(NOT "${idir}" STREQUAL "-xbuiltin") - list(APPEND rv "${idir}") - endif() - endforeach() - if(rv) - if ("${lang}" STREQUAL "C" OR "${lang}" STREQUAL "CXX") - # /usr/include appears to be hardwired in - list(APPEND rv "/usr/include") - endif() - string(APPEND log " got implicit includes via sunpro parser!\n") - else() - string(APPEND log " warning: sunpro parse failed!\n") - endif() - endif() - - # XL compiler - if(("${CMAKE_${lang}_COMPILER_ID}" STREQUAL "XL" - OR "${CMAKE_${lang}_COMPILER_ID}" STREQUAL "XLClang") - AND "${line}" MATCHES "^/" - AND ( ("${lang}" STREQUAL "Fortran" AND - "${line}" MATCHES "/xl[fF]entry " AND - "${line}" MATCHES "OSVAR\\([^ ]+\\)") - OR - ( ("${lang}" STREQUAL "C" OR "${lang}" STREQUAL "CXX") AND - "${line}" MATCHES "/xl[cC]2?entry " AND - "${line}" MATCHES " -qosvar=") - ) ) - # -qnostdinc cancels other stdinc flags, even if present - string(FIND "${line}" " -qnostdinc" nostd) - if(NOT ${nostd} EQUAL -1) - set(rv "") # defined but empty - string(APPEND log " got implicit includes via XL parser (nostdinc)\n") - else() - if("${lang}" STREQUAL "CXX") - string(REGEX MATCHALL " -qcpp_stdinc=([^ ]*)" std "${line}") - string(REGEX MATCHALL " -qgcc_cpp_stdinc=([^ ]*)" gcc_std "${line}") - else() - string(REGEX MATCHALL " -qc_stdinc=([^ ]*)" std "${line}") - string(REGEX MATCHALL " -qgcc_c_stdinc=([^ ]*)" gcc_std "${line}") - endif() - set(xlstd ${std} ${gcc_std}) - foreach(inc IN LISTS xlstd) - string(REGEX REPLACE " -q(cpp|gcc_cpp|c|gcc_c)_stdinc=([^ ]*)" "\\2" - ipath "${inc}") - string(REPLACE ":" ";" ipath "${ipath}") - list(APPEND rv ${ipath}) - endforeach() - endif() - # user can add -I flags via CMAKE_{C,CXX}_FLAGS, look for that too - string(REGEX MATCHALL " (-I ?)([^ ]*)" incs "${line}") - unset(urv) - foreach(inc IN LISTS incs) - string(REGEX REPLACE " (-I ?)([^ ]*)" "\\2" idir "${inc}") - list(APPEND urv "${idir}") - endforeach() - if(urv) - if ("${rv}" STREQUAL "") - set(rv ${urv}) - else() - list(APPEND rv ${urv}) - endif() - endif() - - if(DEFINED rv) - string(APPEND log " got implicit includes via XL parser!\n") - else() - string(APPEND log " warning: XL parse failed!\n") - endif() - endif() - - if(log) - set(${log_var} "${log}" PARENT_SCOPE) - else() - unset(${log_var} PARENT_SCOPE) - endif() - if(DEFINED rv) - set(${id_var} "${rv}" PARENT_SCOPE) - set(${state_var} "done" PARENT_SCOPE) - endif() -endfunction() - -# top-level function to parse implicit include directory information -# from verbose compiler output. sets state_var in parent to 'done' on success. -function(cmake_parse_implicit_include_info text lang dir_var log_var state_var) - set(state start) # values: start, loading, done - - # clear variables we append to (avoids possible polution from parent scopes) - set(implicit_dirs_tmp) - set(log "") - - # go through each line of output... - string(REGEX REPLACE "\r*\n" ";" output_lines "${text}") - foreach(line IN LISTS output_lines) - if(state STREQUAL start) - string(FIND "${line}" "#include \"...\" search starts here:" rv) - if(rv GREATER -1) - set(state loading) - set(preload 1) # looking for include <...> now - string(APPEND log " found start of include info\n") - else() - cmake_parse_implicit_include_line("${line}" "${lang}" implicit_dirs_tmp - linelog state) - if(linelog) - string(APPEND log ${linelog}) - endif() - if(state STREQUAL done) - break() - endif() - endif() - elseif(state STREQUAL loading) - string(FIND "${line}" "End of search list." rv) - if(rv GREATER -1) - set(state done) - string(APPEND log " end of search list found\n") - break() - endif() - if(preload) - string(FIND "${line}" "#include <...> search starts here:" rv) - if(rv GREATER -1) - set(preload 0) - string(APPEND log " found start of implicit include info\n") - endif() - continue() - endif() - if("${line}" MATCHES "^ ") - string(SUBSTRING "${line}" 1 -1 line) # remove leading space - endif() - if ("${line}" MATCHES " \\(framework directory\\)$") - continue() # frameworks are handled elsewhere, ignore them here - endif() - string(REPLACE "\\" "/" path "${line}") - list(APPEND implicit_dirs_tmp "${path}") - string(APPEND log " add: [${path}]\n") - endif() - endforeach() - - set(implicit_dirs "") - foreach(d IN LISTS implicit_dirs_tmp) - if(IS_ABSOLUTE "${d}") - get_filename_component(dir "${d}" ABSOLUTE) - list(APPEND implicit_dirs "${dir}") - string(APPEND log " collapse include dir [${d}] ==> [${dir}]\n") - elseif("${d}" MATCHES [[^\.\.[\/]\.\.[\/](.*)$]]) - # This relative path is deep enough to get out of the CMakeFiles/CMakeTmp - # directory where the ABI check is done. Assume that the compiler has - # computed this path adaptively based on the current working directory - # such that the effective result is absolute. - get_filename_component(dir "${CMAKE_BINARY_DIR}/${CMAKE_MATCH_1}" ABSOLUTE) - list(APPEND implicit_dirs "${dir}") - string(APPEND log " collapse relative include dir [${d}] ==> [${dir}]\n") - else() - string(APPEND log " skipping relative include dir [${d}]\n") - endif() - endforeach() - list(REMOVE_DUPLICATES implicit_dirs) - - # Log results. - if(state STREQUAL done) - string(APPEND log " implicit include dirs: [${implicit_dirs}]\n") - else() - string(APPEND log " warn: unable to parse implicit include dirs!\n") - endif() - - # Return results. - set(${dir_var} "${implicit_dirs}" PARENT_SCOPE) - set(${log_var} "${log}" PARENT_SCOPE) - set(${state_var} "${state}" PARENT_SCOPE) - -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeParseImplicitLinkInfo.cmake b/share/cmake-3.18/Modules/CMakeParseImplicitLinkInfo.cmake deleted file mode 100644 index 0465515..0000000 --- a/share/cmake-3.18/Modules/CMakeParseImplicitLinkInfo.cmake +++ /dev/null
@@ -1,204 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -cmake_policy(PUSH) -cmake_policy(SET CMP0053 NEW) -cmake_policy(SET CMP0054 NEW) - -# Function parse implicit linker options. -# This is used internally by CMake and should not be included by user -# code. - -function(CMAKE_PARSE_IMPLICIT_LINK_INFO text lib_var dir_var fwk_var log_var obj_regex) - set(implicit_libs_tmp "") - set(implicit_dirs_tmp) - set(implicit_fwks_tmp) - set(log "") - - # Parse implicit linker arguments. - set(linker "CMAKE_LINKER-NOTFOUND") - if(CMAKE_LINKER) - get_filename_component(linker ${CMAKE_LINKER} NAME) - string(REGEX REPLACE "([][+.*?()^$])" "\\\\\\1" linker "${linker}") - endif() - set(startfile "CMAKE_LINK_STARTFILE-NOTFOUND") - if(CMAKE_LINK_STARTFILE) - set(startfile "${CMAKE_LINK_STARTFILE}") - endif() - # Construct a regex to match linker lines. It must match both the - # whole line and just the command (argv[0]). - set(linker_regex "^( *|.*[/\\])(${linker}|${startfile}|([^/\\]+-)?ld|collect2)[^/\\]*( |$)") - set(linker_exclude_regex "collect2 version |^[A-Za-z0-9_]+=|/ldfe ") - string(APPEND log " link line regex: [${linker_regex}]\n") - string(REGEX REPLACE "\r?\n" ";" output_lines "${text}") - foreach(line IN LISTS output_lines) - set(cmd) - if("${line}" MATCHES "${linker_regex}" AND - NOT "${line}" MATCHES "${linker_exclude_regex}") - if(XCODE) - # Xcode unconditionally adds a path under the project build tree and - # on older versions it is not reported with proper quotes. Remove it. - string(REGEX REPLACE "([][+.*()^])" "\\\\\\1" _dir_regex "${CMAKE_BINARY_DIR}") - string(REGEX REPLACE " -[FL]${_dir_regex}/([^ ]| [^-])+( |$)" " " xline "${line}") - if(NOT "x${xline}" STREQUAL "x${line}") - string(APPEND log " reduced line: [${line}]\n to: [${xline}]\n") - set(line "${xline}") - endif() - endif() - separate_arguments(args NATIVE_COMMAND "${line}") - list(GET args 0 cmd) - else() - #check to see if the link line is comma-separated instead of space separated - string(REGEX REPLACE "," " " line "${line}") - if("${line}" MATCHES "${linker_regex}" AND - NOT "${line}" MATCHES "${linker_exclude_regex}") - separate_arguments(args NATIVE_COMMAND "${line}") - list(GET args 0 cmd) - if("${cmd}" MATCHES "exec:") - # ibm xl sometimes has 'exec: ' in-front of the linker - list(GET args 1 cmd) - endif() - endif() - endif() - set(is_msvc 0) - if("${cmd}" MATCHES "${linker_regex}") - string(APPEND log " link line: [${line}]\n") - string(REGEX REPLACE ";-([LYz]);" ";-\\1" args "${args}") - set(skip_value_of "") - foreach(arg IN LISTS args) - if(skip_value_of) - string(APPEND log " arg [${arg}] ==> skip value of ${skip_value_of}\n") - set(skip_value_of "") - elseif("${arg}" MATCHES "^-L(.:)?[/\\]") - # Unix search path. - string(REGEX REPLACE "^-L" "" dir "${arg}") - list(APPEND implicit_dirs_tmp ${dir}) - string(APPEND log " arg [${arg}] ==> dir [${dir}]\n") - elseif("${arg}" MATCHES "^[-/](LIBPATH|libpath):(.+)") - # MSVC search path. - set(dir "${CMAKE_MATCH_2}") - list(APPEND implicit_dirs_tmp ${dir}) - string(APPEND log " arg [${arg}] ==> dir [${dir}]\n") - elseif(is_msvc AND "${arg}" STREQUAL "-link") - string(APPEND log " arg [${arg}] ==> ignore MSVC cl option\n") - elseif(is_msvc AND "${arg}" MATCHES "^(.*\\.[Ll][Ii][Bb])$") - set(lib "${CMAKE_MATCH_1}") - list(APPEND implicit_libs_tmp ${lib}) - string(APPEND log " arg [${arg}] ==> lib [${lib}]\n") - elseif("${arg}" STREQUAL "-lto_library") - # ld argument "-lto_library <path>" - set(skip_value_of "${arg}") - string(APPEND log " arg [${arg}] ==> ignore, skip following value\n") - elseif("${arg}" MATCHES "^-l([^:].*)$") - # Unix library. - set(lib "${CMAKE_MATCH_1}") - list(APPEND implicit_libs_tmp ${lib}) - string(APPEND log " arg [${arg}] ==> lib [${lib}]\n") - elseif("${arg}" MATCHES "^(.:)?[/\\].*\\.a$") - # Unix library full path. - list(APPEND implicit_libs_tmp ${arg}) - string(APPEND log " arg [${arg}] ==> lib [${arg}]\n") - elseif("${arg}" MATCHES "^[-/](DEFAULTLIB|defaultlib):(.+)") - # Windows library. - set(lib "${CMAKE_MATCH_2}") - list(APPEND implicit_libs_tmp ${lib}) - string(APPEND log " arg [${arg}] ==> lib [${lib}]\n") - elseif("${arg}" MATCHES "^(.:)?[/\\].*\\.o$" - AND obj_regex AND "${arg}" MATCHES "${obj_regex}") - # Object file full path. - list(APPEND implicit_libs_tmp ${arg}) - string(APPEND log " arg [${arg}] ==> obj [${arg}]\n") - elseif("${arg}" MATCHES "^-Y(P,)?[^0-9]") - # Sun search path ([^0-9] avoids conflict with Mac -Y<num>). - string(REGEX REPLACE "^-Y(P,)?" "" dirs "${arg}") - string(REPLACE ":" ";" dirs "${dirs}") - list(APPEND implicit_dirs_tmp ${dirs}) - string(APPEND log " arg [${arg}] ==> dirs [${dirs}]\n") - elseif("${arg}" MATCHES "^-l:") - # HP named library. - list(APPEND implicit_libs_tmp ${arg}) - string(APPEND log " arg [${arg}] ==> lib [${arg}]\n") - elseif("${arg}" MATCHES "^-z(all|default|weak)extract") - # Link editor option. - list(APPEND implicit_libs_tmp ${arg}) - string(APPEND log " arg [${arg}] ==> opt [${arg}]\n") - elseif("${arg}" STREQUAL "cl.exe") - string(APPEND log " arg [${arg}] ==> recognize MSVC cl\n") - set(is_msvc 1) - else() - string(APPEND log " arg [${arg}] ==> ignore\n") - endif() - endforeach() - break() - elseif("${line}" MATCHES "LPATH(=| is:? *)(.*)$") - string(APPEND log " LPATH line: [${line}]\n") - # HP search path. - string(REPLACE ":" ";" paths "${CMAKE_MATCH_2}") - list(APPEND implicit_dirs_tmp ${paths}) - string(APPEND log " dirs [${paths}]\n") - else() - string(APPEND log " ignore line: [${line}]\n") - endif() - endforeach() - - # Look for library search paths reported by linker. - if("${output_lines}" MATCHES ";Library search paths:((;\t[^;]+)+)") - string(REPLACE ";\t" ";" implicit_dirs_match "${CMAKE_MATCH_1}") - string(APPEND log " Library search paths: [${implicit_dirs_match}]\n") - list(APPEND implicit_dirs_tmp ${implicit_dirs_match}) - endif() - if("${output_lines}" MATCHES ";Framework search paths:((;\t[^;]+)+)") - string(REPLACE ";\t" ";" implicit_fwks_match "${CMAKE_MATCH_1}") - string(APPEND log " Framework search paths: [${implicit_fwks_match}]\n") - list(APPEND implicit_fwks_tmp ${implicit_fwks_match}) - endif() - - # Cleanup list of libraries and flags. - # We remove items that are not language-specific. - set(implicit_libs "") - foreach(lib IN LISTS implicit_libs_tmp) - if("x${lib}" MATCHES "^x(crt.*\\.o|gcc_eh.*|.*libgcc_eh.*|System.*|.*libclang_rt.*|msvcrt.*|libvcruntime.*|libucrt.*|libcmt.*)$") - string(APPEND log " remove lib [${lib}]\n") - elseif(IS_ABSOLUTE "${lib}") - get_filename_component(abs "${lib}" ABSOLUTE) - if(NOT "x${lib}" STREQUAL "x${abs}") - string(APPEND log " collapse lib [${lib}] ==> [${abs}]\n") - endif() - list(APPEND implicit_libs "${abs}") - else() - list(APPEND implicit_libs "${lib}") - endif() - endforeach() - - # Cleanup list of library and framework directories. - set(desc_dirs "library") - set(desc_fwks "framework") - foreach(t dirs fwks) - set(implicit_${t} "") - foreach(d IN LISTS implicit_${t}_tmp) - get_filename_component(dir "${d}" ABSOLUTE) - string(FIND "${dir}" "${CMAKE_FILES_DIRECTORY}/" pos) - if(NOT pos LESS 0) - set(msg ", skipping non-system directory") - else() - set(msg "") - list(APPEND implicit_${t} "${dir}") - endif() - string(APPEND log " collapse ${desc_${t}} dir [${d}] ==> [${dir}]${msg}\n") - endforeach() - list(REMOVE_DUPLICATES implicit_${t}) - endforeach() - - # Log results. - string(APPEND log " implicit libs: [${implicit_libs}]\n") - string(APPEND log " implicit dirs: [${implicit_dirs}]\n") - string(APPEND log " implicit fwks: [${implicit_fwks}]\n") - - # Return results. - set(${lib_var} "${implicit_libs}" PARENT_SCOPE) - set(${dir_var} "${implicit_dirs}" PARENT_SCOPE) - set(${fwk_var} "${implicit_fwks}" PARENT_SCOPE) - set(${log_var} "${log}" PARENT_SCOPE) -endfunction() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CMakePlatformId.h.in b/share/cmake-3.18/Modules/CMakePlatformId.h.in deleted file mode 100644 index 40668a3..0000000 --- a/share/cmake-3.18/Modules/CMakePlatformId.h.in +++ /dev/null
@@ -1,286 +0,0 @@ -#define STRINGIFY_HELPER(X) #X -#define STRINGIFY(X) STRINGIFY_HELPER(X) - -/* Identify known platforms by name. */ -#if defined(__linux) || defined(__linux__) || defined(linux) -# define PLATFORM_ID "Linux" - -#elif defined(__CYGWIN__) -# define PLATFORM_ID "Cygwin" - -#elif defined(__MINGW32__) -# define PLATFORM_ID "MinGW" - -#elif defined(__APPLE__) -# define PLATFORM_ID "Darwin" - -#elif defined(_WIN32) || defined(__WIN32__) || defined(WIN32) -# define PLATFORM_ID "Windows" - -#elif defined(__FreeBSD__) || defined(__FreeBSD) -# define PLATFORM_ID "FreeBSD" - -#elif defined(__NetBSD__) || defined(__NetBSD) -# define PLATFORM_ID "NetBSD" - -#elif defined(__OpenBSD__) || defined(__OPENBSD) -# define PLATFORM_ID "OpenBSD" - -#elif defined(__sun) || defined(sun) -# define PLATFORM_ID "SunOS" - -#elif defined(_AIX) || defined(__AIX) || defined(__AIX__) || defined(__aix) || defined(__aix__) -# define PLATFORM_ID "AIX" - -#elif defined(__hpux) || defined(__hpux__) -# define PLATFORM_ID "HP-UX" - -#elif defined(__HAIKU__) -# define PLATFORM_ID "Haiku" - -#elif defined(__BeOS) || defined(__BEOS__) || defined(_BEOS) -# define PLATFORM_ID "BeOS" - -#elif defined(__QNX__) || defined(__QNXNTO__) -# define PLATFORM_ID "QNX" - -#elif defined(__tru64) || defined(_tru64) || defined(__TRU64__) -# define PLATFORM_ID "Tru64" - -#elif defined(__riscos) || defined(__riscos__) -# define PLATFORM_ID "RISCos" - -#elif defined(__sinix) || defined(__sinix__) || defined(__SINIX__) -# define PLATFORM_ID "SINIX" - -#elif defined(__UNIX_SV__) -# define PLATFORM_ID "UNIX_SV" - -#elif defined(__bsdos__) -# define PLATFORM_ID "BSDOS" - -#elif defined(_MPRAS) || defined(MPRAS) -# define PLATFORM_ID "MP-RAS" - -#elif defined(__osf) || defined(__osf__) -# define PLATFORM_ID "OSF1" - -#elif defined(_SCO_SV) || defined(SCO_SV) || defined(sco_sv) -# define PLATFORM_ID "SCO_SV" - -#elif defined(__ultrix) || defined(__ultrix__) || defined(_ULTRIX) -# define PLATFORM_ID "ULTRIX" - -#elif defined(__XENIX__) || defined(_XENIX) || defined(XENIX) -# define PLATFORM_ID "Xenix" - -#elif defined(__WATCOMC__) -# if defined(__LINUX__) -# define PLATFORM_ID "Linux" - -# elif defined(__DOS__) -# define PLATFORM_ID "DOS" - -# elif defined(__OS2__) -# define PLATFORM_ID "OS2" - -# elif defined(__WINDOWS__) -# define PLATFORM_ID "Windows3x" - -# elif defined(__VXWORKS__) -# define PLATFORM_ID "VxWorks" - -# else /* unknown platform */ -# define PLATFORM_ID -# endif - -#elif defined(__INTEGRITY) -# if defined(INT_178B) -# define PLATFORM_ID "Integrity178" - -# else /* regular Integrity */ -# define PLATFORM_ID "Integrity" -# endif - -#else /* unknown platform */ -# define PLATFORM_ID - -#endif - -/* For windows compilers MSVC and Intel we can determine - the architecture of the compiler being used. This is because - the compilers do not have flags that can change the architecture, - but rather depend on which compiler is being used -*/ -#if defined(_WIN32) && defined(_MSC_VER) -# if defined(_M_IA64) -# define ARCHITECTURE_ID "IA64" - -# elif defined(_M_X64) || defined(_M_AMD64) -# define ARCHITECTURE_ID "x64" - -# elif defined(_M_IX86) -# define ARCHITECTURE_ID "X86" - -# elif defined(_M_ARM64) -# define ARCHITECTURE_ID "ARM64" - -# elif defined(_M_ARM) -# if _M_ARM == 4 -# define ARCHITECTURE_ID "ARMV4I" -# elif _M_ARM == 5 -# define ARCHITECTURE_ID "ARMV5I" -# else -# define ARCHITECTURE_ID "ARMV" STRINGIFY(_M_ARM) -# endif - -# elif defined(_M_MIPS) -# define ARCHITECTURE_ID "MIPS" - -# elif defined(_M_SH) -# define ARCHITECTURE_ID "SHx" - -# else /* unknown architecture */ -# define ARCHITECTURE_ID "" -# endif - -#elif defined(__WATCOMC__) -# if defined(_M_I86) -# define ARCHITECTURE_ID "I86" - -# elif defined(_M_IX86) -# define ARCHITECTURE_ID "X86" - -# else /* unknown architecture */ -# define ARCHITECTURE_ID "" -# endif - -#elif defined(__IAR_SYSTEMS_ICC__) || defined(__IAR_SYSTEMS_ICC) -# if defined(__ICCARM__) -# define ARCHITECTURE_ID "ARM" - -# elif defined(__ICCRX__) -# define ARCHITECTURE_ID "RX" - -# elif defined(__ICCRH850__) -# define ARCHITECTURE_ID "RH850" - -# elif defined(__ICCRL78__) -# define ARCHITECTURE_ID "RL78" - -# elif defined(__ICCRISCV__) -# define ARCHITECTURE_ID "RISCV" - -# elif defined(__ICCAVR__) -# define ARCHITECTURE_ID "AVR" - -# elif defined(__ICC430__) -# define ARCHITECTURE_ID "MSP430" - -# elif defined(__ICCV850__) -# define ARCHITECTURE_ID "V850" - -# elif defined(__ICC8051__) -# define ARCHITECTURE_ID "8051" - -# else /* unknown architecture */ -# define ARCHITECTURE_ID "" -# endif - -#elif defined(__ghs__) -# if defined(__PPC64__) -# define ARCHITECTURE_ID "PPC64" - -# elif defined(__ppc__) -# define ARCHITECTURE_ID "PPC" - -# elif defined(__ARM__) -# define ARCHITECTURE_ID "ARM" - -# elif defined(__x86_64__) -# define ARCHITECTURE_ID "x64" - -# elif defined(__i386__) -# define ARCHITECTURE_ID "X86" - -# else /* unknown architecture */ -# define ARCHITECTURE_ID "" -# endif -#else -# define ARCHITECTURE_ID -#endif - -/* Convert integer to decimal digit literals. */ -#define DEC(n) \ - ('0' + (((n) / 10000000)%10)), \ - ('0' + (((n) / 1000000)%10)), \ - ('0' + (((n) / 100000)%10)), \ - ('0' + (((n) / 10000)%10)), \ - ('0' + (((n) / 1000)%10)), \ - ('0' + (((n) / 100)%10)), \ - ('0' + (((n) / 10)%10)), \ - ('0' + ((n) % 10)) - -/* Convert integer to hex digit literals. */ -#define HEX(n) \ - ('0' + ((n)>>28 & 0xF)), \ - ('0' + ((n)>>24 & 0xF)), \ - ('0' + ((n)>>20 & 0xF)), \ - ('0' + ((n)>>16 & 0xF)), \ - ('0' + ((n)>>12 & 0xF)), \ - ('0' + ((n)>>8 & 0xF)), \ - ('0' + ((n)>>4 & 0xF)), \ - ('0' + ((n) & 0xF)) - -/* Construct a string literal encoding the version number components. */ -#ifdef COMPILER_VERSION_MAJOR -char const info_version[] = { - 'I', 'N', 'F', 'O', ':', - 'c','o','m','p','i','l','e','r','_','v','e','r','s','i','o','n','[', - COMPILER_VERSION_MAJOR, -# ifdef COMPILER_VERSION_MINOR - '.', COMPILER_VERSION_MINOR, -# ifdef COMPILER_VERSION_PATCH - '.', COMPILER_VERSION_PATCH, -# ifdef COMPILER_VERSION_TWEAK - '.', COMPILER_VERSION_TWEAK, -# endif -# endif -# endif - ']','\0'}; -#endif - -/* Construct a string literal encoding the internal version number. */ -#ifdef COMPILER_VERSION_INTERNAL -char const info_version_internal[] = { - 'I', 'N', 'F', 'O', ':', - 'c','o','m','p','i','l','e','r','_','v','e','r','s','i','o','n','_', - 'i','n','t','e','r','n','a','l','[', - COMPILER_VERSION_INTERNAL,']','\0'}; -#endif - -/* Construct a string literal encoding the version number components. */ -#ifdef SIMULATE_VERSION_MAJOR -char const info_simulate_version[] = { - 'I', 'N', 'F', 'O', ':', - 's','i','m','u','l','a','t','e','_','v','e','r','s','i','o','n','[', - SIMULATE_VERSION_MAJOR, -# ifdef SIMULATE_VERSION_MINOR - '.', SIMULATE_VERSION_MINOR, -# ifdef SIMULATE_VERSION_PATCH - '.', SIMULATE_VERSION_PATCH, -# ifdef SIMULATE_VERSION_TWEAK - '.', SIMULATE_VERSION_TWEAK, -# endif -# endif -# endif - ']','\0'}; -#endif - -/* Construct the string literal in pieces to prevent the source from - getting matched. Store it in a pointer rather than an array - because some compilers will just produce instructions to fill the - array rather than assigning a pointer to a static array. */ -char const* info_platform = "INFO" ":" "platform[" PLATFORM_ID "]"; -char const* info_arch = "INFO" ":" "arch[" ARCHITECTURE_ID "]"; -
diff --git a/share/cmake-3.18/Modules/CMakePrintHelpers.cmake b/share/cmake-3.18/Modules/CMakePrintHelpers.cmake deleted file mode 100644 index d652ffa..0000000 --- a/share/cmake-3.18/Modules/CMakePrintHelpers.cmake +++ /dev/null
@@ -1,147 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CMakePrintHelpers ------------------ - -Convenience functions for printing properties and variables, useful -e.g. for debugging. - -:: - - cmake_print_properties([TARGETS target1 .. targetN] - [SOURCES source1 .. sourceN] - [DIRECTORIES dir1 .. dirN] - [TESTS test1 .. testN] - [CACHE_ENTRIES entry1 .. entryN] - PROPERTIES prop1 .. propN ) - -This function prints the values of the properties of the given targets, -source files, directories, tests or cache entries. Exactly one of the -scope keywords must be used. Example:: - - cmake_print_properties(TARGETS foo bar PROPERTIES - LOCATION INTERFACE_INCLUDE_DIRECTORIES) - -This will print the LOCATION and INTERFACE_INCLUDE_DIRECTORIES properties for -both targets foo and bar. - -:: - - cmake_print_variables(var1 var2 .. varN) - -This function will print the name of each variable followed by its value. -Example:: - - cmake_print_variables(CMAKE_C_COMPILER CMAKE_MAJOR_VERSION DOES_NOT_EXIST) - -Gives:: - - -- CMAKE_C_COMPILER="/usr/bin/gcc" ; CMAKE_MAJOR_VERSION="2" ; DOES_NOT_EXIST="" -#]=======================================================================] - -function(cmake_print_variables) - set(msg "") - foreach(var ${ARGN}) - if(msg) - string(APPEND msg " ; ") - endif() - string(APPEND msg "${var}=\"${${var}}\"") - endforeach() - message(STATUS "${msg}") -endfunction() - - -function(cmake_print_properties) - set(options ) - set(oneValueArgs ) - set(multiValueArgs TARGETS SOURCES TESTS DIRECTORIES CACHE_ENTRIES PROPERTIES ) - - cmake_parse_arguments(CPP "${options}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN}) - - if(CPP_UNPARSED_ARGUMENTS) - message(FATAL_ERROR "Unknown keywords given to cmake_print_properties(): \"${CPP_UNPARSED_ARGUMENTS}\"") - return() - endif() - - if(NOT CPP_PROPERTIES) - message(FATAL_ERROR "Required argument PROPERTIES missing in cmake_print_properties() call") - return() - endif() - - set(mode) - set(items) - set(keyword) - - if(CPP_TARGETS) - set(items ${CPP_TARGETS}) - set(mode ${mode} TARGETS) - set(keyword TARGET) - endif() - - if(CPP_SOURCES) - set(items ${CPP_SOURCES}) - set(mode ${mode} SOURCES) - set(keyword SOURCE) - endif() - - if(CPP_TESTS) - set(items ${CPP_TESTS}) - set(mode ${mode} TESTS) - set(keyword TEST) - endif() - - if(CPP_DIRECTORIES) - set(items ${CPP_DIRECTORIES}) - set(mode ${mode} DIRECTORIES) - set(keyword DIRECTORY) - endif() - - if(CPP_CACHE_ENTRIES) - set(items ${CPP_CACHE_ENTRIES}) - set(mode ${mode} CACHE_ENTRIES) - set(keyword CACHE) - endif() - - if(NOT mode) - message(FATAL_ERROR "Mode keyword missing in cmake_print_properties() call, must be one of TARGETS SOURCES TESTS DIRECTORIES CACHE_ENTRIES PROPERTIES") - return() - endif() - - list(LENGTH mode modeLength) - if("${modeLength}" GREATER 1) - message(FATAL_ERROR "Multiple mode keyword used in cmake_print_properties() call, it must be exactly one of TARGETS SOURCES TESTS DIRECTORIES CACHE_ENTRIES PROPERTIES") - return() - endif() - - set(msg "\n") - foreach(item ${items}) - - set(itemExists TRUE) - if(keyword STREQUAL "TARGET") - if(NOT TARGET ${item}) - set(itemExists FALSE) - string(APPEND msg "\n No such TARGET \"${item}\" !\n\n") - endif() - endif() - - if (itemExists) - string(APPEND msg " Properties for ${keyword} ${item}:\n") - foreach(prop ${CPP_PROPERTIES}) - - get_property(propertySet ${keyword} ${item} PROPERTY "${prop}" SET) - - if(propertySet) - get_property(property ${keyword} ${item} PROPERTY "${prop}") - string(APPEND msg " ${item}.${prop} = \"${property}\"\n") - else() - string(APPEND msg " ${item}.${prop} = <NOTFOUND>\n") - endif() - endforeach() - endif() - - endforeach() - message(STATUS "${msg}") - -endfunction()
diff --git a/share/cmake-3.18/Modules/CMakeSwiftInformation.cmake b/share/cmake-3.18/Modules/CMakeSwiftInformation.cmake deleted file mode 100644 index 8f0909c..0000000 --- a/share/cmake-3.18/Modules/CMakeSwiftInformation.cmake +++ /dev/null
@@ -1,103 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -if(UNIX) - set(CMAKE_Swift_OUTPUT_EXTENSION .o) -else() - set(CMAKE_Swift_OUTPUT_EXTENSION .obj) -endif() - -# Load compiler-specific information. -if(CMAKE_Swift_COMPILER_ID) - include(Compiler/${CMAKE_Swift_COMPILER_ID}-Swift OPTIONAL) - - if(CMAKE_SYSTEM_PROCESSOR) - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_Swift_COMPILER_ID}-Swift-${CMAKE_SYSTEM_PROCESSOR} OPTIONAL) - endif() - include(Platform/${CMAKE_EFFECTIVE_SYSTEM_NAME}-${CMAKE_Swift_COMPILER_ID}-Swift OPTIONAL) -endif() - -set(CMAKE_EXE_EXPORTS_Swift_FLAG "-emit-module -emit-module-path <SWIFT_MODULE> ${CMAKE_Swift_IMPLIB_LINKER_FLAGS}") - -set(CMAKE_INCLUDE_FLAG_Swift "-I ") -if(CMAKE_SYSTEM_NAME STREQUAL Darwin) - set(CMAKE_SHARED_LIBRARY_SONAME_Swift_FLAG "-Xlinker -install_name -Xlinker ") -elseif(NOT CMAKE_SYSTEM_NAME STREQUAL Windows) - set(CMAKE_SHARED_LIBRARY_SONAME_Swift_FLAG "-Xlinker -soname -Xlinker ") -endif() - -if(NOT CMAKE_SYSTEM_NAME STREQUAL Windows) - set(CMAKE_EXECUTABLE_RUNTIME_Swift_FLAG "-Xlinker -rpath -Xlinker ") - set(CMAKE_SHARED_LIBRARY_RUNTIME_Swift_FLAG "-Xlinker -rpath -Xlinker ") - if(CMAKE_SYSTEM_NAME STREQUAL Darwin) - set(CMAKE_EXECUTABLE_RUNTIME_Swift_FLAG_SEP "") - set(CMAKE_SHARED_LIBRARY_RUNTIME_Swift_FLAG_SEP "") - else() - set(CMAKE_EXECUTABLE_RUNTIME_Swift_FLAG_SEP ":") - set(CMAKE_SHARED_LIBRARY_RUNTIME_Swift_FLAG_SEP ":") - endif() -endif() - -set(CMAKE_Swift_COMPILE_OPTIONS_TARGET "-target ") -set(CMAKE_Swift_COMPILE_OPTIONS_EXTERNAL_TOOLCHAIN "-tools-directory ") -# NOTE(compnerd) the `-sdk` support is not yet ready in the compiler; when that -# is fully working, we should be able to enable this. -# set(CMAKE_Swift_COMPILE_OPTIONS_SYSROOT "-sdk ") -# NOTE(compnerd) do not setup `-frontend` as we use the compiler as the driver -# during the link phase and use that to drive the compilation -set(CMAKE_Swift_COMPILER_ARG1 "") -set(CMAKE_Swift_DEFINE_FLAG -D) -set(CMAKE_Swift_FRAMEWORK_SEARCH_FLAG "-F ") -set(CMAKE_Swift_LIBRARY_PATH_FLAG "-L ") -set(CMAKE_Swift_LIBRARY_PATH_TERMINATOR "") -set(CMAKE_Swift_LINK_LIBRARY_FLAG "-l") -set(CMAKE_Swift_LINKER_WRAPPER_FLAG "-Xlinker" " ") -set(CMAKE_Swift_RESPONSE_FILE_LINK_FLAG @) - -set(CMAKE_Swift_LINKER_PREFERENCE 50) -set(CMAKE_Swift_LINKER_PREFERENCE_PROPAGATES 1) - -# NOTE(compnerd) use the short form for convenience and ease of search. They -# are treated equivalent to their long form names as well as custom Swift -# specific names. -set(CMAKE_Swift_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreaded -libc MT) -set(CMAKE_Swift_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDLL -libc MD) -set(CMAKE_Swift_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDebug -libc MTd) -set(CMAKE_Swift_COMPILE_OPTIONS_MSVC_RUNTIME_LIBRARY_MultiThreadedDebugDLL -libc MDd) - -set(CMAKE_Swift_FLAGS_DEBUG_INIT "-g") -set(CMAKE_Swift_FLAGS_RELEASE_INIT "-O") -set(CMAKE_Swift_FLAGS_RELWITHDEBINFO_INIT "-O -g") -set(CMAKE_Swift_FLAGS_MINSIZEREL_INIT "-Osize") - -cmake_initialize_per_config_variable(CMAKE_Swift_FLAGS "Swift Compiler Flags") - -# NOTE(compnerd) we do not have an object compile rule since we build the objects as part of the link step -if(NOT CMAKE_Swift_COMPILE_OBJECT) - set(CMAKE_Swift_COMPILE_OBJECT ":") -endif() - -if(NOT CMAKE_Swift_NUM_THREADS MATCHES "^[0-9]+$") - cmake_host_system_information(RESULT CMAKE_Swift_NUM_THREADS QUERY NUMBER_OF_LOGICAL_CORES) -endif() - -if(NOT CMAKE_Swift_CREATE_SHARED_LIBRARY) - set(CMAKE_Swift_CREATE_SHARED_LIBRARY "<CMAKE_Swift_COMPILER> -output-file-map <SWIFT_OUTPUT_FILE_MAP> -incremental -j ${CMAKE_Swift_NUM_THREADS} -emit-library -o <TARGET> -module-name <SWIFT_MODULE_NAME> -module-link-name <SWIFT_LIBRARY_NAME> -emit-module -emit-module-path <SWIFT_MODULE> -emit-dependencies <DEFINES> <FLAGS> <INCLUDES> <SWIFT_SOURCES> <LINK_FLAGS> <SONAME_FLAG> <TARGET_INSTALLNAME_DIR><TARGET_SONAME> ${CMAKE_Swift_IMPLIB_LINKER_FLAGS} <LINK_LIBRARIES>") -endif() - -if(NOT CMAKE_Swift_CREATE_SHARED_MODULE) - set(CMAKE_Swift_CREATE_SHARED_MODULE ${CMAKE_Swift_CREATE_SHARED_LIBRARY}) -endif() - -if(NOT CMAKE_Swift_LINK_EXECUTABLE) - set(CMAKE_Swift_LINK_EXECUTABLE "<CMAKE_Swift_COMPILER> -output-file-map <SWIFT_OUTPUT_FILE_MAP> -incremental -j ${CMAKE_Swift_NUM_THREADS} -emit-executable -o <TARGET> -emit-dependencies <DEFINES> <FLAGS> <INCLUDES> <SWIFT_SOURCES> <LINK_FLAGS> <LINK_LIBRARIES>") -endif() - -if(NOT CMAKE_Swift_CREATE_STATIC_LIBRARY) - set(CMAKE_Swift_CREATE_STATIC_LIBRARY "<CMAKE_Swift_COMPILER> -output-file-map <SWIFT_OUTPUT_FILE_MAP> -incremental -j ${CMAKE_Swift_NUM_THREADS} -emit-library -static -o <TARGET> -module-name <SWIFT_MODULE_NAME> -module-link-name <SWIFT_LIBRARY_NAME> -emit-module -emit-module-path <SWIFT_MODULE> -emit-dependencies <DEFINES> <FLAGS> <INCLUDES> <SWIFT_SOURCES> <LINK_FLAGS> <LINK_LIBRARIES>") - - set(CMAKE_Swift_ARCHIVE_CREATE "<CMAKE_AR> crs <TARGET> <OBJECTS>") - set(CMAKE_Swift_ARCHIVE_FINISH "") -endif() - -set(CMAKE_Swift_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeSystemSpecificInformation.cmake b/share/cmake-3.18/Modules/CMakeSystemSpecificInformation.cmake deleted file mode 100644 index ea3a445..0000000 --- a/share/cmake-3.18/Modules/CMakeSystemSpecificInformation.cmake +++ /dev/null
@@ -1,58 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This file is included by cmGlobalGenerator::EnableLanguage. -# It is included after the compiler has been determined, so -# we know things like the compiler name and if the compiler is gnu. - -# before cmake 2.6 these variables were set in cmMakefile.cxx. This is still -# done to keep scripts and custom language and compiler modules working. -# But they are reset here and set again in the platform files for the target -# platform, so they can be used for testing the target platform instead -# of testing the host platform. -set(APPLE ) -set(UNIX ) -set(CYGWIN ) -set(WIN32 ) - - -# include Generic system information -include(CMakeGenericSystem) - -# 2. now include SystemName.cmake file to set the system specific information -set(CMAKE_SYSTEM_INFO_FILE Platform/${CMAKE_SYSTEM_NAME}) - -include(${CMAKE_SYSTEM_INFO_FILE} OPTIONAL RESULT_VARIABLE _INCLUDED_SYSTEM_INFO_FILE) - -if(NOT _INCLUDED_SYSTEM_INFO_FILE) - message("System is unknown to cmake, create:\n${CMAKE_SYSTEM_INFO_FILE}" - " to use this system, please post your config file on " - "discourse.cmake.org so it can be added to cmake") - if(EXISTS ${CMAKE_BINARY_DIR}/CMakeCache.txt) - configure_file(${CMAKE_BINARY_DIR}/CMakeCache.txt - ${CMAKE_BINARY_DIR}/CopyOfCMakeCache.txt COPYONLY) - message("Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. " - "Please post that file on discourse.cmake.org.") - endif() -endif() - -# optionally include a file which can do extra-generator specific things, e.g. -# CMakeFindEclipseCDT4.cmake asks gcc for the system include dirs for the Eclipse CDT4 generator -if(CMAKE_EXTRA_GENERATOR) - string(REPLACE " " "" _CMAKE_EXTRA_GENERATOR_NO_SPACES ${CMAKE_EXTRA_GENERATOR} ) - include("CMakeFind${_CMAKE_EXTRA_GENERATOR_NO_SPACES}" OPTIONAL) -endif() - - -# for most systems a module is the same as a shared library -# so unless the variable CMAKE_MODULE_EXISTS is set just -# copy the values from the LIBRARY variables -# this has to be done after the system information has been loaded -if(NOT CMAKE_MODULE_EXISTS) - set(CMAKE_SHARED_MODULE_PREFIX "${CMAKE_SHARED_LIBRARY_PREFIX}") - set(CMAKE_SHARED_MODULE_SUFFIX "${CMAKE_SHARED_LIBRARY_SUFFIX}") -endif() - - -set(CMAKE_SYSTEM_SPECIFIC_INFORMATION_LOADED 1)
diff --git a/share/cmake-3.18/Modules/CMakeTestCCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestCCompiler.cmake deleted file mode 100644 index 3734ec4..0000000 --- a/share/cmake-3.18/Modules/CMakeTestCCompiler.cmake +++ /dev/null
@@ -1,98 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(CMAKE_C_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_C_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# work around enforced code signing and / or missing exectuable target type -set(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE ${CMAKE_TRY_COMPILE_TARGET_TYPE}) -if(_CMAKE_FEATURE_DETECTION_TARGET_TYPE) - set(CMAKE_TRY_COMPILE_TARGET_TYPE ${_CMAKE_FEATURE_DETECTION_TARGET_TYPE}) -endif() - -# Remove any cached result from an older CMake version. -# We now store this in CMakeCCompiler.cmake. -unset(CMAKE_C_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeCCompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(C ${CMAKE_ROOT}/Modules/CMakeCCompilerABI.c) -if(CMAKE_C_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_C_COMPILER_WORKS TRUE) - message(STATUS "Check for working C compiler: ${CMAKE_C_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that that selected C compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_C_COMPILER_WORKS) - PrintTestCompilerStatus("C") - __TestCompiler_setTryCompileTargetType() - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testCCompiler.c - "#ifdef __cplusplus\n" - "# error \"The CMAKE_C_COMPILER is set to a C++ compiler\"\n" - "#endif\n" - "#if defined(__CLASSIC_C__)\n" - "int main(argc, argv)\n" - " int argc;\n" - " char* argv[];\n" - "#else\n" - "int main(int argc, char* argv[])\n" - "#endif\n" - "{ (void)argv; return argc-1;}\n") - try_compile(CMAKE_C_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testCCompiler.c - OUTPUT_VARIABLE __CMAKE_C_COMPILER_OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_C_COMPILER_WORKS ${CMAKE_C_COMPILER_WORKS}) - unset(CMAKE_C_COMPILER_WORKS CACHE) - __TestCompiler_restoreTryCompileTargetType() - if(NOT CMAKE_C_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the C compiler works failed with " - "the following output:\n${__CMAKE_C_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_C_COMPILER_OUTPUT}") - message(FATAL_ERROR "The C compiler\n \"${CMAKE_C_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the C compiler works passed with " - "the following output:\n${__CMAKE_C_COMPILER_OUTPUT}\n\n") -endif() - -# Try to identify the compiler features -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompileFeatures.cmake) -CMAKE_DETERMINE_COMPILE_FEATURES(C) - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeCCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCCompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeCCompiler.cmake) - -if(CMAKE_C_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_C_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_C_ABI_FILES) -endif() - -set(CMAKE_TRY_COMPILE_TARGET_TYPE ${__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE}) -unset(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE) -unset(__CMAKE_C_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CMakeTestCSharpCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestCSharpCompiler.cmake deleted file mode 100644 index 1119a45..0000000 --- a/share/cmake-3.18/Modules/CMakeTestCSharpCompiler.cmake +++ /dev/null
@@ -1,67 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -if(CMAKE_CSharp_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_CSharp_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -unset(CMAKE_CSharp_COMPILER_WORKS CACHE) - -set(test_compile_file "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testCSharpCompiler.cs") - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected C# compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_CSharp_COMPILER_WORKS) - # Don't call PrintTestCompilerStatus() because the "C#" we want to pass - # as the LANG doesn't match with the variable name "CMAKE_CSharp_COMPILER" - message(CHECK_START "Check for working C# compiler: ${CMAKE_CSharp_COMPILER}") - file(WRITE "${test_compile_file}" - "namespace Test {" - " public class CSharp {" - " static void Main(string[] args) {}" - " }" - "}" - ) - try_compile(CMAKE_CSharp_COMPILER_WORKS ${CMAKE_BINARY_DIR} "${test_compile_file}" - OUTPUT_VARIABLE __CMAKE_CSharp_COMPILER_OUTPUT - ) - # Move result from cache to normal variable. - set(CMAKE_CSharp_COMPILER_WORKS ${CMAKE_CSharp_COMPILER_WORKS}) - unset(CMAKE_CSharp_COMPILER_WORKS CACHE) - set(CSharp_TEST_WAS_RUN 1) -endif() - -if(NOT CMAKE_CSharp_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the C# compiler works failed with " - "the following output:\n${__CMAKE_CSharp_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_CSharp_COMPILER_OUTPUT}") - message(FATAL_ERROR "The C# compiler\n \"${CMAKE_CSharp_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") -else() - if(CSharp_TEST_WAS_RUN) - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the C# compiler works passed with " - "the following output:\n${__CMAKE_CSharp_COMPILER_OUTPUT}\n\n") - endif() - - # Re-configure to save learned information. - configure_file( - ${CMAKE_ROOT}/Modules/CMakeCSharpCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCSharpCompiler.cmake - @ONLY - ) - include(${CMAKE_PLATFORM_INFO_DIR}/CMakeCSharpCompiler.cmake) -endif()
diff --git a/share/cmake-3.18/Modules/CMakeTestCUDACompiler.cmake b/share/cmake-3.18/Modules/CMakeTestCUDACompiler.cmake deleted file mode 100644 index a18947b..0000000 --- a/share/cmake-3.18/Modules/CMakeTestCUDACompiler.cmake +++ /dev/null
@@ -1,98 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -if(CMAKE_CUDA_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_CUDA_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# Remove any cached result from an older CMake version. -# We now store this in CMakeCUDACompiler.cmake. -unset(CMAKE_CUDA_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeCUDACompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(CUDA ${CMAKE_ROOT}/Modules/CMakeCUDACompilerABI.cu) -if(CMAKE_CUDA_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_CUDA_COMPILER_WORKS TRUE) - message(STATUS "Check for working CUDA compiler: ${CMAKE_CUDA_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected cuda compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_CUDA_COMPILER_WORKS) - PrintTestCompilerStatus("CUDA") - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/main.cu - "#ifndef __CUDACC__\n" - "# error \"The CMAKE_CUDA_COMPILER is set to an invalid CUDA compiler\"\n" - "#endif\n" - "int main(){return 0;}\n") - - try_compile(CMAKE_CUDA_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/main.cu - OUTPUT_VARIABLE __CMAKE_CUDA_COMPILER_OUTPUT) - - # Move result from cache to normal variable. - set(CMAKE_CUDA_COMPILER_WORKS ${CMAKE_CUDA_COMPILER_WORKS}) - unset(CMAKE_CUDA_COMPILER_WORKS CACHE) - if(NOT CMAKE_CUDA_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the CUDA compiler works failed with " - "the following output:\n${__CMAKE_CUDA_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_CUDA_COMPILER_OUTPUT}") - message(FATAL_ERROR "The CUDA compiler\n \"${CMAKE_CUDA_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the CUDA compiler works passed with " - "the following output:\n${__CMAKE_CUDA_COMPILER_OUTPUT}\n\n") -endif() - -# Try to identify the compiler features -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompileFeatures.cmake) -CMAKE_DETERMINE_COMPILE_FEATURES(CUDA) - -if("x${CMAKE_CUDA_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES "${CMAKE_CUDA_HOST_IMPLICIT_LINK_LIBRARIES}") - set(CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES "${CMAKE_CUDA_HOST_IMPLICIT_LINK_DIRECTORIES}") -endif() - -# Filter out implicit link libraries that should not be passed unconditionally. -# See CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES_EXCLUDE in CMakeDetermineCUDACompiler. -list(REMOVE_ITEM CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES ${CMAKE_CUDA_IMPLICIT_LINK_LIBRARIES_EXCLUDE}) - -if(CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA") - # Remove the CUDA Toolkit include directories from the set of - # implicit system include directories. - # This resolves the issue that NVCC doesn't specify these - # includes as SYSTEM includes when compiling device code, and sometimes - # they contain headers that generate warnings, so let users mark them - # as SYSTEM explicitly - if(CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES) - list(REMOVE_ITEM CMAKE_CUDA_IMPLICIT_INCLUDE_DIRECTORIES - ${CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES} - ) - endif() -endif() - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeCUDACompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCUDACompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeCUDACompiler.cmake) - -unset(__CMAKE_CUDA_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CMakeTestCXXCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestCXXCompiler.cmake deleted file mode 100644 index b9cb1dd..0000000 --- a/share/cmake-3.18/Modules/CMakeTestCXXCompiler.cmake +++ /dev/null
@@ -1,91 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(CMAKE_CXX_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_CXX_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# work around enforced code signing and / or missing exectuable target type -set(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE ${CMAKE_TRY_COMPILE_TARGET_TYPE}) -if(_CMAKE_FEATURE_DETECTION_TARGET_TYPE) - set(CMAKE_TRY_COMPILE_TARGET_TYPE ${_CMAKE_FEATURE_DETECTION_TARGET_TYPE}) -endif() - -# Remove any cached result from an older CMake version. -# We now store this in CMakeCXXCompiler.cmake. -unset(CMAKE_CXX_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeCXXCompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(CXX ${CMAKE_ROOT}/Modules/CMakeCXXCompilerABI.cpp) -if(CMAKE_CXX_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_CXX_COMPILER_WORKS TRUE) - message(STATUS "Check for working CXX compiler: ${CMAKE_CXX_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected C++ compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_CXX_COMPILER_WORKS) - PrintTestCompilerStatus("CXX") - __TestCompiler_setTryCompileTargetType() - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testCXXCompiler.cxx - "#ifndef __cplusplus\n" - "# error \"The CMAKE_CXX_COMPILER is set to a C compiler\"\n" - "#endif\n" - "int main(){return 0;}\n") - try_compile(CMAKE_CXX_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testCXXCompiler.cxx - OUTPUT_VARIABLE __CMAKE_CXX_COMPILER_OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_CXX_COMPILER_WORKS ${CMAKE_CXX_COMPILER_WORKS}) - unset(CMAKE_CXX_COMPILER_WORKS CACHE) - __TestCompiler_restoreTryCompileTargetType() - if(NOT CMAKE_CXX_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the CXX compiler works failed with " - "the following output:\n${__CMAKE_CXX_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_CXX_COMPILER_OUTPUT}") - message(FATAL_ERROR "The C++ compiler\n \"${CMAKE_CXX_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the CXX compiler works passed with " - "the following output:\n${__CMAKE_CXX_COMPILER_OUTPUT}\n\n") -endif() - -# Try to identify the compiler features -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompileFeatures.cmake) -CMAKE_DETERMINE_COMPILE_FEATURES(CXX) - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeCXXCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeCXXCompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeCXXCompiler.cmake) - -if(CMAKE_CXX_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_CXX_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_CXX_ABI_FILES) -endif() - -set(CMAKE_TRY_COMPILE_TARGET_TYPE ${__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE}) -unset(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE) -unset(__CMAKE_CXX_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CMakeTestFortranCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestFortranCompiler.cmake deleted file mode 100644 index 10fb0a7..0000000 --- a/share/cmake-3.18/Modules/CMakeTestFortranCompiler.cmake +++ /dev/null
@@ -1,102 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(CMAKE_Fortran_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_Fortran_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# Remove any cached result from an older CMake version. -# We now store this in CMakeFortranCompiler.cmake. -unset(CMAKE_Fortran_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeFortranCompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(Fortran ${CMAKE_ROOT}/Modules/CMakeFortranCompilerABI.F) -if(CMAKE_Fortran_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_Fortran_COMPILER_WORKS TRUE) - message(STATUS "Check for working Fortran compiler: ${CMAKE_Fortran_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected Fortran compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_Fortran_COMPILER_WORKS) - PrintTestCompilerStatus("Fortran") - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompiler.f " - PROGRAM TESTFortran - PRINT *, 'Hello' - END - ") - try_compile(CMAKE_Fortran_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompiler.f - OUTPUT_VARIABLE OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_Fortran_COMPILER_WORKS ${CMAKE_Fortran_COMPILER_WORKS}) - unset(CMAKE_Fortran_COMPILER_WORKS CACHE) - if(NOT CMAKE_Fortran_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Fortran compiler works failed with " - "the following output:\n${OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${OUTPUT}") - message(FATAL_ERROR "The Fortran compiler\n \"${CMAKE_Fortran_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Fortran compiler works passed with " - "the following output:\n${OUTPUT}\n\n") -endif() - -# Test for Fortran 90 support by using an f90-specific construct. -if(NOT DEFINED CMAKE_Fortran_COMPILER_SUPPORTS_F90) - message(CHECK_START "Checking whether ${CMAKE_Fortran_COMPILER} supports Fortran 90") - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompilerF90.f90 " - PROGRAM TESTFortran90 - integer stop ; stop = 1 ; do while ( stop .eq. 0 ) ; end do - END PROGRAM TESTFortran90 -") - try_compile(CMAKE_Fortran_COMPILER_SUPPORTS_F90 ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompilerF90.f90 - OUTPUT_VARIABLE OUTPUT) - if(CMAKE_Fortran_COMPILER_SUPPORTS_F90) - message(CHECK_PASS "yes") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Fortran compiler supports Fortran 90 passed with " - "the following output:\n${OUTPUT}\n\n") - set(CMAKE_Fortran_COMPILER_SUPPORTS_F90 1) - else() - message(CHECK_FAIL "no") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Fortran compiler supports Fortran 90 failed with " - "the following output:\n${OUTPUT}\n\n") - set(CMAKE_Fortran_COMPILER_SUPPORTS_F90 0) - endif() - unset(CMAKE_Fortran_COMPILER_SUPPORTS_F90 CACHE) -endif() - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeFortranCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeFortranCompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeFortranCompiler.cmake) - -if(CMAKE_Fortran_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_Fortran_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_Fortran_ABI_FILES) -endif()
diff --git a/share/cmake-3.18/Modules/CMakeTestGNU.c b/share/cmake-3.18/Modules/CMakeTestGNU.c deleted file mode 100644 index 933e5a2..0000000 --- a/share/cmake-3.18/Modules/CMakeTestGNU.c +++ /dev/null
@@ -1,9 +0,0 @@ -#if defined(__GNUC__) && !defined(__INTEL_COMPILER) -void THIS_IS_GNU(); -#endif -#ifdef __MINGW32__ -void THIS_IS_MINGW(); -#endif -#ifdef __CYGWIN__ -void THIS_IS_CYGWIN(); -#endif
diff --git a/share/cmake-3.18/Modules/CMakeTestOBJCCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestOBJCCompiler.cmake deleted file mode 100644 index 0e333c0..0000000 --- a/share/cmake-3.18/Modules/CMakeTestOBJCCompiler.cmake +++ /dev/null
@@ -1,95 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(CMAKE_OBJC_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_OBJC_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# work around enforced code signing and / or missing exectuable target type -set(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE ${CMAKE_TRY_COMPILE_TARGET_TYPE}) -if(_CMAKE_FEATURE_DETECTION_TARGET_TYPE) - set(CMAKE_TRY_COMPILE_TARGET_TYPE ${_CMAKE_FEATURE_DETECTION_TARGET_TYPE}) -endif() - -# Remove any cached result from an older CMake version. -# We now store this in CMakeCCompiler.cmake. -unset(CMAKE_OBJC_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeOBJCCompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(OBJC ${CMAKE_ROOT}/Modules/CMakeOBJCCompilerABI.m) -if(CMAKE_OBJC_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_OBJC_COMPILER_WORKS TRUE) - message(STATUS "Check for working OBJC compiler: ${CMAKE_OBJC_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that that selected Objective-C compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_OBJC_COMPILER_WORKS) - PrintTestCompilerStatus("OBJC") - __TestCompiler_setTryCompileTargetType() - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testOBJCCompiler.m - "#ifdef __cplusplus\n" - "# error \"The CMAKE_OBJC_COMPILER is set to a C++ compiler\"\n" - "#endif\n" - "#ifndef __OBJC__\n" - "# error \"The CMAKE_OBJC_COMPILER is not an Objective-C compiler\"\n" - "#endif\n" - "int main(int argc, char* argv[])\n" - "{ (void)argv; return argc-1;}\n") - try_compile(CMAKE_OBJC_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testOBJCCompiler.m - OUTPUT_VARIABLE __CMAKE_OBJC_COMPILER_OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_OBJC_COMPILER_WORKS ${CMAKE_OBJC_COMPILER_WORKS}) - unset(CMAKE_OBJC_COMPILER_WORKS CACHE) - __TestCompiler_restoreTryCompileTargetType() - if(NOT CMAKE_OBJC_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Objective-C compiler works failed with " - "the following output:\n${__CMAKE_OBJC_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_OBJC_COMPILER_OUTPUT}") - message(FATAL_ERROR "The Objective-C compiler\n \"${CMAKE_OBJC_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Objective-C compiler works passed with " - "the following output:\n${__CMAKE_OBJC_COMPILER_OUTPUT}\n\n") -endif() - -# Try to identify the compiler features -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompileFeatures.cmake) -CMAKE_DETERMINE_COMPILE_FEATURES(OBJC) - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeOBJCCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCCompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCCompiler.cmake) - -if(CMAKE_OBJC_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_OBJC_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_OBJC_ABI_FILES) -endif() - -set(CMAKE_TRY_COMPILE_TARGET_TYPE ${__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE}) -unset(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE) -unset(__CMAKE_OBJC_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CMakeTestOBJCXXCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestOBJCXXCompiler.cmake deleted file mode 100644 index dc153a7..0000000 --- a/share/cmake-3.18/Modules/CMakeTestOBJCXXCompiler.cmake +++ /dev/null
@@ -1,94 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -if(CMAKE_OBJCXX_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_OBJCXX_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# work around enforced code signing and / or missing exectuable target type -set(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE ${CMAKE_TRY_COMPILE_TARGET_TYPE}) -if(_CMAKE_FEATURE_DETECTION_TARGET_TYPE) - set(CMAKE_TRY_COMPILE_TARGET_TYPE ${_CMAKE_FEATURE_DETECTION_TARGET_TYPE}) -endif() - -# Remove any cached result from an older CMake version. -# We now store this in CMakeOBJCXXCompiler.cmake. -unset(CMAKE_OBJCXX_COMPILER_WORKS CACHE) - -# Try to identify the ABI and configure it into CMakeOBJCXXCompiler.cmake -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompilerABI.cmake) -CMAKE_DETERMINE_COMPILER_ABI(OBJCXX ${CMAKE_ROOT}/Modules/CMakeOBJCXXCompilerABI.mm) -if(CMAKE_OBJCXX_ABI_COMPILED) - # The compiler worked so skip dedicated test below. - set(CMAKE_OBJCXX_COMPILER_WORKS TRUE) - message(STATUS "Check for working OBJCXX compiler: ${CMAKE_OBJCXX_COMPILER} - skipped") -endif() - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected Objective-C++ compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_OBJCXX_COMPILER_WORKS) - PrintTestCompilerStatus("OBJCXX") - __TestCompiler_setTryCompileTargetType() - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testOBJCXXCompiler.mm - "#ifndef __cplusplus\n" - "# error \"The CMAKE_OBJCXX_COMPILER is set to a C compiler\"\n" - "#endif\n" - "#ifndef __OBJC__\n" - "# error \"The CMAKE_OBJCXX_COMPILER is not an Objective-C++ compiler\"\n" - "#endif\n" - "int main(){return 0;}\n") - try_compile(CMAKE_OBJCXX_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testOBJCXXCompiler.mm - OUTPUT_VARIABLE __CMAKE_OBJCXX_COMPILER_OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_OBJCXX_COMPILER_WORKS ${CMAKE_OBJCXX_COMPILER_WORKS}) - unset(CMAKE_OBJCXX_COMPILER_WORKS CACHE) - __TestCompiler_restoreTryCompileTargetType() - if(NOT CMAKE_OBJCXX_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Objective-C++ compiler works failed with " - "the following output:\n${__CMAKE_OBJCXX_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_OBJCXX_COMPILER_OUTPUT}") - message(FATAL_ERROR "The Objective-C++ compiler\n \"${CMAKE_OBJCXX_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") - endif() - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Objective-C++ compiler works passed with " - "the following output:\n${__CMAKE_OBJCXX_COMPILER_OUTPUT}\n\n") -endif() - -# Try to identify the compiler features -include(${CMAKE_ROOT}/Modules/CMakeDetermineCompileFeatures.cmake) -CMAKE_DETERMINE_COMPILE_FEATURES(OBJCXX) - -# Re-configure to save learned information. -configure_file( - ${CMAKE_ROOT}/Modules/CMakeOBJCXXCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCXXCompiler.cmake - @ONLY - ) -include(${CMAKE_PLATFORM_INFO_DIR}/CMakeOBJCXXCompiler.cmake) - -if(CMAKE_OBJCXX_SIZEOF_DATA_PTR) - foreach(f ${CMAKE_OBJCXX_ABI_FILES}) - include(${f}) - endforeach() - unset(CMAKE_OBJCXX_ABI_FILES) -endif() - -set(CMAKE_TRY_COMPILE_TARGET_TYPE ${__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE}) -unset(__CMAKE_SAVED_TRY_COMPILE_TARGET_TYPE) -unset(__CMAKE_OBJCXX_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CMakeTestSwiftCompiler.cmake b/share/cmake-3.18/Modules/CMakeTestSwiftCompiler.cmake deleted file mode 100644 index d98dc9d..0000000 --- a/share/cmake-3.18/Modules/CMakeTestSwiftCompiler.cmake +++ /dev/null
@@ -1,64 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -if(CMAKE_Swift_COMPILER_FORCED) - # The compiler configuration was forced by the user. - # Assume the user has configured all compiler information. - set(CMAKE_Swift_COMPILER_WORKS TRUE) - return() -endif() - -include(CMakeTestCompilerCommon) - -# Remove any cached result from an older CMake version. -# We now store this in CMakeSwiftCompiler.cmake. -unset(CMAKE_Swift_COMPILER_WORKS CACHE) - -# This file is used by EnableLanguage in cmGlobalGenerator to -# determine that the selected C++ compiler can actually compile -# and link the most basic of programs. If not, a fatal error -# is set and cmake stops processing commands and will not generate -# any makefiles or projects. -if(NOT CMAKE_Swift_COMPILER_WORKS) - PrintTestCompilerStatus("Swift") - file(WRITE ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/main.swift - "print(\"CMake\")\n") - try_compile(CMAKE_Swift_COMPILER_WORKS ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/main.swift - OUTPUT_VARIABLE __CMAKE_Swift_COMPILER_OUTPUT) - # Move result from cache to normal variable. - set(CMAKE_Swift_COMPILER_WORKS ${CMAKE_Swift_COMPILER_WORKS}) - unset(CMAKE_Swift_COMPILER_WORKS CACHE) - set(Swift_TEST_WAS_RUN 1) -endif() - -if(NOT CMAKE_Swift_COMPILER_WORKS) - PrintTestCompilerResult(CHECK_FAIL "broken") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Swift compiler works failed with " - "the following output:\n${__CMAKE_Swift_COMPILER_OUTPUT}\n\n") - string(REPLACE "\n" "\n " _output "${__CMAKE_Swift_COMPILER_OUTPUT}") - message(FATAL_ERROR "The Swift compiler\n \"${CMAKE_Swift_COMPILER}\"\n" - "is not able to compile a simple test program.\nIt fails " - "with the following output:\n ${_output}\n\n" - "CMake will not be able to correctly generate this project.") -else() - if(Swift_TEST_WAS_RUN) - PrintTestCompilerResult(CHECK_PASS "works") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Swift compiler works passed with " - "the following output:\n${__CMAKE_Swift_COMPILER_OUTPUT}\n\n") - endif() - - # Unlike C and CXX we do not yet detect any information about the Swift ABI. - # However, one of the steps done for C and CXX as part of that detection is - # to initialize the implicit include directories. That is relevant here. - set(CMAKE_Swift_IMPLICIT_INCLUDE_DIRECTORIES "${_CMAKE_Swift_IMPLICIT_INCLUDE_DIRECTORIES_INIT}") - - # Re-configure to save learned information. - configure_file(${CMAKE_ROOT}/Modules/CMakeSwiftCompiler.cmake.in - ${CMAKE_PLATFORM_INFO_DIR}/CMakeSwiftCompiler.cmake @ONLY) - include(${CMAKE_PLATFORM_INFO_DIR}/CMakeSwiftCompiler.cmake) -endif() - -unset(__CMAKE_Swift_COMPILER_OUTPUT)
diff --git a/share/cmake-3.18/Modules/CPack.cmake b/share/cmake-3.18/Modules/CPack.cmake deleted file mode 100644 index d0cfc2b..0000000 --- a/share/cmake-3.18/Modules/CPack.cmake +++ /dev/null
@@ -1,809 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CPack ------ - -Configure generators for binary installers and source packages. - -Introduction -^^^^^^^^^^^^ - -The CPack module generates the configuration files ``CPackConfig.cmake`` -and ``CPackSourceConfig.cmake``. They are intended for use in a subsequent -run of the :manual:`cpack <cpack(1)>` program where they steer the generation -of installers or/and source packages. - -Depending on the CMake generator, the CPack module may also add two new build -targets, ``package`` and ``package_source``. See the `packaging targets`_ -section below for details. - -The generated binary installers will contain all files that have been installed -via CMake's :command:`install` command (and the deprecated commands -:command:`install_files`, :command:`install_programs`, and -:command:`install_targets`). Certain kinds of binary installers can be -configured such that users can select individual application components to -install. See the :module:`CPackComponent` module for further details. - -Source packages (configured through ``CPackSourceConfig.cmake`` and generated -by the :cpack_gen:`CPack Archive Generator`) will contain all source files in -the project directory except those specified in -:variable:`CPACK_SOURCE_IGNORE_FILES`. - -CPack Generators -^^^^^^^^^^^^^^^^ - -The :variable:`CPACK_GENERATOR` variable has different meanings in different -contexts. In a ``CMakeLists.txt`` file, :variable:`CPACK_GENERATOR` is a -*list of generators*: and when :manual:`cpack <cpack(1)>` is run with no other -arguments, it will iterate over that list and produce one package for each -generator. In a :variable:`CPACK_PROJECT_CONFIG_FILE`, -:variable:`CPACK_GENERATOR` is a *string naming a single generator*. If you -need per-cpack-generator logic to control *other* cpack settings, then you -need a :variable:`CPACK_PROJECT_CONFIG_FILE`. -If set, the :variable:`CPACK_PROJECT_CONFIG_FILE` is included automatically -on a per-generator basis. It only need contain overrides. - -Here's how it works: - -* :manual:`cpack <cpack(1)>` runs -* it includes ``CPackConfig.cmake`` -* it iterates over the generators given by the ``-G`` command line option, - or if no such option was specified, over the list of generators given by - the :variable:`CPACK_GENERATOR` variable set in the ``CPackConfig.cmake`` - input file. -* foreach generator, it then - - - sets :variable:`CPACK_GENERATOR` to the one currently being iterated - - includes the :variable:`CPACK_PROJECT_CONFIG_FILE` - - produces the package for that generator - -This is the key: For each generator listed in :variable:`CPACK_GENERATOR` in -``CPackConfig.cmake``, cpack will *reset* :variable:`CPACK_GENERATOR` -internally to *the one currently being used* and then include the -:variable:`CPACK_PROJECT_CONFIG_FILE`. - -For a list of available generators, see :manual:`cpack-generators(7)`. - -.. _`packaging targets`: - -Targets package and package_source -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -If CMake is run with the Makefile, Ninja, or Xcode generator, then -``include(CPack)`` generates a target ``package``. This makes it possible -to build a binary installer from CMake, Make, or Ninja: Instead of ``cpack``, -one may call ``cmake --build . --target package`` or ``make package`` or -``ninja package``. The VS generator creates an uppercase target ``PACKAGE``. - -If CMake is run with the Makefile or Ninja generator, then ``include(CPack)`` -also generates a target ``package_source``. To build a source package, -instead of ``cpack -G TGZ --config CPackSourceConfig.cmake`` one may call -``cmake --build . --target package_source``, ``make package_source``, -or ``ninja package_source``. - - -Variables common to all CPack Generators -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Before including this CPack module in your ``CMakeLists.txt`` file, there -are a variety of variables that can be set to customize the resulting -installers. The most commonly-used variables are: - -.. variable:: CPACK_PACKAGE_NAME - - The name of the package (or application). If not specified, it defaults to - the project name. - -.. variable:: CPACK_PACKAGE_VENDOR - - The name of the package vendor. (e.g., "Kitware"). The default is "Humanity". - -.. variable:: CPACK_PACKAGE_DIRECTORY - - The directory in which CPack is doing its packaging. If it is not set - then this will default (internally) to the build dir. This variable may - be defined in a CPack config file or from the :manual:`cpack <cpack(1)>` - command line option ``-B``. If set, the command line option overrides the - value found in the config file. - -.. variable:: CPACK_PACKAGE_VERSION_MAJOR - - Package major version. This variable will always be set, but its default - value depends on whether or not version details were given to the - :command:`project` command in the top level CMakeLists.txt file. If version - details were given, the default value will be - :variable:`CMAKE_PROJECT_VERSION_MAJOR`. If no version details were given, - a default version of 0.1.1 will be assumed, leading to - ``CPACK_PACKAGE_VERSION_MAJOR`` having a default value of 0. - -.. variable:: CPACK_PACKAGE_VERSION_MINOR - - Package minor version. The default value is determined based on whether or - not version details were given to the :command:`project` command in the top - level CMakeLists.txt file. If version details were given, the default - value will be :variable:`CMAKE_PROJECT_VERSION_MINOR`, but if no minor - version component was specified then ``CPACK_PACKAGE_VERSION_MINOR`` will be - left unset. If no project version was given at all, a default version of - 0.1.1 will be assumed, leading to ``CPACK_PACKAGE_VERSION_MINOR`` having a - default value of 1. - -.. variable:: CPACK_PACKAGE_VERSION_PATCH - - Package patch version. The default value is determined based on whether or - not version details were given to the :command:`project` command in the top - level CMakeLists.txt file. If version details were given, the default - value will be :variable:`CMAKE_PROJECT_VERSION_PATCH`, but if no patch - version component was specified then ``CPACK_PACKAGE_VERSION_PATCH`` will be - left unset. If no project version was given at all, a default version of - 0.1.1 will be assumed, leading to ``CPACK_PACKAGE_VERSION_PATCH`` having a - default value of 1. - -.. variable:: CPACK_PACKAGE_DESCRIPTION - - A description of the project, used in places such as the introduction - screen of CPack-generated Windows installers. If not set, the value of - this variable is populated from the file named by - :variable:`CPACK_PACKAGE_DESCRIPTION_FILE`. - -.. variable:: CPACK_PACKAGE_DESCRIPTION_FILE - - A text file used to describe the project when - :variable:`CPACK_PACKAGE_DESCRIPTION` is not explicitly set. The default - value for ``CPACK_PACKAGE_DESCRIPTION_FILE`` points to a built-in template - file ``Templates/CPack.GenericDescription.txt``. - -.. variable:: CPACK_PACKAGE_DESCRIPTION_SUMMARY - - Short description of the project (only a few words). If the - :variable:`CMAKE_PROJECT_DESCRIPTION` variable is set, it is used as the - default value, otherwise the default will be a string generated by CMake - based on :variable:`CMAKE_PROJECT_NAME`. - -.. variable:: CPACK_PACKAGE_HOMEPAGE_URL - - Project homepage URL. The default value is taken from the - :variable:`CMAKE_PROJECT_HOMEPAGE_URL` variable, which is set by the top - level :command:`project` command, or else the default will be empty if no - URL was provided to :command:`project`. - -.. variable:: CPACK_PACKAGE_FILE_NAME - - The name of the package file to generate, not including the - extension. For example, ``cmake-2.6.1-Linux-i686``. The default value - is:: - - ${CPACK_PACKAGE_NAME}-${CPACK_PACKAGE_VERSION}-${CPACK_SYSTEM_NAME} - -.. variable:: CPACK_PACKAGE_INSTALL_DIRECTORY - - Installation directory on the target system. This may be used by some - CPack generators like NSIS to create an installation directory e.g., - "CMake 2.5" below the installation prefix. All installed elements will be - put inside this directory. - -.. variable:: CPACK_PACKAGE_ICON - - A branding image that will be displayed inside the installer (used by GUI - installers). - -.. variable:: CPACK_PACKAGE_CHECKSUM - - An algorithm that will be used to generate an additional file with the - checksum of the package. The output file name will be:: - - ${CPACK_PACKAGE_FILE_NAME}.${CPACK_PACKAGE_CHECKSUM} - - Supported algorithms are those listed by the - :ref:`string(\<HASH\>) <Supported Hash Algorithms>` command. - -.. variable:: CPACK_PROJECT_CONFIG_FILE - - CPack-time project CPack configuration file. This file is included at cpack - time, once per generator after CPack has set :variable:`CPACK_GENERATOR` - to the actual generator being used. It allows per-generator setting of - ``CPACK_*`` variables at cpack time. - -.. variable:: CPACK_RESOURCE_FILE_LICENSE - - License to be embedded in the installer. It will typically be displayed - to the user by the produced installer (often with an explicit "Accept" - button, for graphical installers) prior to installation. This license - file is NOT added to the installed files but is used by some CPack generators - like NSIS. If you want to install a license file (may be the same as this - one) along with your project, you must add an appropriate CMake - :command:`install` command in your ``CMakeLists.txt``. - -.. variable:: CPACK_RESOURCE_FILE_README - - ReadMe file to be embedded in the installer. It typically describes in - some detail the purpose of the project during the installation. Not all - CPack generators use this file. - -.. variable:: CPACK_RESOURCE_FILE_WELCOME - - Welcome file to be embedded in the installer. It welcomes users to this - installer. Typically used in the graphical installers on Windows and Mac - OS X. - -.. variable:: CPACK_MONOLITHIC_INSTALL - - Disables the component-based installation mechanism. When set, the - component specification is ignored and all installed items are put in a - single "MONOLITHIC" package. Some CPack generators do monolithic - packaging by default and may be asked to do component packaging by - setting ``CPACK_<GENNAME>_COMPONENT_INSTALL`` to ``TRUE``. - -.. variable:: CPACK_GENERATOR - - List of CPack generators to use. If not specified, CPack will create a - set of options following the naming pattern - :variable:`CPACK_BINARY_<GENNAME>` (e.g. ``CPACK_BINARY_NSIS``) allowing - the user to enable/disable individual generators. If the ``-G`` option is - given on the :manual:`cpack <cpack(1)>` command line, it will override this - variable and any ``CPACK_BINARY_<GENNAME>`` options. - -.. variable:: CPACK_OUTPUT_CONFIG_FILE - - The name of the CPack binary configuration file. This file is the CPack - configuration generated by the CPack module for binary installers. - Defaults to ``CPackConfig.cmake``. - -.. variable:: CPACK_PACKAGE_EXECUTABLES - - Lists each of the executables and associated text label to be used to - create Start Menu shortcuts. For example, setting this to the list - ``ccmake;CMake`` will create a shortcut named "CMake" that will execute the - installed executable ``ccmake``. Not all CPack generators use it (at least - NSIS, WIX and OSXX11 do). - -.. variable:: CPACK_STRIP_FILES - - List of files to be stripped. Starting with CMake 2.6.0, - ``CPACK_STRIP_FILES`` will be a boolean variable which enables - stripping of all files (a list of files evaluates to ``TRUE`` in CMake, - so this change is compatible). - -.. variable:: CPACK_VERBATIM_VARIABLES - - If set to ``TRUE``, values of variables prefixed with ``CPACK_`` will be - escaped before being written to the configuration files, so that the cpack - program receives them exactly as they were specified. If not, characters - like quotes and backslashes can cause parsing errors or alter the value - received by the cpack program. Defaults to ``FALSE`` for backwards - compatibility. - -Variables for Source Package Generators -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following CPack variables are specific to source packages, and -will not affect binary packages: - -.. variable:: CPACK_SOURCE_PACKAGE_FILE_NAME - - The name of the source package. For example ``cmake-2.6.1``. - -.. variable:: CPACK_SOURCE_STRIP_FILES - - List of files in the source tree that will be stripped. Starting with - CMake 2.6.0, ``CPACK_SOURCE_STRIP_FILES`` will be a boolean - variable which enables stripping of all files (a list of files evaluates - to ``TRUE`` in CMake, so this change is compatible). - -.. variable:: CPACK_SOURCE_GENERATOR - - List of generators used for the source packages. As with - :variable:`CPACK_GENERATOR`, if this is not specified then CPack will - create a set of options (e.g. ``CPACK_SOURCE_ZIP``) allowing - users to select which packages will be generated. - -.. variable:: CPACK_SOURCE_OUTPUT_CONFIG_FILE - - The name of the CPack source configuration file. This file is the CPack - configuration generated by the CPack module for source installers. - Defaults to ``CPackSourceConfig.cmake``. - -.. variable:: CPACK_SOURCE_IGNORE_FILES - - Pattern of files in the source tree that won't be packaged when building - a source package. This is a list of regular expression patterns (that - must be properly escaped), e.g., - ``/CVS/;/\\.svn/;\\.swp$;\\.#;/#;.*~;cscope.*`` - -Variables for Advanced Use -^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following variables are for advanced uses of CPack: - -.. variable:: CPACK_CMAKE_GENERATOR - - What CMake generator should be used if the project is a CMake - project. Defaults to the value of :variable:`CMAKE_GENERATOR`. Few users - will want to change this setting. - -.. variable:: CPACK_INSTALL_CMAKE_PROJECTS - - List of four values that specify what project to install. The four values - are: Build directory, Project Name, Project Component, Directory. If - omitted, CPack will build an installer that installs everything. - -.. variable:: CPACK_SYSTEM_NAME - - System name, defaults to the value of :variable:`CMAKE_SYSTEM_NAME`, - except on Windows where it will be ``win32`` or ``win64``. - -.. variable:: CPACK_PACKAGE_VERSION - - Package full version, used internally. By default, this is built from - :variable:`CPACK_PACKAGE_VERSION_MAJOR`, - :variable:`CPACK_PACKAGE_VERSION_MINOR`, and - :variable:`CPACK_PACKAGE_VERSION_PATCH`. - -.. variable:: CPACK_TOPLEVEL_TAG - - Directory for the installed files. - -.. variable:: CPACK_INSTALL_COMMANDS - - Extra commands to install components. The environment variable - ``CMAKE_INSTALL_PREFIX`` is set to the temporary install directory - during execution. - -.. variable:: CPACK_INSTALL_SCRIPTS - - Extra CMake scripts executed by CPack during its local staging - installation, which is done right before packaging the files. - The scripts are not called by a standalone install (e.g.: ``make install``). - For every script, the following variables will be set: - :variable:`CMAKE_CURRENT_SOURCE_DIR`, :variable:`CMAKE_CURRENT_BINARY_DIR` - and :variable:`CMAKE_INSTALL_PREFIX` (which is set to the staging install - directory). The singular form ``CMAKE_INSTALL_SCRIPT`` is supported as - an alternative variable for historical reasons, but its value is ignored if - ``CMAKE_INSTALL_SCRIPTS`` is set and a warning will be issued. - -.. variable:: CPACK_INSTALLED_DIRECTORIES - - Extra directories to install. - -.. variable:: CPACK_PACKAGE_INSTALL_REGISTRY_KEY - - Registry key used when installing this project. This is only used by - installers for Windows. The default value is based on the installation - directory. - -.. variable:: CPACK_CREATE_DESKTOP_LINKS - - List of desktop links to create. Each desktop link requires a - corresponding start menu shortcut as created by - :variable:`CPACK_PACKAGE_EXECUTABLES`. - -.. variable:: CPACK_BINARY_<GENNAME> - - CPack generated options for binary generators. The ``CPack.cmake`` module - generates (when :variable:`CPACK_GENERATOR` is not set) a set of CMake - options (see CMake :command:`option` command) which may then be used to - select the CPack generator(s) to be used when building the ``package`` - target or when running :manual:`cpack <cpack(1)>` without the ``-G`` option. - -#]=======================================================================] - -# Define this var in order to avoid (or warn) concerning multiple inclusion -if(CPack_CMake_INCLUDED) - message(WARNING "CPack.cmake has already been included!!") -else() - set(CPack_CMake_INCLUDED 1) -endif() - -# Pick a configuration file -set(cpack_input_file "${CMAKE_ROOT}/Templates/CPackConfig.cmake.in") -if(EXISTS "${CMAKE_SOURCE_DIR}/CPackConfig.cmake.in") - set(cpack_input_file "${CMAKE_SOURCE_DIR}/CPackConfig.cmake.in") -endif() -set(cpack_source_input_file "${CMAKE_ROOT}/Templates/CPackConfig.cmake.in") -if(EXISTS "${CMAKE_SOURCE_DIR}/CPackSourceConfig.cmake.in") - set(cpack_source_input_file "${CMAKE_SOURCE_DIR}/CPackSourceConfig.cmake.in") -endif() - -# Backward compatibility -# Include CPackComponent macros if it has not already been included before. -include(CPackComponent) - -# Macro for setting values if a user did not overwrite them -# Mangles CMake-special characters. Only kept for backwards compatibility. -macro(cpack_set_if_not_set name value) - message(DEPRECATION "cpack_set_if_not_set is obsolete; do not use.") - _cpack_set_default("${name}" "${value}") -endmacro() - -# cpack_encode_variables - Function to encode variables for the configuration file -# find any variable that starts with CPACK and create a variable -# _CPACK_OTHER_VARIABLES_ that contains SET commands for -# each cpack variable. _CPACK_OTHER_VARIABLES_ is then -# used as an @ replacment in configure_file for the CPackConfig. -function(cpack_encode_variables) - set(commands "") - get_cmake_property(res VARIABLES) - foreach(var ${res}) - if(var MATCHES "^CPACK") - if(CPACK_VERBATIM_VARIABLES) - _cpack_escape_for_cmake(value "${${var}}") - else() - set(value "${${var}}") - endif() - - string(APPEND commands "\nset(${var} \"${value}\")") - endif() - endforeach() - - set(_CPACK_OTHER_VARIABLES_ "${commands}" PARENT_SCOPE) -endfunction() - -# Internal use functions -function(_cpack_set_default name value) - if(NOT DEFINED "${name}") - set("${name}" "${value}" PARENT_SCOPE) - endif() -endfunction() - -function(_cpack_escape_for_cmake var value) - string(REGEX REPLACE "([\\\$\"])" "\\\\\\1" escaped "${value}") - set("${var}" "${escaped}" PARENT_SCOPE) -endfunction() - -# Set the package name -_cpack_set_default(CPACK_PACKAGE_NAME "${CMAKE_PROJECT_NAME}") - -# Set the package version -if(CMAKE_PROJECT_VERSION_MAJOR GREATER_EQUAL 0) - _cpack_set_default(CPACK_PACKAGE_VERSION_MAJOR "${CMAKE_PROJECT_VERSION_MAJOR}") - if(CMAKE_PROJECT_VERSION_MINOR GREATER_EQUAL 0) - _cpack_set_default(CPACK_PACKAGE_VERSION_MINOR "${CMAKE_PROJECT_VERSION_MINOR}") - if(CMAKE_PROJECT_VERSION_PATCH GREATER_EQUAL 0) - _cpack_set_default(CPACK_PACKAGE_VERSION_PATCH "${CMAKE_PROJECT_VERSION_PATCH}") - endif() - endif() -else() - _cpack_set_default(CPACK_PACKAGE_VERSION_MAJOR "0") - _cpack_set_default(CPACK_PACKAGE_VERSION_MINOR "1") - _cpack_set_default(CPACK_PACKAGE_VERSION_PATCH "1") -endif() -if(NOT DEFINED CPACK_PACKAGE_VERSION) - set(CPACK_PACKAGE_VERSION "${CPACK_PACKAGE_VERSION_MAJOR}") - if(CPACK_PACKAGE_VERSION_MINOR GREATER_EQUAL 0) - string(APPEND CPACK_PACKAGE_VERSION ".${CPACK_PACKAGE_VERSION_MINOR}") - if(CPACK_PACKAGE_VERSION_PATCH GREATER_EQUAL 0) - string(APPEND CPACK_PACKAGE_VERSION ".${CPACK_PACKAGE_VERSION_PATCH}") - endif() - endif() -endif() - -_cpack_set_default(CPACK_PACKAGE_VENDOR "Humanity") -set(CPACK_DEFAULT_PACKAGE_DESCRIPTION_SUMMARY "${CMAKE_PROJECT_NAME} built using CMake") -if(CMAKE_PROJECT_DESCRIPTION) - _cpack_set_default(CPACK_PACKAGE_DESCRIPTION_SUMMARY - "${CMAKE_PROJECT_DESCRIPTION}") -else() - _cpack_set_default(CPACK_PACKAGE_DESCRIPTION_SUMMARY - "${CPACK_DEFAULT_PACKAGE_DESCRIPTION_SUMMARY}") -endif() -if(CMAKE_PROJECT_HOMEPAGE_URL) - _cpack_set_default(CPACK_PACKAGE_HOMEPAGE_URL - "${CMAKE_PROJECT_HOMEPAGE_URL}") -endif() - -set(CPACK_DEFAULT_PACKAGE_DESCRIPTION_FILE - "${CMAKE_ROOT}/Templates/CPack.GenericDescription.txt") -_cpack_set_default(CPACK_PACKAGE_DESCRIPTION_FILE - "${CPACK_DEFAULT_PACKAGE_DESCRIPTION_FILE}") -_cpack_set_default(CPACK_RESOURCE_FILE_LICENSE - "${CMAKE_ROOT}/Templates/CPack.GenericLicense.txt") -_cpack_set_default(CPACK_RESOURCE_FILE_README - "${CMAKE_ROOT}/Templates/CPack.GenericDescription.txt") -_cpack_set_default(CPACK_RESOURCE_FILE_WELCOME - "${CMAKE_ROOT}/Templates/CPack.GenericWelcome.txt") - -_cpack_set_default(CPACK_MODULE_PATH "${CMAKE_MODULE_PATH}") - -# Set default directory creation permissions mode -if(CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS) - _cpack_set_default(CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS - "${CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS}") -endif() - -if(CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL) - set(CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL ON) -endif() - -if(CPACK_NSIS_MODIFY_PATH) - set(CPACK_NSIS_MODIFY_PATH ON) -endif() - -set(__cpack_system_name ${CMAKE_SYSTEM_NAME}) -if(__cpack_system_name MATCHES "Windows") - if(CMAKE_SIZEOF_VOID_P EQUAL 8) - set(__cpack_system_name win64) - else() - set(__cpack_system_name win32) - endif() -endif() -_cpack_set_default(CPACK_SYSTEM_NAME "${__cpack_system_name}") - -# Root dir: default value should be the string literal "$PROGRAMFILES" -# for backwards compatibility. Projects may set this value to anything. -# When creating 64 bit binaries we set the default value to "$PROGRAMFILES64" -if("x${__cpack_system_name}" STREQUAL "xwin64") - set(__cpack_root_default "$PROGRAMFILES64") -else() - set(__cpack_root_default "$PROGRAMFILES") -endif() -_cpack_set_default(CPACK_NSIS_INSTALL_ROOT "${__cpack_root_default}") - -# <project>-<major>.<minor>.<patch>-<release>-<platform>.<pkgtype> -_cpack_set_default(CPACK_PACKAGE_FILE_NAME - "${CPACK_PACKAGE_NAME}-${CPACK_PACKAGE_VERSION}-${CPACK_SYSTEM_NAME}") -_cpack_set_default(CPACK_PACKAGE_INSTALL_DIRECTORY - "${CPACK_PACKAGE_NAME} ${CPACK_PACKAGE_VERSION}") -_cpack_set_default(CPACK_PACKAGE_INSTALL_REGISTRY_KEY - "${CPACK_PACKAGE_INSTALL_DIRECTORY}") -_cpack_set_default(CPACK_PACKAGE_DEFAULT_LOCATION "/") -_cpack_set_default(CPACK_PACKAGE_RELOCATABLE "true") - -# always force to exactly "true" or "false" for CPack.Info.plist.in: -if(CPACK_PACKAGE_RELOCATABLE) - set(CPACK_PACKAGE_RELOCATABLE "true") -else() - set(CPACK_PACKAGE_RELOCATABLE "false") -endif() - -macro(cpack_check_file_exists file description) - if(NOT EXISTS "${file}") - message(SEND_ERROR "CPack ${description} file: \"${file}\" could not be found.") - endif() -endmacro() - -cpack_check_file_exists("${CPACK_PACKAGE_DESCRIPTION_FILE}" "package description") -cpack_check_file_exists("${CPACK_RESOURCE_FILE_LICENSE}" "license resource") -cpack_check_file_exists("${CPACK_RESOURCE_FILE_README}" "readme resource") -cpack_check_file_exists("${CPACK_RESOURCE_FILE_WELCOME}" "welcome resource") - -macro(cpack_optional_append _list _cond _item) - if(${_cond}) - set(${_list} ${${_list}} ${_item}) - endif() -endmacro() - -# Provide options to choose generators we might check here if the required -# tools for the generators exist and set the defaults according to the -# results. -if(NOT CPACK_GENERATOR) - if(UNIX) - if(CYGWIN) - option(CPACK_BINARY_CYGWIN "Enable to build Cygwin binary packages" ON) - else() - if(APPLE) - option(CPACK_BINARY_BUNDLE "Enable to build OSX bundles" OFF) - option(CPACK_BINARY_DRAGNDROP "Enable to build OSX Drag And Drop package" OFF) - option(CPACK_BINARY_OSXX11 "Enable to build OSX X11 packages (deprecated)" OFF) - option(CPACK_BINARY_PACKAGEMAKER "Enable to build PackageMaker packages (deprecated)" OFF) - option(CPACK_BINARY_PRODUCTBUILD "Enable to build productbuild packages" OFF) - mark_as_advanced( - CPACK_BINARY_BUNDLE - CPACK_BINARY_DRAGNDROP - CPACK_BINARY_OSXX11 - CPACK_BINARY_PACKAGEMAKER - CPACK_BINARY_PRODUCTBUILD - ) - else() - option(CPACK_BINARY_TZ "Enable to build TZ packages" ON) - mark_as_advanced(CPACK_BINARY_TZ) - endif() - option(CPACK_BINARY_DEB "Enable to build Debian packages" OFF) - option(CPACK_BINARY_FREEBSD "Enable to build FreeBSD packages" OFF) - option(CPACK_BINARY_NSIS "Enable to build NSIS packages" OFF) - option(CPACK_BINARY_RPM "Enable to build RPM packages" OFF) - option(CPACK_BINARY_STGZ "Enable to build STGZ packages" ON) - option(CPACK_BINARY_TBZ2 "Enable to build TBZ2 packages" OFF) - option(CPACK_BINARY_TGZ "Enable to build TGZ packages" ON) - option(CPACK_BINARY_TXZ "Enable to build TXZ packages" OFF) - mark_as_advanced( - CPACK_BINARY_DEB - CPACK_BINARY_FREEBSD - CPACK_BINARY_NSIS - CPACK_BINARY_RPM - CPACK_BINARY_STGZ - CPACK_BINARY_TBZ2 - CPACK_BINARY_TGZ - CPACK_BINARY_TXZ - ) - endif() - else() - option(CPACK_BINARY_7Z "Enable to build 7-Zip packages" OFF) - option(CPACK_BINARY_NSIS "Enable to build NSIS packages" ON) - option(CPACK_BINARY_NUGET "Enable to build NuGet packages" OFF) - option(CPACK_BINARY_WIX "Enable to build WiX packages" OFF) - option(CPACK_BINARY_ZIP "Enable to build ZIP packages" OFF) - mark_as_advanced( - CPACK_BINARY_7Z - CPACK_BINARY_NSIS - CPACK_BINARY_NUGET - CPACK_BINARY_WIX - CPACK_BINARY_ZIP - ) - endif() - option(CPACK_BINARY_IFW "Enable to build IFW packages" OFF) - mark_as_advanced(CPACK_BINARY_IFW) - - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_7Z 7Z) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_BUNDLE Bundle) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_CYGWIN CygwinBinary) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_DEB DEB) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_DRAGNDROP DragNDrop) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_FREEBSD FREEBSD) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_IFW IFW) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_NSIS NSIS) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_NUGET NuGet) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_OSXX11 OSXX11) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_PACKAGEMAKER PackageMaker) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_PRODUCTBUILD productbuild) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_RPM RPM) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_STGZ STGZ) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_TBZ2 TBZ2) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_TGZ TGZ) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_TXZ TXZ) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_TZ TZ) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_WIX WIX) - cpack_optional_append(CPACK_GENERATOR CPACK_BINARY_ZIP ZIP) - -endif() - -# Provide options to choose source generators -if(NOT CPACK_SOURCE_GENERATOR) - if(UNIX) - if(CYGWIN) - option(CPACK_SOURCE_CYGWIN "Enable to build Cygwin source packages" ON) - mark_as_advanced(CPACK_SOURCE_CYGWIN) - else() - option(CPACK_SOURCE_RPM "Enable to build RPM source packages" OFF) - option(CPACK_SOURCE_TBZ2 "Enable to build TBZ2 source packages" ON) - option(CPACK_SOURCE_TGZ "Enable to build TGZ source packages" ON) - option(CPACK_SOURCE_TXZ "Enable to build TXZ source packages" ON) - option(CPACK_SOURCE_TZ "Enable to build TZ source packages" ON) - option(CPACK_SOURCE_ZIP "Enable to build ZIP source packages" OFF) - mark_as_advanced( - CPACK_SOURCE_RPM - CPACK_SOURCE_TBZ2 - CPACK_SOURCE_TGZ - CPACK_SOURCE_TXZ - CPACK_SOURCE_TZ - CPACK_SOURCE_ZIP - ) - endif() - else() - option(CPACK_SOURCE_7Z "Enable to build 7-Zip source packages" ON) - option(CPACK_SOURCE_ZIP "Enable to build ZIP source packages" ON) - mark_as_advanced( - CPACK_SOURCE_7Z - CPACK_SOURCE_ZIP - ) - endif() - - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_7Z 7Z) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_CYGWIN CygwinSource) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_RPM RPM) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_TBZ2 TBZ2) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_TGZ TGZ) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_TXZ TXZ) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_TZ TZ) - cpack_optional_append(CPACK_SOURCE_GENERATOR CPACK_SOURCE_ZIP ZIP) -endif() - -# Set some other variables -_cpack_set_default(CPACK_INSTALL_CMAKE_PROJECTS - "${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};ALL;/") -_cpack_set_default(CPACK_CMAKE_GENERATOR "${CMAKE_GENERATOR}") -_cpack_set_default(CPACK_TOPLEVEL_TAG "${CPACK_SYSTEM_NAME}") -# if the user has set CPACK_NSIS_DISPLAY_NAME remember it -if(DEFINED CPACK_NSIS_DISPLAY_NAME) - set(CPACK_NSIS_DISPLAY_NAME_SET TRUE) -endif() -# if the user has set CPACK_NSIS_DISPLAY -# explicitly, then use that as the default -# value of CPACK_NSIS_PACKAGE_NAME instead -# of CPACK_PACKAGE_INSTALL_DIRECTORY -_cpack_set_default(CPACK_NSIS_DISPLAY_NAME "${CPACK_PACKAGE_INSTALL_DIRECTORY}") -# Specify the name of the Uninstall file in NSIS -_cpack_set_default(CPACK_NSIS_UNINSTALL_NAME "Uninstall") - -if(CPACK_NSIS_DISPLAY_NAME_SET) - _cpack_set_default(CPACK_NSIS_PACKAGE_NAME "${CPACK_NSIS_DISPLAY_NAME}") -else() - _cpack_set_default(CPACK_NSIS_PACKAGE_NAME "${CPACK_PACKAGE_INSTALL_DIRECTORY}") -endif() - -_cpack_set_default(CPACK_OUTPUT_CONFIG_FILE - "${CMAKE_BINARY_DIR}/CPackConfig.cmake") - -_cpack_set_default(CPACK_SOURCE_OUTPUT_CONFIG_FILE - "${CMAKE_BINARY_DIR}/CPackSourceConfig.cmake") - -_cpack_set_default(CPACK_SET_DESTDIR OFF) -_cpack_set_default(CPACK_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}") - -_cpack_set_default(CPACK_NSIS_INSTALLER_ICON_CODE "") -_cpack_set_default(CPACK_NSIS_INSTALLER_MUI_ICON_CODE "") - -# WiX specific variables -_cpack_set_default(CPACK_WIX_SIZEOF_VOID_P "${CMAKE_SIZEOF_VOID_P}") - -# set sysroot so SDK tools can be used -if(CMAKE_OSX_SYSROOT) - _cpack_set_default(CPACK_OSX_SYSROOT "${_CMAKE_OSX_SYSROOT_PATH}") -endif() - -_cpack_set_default(CPACK_BUILD_SOURCE_DIRS "${CMAKE_SOURCE_DIR};${CMAKE_BINARY_DIR}") - -if(DEFINED CPACK_COMPONENTS_ALL) - if(CPACK_MONOLITHIC_INSTALL) - message("CPack warning: both CPACK_COMPONENTS_ALL and CPACK_MONOLITHIC_INSTALL have been set.\nDefaulting to a monolithic installation.") - set(CPACK_COMPONENTS_ALL) - else() - # The user has provided the set of components to be installed as - # part of a component-based installation; trust her. - set(CPACK_COMPONENTS_ALL_SET_BY_USER TRUE) - endif() -else() - # If the user has not specifically requested a monolithic installer - # but has specified components in various "install" commands, tell - # CPack about those components. - if(NOT CPACK_MONOLITHIC_INSTALL) - get_cmake_property(CPACK_COMPONENTS_ALL COMPONENTS) - list(LENGTH CPACK_COMPONENTS_ALL CPACK_COMPONENTS_LEN) - if(CPACK_COMPONENTS_LEN EQUAL 1) - # Only one component: this is not a component-based installation - # (at least, it isn't a component-based installation, but may - # become one later if the user uses the cpack_add_* commands). - set(CPACK_COMPONENTS_ALL) - endif() - set(CPACK_COMPONENTS_LEN) - endif() -endif() - -# CMake always generates a component named "Unspecified", which is -# used to install everything that doesn't have an explicitly-provided -# component. Since these files should always be installed, we'll make -# them hidden and required. -set(CPACK_COMPONENT_UNSPECIFIED_HIDDEN TRUE) -set(CPACK_COMPONENT_UNSPECIFIED_REQUIRED TRUE) - -cpack_encode_variables() -configure_file("${cpack_input_file}" "${CPACK_OUTPUT_CONFIG_FILE}" @ONLY) - -# Generate source file -_cpack_set_default(CPACK_SOURCE_INSTALLED_DIRECTORIES - "${CMAKE_SOURCE_DIR};/") -_cpack_set_default(CPACK_SOURCE_TOPLEVEL_TAG "${CPACK_SYSTEM_NAME}-Source") -_cpack_set_default(CPACK_SOURCE_PACKAGE_FILE_NAME - "${CPACK_PACKAGE_NAME}-${CPACK_PACKAGE_VERSION}-Source") - -set(__cpack_source_ignore_files_default - "/CVS/;/\\.svn/;/\\.bzr/;/\\.hg/;/\\.git/;\\.swp$;\\.#;/#") -if(NOT CPACK_VERBATIM_VARIABLES) - _cpack_escape_for_cmake(__cpack_source_ignore_files_default - "${__cpack_source_ignore_files_default}") -endif() -_cpack_set_default(CPACK_SOURCE_IGNORE_FILES "${__cpack_source_ignore_files_default}") - -set(CPACK_INSTALL_CMAKE_PROJECTS "${CPACK_SOURCE_INSTALL_CMAKE_PROJECTS}") -set(CPACK_INSTALLED_DIRECTORIES "${CPACK_SOURCE_INSTALLED_DIRECTORIES}") -set(CPACK_GENERATOR "${CPACK_SOURCE_GENERATOR}") -set(CPACK_TOPLEVEL_TAG "${CPACK_SOURCE_TOPLEVEL_TAG}") -set(CPACK_PACKAGE_FILE_NAME "${CPACK_SOURCE_PACKAGE_FILE_NAME}") -set(CPACK_IGNORE_FILES "${CPACK_SOURCE_IGNORE_FILES}") -set(CPACK_STRIP_FILES "${CPACK_SOURCE_STRIP_FILES}") - -set(CPACK_RPM_PACKAGE_SOURCES "ON") - -cpack_encode_variables() -configure_file("${cpack_source_input_file}" - "${CPACK_SOURCE_OUTPUT_CONFIG_FILE}" @ONLY)
diff --git a/share/cmake-3.18/Modules/CPackIFW.cmake b/share/cmake-3.18/Modules/CPackIFW.cmake deleted file mode 100644 index 80a907f..0000000 --- a/share/cmake-3.18/Modules/CPackIFW.cmake +++ /dev/null
@@ -1,739 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CPackIFW --------- - -This module looks for the location of the command-line utilities supplied with the -`Qt Installer Framework <http://doc.qt.io/qtinstallerframework/index.html>`_ -(QtIFW). - -The module also defines several commands to control the behavior of the -:cpack_gen:`CPack IFW Generator`. - -Commands -^^^^^^^^ - -The module defines the following commands: - -.. command:: cpack_ifw_configure_component - - Sets the arguments specific to the CPack IFW generator. - - :: - - cpack_ifw_configure_component(<compname> [COMMON] [ESSENTIAL] [VIRTUAL] - [FORCED_INSTALLATION] [REQUIRES_ADMIN_RIGHTS] - [NAME <name>] - [DISPLAY_NAME <display_name>] # Note: Internationalization supported - [DESCRIPTION <description>] # Note: Internationalization supported - [UPDATE_TEXT <update_text>] - [VERSION <version>] - [RELEASE_DATE <release_date>] - [SCRIPT <script>] - [PRIORITY|SORTING_PRIORITY <sorting_priority>] # Note: PRIORITY is deprecated - [DEPENDS|DEPENDENCIES <com_id> ...] - [AUTO_DEPEND_ON <comp_id> ...] - [LICENSES <display_name> <file_path> ...] - [DEFAULT <value>] - [USER_INTERFACES <file_path> <file_path> ...] - [TRANSLATIONS <file_path> <file_path> ...] - [REPLACES <comp_id> ...] - [CHECKABLE <value>]) - - This command should be called after :command:`cpack_add_component` command. - - ``COMMON`` - if set, then the component will be packaged and installed as part - of a group to which it belongs. - - ``ESSENTIAL`` - if set, then the package manager stays disabled until that - component is updated. - - ``VIRTUAL`` - if set, then the component will be hidden from the installer. - It is a equivalent of the ``HIDDEN`` option from the - :command:`cpack_add_component` command. - - ``FORCED_INSTALLATION`` - if set, then the component must always be installed. - It is a equivalent of the ``REQUIRED`` option from the - :command:`cpack_add_component` command. - - ``REQUIRES_ADMIN_RIGHTS`` - set it if the component needs to be installed with elevated permissions. - - ``NAME`` - is used to create domain-like identification for this component. - By default used origin component name. - - ``DISPLAY_NAME`` - set to rewrite original name configured by - :command:`cpack_add_component` command. - - ``DESCRIPTION`` - set to rewrite original description configured by - :command:`cpack_add_component` command. - - ``UPDATE_TEXT`` - will be added to the component description if this is an update to - the component. - - ``VERSION`` - is version of component. - By default used :variable:`CPACK_PACKAGE_VERSION`. - - ``RELEASE_DATE`` - keep empty to auto generate. - - ``SCRIPT`` - is a relative or absolute path to operations script - for this component. - - ``PRIORITY`` | ``SORTING_PRIORITY`` - is priority of the component in the tree. - The ``PRIORITY`` option is deprecated and will be removed in a future - version of CMake. Please use ``SORTING_PRIORITY`` option instead. - - ``DEPENDS`` | ``DEPENDENCIES`` - list of dependency component or component group identifiers in - QtIFW style. - - ``AUTO_DEPEND_ON`` - list of identifiers of component or component group in QtIFW style - that this component has an automatic dependency on. - - ``LICENSES`` - pair of <display_name> and <file_path> of license text for this - component. You can specify more then one license. - - ``DEFAULT`` - Possible values are: TRUE, FALSE, and SCRIPT. - Set to FALSE to disable the component in the installer or to SCRIPT - to resolved during runtime (don't forget add the file of the script - as a value of the ``SCRIPT`` option). - - ``USER_INTERFACES`` - is a list of <file_path> ('.ui' files) representing pages to load. - - ``TRANSLATIONS`` - is a list of <file_path> ('.qm' files) representing translations to load. - - ``REPLACES`` - list of identifiers of component or component group to replace. - - ``CHECKABLE`` - Possible values are: TRUE, FALSE. - Set to FALSE if you want to hide the checkbox for an item. - This is useful when only a few subcomponents should be selected - instead of all. - - -.. command:: cpack_ifw_configure_component_group - - Sets the arguments specific to the CPack IFW generator. - - :: - - cpack_ifw_configure_component_group(<groupname> [VIRTUAL] - [FORCED_INSTALLATION] [REQUIRES_ADMIN_RIGHTS] - [NAME <name>] - [DISPLAY_NAME <display_name>] # Note: Internationalization supported - [DESCRIPTION <description>] # Note: Internationalization supported - [UPDATE_TEXT <update_text>] - [VERSION <version>] - [RELEASE_DATE <release_date>] - [SCRIPT <script>] - [PRIORITY|SORTING_PRIORITY <sorting_priority>] # Note: PRIORITY is deprecated - [DEPENDS|DEPENDENCIES <com_id> ...] - [AUTO_DEPEND_ON <comp_id> ...] - [LICENSES <display_name> <file_path> ...] - [DEFAULT <value>] - [USER_INTERFACES <file_path> <file_path> ...] - [TRANSLATIONS <file_path> <file_path> ...] - [REPLACES <comp_id> ...] - [CHECKABLE <value>]) - - This command should be called after :command:`cpack_add_component_group` - command. - - ``VIRTUAL`` - if set, then the group will be hidden from the installer. - Note that setting this on a root component does not work. - - ``FORCED_INSTALLATION`` - if set, then the group must always be installed. - - ``REQUIRES_ADMIN_RIGHTS`` - set it if the component group needs to be installed with elevated - permissions. - - ``NAME`` - is used to create domain-like identification for this component group. - By default used origin component group name. - - ``DISPLAY_NAME`` - set to rewrite original name configured by - :command:`cpack_add_component_group` command. - - ``DESCRIPTION`` - set to rewrite original description configured by - :command:`cpack_add_component_group` command. - - ``UPDATE_TEXT`` - will be added to the component group description if this is an update to - the component group. - - ``VERSION`` - is version of component group. - By default used :variable:`CPACK_PACKAGE_VERSION`. - - ``RELEASE_DATE`` - keep empty to auto generate. - - ``SCRIPT`` - is a relative or absolute path to operations script - for this component group. - - ``PRIORITY`` | ``SORTING_PRIORITY`` - is priority of the component group in the tree. - The ``PRIORITY`` option is deprecated and will be removed in a future - version of CMake. Please use ``SORTING_PRIORITY`` option instead. - - ``DEPENDS`` | ``DEPENDENCIES`` - list of dependency component or component group identifiers in - QtIFW style. - - ``AUTO_DEPEND_ON`` - list of identifiers of component or component group in QtIFW style - that this component group has an automatic dependency on. - - ``LICENSES`` - pair of <display_name> and <file_path> of license text for this - component group. You can specify more then one license. - - ``DEFAULT`` - Possible values are: TRUE, FALSE, and SCRIPT. - Set to TRUE to preselect the group in the installer - (this takes effect only on groups that have no visible child components) - or to SCRIPT to resolved during runtime (don't forget add the file of - the script as a value of the ``SCRIPT`` option). - - ``USER_INTERFACES`` - is a list of <file_path> ('.ui' files) representing pages to load. - - ``TRANSLATIONS`` - is a list of <file_path> ('.qm' files) representing translations to load. - - ``REPLACES`` - list of identifiers of component or component group to replace. - - ``CHECKABLE`` - Possible values are: TRUE, FALSE. - Set to FALSE if you want to hide the checkbox for an item. - This is useful when only a few subcomponents should be selected - instead of all. - - -.. command:: cpack_ifw_add_repository - - Add QtIFW specific remote repository to binary installer. - - :: - - cpack_ifw_add_repository(<reponame> [DISABLED] - URL <url> - [USERNAME <username>] - [PASSWORD <password>] - [DISPLAY_NAME <display_name>]) - - This command will also add the <reponame> repository - to a variable :variable:`CPACK_IFW_REPOSITORIES_ALL`. - - ``DISABLED`` - if set, then the repository will be disabled by default. - - ``URL`` - is points to a list of available components. - - ``USERNAME`` - is used as user on a protected repository. - - ``PASSWORD`` - is password to use on a protected repository. - - ``DISPLAY_NAME`` - is string to display instead of the URL. - - -.. command:: cpack_ifw_update_repository - - Update QtIFW specific repository from remote repository. - - :: - - cpack_ifw_update_repository(<reponame> - [[ADD|REMOVE] URL <url>]| - [REPLACE OLD_URL <old_url> NEW_URL <new_url>]] - [USERNAME <username>] - [PASSWORD <password>] - [DISPLAY_NAME <display_name>]) - - This command will also add the <reponame> repository - to a variable :variable:`CPACK_IFW_REPOSITORIES_ALL`. - - ``URL`` - is points to a list of available components. - - ``OLD_URL`` - is points to a list that will replaced. - - ``NEW_URL`` - is points to a list that will replace to. - - ``USERNAME`` - is used as user on a protected repository. - - ``PASSWORD`` - is password to use on a protected repository. - - ``DISPLAY_NAME`` - is string to display instead of the URL. - - -.. command:: cpack_ifw_add_package_resources - - Add additional resources in the installer binary. - - :: - - cpack_ifw_add_package_resources(<file_path> <file_path> ...) - - This command will also add the specified files - to a variable :variable:`CPACK_IFW_PACKAGE_RESOURCES`. - -#]=======================================================================] - -# TODO: -# All of the internal implementation CMake modules for other CPack generators -# have been moved into the Internal/CPack directory. This one has not, because -# it contains user-facing macros which would be lost if it were moved. At some -# point, this module should be split into user-facing macros (which would live -# in this module) and internal implementation details (which would live in -# Internal/CPack/CPackIFW.cmake). - -#============================================================================= -# Search Qt Installer Framework tools -#============================================================================= - -# Default path - -foreach(_CPACK_IFW_PATH_VAR "CPACK_IFW_ROOT" "QTIFWDIR" "QTDIR") - if(DEFINED ${_CPACK_IFW_PATH_VAR} - AND NOT "${${_CPACK_IFW_PATH_VAR}}" STREQUAL "") - list(APPEND _CPACK_IFW_PATHS "${${_CPACK_IFW_PATH_VAR}}") - endif() - if(NOT "$ENV{${_CPACK_IFW_PATH_VAR}}" STREQUAL "") - list(APPEND _CPACK_IFW_PATHS "$ENV{${_CPACK_IFW_PATH_VAR}}") - endif() -endforeach() -if(WIN32) - list(APPEND _CPACK_IFW_PATHS - "$ENV{HOMEDRIVE}/Qt" - "C:/Qt") -else() - list(APPEND _CPACK_IFW_PATHS - "$ENV{HOME}/Qt" - "/opt/Qt") -endif() -list(REMOVE_DUPLICATES _CPACK_IFW_PATHS) - -set(_CPACK_IFW_PREFIXES - # QtSDK - "Tools/QtInstallerFramework/" - # Second branch - "QtIFW" - # First branch - "QtIFW-") - -set(_CPACK_IFW_VERSIONS - "3.2" - "3.2.0" - "3.1" - "3.1.0" - "3.0" - "3.0.0" - "2.3" - "2.3.0" - "2.2" - "2.2.0" - "2.1" - "2.1.0" - "2.0" - "2.0.5" - "2.0.3" - "2.0.2" - "2.0.1" - "2.0.0" - "1.6" - "1.6.0" - "1.5" - "1.5.0" - "1.4" - "1.4.0" - "1.3" - "1.3.0") - -set(_CPACK_IFW_SUFFIXES "bin") -foreach(_CPACK_IFW_PREFIX ${_CPACK_IFW_PREFIXES}) - foreach(_CPACK_IFW_VERSION ${_CPACK_IFW_VERSIONS}) - list(APPEND - _CPACK_IFW_SUFFIXES "${_CPACK_IFW_PREFIX}${_CPACK_IFW_VERSION}/bin") - endforeach() -endforeach() - -# Look for 'binarycreator' - -find_program(CPACK_IFW_BINARYCREATOR_EXECUTABLE - NAMES binarycreator - PATHS ${_CPACK_IFW_PATHS} - PATH_SUFFIXES ${_CPACK_IFW_SUFFIXES} - DOC "QtIFW binarycreator command line client") - -mark_as_advanced(CPACK_IFW_BINARYCREATOR_EXECUTABLE) - -# Look for 'repogen' - -find_program(CPACK_IFW_REPOGEN_EXECUTABLE - NAMES repogen - PATHS ${_CPACK_IFW_PATHS} - PATH_SUFFIXES ${_CPACK_IFW_SUFFIXES} - DOC "QtIFW repogen command line client" - ) -mark_as_advanced(CPACK_IFW_REPOGEN_EXECUTABLE) - -# Look for 'installerbase' - -find_program(CPACK_IFW_INSTALLERBASE_EXECUTABLE - NAMES installerbase - PATHS ${_CPACK_IFW_PATHS} - PATH_SUFFIXES ${_CPACK_IFW_SUFFIXES} - DOC "QtIFW installer executable base" - ) -mark_as_advanced(CPACK_IFW_INSTALLERBASE_EXECUTABLE) - -# Look for 'devtool' (appeared in the second branch) - -find_program(CPACK_IFW_DEVTOOL_EXECUTABLE - NAMES devtool - PATHS ${_CPACK_IFW_PATHS} - PATH_SUFFIXES ${_CPACK_IFW_SUFFIXES} - DOC "QtIFW devtool command line client" - ) -mark_as_advanced(CPACK_IFW_DEVTOOL_EXECUTABLE) - -# -## Next code is included only once -# - -if(NOT CPackIFW_CMake_INCLUDED) -set(CPackIFW_CMake_INCLUDED 1) - -#============================================================================= -# Framework version -#============================================================================= - -set(CPACK_IFW_FRAMEWORK_VERSION_FORCED "" - CACHE STRING "The forced version of used QtIFW tools") -mark_as_advanced(CPACK_IFW_FRAMEWORK_VERSION_FORCED) -set(CPACK_IFW_FRAMEWORK_VERSION_TIMEOUT 1 - CACHE STRING "The timeout to return QtIFW framework version string from \"installerbase\" executable") -mark_as_advanced(CPACK_IFW_FRAMEWORK_VERSION_TIMEOUT) -if(CPACK_IFW_INSTALLERBASE_EXECUTABLE AND NOT CPACK_IFW_FRAMEWORK_VERSION_FORCED) - set(CPACK_IFW_FRAMEWORK_VERSION) - # Invoke version from "installerbase" executable - foreach(_ifw_version_argument --framework-version --version) - if(NOT CPACK_IFW_FRAMEWORK_VERSION) - execute_process(COMMAND - "${CPACK_IFW_INSTALLERBASE_EXECUTABLE}" ${_ifw_version_argument} - TIMEOUT ${CPACK_IFW_FRAMEWORK_VERSION_TIMEOUT} - RESULT_VARIABLE CPACK_IFW_FRAMEWORK_VERSION_RESULT - OUTPUT_VARIABLE CPACK_IFW_FRAMEWORK_VERSION_OUTPUT - OUTPUT_STRIP_TRAILING_WHITESPACE - ENCODING UTF8) - if(NOT CPACK_IFW_FRAMEWORK_VERSION_RESULT AND CPACK_IFW_FRAMEWORK_VERSION_OUTPUT) - string(REGEX MATCH "[0-9]+(\\.[0-9]+)*" - CPACK_IFW_FRAMEWORK_VERSION "${CPACK_IFW_FRAMEWORK_VERSION_OUTPUT}") - if(CPACK_IFW_FRAMEWORK_VERSION) - if("${_ifw_version_argument}" STREQUAL "--framework-version") - set(CPACK_IFW_FRAMEWORK_VERSION_SOURCE "INSTALLERBASE_FRAMEWORK_VERSION") - elseif("${_ifw_version_argument}" STREQUAL "--version") - set(CPACK_IFW_FRAMEWORK_VERSION_SOURCE "INSTALLERBASE_FRAMEWORK_VERSION") - endif() - endif() - endif() - endif() - endforeach() - # Finally try to get version from executable path - if(NOT CPACK_IFW_FRAMEWORK_VERSION) - string(REGEX MATCH "[0-9]+(\\.[0-9]+)*" - CPACK_IFW_FRAMEWORK_VERSION "${CPACK_IFW_INSTALLERBASE_EXECUTABLE}") - if(CPACK_IFW_FRAMEWORK_VERSION) - set(CPACK_IFW_FRAMEWORK_VERSION_SOURCE "INSTALLERBASE_PATH") - endif() - endif() -elseif(CPACK_IFW_FRAMEWORK_VERSION_FORCED) - set(CPACK_IFW_FRAMEWORK_VERSION ${CPACK_IFW_FRAMEWORK_VERSION_FORCED}) - set(CPACK_IFW_FRAMEWORK_VERSION_SOURCE "FORCED") -endif() -if(CPACK_IFW_VERBOSE) - if(CPACK_IFW_FRAMEWORK_VERSION AND CPACK_IFW_FRAMEWORK_VERSION_FORCED) - message(STATUS "Found QtIFW ${CPACK_IFW_FRAMEWORK_VERSION} (forced) version") - elseif(CPACK_IFW_FRAMEWORK_VERSION) - message(STATUS "Found QtIFW ${CPACK_IFW_FRAMEWORK_VERSION} version") - endif() -endif() -if(CPACK_IFW_INSTALLERBASE_EXECUTABLE AND NOT CPACK_IFW_FRAMEWORK_VERSION) - message(WARNING "Could not detect QtIFW tools version. Set used version to variable \"CPACK_IFW_FRAMEWORK_VERSION_FORCED\" manually.") -endif() - -#============================================================================= -# Macro definition -#============================================================================= - -# Macro definition based on CPackComponent - -if(NOT CPackComponent_CMake_INCLUDED) - include(CPackComponent) -endif() - -# Resolve full filename for script file -macro(_cpack_ifw_resolve_script _variable) - set(_ifw_script_macro ${_variable}) - set(_ifw_script_file ${${_ifw_script_macro}}) - if(DEFINED ${_ifw_script_macro}) - get_filename_component(${_ifw_script_macro} ${_ifw_script_file} ABSOLUTE) - set(_ifw_script_file ${${_ifw_script_macro}}) - if(NOT EXISTS ${_ifw_script_file}) - message(WARNING "CPack IFW: script file \"${_ifw_script_file}\" does not exist") - set(${_ifw_script_macro}) - endif() - endif() -endmacro() - -# Resolve full path to license file -macro(_cpack_ifw_resolve_lisenses _variable) - if(${_variable}) - set(_ifw_license_file FALSE) - set(_ifw_licenses_fix) - foreach(_ifw_licenses_arg ${${_variable}}) - if(_ifw_license_file) - get_filename_component(_ifw_licenses_arg "${_ifw_licenses_arg}" ABSOLUTE) - set(_ifw_license_file FALSE) - else() - set(_ifw_license_file TRUE) - endif() - list(APPEND _ifw_licenses_fix "${_ifw_licenses_arg}") - endforeach(_ifw_licenses_arg) - set(${_variable} "${_ifw_licenses_fix}") - endif() -endmacro() - -# Resolve full path to a list of provided files -macro(_cpack_ifw_resolve_file_list _variable) - if(${_variable}) - set(_ifw_list_fix) - foreach(_ifw_file_arg ${${_variable}}) - get_filename_component(_ifw_file_arg "${_ifw_file_arg}" ABSOLUTE) - if(EXISTS ${_ifw_file_arg}) - list(APPEND _ifw_list_fix "${_ifw_file_arg}") - else() - message(WARNING "CPack IFW: page file \"${_ifw_file_arg}\" does not exist. Skipping") - endif() - endforeach(_ifw_file_arg) - set(${_variable} "${_ifw_list_fix}") - endif() -endmacro() - -# Macro for configure component -macro(cpack_ifw_configure_component compname) - - string(TOUPPER ${compname} _CPACK_IFWCOMP_UNAME) - - set(_IFW_OPT COMMON ESSENTIAL VIRTUAL FORCED_INSTALLATION REQUIRES_ADMIN_RIGHTS) - set(_IFW_ARGS NAME VERSION RELEASE_DATE SCRIPT PRIORITY SORTING_PRIORITY UPDATE_TEXT DEFAULT CHECKABLE) - set(_IFW_MULTI_ARGS DISPLAY_NAME DESCRIPTION DEPENDS DEPENDENCIES AUTO_DEPEND_ON LICENSES USER_INTERFACES TRANSLATIONS REPLACES) - cmake_parse_arguments(CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME} "${_IFW_OPT}" "${_IFW_ARGS}" "${_IFW_MULTI_ARGS}" ${ARGN}) - - _cpack_ifw_resolve_script(CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_SCRIPT) - _cpack_ifw_resolve_lisenses(CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_LICENSES) - _cpack_ifw_resolve_file_list(CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_USER_INTERFACES) - _cpack_ifw_resolve_file_list(CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_TRANSLATIONS) - - set(_CPACK_IFWCOMP_STR "\n# Configuration for IFW component \"${compname}\"\n") - - foreach(_IFW_ARG_NAME ${_IFW_OPT}) - cpack_append_option_set_command( - CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWCOMP_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_ARGS}) - cpack_append_string_variable_set_command( - CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWCOMP_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_MULTI_ARGS}) - cpack_append_list_variable_set_command( - CPACK_IFW_COMPONENT_${_CPACK_IFWCOMP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWCOMP_STR) - endforeach() - - if(CPack_CMake_INCLUDED) - file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_IFWCOMP_STR}") - endif() - -endmacro() - -# Macro for configure group -macro(cpack_ifw_configure_component_group grpname) - - string(TOUPPER ${grpname} _CPACK_IFWGRP_UNAME) - - set(_IFW_OPT VIRTUAL FORCED_INSTALLATION REQUIRES_ADMIN_RIGHTS) - set(_IFW_ARGS NAME VERSION RELEASE_DATE SCRIPT PRIORITY SORTING_PRIORITY UPDATE_TEXT DEFAULT CHECKABLE) - set(_IFW_MULTI_ARGS DISPLAY_NAME DESCRIPTION DEPENDS DEPENDENCIES AUTO_DEPEND_ON LICENSES USER_INTERFACES TRANSLATIONS REPLACES) - cmake_parse_arguments(CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME} "${_IFW_OPT}" "${_IFW_ARGS}" "${_IFW_MULTI_ARGS}" ${ARGN}) - - _cpack_ifw_resolve_script(CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_SCRIPT) - _cpack_ifw_resolve_lisenses(CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_LICENSES) - _cpack_ifw_resolve_file_list(CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_USER_INTERFACES) - _cpack_ifw_resolve_file_list(CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_TRANSLATIONS) - - set(_CPACK_IFWGRP_STR "\n# Configuration for IFW component group \"${grpname}\"\n") - - foreach(_IFW_ARG_NAME ${_IFW_OPT}) - cpack_append_option_set_command( - CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWGRP_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_ARGS}) - cpack_append_string_variable_set_command( - CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWGRP_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_MULTI_ARGS}) - cpack_append_list_variable_set_command( - CPACK_IFW_COMPONENT_GROUP_${_CPACK_IFWGRP_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWGRP_STR) - endforeach() - - if(CPack_CMake_INCLUDED) - file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_IFWGRP_STR}") - endif() -endmacro() - -# Macro for adding repository -macro(cpack_ifw_add_repository reponame) - - string(TOUPPER ${reponame} _CPACK_IFWREPO_UNAME) - - set(_IFW_OPT DISABLED) - set(_IFW_ARGS URL USERNAME PASSWORD DISPLAY_NAME) - set(_IFW_MULTI_ARGS) - cmake_parse_arguments(CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME} "${_IFW_OPT}" "${_IFW_ARGS}" "${_IFW_MULTI_ARGS}" ${ARGN}) - - set(_CPACK_IFWREPO_STR "\n# Configuration for IFW repository \"${reponame}\"\n") - - foreach(_IFW_ARG_NAME ${_IFW_OPT}) - cpack_append_option_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_ARGS}) - cpack_append_string_variable_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_MULTI_ARGS}) - cpack_append_variable_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - list(APPEND CPACK_IFW_REPOSITORIES_ALL ${reponame}) - string(APPEND _CPACK_IFWREPO_STR "list(APPEND CPACK_IFW_REPOSITORIES_ALL ${reponame})\n") - - if(CPack_CMake_INCLUDED) - file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_IFWREPO_STR}") - endif() - -endmacro() - -# Macro for updating repository -macro(cpack_ifw_update_repository reponame) - - string(TOUPPER ${reponame} _CPACK_IFWREPO_UNAME) - - set(_IFW_OPT ADD REMOVE REPLACE DISABLED) - set(_IFW_ARGS URL OLD_URL NEW_URL USERNAME PASSWORD DISPLAY_NAME) - set(_IFW_MULTI_ARGS) - cmake_parse_arguments(CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME} "${_IFW_OPT}" "${_IFW_ARGS}" "${_IFW_MULTI_ARGS}" ${ARGN}) - - set(_CPACK_IFWREPO_STR "\n# Configuration for IFW repository \"${reponame}\" update\n") - - foreach(_IFW_ARG_NAME ${_IFW_OPT}) - cpack_append_option_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_ARGS}) - cpack_append_string_variable_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - foreach(_IFW_ARG_NAME ${_IFW_MULTI_ARGS}) - cpack_append_variable_set_command( - CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_${_IFW_ARG_NAME} - _CPACK_IFWREPO_STR) - endforeach() - - if(CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_ADD - OR CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_REMOVE - OR CPACK_IFW_REPOSITORY_${_CPACK_IFWREPO_UNAME}_REPLACE) - list(APPEND CPACK_IFW_REPOSITORIES_ALL ${reponame}) - string(APPEND _CPACK_IFWREPO_STR "list(APPEND CPACK_IFW_REPOSITORIES_ALL ${reponame})\n") - else() - set(_CPACK_IFWREPO_STR) - endif() - - if(CPack_CMake_INCLUDED AND _CPACK_IFWREPO_STR) - file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_IFWREPO_STR}") - endif() - -endmacro() - -# Macro for adding resources -macro(cpack_ifw_add_package_resources) - set(_CPACK_IFW_PACKAGE_RESOURCES ${ARGV}) - _cpack_ifw_resolve_file_list(_CPACK_IFW_PACKAGE_RESOURCES) - list(APPEND CPACK_IFW_PACKAGE_RESOURCES ${_CPACK_IFW_PACKAGE_RESOURCES}) - set(_CPACK_IFWQRC_STR "list(APPEND CPACK_IFW_PACKAGE_RESOURCES \"${_CPACK_IFW_PACKAGE_RESOURCES}\")\n") - if(CPack_CMake_INCLUDED) - file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_IFWQRC_STR}") - endif() -endmacro() - -# Resolve package control script -_cpack_ifw_resolve_script(CPACK_IFW_PACKAGE_CONTROL_SCRIPT) - -endif() # NOT CPackIFW_CMake_INCLUDED
diff --git a/share/cmake-3.18/Modules/CPackIFWConfigureFile.cmake b/share/cmake-3.18/Modules/CPackIFWConfigureFile.cmake deleted file mode 100644 index 0abe0da..0000000 --- a/share/cmake-3.18/Modules/CPackIFWConfigureFile.cmake +++ /dev/null
@@ -1,66 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CPackIFWConfigureFile ---------------------- - -The module defines :command:`configure_file` similar command to -configure file templates prepared in QtIFW/SDK/Creator style. - - -Commands -^^^^^^^^ - -The module defines the following commands: - -.. command:: cpack_ifw_configure_file - - Copy a file to another location and modify its contents. - - :: - - cpack_ifw_configure_file(<input> <output>) - - Copies an ``<input>`` file to an ``<output>`` file and substitutes variable - values referenced as ``%{VAR}`` or ``%VAR%`` in the input file content. - Each variable reference will be replaced with the current value of the - variable, or the empty string if the variable is not defined. - -#]=======================================================================] - -# NOTE: This file used to himself packaging via CPack IFW generator and -# should be compatible with minimal CMake version defined in -# ../CMakeLists.txt file. - -if(NOT DEFINED CPackIFWConfigureFile_CMake_INCLUDED) -set(CPackIFWConfigureFile_CMake_INCLUDED 1) - -macro(cpack_ifw_configure_file INPUT OUTPUT) - file(READ "${INPUT}" _tmp) - foreach(_tmp_regex "%{([^%}]+)}" "%([^%]+)%") - string(REGEX MATCHALL "${_tmp_regex}" _tmp_vars "${_tmp}") - while(_tmp_vars) - foreach(_tmp_var ${_tmp_vars}) - string(REGEX REPLACE "${_tmp_regex}" "\\1" - _tmp_var_name "${_tmp_var}") - if(DEFINED ${_tmp_var_name}) - set(_tmp_var_value "${${_tmp_var_name}}") - elseif(NOT "$ENV{${_tmp_var_name}}" STREQUAL "") - set(_tmp_var_value "$ENV{${_tmp_var_name}}") - else() - set(_tmp_var_value "") - endif() - string(REPLACE "${_tmp_var}" "${_tmp_var_value}" _tmp "${_tmp}") - endforeach() - string(REGEX MATCHALL "${_tmp_regex}" _tmp_vars "${_tmp}") - endwhile() - endforeach() - if(IS_ABSOLUTE "${OUTPUT}") - file(WRITE "${OUTPUT}" "${_tmp}") - else() - file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/${OUTPUT}" "${_tmp}") - endif() -endmacro() - -endif() # NOT DEFINED CPackIFWConfigureFile_CMake_INCLUDED
diff --git a/share/cmake-3.18/Modules/CSharpUtilities.cmake b/share/cmake-3.18/Modules/CSharpUtilities.cmake deleted file mode 100644 index 6a4b5c7..0000000 --- a/share/cmake-3.18/Modules/CSharpUtilities.cmake +++ /dev/null
@@ -1,311 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CSharpUtilities ---------------- - -Functions to make configuration of CSharp/.NET targets easier. - -A collection of CMake utility functions useful for dealing with CSharp -targets for Visual Studio generators from version 2010 and later. - -The following functions are provided by this module: - -**Main functions** - -- :command:`csharp_set_windows_forms_properties` -- :command:`csharp_set_designer_cs_properties` -- :command:`csharp_set_xaml_cs_properties` - -**Helper functions** - -- :command:`csharp_get_filename_keys` -- :command:`csharp_get_filename_key_base` -- :command:`csharp_get_dependentupon_name` - -Main functions provided by the module -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. command:: csharp_set_windows_forms_properties - - Sets source file properties for use of Windows Forms. Use this, if your CSharp - target uses Windows Forms:: - - csharp_set_windows_forms_properties([<file1> [<file2> [...]]]) - - ``<fileN>`` - List of all source files which are relevant for setting the - :prop_sf:`VS_CSHARP_<tagname>` properties (including ``.cs``, ``.resx`` and - ``.Designer.cs`` extensions). - - In the list of all given files for all files ending with ``.Designer.cs`` and - ``.resx`` is searched. For every *designer* or *resource* file a file with the - same base name but only ``.cs`` as extension is searched. If this is found, the - :prop_sf:`VS_CSHARP_<tagname>` properties are set as follows: - - for the **.cs** file: - - VS_CSHARP_SubType "Form" - - for the **.Designer.cs** file (if it exists): - - VS_CSHARP_DependentUpon <cs-filename> - - VS_CSHARP_DesignTime "" (delete tag if previously defined) - - VS_CSHARP_AutoGen ""(delete tag if previously defined) - - for the **.resx** file (if it exists): - - VS_RESOURCE_GENERATOR "" (delete tag if previously defined) - - VS_CSHARP_DependentUpon <cs-filename> - - VS_CSHARP_SubType "Designer" - -.. command:: csharp_set_designer_cs_properties - - Sets source file properties of ``.Designer.cs`` files depending on - sibling filenames. Use this, if your CSharp target does **not** - use Windows Forms (for Windows Forms use - :command:`csharp_set_designer_cs_properties` instead):: - - csharp_set_designer_cs_properties([<file1> [<file2> [...]]]) - - ``<fileN>`` - List of all source files which are relevant for setting the - :prop_sf:`VS_CSHARP_<tagname>` properties (including ``.cs``, - ``.resx``, ``.settings`` and ``.Designer.cs`` extensions). - - In the list of all given files for all files ending with - ``.Designer.cs`` is searched. For every *designer* file all files - with the same base name but different extensions are searched. If - a match is found, the source file properties of the *designer* file - are set depending on the extension of the matched file: - - if match is **.resx** file: - - VS_CSHARP_AutoGen "True" - - VS_CSHARP_DesignTime "True" - - VS_CSHARP_DependentUpon <resx-filename> - - if match is **.cs** file: - - VS_CSHARP_DependentUpon <cs-filename> - - if match is **.settings** file: - - VS_CSHARP_AutoGen "True" - - VS_CSHARP_DesignTimeSharedInput "True" - - VS_CSHARP_DependentUpon <settings-filename> - -.. note:: - - Because the source file properties of the ``.Designer.cs`` file are set according - to the found matches and every match sets the **VS_CSHARP_DependentUpon** - property, there should only be one match for each ``Designer.cs`` file. - -.. command:: csharp_set_xaml_cs_properties - - Sets source file properties for use of Windows Presentation Foundation (WPF) and - XAML. Use this, if your CSharp target uses WPF/XAML:: - - csharp_set_xaml_cs_properties([<file1> [<file2> [...]]]) - - ``<fileN>`` - List of all source files which are relevant for setting the - :prop_sf:`VS_CSHARP_<tagname>` properties (including ``.cs``, - ``.xaml``, and ``.xaml.cs`` extensions). - - In the list of all given files for all files ending with - ``.xaml.cs`` is searched. For every *xaml-cs* file, a file - with the same base name but extension ``.xaml`` is searched. - If a match is found, the source file properties of the ``.xaml.cs`` - file are set: - - - VS_CSHARP_DependentUpon <xaml-filename> - -Helper functions which are used by the above ones -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. command:: csharp_get_filename_keys - - Helper function which computes a list of key values to identify - source files independently of relative/absolute paths given in cmake - and eliminates case sensitivity:: - - csharp_get_filename_keys(OUT [<file1> [<file2> [...]]]) - - ``OUT`` - Name of the variable in which the list of keys is stored - - ``<fileN>`` - filename(s) as given to to CSharp target using :command:`add_library` - or :command:`add_executable` - - In some way the function applies a canonicalization to the source names. - This is necessary to find file matches if the files have been added to - the target with different directory prefixes: - - .. code-block:: cmake - - add_library(lib - myfile.cs - ${CMAKE_CURRENT_SOURCE_DIR}/myfile.Designer.cs) - - set_source_files_properties(myfile.Designer.cs PROPERTIES - VS_CSHARP_DependentUpon myfile.cs) - - # this will fail, because in cmake - # - ${CMAKE_CURRENT_SOURCE_DIR}/myfile.Designer.cs - # - myfile.Designer.cs - # are not the same source file. The source file property is not set. - -.. command:: csharp_get_filename_key_base - - Returns the full filepath and name **without** extension of a key. - KEY is expected to be a key from csharp_get_filename_keys. In BASE - the value of KEY without the file extension is returned:: - - csharp_get_filename_key_base(BASE KEY) - - ``BASE`` - Name of the variable with the computed "base" of ``KEY``. - - ``KEY`` - The key of which the base will be computed. Expected to be a - upper case full filename. - -.. command:: csharp_get_dependentupon_name - - Computes a string which can be used as value for the source file property - :prop_sf:`VS_CSHARP_<tagname>` with *target* being ``DependentUpon``:: - - csharp_get_dependentupon_name(NAME FILE) - - ``NAME`` - Name of the variable with the result value - - ``FILE`` - Filename to convert to ``<DependentUpon>`` value - - Actually this is only the filename without any path given at the moment. - -#]=======================================================================] - -cmake_policy(PUSH) -cmake_policy(SET CMP0057 NEW) # if IN_LIST - -function(csharp_get_filename_keys OUT) - set(${OUT} "") - foreach(f ${ARGN}) - get_filename_component(f ${f} REALPATH) - string(TOUPPER ${f} f) - list(APPEND ${OUT} ${f}) - endforeach() - set(${OUT} "${${OUT}}" PARENT_SCOPE) -endfunction() - -function(csharp_get_filename_key_base base key) - get_filename_component(dir ${key} DIRECTORY) - get_filename_component(fil ${key} NAME_WE) - set(${base} "${dir}/${fil}" PARENT_SCOPE) -endfunction() - -function(csharp_get_dependentupon_name out in) - get_filename_component(${out} ${in} NAME) - set(${out} ${${out}} PARENT_SCOPE) -endfunction() - -function(csharp_set_windows_forms_properties) - csharp_get_filename_keys(fileKeys ${ARGN}) - foreach(key ${fileKeys}) - get_filename_component(ext ${key} EXT) - if(${ext} STREQUAL ".DESIGNER.CS" OR - ${ext} STREQUAL ".RESX") - csharp_get_filename_key_base(NAME_BASE ${key}) - list(FIND fileKeys "${NAME_BASE}.CS" FILE_INDEX) - if(NOT ${FILE_INDEX} EQUAL -1) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - # set properties of main form file - set_source_files_properties("${FILE_NAME}" - PROPERTIES - VS_CSHARP_SubType "Form") - csharp_get_dependentupon_name(LINK "${FILE_NAME}") - # set properties of designer file (if found) - list(FIND fileKeys "${NAME_BASE}.DESIGNER.CS" FILE_INDEX) - if(NOT ${FILE_INDEX} EQUAL -1) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - set_source_files_properties("${FILE_NAME}" - PROPERTIES - VS_CSHARP_DependentUpon "${LINK}" - VS_CSHARP_DesignTime "" - VS_CSHARP_AutoGen "") - endif() - # set properties of corresponding resource file (if found) - list(FIND fileKeys "${NAME_BASE}.RESX" FILE_INDEX) - if(NOT ${FILE_INDEX} EQUAL -1) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - set_source_files_properties("${FILE_NAME}" - PROPERTIES - VS_RESOURCE_GENERATOR "" - VS_CSHARP_DependentUpon "${LINK}" - VS_CSHARP_SubType "Designer") - endif() - endif() - endif() - endforeach() -endfunction() - -function(csharp_set_designer_cs_properties) - csharp_get_filename_keys(fileKeys ${ARGN}) - set(INDEX -1) - foreach(key ${fileKeys}) - math(EXPR INDEX "${INDEX}+1") - list(GET ARGN ${INDEX} source) - get_filename_component(ext ${key} EXT) - if(${ext} STREQUAL ".DESIGNER.CS") - csharp_get_filename_key_base(NAME_BASE ${key}) - if("${NAME_BASE}.RESX" IN_LIST fileKeys) - list(FIND fileKeys "${NAME_BASE}.RESX" FILE_INDEX) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - csharp_get_dependentupon_name(LINK "${FILE_NAME}") - set_source_files_properties("${source}" - PROPERTIES - VS_CSHARP_AutoGen "True" - VS_CSHARP_DesignTime "True" - VS_CSHARP_DependentUpon "${LINK}") - elseif("${NAME_BASE}.CS" IN_LIST fileKeys) - list(FIND fileKeys "${NAME_BASE}.CS" FILE_INDEX) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - csharp_get_dependentupon_name(LINK "${FILE_NAME}") - set_source_files_properties("${source}" - PROPERTIES - VS_CSHARP_DependentUpon "${LINK}") - elseif("${NAME_BASE}.SETTINGS" IN_LIST fileKeys) - list(FIND fileKeys "${NAME_BASE}.SETTINGS" FILE_INDEX) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - csharp_get_dependentupon_name(LINK "${FILE_NAME}") - set_source_files_properties("${source}" - PROPERTIES - VS_CSHARP_AutoGen "True" - VS_CSHARP_DesignTimeSharedInput "True" - VS_CSHARP_DependentUpon "${LINK}") - endif() - endif() - endforeach() -endfunction() - -function(csharp_set_xaml_cs_properties) - csharp_get_filename_keys(fileKeys ${ARGN}) - set(INDEX -1) - foreach(key ${fileKeys}) - math(EXPR INDEX "${INDEX}+1") - list(GET ARGN ${INDEX} source) - get_filename_component(ext ${key} EXT) - if(${ext} STREQUAL ".XAML.CS") - csharp_get_filename_key_base(NAME_BASE ${key}) - if("${NAME_BASE}.XAML" IN_LIST fileKeys) - list(FIND fileKeys "${NAME_BASE}.XAML" FILE_INDEX) - list(GET ARGN ${FILE_INDEX} FILE_NAME) - csharp_get_dependentupon_name(LINK "${FILE_NAME}") - set_source_files_properties("${source}" - PROPERTIES - VS_CSHARP_DependentUpon "${LINK}") - endif() - endif() - endforeach() -endfunction() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CTest.cmake b/share/cmake-3.18/Modules/CTest.cmake deleted file mode 100644 index 8109108..0000000 --- a/share/cmake-3.18/Modules/CTest.cmake +++ /dev/null
@@ -1,269 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CTest ------ - -Configure a project for testing with CTest/CDash - -Include this module in the top CMakeLists.txt file of a project to -enable testing with CTest and dashboard submissions to CDash:: - - project(MyProject) - ... - include(CTest) - -The module automatically creates a ``BUILD_TESTING`` option that selects -whether to enable testing support (``ON`` by default). After including -the module, use code like:: - - if(BUILD_TESTING) - # ... CMake code to create tests ... - endif() - -to creating tests when testing is enabled. - -To enable submissions to a CDash server, create a ``CTestConfig.cmake`` -file at the top of the project with content such as:: - - set(CTEST_NIGHTLY_START_TIME "01:00:00 UTC") - set(CTEST_SUBMIT_URL "http://my.cdash.org/submit.php?project=MyProject") - -(the CDash server can provide the file to a project administrator who -configures ``MyProject``). Settings in the config file are shared by -both this ``CTest`` module and the :manual:`ctest(1)` command-line -:ref:`Dashboard Client` mode (``ctest -S``). - -While building a project for submission to CDash, CTest scans the -build output for errors and warnings and reports them with surrounding -context from the build log. This generic approach works for all build -tools, but does not give details about the command invocation that -produced a given problem. One may get more detailed reports by setting -the :variable:`CTEST_USE_LAUNCHERS` variable:: - - set(CTEST_USE_LAUNCHERS 1) - -in the ``CTestConfig.cmake`` file. -#]=======================================================================] - -option(BUILD_TESTING "Build the testing tree." ON) - -# function to turn generator name into a version string -# like vs9 or vs10 -function(GET_VS_VERSION_STRING generator var) - string(REGEX REPLACE "Visual Studio ([0-9][0-9]?)($|.*)" "\\1" - NUMBER "${generator}") - set(ver_string "vs${NUMBER}") - set(${var} ${ver_string} PARENT_SCOPE) -endfunction() - -include(CTestUseLaunchers) - -if(BUILD_TESTING) - # Setup some auxiliary macros - macro(SET_IF_NOT_SET var val) - if(NOT DEFINED "${var}") - set("${var}" "${val}") - endif() - endmacro() - - macro(SET_IF_SET var val) - if(NOT "${val}" STREQUAL "") - set("${var}" "${val}") - endif() - endmacro() - - macro(SET_IF_SET_AND_NOT_SET var val) - if(NOT "${val}" STREQUAL "") - SET_IF_NOT_SET("${var}" "${val}") - endif() - endmacro() - - # Make sure testing is enabled - enable_testing() - - if(EXISTS "${PROJECT_SOURCE_DIR}/CTestConfig.cmake") - include("${PROJECT_SOURCE_DIR}/CTestConfig.cmake") - SET_IF_SET_AND_NOT_SET(NIGHTLY_START_TIME "${CTEST_NIGHTLY_START_TIME}") - SET_IF_SET_AND_NOT_SET(SUBMIT_URL "${CTEST_SUBMIT_URL}") - SET_IF_SET_AND_NOT_SET(DROP_METHOD "${CTEST_DROP_METHOD}") - SET_IF_SET_AND_NOT_SET(DROP_SITE "${CTEST_DROP_SITE}") - SET_IF_SET_AND_NOT_SET(DROP_SITE_USER "${CTEST_DROP_SITE_USER}") - SET_IF_SET_AND_NOT_SET(DROP_SITE_PASSWORD "${CTEST_DROP_SITE_PASWORD}") - SET_IF_SET_AND_NOT_SET(DROP_SITE_MODE "${CTEST_DROP_SITE_MODE}") - SET_IF_SET_AND_NOT_SET(DROP_LOCATION "${CTEST_DROP_LOCATION}") - SET_IF_SET_AND_NOT_SET(TRIGGER_SITE "${CTEST_TRIGGER_SITE}") - SET_IF_SET_AND_NOT_SET(UPDATE_TYPE "${CTEST_UPDATE_TYPE}") - endif() - - # the project can have a DartConfig.cmake file - if(EXISTS "${PROJECT_SOURCE_DIR}/DartConfig.cmake") - include("${PROJECT_SOURCE_DIR}/DartConfig.cmake") - else() - # Dashboard is opened for submissions for a 24 hour period starting at - # the specified NIGHTLY_START_TIME. Time is specified in 24 hour format. - SET_IF_NOT_SET (NIGHTLY_START_TIME "00:00:00 EDT") - SET_IF_NOT_SET(DROP_METHOD "http") - SET_IF_NOT_SET (COMPRESS_SUBMISSION ON) - endif() - SET_IF_NOT_SET (NIGHTLY_START_TIME "00:00:00 EDT") - - if(NOT SUBMIT_URL) - set(SUBMIT_URL "${DROP_METHOD}://") - if(DROP_SITE_USER) - string(APPEND SUBMIT_URL "${DROP_SITE_USER}") - if(DROP_SITE_PASSWORD) - string(APPEND SUBMIT_URL ":${DROP_SITE_PASSWORD}") - endif() - string(APPEND SUBMIT_URL "@") - endif() - string(APPEND SUBMIT_URL "${DROP_SITE}${DROP_LOCATION}") - endif() - - find_program(CVSCOMMAND cvs ) - set(CVS_UPDATE_OPTIONS "-d -A -P" CACHE STRING - "Options passed to the cvs update command.") - find_program(SVNCOMMAND svn) - find_program(BZRCOMMAND bzr) - find_program(HGCOMMAND hg) - find_program(GITCOMMAND git) - find_program(P4COMMAND p4) - - if(NOT UPDATE_TYPE) - if(EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/CVS") - set(UPDATE_TYPE cvs) - elseif(EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/.svn") - set(UPDATE_TYPE svn) - elseif(EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/.bzr") - set(UPDATE_TYPE bzr) - elseif(EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/.hg") - set(UPDATE_TYPE hg) - elseif(EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/.git") - set(UPDATE_TYPE git) - endif() - endif() - - string(TOLOWER "${UPDATE_TYPE}" _update_type) - if("${_update_type}" STREQUAL "cvs") - set(UPDATE_COMMAND "${CVSCOMMAND}") - set(UPDATE_OPTIONS "${CVS_UPDATE_OPTIONS}") - elseif("${_update_type}" STREQUAL "svn") - set(UPDATE_COMMAND "${SVNCOMMAND}") - set(UPDATE_OPTIONS "${SVN_UPDATE_OPTIONS}") - elseif("${_update_type}" STREQUAL "bzr") - set(UPDATE_COMMAND "${BZRCOMMAND}") - set(UPDATE_OPTIONS "${BZR_UPDATE_OPTIONS}") - elseif("${_update_type}" STREQUAL "hg") - set(UPDATE_COMMAND "${HGCOMMAND}") - set(UPDATE_OPTIONS "${HG_UPDATE_OPTIONS}") - elseif("${_update_type}" STREQUAL "git") - set(UPDATE_COMMAND "${GITCOMMAND}") - set(UPDATE_OPTIONS "${GIT_UPDATE_OPTIONS}") - elseif("${_update_type}" STREQUAL "p4") - set(UPDATE_COMMAND "${P4COMMAND}") - set(UPDATE_OPTIONS "${P4_UPDATE_OPTIONS}") - endif() - - set(DART_TESTING_TIMEOUT 1500 CACHE STRING - "Maximum time allowed before CTest will kill the test.") - - set(CTEST_SUBMIT_RETRY_DELAY 5 CACHE STRING - "How long to wait between timed-out CTest submissions.") - set(CTEST_SUBMIT_RETRY_COUNT 3 CACHE STRING - "How many times to retry timed-out CTest submissions.") - - find_program(MEMORYCHECK_COMMAND - NAMES purify valgrind boundscheck drmemory - PATHS - "[HKEY_LOCAL_MACHINE\\SOFTWARE\\Rational Software\\Purify\\Setup;InstallFolder]" - DOC "Path to the memory checking command, used for memory error detection." - ) - find_program(SLURM_SBATCH_COMMAND sbatch DOC - "Path to the SLURM sbatch executable" - ) - find_program(SLURM_SRUN_COMMAND srun DOC - "Path to the SLURM srun executable" - ) - set(MEMORYCHECK_SUPPRESSIONS_FILE "" CACHE FILEPATH - "File that contains suppressions for the memory checker") - find_program(COVERAGE_COMMAND gcov DOC - "Path to the coverage program that CTest uses for performing coverage inspection" - ) - set(COVERAGE_EXTRA_FLAGS "-l" CACHE STRING - "Extra command line flags to pass to the coverage tool") - - # set the site name - site_name(SITE) - # set the build name - if(NOT BUILDNAME) - set(DART_COMPILER "${CMAKE_CXX_COMPILER}") - if(NOT DART_COMPILER) - set(DART_COMPILER "${CMAKE_C_COMPILER}") - endif() - if(NOT DART_COMPILER) - set(DART_COMPILER "unknown") - endif() - if(WIN32) - set(DART_NAME_COMPONENT "NAME_WE") - else() - set(DART_NAME_COMPONENT "NAME") - endif() - if(NOT BUILD_NAME_SYSTEM_NAME) - set(BUILD_NAME_SYSTEM_NAME "${CMAKE_SYSTEM_NAME}") - endif() - if(WIN32) - set(BUILD_NAME_SYSTEM_NAME "Win32") - endif() - if(UNIX OR BORLAND) - get_filename_component(DART_COMPILER_NAME - "${DART_COMPILER}" ${DART_NAME_COMPONENT}) - else() - get_filename_component(DART_COMPILER_NAME - "${CMAKE_MAKE_PROGRAM}" ${DART_NAME_COMPONENT}) - endif() - if(DART_COMPILER_NAME MATCHES "devenv") - GET_VS_VERSION_STRING("${CMAKE_GENERATOR}" DART_COMPILER_NAME) - endif() - set(BUILDNAME "${BUILD_NAME_SYSTEM_NAME}-${DART_COMPILER_NAME}") - endif() - - # the build command - build_command(MAKECOMMAND_DEFAULT_VALUE - CONFIGURATION "\${CTEST_CONFIGURATION_TYPE}") - set(MAKECOMMAND ${MAKECOMMAND_DEFAULT_VALUE} - CACHE STRING "Command to build the project") - - # the default build configuration the ctest build handler will use - # if there is no -C arg given to ctest: - set(DEFAULT_CTEST_CONFIGURATION_TYPE "$ENV{CMAKE_CONFIG_TYPE}") - if(DEFAULT_CTEST_CONFIGURATION_TYPE STREQUAL "") - set(DEFAULT_CTEST_CONFIGURATION_TYPE "Release") - endif() - - mark_as_advanced( - BZRCOMMAND - COVERAGE_COMMAND - COVERAGE_EXTRA_FLAGS - CTEST_SUBMIT_RETRY_DELAY - CTEST_SUBMIT_RETRY_COUNT - CVSCOMMAND - CVS_UPDATE_OPTIONS - DART_TESTING_TIMEOUT - GITCOMMAND - P4COMMAND - HGCOMMAND - MAKECOMMAND - MEMORYCHECK_COMMAND - MEMORYCHECK_SUPPRESSIONS_FILE - SLURM_SBATCH_COMMAND - SLURM_SRUN_COMMAND - SITE - SVNCOMMAND - ) - if(NOT RUN_FROM_DART) - set(RUN_FROM_CTEST_OR_DART 1) - include(CTestTargets) - set(RUN_FROM_CTEST_OR_DART) - endif() -endif()
diff --git a/share/cmake-3.18/Modules/CTestCoverageCollectGCOV.cmake b/share/cmake-3.18/Modules/CTestCoverageCollectGCOV.cmake deleted file mode 100644 index b1268be..0000000 --- a/share/cmake-3.18/Modules/CTestCoverageCollectGCOV.cmake +++ /dev/null
@@ -1,339 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CTestCoverageCollectGCOV ------------------------- - -This module provides the ``ctest_coverage_collect_gcov`` function. - -This function runs gcov on all .gcda files found in the binary tree -and packages the resulting .gcov files into a tar file. -This tarball also contains the following: - -* *data.json* defines the source and build directories for use by CDash. -* *Labels.json* indicates any :prop_sf:`LABELS` that have been set on the - source files. -* The *uncovered* directory holds any uncovered files found by - :variable:`CTEST_EXTRA_COVERAGE_GLOB`. - -After generating this tar file, it can be sent to CDash for display with the -:command:`ctest_submit(CDASH_UPLOAD)` command. - -.. command:: ctest_coverage_collect_gcov - - :: - - ctest_coverage_collect_gcov(TARBALL <tarfile> - [SOURCE <source_dir>][BUILD <build_dir>] - [GCOV_COMMAND <gcov_command>] - [GCOV_OPTIONS <options>...] - ) - - Run gcov and package a tar file for CDash. The options are: - - ``TARBALL <tarfile>`` - Specify the location of the ``.tar`` file to be created for later - upload to CDash. Relative paths will be interpreted with respect - to the top-level build directory. - - ``TARBALL_COMPRESSION <option>`` Specify a compression algorithm for the - ``TARBALL`` data file. Using this option reduces the size of the data file - before it is submitted to CDash. ``<option>`` must be one of ``GZIP``, - ``BZIP2``, ``XZ``, ``ZSTD``, ``FROM_EXT``, or an expression that CMake - evaluates as ``FALSE``. The default value is ``BZIP2``. - - If ``FROM_EXT`` is specified, the resulting file will be compressed based on - the file extension of the ``<tarfile>`` (i.e. ``.tar.gz`` will use ``GZIP`` - compression). File extensions that will produce compressed output include - ``.tar.gz``, ``.tgz``, ``.tar.bzip2``, ``.tbz``, ``.tar.xz``, and ``.txz``. - - ``SOURCE <source_dir>`` - Specify the top-level source directory for the build. - Default is the value of :variable:`CTEST_SOURCE_DIRECTORY`. - - ``BUILD <build_dir>`` - Specify the top-level build directory for the build. - Default is the value of :variable:`CTEST_BINARY_DIRECTORY`. - - ``GCOV_COMMAND <gcov_command>`` - Specify the full path to the ``gcov`` command on the machine. - Default is the value of :variable:`CTEST_COVERAGE_COMMAND`. - - ``GCOV_OPTIONS <options>...`` - Specify options to be passed to gcov. The ``gcov`` command - is run as ``gcov <options>... -o <gcov-dir> <file>.gcda``. - If not specified, the default option is just ``-b -x``. - - ``GLOB`` - Recursively search for .gcda files in build_dir rather than - determining search locations by reading TargetDirectories.txt. - - ``DELETE`` - Delete coverage files after they've been packaged into the .tar. - - ``QUIET`` - Suppress non-error messages that otherwise would have been - printed out by this function. -#]=======================================================================] - -function(ctest_coverage_collect_gcov) - set(options QUIET GLOB DELETE) - set(oneValueArgs TARBALL SOURCE BUILD GCOV_COMMAND TARBALL_COMPRESSION) - set(multiValueArgs GCOV_OPTIONS) - cmake_parse_arguments(GCOV "${options}" "${oneValueArgs}" - "${multiValueArgs}" "" ${ARGN} ) - if(NOT DEFINED GCOV_TARBALL) - message(FATAL_ERROR - "TARBALL must be specified. for ctest_coverage_collect_gcov") - endif() - if(NOT DEFINED GCOV_SOURCE) - set(source_dir "${CTEST_SOURCE_DIRECTORY}") - else() - set(source_dir "${GCOV_SOURCE}") - endif() - if(NOT DEFINED GCOV_BUILD) - set(binary_dir "${CTEST_BINARY_DIRECTORY}") - else() - set(binary_dir "${GCOV_BUILD}") - endif() - if(NOT DEFINED GCOV_GCOV_COMMAND) - set(gcov_command "${CTEST_COVERAGE_COMMAND}") - else() - set(gcov_command "${GCOV_GCOV_COMMAND}") - endif() - if(NOT DEFINED GCOV_TARBALL_COMPRESSION) - set(GCOV_TARBALL_COMPRESSION "BZIP2") - elseif( GCOV_TARBALL_COMPRESSION AND - NOT GCOV_TARBALL_COMPRESSION MATCHES "^(GZIP|BZIP2|XZ|ZSTD|FROM_EXT)$") - message(FATAL_ERROR "TARBALL_COMPRESSION must be one of OFF, GZIP, " - "BZIP2, XZ, ZSTD, or FROM_EXT for ctest_coverage_collect_gcov") - endif() - # run gcov on each gcda file in the binary tree - set(gcda_files) - set(label_files) - if (GCOV_GLOB) - file(GLOB_RECURSE gfiles "${binary_dir}/*.gcda") - list(LENGTH gfiles len) - # if we have gcda files then also grab the labels file for that target - if(${len} GREATER 0) - file(GLOB_RECURSE lfiles RELATIVE ${binary_dir} "${binary_dir}/Labels.json") - list(APPEND gcda_files ${gfiles}) - list(APPEND label_files ${lfiles}) - endif() - else() - # look for gcda files in the target directories - # this will be faster and only look where the files will be - file(STRINGS "${binary_dir}/CMakeFiles/TargetDirectories.txt" target_dirs - ENCODING UTF-8) - foreach(target_dir ${target_dirs}) - file(GLOB_RECURSE gfiles "${target_dir}/*.gcda") - list(LENGTH gfiles len) - # if we have gcda files then also grab the labels file for that target - if(${len} GREATER 0) - file(GLOB_RECURSE lfiles RELATIVE ${binary_dir} - "${target_dir}/Labels.json") - list(APPEND gcda_files ${gfiles}) - list(APPEND label_files ${lfiles}) - endif() - endforeach() - endif() - # return early if no coverage files were found - list(LENGTH gcda_files len) - if(len EQUAL 0) - if (NOT GCOV_QUIET) - message("ctest_coverage_collect_gcov: No .gcda files found, " - "ignoring coverage request.") - endif() - return() - endif() - # setup the dir for the coverage files - set(coverage_dir "${binary_dir}/Testing/CoverageInfo") - file(MAKE_DIRECTORY "${coverage_dir}") - # run gcov, this will produce the .gcov files in the current - # working directory - if(NOT DEFINED GCOV_GCOV_OPTIONS) - set(GCOV_GCOV_OPTIONS -b -x) - endif() - if (GCOV_QUIET) - set(coverage_out_opts - OUTPUT_QUIET - ERROR_QUIET - ) - else() - set(coverage_out_opts - OUTPUT_FILE "${coverage_dir}/gcov.log" - ERROR_FILE "${coverage_dir}/gcov.log" - ) - endif() - execute_process(COMMAND - ${gcov_command} ${GCOV_GCOV_OPTIONS} ${gcda_files} - RESULT_VARIABLE res - WORKING_DIRECTORY ${coverage_dir} - ${coverage_out_opts} - ) - - if (GCOV_DELETE) - file(REMOVE ${gcda_files}) - endif() - - if(NOT "${res}" EQUAL 0) - if (NOT GCOV_QUIET) - message(STATUS "Error running gcov: ${res}, see\n ${coverage_dir}/gcov.log") - endif() - endif() - # create json file with project information - file(WRITE ${coverage_dir}/data.json - "{ - \"Source\": \"${source_dir}\", - \"Binary\": \"${binary_dir}\" -}") - # collect the gcov files - set(unfiltered_gcov_files) - file(GLOB_RECURSE unfiltered_gcov_files RELATIVE ${binary_dir} "${coverage_dir}/*.gcov") - - # if CTEST_EXTRA_COVERAGE_GLOB was specified we search for files - # that might be uncovered - if (DEFINED CTEST_EXTRA_COVERAGE_GLOB) - set(uncovered_files) - foreach(search_entry IN LISTS CTEST_EXTRA_COVERAGE_GLOB) - if(NOT GCOV_QUIET) - message("Add coverage glob: ${search_entry}") - endif() - file(GLOB_RECURSE matching_files "${source_dir}/${search_entry}") - if (matching_files) - list(APPEND uncovered_files "${matching_files}") - endif() - endforeach() - endif() - - set(gcov_files) - foreach(gcov_file ${unfiltered_gcov_files}) - file(STRINGS ${binary_dir}/${gcov_file} first_line LIMIT_COUNT 1 ENCODING UTF-8) - - set(is_excluded false) - if(first_line MATCHES "^ -: 0:Source:(.*)$") - set(source_file ${CMAKE_MATCH_1}) - elseif(NOT GCOV_QUIET) - message(STATUS "Could not determine source file corresponding to: ${gcov_file}") - endif() - - foreach(exclude_entry IN LISTS CTEST_CUSTOM_COVERAGE_EXCLUDE) - if(source_file MATCHES "${exclude_entry}") - set(is_excluded true) - - if(NOT GCOV_QUIET) - message("Excluding coverage for: ${source_file} which matches ${exclude_entry}") - endif() - - break() - endif() - endforeach() - - get_filename_component(resolved_source_file "${source_file}" ABSOLUTE) - foreach(uncovered_file IN LISTS uncovered_files) - get_filename_component(resolved_uncovered_file "${uncovered_file}" ABSOLUTE) - if (resolved_uncovered_file STREQUAL resolved_source_file) - list(REMOVE_ITEM uncovered_files "${uncovered_file}") - endif() - endforeach() - - if(NOT is_excluded) - list(APPEND gcov_files ${gcov_file}) - endif() - endforeach() - - foreach (uncovered_file ${uncovered_files}) - # Check if this uncovered file should be excluded. - set(is_excluded false) - foreach(exclude_entry IN LISTS CTEST_CUSTOM_COVERAGE_EXCLUDE) - if(uncovered_file MATCHES "${exclude_entry}") - set(is_excluded true) - if(NOT GCOV_QUIET) - message("Excluding coverage for: ${uncovered_file} which matches ${exclude_entry}") - endif() - break() - endif() - endforeach() - if(is_excluded) - continue() - endif() - - # Copy from source to binary dir, preserving any intermediate subdirectories. - get_filename_component(filename "${uncovered_file}" NAME) - get_filename_component(relative_path "${uncovered_file}" DIRECTORY) - string(REPLACE "${source_dir}" "" relative_path "${relative_path}") - if (relative_path) - # Strip leading slash. - string(SUBSTRING "${relative_path}" 1 -1 relative_path) - endif() - file(COPY ${uncovered_file} DESTINATION ${binary_dir}/uncovered/${relative_path}) - if(relative_path) - list(APPEND uncovered_files_for_tar uncovered/${relative_path}/${filename}) - else() - list(APPEND uncovered_files_for_tar uncovered/${filename}) - endif() - endforeach() - - # tar up the coverage info with the same date so that the md5 - # sum will be the same for the tar file independent of file time - # stamps - string(REPLACE ";" "\n" gcov_files "${gcov_files}") - string(REPLACE ";" "\n" label_files "${label_files}") - string(REPLACE ";" "\n" uncovered_files_for_tar "${uncovered_files_for_tar}") - file(WRITE "${coverage_dir}/coverage_file_list.txt" - "${gcov_files} -${coverage_dir}/data.json -${label_files} -${uncovered_files_for_tar} -") - - # Prepare tar command line arguments - - set(tar_opts "") - # Select data compression mode - if( GCOV_TARBALL_COMPRESSION STREQUAL "FROM_EXT") - if( GCOV_TARBALL MATCHES [[\.(tgz|tar.gz)$]] ) - string(APPEND tar_opts "z") - elseif( GCOV_TARBALL MATCHES [[\.(txz|tar.xz)$]] ) - string(APPEND tar_opts "J") - elseif( GCOV_TARBALL MATCHES [[\.(tbz|tar.bz)$]] ) - string(APPEND tar_opts "j") - endif() - elseif(GCOV_TARBALL_COMPRESSION STREQUAL "GZIP") - string(APPEND tar_opts "z") - elseif(GCOV_TARBALL_COMPRESSION STREQUAL "XZ") - string(APPEND tar_opts "J") - elseif(GCOV_TARBALL_COMPRESSION STREQUAL "BZIP2") - string(APPEND tar_opts "j") - elseif(GCOV_TARBALL_COMPRESSION STREQUAL "ZSTD") - set(zstd_tar_opt "--zstd") - endif() - # Verbosity options - if(NOT GCOV_QUIET AND NOT tar_opts MATCHES v) - string(APPEND tar_opts "v") - endif() - # Prepend option 'c' specifying 'create' - string(PREPEND tar_opts "c") - # Append option 'f' so that the next argument is the filename - string(APPEND tar_opts "f") - - execute_process(COMMAND - ${CMAKE_COMMAND} -E tar ${tar_opts} ${GCOV_TARBALL} ${zstd_tar_opt} - "--mtime=1970-01-01 0:0:0 UTC" - "--format=gnutar" - --files-from=${coverage_dir}/coverage_file_list.txt - WORKING_DIRECTORY ${binary_dir}) - - if (GCOV_DELETE) - foreach(gcov_file ${unfiltered_gcov_files}) - file(REMOVE ${binary_dir}/${gcov_file}) - endforeach() - file(REMOVE ${coverage_dir}/coverage_file_list.txt) - file(REMOVE ${coverage_dir}/data.json) - if (EXISTS ${binary_dir}/uncovered) - file(REMOVE ${binary_dir}/uncovered) - endif() - endif() - -endfunction()
diff --git a/share/cmake-3.18/Modules/CTestUseLaunchers.cmake b/share/cmake-3.18/Modules/CTestUseLaunchers.cmake deleted file mode 100644 index 3dff926..0000000 --- a/share/cmake-3.18/Modules/CTestUseLaunchers.cmake +++ /dev/null
@@ -1,70 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CTestUseLaunchers ------------------ - -Set the RULE_LAUNCH_* global properties when CTEST_USE_LAUNCHERS is on. - -CTestUseLaunchers is automatically included when you include(CTest). -However, it is split out into its own module file so projects can use -the CTEST_USE_LAUNCHERS functionality independently. - -To use launchers, set CTEST_USE_LAUNCHERS to ON in a ctest -S -dashboard script, and then also set it in the cache of the configured -project. Both cmake and ctest need to know the value of it for the -launchers to work properly. CMake needs to know in order to generate -proper build rules, and ctest, in order to produce the proper error -and warning analysis. - -For convenience, you may set the ENV variable -CTEST_USE_LAUNCHERS_DEFAULT in your ctest -S script, too. Then, as -long as your CMakeLists uses include(CTest) or -include(CTestUseLaunchers), it will use the value of the ENV variable -to initialize a CTEST_USE_LAUNCHERS cache variable. This cache -variable initialization only occurs if CTEST_USE_LAUNCHERS is not -already defined. If CTEST_USE_LAUNCHERS is on in a ctest -S script -the ctest_configure command will add -DCTEST_USE_LAUNCHERS:BOOL=TRUE -to the cmake command used to configure the project. -#]=======================================================================] - -if(NOT DEFINED CTEST_USE_LAUNCHERS AND DEFINED ENV{CTEST_USE_LAUNCHERS_DEFAULT}) - set(CTEST_USE_LAUNCHERS "$ENV{CTEST_USE_LAUNCHERS_DEFAULT}" - CACHE INTERNAL "CTEST_USE_LAUNCHERS initial value from ENV") -endif() - -if(NOT "${CMAKE_GENERATOR}" MATCHES "Make|Ninja") - set(CTEST_USE_LAUNCHERS 0) -endif() - -if(CTEST_USE_LAUNCHERS) - set(__launch_common_options - "--target-name <TARGET_NAME> --build-dir <CMAKE_CURRENT_BINARY_DIR>") - - set(__launch_compile_options - "${__launch_common_options} --output <OBJECT> --source <SOURCE> --language <LANGUAGE>") - - set(__launch_link_options - "${__launch_common_options} --output <TARGET> --target-type <TARGET_TYPE> --language <LANGUAGE>") - - set(__launch_custom_options - "${__launch_common_options} --output <OUTPUT>") - - if("${CMAKE_GENERATOR}" MATCHES "Ninja") - string(APPEND __launch_compile_options " --filter-prefix <CMAKE_CL_SHOWINCLUDES_PREFIX>") - endif() - - set(CTEST_LAUNCH_COMPILE - "\"${CMAKE_CTEST_COMMAND}\" --launch ${__launch_compile_options} --") - - set(CTEST_LAUNCH_LINK - "\"${CMAKE_CTEST_COMMAND}\" --launch ${__launch_link_options} --") - - set(CTEST_LAUNCH_CUSTOM - "\"${CMAKE_CTEST_COMMAND}\" --launch ${__launch_custom_options} --") - - set_property(GLOBAL PROPERTY RULE_LAUNCH_COMPILE "${CTEST_LAUNCH_COMPILE}") - set_property(GLOBAL PROPERTY RULE_LAUNCH_LINK "${CTEST_LAUNCH_LINK}") - set_property(GLOBAL PROPERTY RULE_LAUNCH_CUSTOM "${CTEST_LAUNCH_CUSTOM}") -endif()
diff --git a/share/cmake-3.18/Modules/CheckCCompilerFlag.cmake b/share/cmake-3.18/Modules/CheckCCompilerFlag.cmake deleted file mode 100644 index 6d65313..0000000 --- a/share/cmake-3.18/Modules/CheckCCompilerFlag.cmake +++ /dev/null
@@ -1,58 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCCompilerFlag ------------------- - -Check whether the C compiler supports a given flag. - -.. command:: check_c_compiler_flag - - .. code-block:: cmake - - check_c_compiler_flag(<flag> <var>) - - Check that the ``<flag>`` is accepted by the compiler without - a diagnostic. Stores the result in an internal cache entry - named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_DEFINITIONS`` variable -and calls the ``check_c_source_compiles`` macro from the -:module:`CheckCSourceCompiles` module. See documentation of that -module for a listing of variables that can otherwise modify the build. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_C_FLAGS <CMAKE_<LANG>_FLAGS>`, unknown flags - in such variables may cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckCSourceCompiles) -include(CMakeCheckCompilerFlagCommonPatterns) - -function(check_c_compiler_flag _flag _var) - set(CMAKE_REQUIRED_DEFINITIONS "${_flag}") - - # Normalize locale during test compilation. - set(_locale_vars LC_ALL LC_MESSAGES LANG) - foreach(v IN LISTS _locale_vars) - set(_locale_vars_saved_${v} "$ENV{${v}}") - set(ENV{${v}} C) - endforeach() - check_compiler_flag_common_patterns(_common_patterns) - check_c_source_compiles("int main(void) { return 0; }" ${_var} - # Some compilers do not fail with a bad flag - FAIL_REGEX "command line option .* is valid for .* but not for C" # GNU - ${_common_patterns} - ) - foreach(v IN LISTS _locale_vars) - set(ENV{${v}} ${_locale_vars_saved_${v}}) - endforeach() - set(${_var} "${${_var}}" PARENT_SCOPE) -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckCSourceCompiles.cmake b/share/cmake-3.18/Modules/CheckCSourceCompiles.cmake deleted file mode 100644 index 67fc993..0000000 --- a/share/cmake-3.18/Modules/CheckCSourceCompiles.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCSourceCompiles --------------------- - -Check if given C source compiles and links into an executable. - -.. command:: check_c_source_compiles - - .. code-block:: cmake - - check_c_source_compiles(<code> <resultVar> - [FAIL_REGEX <regex1> [<regex2>...]]) - - Check that the source supplied in ``<code>`` can be compiled as a C source - file and linked as an executable (so it must contain at least a ``main()`` - function). The result will be stored in the internal cache variable specified - by ``<resultVar>``, with a boolean true value for success and boolean false - for failure. If ``FAIL_REGEX`` is provided, then failure is determined by - checking if anything in the output matches any of the specified regular - expressions. - - The underlying check is performed by the :command:`try_compile` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_c_source_compiles()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_C_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_compile()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_C_SOURCE_COMPILES SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_FAIL_REGEX) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(FAIL_REGEX)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_C_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_C_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.c" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_compile(${VAR} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.c - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - "${CHECK_C_SOURCE_COMPILES_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - foreach(_regex ${_FAIL_REGEX}) - if("${OUTPUT}" MATCHES "${_regex}") - set(${VAR} 0) - endif() - endforeach() - - if(${VAR}) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing C SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing C SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckCSourceRuns.cmake b/share/cmake-3.18/Modules/CheckCSourceRuns.cmake deleted file mode 100644 index 7d116db..0000000 --- a/share/cmake-3.18/Modules/CheckCSourceRuns.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCSourceRuns ----------------- - -Check if given C source compiles and links into an executable and can -subsequently be run. - -.. command:: check_c_source_runs - - .. code-block:: cmake - - check_c_source_runs(<code> <resultVar>) - - Check that the source supplied in ``<code>`` can be compiled as a C source - file, linked as an executable and then run. The ``<code>`` must contain at - least a ``main()`` function. If the ``<code>`` could be built and run - successfully, the internal cache variable specified by ``<resultVar>`` will - be set to 1, otherwise it will be set to an value that evaluates to boolean - false (e.g. an empty string or an error message). - - The underlying check is performed by the :command:`try_run` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_c_source_runs()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_C_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_run` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_C_SOURCE_RUNS SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_C_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_C_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.c" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_run(${VAR}_EXITCODE ${VAR}_COMPILED - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.c - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_C_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_C_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - -DCMAKE_SKIP_RPATH:BOOL=${CMAKE_SKIP_RPATH} - "${CHECK_C_SOURCE_COMPILES_ADD_INCLUDES}" - COMPILE_OUTPUT_VARIABLE OUTPUT - RUN_OUTPUT_VARIABLE RUN_OUTPUT) - # if it did not compile make the return value fail code of 1 - if(NOT ${VAR}_COMPILED) - set(${VAR}_EXITCODE 1) - endif() - # if the return value was 0 then it worked - if("${${VAR}_EXITCODE}" EQUAL 0) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing C SOURCE FILE Test ${VAR} succeeded with the following compile output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}}\n" - "Source file was:\n${SOURCE}\n") - else() - if(CMAKE_CROSSCOMPILING AND "${${VAR}_EXITCODE}" MATCHES "FAILED_TO_RUN") - set(${VAR} "${${VAR}_EXITCODE}") - else() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing C SOURCE FILE Test ${VAR} failed with the following compile output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}_EXITCODE}\n" - "Source file was:\n${SOURCE}\n") - - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckCXXCompilerFlag.cmake b/share/cmake-3.18/Modules/CheckCXXCompilerFlag.cmake deleted file mode 100644 index 5e07c25..0000000 --- a/share/cmake-3.18/Modules/CheckCXXCompilerFlag.cmake +++ /dev/null
@@ -1,58 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCXXCompilerFlag ------------------------- - -Check whether the CXX compiler supports a given flag. - -.. command:: check_cxx_compiler_flag - - .. code-block:: cmake - - check_cxx_compiler_flag(<flag> <var>) - - Check that the ``<flag>`` is accepted by the compiler without - a diagnostic. Stores the result in an internal cache entry - named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_DEFINITIONS`` variable -and calls the ``check_cxx_source_compiles`` macro from the -:module:`CheckCXXSourceCompiles` module. See documentation of that -module for a listing of variables that can otherwise modify the build. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_CXX_FLAGS <CMAKE_<LANG>_FLAGS>`, unknown flags - in such variables may cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckCXXSourceCompiles) -include(CMakeCheckCompilerFlagCommonPatterns) - -function(check_cxx_compiler_flag _flag _var) - set(CMAKE_REQUIRED_DEFINITIONS "${_flag}") - - # Normalize locale during test compilation. - set(_locale_vars LC_ALL LC_MESSAGES LANG) - foreach(v IN LISTS _locale_vars) - set(_locale_vars_saved_${v} "$ENV{${v}}") - set(ENV{${v}} C) - endforeach() - check_compiler_flag_common_patterns(_common_patterns) - check_cxx_source_compiles("int main() { return 0; }" ${_var} - # Some compilers do not fail with a bad flag - FAIL_REGEX "command line option .* is valid for .* but not for C\\\\+\\\\+" # GNU - ${_common_patterns} - ) - foreach(v IN LISTS _locale_vars) - set(ENV{${v}} ${_locale_vars_saved_${v}}) - endforeach() - set(${_var} "${${_var}}" PARENT_SCOPE) -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckCXXSourceCompiles.cmake b/share/cmake-3.18/Modules/CheckCXXSourceCompiles.cmake deleted file mode 100644 index c693d32..0000000 --- a/share/cmake-3.18/Modules/CheckCXXSourceCompiles.cmake +++ /dev/null
@@ -1,146 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCXXSourceCompiles ----------------------- - -Check if given C++ source compiles and links into an executable. - -.. command:: check_cxx_source_compiles - - .. code-block:: cmake - - check_cxx_source_compiles(<code> <resultVar> - [FAIL_REGEX <regex1> [<regex2>...]]) - - Check that the source supplied in ``<code>`` can be compiled as a C++ source - file and linked as an executable (so it must contain at least a ``main()`` - function). The result will be stored in the internal cache variable specified - by ``<resultVar>``, with a boolean true value for success and boolean false - for failure. If ``FAIL_REGEX`` is provided, then failure is determined by - checking if anything in the output matches any of the specified regular - expressions. - - The underlying check is performed by the :command:`try_compile` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_cxx_source_compiles()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_CXX_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_compile()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_CXX_SOURCE_COMPILES SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_FAIL_REGEX) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(FAIL_REGEX)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.cxx" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_compile(${VAR} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.cxx - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - "${CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - foreach(_regex ${_FAIL_REGEX}) - if("${OUTPUT}" MATCHES "${_regex}") - set(${VAR} 0) - endif() - endforeach() - - if(${VAR}) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing C++ SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing C++ SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckCXXSourceRuns.cmake b/share/cmake-3.18/Modules/CheckCXXSourceRuns.cmake deleted file mode 100644 index 408e183..0000000 --- a/share/cmake-3.18/Modules/CheckCXXSourceRuns.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCXXSourceRuns ------------------- - -Check if given C++ source compiles and links into an executable and can -subsequently be run. - -.. command:: check_cxx_source_runs - - .. code-block:: cmake - - check_cxx_source_runs(<code> <resultVar>) - - Check that the source supplied in ``<code>`` can be compiled as a C++ source - file, linked as an executable and then run. The ``<code>`` must contain at - least a ``main()`` function. If the ``<code>`` could be built and run - successfully, the internal cache variable specified by ``<resultVar>`` will - be set to 1, otherwise it will be set to an value that evaluates to boolean - false (e.g. an empty string or an error message). - - The underlying check is performed by the :command:`try_run` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_cxx_source_runs()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_CXX_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_run` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_CXX_SOURCE_RUNS SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.cxx" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_run(${VAR}_EXITCODE ${VAR}_COMPILED - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.cxx - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_CXX_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_CXX_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - -DCMAKE_SKIP_RPATH:BOOL=${CMAKE_SKIP_RPATH} - "${CHECK_CXX_SOURCE_COMPILES_ADD_INCLUDES}" - COMPILE_OUTPUT_VARIABLE OUTPUT - RUN_OUTPUT_VARIABLE RUN_OUTPUT) - - # if it did not compile make the return value fail code of 1 - if(NOT ${VAR}_COMPILED) - set(${VAR}_EXITCODE 1) - endif() - # if the return value was 0 then it worked - if("${${VAR}_EXITCODE}" EQUAL 0) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing C++ SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}}\n" - "Source file was:\n${SOURCE}\n") - else() - if(CMAKE_CROSSCOMPILING AND "${${VAR}_EXITCODE}" MATCHES "FAILED_TO_RUN") - set(${VAR} "${${VAR}_EXITCODE}") - else() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing C++ SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}_EXITCODE}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckCXXSymbolExists.cmake b/share/cmake-3.18/Modules/CheckCXXSymbolExists.cmake deleted file mode 100644 index 5c9079d..0000000 --- a/share/cmake-3.18/Modules/CheckCXXSymbolExists.cmake +++ /dev/null
@@ -1,76 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckCXXSymbolExists --------------------- - -Check if a symbol exists as a function, variable, or macro in ``C++``. - -.. command:: check_cxx_symbol_exists - - .. code-block:: cmake - - check_cxx_symbol_exists(<symbol> <files> <variable>) - - Check that the ``<symbol>`` is available after including given header - ``<files>`` and store the result in a ``<variable>``. Specify the list of - files in one argument as a semicolon-separated list. - ``check_cxx_symbol_exists()`` can be used to check for symbols as seen by - the C++ compiler, as opposed to :command:`check_symbol_exists`, which always - uses the ``C`` compiler. - - If the header files define the symbol as a macro it is considered - available and assumed to work. If the header files declare the symbol - as a function or variable then the symbol must also be available for - linking. If the symbol is a type, enum value, or C++ template it will - not be recognized: consider using the :module:`CheckTypeSize` - or :module:`CheckCXXSourceCompiles` module instead. - -.. note:: - - This command is unreliable when ``<symbol>`` is (potentially) an overloaded - function. Since there is no reliable way to predict whether a given function - in the system environment may be defined as an overloaded function or may be - an overloaded function on other systems or will become so in the future, it - is generally advised to use the :module:`CheckCXXSourceCompiles` module for - checking any function symbol (unless somehow you surely know the checked - function is not overloaded on other systems or will not be so in the - future). - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -For example: - -.. code-block:: cmake - - include(CheckCXXSymbolExists) - - # Check for macro SEEK_SET - check_cxx_symbol_exists(SEEK_SET "cstdio" HAVE_SEEK_SET) - # Check for function std::fopen - check_cxx_symbol_exists(std::fopen "cstdio" HAVE_STD_FOPEN) -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckSymbolExists) - -macro(CHECK_CXX_SYMBOL_EXISTS SYMBOL FILES VARIABLE) - __CHECK_SYMBOL_EXISTS_IMPL("${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckSymbolExists.cxx" "${SYMBOL}" "${FILES}" "${VARIABLE}" ) -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckFortranCompilerFlag.cmake b/share/cmake-3.18/Modules/CheckFortranCompilerFlag.cmake deleted file mode 100644 index 299cd8c..0000000 --- a/share/cmake-3.18/Modules/CheckFortranCompilerFlag.cmake +++ /dev/null
@@ -1,63 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckFortranCompilerFlag ------------------------- - -Check whether the Fortran compiler supports a given flag. - -.. command:: check_fortran_compiler_flag - - .. code-block:: cmake - - check_fortran_compiler_flag(<flag> <var>) - - Check that the ``<flag>`` is accepted by the compiler without - a diagnostic. Stores the result in an internal cache entry - named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_DEFINITIONS`` variable -and calls the ``check_fortran_source_compiles`` macro from the -:module:`CheckFortranSourceCompiles` module. See documentation of that -module for a listing of variables that can otherwise modify the build. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_Fortran_FLAGS <CMAKE_<LANG>_FLAGS>`, unknown flags - in such variables may cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckFortranSourceCompiles) -include(CMakeCheckCompilerFlagCommonPatterns) - -macro (CHECK_Fortran_COMPILER_FLAG _FLAG _RESULT) - set(SAFE_CMAKE_REQUIRED_DEFINITIONS "${CMAKE_REQUIRED_DEFINITIONS}") - set(CMAKE_REQUIRED_DEFINITIONS "${_FLAG}") - - # Normalize locale during test compilation. - set(_CheckFortranCompilerFlag_LOCALE_VARS LC_ALL LC_MESSAGES LANG) - foreach(v ${_CheckFortranCompilerFlag_LOCALE_VARS}) - set(_CheckFortranCompilerFlag_SAVED_${v} "$ENV{${v}}") - set(ENV{${v}} C) - endforeach() - CHECK_COMPILER_FLAG_COMMON_PATTERNS(_CheckFortranCompilerFlag_COMMON_PATTERNS) - CHECK_Fortran_SOURCE_COMPILES(" program test\n stop\n end program" ${_RESULT} - # Some compilers do not fail with a bad flag - FAIL_REGEX "command line option .* is valid for .* but not for Fortran" # GNU - ${_CheckFortranCompilerFlag_COMMON_PATTERNS} - ) - foreach(v ${_CheckFortranCompilerFlag_LOCALE_VARS}) - set(ENV{${v}} ${_CheckFortranCompilerFlag_SAVED_${v}}) - unset(_CheckFortranCompilerFlag_SAVED_${v}) - endforeach() - unset(_CheckFortranCompilerFlag_LOCALE_VARS) - unset(_CheckFortranCompilerFlag_COMMON_PATTERNS) - - set (CMAKE_REQUIRED_DEFINITIONS "${SAFE_CMAKE_REQUIRED_DEFINITIONS}") -endmacro ()
diff --git a/share/cmake-3.18/Modules/CheckFortranFunctionExists.cmake b/share/cmake-3.18/Modules/CheckFortranFunctionExists.cmake deleted file mode 100644 index d06203f..0000000 --- a/share/cmake-3.18/Modules/CheckFortranFunctionExists.cmake +++ /dev/null
@@ -1,84 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckFortranFunctionExists --------------------------- - -Check if a Fortran function exists. - -.. command:: CHECK_FORTRAN_FUNCTION_EXISTS - - .. code-block:: cmake - - CHECK_FORTRAN_FUNCTION_EXISTS(<function> <result>) - - where - - ``<function>`` - the name of the Fortran function - ``<result>`` - variable to store the result; will be created as an internal cache variable. - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - -``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_FORTRAN_FUNCTION_EXISTS FUNCTION VARIABLE) - if(NOT DEFINED ${VARIABLE}) - message(CHECK_START "Looking for Fortran ${FUNCTION}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_FUNCTION_EXISTS_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_FUNCTION_EXISTS_ADD_LIBRARIES) - endif() - file(WRITE - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompiler.f - " - program TESTFortran - external ${FUNCTION} - call ${FUNCTION}() - end program TESTFortran - " - ) - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/testFortranCompiler.f - ${CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS} - ${CHECK_FUNCTION_EXISTS_ADD_LIBRARIES} - OUTPUT_VARIABLE OUTPUT - ) - if(${VARIABLE}) - set(${VARIABLE} 1 CACHE INTERNAL "Have Fortran function ${FUNCTION}") - message(CHECK_PASS "found") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the Fortran ${FUNCTION} exists passed with the following output:\n" - "${OUTPUT}\n\n") - else() - message(CHECK_FAIL "not found") - set(${VARIABLE} "" CACHE INTERNAL "Have Fortran function ${FUNCTION}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the Fortran ${FUNCTION} exists failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckFortranSourceCompiles.cmake b/share/cmake-3.18/Modules/CheckFortranSourceCompiles.cmake deleted file mode 100644 index 3354bfb..0000000 --- a/share/cmake-3.18/Modules/CheckFortranSourceCompiles.cmake +++ /dev/null
@@ -1,166 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckFortranSourceCompiles --------------------------- - -Check if given Fortran source compiles and links into an executable. - -.. command:: check_fortran_source_compiles - - .. code-block:: cmake - - check_fortran_source_compiles(<code> <resultVar> - [FAIL_REGEX <regex>...] - [SRC_EXT <extension>] - ) - - Checks that the source supplied in ``<code>`` can be compiled as a Fortran - source file and linked as an executable. The ``<code>`` must be a Fortran program - containing at least an ``end`` statement--for example: - - .. code-block:: cmake - - check_fortran_source_compiles("character :: b; error stop b; end" F2018ESTOPOK SRC_EXT F90) - - This command can help avoid costly build processes when a compiler lacks support - for a necessary feature, or a particular vendor library is not compatible with - the Fortran compiler version being used. This generate-time check may advise the - user of such before the main build process. See also the - :command:`check_fortran_source_runs` command to actually run the compiled code. - - The result will be stored in the internal cache - variable ``<resultVar>``, with a boolean true value for success and boolean - false for failure. - - If ``FAIL_REGEX`` is provided, then failure is determined by checking - if anything in the output matches any of the specified regular expressions. - - By default, the test source file will be given a ``.F`` file extension. The - ``SRC_EXT`` option can be used to override this with ``.<extension>`` instead-- - ``.F90`` is a typical choice. - - The underlying check is performed by the :command:`try_compile` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_fortran_source_compiles()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_Fortran_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_compile()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_Fortran_SOURCE_COMPILES SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_FAIL_REGEX) - set(_SRC_EXT) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(FAIL_REGEX|SRC_EXT)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - if(NOT _SRC_EXT) - set(_SRC_EXT F) - endif() - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.${_SRC_EXT}" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_compile(${VAR} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.${_SRC_EXT} - COMPILE_DEFINITIONS -D${VAR} ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${CMAKE_REQUIRED_FLAGS} - "${CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - foreach(_regex ${_FAIL_REGEX}) - if("${OUTPUT}" MATCHES "${_regex}") - set(${VAR} 0) - endif() - endforeach() - - if(${VAR}) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Fortran SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Fortran SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckFortranSourceRuns.cmake b/share/cmake-3.18/Modules/CheckFortranSourceRuns.cmake deleted file mode 100644 index f858b84..0000000 --- a/share/cmake-3.18/Modules/CheckFortranSourceRuns.cmake +++ /dev/null
@@ -1,173 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckFortranSourceRuns ----------------------- - -Check if given Fortran source compiles and links into an executable and can -subsequently be run. - -.. command:: check_fortran_source_runs - - .. code-block:: cmake - - check_fortran_source_runs(<code> <resultVar> - [SRC_EXT <extension>]) - - Check that the source supplied in ``<code>`` can be compiled as a Fortran source - file, linked as an executable and then run. The ``<code>`` must be a Fortran program - containing at least an ``end`` statement--for example: - - .. code-block:: cmake - - check_fortran_source_runs("real :: x[*]; call co_sum(x); end" F2018coarrayOK) - - This command can help avoid costly build processes when a compiler lacks support - for a necessary feature, or a particular vendor library is not compatible with - the Fortran compiler version being used. Some of these failures only occur at runtime - instead of linktime, and a trivial runtime example can catch the issue before the - main build process. - - If the ``<code>`` could be built and run - successfully, the internal cache variable specified by ``<resultVar>`` will - be set to 1, otherwise it will be set to an value that evaluates to boolean - false (e.g. an empty string or an error message). - - By default, the test source file will be given a ``.F90`` file extension. The - ``SRC_EXT`` option can be used to override this with ``.<extension>`` instead. - - The underlying check is performed by the :command:`try_run` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_fortran_source_runs()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_Fortran_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_run` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_Fortran_SOURCE_RUNS SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_SRC_EXT) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(SRC_EXT)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - if(NOT _SRC_EXT) - set(_SRC_EXT F90) - endif() - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.${_SRC_EXT}" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_run(${VAR}_EXITCODE ${VAR}_COMPILED - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.${_SRC_EXT} - COMPILE_DEFINITIONS -D${VAR} ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_Fortran_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_Fortran_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${CMAKE_REQUIRED_FLAGS} - -DCMAKE_SKIP_RPATH:BOOL=${CMAKE_SKIP_RPATH} - "${CHECK_Fortran_SOURCE_COMPILES_ADD_INCLUDES}" - COMPILE_OUTPUT_VARIABLE OUTPUT - RUN_OUTPUT_VARIABLE RUN_OUTPUT) - - # if it did not compile make the return value fail code of 1 - if(NOT ${VAR}_COMPILED) - set(${VAR}_EXITCODE 1) - endif() - # if the return value was 0 then it worked - if("${${VAR}_EXITCODE}" EQUAL 0) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Fortran SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}}\n" - "Source file was:\n${SOURCE}\n") - else() - if(CMAKE_CROSSCOMPILING AND "${${VAR}_EXITCODE}" MATCHES "FAILED_TO_RUN") - set(${VAR} "${${VAR}_EXITCODE}") - else() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Fortran SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}_EXITCODE}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckFunctionExists.cmake b/share/cmake-3.18/Modules/CheckFunctionExists.cmake deleted file mode 100644 index 136da89..0000000 --- a/share/cmake-3.18/Modules/CheckFunctionExists.cmake +++ /dev/null
@@ -1,119 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckFunctionExists -------------------- - -Check if a C function can be linked - -.. command:: check_function_exists - - .. code-block:: cmake - - check_function_exists(<function> <variable>) - - Checks that the ``<function>`` is provided by libraries on the system and store - the result in a ``<variable>``, which will be created as an internal - cache variable. - -The following variables may be set before calling this macro to modify the -way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -.. note:: - - Prefer using :Module:`CheckSymbolExists` instead of this module, - for the following reasons: - - * ``check_function_exists()`` can't detect functions that are inlined - in headers or specified as a macro. - - * ``check_function_exists()`` can't detect anything in the 32-bit - versions of the Win32 API, because of a mismatch in calling conventions. - - * ``check_function_exists()`` only verifies linking, it does not verify - that the function is declared in system headers. -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_FUNCTION_EXISTS FUNCTION VARIABLE) - if(NOT DEFINED "${VARIABLE}" OR "x${${VARIABLE}}" STREQUAL "x${VARIABLE}") - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-DCHECK_FUNCTION_EXISTS=${FUNCTION} ${CMAKE_REQUIRED_FLAGS}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${FUNCTION}") - endif() - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_FUNCTION_EXISTS_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_FUNCTION_EXISTS_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_FUNCTION_EXISTS_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_FUNCTION_EXISTS_ADD_INCLUDES) - endif() - - if(CMAKE_C_COMPILER_LOADED) - set(_cfe_source ${CMAKE_ROOT}/Modules/CheckFunctionExists.c) - elseif(CMAKE_CXX_COMPILER_LOADED) - set(_cfe_source ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckFunctionExists/CheckFunctionExists.cxx) - configure_file(${CMAKE_ROOT}/Modules/CheckFunctionExists.c "${_cfe_source}" COPYONLY) - else() - message(FATAL_ERROR "CHECK_FUNCTION_EXISTS needs either C or CXX language enabled") - endif() - - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${_cfe_source} - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_FUNCTION_EXISTS_ADD_LINK_OPTIONS} - ${CHECK_FUNCTION_EXISTS_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - "${CHECK_FUNCTION_EXISTS_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - unset(_cfe_source) - - if(${VARIABLE}) - set(${VARIABLE} 1 CACHE INTERNAL "Have function ${FUNCTION}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the function ${FUNCTION} exists passed with the following output:\n" - "${OUTPUT}\n\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have function ${FUNCTION}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the function ${FUNCTION} exists failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckIPOSupported.cmake b/share/cmake-3.18/Modules/CheckIPOSupported.cmake deleted file mode 100644 index 90a9f61..0000000 --- a/share/cmake-3.18/Modules/CheckIPOSupported.cmake +++ /dev/null
@@ -1,239 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckIPOSupported ------------------ - -Check whether the compiler supports an interprocedural optimization (IPO/LTO). -Use this before enabling the :prop_tgt:`INTERPROCEDURAL_OPTIMIZATION` target -property. - -.. command:: check_ipo_supported - - :: - - check_ipo_supported([RESULT <result>] [OUTPUT <output>] - [LANGUAGES <lang>...]) - - Options are: - - ``RESULT <result>`` - Set ``<result>`` variable to ``YES`` if IPO is supported by the - compiler and ``NO`` otherwise. If this option is not given then - the command will issue a fatal error if IPO is not supported. - ``OUTPUT <output>`` - Set ``<output>`` variable with details about any error. - ``LANGUAGES <lang>...`` - Specify languages whose compilers to check. - Languages ``C``, ``CXX``, and ``Fortran`` are supported. - -It makes no sense to use this module when :policy:`CMP0069` is set to ``OLD`` so -module will return error in this case. See policy :policy:`CMP0069` for details. - -Examples -^^^^^^^^ - -.. code-block:: cmake - - check_ipo_supported() # fatal error if IPO is not supported - set_property(TARGET foo PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE) - -.. code-block:: cmake - - # Optional IPO. Do not use IPO if it's not supported by compiler. - check_ipo_supported(RESULT result OUTPUT output) - if(result) - set_property(TARGET foo PROPERTY INTERPROCEDURAL_OPTIMIZATION TRUE) - else() - message(WARNING "IPO is not supported: ${output}") - endif() - -#]=======================================================================] - -# X_RESULT - name of the final result variable -# X_OUTPUT - name of the variable with information about error -macro(_ipo_not_supported output) - if(NOT X_RESULT) - message(FATAL_ERROR "IPO is not supported (${output}).") - endif() - - set("${X_RESULT}" NO PARENT_SCOPE) - if(X_OUTPUT) - set("${X_OUTPUT}" "${output}" PARENT_SCOPE) - endif() -endmacro() - -# Run IPO/LTO test -macro(_ipo_run_language_check language) - set(testdir "${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/_CMakeLTOTest-${language}") - - file(REMOVE_RECURSE "${testdir}") - file(MAKE_DIRECTORY "${testdir}") - - set(bindir "${testdir}/bin") - set(srcdir "${testdir}/src") - - file(MAKE_DIRECTORY "${bindir}") - file(MAKE_DIRECTORY "${srcdir}") - - set(TRY_COMPILE_PROJECT_NAME "lto-test") - - set(try_compile_src "${CMAKE_ROOT}/Modules/CheckIPOSupported") - - # Use: - # * TRY_COMPILE_PROJECT_NAME - # * CMAKE_VERSION - configure_file( - "${try_compile_src}/CMakeLists-${language}.txt.in" - "${srcdir}/CMakeLists.txt" - @ONLY - ) - - string(COMPARE EQUAL "${language}" "C" is_c) - string(COMPARE EQUAL "${language}" "CXX" is_cxx) - string(COMPARE EQUAL "${language}" "Fortran" is_fortran) - - if(is_c) - set(copy_sources foo.c main.c) - elseif(is_cxx) - set(copy_sources foo.cpp main.cpp) - elseif(is_fortran) - set(copy_sources foo.f main.f) - else() - message(FATAL_ERROR "Language not supported") - endif() - - foreach(x ${copy_sources}) - configure_file( - "${try_compile_src}/${x}" - "${srcdir}/${x}" - COPYONLY - ) - endforeach() - - try_compile( - _IPO_LANGUAGE_CHECK_RESULT - "${bindir}" - "${srcdir}" - "${TRY_COMPILE_PROJECT_NAME}" - CMAKE_FLAGS - "-DCMAKE_VERBOSE_MAKEFILE=ON" - "-DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON" - OUTPUT_VARIABLE output - ) - set(_IPO_LANGUAGE_CHECK_RESULT "${_IPO_LANGUAGE_CHECK_RESULT}") - unset(_IPO_LANGUAGE_CHECK_RESULT CACHE) - - if(NOT _IPO_LANGUAGE_CHECK_RESULT) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "${language} compiler IPO check failed with the following output:\n" - "${output}\n") - _ipo_not_supported("check failed to compile") - if(X_OUTPUT) - set("${X_OUTPUT}" "${output}" PARENT_SCOPE) - endif() - return() - endif() -endmacro() - -function(check_ipo_supported) - cmake_policy(GET CMP0069 x) - - string(COMPARE EQUAL "${x}" "" not_set) - if(not_set) - message(FATAL_ERROR "Policy CMP0069 is not set") - endif() - - string(COMPARE EQUAL "${x}" "OLD" is_old) - if(is_old) - message(FATAL_ERROR "Policy CMP0069 set to OLD") - endif() - - set(optional) - set(one RESULT OUTPUT) - set(multiple LANGUAGES) - - # Introduce: - # * X_RESULT - # * X_OUTPUT - # * X_LANGUAGES - cmake_parse_arguments(X "${optional}" "${one}" "${multiple}" "${ARGV}") - - string(COMPARE NOTEQUAL "${X_UNPARSED_ARGUMENTS}" "" has_unparsed) - if(has_unparsed) - message(FATAL_ERROR "Unparsed arguments: ${X_UNPARSED_ARGUMENTS}") - endif() - - string(COMPARE EQUAL "${X_LANGUAGES}" "" no_languages) - if(no_languages) - # User did not set any languages, use defaults - get_property(enabled_languages GLOBAL PROPERTY ENABLED_LANGUAGES) - string(COMPARE EQUAL "${enabled_languages}" "" no_languages) - if(no_languages) - _ipo_not_supported( - "no languages found in ENABLED_LANGUAGES global property" - ) - return() - endif() - - set(languages "") - list(FIND enabled_languages "CXX" result) - if(NOT result EQUAL -1) - list(APPEND languages "CXX") - endif() - - list(FIND enabled_languages "C" result) - if(NOT result EQUAL -1) - list(APPEND languages "C") - endif() - - list(FIND enabled_languages "Fortran" result) - if(NOT result EQUAL -1) - list(APPEND languages "Fortran") - endif() - - string(COMPARE EQUAL "${languages}" "" no_languages) - if(no_languages) - _ipo_not_supported( - "no C/CXX/Fortran languages found in ENABLED_LANGUAGES global property" - ) - return() - endif() - else() - set(languages "${X_LANGUAGES}") - - set(unsupported_languages "${languages}") - list(REMOVE_ITEM unsupported_languages "C" "CXX" "Fortran") - string(COMPARE NOTEQUAL "${unsupported_languages}" "" has_unsupported) - if(has_unsupported) - _ipo_not_supported( - "language(s) '${unsupported_languages}' not supported" - ) - return() - endif() - endif() - - foreach(lang ${languages}) - if(NOT _CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE) - _ipo_not_supported("CMake doesn't support IPO for current ${lang} compiler") - return() - endif() - - if(NOT _CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER) - _ipo_not_supported("${lang} compiler doesn't support IPO") - return() - endif() - endforeach() - - if(CMAKE_GENERATOR MATCHES "^Visual Studio 9 ") - _ipo_not_supported("CMake doesn't support IPO for current generator") - return() - endif() - - foreach(x ${languages}) - _ipo_run_language_check(${x}) - endforeach() - - set("${X_RESULT}" YES PARENT_SCOPE) -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckIncludeFile.cmake b/share/cmake-3.18/Modules/CheckIncludeFile.cmake deleted file mode 100644 index 3a10473..0000000 --- a/share/cmake-3.18/Modules/CheckIncludeFile.cmake +++ /dev/null
@@ -1,130 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckIncludeFile ----------------- - -Provides a macro to check if a header file can be included in ``C``. - -.. command:: CHECK_INCLUDE_FILE - - .. code-block:: cmake - - CHECK_INCLUDE_FILE(<include> <variable> [<flags>]) - - Check if the given ``<include>`` file may be included in a ``C`` - source file and store the result in an internal cache entry named - ``<variable>``. The optional third argument may be used to add - compilation flags to the check (or use ``CMAKE_REQUIRED_FLAGS`` below). - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -See the :module:`CheckIncludeFiles` module to check for multiple headers -at once. See the :module:`CheckIncludeFileCXX` module to check for headers -using the ``CXX`` language. -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_INCLUDE_FILE INCLUDE VARIABLE) - if(NOT DEFINED "${VARIABLE}") - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_INCLUDE_FILE_C_INCLUDE_DIRS "-DINCLUDE_DIRECTORIES=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_INCLUDE_FILE_C_INCLUDE_DIRS) - endif() - set(MACRO_CHECK_INCLUDE_FILE_FLAGS ${CMAKE_REQUIRED_FLAGS}) - set(CHECK_INCLUDE_FILE_VAR ${INCLUDE}) - configure_file(${CMAKE_ROOT}/Modules/CheckIncludeFile.c.in - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckIncludeFile.c) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${INCLUDE}") - endif() - if(${ARGC} EQUAL 3) - set(CMAKE_C_FLAGS_SAVE ${CMAKE_C_FLAGS}) - string(APPEND CMAKE_C_FLAGS " ${ARGV2}") - endif() - - set(_CIF_LINK_OPTIONS) - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(_CIF_LINK_OPTIONS LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - endif() - - set(_CIF_LINK_LIBRARIES "") - if(CMAKE_REQUIRED_LIBRARIES) - cmake_policy(GET CMP0075 _CIF_CMP0075 - PARENT_SCOPE # undocumented, do not use outside of CMake - ) - if("x${_CIF_CMP0075}x" STREQUAL "xNEWx") - set(_CIF_LINK_LIBRARIES LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - elseif("x${_CIF_CMP0075}x" STREQUAL "xOLDx") - elseif(NOT _CIF_CMP0075_WARNED) - set(_CIF_CMP0075_WARNED 1) - message(AUTHOR_WARNING - "Policy CMP0075 is not set: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. " - "Run \"cmake --help-policy CMP0075\" for policy details. " - "Use the cmake_policy command to set the policy and suppress this warning." - "\n" - "CMAKE_REQUIRED_LIBRARIES is set to:\n" - " ${CMAKE_REQUIRED_LIBRARIES}\n" - "For compatibility with CMake 3.11 and below this check is ignoring it." - ) - endif() - unset(_CIF_CMP0075) - endif() - - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckIncludeFile.c - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${_CIF_LINK_OPTIONS} - ${_CIF_LINK_LIBRARIES} - CMAKE_FLAGS - -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_INCLUDE_FILE_FLAGS} - "${CHECK_INCLUDE_FILE_C_INCLUDE_DIRS}" - OUTPUT_VARIABLE OUTPUT) - unset(_CIF_LINK_OPTIONS) - unset(_CIF_LINK_LIBRARIES) - - if(${ARGC} EQUAL 3) - set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS_SAVE}) - endif() - - if(${VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - set(${VARIABLE} 1 CACHE INTERNAL "Have include ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the include file ${INCLUDE} " - "exists passed with the following output:\n" - "${OUTPUT}\n\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have include ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the include file ${INCLUDE} " - "exists failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckIncludeFileCXX.cmake b/share/cmake-3.18/Modules/CheckIncludeFileCXX.cmake deleted file mode 100644 index 496550f..0000000 --- a/share/cmake-3.18/Modules/CheckIncludeFileCXX.cmake +++ /dev/null
@@ -1,129 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckIncludeFileCXX -------------------- - -Provides a macro to check if a header file can be included in ``CXX``. - -.. command:: CHECK_INCLUDE_FILE_CXX - - .. code-block:: cmake - - CHECK_INCLUDE_FILE_CXX(<include> <variable> [<flags>]) - - Check if the given ``<include>`` file may be included in a ``CXX`` - source file and store the result in an internal cache entry named - ``<variable>``. The optional third argument may be used to add - compilation flags to the check (or use ``CMAKE_REQUIRED_FLAGS`` below). - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -See modules :module:`CheckIncludeFile` and :module:`CheckIncludeFiles` -to check for one or more ``C`` headers. -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_INCLUDE_FILE_CXX INCLUDE VARIABLE) - if(NOT DEFINED "${VARIABLE}" OR "x${${VARIABLE}}" STREQUAL "x${VARIABLE}") - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_INCLUDE_FILE_CXX_INCLUDE_DIRS "-DINCLUDE_DIRECTORIES=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_INCLUDE_FILE_CXX_INCLUDE_DIRS) - endif() - set(MACRO_CHECK_INCLUDE_FILE_FLAGS ${CMAKE_REQUIRED_FLAGS}) - set(CHECK_INCLUDE_FILE_VAR ${INCLUDE}) - configure_file(${CMAKE_ROOT}/Modules/CheckIncludeFile.cxx.in - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckIncludeFile.cxx) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for C++ include ${INCLUDE}") - endif() - if(${ARGC} EQUAL 3) - set(CMAKE_CXX_FLAGS_SAVE ${CMAKE_CXX_FLAGS}) - string(APPEND CMAKE_CXX_FLAGS " ${ARGV2}") - endif() - - set(_CIF_LINK_OPTIONS) - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(_CIF_LINK_OPTIONS LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - endif() - - set(_CIF_LINK_LIBRARIES "") - if(CMAKE_REQUIRED_LIBRARIES) - cmake_policy(GET CMP0075 _CIF_CMP0075 - PARENT_SCOPE # undocumented, do not use outside of CMake - ) - if("x${_CIF_CMP0075}x" STREQUAL "xNEWx") - set(_CIF_LINK_LIBRARIES LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - elseif("x${_CIF_CMP0075}x" STREQUAL "xOLDx") - elseif(NOT _CIF_CMP0075_WARNED) - set(_CIF_CMP0075_WARNED 1) - message(AUTHOR_WARNING - "Policy CMP0075 is not set: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. " - "Run \"cmake --help-policy CMP0075\" for policy details. " - "Use the cmake_policy command to set the policy and suppress this warning." - "\n" - "CMAKE_REQUIRED_LIBRARIES is set to:\n" - " ${CMAKE_REQUIRED_LIBRARIES}\n" - "For compatibility with CMake 3.11 and below this check is ignoring it." - ) - endif() - unset(_CIF_CMP0075) - endif() - - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckIncludeFile.cxx - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${_CIF_LINK_OPTIONS} - ${_CIF_LINK_LIBRARIES} - CMAKE_FLAGS - -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_INCLUDE_FILE_FLAGS} - "${CHECK_INCLUDE_FILE_CXX_INCLUDE_DIRS}" - OUTPUT_VARIABLE OUTPUT) - unset(_CIF_LINK_OPTIONS) - unset(_CIF_LINK_LIBRARIES) - - if(${ARGC} EQUAL 3) - set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS_SAVE}) - endif() - - if(${VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - set(${VARIABLE} 1 CACHE INTERNAL "Have include ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the include file ${INCLUDE} " - "exists passed with the following output:\n" - "${OUTPUT}\n\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have include ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the include file ${INCLUDE} " - "exists failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckIncludeFiles.cmake b/share/cmake-3.18/Modules/CheckIncludeFiles.cmake deleted file mode 100644 index 8e10cd6..0000000 --- a/share/cmake-3.18/Modules/CheckIncludeFiles.cmake +++ /dev/null
@@ -1,168 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckIncludeFiles ------------------ - -Provides a macro to check if a list of one or more header files can -be included together. - -.. command:: CHECK_INCLUDE_FILES - - .. code-block:: cmake - - CHECK_INCLUDE_FILES("<includes>" <variable> [LANGUAGE <language>]) - - Check if the given ``<includes>`` list may be included together - in a source file and store the result in an internal cache - entry named ``<variable>``. Specify the ``<includes>`` argument - as a :ref:`;-list <CMake Language Lists>` of header file names. - - If ``LANGUAGE`` is set, the specified compiler will be used to perform the - check. Acceptable values are ``C`` and ``CXX``. If not set, the C compiler - will be used if enabled. If the C compiler is not enabled, the C++ - compiler will be used if enabled. - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -See modules :module:`CheckIncludeFile` and :module:`CheckIncludeFileCXX` -to check for a single header file in ``C`` or ``CXX`` languages. -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_INCLUDE_FILES INCLUDE VARIABLE) - if(NOT DEFINED "${VARIABLE}") - set(CMAKE_CONFIGURABLE_FILE_CONTENT "/* */\n") - - if("x${ARGN}" STREQUAL "x") - if(CMAKE_C_COMPILER_LOADED) - set(_lang C) - elseif(CMAKE_CXX_COMPILER_LOADED) - set(_lang CXX) - else() - message(FATAL_ERROR "CHECK_INCLUDE_FILES needs either C or CXX language enabled.\n") - endif() - elseif("x${ARGN}" MATCHES "^xLANGUAGE;([a-zA-Z]+)$") - set(_lang "${CMAKE_MATCH_1}") - elseif("x${ARGN}" MATCHES "^xLANGUAGE$") - message(FATAL_ERROR "No languages listed for LANGUAGE option.\nSupported languages: C, CXX.\n") - else() - message(FATAL_ERROR "Unknown arguments:\n ${ARGN}\n") - endif() - - if(_lang STREQUAL "C") - set(src ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckIncludeFiles/${VARIABLE}.c) - elseif(_lang STREQUAL "CXX") - set(src ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckIncludeFiles/${VARIABLE}.cpp) - else() - message(FATAL_ERROR "Unknown language:\n ${_lang}\nSupported languages: C, CXX.\n") - endif() - - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_INCLUDE_FILES_INCLUDE_DIRS "-DINCLUDE_DIRECTORIES=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_INCLUDE_FILES_INCLUDE_DIRS) - endif() - set(CHECK_INCLUDE_FILES_CONTENT "/* */\n") - set(MACRO_CHECK_INCLUDE_FILES_FLAGS ${CMAKE_REQUIRED_FLAGS}) - foreach(FILE ${INCLUDE}) - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT - "#include <${FILE}>\n") - endforeach() - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT - "\n\nint main(void){return 0;}\n") - configure_file("${CMAKE_ROOT}/Modules/CMakeConfigurableFile.in" - "${src}" @ONLY) - - set(_INCLUDE ${INCLUDE}) # remove empty elements - if("${_INCLUDE}" MATCHES "^([^;]+);.+;([^;]+)$") - list(LENGTH _INCLUDE _INCLUDE_LEN) - set(_description "${_INCLUDE_LEN} include files ${CMAKE_MATCH_1}, ..., ${CMAKE_MATCH_2}") - elseif("${_INCLUDE}" MATCHES "^([^;]+);([^;]+)$") - set(_description "include files ${CMAKE_MATCH_1}, ${CMAKE_MATCH_2}") - else() - set(_description "include file ${_INCLUDE}") - endif() - - set(_CIF_LINK_OPTIONS) - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(_CIF_LINK_OPTIONS LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - endif() - - set(_CIF_LINK_LIBRARIES "") - if(CMAKE_REQUIRED_LIBRARIES) - cmake_policy(GET CMP0075 _CIF_CMP0075 - PARENT_SCOPE # undocumented, do not use outside of CMake - ) - if("x${_CIF_CMP0075}x" STREQUAL "xNEWx") - set(_CIF_LINK_LIBRARIES LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - elseif("x${_CIF_CMP0075}x" STREQUAL "xOLDx") - elseif(NOT _CIF_CMP0075_WARNED) - set(_CIF_CMP0075_WARNED 1) - message(AUTHOR_WARNING - "Policy CMP0075 is not set: Include file check macros honor CMAKE_REQUIRED_LIBRARIES. " - "Run \"cmake --help-policy CMP0075\" for policy details. " - "Use the cmake_policy command to set the policy and suppress this warning." - "\n" - "CMAKE_REQUIRED_LIBRARIES is set to:\n" - " ${CMAKE_REQUIRED_LIBRARIES}\n" - "For compatibility with CMake 3.11 and below this check is ignoring it." - ) - endif() - unset(_CIF_CMP0075) - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${_description}") - endif() - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${src} - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${_CIF_LINK_OPTIONS} - ${_CIF_LINK_LIBRARIES} - CMAKE_FLAGS - -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_INCLUDE_FILES_FLAGS} - "${CHECK_INCLUDE_FILES_INCLUDE_DIRS}" - OUTPUT_VARIABLE OUTPUT) - unset(_CIF_LINK_OPTIONS) - unset(_CIF_LINK_LIBRARIES) - if(${VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - set(${VARIABLE} 1 CACHE INTERNAL "Have include ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if files ${INCLUDE} " - "exist passed with the following output:\n" - "${OUTPUT}\n\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have includes ${INCLUDE}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if files ${INCLUDE} " - "exist failed with the following output:\n" - "${OUTPUT}\nSource:\n${CMAKE_CONFIGURABLE_FILE_CONTENT}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckLanguage.cmake b/share/cmake-3.18/Modules/CheckLanguage.cmake deleted file mode 100644 index d67d8d3..0000000 --- a/share/cmake-3.18/Modules/CheckLanguage.cmake +++ /dev/null
@@ -1,106 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckLanguage -------------- - -Check if a language can be enabled - -Usage: - -:: - - check_language(<lang>) - -where ``<lang>`` is a language that may be passed to :command:`enable_language` -such as ``Fortran``. If :variable:`CMAKE_<LANG>_COMPILER` is already defined -the check does nothing. Otherwise it tries enabling the language in a -test project. The result is cached in :variable:`CMAKE_<LANG>_COMPILER` -as the compiler that was found, or ``NOTFOUND`` if the language cannot be -enabled. For CUDA which can have an explicit host compiler, the cache -:variable:`CMAKE_CUDA_HOST_COMPILER` variable will be set if it was required -for compilation. - -Example: - -:: - - check_language(Fortran) - if(CMAKE_Fortran_COMPILER) - enable_language(Fortran) - else() - message(STATUS "No Fortran support") - endif() -#]=======================================================================] - -include_guard(GLOBAL) - -macro(check_language lang) - if(NOT DEFINED CMAKE_${lang}_COMPILER) - set(_desc "Looking for a ${lang} compiler") - message(CHECK_START "${_desc}") - file(REMOVE_RECURSE ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/Check${lang}) - - set(extra_compiler_variables) - if(${lang} STREQUAL CUDA) - set(extra_compiler_variables "set(CMAKE_CUDA_HOST_COMPILER \\\"\${CMAKE_CUDA_HOST_COMPILER}\\\")") - endif() - - set(_cl_content - "cmake_minimum_required(VERSION ${CMAKE_VERSION}) -project(Check${lang} ${lang}) -file(WRITE \"\${CMAKE_CURRENT_BINARY_DIR}/result.cmake\" - \"set(CMAKE_${lang}_COMPILER \\\"\${CMAKE_${lang}_COMPILER}\\\")\\n\" - \"${extra_compiler_variables}\\n\" - )" - ) - - file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/Check${lang}/CMakeLists.txt" - "${_cl_content}") - if(CMAKE_GENERATOR_INSTANCE) - set(_D_CMAKE_GENERATOR_INSTANCE "-DCMAKE_GENERATOR_INSTANCE:INTERNAL=${CMAKE_GENERATOR_INSTANCE}") - else() - set(_D_CMAKE_GENERATOR_INSTANCE "") - endif() - if(CMAKE_GENERATOR MATCHES "^(Xcode$|Green Hills MULTI$|Visual Studio)") - set(_D_CMAKE_MAKE_PROGRAM "") - else() - set(_D_CMAKE_MAKE_PROGRAM "-DCMAKE_MAKE_PROGRAM:FILEPATH=${CMAKE_MAKE_PROGRAM}") - endif() - execute_process( - WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/Check${lang} - COMMAND ${CMAKE_COMMAND} . -G ${CMAKE_GENERATOR} - -A "${CMAKE_GENERATOR_PLATFORM}" - -T "${CMAKE_GENERATOR_TOOLSET}" - ${_D_CMAKE_GENERATOR_INSTANCE} - ${_D_CMAKE_MAKE_PROGRAM} - OUTPUT_VARIABLE _cl_output - ERROR_VARIABLE _cl_output - RESULT_VARIABLE _cl_result - ) - include(${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/Check${lang}/result.cmake OPTIONAL) - if(CMAKE_${lang}_COMPILER AND "${_cl_result}" STREQUAL "0") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "${_desc} passed with the following output:\n" - "${_cl_output}\n") - set(_CHECK_COMPILER_STATUS CHECK_PASS) - else() - set(CMAKE_${lang}_COMPILER NOTFOUND) - set(_CHECK_COMPILER_STATUS CHECK_FAIL) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "${_desc} failed with the following output:\n" - "${_cl_output}\n") - endif() - message(${_CHECK_COMPILER_STATUS} "${CMAKE_${lang}_COMPILER}") - set(CMAKE_${lang}_COMPILER "${CMAKE_${lang}_COMPILER}" CACHE FILEPATH "${lang} compiler") - mark_as_advanced(CMAKE_${lang}_COMPILER) - - if(CMAKE_${lang}_HOST_COMPILER) - message(STATUS "Looking for a ${lang} host compiler - ${CMAKE_${lang}_HOST_COMPILER}") - set(CMAKE_${lang}_HOST_COMPILER "${CMAKE_${lang}_HOST_COMPILER}" CACHE FILEPATH "${lang} host compiler") - mark_as_advanced(CMAKE_${lang}_HOST_COMPILER) - endif() - - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckLibraryExists.cmake b/share/cmake-3.18/Modules/CheckLibraryExists.cmake deleted file mode 100644 index 6470dfd..0000000 --- a/share/cmake-3.18/Modules/CheckLibraryExists.cmake +++ /dev/null
@@ -1,99 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckLibraryExists ------------------- - -Check if the function exists. - -.. command:: CHECK_LIBRARY_EXISTS - - .. code-block:: cmake - - CHECK_LIBRARY_EXISTS(LIBRARY FUNCTION LOCATION VARIABLE) - - :: - - LIBRARY - the name of the library you are looking for - FUNCTION - the name of the function - LOCATION - location where the library should be found - VARIABLE - variable to store the result - Will be created as an internal cache variable. - - - -The following variables may be set before calling this macro to modify -the way the check is run: - -:: - - CMAKE_REQUIRED_FLAGS = string of compile command line flags - CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar) - CMAKE_REQUIRED_LINK_OPTIONS = list of options to pass to link command - CMAKE_REQUIRED_LIBRARIES = list of libraries to link - CMAKE_REQUIRED_QUIET = execute quietly without messages -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_LIBRARY_EXISTS LIBRARY FUNCTION LOCATION VARIABLE) - if(NOT DEFINED "${VARIABLE}") - set(MACRO_CHECK_LIBRARY_EXISTS_DEFINITION - "-DCHECK_FUNCTION_EXISTS=${FUNCTION} ${CMAKE_REQUIRED_FLAGS}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${FUNCTION} in ${LIBRARY}") - endif() - set(CHECK_LIBRARY_EXISTS_LINK_OPTIONS) - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_LIBRARY_EXISTS_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - endif() - set(CHECK_LIBRARY_EXISTS_LIBRARIES ${LIBRARY}) - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_LIBRARY_EXISTS_LIBRARIES - ${CHECK_LIBRARY_EXISTS_LIBRARIES} ${CMAKE_REQUIRED_LIBRARIES}) - endif() - - if(CMAKE_C_COMPILER_LOADED) - set(_cle_source ${CMAKE_ROOT}/Modules/CheckFunctionExists.c) - elseif(CMAKE_CXX_COMPILER_LOADED) - set(_cle_source ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckLibraryExists/CheckFunctionExists.cxx) - configure_file(${CMAKE_ROOT}/Modules/CheckFunctionExists.c "${_cle_source}" COPYONLY) - else() - message(FATAL_ERROR "CHECK_FUNCTION_EXISTS needs either C or CXX language enabled") - endif() - - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${_cle_source} - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_LIBRARY_EXISTS_LINK_OPTIONS} - LINK_LIBRARIES ${CHECK_LIBRARY_EXISTS_LIBRARIES} - CMAKE_FLAGS - -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_LIBRARY_EXISTS_DEFINITION} - -DLINK_DIRECTORIES:STRING=${LOCATION} - OUTPUT_VARIABLE OUTPUT) - unset(_cle_source) - - if(${VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - set(${VARIABLE} 1 CACHE INTERNAL "Have library ${LIBRARY}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the function ${FUNCTION} exists in the ${LIBRARY} " - "passed with the following output:\n" - "${OUTPUT}\n\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have library ${LIBRARY}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the function ${FUNCTION} exists in the ${LIBRARY} " - "failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckLinkerFlag.cmake b/share/cmake-3.18/Modules/CheckLinkerFlag.cmake deleted file mode 100644 index beda5fe..0000000 --- a/share/cmake-3.18/Modules/CheckLinkerFlag.cmake +++ /dev/null
@@ -1,81 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckLinkerFlag ---------------- - -Check whether the compiler supports a given link flag. - -.. command:: check_linker_flag - - .. code-block:: cmake - - check_linker_flag(<lang> <flag> <var>) - -Check that the link ``<flag>`` is accepted by the ``<lang>`` compiler without -a diagnostic. Stores the result in an internal cache entry named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_LINK_OPTIONS`` variable -and calls the ``check_<lang>_source_compiles`` macro from the -``Check<lang>SourceCompiles`` module (:module:`CheckCSourceCompiles`, -:module:`CheckCSourceCompiles`, :module:`CheckCXXSourceCompiles`, -:module:`CheckOBJCSourceCompiles`, :module:`CheckOBJCXXSourceCompiles` or -:module:`CheckFortranSourceCompiles`). See documentation of these -modules for a listing of variables that can otherwise modify the build. - -The underlying implementation rely on :prop_tgt:`LINK_OPTIONS` property to -check the specified flag. The ``LINKER:`` prefix, as described in -:command:`target_link_options` command, can be used as well. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the link flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_<LANG>_FLAGS`, unknown flags in such variables may - cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) - -include(CMakeCheckCompilerFlagCommonPatterns) - -function(CHECK_LINKER_FLAG _lang _flag _var) - get_property (_supported_languages GLOBAL PROPERTY ENABLED_LANGUAGES) - if (NOT _lang IN_LIST _supported_languages) - message (SEND_ERROR "check_linker_flag: ${_lang}: unknown language.") - return() - endif() - - include (Check${_lang}SourceCompiles) - - set(CMAKE_REQUIRED_LINK_OPTIONS "${_flag}") - - # Normalize locale during test compilation. - set(_locale_vars LC_ALL LC_MESSAGES LANG) - foreach(v IN LISTS _locale_vars) - set(_locale_vars_saved_${v} "$ENV{${v}}") - set(ENV{${v}} C) - endforeach() - - if (_lang MATCHES "^(C|CXX)$") - set (_source "int main() { return 0; }") - elseif (_lang STREQUAL "Fortran") - set (_source " program test\n stop\n end program") - elseif (_lang MATCHES "^(OBJC|OBJCXX)$") - set (_source "#ifndef __OBJC__\n# error \"Not an Objective-C++ compiler\"\n#endif\nint main(void) { return 0; }") - else() - message (SEND_ERROR "check_linker_flag: ${_lang}: unsupported language.") - return() - endif() - check_compiler_flag_common_patterns(_common_patterns) - - cmake_language (CALL check_${_lang}_source_compiles "${_source}" ${_var} ${_common_patterns}) - - foreach(v IN LISTS _locale_vars) - set(ENV{${v}} ${_locale_vars_saved_${v}}) - endforeach() - set(${_var} "${${_var}}" PARENT_SCOPE) -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckOBJCCompilerFlag.cmake b/share/cmake-3.18/Modules/CheckOBJCCompilerFlag.cmake deleted file mode 100644 index 1d975da..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCCompilerFlag.cmake +++ /dev/null
@@ -1,64 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCCompilerFlag ---------------------- - -Check whether the Objective-C compiler supports a given flag. - -.. command:: check_objc_compiler_flag - - .. code-block:: cmake - - check_objc_compiler_flag(<flag> <var>) - - Check that the ``<flag>`` is accepted by the compiler without - a diagnostic. Stores the result in an internal cache entry - named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_DEFINITIONS`` variable -and calls the ``check_objc_source_compiles`` macro from the -:module:`CheckOBJCSourceCompiles` module. See documentation of that -module for a listing of variables that can otherwise modify the build. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_OBJC_FLAGS <CMAKE_<LANG>_FLAGS>`, unknown flags - in such variables may cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckOBJCSourceCompiles) -include(CMakeCheckCompilerFlagCommonPatterns) - -macro (CHECK_OBJC_COMPILER_FLAG _FLAG _RESULT) - set(SAFE_CMAKE_REQUIRED_DEFINITIONS "${CMAKE_REQUIRED_DEFINITIONS}") - set(CMAKE_REQUIRED_DEFINITIONS "${_FLAG}") - - # Normalize locale during test compilation. - set(_CheckOBJCCompilerFlag_LOCALE_VARS LC_ALL LC_MESSAGES LANG) - foreach(v ${_CheckOBJCCompilerFlag_LOCALE_VARS}) - set(_CheckOBJCCompilerFlag_SAVED_${v} "$ENV{${v}}") - set(ENV{${v}} OBJC) - endforeach() - CHECK_COMPILER_FLAG_COMMON_PATTERNS(_CheckOBJCCompilerFlag_COMMON_PATTERNS) - CHECK_OBJC_SOURCE_COMPILES("#ifndef __OBJC__\n# error \"Not an Objective-C compiler\"\n#endif\nint main(void) { return 0; }" ${_RESULT} - # Some compilers do not fail with a bad flag - FAIL_REGEX "command line option .* is valid for .* but not for Objective-C" # GNU - FAIL_REGEX "argument unused during compilation: .*" # Clang - ${_CheckOBJCCompilerFlag_COMMON_PATTERNS} - ) - foreach(v ${_CheckOBJCCompilerFlag_LOCALE_VARS}) - set(ENV{${v}} ${_CheckOBJCCompilerFlag_SAVED_${v}}) - unset(_CheckOBJCCompilerFlag_SAVED_${v}) - endforeach() - unset(_CheckOBJCCompilerFlag_LOCALE_VARS) - unset(_CheckOBJCCompilerFlag_COMMON_PATTERNS) - - set (CMAKE_REQUIRED_DEFINITIONS "${SAFE_CMAKE_REQUIRED_DEFINITIONS}") -endmacro ()
diff --git a/share/cmake-3.18/Modules/CheckOBJCSourceCompiles.cmake b/share/cmake-3.18/Modules/CheckOBJCSourceCompiles.cmake deleted file mode 100644 index 601f1fa..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCSourceCompiles.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCSourceCompiles ------------------------ - -Check if given Objective-C source compiles and links into an executable. - -.. command:: check_objc_source_compiles - - .. code-block:: cmake - - check_objc_source_compiles(<code> <resultVar> - [FAIL_REGEX <regex1> [<regex2>...]]) - - Check that the source supplied in ``<code>`` can be compiled as a Objectie-C source - file and linked as an executable (so it must contain at least a ``main()`` - function). The result will be stored in the internal cache variable specified - by ``<resultVar>``, with a boolean true value for success and boolean false - for failure. If ``FAIL_REGEX`` is provided, then failure is determined by - checking if anything in the output matches any of the specified regular - expressions. - - The underlying check is performed by the :command:`try_compile` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_objc_source_compiles()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_OBJC_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_compile()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_OBJC_SOURCE_COMPILES SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_FAIL_REGEX) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(FAIL_REGEX)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.m" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_compile(${VAR} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.m - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - "${CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - foreach(_regex ${_FAIL_REGEX}) - if("${OUTPUT}" MATCHES "${_regex}") - set(${VAR} 0) - endif() - endforeach() - - if(${VAR}) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Objective-C SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Objective-C SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckOBJCSourceRuns.cmake b/share/cmake-3.18/Modules/CheckOBJCSourceRuns.cmake deleted file mode 100644 index 6684693..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCSourceRuns.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCSourceRuns -------------------- - -Check if given Objective-C source compiles and links into an executable and can -subsequently be run. - -.. command:: check_objc_source_runs - - .. code-block:: cmake - - check_objc_source_runs(<code> <resultVar>) - - Check that the source supplied in ``<code>`` can be compiled as a Objective-C source - file, linked as an executable and then run. The ``<code>`` must contain at - least a ``main()`` function. If the ``<code>`` could be built and run - successfully, the internal cache variable specified by ``<resultVar>`` will - be set to 1, otherwise it will be set to an value that evaluates to boolean - false (e.g. an empty string or an error message). - - The underlying check is performed by the :command:`try_run` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_objc_source_runs()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_OBJC_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_run` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_OBJC_SOURCE_RUNS SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.m" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_run(${VAR}_EXITCODE ${VAR}_COMPILED - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.m - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_OBJC_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_OBJC_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - -DCMAKE_SKIP_RPATH:BOOL=${CMAKE_SKIP_RPATH} - "${CHECK_OBJC_SOURCE_COMPILES_ADD_INCLUDES}" - COMPILE_OUTPUT_VARIABLE OUTPUT - RUN_OUTPUT_VARIABLE RUN_OUTPUT) - # if it did not compile make the return value fail code of 1 - if(NOT ${VAR}_COMPILED) - set(${VAR}_EXITCODE 1) - endif() - # if the return value was 0 then it worked - if("${${VAR}_EXITCODE}" EQUAL 0) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Objective-C SOURCE FILE Test ${VAR} succeeded with the following compile output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}}\n" - "Source file was:\n${SOURCE}\n") - else() - if(CMAKE_CROSSCOMPILING AND "${${VAR}_EXITCODE}" MATCHES "FAILED_TO_RUN") - set(${VAR} "${${VAR}_EXITCODE}") - else() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Objective-C SOURCE FILE Test ${VAR} failed with the following compile output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}_EXITCODE}\n" - "Source file was:\n${SOURCE}\n") - - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckOBJCXXCompilerFlag.cmake b/share/cmake-3.18/Modules/CheckOBJCXXCompilerFlag.cmake deleted file mode 100644 index c32741b..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCXXCompilerFlag.cmake +++ /dev/null
@@ -1,64 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCXXCompilerFlag ------------------------ - -Check whether the Objective-C++ compiler supports a given flag. - -.. command:: check_objcxx_compiler_flag - - .. code-block:: cmake - - check_objcxx_compiler_flag(<flag> <var>) - - Check that the ``<flag>`` is accepted by the compiler without - a diagnostic. Stores the result in an internal cache entry - named ``<var>``. - -This command temporarily sets the ``CMAKE_REQUIRED_DEFINITIONS`` variable -and calls the ``check_objcxx_source_compiles`` macro from the -:module:`CheckOBJCXXSourceCompiles` module. See documentation of that -module for a listing of variables that can otherwise modify the build. - -A positive result from this check indicates only that the compiler did not -issue a diagnostic message when given the flag. Whether the flag has any -effect or even a specific one is beyond the scope of this module. - -.. note:: - Since the :command:`try_compile` command forwards flags from variables - like :variable:`CMAKE_OBJCXX_FLAGS <CMAKE_<LANG>_FLAGS>`, unknown flags - in such variables may cause a false negative for this check. -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckOBJCXXSourceCompiles) -include(CMakeCheckCompilerFlagCommonPatterns) - -macro (CHECK_OBJCXX_COMPILER_FLAG _FLAG _RESULT) - set(SAFE_CMAKE_REQUIRED_DEFINITIONS "${CMAKE_REQUIRED_DEFINITIONS}") - set(CMAKE_REQUIRED_DEFINITIONS "${_FLAG}") - - # Normalize locale during test compilation. - set(_CheckOBJCXXCompilerFlag_LOCALE_VARS LC_ALL LC_MESSAGES LANG) - foreach(v ${_CheckOBJCXXCompilerFlag_LOCALE_VARS}) - set(_CheckOBJCXXCompilerFlag_SAVED_${v} "$ENV{${v}}") - set(ENV{${v}} OBJCXX) - endforeach() - CHECK_COMPILER_FLAG_COMMON_PATTERNS(_CheckOBJCXXCompilerFlag_COMMON_PATTERNS) - CHECK_OBJCXX_SOURCE_COMPILES("#ifndef __OBJC__\n# error \"Not an Objective-C++ compiler\"\n#endif\nint main(void) { return 0; }" ${_RESULT} - # Some compilers do not fail with a bad flag - FAIL_REGEX "command line option .* is valid for .* but not for Objective-C\\\\+\\\\+" # GNU - FAIL_REGEX "argument unused during compilation: .*" # Clang - ${_CheckOBJCXXCompilerFlag_COMMON_PATTERNS} - ) - foreach(v ${_CheckOBJCXXCompilerFlag_LOCALE_VARS}) - set(ENV{${v}} ${_CheckOBJCXXCompilerFlag_SAVED_${v}}) - unset(_CheckOBJCXXCompilerFlag_SAVED_${v}) - endforeach() - unset(_CheckOBJCXXCompilerFlag_LOCALE_VARS) - unset(_CheckOBJCXXCompilerFlag_COMMON_PATTERNS) - - set (CMAKE_REQUIRED_DEFINITIONS "${SAFE_CMAKE_REQUIRED_DEFINITIONS}") -endmacro ()
diff --git a/share/cmake-3.18/Modules/CheckOBJCXXSourceCompiles.cmake b/share/cmake-3.18/Modules/CheckOBJCXXSourceCompiles.cmake deleted file mode 100644 index 2ee79f4..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCXXSourceCompiles.cmake +++ /dev/null
@@ -1,146 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCXXSourceCompiles -------------------------- - -Check if given Objective-C++ source compiles and links into an executable. - -.. command:: check_objcxx_source_compiles - - .. code-block:: cmake - - check_objcxx_source_compiles(<code> <resultVar> - [FAIL_REGEX <regex1> [<regex2>...]]) - - Check that the source supplied in ``<code>`` can be compiled as a Objective-C++ source - file and linked as an executable (so it must contain at least a ``main()`` - function). The result will be stored in the internal cache variable specified - by ``<resultVar>``, with a boolean true value for success and boolean false - for failure. If ``FAIL_REGEX`` is provided, then failure is determined by - checking if anything in the output matches any of the specified regular - expressions. - - The underlying check is performed by the :command:`try_compile` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_objcxx_source_compiles()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_OBJCXX_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_compile()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_compile` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_compile` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_OBJCXX_SOURCE_COMPILES SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(_FAIL_REGEX) - set(_key) - foreach(arg ${ARGN}) - if("${arg}" MATCHES "^(FAIL_REGEX)$") - set(_key "${arg}") - elseif(_key) - list(APPEND _${_key} "${arg}") - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.mm" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_compile(${VAR} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.mm - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - "${CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - foreach(_regex ${_FAIL_REGEX}) - if("${OUTPUT}" MATCHES "${_regex}") - set(${VAR} 0) - endif() - endforeach() - - if(${VAR}) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Objective-C++ SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Objective-C++ SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckOBJCXXSourceRuns.cmake b/share/cmake-3.18/Modules/CheckOBJCXXSourceRuns.cmake deleted file mode 100644 index 7f7e04f..0000000 --- a/share/cmake-3.18/Modules/CheckOBJCXXSourceRuns.cmake +++ /dev/null
@@ -1,145 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckOBJCXXSourceRuns ---------------------- - -Check if given Objective-C++ source compiles and links into an executable and can -subsequently be run. - -.. command:: check_objcxx_source_runs - - .. code-block:: cmake - - check_objcxx_source_runs(<code> <resultVar>) - - Check that the source supplied in ``<code>`` can be compiled as a Objective-C++ source - file, linked as an executable and then run. The ``<code>`` must contain at - least a ``main()`` function. If the ``<code>`` could be built and run - successfully, the internal cache variable specified by ``<resultVar>`` will - be set to 1, otherwise it will be set to an value that evaluates to boolean - false (e.g. an empty string or an error message). - - The underlying check is performed by the :command:`try_run` command. The - compile and link commands can be influenced by setting any of the following - variables prior to calling ``check_objcxx_source_runs()``: - - ``CMAKE_REQUIRED_FLAGS`` - Additional flags to pass to the compiler. Note that the contents of - :variable:`CMAKE_OBJCXX_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated - configuration-specific variable are automatically added to the compiler - command before the contents of ``CMAKE_REQUIRED_FLAGS``. - - ``CMAKE_REQUIRED_DEFINITIONS`` - A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form - ``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by - ``<resultVar>`` will also be added automatically. - - ``CMAKE_REQUIRED_INCLUDES`` - A :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. These will be the only header search paths used by - ``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES` - directory property will be ignored. - - ``CMAKE_REQUIRED_LINK_OPTIONS`` - A :ref:`;-list <CMake Language Lists>` of options to add to the link - command (see :command:`try_run` for further details). - - ``CMAKE_REQUIRED_LIBRARIES`` - A :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. These can be the name of system libraries or they can be - :ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for - further details). - - ``CMAKE_REQUIRED_QUIET`` - If this variable evaluates to a boolean true value, all status messages - associated with the check will be suppressed. - - The check is only performed once, with the result cached in the variable - named by ``<resultVar>``. Every subsequent CMake run will re-use this cached - value rather than performing the check again, even if the ``<code>`` changes. - In order to force the check to be re-evaluated, the variable named by - ``<resultVar>`` must be manually removed from the cache. - -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_OBJCXX_SOURCE_RUNS SOURCE VAR) - if(NOT DEFINED "${VAR}") - set(MACRO_CHECK_FUNCTION_DEFINITIONS - "-D${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES) - endif() - file(WRITE "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.mm" - "${SOURCE}\n") - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Performing Test ${VAR}") - endif() - try_run(${VAR}_EXITCODE ${VAR}_COMPILED - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/src.mm - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_OBJCXX_SOURCE_COMPILES_ADD_LINK_OPTIONS} - ${CHECK_OBJCXX_SOURCE_COMPILES_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_FUNCTION_DEFINITIONS} - -DCMAKE_SKIP_RPATH:BOOL=${CMAKE_SKIP_RPATH} - "${CHECK_OBJCXX_SOURCE_COMPILES_ADD_INCLUDES}" - COMPILE_OUTPUT_VARIABLE OUTPUT - RUN_OUTPUT_VARIABLE RUN_OUTPUT) - - # if it did not compile make the return value fail code of 1 - if(NOT ${VAR}_COMPILED) - set(${VAR}_EXITCODE 1) - endif() - # if the return value was 0 then it worked - if("${${VAR}_EXITCODE}" EQUAL 0) - set(${VAR} 1 CACHE INTERNAL "Test ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "Success") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Performing Objective-C++ SOURCE FILE Test ${VAR} succeeded with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}}\n" - "Source file was:\n${SOURCE}\n") - else() - if(CMAKE_CROSSCOMPILING AND "${${VAR}_EXITCODE}" MATCHES "FAILED_TO_RUN") - set(${VAR} "${${VAR}_EXITCODE}") - else() - set(${VAR} "" CACHE INTERNAL "Test ${VAR}") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "Failed") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Performing Objective-C++ SOURCE FILE Test ${VAR} failed with the following output:\n" - "${OUTPUT}\n" - "...and run output:\n" - "${RUN_OUTPUT}\n" - "Return value: ${${VAR}_EXITCODE}\n" - "Source file was:\n${SOURCE}\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/CheckPIESupported.cmake b/share/cmake-3.18/Modules/CheckPIESupported.cmake deleted file mode 100644 index 6d63f0b..0000000 --- a/share/cmake-3.18/Modules/CheckPIESupported.cmake +++ /dev/null
@@ -1,134 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckPIESupported ------------------ - -Check whether the linker supports Position Independent Code (PIE) or No -Position Independent Code (NO_PIE) for executables. -Use this to ensure that the :prop_tgt:`POSITION_INDEPENDENT_CODE` target -property for executables will be honored at link time. - -.. command:: check_pie_supported - - :: - - check_pie_supported([OUTPUT_VARIABLE <output>] - [LANGUAGES <lang>...]) - - Options are: - - ``OUTPUT_VARIABLE <output>`` - Set ``<output>`` variable with details about any error. - ``LANGUAGES <lang>...`` - Check the linkers used for each of the specified languages. - Supported languages are ``C``, ``CXX``, and ``Fortran``. - -It makes no sense to use this module when :policy:`CMP0083` is set to ``OLD``, -so the command will return an error in this case. See policy :policy:`CMP0083` -for details. - -Variables -^^^^^^^^^ - -For each language checked, two boolean cache variables are defined. - - ``CMAKE_<lang>_LINK_PIE_SUPPORTED`` - Set to ``YES`` if ``PIE`` is supported by the linker and ``NO`` otherwise. - ``CMAKE_<lang>_LINK_NO_PIE_SUPPORTED`` - Set to ``YES`` if ``NO_PIE`` is supported by the linker and ``NO`` otherwise. - -Examples -^^^^^^^^ - -.. code-block:: cmake - - check_pie_supported() - set_property(TARGET foo PROPERTY POSITION_INDEPENDENT_CODE TRUE) - -.. code-block:: cmake - - # Retrieve any error message. - check_pie_supported(OUTPUT_VARIABLE output LANGUAGES C) - set_property(TARGET foo PROPERTY POSITION_INDEPENDENT_CODE TRUE) - if(NOT CMAKE_C_LINK_PIE_SUPPORTED) - message(WARNING "PIE is not supported at link time: ${output}.\n" - "PIE link options will not be passed to linker.") - endif() - -#]=======================================================================] - - -include (Internal/CMakeCheckCompilerFlag) - -function (check_pie_supported) - cmake_policy(GET CMP0083 cmp0083) - - if (NOT cmp0083) - message(FATAL_ERROR "check_pie_supported: Policy CMP0083 is not set") - endif() - - if(cmp0083 STREQUAL "OLD") - message(FATAL_ERROR "check_pie_supported: Policy CMP0083 set to OLD") - endif() - - set(optional) - set(one OUTPUT_VARIABLE) - set(multiple LANGUAGES) - - cmake_parse_arguments(CHECK_PIE "${optional}" "${one}" "${multiple}" "${ARGN}") - if(CHECK_PIE_UNPARSED_ARGUMENTS) - message(FATAL_ERROR "check_pie_supported: Unparsed arguments: ${CHECK_PIE_UNPARSED_ARGUMENTS}") - endif() - - if (CHECK_PIE_LANGUAGES) - set (unsupported_languages "${CHECK_PIE_LANGUAGES}") - list (REMOVE_ITEM unsupported_languages "C" "CXX" "Fortran") - if(unsupported_languages) - message(FATAL_ERROR "check_pie_supported: language(s) '${unsupported_languages}' not supported") - endif() - else() - # User did not set any languages, use defaults - get_property (enabled_languages GLOBAL PROPERTY ENABLED_LANGUAGES) - if (NOT enabled_languages) - return() - endif() - - list (FILTER enabled_languages INCLUDE REGEX "^(C|CXX|Fortran)$") - if (NOT enabled_languages) - return() - endif() - - set (CHECK_PIE_LANGUAGES ${enabled_languages}) - endif() - - set (outputs) - - foreach(lang IN LISTS CHECK_PIE_LANGUAGES) - if(_CMAKE_${lang}_PIE_MAY_BE_SUPPORTED_BY_LINKER) - cmake_check_compiler_flag(${lang} "${CMAKE_${lang}_LINK_OPTIONS_PIE}" - CMAKE_${lang}_LINK_PIE_SUPPORTED - OUTPUT_VARIABLE output) - if (NOT CMAKE_${lang}_LINK_PIE_SUPPORTED) - string (APPEND outputs "PIE (${lang}): ${output}\n") - endif() - - cmake_check_compiler_flag(${lang} "${CMAKE_${lang}_LINK_OPTIONS_NO_PIE}" - CMAKE_${lang}_LINK_NO_PIE_SUPPORTED - OUTPUT_VARIABLE output) - if (NOT CMAKE_${lang}_LINK_NO_PIE_SUPPORTED) - string (APPEND outputs "NO_PIE (${lang}): ${output}\n") - endif() - else() - # no support at link time. Set cache variables to NO - set(CMAKE_${lang}_LINK_PIE_SUPPORTED NO CACHE INTERNAL "PIE (${lang})") - set(CMAKE_${lang}_LINK_NO_PIE_SUPPORTED NO CACHE INTERNAL "NO_PIE (${lang})") - string (APPEND outputs "PIE and NO_PIE are not supported by linker for ${lang}") - endif() - endforeach() - - if (CHECK_PIE_OUTPUT_VARIABLE) - set (${CHECK_PIE_OUTPUT_VARIABLE} "${outputs}" PARENT_SCOPE) - endif() -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckPrototypeDefinition.cmake b/share/cmake-3.18/Modules/CheckPrototypeDefinition.cmake deleted file mode 100644 index 8b06403..0000000 --- a/share/cmake-3.18/Modules/CheckPrototypeDefinition.cmake +++ /dev/null
@@ -1,125 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckPrototypeDefinition ------------------------- - -Check if the prototype we expect is correct. - -.. command:: check_prototype_definition - - .. code-block:: cmake - - check_prototype_definition(FUNCTION PROTOTYPE RETURN HEADER VARIABLE) - - :: - - FUNCTION - The name of the function (used to check if prototype exists) - PROTOTYPE- The prototype to check. - RETURN - The return value of the function. - HEADER - The header files required. - VARIABLE - The variable to store the result. - Will be created as an internal cache variable. - - Example: - - .. code-block:: cmake - - check_prototype_definition(getpwent_r - "struct passwd *getpwent_r(struct passwd *src, char *buf, int buflen)" - "NULL" - "unistd.h;pwd.h" - SOLARIS_GETPWENT_R) - -The following variables may be set before calling this function to modify -the way the check is run: - -:: - - CMAKE_REQUIRED_FLAGS = string of compile command line flags - CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar) - CMAKE_REQUIRED_INCLUDES = list of include directories - CMAKE_REQUIRED_LINK_OPTIONS = list of options to pass to link command - CMAKE_REQUIRED_LIBRARIES = list of libraries to link - CMAKE_REQUIRED_QUIET = execute quietly without messages -#]=======================================================================] - -# - -get_filename_component(__check_proto_def_dir "${CMAKE_CURRENT_LIST_FILE}" PATH) - -include_guard(GLOBAL) - -function(check_prototype_definition _FUNCTION _PROTOTYPE _RETURN _HEADER _VARIABLE) - - if (NOT DEFINED ${_VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Checking prototype ${_FUNCTION} for ${_VARIABLE}") - endif() - set(CHECK_PROTOTYPE_DEFINITION_CONTENT "/* */\n") - - set(CHECK_PROTOTYPE_DEFINITION_FLAGS ${CMAKE_REQUIRED_FLAGS}) - if (CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_PROTOTYPE_DEFINITION_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_PROTOTYPE_DEFINITION_LINK_OPTIONS) - endif() - if (CMAKE_REQUIRED_LIBRARIES) - set(CHECK_PROTOTYPE_DEFINITION_LIBS - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_PROTOTYPE_DEFINITION_LIBS) - endif() - if (CMAKE_REQUIRED_INCLUDES) - set(CMAKE_SYMBOL_EXISTS_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CMAKE_SYMBOL_EXISTS_INCLUDES) - endif() - - foreach(_FILE ${_HEADER}) - string(APPEND CHECK_PROTOTYPE_DEFINITION_HEADER - "#include <${_FILE}>\n") - endforeach() - - set(CHECK_PROTOTYPE_DEFINITION_SYMBOL ${_FUNCTION}) - set(CHECK_PROTOTYPE_DEFINITION_PROTO ${_PROTOTYPE}) - set(CHECK_PROTOTYPE_DEFINITION_RETURN ${_RETURN}) - - configure_file("${__check_proto_def_dir}/CheckPrototypeDefinition.c.in" - "${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckPrototypeDefinition.c" @ONLY) - - file(READ ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckPrototypeDefinition.c _SOURCE) - - try_compile(${_VARIABLE} - ${CMAKE_BINARY_DIR} - ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckPrototypeDefinition.c - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_PROTOTYPE_DEFINITION_LINK_OPTIONS} - ${CHECK_PROTOTYPE_DEFINITION_LIBS} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${CHECK_PROTOTYPE_DEFINITION_FLAGS} - "${CMAKE_SYMBOL_EXISTS_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - - if (${_VARIABLE}) - set(${_VARIABLE} 1 CACHE INTERNAL "Have correct prototype for ${_FUNCTION}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "True") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the prototype ${_FUNCTION} exists for ${_VARIABLE} passed with the following output:\n" - "${OUTPUT}\n\n") - else () - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "False") - endif() - set(${_VARIABLE} 0 CACHE INTERNAL "Have correct prototype for ${_FUNCTION}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the prototype ${_FUNCTION} exists for ${_VARIABLE} failed with the following output:\n" - "${OUTPUT}\n\n${_SOURCE}\n\n") - endif () - endif() - -endfunction()
diff --git a/share/cmake-3.18/Modules/CheckStructHasMember.cmake b/share/cmake-3.18/Modules/CheckStructHasMember.cmake deleted file mode 100644 index 842a8fd..0000000 --- a/share/cmake-3.18/Modules/CheckStructHasMember.cmake +++ /dev/null
@@ -1,82 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckStructHasMember --------------------- - -Check if the given struct or class has the specified member variable - -.. command:: CHECK_STRUCT_HAS_MEMBER - - .. code-block:: cmake - - CHECK_STRUCT_HAS_MEMBER(<struct> <member> <header> <variable> - [LANGUAGE <language>]) - - :: - - <struct> - the name of the struct or class you are interested in - <member> - the member which existence you want to check - <header> - the header(s) where the prototype should be declared - <variable> - variable to store the result - <language> - the compiler to use (C or CXX) - - - -The following variables may be set before calling this macro to modify -the way the check is run: - -:: - - CMAKE_REQUIRED_FLAGS = string of compile command line flags - CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar) - CMAKE_REQUIRED_INCLUDES = list of include directories - CMAKE_REQUIRED_LINK_OPTIONS = list of options to pass to link command - CMAKE_REQUIRED_LIBRARIES = list of libraries to link - CMAKE_REQUIRED_QUIET = execute quietly without messages - - -Example: - -.. code-block:: cmake - - CHECK_STRUCT_HAS_MEMBER("struct timeval" tv_sec sys/select.h - HAVE_TIMEVAL_TV_SEC LANGUAGE C) -#]=======================================================================] - -include_guard(GLOBAL) -include(CheckCSourceCompiles) -include(CheckCXXSourceCompiles) - -macro (CHECK_STRUCT_HAS_MEMBER _STRUCT _MEMBER _HEADER _RESULT) - set(_INCLUDE_FILES) - foreach (it ${_HEADER}) - string(APPEND _INCLUDE_FILES "#include <${it}>\n") - endforeach () - - if("x${ARGN}" STREQUAL "x") - set(_lang C) - elseif("x${ARGN}" MATCHES "^xLANGUAGE;([a-zA-Z]+)$") - set(_lang "${CMAKE_MATCH_1}") - else() - message(FATAL_ERROR "Unknown arguments:\n ${ARGN}\n") - endif() - - set(_CHECK_STRUCT_MEMBER_SOURCE_CODE " -${_INCLUDE_FILES} -int main() -{ - (void)sizeof(((${_STRUCT} *)0)->${_MEMBER}); - return 0; -} -") - - if("${_lang}" STREQUAL "C") - CHECK_C_SOURCE_COMPILES("${_CHECK_STRUCT_MEMBER_SOURCE_CODE}" ${_RESULT}) - elseif("${_lang}" STREQUAL "CXX") - CHECK_CXX_SOURCE_COMPILES("${_CHECK_STRUCT_MEMBER_SOURCE_CODE}" ${_RESULT}) - else() - message(FATAL_ERROR "Unknown language:\n ${_lang}\nSupported languages: C, CXX.\n") - endif() -endmacro ()
diff --git a/share/cmake-3.18/Modules/CheckSymbolExists.cmake b/share/cmake-3.18/Modules/CheckSymbolExists.cmake deleted file mode 100644 index 4f202c4..0000000 --- a/share/cmake-3.18/Modules/CheckSymbolExists.cmake +++ /dev/null
@@ -1,166 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckSymbolExists ------------------ - -Provides a macro to check if a symbol exists as a function, variable, -or macro in ``C``. - -.. command:: check_symbol_exists - - .. code-block:: cmake - - check_symbol_exists(<symbol> <files> <variable>) - - Check that the ``<symbol>`` is available after including given header - ``<files>`` and store the result in a ``<variable>``. Specify the list - of files in one argument as a semicolon-separated list. - ``<variable>`` will be created as an internal cache variable. - -If the header files define the symbol as a macro it is considered -available and assumed to work. If the header files declare the symbol -as a function or variable then the symbol must also be available for -linking (so intrinsics may not be detected). -If the symbol is a type, enum value, or intrinsic it will not be recognized -(consider using :module:`CheckTypeSize` or :module:`CheckCSourceCompiles`). -If the check needs to be done in C++, consider using -:module:`CheckCXXSymbolExists` instead. - -The following variables may be set before calling this macro to modify -the way the check is run: - -``CMAKE_REQUIRED_FLAGS`` - string of compile command line flags. -``CMAKE_REQUIRED_DEFINITIONS`` - a :ref:`;-list <CMake Language Lists>` of macros to define (-DFOO=bar). -``CMAKE_REQUIRED_INCLUDES`` - a :ref:`;-list <CMake Language Lists>` of header search paths to pass to - the compiler. -``CMAKE_REQUIRED_LINK_OPTIONS`` - a :ref:`;-list <CMake Language Lists>` of options to add to the link command. -``CMAKE_REQUIRED_LIBRARIES`` - a :ref:`;-list <CMake Language Lists>` of libraries to add to the link - command. See policy :policy:`CMP0075`. -``CMAKE_REQUIRED_QUIET`` - execute quietly without messages. - -For example: - -.. code-block:: cmake - - include(CheckSymbolExists) - - # Check for macro SEEK_SET - check_symbol_exists(SEEK_SET "stdio.h" HAVE_SEEK_SET) - # Check for function fopen - check_symbol_exists(fopen "stdio.h" HAVE_FOPEN) -#]=======================================================================] - -include_guard(GLOBAL) - -cmake_policy(PUSH) -cmake_policy(SET CMP0054 NEW) # if() quoted variables not dereferenced - -macro(CHECK_SYMBOL_EXISTS SYMBOL FILES VARIABLE) - if(CMAKE_C_COMPILER_LOADED) - __CHECK_SYMBOL_EXISTS_IMPL("${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckSymbolExists.c" "${SYMBOL}" "${FILES}" "${VARIABLE}" ) - elseif(CMAKE_CXX_COMPILER_LOADED) - __CHECK_SYMBOL_EXISTS_IMPL("${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/CheckSymbolExists.cxx" "${SYMBOL}" "${FILES}" "${VARIABLE}" ) - else() - message(FATAL_ERROR "CHECK_SYMBOL_EXISTS needs either C or CXX language enabled") - endif() -endmacro() - -macro(__CHECK_SYMBOL_EXISTS_IMPL SOURCEFILE SYMBOL FILES VARIABLE) - if(NOT DEFINED "${VARIABLE}" OR "x${${VARIABLE}}" STREQUAL "x${VARIABLE}") - set(CMAKE_CONFIGURABLE_FILE_CONTENT "/* */\n") - set(MACRO_CHECK_SYMBOL_EXISTS_FLAGS ${CMAKE_REQUIRED_FLAGS}) - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_SYMBOL_EXISTS_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_SYMBOL_EXISTS_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_SYMBOL_EXISTS_LIBS - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_SYMBOL_EXISTS_LIBS) - endif() - if(CMAKE_REQUIRED_INCLUDES) - set(CMAKE_SYMBOL_EXISTS_INCLUDES - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}") - else() - set(CMAKE_SYMBOL_EXISTS_INCLUDES) - endif() - foreach(FILE ${FILES}) - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT - "#include <${FILE}>\n") - endforeach() - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT " -int main(int argc, char** argv) -{ - (void)argv;") - set(_CSE_CHECK_NON_MACRO "return ((int*)(&${SYMBOL}))[argc];") - if("${SYMBOL}" MATCHES "^[a-zA-Z_][a-zA-Z0-9_]*$") - # The SYMBOL has a legal macro name. Test whether it exists as a macro. - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT " -#ifndef ${SYMBOL} - ${_CSE_CHECK_NON_MACRO} -#else - (void)argc; - return 0; -#endif") - else() - # The SYMBOL cannot be a macro (e.g., a template function). - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT " - ${_CSE_CHECK_NON_MACRO}") - endif() - string(APPEND CMAKE_CONFIGURABLE_FILE_CONTENT " -}") - unset(_CSE_CHECK_NON_MACRO) - - configure_file("${CMAKE_ROOT}/Modules/CMakeConfigurableFile.in" - "${SOURCEFILE}" @ONLY) - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${SYMBOL}") - endif() - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - "${SOURCEFILE}" - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_SYMBOL_EXISTS_LINK_OPTIONS} - ${CHECK_SYMBOL_EXISTS_LIBS} - CMAKE_FLAGS - -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_SYMBOL_EXISTS_FLAGS} - "${CMAKE_SYMBOL_EXISTS_INCLUDES}" - OUTPUT_VARIABLE OUTPUT) - if(${VARIABLE}) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - set(${VARIABLE} 1 CACHE INTERNAL "Have symbol ${SYMBOL}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the ${SYMBOL} " - "exist passed with the following output:\n" - "${OUTPUT}\nFile ${SOURCEFILE}:\n" - "${CMAKE_CONFIGURABLE_FILE_CONTENT}\n") - else() - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - set(${VARIABLE} "" CACHE INTERNAL "Have symbol ${SYMBOL}") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the ${SYMBOL} " - "exist failed with the following output:\n" - "${OUTPUT}\nFile ${SOURCEFILE}:\n" - "${CMAKE_CONFIGURABLE_FILE_CONTENT}\n") - endif() - unset(CMAKE_CONFIGURABLE_FILE_CONTENT) - endif() -endmacro() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CheckTypeSize.cmake b/share/cmake-3.18/Modules/CheckTypeSize.cmake deleted file mode 100644 index 2b07b7c..0000000 --- a/share/cmake-3.18/Modules/CheckTypeSize.cmake +++ /dev/null
@@ -1,270 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckTypeSize -------------- - -Check sizeof a type - -.. command:: CHECK_TYPE_SIZE - - .. code-block:: cmake - - CHECK_TYPE_SIZE(TYPE VARIABLE [BUILTIN_TYPES_ONLY] - [LANGUAGE <language>]) - - Check if the type exists and determine its size. On return, - ``HAVE_${VARIABLE}`` holds the existence of the type, and ``${VARIABLE}`` - holds one of the following: - - :: - - <size> = type has non-zero size <size> - "0" = type has arch-dependent size (see below) - "" = type does not exist - - Both ``HAVE_${VARIABLE}`` and ``${VARIABLE}`` will be created as internal - cache variables. - - Furthermore, the variable ``${VARIABLE}_CODE`` holds C preprocessor code - to define the macro ``${VARIABLE}`` to the size of the type, or leave - the macro undefined if the type does not exist. - - The variable ``${VARIABLE}`` may be ``0`` when - :variable:`CMAKE_OSX_ARCHITECTURES` has multiple architectures for building - OS X universal binaries. This indicates that the type size varies across - architectures. In this case ``${VARIABLE}_CODE`` contains C preprocessor - tests mapping from each architecture macro to the corresponding type size. - The list of architecture macros is stored in ``${VARIABLE}_KEYS``, and the - value for each key is stored in ``${VARIABLE}-${KEY}``. - - If the ``BUILTIN_TYPES_ONLY`` option is not given, the macro checks for - headers ``<sys/types.h>``, ``<stdint.h>``, and ``<stddef.h>``, and saves - results in ``HAVE_SYS_TYPES_H``, ``HAVE_STDINT_H``, and ``HAVE_STDDEF_H``. - The type size check automatically includes the available headers, thus - supporting checks of types defined in the headers. - - If ``LANGUAGE`` is set, the specified compiler will be used to perform the - check. Acceptable values are ``C`` and ``CXX``. - -Despite the name of the macro you may use it to check the size of more -complex expressions, too. To check e.g. for the size of a struct -member you can do something like this: - -.. code-block:: cmake - - check_type_size("((struct something*)0)->member" SIZEOF_MEMBER) - - - -The following variables may be set before calling this macro to modify -the way the check is run: - -:: - - CMAKE_REQUIRED_FLAGS = string of compile command line flags - CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar) - CMAKE_REQUIRED_INCLUDES = list of include directories - CMAKE_REQUIRED_LINK_OPTIONS = list of options to pass to link command - CMAKE_REQUIRED_LIBRARIES = list of libraries to link - CMAKE_REQUIRED_QUIET = execute quietly without messages - CMAKE_EXTRA_INCLUDE_FILES = list of extra headers to include -#]=======================================================================] - -include(CheckIncludeFile) -include(CheckIncludeFileCXX) - -get_filename_component(__check_type_size_dir "${CMAKE_CURRENT_LIST_FILE}" PATH) - -include_guard(GLOBAL) - -cmake_policy(PUSH) -cmake_policy(SET CMP0054 NEW) - -#----------------------------------------------------------------------------- -# Helper function. DO NOT CALL DIRECTLY. -function(__check_type_size_impl type var map builtin language) - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Check size of ${type}") - endif() - - # Include header files. - set(headers) - if(builtin) - if(HAVE_SYS_TYPES_H) - string(APPEND headers "#include <sys/types.h>\n") - endif() - if(HAVE_STDINT_H) - string(APPEND headers "#include <stdint.h>\n") - endif() - if(HAVE_STDDEF_H) - string(APPEND headers "#include <stddef.h>\n") - endif() - endif() - foreach(h ${CMAKE_EXTRA_INCLUDE_FILES}) - string(APPEND headers "#include \"${h}\"\n") - endforeach() - - # Perform the check. - - if(language STREQUAL "C") - set(src ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckTypeSize/${var}.c) - elseif(language STREQUAL "CXX") - set(src ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckTypeSize/${var}.cpp) - else() - message(FATAL_ERROR "Unknown language:\n ${language}\nSupported languages: C, CXX.\n") - endif() - set(bin ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CheckTypeSize/${var}.bin) - configure_file(${__check_type_size_dir}/CheckTypeSize.c.in ${src} @ONLY) - try_compile(HAVE_${var} ${CMAKE_BINARY_DIR} ${src} - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS} - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES} - CMAKE_FLAGS - "-DCOMPILE_DEFINITIONS:STRING=${CMAKE_REQUIRED_FLAGS}" - "-DINCLUDE_DIRECTORIES:STRING=${CMAKE_REQUIRED_INCLUDES}" - OUTPUT_VARIABLE output - COPY_FILE ${bin} - ) - - if(HAVE_${var}) - # The check compiled. Load information from the binary. - file(STRINGS ${bin} strings LIMIT_COUNT 10 REGEX "INFO:size") - - # Parse the information strings. - set(regex_size ".*INFO:size\\[0*([^]]*)\\].*") - set(regex_key " key\\[([^]]*)\\]") - set(keys) - set(code) - set(mismatch) - set(first 1) - foreach(info ${strings}) - if("${info}" MATCHES "${regex_size}") - # Get the type size. - set(size "${CMAKE_MATCH_1}") - if(first) - set(${var} ${size}) - elseif(NOT "${size}" STREQUAL "${${var}}") - set(mismatch 1) - endif() - set(first 0) - - # Get the architecture map key. - string(REGEX MATCH "${regex_key}" key "${info}") - string(REGEX REPLACE "${regex_key}" "\\1" key "${key}") - if(key) - string(APPEND code "\nset(${var}-${key} \"${size}\")") - list(APPEND keys ${key}) - endif() - endif() - endforeach() - - # Update the architecture-to-size map. - if(mismatch AND keys) - configure_file(${__check_type_size_dir}/CheckTypeSizeMap.cmake.in ${map} @ONLY) - set(${var} 0) - else() - file(REMOVE ${map}) - endif() - - if(mismatch AND NOT keys) - message(SEND_ERROR "CHECK_TYPE_SIZE found different results, consider setting CMAKE_OSX_ARCHITECTURES or CMAKE_TRY_COMPILE_OSX_ARCHITECTURES to one or no architecture !") - endif() - - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "done") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining size of ${type} passed with the following output:\n${output}\n\n") - set(${var} "${${var}}" CACHE INTERNAL "CHECK_TYPE_SIZE: sizeof(${type})") - else() - # The check failed to compile. - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "failed") - endif() - file(READ ${src} content) - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining size of ${type} failed with the following output:\n${output}\n${src}:\n${content}\n\n") - set(${var} "" CACHE INTERNAL "CHECK_TYPE_SIZE: ${type} unknown") - file(REMOVE ${map}) - endif() -endfunction() - -#----------------------------------------------------------------------------- -macro(CHECK_TYPE_SIZE TYPE VARIABLE) - # parse arguments - unset(doing) - foreach(arg ${ARGN}) - if("x${arg}" STREQUAL "xBUILTIN_TYPES_ONLY") - set(_CHECK_TYPE_SIZE_${arg} 1) - unset(doing) - elseif("x${arg}" STREQUAL "xLANGUAGE") # change to MATCHES for more keys - set(doing "${arg}") - set(_CHECK_TYPE_SIZE_${doing} "") - elseif("x${doing}" STREQUAL "xLANGUAGE") - set(_CHECK_TYPE_SIZE_${doing} "${arg}") - unset(doing) - else() - message(FATAL_ERROR "Unknown argument:\n ${arg}\n") - endif() - endforeach() - if("x${doing}" MATCHES "^x(LANGUAGE)$") - message(FATAL_ERROR "Missing argument:\n ${doing} arguments requires a value\n") - endif() - if(DEFINED _CHECK_TYPE_SIZE_LANGUAGE) - if(NOT "x${_CHECK_TYPE_SIZE_LANGUAGE}" MATCHES "^x(C|CXX)$") - message(FATAL_ERROR "Unknown language:\n ${_CHECK_TYPE_SIZE_LANGUAGE}.\nSupported languages: C, CXX.\n") - endif() - set(_language ${_CHECK_TYPE_SIZE_LANGUAGE}) - else() - set(_language C) - endif() - - # Optionally check for standard headers. - if(_CHECK_TYPE_SIZE_BUILTIN_TYPES_ONLY) - set(_builtin 0) - else() - set(_builtin 1) - if(_language STREQUAL "C") - check_include_file(sys/types.h HAVE_SYS_TYPES_H) - check_include_file(stdint.h HAVE_STDINT_H) - check_include_file(stddef.h HAVE_STDDEF_H) - elseif(_language STREQUAL "CXX") - check_include_file_cxx(sys/types.h HAVE_SYS_TYPES_H) - check_include_file_cxx(stdint.h HAVE_STDINT_H) - check_include_file_cxx(stddef.h HAVE_STDDEF_H) - endif() - endif() - unset(_CHECK_TYPE_SIZE_BUILTIN_TYPES_ONLY) - unset(_CHECK_TYPE_SIZE_LANGUAGE) - - # Compute or load the size or size map. - set(${VARIABLE}_KEYS) - set(_map_file ${CMAKE_BINARY_DIR}/${CMAKE_FILES_DIRECTORY}/CheckTypeSize/${VARIABLE}.cmake) - if(NOT DEFINED HAVE_${VARIABLE}) - __check_type_size_impl(${TYPE} ${VARIABLE} ${_map_file} ${_builtin} ${_language}) - endif() - include(${_map_file} OPTIONAL) - set(_map_file) - set(_builtin) - - # Create preprocessor code. - if(${VARIABLE}_KEYS) - set(${VARIABLE}_CODE) - set(_if if) - foreach(key ${${VARIABLE}_KEYS}) - string(APPEND ${VARIABLE}_CODE "#${_if} defined(${key})\n# define ${VARIABLE} ${${VARIABLE}-${key}}\n") - set(_if elif) - endforeach() - string(APPEND ${VARIABLE}_CODE "#else\n# error ${VARIABLE} unknown\n#endif") - set(_if) - elseif(${VARIABLE}) - set(${VARIABLE}_CODE "#define ${VARIABLE} ${${VARIABLE}}") - else() - set(${VARIABLE}_CODE "/* #undef ${VARIABLE} */") - endif() -endmacro() - -#----------------------------------------------------------------------------- -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/CheckVariableExists.cmake b/share/cmake-3.18/Modules/CheckVariableExists.cmake deleted file mode 100644 index 8a93535..0000000 --- a/share/cmake-3.18/Modules/CheckVariableExists.cmake +++ /dev/null
@@ -1,85 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -CheckVariableExists -------------------- - -Check if the variable exists. - -.. command:: CHECK_VARIABLE_EXISTS - - .. code-block:: cmake - - CHECK_VARIABLE_EXISTS(VAR VARIABLE) - - - :: - - VAR - the name of the variable - VARIABLE - variable to store the result - Will be created as an internal cache variable. - - - This macro is only for ``C`` variables. - -The following variables may be set before calling this macro to modify -the way the check is run: - -:: - - CMAKE_REQUIRED_FLAGS = string of compile command line flags - CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar) - CMAKE_REQUIRED_LINK_OPTIONS = list of options to pass to link command - CMAKE_REQUIRED_LIBRARIES = list of libraries to link - CMAKE_REQUIRED_QUIET = execute quietly without messages -#]=======================================================================] - -include_guard(GLOBAL) - -macro(CHECK_VARIABLE_EXISTS VAR VARIABLE) - if(NOT DEFINED "${VARIABLE}") - set(MACRO_CHECK_VARIABLE_DEFINITIONS - "-DCHECK_VARIABLE_EXISTS=${VAR} ${CMAKE_REQUIRED_FLAGS}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_START "Looking for ${VAR}") - endif() - if(CMAKE_REQUIRED_LINK_OPTIONS) - set(CHECK_VARIABLE_EXISTS_ADD_LINK_OPTIONS - LINK_OPTIONS ${CMAKE_REQUIRED_LINK_OPTIONS}) - else() - set(CHECK_VARIABLE_EXISTS_ADD_LINK_OPTIONS) - endif() - if(CMAKE_REQUIRED_LIBRARIES) - set(CHECK_VARIABLE_EXISTS_ADD_LIBRARIES - LINK_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}) - else() - set(CHECK_VARIABLE_EXISTS_ADD_LIBRARIES) - endif() - try_compile(${VARIABLE} - ${CMAKE_BINARY_DIR} - ${CMAKE_ROOT}/Modules/CheckVariableExists.c - COMPILE_DEFINITIONS ${CMAKE_REQUIRED_DEFINITIONS} - ${CHECK_VARIABLE_EXISTS_ADD_LINK_OPTIONS} - ${CHECK_VARIABLE_EXISTS_ADD_LIBRARIES} - CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MACRO_CHECK_VARIABLE_DEFINITIONS} - OUTPUT_VARIABLE OUTPUT) - if(${VARIABLE}) - set(${VARIABLE} 1 CACHE INTERNAL "Have variable ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_PASS "found") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Determining if the variable ${VAR} exists passed with the following output:\n" - "${OUTPUT}\n\n") - else() - set(${VARIABLE} "" CACHE INTERNAL "Have variable ${VAR}") - if(NOT CMAKE_REQUIRED_QUIET) - message(CHECK_FAIL "not found") - endif() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Determining if the variable ${VAR} exists failed with the following output:\n" - "${OUTPUT}\n\n") - endif() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/ARMCC.cmake b/share/cmake-3.18/Modules/Compiler/ARMCC.cmake deleted file mode 100644 index f949568..0000000 --- a/share/cmake-3.18/Modules/Compiler/ARMCC.cmake +++ /dev/null
@@ -1,39 +0,0 @@ -if(_ARMCC_CMAKE_LOADED) - return() -endif() -set(_ARMCC_CMAKE_LOADED TRUE) - -# See ARM Compiler documentation at: -# http://infocenter.arm.com/help/topic/com.arm.doc.set.swdev/index.html - -get_filename_component(_CMAKE_C_TOOLCHAIN_LOCATION "${CMAKE_C_COMPILER}" PATH) -get_filename_component(_CMAKE_CXX_TOOLCHAIN_LOCATION "${CMAKE_CXX_COMPILER}" PATH) - -set(CMAKE_EXECUTABLE_SUFFIX ".elf") - -find_program(CMAKE_ARMCC_LINKER armlink HINTS "${_CMAKE_C_TOOLCHAIN_LOCATION}" "${_CMAKE_CXX_TOOLCHAIN_LOCATION}" ) -find_program(CMAKE_ARMCC_AR armar HINTS "${_CMAKE_C_TOOLCHAIN_LOCATION}" "${_CMAKE_CXX_TOOLCHAIN_LOCATION}" ) - -set(CMAKE_LINKER "${CMAKE_ARMCC_LINKER}" CACHE FILEPATH "The ARMCC linker" FORCE) -mark_as_advanced(CMAKE_ARMCC_LINKER) -set(CMAKE_AR "${CMAKE_ARMCC_AR}" CACHE FILEPATH "The ARMCC archiver" FORCE) -mark_as_advanced(CMAKE_ARMCC_AR) - -macro(__compiler_armcc lang) - string(APPEND CMAKE_${lang}_FLAGS_INIT " ") - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -g") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -Ospace -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -Otime -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -O2 -g") - - set(CMAKE_${lang}_OUTPUT_EXTENSION ".o") - set(CMAKE_${lang}_OUTPUT_EXTENSION_REPLACE 1) - set(CMAKE_${lang}_RESPONSE_FILE_LINK_FLAG "--via=") - - set(CMAKE_${lang}_LINK_EXECUTABLE "<CMAKE_LINKER> <CMAKE_${lang}_LINK_FLAGS> <LINK_FLAGS> <LINK_LIBRARIES> <OBJECTS> -o <TARGET> --list <TARGET_BASE>.map") - set(CMAKE_${lang}_CREATE_STATIC_LIBRARY "<CMAKE_AR> --create -cr <TARGET> <LINK_FLAGS> <OBJECTS>") - - set(CMAKE_DEPFILE_FLAGS_${lang} "--depend=<DEPFILE> --depend_single_line --no_depend_system_headers") - - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Xlinker" " ") -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/ARMClang-ASM.cmake b/share/cmake-3.18/Modules/Compiler/ARMClang-ASM.cmake deleted file mode 100644 index ceff3e8..0000000 --- a/share/cmake-3.18/Modules/Compiler/ARMClang-ASM.cmake +++ /dev/null
@@ -1,9 +0,0 @@ -include(Compiler/ARMClang) - -set(CMAKE_ASM_OUTPUT_EXTENSION ".o") -set(CMAKE_ASM_OUTPUT_EXTENSION_REPLACE 1) - -set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> <INCLUDES> <FLAGS> -c -o <OBJECT> <SOURCE>") -set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS S;s;asm;msa) - -__compiler_armclang(ASM)
diff --git a/share/cmake-3.18/Modules/Compiler/ARMClang-C.cmake b/share/cmake-3.18/Modules/Compiler/ARMClang-C.cmake deleted file mode 100644 index 0a64a8a..0000000 --- a/share/cmake-3.18/Modules/Compiler/ARMClang-C.cmake +++ /dev/null
@@ -1,15 +0,0 @@ -include(Compiler/Clang-C) -include(Compiler/ARMClang) -__compiler_armclang(C) - -set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c90") -set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu90") -set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - -set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") -set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") -set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - -set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") -set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") -set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON)
diff --git a/share/cmake-3.18/Modules/Compiler/ARMClang-CXX.cmake b/share/cmake-3.18/Modules/Compiler/ARMClang-CXX.cmake deleted file mode 100644 index 5dfb401..0000000 --- a/share/cmake-3.18/Modules/Compiler/ARMClang-CXX.cmake +++ /dev/null
@@ -1,3 +0,0 @@ -include(Compiler/Clang-CXX) -include(Compiler/ARMClang) -__compiler_armclang(CXX)
diff --git a/share/cmake-3.18/Modules/Compiler/ARMClang.cmake b/share/cmake-3.18/Modules/Compiler/ARMClang.cmake deleted file mode 100644 index 01ce91d..0000000 --- a/share/cmake-3.18/Modules/Compiler/ARMClang.cmake +++ /dev/null
@@ -1,130 +0,0 @@ -if(_ARMClang_CMAKE_LOADED) - return() -endif() -set(_ARMClang_CMAKE_LOADED TRUE) - -cmake_policy(PUSH) -cmake_policy(SET CMP0057 NEW) # if IN_LIST - -get_filename_component(_CMAKE_C_TOOLCHAIN_LOCATION "${CMAKE_C_COMPILER}" PATH) -get_filename_component(_CMAKE_CXX_TOOLCHAIN_LOCATION "${CMAKE_CXX_COMPILER}" PATH) - -set(CMAKE_EXECUTABLE_SUFFIX ".elf") - -find_program(CMAKE_ARMClang_LINKER armlink HINTS "${_CMAKE_C_TOOLCHAIN_LOCATION}" "${_CMAKE_CXX_TOOLCHAIN_LOCATION}" ) -find_program(CMAKE_ARMClang_AR armar HINTS "${_CMAKE_C_TOOLCHAIN_LOCATION}" "${_CMAKE_CXX_TOOLCHAIN_LOCATION}" ) - -set(CMAKE_LINKER "${CMAKE_ARMClang_LINKER}" CACHE FILEPATH "The ARMClang linker" FORCE) -mark_as_advanced(CMAKE_ARMClang_LINKER) -set(CMAKE_AR "${CMAKE_ARMClang_AR}" CACHE FILEPATH "The ARMClang archiver" FORCE) -mark_as_advanced(CMAKE_ARMClang_AR) - -if (CMAKE_LINKER MATCHES "armlink") - set(__CMAKE_ARMClang_USING_armlink TRUE) - set(CMAKE_LIBRARY_PATH_FLAG "--userlibpath=") -else() - set(__CMAKE_ARMClang_USING_armlink FALSE) -endif() - -# get compiler supported cpu list -function(__armclang_set_processor_list lang out_var) - execute_process(COMMAND "${CMAKE_${lang}_COMPILER}" --target=${CMAKE_${lang}_COMPILER_TARGET} -mcpu=list - OUTPUT_VARIABLE processor_list - ERROR_VARIABLE processor_list) - string(REGEX MATCHALL "-mcpu=([^ \n]*)" processor_list "${processor_list}") - string(REGEX REPLACE "-mcpu=" "" processor_list "${processor_list}") - set(${out_var} "${processor_list}" PARENT_SCOPE) -endfunction() - -# check processor is in list -function(__armclang_check_processor processor list out_var) - string(TOLOWER "${processor}" processor) - if(processor IN_LIST list) - set(${out_var} TRUE PARENT_SCOPE) - else() - set(${out_var} FALSE PARENT_SCOPE) - endif() -endfunction() - -# get compiler supported arch list -function(__armclang_set_arch_list lang out_var) - execute_process(COMMAND "${CMAKE_${lang}_COMPILER}" --target=${CMAKE_${lang}_COMPILER_TARGET} -march=list - OUTPUT_VARIABLE arch_list - ERROR_VARIABLE arch_list) - string(REGEX MATCHALL "-march=([^ \n]*)" arch_list "${arch_list}") - string(REGEX REPLACE "-march=" "" arch_list "${arch_list}") - set(${out_var} "${arch_list}" PARENT_SCOPE) -endfunction() - -# get linker supported cpu list -function(__armlink_set_cpu_list lang out_var) - if(__CMAKE_ARMClang_USING_armlink) - set(__linker_wrapper_flags "") - else() - set(__linker_wrapper_flags --target=${CMAKE_${lang}_COMPILER_TARGET} -Xlinker) - endif() - - execute_process(COMMAND "${CMAKE_LINKER}" ${__linker_wrapper_flags} --cpu=list - OUTPUT_VARIABLE cpu_list - ERROR_VARIABLE cpu_list) - string(REGEX MATCHALL "--cpu=([^ \n]*)" cpu_list "${cpu_list}") - string(REGEX REPLACE "--cpu=" "" cpu_list "${cpu_list}") - set(${out_var} "${cpu_list}" PARENT_SCOPE) -endfunction() - -macro(__compiler_armclang lang) - if(NOT CMAKE_${lang}_COMPILER_TARGET) - set(CMAKE_${lang}_COMPILER_TARGET arm-arm-none-eabi) - endif() - if(NOT CMAKE_${lang}_COMPILER_PROCESSOR_LIST) - __armclang_set_processor_list(${lang} CMAKE_${lang}_COMPILER_PROCESSOR_LIST) - endif() - if(NOT CMAKE_${lang}_COMPILER_ARCH_LIST) - __armclang_set_arch_list(${lang} CMAKE_${lang}_COMPILER_ARCH_LIST) - endif() - if(NOT CMAKE_SYSTEM_PROCESSOR AND NOT CMAKE_SYSTEM_ARCH) - message(FATAL_ERROR " CMAKE_SYSTEM_PROCESSOR or CMAKE_SYSTEM_ARCH must be set for ARMClang\n" - " Supported processor: ${CMAKE_${lang}_COMPILER_PROCESSOR_LIST}\n" - " Supported Architecture: ${CMAKE_${lang}_COMPILER_ARCH_LIST}") - else() - __armclang_check_processor("${CMAKE_SYSTEM_ARCH}" "${CMAKE_${lang}_COMPILER_ARCH_LIST}" _CMAKE_${lang}_CHECK_ARCH_RESULT) - if( _CMAKE_${lang}_CHECK_ARCH_RESULT) - string(APPEND CMAKE_${lang}_FLAGS_INIT "-march=${CMAKE_SYSTEM_ARCH}") - set(__march_flag_set TRUE) - endif() - __armclang_check_processor("${CMAKE_SYSTEM_PROCESSOR}" "${CMAKE_${lang}_COMPILER_PROCESSOR_LIST}" _CMAKE_${lang}_CHECK_PROCESSOR_RESULT) - if(_CMAKE_${lang}_CHECK_PROCESSOR_RESULT) - string(APPEND CMAKE_${lang}_FLAGS_INIT "-mcpu=${CMAKE_SYSTEM_PROCESSOR}") - set(__mcpu_flag_set TRUE) - endif() - if(NOT __march_flag_set AND NOT __mcpu_flag_set) - message(FATAL_ERROR "Atleast one of the variables CMAKE_SYSTEM_PROCESSOR or CMAKE_SYSTEM_ARCH must be set for ARMClang\n" - "Supported processor: ${CMAKE_${lang}_COMPILER_PROCESSOR_LIST}\n" - " Supported Architecture: ${CMAKE_${lang}_COMPILER_ARCH_LIST}") - endif() - unset(_CMAKE_${lang}_CHECK_PROCESSOR_RESULT) - unset(_CMAKE_${lang}_CHECK_ARCH_RESULT) - endif() - - #check if CMAKE_SYSTEM_PROCESSOR belongs to supported cpu list for armlink - __armlink_set_cpu_list( ${lang} CMAKE_LINKER_CPU_LIST) - list(TRANSFORM CMAKE_LINKER_CPU_LIST TOLOWER) - __armclang_check_processor("${CMAKE_SYSTEM_PROCESSOR}" "${CMAKE_LINKER_CPU_LIST}" _CMAKE_CHECK_LINK_CPU_RESULT) - if(_CMAKE_CHECK_LINK_CPU_RESULT) - string(APPEND CMAKE_${lang}_LINK_FLAGS "--cpu=${CMAKE_SYSTEM_PROCESSOR}") - endif() - - if(__CMAKE_ARMClang_USING_armlink) - set(__CMAKE_ARMClang_USING_armlink_WRAPPER "") - else() - set(__CMAKE_ARMClang_USING_armlink_WRAPPER ${CMAKE_${lang}_LINKER_WRAPPER_FLAG}) - endif() - set(CMAKE_${lang}_LINK_EXECUTABLE "<CMAKE_LINKER> <CMAKE_${lang}_LINK_FLAGS> <LINK_FLAGS> <LINK_LIBRARIES> <OBJECTS> -o <TARGET> ${__CMAKE_ARMClang_USING_armlink_WRAPPER} --list <TARGET_BASE>.map") - set(CMAKE_${lang}_CREATE_STATIC_LIBRARY "<CMAKE_AR> --create -cr <TARGET> <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_CREATE "<CMAKE_AR> --create -cr <TARGET> <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_RESPONSE_FILE_LINK_FLAG "${__CMAKE_ARMClang_USING_armlink_WRAPPER} --via=") - set(CMAKE_${lang}_OUTPUT_EXTENSION ".o") - set(CMAKE_${lang}_OUTPUT_EXTENSION_REPLACE 1) -endmacro() - -cmake_policy(POP)
diff --git a/share/cmake-3.18/Modules/Compiler/AppleClang-C.cmake b/share/cmake-3.18/Modules/Compiler/AppleClang-C.cmake deleted file mode 100644 index 2794f52..0000000 --- a/share/cmake-3.18/Modules/Compiler/AppleClang-C.cmake +++ /dev/null
@@ -1,18 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(C) - -if(NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c90") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu90") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -__compiler_check_default_language_standard(C 4.0 99)
diff --git a/share/cmake-3.18/Modules/Compiler/AppleClang-CXX.cmake b/share/cmake-3.18/Modules/Compiler/AppleClang-CXX.cmake deleted file mode 100644 index 15edc21..0000000 --- a/share/cmake-3.18/Modules/Compiler/AppleClang-CXX.cmake +++ /dev/null
@@ -1,45 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(CXX) - -if(NOT "x${CMAKE_CXX_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fvisibility-inlines-hidden") -endif() - -if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "-std=c++98") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "-std=gnu++98") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++11") -endif() - -if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 6.1) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++14") - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) -elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.1) - # AppleClang 5.0 knows this flag, but does not set a __cplusplus macro greater than 201103L - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++1y") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 10.0) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std=gnu++17") -elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 6.1) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std=c++1z") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std=gnu++1z") -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 8.0) - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 10.0) - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "-std=c++2a") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "-std=gnu++2a") -endif() - -__compiler_check_default_language_standard(CXX 4.0 98)
diff --git a/share/cmake-3.18/Modules/Compiler/AppleClang-OBJC.cmake b/share/cmake-3.18/Modules/Compiler/AppleClang-OBJC.cmake deleted file mode 100644 index d1f3706..0000000 --- a/share/cmake-3.18/Modules/Compiler/AppleClang-OBJC.cmake +++ /dev/null
@@ -1,17 +0,0 @@ -include(Compiler/Clang-OBJC) - -if(NOT CMAKE_OBJC_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_OBJC90_STANDARD_COMPILE_OPTION "-std=c90") - set(CMAKE_OBJC90_EXTENSION_COMPILE_OPTION "-std=gnu90") - set(CMAKE_OBJC90_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_OBJC99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_OBJC99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_OBJC99_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_OBJC11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_OBJC11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_OBJC11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -__compiler_check_default_language_standard(OBJC 4.0 99)
diff --git a/share/cmake-3.18/Modules/Compiler/AppleClang-OBJCXX.cmake b/share/cmake-3.18/Modules/Compiler/AppleClang-OBJCXX.cmake deleted file mode 100644 index 409bd4a..0000000 --- a/share/cmake-3.18/Modules/Compiler/AppleClang-OBJCXX.cmake +++ /dev/null
@@ -1,42 +0,0 @@ -include(Compiler/Clang-OBJCXX) - -set(CMAKE_OBJCXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fvisibility-inlines-hidden") - -if(NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_OBJCXX98_STANDARD_COMPILE_OPTION "-std=c++98") - set(CMAKE_OBJCXX98_EXTENSION_COMPILE_OPTION "-std=gnu++98") - set(CMAKE_OBJCXX98_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_OBJCXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_OBJCXX11_EXTENSION_COMPILE_OPTION "-std=gnu++11") -endif() - -if(NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 6.1) - set(CMAKE_OBJCXX14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_OBJCXX14_EXTENSION_COMPILE_OPTION "-std=gnu++14") - set(CMAKE_OBJCXX14_STANDARD__HAS_FULL_SUPPORT ON) -elseif(NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 5.1) - # AppleClang 5.0 knows this flag, but does not set a __cplusplus macro greater than 201103L - set(CMAKE_OBJCXX14_STANDARD_COMPILE_OPTION "-std=c++1y") - set(CMAKE_OBJCXX14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") - set(CMAKE_OBJCXX14_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 10.0) - set(CMAKE_OBJCXX17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_OBJCXX17_EXTENSION_COMPILE_OPTION "-std=gnu++17") -elseif (NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 6.1) - set(CMAKE_OBJCXX17_STANDARD_COMPILE_OPTION "-std=c++1z") - set(CMAKE_OBJCXX17_EXTENSION_COMPILE_OPTION "-std=gnu++1z") -endif() - -if (NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 8.0) - set(CMAKE_OBJCXX11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 10.0) - set(CMAKE_OBJCXX20_STANDARD_COMPILE_OPTION "-std=c++2a") - set(CMAKE_OBJCXX20_EXTENSION_COMPILE_OPTION "-std=gnu++2a") -endif() - -__compiler_check_default_language_standard(OBJCXX 4.0 98)
diff --git a/share/cmake-3.18/Modules/Compiler/CMakeCommonCompilerMacros.cmake b/share/cmake-3.18/Modules/Compiler/CMakeCommonCompilerMacros.cmake deleted file mode 100644 index 409b65a..0000000 --- a/share/cmake-3.18/Modules/Compiler/CMakeCommonCompilerMacros.cmake +++ /dev/null
@@ -1,180 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -# This module is shared by multiple languages and compilers; use include guard -if (__COMPILER_CMAKE_COMMON_COMPILER_MACROS) - return() -endif () -set(__COMPILER_CMAKE_COMMON_COMPILER_MACROS 1) - - -# Check that a compiler's language standard is properly detected -# Parameters: -# lang - Language to check -# stdver1 - Minimum version to set a given default for -# std1 - Default to use for compiler ver >= stdver1 -# stdverN - Minimum version to set a given default for -# stdN - Default to use for compiler ver >= stdverN -# -# The order of stdverN stdN pairs passed as arguments is expected to be in -# monotonically increasing version order. -# -# Note: -# This macro can be called with multiple version / std pairs to convey that -# newer compiler versions may use a newer standard default. -# -# Example: -# To specify that compiler version 6.1 and newer defaults to C++11 while -# 4.8 <= ver < 6.1 default to C++98, you would call: -# -# __compiler_check_default_language_standard(CXX 4.8 98 6.1 11) -# -macro(__compiler_check_default_language_standard lang stdver1 std1) - set(__std_ver_pairs "${stdver1};${std1};${ARGN}") - string(REGEX REPLACE " *; *" " " __std_ver_pairs "${__std_ver_pairs}") - string(REGEX MATCHALL "[^ ]+ [^ ]+" __std_ver_pairs "${__std_ver_pairs}") - - # If the compiler version is below the threshold of even having CMake - # support for language standards, then don't bother. - if (CMAKE_${lang}_COMPILER_VERSION VERSION_GREATER_EQUAL "${stdver1}") - if (NOT CMAKE_${lang}_COMPILER_FORCED) - if (NOT CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT) - message(FATAL_ERROR "CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT should be set for ${CMAKE_${lang}_COMPILER_ID} (${CMAKE_${lang}_COMPILER}) version ${CMAKE_${lang}_COMPILER_VERSION}") - endif () - set(CMAKE_${lang}_STANDARD_DEFAULT ${CMAKE_${lang}_STANDARD_COMPUTED_DEFAULT}) - else () - list(REVERSE __std_ver_pairs) - foreach (__std_ver_pair IN LISTS __std_ver_pairs) - string(REGEX MATCH "([^ ]+) (.+)" __std_ver_pair "${__std_ver_pair}") - set(__stdver ${CMAKE_MATCH_1}) - set(__std ${CMAKE_MATCH_2}) - if (CMAKE_${lang}_COMPILER_VERSION VERSION_GREATER_EQUAL __stdver AND - NOT DEFINED CMAKE_${lang}_STANDARD_DEFAULT) - # Compiler id was forced so just guess the default standard level. - set(CMAKE_${lang}_STANDARD_DEFAULT ${__std}) - endif () - unset(__std) - unset(__stdver) - endforeach () - endif () - endif () - unset(__std_ver_pairs) -endmacro() - -# Define to allow compile features to be automatically determined -macro(cmake_record_c_compile_features) - set(_result 0) - if(_result EQUAL 0 AND DEFINED CMAKE_C11_STANDARD_COMPILE_OPTION) - if(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_c(11) - else() - _record_compiler_features_c(11) - endif() - unset(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_C99_STANDARD_COMPILE_OPTION) - if(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_c(99) - else() - _record_compiler_features_c(99) - endif() - unset(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_C90_STANDARD_COMPILE_OPTION) - if(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_c(90) - else() - _record_compiler_features_c(90) - endif() - unset(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT) - endif() -endmacro() - -# Define to allow compile features to be automatically determined -macro(cmake_record_cxx_compile_features) - set(_result 0) - if(_result EQUAL 0 AND DEFINED CMAKE_CXX20_STANDARD_COMPILE_OPTION) - if(CMAKE_CXX20_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cxx(20) - else() - _record_compiler_features_cxx(20) - endif() - unset(CMAKE_CXX20_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CXX17_STANDARD_COMPILE_OPTION) - if(CMAKE_CXX17_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cxx(17) - else() - _record_compiler_features_cxx(17) - endif() - unset(CMAKE_CXX17_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CXX14_STANDARD_COMPILE_OPTION) - if(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cxx(14) - else() - _record_compiler_features_cxx(14) - endif() - unset(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CXX11_STANDARD_COMPILE_OPTION) - if(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cxx(11) - else() - _record_compiler_features_cxx(11) - endif() - unset(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CXX98_STANDARD_COMPILE_OPTION) - if(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cxx(98) - else() - _record_compiler_features_cxx(98) - endif() - unset(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT) - endif() -endmacro() - -macro(cmake_record_cuda_compile_features) - set(_result 0) - if(_result EQUAL 0 AND DEFINED CMAKE_CUDA20_STANDARD_COMPILE_OPTION) - if(CMAKE_CUDA20_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cuda(20) - else() - _record_compiler_features_cuda(20) - endif() - unset(CMAKE_CUDA20_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CUDA17_STANDARD_COMPILE_OPTION) - if(CMAKE_CUDA17_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cuda(17) - else() - _record_compiler_features_cuda(17) - endif() - unset(CMAKE_CUDA17_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CUDA14_STANDARD_COMPILE_OPTION) - if(CMAKE_CUDA14_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cuda(14) - else() - _record_compiler_features_cuda(14) - endif() - unset(CMAKE_CUDA14_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CUDA11_STANDARD_COMPILE_OPTION) - if(CMAKE_CUDA11_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cuda(11) - else() - _record_compiler_features_cuda(11) - endif() - unset(CMAKE_CUDA11_STANDARD__HAS_FULL_SUPPORT) - endif() - if(_result EQUAL 0 AND DEFINED CMAKE_CUDA03_STANDARD_COMPILE_OPTION) - if(CMAKE_CUDA03_STANDARD__HAS_FULL_SUPPORT) - _has_compiler_features_cuda(03) - else() - _record_compiler_features_cuda(03) - endif() - unset(CMAKE_CUDA03_STANDARD__HAS_FULL_SUPPORT) - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-C.cmake b/share/cmake-3.18/Modules/Compiler/Clang-C.cmake deleted file mode 100644 index 7c4a263..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-C.cmake +++ /dev/null
@@ -1,46 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(C) - -cmake_policy(GET CMP0025 appleClangPolicy) -if(APPLE AND NOT appleClangPolicy STREQUAL NEW) - return() -endif() - -if("x${CMAKE_C_COMPILER_FRONTEND_VARIANT}" STREQUAL "xMSVC") - set(CMAKE_C_CLANG_TIDY_DRIVER_MODE "cl") -endif() - -if(NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 3.4) - if(NOT "x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c90") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu90") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) - else() - # clang-cl doesn't have any of these - set(CMAKE_C90_STANDARD_COMPILE_OPTION "") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C99_STANDARD_COMPILE_OPTION "") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_C11_STANDARD_COMPILE_OPTION "") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) - endif() -endif() - -if(NOT "x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC") - __compiler_check_default_language_standard(C 3.4 99 3.6 11) -else() - set(CMAKE_C_STANDARD_DEFAULT "") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-CUDA.cmake b/share/cmake-3.18/Modules/Compiler/Clang-CUDA.cmake deleted file mode 100644 index 336827b..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-CUDA.cmake +++ /dev/null
@@ -1,28 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(CUDA) - -# Set explicitly, because __compiler_clang() doesn't set this if we're simulating MSVC. -set(CMAKE_DEPFILE_FLAGS_CUDA "-MD -MT <OBJECT> -MF <DEPFILE>") - -# C++03 isn't supported for CXX, but is for CUDA, so we need to set these manually. -# Do this before __compiler_clang_cxx_standards() since that adds the feature. -set(CMAKE_CUDA03_STANDARD_COMPILE_OPTION "-std=c++03") -set(CMAKE_CUDA03_EXTENSION_COMPILE_OPTION "-std=gnu++03") -__compiler_clang_cxx_standards(CUDA) - -set(CMAKE_CUDA_COMPILER_HAS_DEVICE_LINK_PHASE TRUE) -set(_CMAKE_COMPILE_AS_CUDA_FLAG "-x cuda") -set(_CMAKE_CUDA_PTX_FLAG "--cuda-device-only -S") - -# RulePlaceholderExpander expands crosscompile variables like sysroot and target only for CMAKE_<LANG>_COMPILER. Override the default. -set(CMAKE_CUDA_LINK_EXECUTABLE "<CMAKE_CUDA_COMPILER> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>${__IMPLICT_LINKS}") -set(CMAKE_CUDA_CREATE_SHARED_LIBRARY "<CMAKE_CUDA_COMPILER> <CMAKE_SHARED_LIBRARY_CUDA_FLAGS> <LINK_FLAGS> <CMAKE_SHARED_LIBRARY_CREATE_CUDA_FLAGS> <SONAME_FLAG><TARGET_SONAME> -o <TARGET> <OBJECTS> <LINK_LIBRARIES>${__IMPLICT_LINKS}") - -set(CMAKE_CUDA_RUNTIME_LIBRARY_DEFAULT "STATIC") -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_STATIC "cudadevrt;cudart_static") -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_SHARED "cudadevrt;cudart") -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_NONE "") - -if(UNIX) - list(APPEND CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_STATIC "rt" "pthread" "dl") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-CXX.cmake b/share/cmake-3.18/Modules/Compiler/Clang-CXX.cmake deleted file mode 100644 index 789e991..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-CXX.cmake +++ /dev/null
@@ -1,16 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(CXX) -__compiler_clang_cxx_standards(CXX) - -if("x${CMAKE_CXX_COMPILER_FRONTEND_VARIANT}" STREQUAL "xGNU") - set(CMAKE_CXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fvisibility-inlines-hidden") -endif() - -cmake_policy(GET CMP0025 appleClangPolicy) -if(APPLE AND NOT appleClangPolicy STREQUAL NEW) - return() -endif() - -if("x${CMAKE_CXX_COMPILER_FRONTEND_VARIANT}" STREQUAL "xMSVC") - set(CMAKE_CXX_CLANG_TIDY_DRIVER_MODE "cl") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-FindBinUtils.cmake b/share/cmake-3.18/Modules/Compiler/Clang-FindBinUtils.cmake deleted file mode 100644 index b852660..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-FindBinUtils.cmake +++ /dev/null
@@ -1,35 +0,0 @@ -if(NOT DEFINED _CMAKE_PROCESSING_LANGUAGE OR _CMAKE_PROCESSING_LANGUAGE STREQUAL "") - message(FATAL_ERROR "Internal error: _CMAKE_PROCESSING_LANGUAGE is not set") -endif() - -# Debian: -# * /usr/bin/llvm-ar-4.0 -# * /usr/bin/llvm-ranlib-4.0 -string(REGEX MATCH "^([0-9]+\\.[0-9]+)" __version_x_y - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_VERSION}") - -# Try to find tools in the same directory as Clang itself -get_filename_component(__clang_hint_1 "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER}" REALPATH) -get_filename_component(__clang_hint_1 "${__clang_hint_1}" DIRECTORY) - -get_filename_component(__clang_hint_2 "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER}" DIRECTORY) - -set(__clang_hints ${__clang_hint_1} ${__clang_hint_2}) - -# http://manpages.ubuntu.com/manpages/precise/en/man1/llvm-ar.1.html -find_program(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_AR NAMES - "${_CMAKE_TOOLCHAIN_PREFIX}llvm-ar-${__version_x_y}" - "${_CMAKE_TOOLCHAIN_PREFIX}llvm-ar" - HINTS ${__clang_hints} - DOC "LLVM archiver" -) -mark_as_advanced(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_AR) - -# http://manpages.ubuntu.com/manpages/precise/en/man1/llvm-ranlib.1.html -find_program(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_RANLIB NAMES - "${_CMAKE_TOOLCHAIN_PREFIX}llvm-ranlib-${__version_x_y}" - "${_CMAKE_TOOLCHAIN_PREFIX}llvm-ranlib" - HINTS ${__clang_hints} - DOC "Generate index for LLVM archive" -) -mark_as_advanced(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_RANLIB)
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-OBJC.cmake b/share/cmake-3.18/Modules/Compiler/Clang-OBJC.cmake deleted file mode 100644 index c61c497..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-OBJC.cmake +++ /dev/null
@@ -1,18 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(OBJC) - -if(NOT CMAKE_OBJC_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_OBJC90_STANDARD_COMPILE_OPTION "-std=c90") - set(CMAKE_OBJC90_EXTENSION_COMPILE_OPTION "-std=gnu90") - set(CMAKE_OBJC90_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_OBJC99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_OBJC99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_OBJC99_STANDARD__HAS_FULL_SUPPORT ON) - - set(CMAKE_OBJC11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_OBJC11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_OBJC11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -__compiler_check_default_language_standard(OBJC 3.4 99 3.6 11)
diff --git a/share/cmake-3.18/Modules/Compiler/Clang-OBJCXX.cmake b/share/cmake-3.18/Modules/Compiler/Clang-OBJCXX.cmake deleted file mode 100644 index 453b5fd..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang-OBJCXX.cmake +++ /dev/null
@@ -1,3 +0,0 @@ -include(Compiler/Clang) -__compiler_clang(OBJCXX) -__compiler_clang_cxx_standards(OBJCXX)
diff --git a/share/cmake-3.18/Modules/Compiler/Clang.cmake b/share/cmake-3.18/Modules/Compiler/Clang.cmake deleted file mode 100644 index 52d5350..0000000 --- a/share/cmake-3.18/Modules/Compiler/Clang.cmake +++ /dev/null
@@ -1,234 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This module is shared by multiple languages; use include blocker. -if(__COMPILER_CLANG) - return() -endif() -set(__COMPILER_CLANG 1) - -include(Compiler/CMakeCommonCompilerMacros) - -if("x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC" - OR "x${CMAKE_CXX_SIMULATE_ID}" STREQUAL "xMSVC" - OR "x${CMAKE_Fortran_SIMULATE_ID}" STREQUAL "xMSVC") - macro(__compiler_clang lang) - endmacro() -else() - include(Compiler/GNU) - - macro(__compiler_clang lang) - __compiler_gnu(${lang}) - set(CMAKE_${lang}_COMPILE_OPTIONS_PIE "-fPIE") - # Link options for PIE are already set in 'Compiler/GNU.cmake' - # but clang may require alternate syntax on some platforms - if (APPLE) - set(CMAKE_${lang}_LINK_OPTIONS_PIE ${CMAKE_${lang}_COMPILE_OPTIONS_PIE} -Xlinker -pie) - set(CMAKE_${lang}_LINK_OPTIONS_NO_PIE -Xlinker -no_pie) - endif() - set(CMAKE_INCLUDE_SYSTEM_FLAG_${lang} "-isystem ") - set(CMAKE_${lang}_COMPILE_OPTIONS_VISIBILITY "-fvisibility=") - if(CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.4.0) - set(CMAKE_${lang}_COMPILE_OPTIONS_TARGET "-target ") - set(CMAKE_${lang}_COMPILE_OPTIONS_EXTERNAL_TOOLCHAIN "-gcc-toolchain ") - else() - set(CMAKE_${lang}_COMPILE_OPTIONS_TARGET "--target=") - set(CMAKE_${lang}_COMPILE_OPTIONS_EXTERNAL_TOOLCHAIN "--gcc-toolchain=") - endif() - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Xlinker" " ") - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG_SEP) - - if(CMAKE_${lang}_COMPILER_TARGET) - if(CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.4.0) - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "-target" "${CMAKE_${lang}_COMPILER_TARGET}") - else() - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "--target=${CMAKE_${lang}_COMPILER_TARGET}") - endif() - endif() - - set(_CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE YES) - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER YES) - - string(COMPARE EQUAL "${CMAKE_${lang}_COMPILER_ID}" "AppleClang" __is_apple_clang) - - # '-flto=thin' available since Clang 3.9 and Xcode 8 - # * http://clang.llvm.org/docs/ThinLTO.html#clang-llvm - # * https://trac.macports.org/wiki/XcodeVersionInfo - set(_CMAKE_LTO_THIN TRUE) - if(__is_apple_clang) - if(CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 8.0) - set(_CMAKE_LTO_THIN FALSE) - endif() - else() - if(CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.9) - set(_CMAKE_LTO_THIN FALSE) - endif() - endif() - - if(_CMAKE_LTO_THIN) - set(CMAKE_${lang}_COMPILE_OPTIONS_IPO "-flto=thin") - else() - set(CMAKE_${lang}_COMPILE_OPTIONS_IPO "-flto") - endif() - - if(ANDROID) - # https://github.com/android-ndk/ndk/issues/242 - set(CMAKE_${lang}_LINK_OPTIONS_IPO "-fuse-ld=gold") - endif() - - if(ANDROID OR __is_apple_clang) - set(__ar "${CMAKE_AR}") - set(__ranlib "${CMAKE_RANLIB}") - else() - set(__ar "${CMAKE_${lang}_COMPILER_AR}") - set(__ranlib "${CMAKE_${lang}_COMPILER_RANLIB}") - endif() - - set(CMAKE_${lang}_ARCHIVE_CREATE_IPO - "\"${__ar}\" cr <TARGET> <LINK_FLAGS> <OBJECTS>" - ) - - set(CMAKE_${lang}_ARCHIVE_APPEND_IPO - "\"${__ar}\" r <TARGET> <LINK_FLAGS> <OBJECTS>" - ) - - set(CMAKE_${lang}_ARCHIVE_FINISH_IPO - "\"${__ranlib}\" <TARGET>" - ) - - set(CMAKE_PCH_EXTENSION .pch) - if (NOT CMAKE_GENERATOR MATCHES "Xcode") - set(CMAKE_PCH_PROLOGUE "#pragma clang system_header") - endif() - set(CMAKE_${lang}_COMPILE_OPTIONS_USE_PCH -Xclang -include-pch -Xclang <PCH_FILE> -Xclang -include -Xclang <PCH_HEADER>) - set(CMAKE_${lang}_COMPILE_OPTIONS_CREATE_PCH -Xclang -emit-pch -Xclang -include -Xclang <PCH_HEADER>) - endmacro() -endif() - -macro(__compiler_clang_cxx_standards lang) - if("x${CMAKE_${lang}_COMPILER_FRONTEND_VARIANT}" STREQUAL "xGNU") - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 2.1) - set(CMAKE_${lang}98_STANDARD_COMPILE_OPTION "-std=c++98") - set(CMAKE_${lang}98_EXTENSION_COMPILE_OPTION "-std=gnu++98") - endif() - - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.1) - set(CMAKE_${lang}98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_${lang}11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_${lang}11_EXTENSION_COMPILE_OPTION "-std=gnu++11") - set(CMAKE_${lang}11_STANDARD__HAS_FULL_SUPPORT ON) - elseif(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 2.1) - set(CMAKE_${lang}11_STANDARD_COMPILE_OPTION "-std=c++0x") - set(CMAKE_${lang}11_EXTENSION_COMPILE_OPTION "-std=gnu++0x") - endif() - - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.5) - set(CMAKE_${lang}14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_${lang}14_EXTENSION_COMPILE_OPTION "-std=gnu++14") - set(CMAKE_${lang}14_STANDARD__HAS_FULL_SUPPORT ON) - elseif(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_${lang}14_STANDARD_COMPILE_OPTION "-std=c++1y") - set(CMAKE_${lang}14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") - set(CMAKE_${lang}14_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - set(_clang_version_std17 5.0) - if(CMAKE_SYSTEM_NAME STREQUAL "Android") - set(_clang_version_std17 6.0) - endif() - - if (NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS "${_clang_version_std17}") - set(CMAKE_${lang}17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_${lang}17_EXTENSION_COMPILE_OPTION "-std=gnu++17") - elseif (NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.5) - set(CMAKE_${lang}17_STANDARD_COMPILE_OPTION "-std=c++1z") - set(CMAKE_${lang}17_EXTENSION_COMPILE_OPTION "-std=gnu++1z") - endif() - - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 6.0) - set(CMAKE_${lang}17_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 11.0) - set(CMAKE_${lang}20_STANDARD_COMPILE_OPTION "-std=c++20") - set(CMAKE_${lang}20_EXTENSION_COMPILE_OPTION "-std=gnu++20") - elseif(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS "${_clang_version_std17}") - set(CMAKE_${lang}20_STANDARD_COMPILE_OPTION "-std=c++2a") - set(CMAKE_${lang}20_EXTENSION_COMPILE_OPTION "-std=gnu++2a") - endif() - - unset(_clang_version_std17) - - if("x${CMAKE_${lang}_SIMULATE_ID}" STREQUAL "xMSVC") - # The MSVC standard library requires C++14, and MSVC itself has no - # notion of operating in a mode not aware of at least that standard. - set(CMAKE_${lang}98_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_${lang}98_EXTENSION_COMPILE_OPTION "-std=gnu++14") - set(CMAKE_${lang}11_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_${lang}11_EXTENSION_COMPILE_OPTION "-std=gnu++14") - - # This clang++ is missing some features because of MSVC compatibility. - unset(CMAKE_${lang}11_STANDARD__HAS_FULL_SUPPORT) - unset(CMAKE_${lang}14_STANDARD__HAS_FULL_SUPPORT) - unset(CMAKE_${lang}17_STANDARD__HAS_FULL_SUPPORT) - unset(CMAKE_${lang}20_STANDARD__HAS_FULL_SUPPORT) - endif() - - __compiler_check_default_language_standard(${lang} 2.1 98) - elseif(CMAKE_${lang}_COMPILER_VERSION VERSION_GREATER_EQUAL 3.9 - AND CMAKE_${lang}_SIMULATE_VERSION VERSION_GREATER_EQUAL 19.0) - # This version of clang-cl and the MSVC version it simulates have - # support for -std: flags. - set(CMAKE_${lang}98_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_${lang}11_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}11_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}14_STANDARD_COMPILE_OPTION "-std:c++14") - set(CMAKE_${lang}14_EXTENSION_COMPILE_OPTION "-std:c++14") - if (CMAKE_${lang}_COMPILER_VERSION VERSION_GREATER_EQUAL 6.0) - set(CMAKE_${lang}17_STANDARD_COMPILE_OPTION "-std:c++17") - set(CMAKE_${lang}17_EXTENSION_COMPILE_OPTION "-std:c++17") - set(CMAKE_${lang}20_STANDARD_COMPILE_OPTION "-std:c++latest") - set(CMAKE_${lang}20_EXTENSION_COMPILE_OPTION "-std:c++latest") - else() - set(CMAKE_${lang}17_STANDARD_COMPILE_OPTION "-std:c++latest") - set(CMAKE_${lang}17_EXTENSION_COMPILE_OPTION "-std:c++latest") - endif() - - __compiler_check_default_language_standard(${lang} 3.9 14) - else() - # This version of clang-cl, or the MSVC version it simulates, does not have - # language standards. Set these options as empty strings so the feature - # test infrastructure can at least check to see if they are defined. - set(CMAKE_${lang}98_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}11_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}11_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}14_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}14_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}17_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}17_EXTENSION_COMPILE_OPTION "") - set(CMAKE_${lang}20_STANDARD_COMPILE_OPTION "") - set(CMAKE_${lang}20_EXTENSION_COMPILE_OPTION "") - - # There is no meaningful default for this - set(CMAKE_${lang}_STANDARD_DEFAULT "") - - # There are no compiler modes so we only need to test features once. - # Override the default macro for this special case. Pretend that - # all language standards are available so that at least compilation - # can be attempted. - macro(cmake_record_${lang}_compile_features) - list(APPEND CMAKE_${lang}_COMPILE_FEATURES - cxx_std_98 - cxx_std_11 - cxx_std_14 - cxx_std_17 - cxx_std_20 - ) - _record_compiler_features(${lang} "" CMAKE_${lang}_COMPILE_FEATURES) - endmacro() - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/Cray-Fortran.cmake b/share/cmake-3.18/Modules/Compiler/Cray-Fortran.cmake deleted file mode 100644 index 696ae76..0000000 --- a/share/cmake-3.18/Modules/Compiler/Cray-Fortran.cmake +++ /dev/null
@@ -1,21 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(Compiler/Cray) -__compiler_cray(Fortran) - -set(CMAKE_Fortran_SUBMODULE_SEP "") -set(CMAKE_Fortran_SUBMODULE_EXT ".mod") -set(CMAKE_Fortran_MODOUT_FLAG -em) -set(CMAKE_Fortran_MODDIR_FLAG -J) -set(CMAKE_Fortran_MODDIR_DEFAULT .) -set(CMAKE_Fortran_FORMAT_FIXED_FLAG "-f fixed") -set(CMAKE_Fortran_FORMAT_FREE_FLAG "-f free") - -if (NOT CMAKE_Fortran_COMPILER_VERSION VERSION_LESS 8.5) - set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_ON "-eT") - set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_OFF "-dT") -else() - set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_ON "-eZ") - set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_OFF "-dZ") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/Fujitsu-DetermineCompiler.cmake b/share/cmake-3.18/Modules/Compiler/Fujitsu-DetermineCompiler.cmake deleted file mode 100644 index 73ee38c..0000000 --- a/share/cmake-3.18/Modules/Compiler/Fujitsu-DetermineCompiler.cmake +++ /dev/null
@@ -1,2 +0,0 @@ - -set(_compiler_id_pp_test "defined(__FUJITSU) || defined(__FCC_VERSION) || defined(__fcc_version)")
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-ASM.cmake b/share/cmake-3.18/Modules/Compiler/GNU-ASM.cmake deleted file mode 100644 index 94af401..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-ASM.cmake +++ /dev/null
@@ -1,13 +0,0 @@ -# This file is loaded when gcc/g++ is used for assembler files (the "ASM" cmake language) -include(Compiler/GNU) - -set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;S;asm) - -__compiler_gnu(ASM) - -if(CMAKE_ASM${ASM_DIALECT}_COMPILER_ID_VENDOR_MATCH STREQUAL "GNU assembler") - set(CMAKE_DEPFILE_FLAGS_ASM${ASM_DIALECT} "--MD <DEPFILE>") - set(CMAKE_ASM${ASM_DIALECT}_LINK_EXECUTABLE - "<CMAKE_LINKER> <FLAGS> <CMAKE_ASM${ASM_DIALECT}_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> -o <TARGET> <LINK_LIBRARIES>") - set(CMAKE_ASM_DEFINE_FLAG "--defsym ") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-C.cmake b/share/cmake-3.18/Modules/Compiler/GNU-C.cmake deleted file mode 100644 index ca286b3..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-C.cmake +++ /dev/null
@@ -1,28 +0,0 @@ -include(Compiler/GNU) -__compiler_gnu(C) - -if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 4.5) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c90") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu90") -elseif (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c89") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu89") -endif() - -if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 4.7) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) -elseif (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 4.6) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c1x") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu1x") -endif() - -__compiler_check_default_language_standard(C 3.4 90 5.0 11)
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-CXX.cmake b/share/cmake-3.18/Modules/Compiler/GNU-CXX.cmake deleted file mode 100644 index fcaaeab..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-CXX.cmake +++ /dev/null
@@ -1,58 +0,0 @@ -include(Compiler/GNU) -__compiler_gnu(CXX) - -if (WIN32) - if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.6) - set(CMAKE_CXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fno-keep-inline-dllexport") - endif() -else() - if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_CXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fvisibility-inlines-hidden") - endif() -endif() - -if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "-std=c++98") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "-std=gnu++98") -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.7) - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++11") -elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.4) - # 4.3 supports 0x variants - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++0x") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++0x") -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.8.1) - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.9) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++14") -elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.8) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++1y") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.0) - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 8.0) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std=gnu++17") -elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.1) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std=c++1z") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std=gnu++1z") -endif() - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 8.0) - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "-std=c++2a") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "-std=gnu++2a") -endif() - -__compiler_check_default_language_standard(CXX 3.4 98 6.0 14)
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-FindBinUtils.cmake b/share/cmake-3.18/Modules/Compiler/GNU-FindBinUtils.cmake deleted file mode 100644 index 097fbf3..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-FindBinUtils.cmake +++ /dev/null
@@ -1,35 +0,0 @@ -if(NOT DEFINED _CMAKE_PROCESSING_LANGUAGE OR _CMAKE_PROCESSING_LANGUAGE STREQUAL "") - message(FATAL_ERROR "Internal error: _CMAKE_PROCESSING_LANGUAGE is not set") -endif() - -# Ubuntu 16.04: -# * /usr/bin/gcc-ar-5 -# * /usr/bin/gcc-ranlib-5 -string(REGEX MATCH "^([0-9]+)" __version_x - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_VERSION}") - -string(REGEX MATCH "^([0-9]+\\.[0-9]+)" __version_x_y - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_VERSION}") - -# Try to find tools in the same directory as GCC itself -get_filename_component(__gcc_hints "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER}" DIRECTORY) - -# http://manpages.ubuntu.com/manpages/wily/en/man1/gcc-ar.1.html -find_program(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_AR NAMES - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ar-${__version_x_y}" - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ar-${__version_x}" - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ar${_CMAKE_COMPILER_SUFFIX}" - HINTS ${__gcc_hints} - DOC "A wrapper around 'ar' adding the appropriate '--plugin' option for the GCC compiler" -) -mark_as_advanced(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_AR) - -# http://manpages.ubuntu.com/manpages/wily/en/man1/gcc-ranlib.1.html -find_program(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_RANLIB NAMES - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ranlib-${__version_x_y}" - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ranlib-${__version_x}" - "${_CMAKE_TOOLCHAIN_PREFIX}gcc-ranlib${_CMAKE_COMPILER_SUFFIX}" - HINTS ${__gcc_hints} - DOC "A wrapper around 'ranlib' adding the appropriate '--plugin' option for the GCC compiler" -) -mark_as_advanced(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_RANLIB)
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-OBJC.cmake b/share/cmake-3.18/Modules/Compiler/GNU-OBJC.cmake deleted file mode 100644 index fb9b0b2..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-OBJC.cmake +++ /dev/null
@@ -1,2 +0,0 @@ -include(Compiler/GNU) -__compiler_gnu(OBJC)
diff --git a/share/cmake-3.18/Modules/Compiler/GNU-OBJCXX.cmake b/share/cmake-3.18/Modules/Compiler/GNU-OBJCXX.cmake deleted file mode 100644 index 06f0244..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU-OBJCXX.cmake +++ /dev/null
@@ -1,10 +0,0 @@ -include(Compiler/GNU) -__compiler_gnu(OBJCXX) - -if(NOT CMAKE_OBJCXX_COMPILER_VERSION VERSION_LESS 4.2) - set(CMAKE_OBJCXX_COMPILE_OPTIONS_VISIBILITY_INLINES_HIDDEN "-fvisibility-inlines-hidden") -endif() - -if(NOT CMAKE_OBJCXX_LINK_FLAGS) - set(CMAKE_OBCXX_LINK_FLAGS "-lstdc++") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/GNU.cmake b/share/cmake-3.18/Modules/Compiler/GNU.cmake deleted file mode 100644 index 668a6a9..0000000 --- a/share/cmake-3.18/Modules/Compiler/GNU.cmake +++ /dev/null
@@ -1,123 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This module is shared by multiple languages; use include blocker. -if(__COMPILER_GNU) - return() -endif() -set(__COMPILER_GNU 1) - -include(Compiler/CMakeCommonCompilerMacros) -include(Internal/CMakeCheckCompilerFlag) - -set(__pch_header_C "c-header") -set(__pch_header_CXX "c++-header") -set(__pch_header_OBJC "objective-c-header") -set(__pch_header_OBJCXX "objective-c++-header") - -macro(__compiler_gnu lang) - # Feature flags. - set(CMAKE_${lang}_VERBOSE_FLAG "-v") - set(CMAKE_${lang}_COMPILE_OPTIONS_PIC "-fPIC") - set (_CMAKE_${lang}_PIE_MAY_BE_SUPPORTED_BY_LINKER NO) - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 3.4) - set(CMAKE_${lang}_COMPILE_OPTIONS_PIE "-fPIE") - # Support of PIE at link stage depends on various elements : platform, compiler, linker - # so to activate it, module CheckPIESupported must be used. - set (_CMAKE_${lang}_PIE_MAY_BE_SUPPORTED_BY_LINKER YES) - set(CMAKE_${lang}_LINK_OPTIONS_PIE ${CMAKE_${lang}_COMPILE_OPTIONS_PIE} "-pie") - set(CMAKE_${lang}_LINK_OPTIONS_NO_PIE "-no-pie") - endif() - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 4.0) - set(CMAKE_${lang}_COMPILE_OPTIONS_VISIBILITY "-fvisibility=") - endif() - set(CMAKE_SHARED_LIBRARY_${lang}_FLAGS "-fPIC") - set(CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS "-shared") - set(CMAKE_${lang}_COMPILE_OPTIONS_SYSROOT "--sysroot=") - - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Wl,") - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG_SEP ",") - - # Older versions of gcc (< 4.5) contain a bug causing them to report a missing - # header file as a warning if depfiles are enabled, causing check_header_file - # tests to always succeed. Work around this by disabling dependency tracking - # in try_compile mode. - get_property(_IN_TC GLOBAL PROPERTY IN_TRY_COMPILE) - if(CMAKE_${lang}_COMPILER_ID STREQUAL "GNU" AND _IN_TC AND NOT CMAKE_FORCE_DEPFILES) - else() - # distcc does not transform -o to -MT when invoking the preprocessor - # internally, as it ought to. Work around this bug by setting -MT here - # even though it isn't strictly necessary. - set(CMAKE_DEPFILE_FLAGS_${lang} "-MD -MT <OBJECT> -MF <DEPFILE>") - endif() - - # Initial configuration flags. - string(APPEND CMAKE_${lang}_FLAGS_INIT " ") - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -g") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -Os -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -O3 -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -O2 -g -DNDEBUG") - set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") - set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>") - if(NOT APPLE OR NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 4) # work around #4462 - set(CMAKE_INCLUDE_SYSTEM_FLAG_${lang} "-isystem ") - endif() - - set(_CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE YES) - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER NO) - - # '-flto' introduced since GCC 4.5: - # * https://gcc.gnu.org/onlinedocs/gcc-4.4.7/gcc/Option-Summary.html (no) - # * https://gcc.gnu.org/onlinedocs/gcc-4.5.4/gcc/Option-Summary.html (yes) - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 4.5) - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER YES) - set(__lto_flags -flto) - - if(NOT CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 4.7) - # '-ffat-lto-objects' introduced since GCC 4.7: - # * https://gcc.gnu.org/onlinedocs/gcc-4.6.4/gcc/Option-Summary.html (no) - # * https://gcc.gnu.org/onlinedocs/gcc-4.7.4/gcc/Option-Summary.html (yes) - list(APPEND __lto_flags -fno-fat-lto-objects) - endif() - - set(CMAKE_${lang}_COMPILE_OPTIONS_IPO ${__lto_flags}) - - # Need to use version of 'ar'/'ranlib' with plugin support. - # Quote from [documentation][1]: - # - # To create static libraries suitable for LTO, - # use gcc-ar and gcc-ranlib instead of ar and ranlib - # - # [1]: https://gcc.gnu.org/onlinedocs/gcc-4.9.4/gcc/Optimize-Options.html - set(CMAKE_${lang}_ARCHIVE_CREATE_IPO - "\"${CMAKE_${lang}_COMPILER_AR}\" cr <TARGET> <LINK_FLAGS> <OBJECTS>" - ) - - set(CMAKE_${lang}_ARCHIVE_APPEND_IPO - "\"${CMAKE_${lang}_COMPILER_AR}\" r <TARGET> <LINK_FLAGS> <OBJECTS>" - ) - - set(CMAKE_${lang}_ARCHIVE_FINISH_IPO - "\"${CMAKE_${lang}_COMPILER_RANLIB}\" <TARGET>" - ) - endif() - - set(CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "${CMAKE_${lang}_COMPILER}") - if(CMAKE_${lang}_COMPILER_ARG1) - separate_arguments(_COMPILER_ARGS NATIVE_COMMAND "${CMAKE_${lang}_COMPILER_ARG1}") - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND ${_COMPILER_ARGS}) - unset(_COMPILER_ARGS) - endif() - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "-dM" "-E" "-c" "${CMAKE_ROOT}/Modules/CMakeCXXCompilerABI.cpp") - - if(NOT "x${lang}" STREQUAL "xFortran") - set(CMAKE_PCH_EXTENSION .gch) - if (NOT CMAKE_GENERATOR MATCHES "Xcode") - set(CMAKE_PCH_PROLOGUE "#pragma GCC system_header") - endif() - set(CMAKE_${lang}_COMPILE_OPTIONS_INVALID_PCH -Winvalid-pch) - set(CMAKE_${lang}_COMPILE_OPTIONS_USE_PCH -include <PCH_HEADER>) - set(CMAKE_${lang}_COMPILE_OPTIONS_CREATE_PCH -x ${__pch_header_${lang}} -include <PCH_HEADER>) - endif() -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/IAR-ASM.cmake b/share/cmake-3.18/Modules/Compiler/IAR-ASM.cmake deleted file mode 100644 index 936d4ae..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR-ASM.cmake +++ /dev/null
@@ -1,52 +0,0 @@ -# This file is processed when the IAR compiler is used for an assembler file - -include(Compiler/IAR) - -if("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "ARM") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> -S <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_ilink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RX") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_ilink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RH850") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_ilink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RL78") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_ilink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RISC-V") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_ilink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "AVR") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> -S <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_xlink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s90;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "MSP430") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> -S <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_xlink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s43;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "V850") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> -S <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_xlink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s85;asm;msa) - -elseif("${CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID}" STREQUAL "8051") - set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> -S <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - __compiler_iar_xlink(ASM) - set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s51;asm;msa) - -else() - message(FATAL_ERROR "CMAKE_ASM${ASM_DIALECT}_COMPILER_ARCHITECTURE_ID not detected. This should be automatic.") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/IAR-C.cmake b/share/cmake-3.18/Modules/Compiler/IAR-C.cmake deleted file mode 100644 index e27fdfc..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR-C.cmake +++ /dev/null
@@ -1,75 +0,0 @@ -# This file is processed when the IAR compiler is used for a C file - -include(Compiler/IAR) -include(Compiler/CMakeCommonCompilerMacros) - -# Common -if(NOT CMAKE_C_COMPILER_VERSION) - message(FATAL_ERROR "CMAKE_C_COMPILER_VERSION not detected. This should be automatic.") -endif() - -set(CMAKE_C_EXTENSION_COMPILE_OPTION -e) - -if(CMAKE_C_COMPILER_VERSION_INTERNAL VERSION_GREATER 7) - set(CMAKE_C90_STANDARD_COMPILE_OPTION --c89) - set(CMAKE_C90_EXTENSION_COMPILE_OPTION --c89 -e) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION -e) -else() - set(CMAKE_C90_STANDARD_COMPILE_OPTION "") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION -e) -endif() - -if(CMAKE_C_COMPILER_VERSION_INTERNAL VERSION_GREATER 8) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION -e) -endif() - -# Architecture specific -if("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "ARM") - if(CMAKE_C_COMPILER_VERSION_INTERNAL VERSION_LESS 7) - # IAR ARM 4.X uses xlink.exe, detection is not yet implemented - message(FATAL_ERROR "CMAKE_C_COMPILER_VERSION = ${CMAKE_C_COMPILER_VERSION} not supported by CMake.") - endif() - __compiler_iar_ilink(C) - __compiler_check_default_language_standard(C 1.10 90 6.10 99 8.10 11) - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "RX") - __compiler_iar_ilink(C) - __compiler_check_default_language_standard(C 1.10 90 2.10 99 4.10 11) - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "RH850") - __compiler_iar_ilink(C) - __compiler_check_default_language_standard(C 1.10 90 1.10 99 2.10 11) - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "RL78") - __compiler_iar_ilink(C) - __compiler_check_default_language_standard(C 1.10 90 1.10 99 4.10 11) - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "RISCV") - __compiler_iar_ilink(C) - __compiler_check_default_language_standard(C 1.10 90 1.10 99 1.10 11) - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "AVR") - __compiler_iar_xlink(C) - __compiler_check_default_language_standard(C 7.10 99) - set(CMAKE_C_OUTPUT_EXTENSION ".r90") - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "MSP430") - __compiler_iar_xlink(C) - __compiler_check_default_language_standard(C 1.10 90 5.10 99) - set(CMAKE_C_OUTPUT_EXTENSION ".r43") - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "V850") - __compiler_iar_xlink(C) - __compiler_check_default_language_standard(C 1.10 90 4.10 99) - set(CMAKE_C_OUTPUT_EXTENSION ".r85") - -elseif("${CMAKE_C_COMPILER_ARCHITECTURE_ID}" STREQUAL "8051") - __compiler_iar_xlink(C) - __compiler_check_default_language_standard(C 6.10 90 8.10 99) - set(CMAKE_C_OUTPUT_EXTENSION ".r51") - -else() - message(FATAL_ERROR "CMAKE_C_COMPILER_ARCHITECTURE_ID not detected. This should be automatic.") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/IAR-CXX.cmake b/share/cmake-3.18/Modules/Compiler/IAR-CXX.cmake deleted file mode 100644 index eca89c5..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR-CXX.cmake +++ /dev/null
@@ -1,83 +0,0 @@ -# This file is processed when the IAR compiler is used for a C++ file - -include(Compiler/IAR) -include(Compiler/CMakeCommonCompilerMacros) - -# Common -if(NOT CMAKE_CXX_COMPILER_VERSION) - message(FATAL_ERROR "CMAKE_CXX_COMPILER_VERSION not detected. This should be automatic.") -endif() - -if(NOT CMAKE_IAR_CXX_FLAG) - # The --c++ flag was introduced in platform version 9 for all architectures except ARM where it was introduced already in version 7 - if(CMAKE_CXX_COMPILER_VERSION_INTERNAL VERSION_GREATER 8 OR - (CMAKE_CXX_COMPILER_VERSION_INTERNAL VERSION_GREATER 6 AND "${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "ARM") ) - set(CMAKE_IAR_CXX_FLAG --c++) - else() - set(CMAKE_IAR_CXX_FLAG --eec++) - endif() -endif() - -set(CMAKE_CXX_EXTENSION_COMPILE_OPTION -e) - -if(CMAKE_CXX_COMPILER_VERSION_INTERNAL VERSION_GREATER 7) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION -e) - set(CMAKE_CXX03_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX03_EXTENSION_COMPILE_OPTION -e) -endif() - -if(CMAKE_CXX_COMPILER_VERSION_INTERNAL VERSION_GREATER 8) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION -e) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION -e) -endif() - -# Architecture specific -if("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "ARM") - if(CMAKE_CXX_COMPILER_VERSION_INTERNAL VERSION_LESS 7) - # IAR ARM 4.X uses xlink.exe, detection is not yet implemented - message(FATAL_ERROR "CMAKE_CXX_COMPILER_VERSION = ${CMAKE_C_COMPILER_VERSION} not supported by CMake.") - endif() - __compiler_iar_ilink(CXX) - __compiler_check_default_language_standard(CXX 6.10 98 8.10 14) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "RX") - __compiler_iar_ilink(CXX) - __compiler_check_default_language_standard(CXX 2.10 98 4.10 14) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "RH850") - __compiler_iar_ilink(CXX) - __compiler_check_default_language_standard(CXX 1.10 98 2.10 14) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "RL78") - __compiler_iar_ilink(CXX) - __compiler_check_default_language_standard(CXX 1.10 98 4.10 14) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "RISCV") - __compiler_iar_ilink(CXX) - __compiler_check_default_language_standard(CXX 1.10 98 1.10 14) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "AVR") - __compiler_iar_xlink(CXX) - __compiler_check_default_language_standard(CXX 7.10 98) - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "MSP430") - __compiler_iar_xlink(CXX) - __compiler_check_default_language_standard(CXX 5.10 98) - set(CMAKE_CXX_OUTPUT_EXTENSION ".r43") - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "V850") - __compiler_iar_xlink(CXX) - __compiler_check_default_language_standard(CXX 1.10 98) - set(CMAKE_C_OUTPUT_EXTENSION ".r85") - -elseif("${CMAKE_CXX_COMPILER_ARCHITECTURE_ID}" STREQUAL "8051") - __compiler_iar_xlink(CXX) - __compiler_check_default_language_standard(CXX 6.10 98) - set(CMAKE_C_OUTPUT_EXTENSION ".r51") - -else() - message(FATAL_ERROR "CMAKE_CXX_COMPILER_ARCHITECTURE_ID not detected. This should be automatic." ) -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/IAR-DetermineCompiler.cmake b/share/cmake-3.18/Modules/Compiler/IAR-DetermineCompiler.cmake deleted file mode 100644 index 0a026b2..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR-DetermineCompiler.cmake +++ /dev/null
@@ -1,39 +0,0 @@ -# IAR Systems compiler for ARM embedded systems. -# http://www.iar.com -# http://supp.iar.com/FilesPublic/UPDINFO/004916/arm/doc/EWARM_DevelopmentGuide.ENU.pdf -# -# __IAR_SYSTEMS_ICC__ An integer that identifies the IAR compiler platform: -# 9 and higher means C11 and C++14 as language default -# 8 means C99 and C++03 as language default -# 7 and lower means C89 and EC++ as language default. -# __ICCARM__ An integer that is set to 1 when the code is compiled with the IAR C/C++ Compiler for ARM -# __VER__ An integer that identifies the version number of the IAR compiler in use. For example, -# version 5.11.3 is returned as 5011003. -# -# IAR Systems Compiler for AVR embedded systems -# http://supp.iar.com/FilesPublic/UPDINFO/007051/ew/doc/EWAVR_CompilerReference.pdf -# -# __IAR_SYSTEMS_ICC__ An integer that identifies the IAR compiler platform. -# __ICCAVR__ An integer that is set to 1 when the code is compiled with the IAR C/C++ Compiler for AVR -# __VER__ An integer that identifies the version number of the IAR compiler in use. -# The value is calculated by (100 * VERSION_MAJOR + VERSION_MINOR). For example the version -# 3.34 is given as 334 -# __SUBVERSION__ An integer that identifies the subversion number of the compiler version number -# for example 3 in 1.2.3.4. THis is used as the patch version, as seen when running iccavr -# from the command line -# - -set(_compiler_id_pp_test "defined(__IAR_SYSTEMS_ICC__) || defined(__IAR_SYSTEMS_ICC)") - -set(_compiler_id_version_compute " -# if defined(__VER__) && defined(__ICCARM__) -# define @PREFIX@COMPILER_VERSION_MAJOR @MACRO_DEC@((__VER__) / 1000000) -# define @PREFIX@COMPILER_VERSION_MINOR @MACRO_DEC@(((__VER__) / 1000) % 1000) -# define @PREFIX@COMPILER_VERSION_PATCH @MACRO_DEC@((__VER__) % 1000) -# define @PREFIX@COMPILER_VERSION_INTERNAL @MACRO_DEC@(__IAR_SYSTEMS_ICC__) -# elif defined(__VER__) && (defined(__ICCAVR__) || defined(__ICCRX__) || defined(__ICCRH850__) || defined(__ICCRL78__) || defined(__ICC430__) || defined(__ICCRISCV__) || defined(__ICCV850__) || defined(__ICC8051__)) -# define @PREFIX@COMPILER_VERSION_MAJOR @MACRO_DEC@((__VER__) / 100) -# define @PREFIX@COMPILER_VERSION_MINOR @MACRO_DEC@((__VER__) - (((__VER__) / 100)*100)) -# define @PREFIX@COMPILER_VERSION_PATCH @MACRO_DEC@(__SUBVERSION__) -# define @PREFIX@COMPILER_VERSION_INTERNAL @MACRO_DEC@(__IAR_SYSTEMS_ICC__) -# endif")
diff --git a/share/cmake-3.18/Modules/Compiler/IAR-FindBinUtils.cmake b/share/cmake-3.18/Modules/Compiler/IAR-FindBinUtils.cmake deleted file mode 100644 index 6ef3759..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR-FindBinUtils.cmake +++ /dev/null
@@ -1,63 +0,0 @@ -if(NOT DEFINED _CMAKE_PROCESSING_LANGUAGE OR _CMAKE_PROCESSING_LANGUAGE STREQUAL "") - message(FATAL_ERROR "Internal error: _CMAKE_PROCESSING_LANGUAGE is not set") -endif() - -# Try to find tools in the same directory as the compiler itself -get_filename_component(__iar_hint_1 "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER}" REALPATH) -get_filename_component(__iar_hint_1 "${__iar_hint_1}" DIRECTORY) - -get_filename_component(__iar_hint_2 "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER}" DIRECTORY) - -set(__iar_hints "${__iar_hint_1}" "${__iar_hint_2}") - -if("${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "ARM" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RX" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RH850" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RL78" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "RISCV") - - string(TOLOWER "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" _archid_lower) - - # Find linker - find_program(CMAKE_IAR_LINKER ilink${_archid_lower} HINTS ${__iar_hints} - DOC "The IAR ILINK linker") - find_program(CMAKE_IAR_ARCHIVE iarchive HINTS ${__iar_hints} - DOC "The IAR archiver") - - # Find utility tools - find_program(CMAKE_IAR_ELFTOOL ielftool HINTS ${__iar_hints} - DOC "The IAR ELF Tool") - find_program(CMAKE_IAR_ELFDUMP ielfdump${_archid_lower} HINTS ${__iar_hints} - DOC "The IAR ELF Dumper") - find_program(CMAKE_IAR_OBJMANIP iobjmanip HINTS ${__iar_hints} - DOC "The IAR ELF Object Tool") - find_program(CMAKE_IAR_SYMEXPORT isymexport HINTS ${__iar_hints} - DOC "The IAR Absolute Symbol Exporter") - mark_as_advanced(CMAKE_IAR_LINKER CMAKE_IAR_ARCHIVE CMAKE_IAR_ELFTOOL CMAKE_IAR_ELFDUMP CMAKE_IAR_OBJMANIP CMAKE_IAR_SYMEXPORT) - - set(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_CUSTOM_CODE -"set(CMAKE_IAR_LINKER \"${CMAKE_IAR_LINKER}\") -set(CMAKE_IAR_ARCHIVE \"${CMAKE_IAR_ARCHIVE}\") -set(CMAKE_IAR_ELFTOOL \"${CMAKE_IAR_ELFTOOL}\") -set(CMAKE_IAR_ELFDUMP \"${CMAKE_IAR_ELFDUMP}\") -set(CMAKE_IAR_OBJMANIP \"${CMAKE_IAR_OBJMANIP}\") -set(CMAKE_IAR_LINKER \"${CMAKE_IAR_LINKER}\") -") - -elseif("${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "AVR" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "MSP430" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "V850" OR - "${CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_ARCHITECTURE_ID}" STREQUAL "8051") - - # Find the "xlink" linker and "xar" archiver: - find_program(CMAKE_IAR_LINKER xlink HINTS ${__iar_hints} - DOC "The IAR XLINK linker") - find_program(CMAKE_IAR_AR xar HINTS ${__iar_hints} - DOC "The IAR archiver") - mark_as_advanced(CMAKE_IAR_LINKER CMAKE_IAR_AR) - - set(CMAKE_${_CMAKE_PROCESSING_LANGUAGE}_COMPILER_CUSTOM_CODE -"set(CMAKE_IAR_LINKER \"${CMAKE_IAR_LINKER}\") -set(CMAKE_IAR_AR \"${CMAKE_IAR_AR}\") -") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/IAR.cmake b/share/cmake-3.18/Modules/Compiler/IAR.cmake deleted file mode 100644 index 296e2fd..0000000 --- a/share/cmake-3.18/Modules/Compiler/IAR.cmake +++ /dev/null
@@ -1,114 +0,0 @@ -# This file is processed when the IAR compiler is used for a C or C++ file -# Documentation can be downloaded here: http://www.iar.com/website1/1.0.1.0/675/1/ -# The initial feature request is here: https://gitlab.kitware.com/cmake/cmake/-/issues/10176 -# It also contains additional links and information. -# See USER GUIDES -> C/C++ Development Guide and ReleaseNotes for EWARM: -# version 6.30.8: http://supp.iar.com/FilesPublic/UPDINFO/006607/arm/doc/infocenter/index.ENU.html -# version 7.60.1: http://supp.iar.com/FilesPublic/UPDINFO/011006/arm/doc/infocenter/index.ENU.html -# version 8.10.1: http://netstorage.iar.com/SuppDB/Public/UPDINFO/011854/arm/doc/infocenter/index.ENU.html - -# The IAR internal compiler platform generations (Predefined symbol __IAR_SYSTEMS_ICC__): -# 9 and higher means C11 and C++14 as language default (EWARM v8.x, EWRX v4.x and higher) -# 8 means C99 and C++03 as language default (EWARM v6.x, v7.x. EWRX v2.x, 3.x) -# 7 and lower means C89 and EC++ as language default. (EWARM v5.x and lower) - -# C/C++ Standard versions -# -# IAR typically only supports one C and C++ Standard version, -# the exception is C89 which is always supported and can be selected -# if its not the default -# -# C++ is trickier, there were historically 3 switches, -# and some IAR versions support multiple of those. -# they are --eec++, --ec++ and --c++ and where used to -# enable various language features like exceptions -# -# recent versions only have --c++ for full support -# but can choose to disable features with further arguments -# -# C/C++ Standard compliance -# -# IAR has 3 modes: default, strict and extended -# the extended mode is needed for popular libraries like CMSIS -# -# "Silent" Operation -# -# this really is different to most programs I know. -# nothing meaningful from the operation is lost, just some redundant -# code and data size printouts (that can be inspected with common tools). - -# This module is shared by multiple languages; use include blocker. -include_guard() - -macro(__compiler_iar_ilink lang) - set(CMAKE_EXECUTABLE_SUFFIX ".elf") - if (${lang} STREQUAL "C" OR ${lang} STREQUAL "CXX") - set(CMAKE_${lang}_COMPILE_OBJECT "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> --preprocess=cnl <PREPROCESSED_SOURCE>") - set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -lAH <ASSEMBLY_SOURCE> -o <OBJECT>.dummy") - - set(CMAKE_${lang}_RESPONSE_FILE_LINK_FLAG "-f ") - set(CMAKE_DEPFILE_FLAGS_${lang} "--dependencies=ns <DEPFILE>") - - string(APPEND CMAKE_${lang}_FLAGS_INIT " ") - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -r") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -Ohz -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -Oh -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -Oh -r -DNDEBUG") - endif() - - if (${lang} STREQUAL "ASM") - string(APPEND CMAKE_ASM_FLAGS_INIT " ") - string(APPEND CMAKE_ASM_FLAGS_DEBUG_INIT " -r") - string(APPEND CMAKE_ASM_FLAGS_MINSIZEREL_INIT " -DNDEBUG") - string(APPEND CMAKE_ASM_FLAGS_RELEASE_INIT " -DNDEBUG") - string(APPEND CMAKE_ASM_FLAGS_RELWITHDEBINFO_INIT " -r -DNDEBUG") - endif() - - set(CMAKE_${lang}_LINK_EXECUTABLE "\"${CMAKE_IAR_LINKER}\" --silent <OBJECTS> <CMAKE_${lang}_LINK_FLAGS> <LINK_FLAGS> <LINK_LIBRARIES> -o <TARGET>") - set(CMAKE_${lang}_CREATE_STATIC_LIBRARY "\"${CMAKE_IAR_ARCHIVE}\" <TARGET> --create <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_CREATE "\"${CMAKE_IAR_ARCHIVE}\" <TARGET> --create <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_APPEND "\"${CMAKE_IAR_ARCHIVE}\" <TARGET> --replace <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_FINISH "") - - set(CMAKE_LINKER "${CMAKE_IAR_LINKER}" CACHE FILEPATH "The IAR linker" FORCE) - set(CMAKE_AR "${CMAKE_IAR_ARCHIVE}" CACHE FILEPATH "The IAR archiver" FORCE) -endmacro() - -macro(__compiler_iar_xlink lang) - set(CMAKE_EXECUTABLE_SUFFIX ".bin") - if (${lang} STREQUAL "C" OR ${lang} STREQUAL "CXX") - - set(CMAKE_${lang}_COMPILE_OBJECT "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT>") - set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> --preprocess=cnl <PREPROCESSED_SOURCE>") - set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "<CMAKE_${lang}_COMPILER> ${CMAKE_IAR_${lang}_FLAG} --silent <SOURCE> <DEFINES> <INCLUDES> <FLAGS> -lAH <ASSEMBLY_SOURCE> -o <OBJECT>.dummy") - - set(CMAKE_${lang}_RESPONSE_FILE_LINK_FLAG "-f ") - set(CMAKE_DEPFILE_FLAGS_${lang} "--dependencies=ns <DEPFILE>") - - string(APPEND CMAKE_${lang}_FLAGS_INIT " ") - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -r") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -Ohz -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -Oh -DNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -Oh -r -DNDEBUG") - endif() - - if (${lang} STREQUAL "ASM") - string(APPEND CMAKE_ASM_FLAGS_INIT " ") - string(APPEND CMAKE_ASM_FLAGS_DEBUG_INIT " -r") - string(APPEND CMAKE_ASM_FLAGS_MINSIZEREL_INIT " -DNDEBUG") - string(APPEND CMAKE_ASM_FLAGS_RELEASE_INIT " -DNDEBUG") - string(APPEND CMAKE_ASM_FLAGS_RELWITHDEBINFO_INIT " -r -DNDEBUG") - endif() - - set(CMAKE_${lang}_LINK_EXECUTABLE "\"${CMAKE_IAR_LINKER}\" -S <OBJECTS> <CMAKE_${lang}_LINK_FLAGS> <LINK_FLAGS> <LINK_LIBRARIES> -o <TARGET>") - set(CMAKE_${lang}_CREATE_STATIC_LIBRARY "\"${CMAKE_IAR_AR}\" <TARGET> <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_CREATE "\"${CMAKE_IAR_AR}\" <TARGET> <LINK_FLAGS> <OBJECTS>") - set(CMAKE_${lang}_ARCHIVE_APPEND "") - set(CMAKE_${lang}_ARCHIVE_FINISH "") - - set(CMAKE_LIBRARY_PATH_FLAG "-I") - - set(CMAKE_LINKER "${CMAKE_IAR_LINKER}" CACHE FILEPATH "The IAR linker" FORCE) - set(CMAKE_AR "${CMAKE_IAR_AR}" CACHE FILEPATH "The IAR archiver" FORCE) -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/Intel-C.cmake b/share/cmake-3.18/Modules/Compiler/Intel-C.cmake deleted file mode 100644 index ec3bfd8..0000000 --- a/share/cmake-3.18/Modules/Compiler/Intel-C.cmake +++ /dev/null
@@ -1,51 +0,0 @@ -include(Compiler/Intel) -__compiler_intel(C) - -string(APPEND CMAKE_C_FLAGS_MINSIZEREL_INIT " -DNDEBUG") -string(APPEND CMAKE_C_FLAGS_RELEASE_INIT " -DNDEBUG") -string(APPEND CMAKE_C_FLAGS_RELWITHDEBINFO_INIT " -DNDEBUG") - -set(CMAKE_DEPFILE_FLAGS_C "-MD -MT <OBJECT> -MF <DEPFILE>") - -if("x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC") - - set(CMAKE_C_CLANG_TIDY_DRIVER_MODE "cl") - - if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 16.0.0) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-Qstd=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-Qstd=c11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 12.0) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-Qstd=c89") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-Qstd=c89") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-Qstd=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-Qstd=c99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - endif() - -else() - - if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 15.0.0) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - if (NOT CMAKE_C_COMPILER_VERSION VERSION_LESS 12.0) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c89") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu89") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - endif() - -endif() - -__compiler_check_default_language_standard(C 12.0 90 15.0.0 11) - -set(CMAKE_C_CREATE_PREPROCESSED_SOURCE "<CMAKE_C_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_C_CREATE_ASSEMBLY_SOURCE "<CMAKE_C_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>")
diff --git a/share/cmake-3.18/Modules/Compiler/Intel-CXX.cmake b/share/cmake-3.18/Modules/Compiler/Intel-CXX.cmake deleted file mode 100644 index b71b946..0000000 --- a/share/cmake-3.18/Modules/Compiler/Intel-CXX.cmake +++ /dev/null
@@ -1,96 +0,0 @@ -include(Compiler/Intel) -__compiler_intel(CXX) - -string(APPEND CMAKE_CXX_FLAGS_MINSIZEREL_INIT " -DNDEBUG") -string(APPEND CMAKE_CXX_FLAGS_RELEASE_INIT " -DNDEBUG") -string(APPEND CMAKE_CXX_FLAGS_RELWITHDEBINFO_INIT " -DNDEBUG") - -set(CMAKE_DEPFILE_FLAGS_CXX "-MD -MT <OBJECT> -MF <DEPFILE>") - -if("x${CMAKE_CXX_SIMULATE_ID}" STREQUAL "xMSVC") - - set(CMAKE_CXX_CLANG_TIDY_DRIVER_MODE "cl") - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19.0.0) - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "-Qstd=c++20") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "-Qstd=c++20") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 18.0.0) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-Qstd=c++17") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-Qstd=c++17") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 16.0) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-Qstd=c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-Qstd=c++14") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 13.0) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-Qstd=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-Qstd=c++11") - elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 12.1) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-Qstd=c++0x") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-Qstd=c++0x") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 12.1) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - endif() - -else() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19.0.0) - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "-std=c++20") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "-std=gnu++20") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 18.0.0) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std=gnu++17") - endif() - - if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 17.0) - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 15.0.2) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++14") - elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 15.0.0) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++1y") - endif() - - # Intel 15.0.2 accepts c++14 instead of c++1y, but not gnu++14 - # instead of gnu++1y. Intel 17.0.0 accepts gnu++14 too. - if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 17.0) - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++14") - elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 15.0.0) - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 15.0) - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 13.0) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++11") - elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 12.1) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++0x") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++0x") - endif() - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 12.1) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "-std=c++98") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "-std=gnu++98") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - endif() - -endif() - -__compiler_check_default_language_standard(CXX 12.1 98) - -set(CMAKE_CXX_CREATE_PREPROCESSED_SOURCE "<CMAKE_CXX_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_CXX_CREATE_ASSEMBLY_SOURCE "<CMAKE_CXX_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>")
diff --git a/share/cmake-3.18/Modules/Compiler/Intel-DetermineCompiler.cmake b/share/cmake-3.18/Modules/Compiler/Intel-DetermineCompiler.cmake deleted file mode 100644 index c31aa77..0000000 --- a/share/cmake-3.18/Modules/Compiler/Intel-DetermineCompiler.cmake +++ /dev/null
@@ -1,40 +0,0 @@ - -set(_compiler_id_pp_test "defined(__INTEL_COMPILER) || defined(__ICC)") - -set(_compiler_id_version_compute " - /* __INTEL_COMPILER = VRP */ -# define @PREFIX@COMPILER_VERSION_MAJOR @MACRO_DEC@(__INTEL_COMPILER/100) -# define @PREFIX@COMPILER_VERSION_MINOR @MACRO_DEC@(__INTEL_COMPILER/10 % 10) -# if defined(__INTEL_COMPILER_UPDATE) -# define @PREFIX@COMPILER_VERSION_PATCH @MACRO_DEC@(__INTEL_COMPILER_UPDATE) -# else -# define @PREFIX@COMPILER_VERSION_PATCH @MACRO_DEC@(__INTEL_COMPILER % 10) -# endif -# if defined(__INTEL_COMPILER_BUILD_DATE) - /* __INTEL_COMPILER_BUILD_DATE = YYYYMMDD */ -# define @PREFIX@COMPILER_VERSION_TWEAK @MACRO_DEC@(__INTEL_COMPILER_BUILD_DATE) -# endif -# if defined(_MSC_VER) - /* _MSC_VER = VVRR */ -# define @PREFIX@SIMULATE_VERSION_MAJOR @MACRO_DEC@(_MSC_VER / 100) -# define @PREFIX@SIMULATE_VERSION_MINOR @MACRO_DEC@(_MSC_VER % 100) -# endif -# if defined(__GNUC__) -# define @PREFIX@SIMULATE_VERSION_MAJOR @MACRO_DEC@(__GNUC__) -# elif defined(__GNUG__) -# define @PREFIX@SIMULATE_VERSION_MAJOR @MACRO_DEC@(__GNUG__) -# endif -# if defined(__GNUC_MINOR__) -# define @PREFIX@SIMULATE_VERSION_MINOR @MACRO_DEC@(__GNUC_MINOR__) -# endif -# if defined(__GNUC_PATCHLEVEL__) -# define @PREFIX@SIMULATE_VERSION_PATCH @MACRO_DEC@(__GNUC_PATCHLEVEL__) -# endif") - -set(_compiler_id_simulate " -# if defined(_MSC_VER) -# define @PREFIX@SIMULATE_ID \"MSVC\" -# endif -# if defined(__GNUC__) -# define @PREFIX@SIMULATE_ID \"GNU\" -# endif")
diff --git a/share/cmake-3.18/Modules/Compiler/Intel-Fortran.cmake b/share/cmake-3.18/Modules/Compiler/Intel-Fortran.cmake deleted file mode 100644 index 71f25f4..0000000 --- a/share/cmake-3.18/Modules/Compiler/Intel-Fortran.cmake +++ /dev/null
@@ -1,19 +0,0 @@ -include(Compiler/Intel) -__compiler_intel(Fortran) - -set(CMAKE_Fortran_SUBMODULE_SEP "@") -set(CMAKE_Fortran_SUBMODULE_EXT ".smod") - -set(CMAKE_Fortran_MODDIR_FLAG "-module ") -set(CMAKE_Fortran_FORMAT_FIXED_FLAG "-fixed") -set(CMAKE_Fortran_FORMAT_FREE_FLAG "-free") - -set(CMAKE_Fortran_COMPILE_WITH_DEFINES 1) - -set(CMAKE_Fortran_CREATE_PREPROCESSED_SOURCE "<CMAKE_Fortran_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_Fortran_CREATE_ASSEMBLY_SOURCE "<CMAKE_Fortran_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>") - -set(CMAKE_Fortran_PREPROCESS_SOURCE - "<CMAKE_Fortran_COMPILER> -fpp <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_ON "-fpp") -set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_OFF "-nofpp")
diff --git a/share/cmake-3.18/Modules/Compiler/MSVC-C-FeatureTests.cmake b/share/cmake-3.18/Modules/Compiler/MSVC-C-FeatureTests.cmake deleted file mode 100644 index 3f09be2..0000000 --- a/share/cmake-3.18/Modules/Compiler/MSVC-C-FeatureTests.cmake +++ /dev/null
@@ -1,8 +0,0 @@ -set(_cmake_oldestSupported "_MSC_VER >= 1600") - -# Not yet supported: -#set(_cmake_feature_test_c_static_assert "") -#set(_cmake_feature_test_c_restrict "") - -set(_cmake_feature_test_c_variadic_macros "${_cmake_oldestSupported}") -set(_cmake_feature_test_c_function_prototypes "${_cmake_oldestSupported}")
diff --git a/share/cmake-3.18/Modules/Compiler/MSVC-C.cmake b/share/cmake-3.18/Modules/Compiler/MSVC-C.cmake deleted file mode 100644 index bca9764..0000000 --- a/share/cmake-3.18/Modules/Compiler/MSVC-C.cmake +++ /dev/null
@@ -1,40 +0,0 @@ -# MSVC has no specific options to set C language standards, but set them as -# empty strings anyways so the feature test infrastructure can at least check -# to see if they are defined. -set(CMAKE_C90_STANDARD_COMPILE_OPTION "") -set(CMAKE_C90_EXTENSION_COMPILE_OPTION "") -set(CMAKE_C99_STANDARD_COMPILE_OPTION "") -set(CMAKE_C99_EXTENSION_COMPILE_OPTION "") -set(CMAKE_C11_STANDARD_COMPILE_OPTION "") -set(CMAKE_C11_EXTENSION_COMPILE_OPTION "") - -# There is no meaningful default for this -set(CMAKE_C_STANDARD_DEFAULT "") - -set(CMAKE_C_CLANG_TIDY_DRIVER_MODE "cl") - -# There are no C compiler modes so we hard-code the known compiler supported -# features. Override the default macro for this special case. Pretend that -# all language standards are available so that at least compilation -# can be attempted. -macro(cmake_record_c_compile_features) - list(APPEND CMAKE_C_COMPILE_FEATURES - c_std_90 - c_std_99 - c_std_11 - c_function_prototypes - ) - list(APPEND CMAKE_C90_COMPILE_FEATURES c_std_90 c_function_prototypes) - list(APPEND CMAKE_C99_COMPILE_FEATURES c_std_99) - list(APPEND CMAKE_C11_COMPILE_FEATURES c_std_11) - if (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 14.0) - list(APPEND CMAKE_C_COMPILE_FEATURES c_variadic_macros) - list(APPEND CMAKE_C99_COMPILE_FEATURES c_variadic_macros) - endif() - set(_result 0) # expected by cmake_determine_compile_features -endmacro() - -# /JMC "Just My Code" is only supported by MSVC 19.05 onward. -if (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 19.05) - set(CMAKE_C_COMPILE_OPTIONS_JMC "-JMC") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/MSVC-CXX.cmake b/share/cmake-3.18/Modules/Compiler/MSVC-CXX.cmake deleted file mode 100644 index 1dfc760..0000000 --- a/share/cmake-3.18/Modules/Compiler/MSVC-CXX.cmake +++ /dev/null
@@ -1,74 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(Compiler/CMakeCommonCompilerMacros) - -set(CMAKE_CXX_CLANG_TIDY_DRIVER_MODE "cl") - -if ((CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 19.0.24215.1 AND - CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19.10) OR - CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 19.10.25017) - - # VS 2015 Update 3 and above support language standard level flags, - # with the default and minimum level being C++14. - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std:c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std:c++14") - if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 19.11.25505) - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std:c++17") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std:c++17") - else() - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "-std:c++latest") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "-std:c++latest") - endif() - if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 19.12.25835) - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "-std:c++latest") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "-std:c++latest") - endif() - - __compiler_check_default_language_standard(CXX 19.0 14) - -elseif (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 16.0) - # MSVC has no specific options to set language standards, but set them as - # empty strings anyways so the feature test infrastructure can at least check - # to see if they are defined. - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX20_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX20_EXTENSION_COMPILE_OPTION "") - - # There is no meaningful default for this - set(CMAKE_CXX_STANDARD_DEFAULT "") - - # There are no compiler modes so we only need to test features once. - # Override the default macro for this special case. Pretend that - # all language standards are available so that at least compilation - # can be attempted. - macro(cmake_record_cxx_compile_features) - list(APPEND CMAKE_CXX_COMPILE_FEATURES - cxx_std_98 - cxx_std_11 - cxx_std_14 - cxx_std_17 - cxx_std_20 - ) - _record_compiler_features(CXX "" CMAKE_CXX_COMPILE_FEATURES) - endmacro() -endif() - -# /JMC "Just My Code" is only supported by MSVC 19.05 onward. -if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 19.05) - set(CMAKE_CXX_COMPILE_OPTIONS_JMC "-JMC") -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/NAG-Fortran.cmake b/share/cmake-3.18/Modules/Compiler/NAG-Fortran.cmake deleted file mode 100644 index ffce97e..0000000 --- a/share/cmake-3.18/Modules/Compiler/NAG-Fortran.cmake +++ /dev/null
@@ -1,40 +0,0 @@ -# Help CMAKE_PARSE_IMPLICIT_LINK_INFO detect NAG Fortran object files. -if(NOT CMAKE_Fortran_COMPILER_WORKS AND NOT CMAKE_Fortran_COMPILER_FORCED) - message(CHECK_START "Detecting NAG Fortran directory") - # Run with -dryrun to see sample "link" line. - execute_process( - COMMAND ${CMAKE_Fortran_COMPILER} dummy.o -dryrun - OUTPUT_VARIABLE _dryrun - ERROR_VARIABLE _dryrun - ) - # Match an object file. - string(REGEX MATCH "/[^ ]*/[^ /][^ /]*\\.o" _nag_obj "${_dryrun}") - if(_nag_obj) - # Parse object directory and convert to a regex. - string(REGEX REPLACE "/[^/]*$" "" _nag_dir "${_nag_obj}") - string(REGEX REPLACE "([][+.*()^])" "\\\\\\1" _nag_regex "${_nag_dir}") - set(CMAKE_Fortran_IMPLICIT_OBJECT_REGEX "^${_nag_regex}/") - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log - "Detecting NAG Fortran directory with -dryrun found\n" - " object: ${_nag_obj}\n" - " directory: ${_nag_dir}\n" - " regex: ${CMAKE_Fortran_IMPLICIT_OBJECT_REGEX}\n" - "from output:\n${_dryrun}\n\n") - message(CHECK_PASS "${_nag_dir}") - else() - file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeError.log - "Detecting NAG Fortran directory with -dryrun failed:\n${_dryrun}\n\n") - message(CHECK_FAIL "failed") - endif() -endif() - -set(CMAKE_Fortran_SUBMODULE_SEP ".") -set(CMAKE_Fortran_SUBMODULE_EXT ".sub") -set(CMAKE_Fortran_MODDIR_FLAG "-mdir ") -set(CMAKE_SHARED_LIBRARY_Fortran_FLAGS "-PIC") -set(CMAKE_Fortran_FORMAT_FIXED_FLAG "-fixed") -set(CMAKE_Fortran_FORMAT_FREE_FLAG "-free") -set(CMAKE_Fortran_COMPILE_OPTIONS_PIC "-PIC") -set(CMAKE_Fortran_COMPILE_OPTIONS_PIE "-PIC") -set(CMAKE_Fortran_RESPONSE_FILE_LINK_FLAG "-Wl,@") -set(CMAKE_Fortran_COMPILE_OPTIONS_PREPROCESS_ON "-fpp")
diff --git a/share/cmake-3.18/Modules/Compiler/NVIDIA-CUDA.cmake b/share/cmake-3.18/Modules/Compiler/NVIDIA-CUDA.cmake deleted file mode 100644 index feb5ecc..0000000 --- a/share/cmake-3.18/Modules/Compiler/NVIDIA-CUDA.cmake +++ /dev/null
@@ -1,119 +0,0 @@ -include(Compiler/CMakeCommonCompilerMacros) - -set(CMAKE_CUDA_COMPILER_HAS_DEVICE_LINK_PHASE True) -set(CMAKE_CUDA_VERBOSE_FLAG "-v") -set(CMAKE_CUDA_VERBOSE_COMPILE_FLAG "-Xcompiler=-v") - -set(_CMAKE_COMPILE_AS_CUDA_FLAG "-x cu") -set(_CMAKE_CUDA_PTX_FLAG "-ptx") - -if (CMAKE_CUDA_COMPILER_VERSION VERSION_GREATER_EQUAL 10.2.89) - # The -forward-unknown-to-host-compiler flag was only - # added to nvcc in 10.2 so before that we had no good - # way to invoke the CUDA compiler and propagate unknown - # flags such as -pthread to the host compiler - set(_CMAKE_CUDA_EXTRA_FLAGS "-forward-unknown-to-host-compiler") -else() - set(_CMAKE_CUDA_EXTRA_FLAGS "") -endif() - -if(CMAKE_CUDA_COMPILER_VERSION VERSION_GREATER_EQUAL "8.0.0") - set(_CMAKE_CUDA_EXTRA_DEVICE_LINK_FLAGS "-Wno-deprecated-gpu-targets") -else() - set(_CMAKE_CUDA_EXTRA_DEVICE_LINK_FLAGS "") -endif() - -if (CMAKE_CUDA_COMPILER_VERSION VERSION_GREATER_EQUAL 10.2.89) - # The -MD flag was only added to nvcc in 10.2 so - # before that we had to invoke the compiler twice - # to get header dependency information - set(CMAKE_DEPFILE_FLAGS_CUDA "-MD -MT <OBJECT> -MF <DEPFILE>") -endif() - -if(NOT "x${CMAKE_CUDA_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CUDA_COMPILE_OPTIONS_PIE -Xcompiler=-fPIE) - set(CMAKE_CUDA_COMPILE_OPTIONS_PIC -Xcompiler=-fPIC) - set(CMAKE_CUDA_COMPILE_OPTIONS_VISIBILITY -Xcompiler=-fvisibility=) - # CMAKE_SHARED_LIBRARY_CUDA_FLAGS is sent to the host linker so we - # don't need to forward it through nvcc. - set(CMAKE_SHARED_LIBRARY_CUDA_FLAGS -fPIC) - string(APPEND CMAKE_CUDA_FLAGS_INIT " ") - string(APPEND CMAKE_CUDA_FLAGS_DEBUG_INIT " -g") - string(APPEND CMAKE_CUDA_FLAGS_RELEASE_INIT " -O3 -DNDEBUG") - string(APPEND CMAKE_CUDA_FLAGS_MINSIZEREL_INIT " -O1 -DNDEBUG") - string(APPEND CMAKE_CUDA_FLAGS_RELWITHDEBINFO_INIT " -O2 -g -DNDEBUG") -endif() -set(CMAKE_SHARED_LIBRARY_CREATE_CUDA_FLAGS -shared) -set(CMAKE_INCLUDE_SYSTEM_FLAG_CUDA -isystem=) - -if (CMAKE_CUDA_SIMULATE_ID STREQUAL "GNU") - set(CMAKE_CUDA_LINKER_WRAPPER_FLAG "-Wl,") - set(CMAKE_CUDA_LINKER_WRAPPER_FLAG_SEP ",") -elseif(CMAKE_CUDA_SIMULATE_ID STREQUAL "Clang") - set(CMAKE_CUDA_LINKER_WRAPPER_FLAG "-Xlinker" " ") - set(CMAKE_CUDA_LINKER_WRAPPER_FLAG_SEP) -endif() - -set(CMAKE_CUDA_DEVICE_COMPILER_WRAPPER_FLAG "-Xcompiler=") -set(CMAKE_CUDA_DEVICE_COMPILER_WRAPPER_FLAG_SEP ",") -set(CMAKE_CUDA_DEVICE_LINKER_WRAPPER_FLAG "-Xlinker=") -set(CMAKE_CUDA_DEVICE_LINKER_WRAPPER_FLAG_SEP ",") - -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_STATIC "cudadevrt;cudart_static") -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_SHARED "cudadevrt;cudart") -set(CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_NONE "") - -if(UNIX) - list(APPEND CMAKE_CUDA_RUNTIME_LIBRARY_LINK_OPTIONS_STATIC "rt" "pthread" "dl") -endif() - -if("x${CMAKE_CUDA_SIMULATE_ID}" STREQUAL "xMSVC") - set(CMAKE_CUDA03_STANDARD_COMPILE_OPTION "") - set(CMAKE_CUDA03_EXTENSION_COMPILE_OPTION "") - - set(CMAKE_CUDA11_STANDARD_COMPILE_OPTION "") - set(CMAKE_CUDA11_EXTENSION_COMPILE_OPTION "") - - if (NOT CMAKE_CUDA_COMPILER_VERSION VERSION_LESS 9.0) - set(CMAKE_CUDA14_STANDARD_COMPILE_OPTION "") - set(CMAKE_CUDA14_EXTENSION_COMPILE_OPTION "") - endif() - - if (NOT CMAKE_CUDA_COMPILER_VERSION VERSION_LESS 11.0) - set(CMAKE_CUDA17_STANDARD_COMPILE_OPTION "") - set(CMAKE_CUDA17_EXTENSION_COMPILE_OPTION "") - endif() - -else() - set(CMAKE_CUDA03_STANDARD_COMPILE_OPTION "") - set(CMAKE_CUDA03_EXTENSION_COMPILE_OPTION "") - - set(CMAKE_CUDA11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CUDA11_EXTENSION_COMPILE_OPTION "-std=c++11") - - if (NOT CMAKE_CUDA_COMPILER_VERSION VERSION_LESS 9.0) - set(CMAKE_CUDA03_STANDARD_COMPILE_OPTION "-std=c++03") - set(CMAKE_CUDA03_EXTENSION_COMPILE_OPTION "-std=c++03") - set(CMAKE_CUDA14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_CUDA14_EXTENSION_COMPILE_OPTION "-std=c++14") - endif() - - if (NOT CMAKE_CUDA_COMPILER_VERSION VERSION_LESS 11.0) - set(CMAKE_CUDA17_STANDARD_COMPILE_OPTION "-std=c++17") - set(CMAKE_CUDA17_EXTENSION_COMPILE_OPTION "-std=c++17") - endif() - -endif() - -# FIXME: investigate use of --options-file. -# Tell Makefile generator that nvcc does not support @<rspfile> syntax. -set(CMAKE_CUDA_USE_RESPONSE_FILE_FOR_INCLUDES 0) -set(CMAKE_CUDA_USE_RESPONSE_FILE_FOR_LIBRARIES 0) -set(CMAKE_CUDA_USE_RESPONSE_FILE_FOR_OBJECTS 0) - -if (CMAKE_CUDA_COMPILER_VERSION VERSION_GREATER_EQUAL "9.0") - set(CMAKE_CUDA_RESPONSE_FILE_DEVICE_LINK_FLAG "--options-file ") - set(CMAKE_CUDA_RESPONSE_FILE_FLAG "--options-file ") -endif() - -__compiler_check_default_language_standard(CUDA 6.0 03)
diff --git a/share/cmake-3.18/Modules/Compiler/OpenWatcom.cmake b/share/cmake-3.18/Modules/Compiler/OpenWatcom.cmake deleted file mode 100644 index 9efbfc2..0000000 --- a/share/cmake-3.18/Modules/Compiler/OpenWatcom.cmake +++ /dev/null
@@ -1,118 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -# This module is shared by multiple languages; use include blocker. -include_guard() - -set(CMAKE_LIBRARY_PATH_FLAG "libpath ") -set(CMAKE_LINK_LIBRARY_FLAG "library ") -set(CMAKE_LINK_LIBRARY_FILE_FLAG "library ") - -if(CMAKE_VERBOSE_MAKEFILE) - set(CMAKE_WCL_QUIET) - set(CMAKE_WLINK_QUIET) - set(CMAKE_LIB_QUIET) -else() - set(CMAKE_WCL_QUIET "-zq") - set(CMAKE_WLINK_QUIET "option quiet") - set(CMAKE_LIB_QUIET "-q") -endif() - -foreach(type CREATE_SHARED_LIBRARY CREATE_SHARED_MODULE LINK_EXECUTABLE) - set(CMAKE_C_${type}_USE_WATCOM_QUOTE 1) - set(CMAKE_CXX_${type}_USE_WATCOM_QUOTE 1) -endforeach() - -foreach(type SHARED MODULE EXE) - # linker map file creation directives - string(APPEND CMAKE_${type}_LINKER_FLAGS_INIT " opt map") - # linker debug directives - string(APPEND CMAKE_${type}_LINKER_FLAGS_DEBUG_INIT " debug all") - string(APPEND CMAKE_${type}_LINKER_FLAGS_RELWITHDEBINFO_INIT " debug all") -endforeach() - -foreach(lang C CXX) - # warning level - string(APPEND CMAKE_${lang}_FLAGS_INIT " -w3") - # debug options - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -d2") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -s -os -d0 -dNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -s -ot -d0 -dNDEBUG") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -s -ot -d1 -dNDEBUG") -endforeach() - -# C create import library -set(CMAKE_C_CREATE_IMPORT_LIBRARY - "wlib -c -q -n -b <TARGET_IMPLIB> +<TARGET_QUOTED>") -# C++ create import library -set(CMAKE_CXX_CREATE_IMPORT_LIBRARY ${CMAKE_C_CREATE_IMPORT_LIBRARY}) - -# C link a object files into an executable file -set(CMAKE_C_LINK_EXECUTABLE - "wlink ${CMAKE_WLINK_QUIET} name <TARGET> <LINK_FLAGS> file {<OBJECTS>} <LINK_LIBRARIES>") -# C++ link a object files into an executable file -set(CMAKE_CXX_LINK_EXECUTABLE ${CMAKE_C_LINK_EXECUTABLE}) - -# C compile a file into an object file -set(CMAKE_C_COMPILE_OBJECT - "<CMAKE_C_COMPILER> ${CMAKE_WCL_QUIET} -d+ <DEFINES> <INCLUDES> <FLAGS> -fo<OBJECT> -c -cc <SOURCE>") -# C++ compile a file into an object file -set(CMAKE_CXX_COMPILE_OBJECT - "<CMAKE_CXX_COMPILER> ${CMAKE_WCL_QUIET} -d+ <DEFINES> <INCLUDES> <FLAGS> -fo<OBJECT> -c -cc++ <SOURCE>") - -# C preprocess a source file -set(CMAKE_C_CREATE_PREPROCESSED_SOURCE - "<CMAKE_C_COMPILER> ${CMAKE_WCL_QUIET} -d+ <DEFINES> <INCLUDES> <FLAGS> -fo<PREPROCESSED_SOURCE> -pl -cc <SOURCE>") -# C++ preprocess a source file -set(CMAKE_CXX_CREATE_PREPROCESSED_SOURCE - "<CMAKE_CXX_COMPILER> ${CMAKE_WCL_QUIET} -d+ <DEFINES> <INCLUDES> <FLAGS> -fo<PREPROCESSED_SOURCE> -pl -cc++ <SOURCE>") - -# C create a shared library -set(CMAKE_C_CREATE_SHARED_LIBRARY - "wlink ${CMAKE_WLINK_QUIET} name <TARGET> <LINK_FLAGS> option implib=<TARGET_IMPLIB> file {<OBJECTS>} <LINK_LIBRARIES>") -# C++ create a shared library -set(CMAKE_CXX_CREATE_SHARED_LIBRARY ${CMAKE_C_CREATE_SHARED_LIBRARY}) - -# C create a shared module -set(CMAKE_C_CREATE_SHARED_MODULE - "wlink ${CMAKE_WLINK_QUIET} name <TARGET> <LINK_FLAGS> file {<OBJECTS>} <LINK_LIBRARIES>") -# C++ create a shared module -set(CMAKE_CXX_CREATE_SHARED_MODULE ${CMAKE_C_CREATE_SHARED_MODULE}) - -# C create a static library -set(CMAKE_C_CREATE_STATIC_LIBRARY - "wlib ${CMAKE_LIB_QUIET} -c -n -b <TARGET_QUOTED> <LINK_FLAGS> <OBJECTS> ") -# C++ create a static library -set(CMAKE_CXX_CREATE_STATIC_LIBRARY ${CMAKE_C_CREATE_STATIC_LIBRARY}) - - -# old CMake internaly used OpenWatcom version macros -# for backward compatibility -if(NOT _CMAKE_WATCOM_VERSION) - set(_CMAKE_WATCOM_VERSION 1) - if(CMAKE_C_COMPILER_VERSION) - set(_compiler_version ${CMAKE_C_COMPILER_VERSION}) - set(_compiler_id ${CMAKE_C_COMPILER_ID}) - else() - set(_compiler_version ${CMAKE_CXX_COMPILER_VERSION}) - set(_compiler_id ${CMAKE_CXX_COMPILER_ID}) - endif() - set(WATCOM16) - set(WATCOM17) - set(WATCOM18) - set(WATCOM19) - if("${_compiler_id}" STREQUAL "OpenWatcom") - if("${_compiler_version}" VERSION_LESS 1.7) - set(WATCOM16 1) - endif() - if("${_compiler_version}" VERSION_EQUAL 1.7) - set(WATCOM17 1) - endif() - if("${_compiler_version}" VERSION_EQUAL 1.8) - set(WATCOM18 1) - endif() - if("${_compiler_version}" VERSION_EQUAL 1.9) - set(WATCOM19 1) - endif() - endif() -endif()
diff --git a/share/cmake-3.18/Modules/Compiler/PGI-CXX.cmake b/share/cmake-3.18/Modules/Compiler/PGI-CXX.cmake deleted file mode 100644 index c77de36..0000000 --- a/share/cmake-3.18/Modules/Compiler/PGI-CXX.cmake +++ /dev/null
@@ -1,27 +0,0 @@ -include(Compiler/PGI) -__compiler_pgi(CXX) -string(APPEND CMAKE_CXX_FLAGS_MINSIZEREL_INIT " -DNDEBUG") -string(APPEND CMAKE_CXX_FLAGS_RELEASE_INIT " -DNDEBUG") - -if(CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 12.10) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION -A) - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION --gnu_extensions) - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - if(CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 13.10) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION --c++11 -A) - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION --c++11 --gnu_extensions) - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) - if(CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 15.7) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION --c++14 -A) - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION --c++14 --gnu_extensions) - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) - if(CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 17.1) - set(CMAKE_CXX17_STANDARD_COMPILE_OPTION --c++17 -A) - set(CMAKE_CXX17_EXTENSION_COMPILE_OPTION --c++17 --gnu_extensions) - set(CMAKE_CXX17_STANDARD__HAS_FULL_SUPPORT ON) - endif() - endif() - endif() -endif() - -__compiler_check_default_language_standard(CXX 12.10 98)
diff --git a/share/cmake-3.18/Modules/Compiler/PGI.cmake b/share/cmake-3.18/Modules/Compiler/PGI.cmake deleted file mode 100644 index 4f8b90b..0000000 --- a/share/cmake-3.18/Modules/Compiler/PGI.cmake +++ /dev/null
@@ -1,42 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This module is shared by multiple languages; use include blocker. -if(__COMPILER_PGI) - return() -endif() -set(__COMPILER_PGI 1) - -include(Compiler/CMakeCommonCompilerMacros) - -macro(__compiler_pgi lang) - # Feature flags. - set(CMAKE_${lang}_VERBOSE_FLAG "-v") - - # Initial configuration flags. - string(APPEND CMAKE_${lang}_FLAGS_INIT " ") - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -g -O0") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -O2 -s") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -fast -O3") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -O2 -gopt") - - if(CMAKE_HOST_WIN32) - string(APPEND CMAKE_${lang}_FLAGS_INIT " -Bdynamic") - endif() - - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Wl,") - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG ",") - - set(_CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE YES) - if(NOT CMAKE_SYSTEM_PROCESSOR STREQUAL ppc64le AND (NOT CMAKE_HOST_WIN32 OR CMAKE_${lang}_COMPILER_VERSION VERSION_LESS 16.3)) - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER YES) - set(CMAKE_${lang}_COMPILE_OPTIONS_IPO "-Mipa=fast,inline") - else() - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER NO) - endif() - - # Preprocessing and assembly rules. - set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") - set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>") -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/QCC.cmake b/share/cmake-3.18/Modules/Compiler/QCC.cmake deleted file mode 100644 index 10e1389..0000000 --- a/share/cmake-3.18/Modules/Compiler/QCC.cmake +++ /dev/null
@@ -1,37 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -include(Compiler/GNU) - -macro(__compiler_qcc lang) - __compiler_gnu(${lang}) - - # http://www.qnx.com/developers/docs/6.4.0/neutrino/utilities/q/qcc.html#examples - set(CMAKE_${lang}_COMPILE_OPTIONS_TARGET "-V") - - set(CMAKE_PREFIX_LIBRARY_ARCHITECTURE "ON") - - set(CMAKE_${lang}_COMPILE_OPTIONS_SYSROOT "-Wc,-isysroot,") - set(CMAKE_INCLUDE_SYSTEM_FLAG_${lang} "-Wp,-isystem,") - set(CMAKE_DEPFILE_FLAGS_${lang} "-Wp,-MD,<DEPFILE> -Wp,-MT,<OBJECT> -Wp,-MF,<DEPFILE>") - - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Wl,") - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG_SEP ",") - - set(_CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE NO) - set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER NO) - - set(CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "${CMAKE_${lang}_COMPILER}") - if(CMAKE_${lang}_COMPILER_ARG1) - separate_arguments(_COMPILER_ARGS NATIVE_COMMAND "${CMAKE_${lang}_COMPILER_ARG1}") - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND ${_COMPILER_ARGS}) - unset(_COMPILER_ARGS) - endif() - list(APPEND CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "-Wp,-dM" "-E" "-c" "${CMAKE_ROOT}/Modules/CMakeCXXCompilerABI.cpp") - - unset(CMAKE_${lang}_COMPILE_OPTIONS_IPO) - unset(CMAKE_${lang}_ARCHIVE_CREATE_IPO) - unset(CMAKE_${lang}_ARCHIVE_APPEND_IPO) - unset(CMAKE_${lang}_ARCHIVE_FINISH_IPO) -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/SunPro-C.cmake b/share/cmake-3.18/Modules/Compiler/SunPro-C.cmake deleted file mode 100644 index 7e962b8..0000000 --- a/share/cmake-3.18/Modules/Compiler/SunPro-C.cmake +++ /dev/null
@@ -1,59 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(Compiler/SunPro) - -set(CMAKE_C_VERBOSE_FLAG "-#") - -set(CMAKE_C_COMPILE_OPTIONS_PIC -KPIC) -set(CMAKE_C_COMPILE_OPTIONS_PIE "") -set(_CMAKE_C_PIE_MAY_BE_SUPPORTED_BY_LINKER NO) -set(CMAKE_C_LINK_OPTIONS_PIE "") -set(CMAKE_C_LINK_OPTIONS_NO_PIE "") -set(CMAKE_SHARED_LIBRARY_C_FLAGS "-KPIC") -set(CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS "-G") -set(CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG "-R") -set(CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG_SEP ":") -set(CMAKE_SHARED_LIBRARY_SONAME_C_FLAG "-h") - -string(APPEND CMAKE_C_FLAGS_INIT " ") -string(APPEND CMAKE_C_FLAGS_DEBUG_INIT " -g") -string(APPEND CMAKE_C_FLAGS_MINSIZEREL_INIT " -xO2 -xspace -DNDEBUG") -string(APPEND CMAKE_C_FLAGS_RELEASE_INIT " -xO3 -DNDEBUG") -string(APPEND CMAKE_C_FLAGS_RELWITHDEBINFO_INIT " -g -xO2 -DNDEBUG") - -set(CMAKE_DEPFILE_FLAGS_C "-xMD -xMF <DEPFILE>") - -# Initialize C link type selection flags. These flags are used when -# building a shared library, shared module, or executable that links -# to other libraries to select whether to use the static or shared -# versions of the libraries. -foreach(type SHARED_LIBRARY SHARED_MODULE EXE) - set(CMAKE_${type}_LINK_STATIC_C_FLAGS "-Bstatic") - set(CMAKE_${type}_LINK_DYNAMIC_C_FLAGS "-Bdynamic") -endforeach() - -set(CMAKE_C_LINKER_WRAPPER_FLAG "-Qoption" "ld" " ") -set(CMAKE_C_LINKER_WRAPPER_FLAG_SEP ",") - -if (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 5.13) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c89") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=c89") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) -elseif (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 5.11) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "") - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-xc99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-xc99") -endif() - -__compiler_check_default_language_standard(C 5.11 90 5.14 11) - -set(CMAKE_C_CREATE_PREPROCESSED_SOURCE "<CMAKE_C_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_C_CREATE_ASSEMBLY_SOURCE "<CMAKE_C_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>")
diff --git a/share/cmake-3.18/Modules/Compiler/SunPro-CXX.cmake b/share/cmake-3.18/Modules/Compiler/SunPro-CXX.cmake deleted file mode 100644 index c946c64..0000000 --- a/share/cmake-3.18/Modules/Compiler/SunPro-CXX.cmake +++ /dev/null
@@ -1,66 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -include(Compiler/SunPro) - -set(CMAKE_CXX_VERBOSE_FLAG "-v") - -set(CMAKE_CXX_COMPILE_OPTIONS_PIC -KPIC) -set(CMAKE_CXX_COMPILE_OPTIONS_PIE "") -set(_CMAKE_CXX_PIE_MAY_BE_SUPPORTED_BY_LINKER NO) -set(CMAKE_CXX_LINK_OPTIONS_PIE "") -set(CMAKE_CXX_LINK_OPTIONS_NO_PIE "") -set(CMAKE_SHARED_LIBRARY_CXX_FLAGS "-KPIC") -set(CMAKE_SHARED_LIBRARY_CREATE_CXX_FLAGS "-G") -set(CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG "-R") -set(CMAKE_SHARED_LIBRARY_RUNTIME_CXX_FLAG_SEP ":") -set(CMAKE_SHARED_LIBRARY_SONAME_CXX_FLAG "-h") - -string(APPEND CMAKE_CXX_FLAGS_INIT " ") -string(APPEND CMAKE_CXX_FLAGS_DEBUG_INIT " -g") -string(APPEND CMAKE_CXX_FLAGS_MINSIZEREL_INIT " -xO2 -xspace -DNDEBUG") -string(APPEND CMAKE_CXX_FLAGS_RELEASE_INIT " -xO3 -DNDEBUG") -string(APPEND CMAKE_CXX_FLAGS_RELWITHDEBINFO_INIT " -g -xO2 -DNDEBUG") - -set(CMAKE_DEPFILE_FLAGS_CXX "-xMD -xMF <DEPFILE>") - -# Initialize C link type selection flags. These flags are used when -# building a shared library, shared module, or executable that links -# to other libraries to select whether to use the static or shared -# versions of the libraries. -foreach(type SHARED_LIBRARY SHARED_MODULE EXE) - set(CMAKE_${type}_LINK_STATIC_CXX_FLAGS "-Bstatic") - set(CMAKE_${type}_LINK_DYNAMIC_CXX_FLAGS "-Bdynamic") -endforeach() - -set(CMAKE_CXX_LINKER_WRAPPER_FLAG "-Qoption" "ld" " ") -set(CMAKE_CXX_LINKER_WRAPPER_FLAG_SEP ",") - -set(CMAKE_CXX_CREATE_PREPROCESSED_SOURCE "<CMAKE_CXX_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") -set(CMAKE_CXX_CREATE_ASSEMBLY_SOURCE "<CMAKE_CXX_COMPILER> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>") - -# Create archives with "CC -xar" in case user adds "-instances=extern" -# so that template instantiations are available to archive members. -set(CMAKE_CXX_CREATE_STATIC_LIBRARY - "<CMAKE_CXX_COMPILER> -xar -o <TARGET> <OBJECTS> " - "<CMAKE_RANLIB> <TARGET> ") - -if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.13) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "-std=c++03") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "-std=c++03") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX_LINK_WITH_STANDARD_COMPILE_OPTION 1) - - if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.14) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=c++14") - endif() -else() - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "-library=stlport4") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "-library=stlport4") - set(CMAKE_CXX_LINK_WITH_STANDARD_COMPILE_OPTION 1) -endif() - -__compiler_check_default_language_standard(CXX 1 98)
diff --git a/share/cmake-3.18/Modules/Compiler/TI-ASM.cmake b/share/cmake-3.18/Modules/Compiler/TI-ASM.cmake deleted file mode 100644 index a566d70..0000000 --- a/share/cmake-3.18/Modules/Compiler/TI-ASM.cmake +++ /dev/null
@@ -1,8 +0,0 @@ -set(CMAKE_LIBRARY_PATH_FLAG "--search_path=") -set(CMAKE_LINK_LIBRARY_FLAG "--library=") -set(CMAKE_INCLUDE_FLAG_ASM "--include_path=") - -set(CMAKE_ASM_COMPILE_OBJECT "<CMAKE_ASM_COMPILER> --compile_only --asm_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<OBJECT>") -set(CMAKE_ASM_LINK_EXECUTABLE "<CMAKE_ASM_COMPILER> <OBJECTS> --run_linker --output_file=<TARGET> <CMAKE_ASM_LINK_FLAGS> <LINK_FLAGS> <LINK_LIBRARIES>") - -set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS asm;s;abs)
diff --git a/share/cmake-3.18/Modules/Compiler/TI-C.cmake b/share/cmake-3.18/Modules/Compiler/TI-C.cmake deleted file mode 100644 index b060ee9..0000000 --- a/share/cmake-3.18/Modules/Compiler/TI-C.cmake +++ /dev/null
@@ -1,22 +0,0 @@ -set(CMAKE_LIBRARY_PATH_FLAG "--search_path=") -set(CMAKE_LINK_LIBRARY_FLAG "--library=") -set(CMAKE_INCLUDE_FLAG_C "--include_path=") - -set(CMAKE_C90_STANDARD_COMPILE_OPTION "--c89") -set(CMAKE_C90_EXTENSION_COMPILE_OPTION "--c89 --relaxed_ansi") - -set(CMAKE_C99_STANDARD_COMPILE_OPTION "--c99") -set(CMAKE_C99_EXTENSION_COMPILE_OPTION "--c99 --relaxed_ansi") - -set(CMAKE_DEPFILE_FLAGS_C "--preproc_with_compile --preproc_dependency=<DEPFILE>") - -set(CMAKE_C_CREATE_ASSEMBLY_SOURCE "<CMAKE_C_COMPILER> --compile_only --skip_assembler --c_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<ASSEMBLY_SOURCE>") -set(CMAKE_C_CREATE_PREPROCESSED_SOURCE "<CMAKE_C_COMPILER> --preproc_only --c_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<PREPROCESSED_SOURCE>") - -set(CMAKE_C_COMPILE_OBJECT "<CMAKE_C_COMPILER> --compile_only --c_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<OBJECT>") -set(CMAKE_C_ARCHIVE_CREATE "<CMAKE_AR> qr <TARGET> <OBJECTS>") -set(CMAKE_C_ARCHIVE_APPEND "<CMAKE_AR> qa <TARGET> <OBJECTS>") -set(CMAKE_C_LINK_EXECUTABLE "<CMAKE_C_COMPILER> --run_linker --output_file=<TARGET> --map_file=<TARGET_NAME>.map <CMAKE_C_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> <LINK_LIBRARIES>") -set(CMAKE_ASM_RESPONSE_FILE_FLAG "--cmd_file=") -set(CMAKE_C_RESPONSE_FILE_FLAG "--cmd_file=") -set(CMAKE_C_RESPONSE_FILE_LINK_FLAG " ")
diff --git a/share/cmake-3.18/Modules/Compiler/TI-CXX.cmake b/share/cmake-3.18/Modules/Compiler/TI-CXX.cmake deleted file mode 100644 index 7836543..0000000 --- a/share/cmake-3.18/Modules/Compiler/TI-CXX.cmake +++ /dev/null
@@ -1,15 +0,0 @@ -set(CMAKE_LIBRARY_PATH_FLAG "--search_path=") -set(CMAKE_LINK_LIBRARY_FLAG "--library=") -set(CMAKE_INCLUDE_FLAG_CXX "--include_path=") - -set(CMAKE_DEPFILE_FLAGS_CXX "--preproc_with_compile --preproc_dependency=<DEPFILE>") - -set(CMAKE_CXX_CREATE_ASSEMBLY_SOURCE "<CMAKE_CXX_COMPILER> --compile_only --skip_assembler --cpp_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<ASSEMBLY_SOURCE>") -set(CMAKE_CXX_CREATE_PREPROCESSED_SOURCE "<CMAKE_CXX_COMPILER> --preproc_only --cpp_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<PREPROCESSED_SOURCE>") - -set(CMAKE_CXX_COMPILE_OBJECT "<CMAKE_CXX_COMPILER> --compile_only --cpp_file=<SOURCE> <DEFINES> <INCLUDES> <FLAGS> --output_file=<OBJECT>") -set(CMAKE_CXX_ARCHIVE_CREATE "<CMAKE_AR> qr <TARGET> <OBJECTS>") -set(CMAKE_CXX_ARCHIVE_APPEND "<CMAKE_AR> qa <TARGET> <OBJECTS>") -set(CMAKE_CXX_LINK_EXECUTABLE "<CMAKE_CXX_COMPILER> --run_linker --output_file=<TARGET> --map_file=<TARGET_NAME>.map <CMAKE_CXX_LINK_FLAGS> <LINK_FLAGS> <OBJECTS> <LINK_LIBRARIES>") -set(CMAKE_CXX_RESPONSE_FILE_FLAG "--cmd_file=") -set(CMAKE_CXX_RESPONSE_FILE_LINK_FLAG " ")
diff --git a/share/cmake-3.18/Modules/Compiler/XL.cmake b/share/cmake-3.18/Modules/Compiler/XL.cmake deleted file mode 100644 index fc71ab4..0000000 --- a/share/cmake-3.18/Modules/Compiler/XL.cmake +++ /dev/null
@@ -1,34 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - - -# This module is shared by multiple languages; use include blocker. -if(__COMPILER_XL) - return() -endif() -set(__COMPILER_XL 1) - -include(Compiler/CMakeCommonCompilerMacros) - -macro(__compiler_xl lang) - # Feature flags. - set(CMAKE_${lang}_VERBOSE_FLAG "-V") - set(CMAKE_${lang}_COMPILE_OPTIONS_PIC "-qpic") - set(CMAKE_${lang}_COMPILE_OPTIONS_PIE "-qpic") - set(CMAKE_${lang}_RESPONSE_FILE_FLAG "-qoptfile=") - set(CMAKE_${lang}_RESPONSE_FILE_LINK_FLAG "-qoptfile=") - - set(CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS "-qmkshrobj") - - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG "-Wl,") - set(CMAKE_${lang}_LINKER_WRAPPER_FLAG_SEP ",") - - string(APPEND CMAKE_${lang}_FLAGS_DEBUG_INIT " -g") - string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -O") - string(APPEND CMAKE_${lang}_FLAGS_MINSIZEREL_INIT " -O") - string(APPEND CMAKE_${lang}_FLAGS_RELWITHDEBINFO_INIT " -g") - set(CMAKE_${lang}_CREATE_PREPROCESSED_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -E <SOURCE> > <PREPROCESSED_SOURCE>") - set(CMAKE_${lang}_CREATE_ASSEMBLY_SOURCE "<CMAKE_${lang}_COMPILER> <DEFINES> <INCLUDES> <FLAGS> -S <SOURCE> -o <ASSEMBLY_SOURCE>") - - set(CMAKE_DEPFILE_FLAGS_${lang} "-MF <DEPFILE> -qmakedep=gcc") -endmacro()
diff --git a/share/cmake-3.18/Modules/Compiler/XLClang-C.cmake b/share/cmake-3.18/Modules/Compiler/XLClang-C.cmake deleted file mode 100644 index 54c18a6..0000000 --- a/share/cmake-3.18/Modules/Compiler/XLClang-C.cmake +++ /dev/null
@@ -1,20 +0,0 @@ -include(Compiler/XLClang) -__compiler_xlclang(C) - -if (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 13.1.1) - set(CMAKE_C90_STANDARD_COMPILE_OPTION "-std=c89") - set(CMAKE_C90_EXTENSION_COMPILE_OPTION "-std=gnu89") - set(CMAKE_C90_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C99_STANDARD_COMPILE_OPTION "-std=c99") - set(CMAKE_C99_EXTENSION_COMPILE_OPTION "-std=gnu99") - set(CMAKE_C99_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-qlanglvl=extc1x") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-qlanglvl=extc1x") - if (CMAKE_C_COMPILER_VERSION VERSION_GREATER_EQUAL 13.1.2) - set(CMAKE_C11_STANDARD_COMPILE_OPTION "-std=c11") - set(CMAKE_C11_EXTENSION_COMPILE_OPTION "-std=gnu11") - set(CMAKE_C11_STANDARD__HAS_FULL_SUPPORT ON) - endif () -endif() - -__compiler_check_default_language_standard(C 13.1.1 99)
diff --git a/share/cmake-3.18/Modules/Compiler/XLClang-CXX.cmake b/share/cmake-3.18/Modules/Compiler/XLClang-CXX.cmake deleted file mode 100644 index 9ea3d7c..0000000 --- a/share/cmake-3.18/Modules/Compiler/XLClang-CXX.cmake +++ /dev/null
@@ -1,27 +0,0 @@ -include(Compiler/XLClang) -__compiler_xlclang(CXX) - -if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 13.1.1) - set(CMAKE_CXX98_STANDARD_COMPILE_OPTION "") - set(CMAKE_CXX98_EXTENSION_COMPILE_OPTION "") - set(CMAKE_CXX98_STANDARD__HAS_FULL_SUPPORT ON) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-qlanglvl=extended0x") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-qlanglvl=extended0x") - set(CMAKE_CXX11_STANDARD__HAS_FULL_SUPPORT ON) - if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 13.1.2) - set(CMAKE_CXX11_STANDARD_COMPILE_OPTION "-std=c++11") - set(CMAKE_CXX11_EXTENSION_COMPILE_OPTION "-std=gnu++11") - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++1y") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++1y") - set(CMAKE_CXX14_STANDARD__HAS_FULL_SUPPORT ON) - endif () - if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 16.1.0) - set(CMAKE_CXX14_STANDARD_COMPILE_OPTION "-std=c++14") - set(CMAKE_CXX14_EXTENSION_COMPILE_OPTION "-std=gnu++14") - endif() -endif() - -__compiler_check_default_language_standard(CXX 13.1.1 98) - -set(CMAKE_CXX_COMPILE_OBJECT - "<CMAKE_CXX_COMPILER> -x c++ <DEFINES> <INCLUDES> <FLAGS> -o <OBJECT> -c <SOURCE>")
diff --git a/share/cmake-3.18/Modules/CompilerId/VS-10.csproj.in b/share/cmake-3.18/Modules/CompilerId/VS-10.csproj.in deleted file mode 100644 index ed5e847..0000000 --- a/share/cmake-3.18/Modules/CompilerId/VS-10.csproj.in +++ /dev/null
@@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> - <PropertyGroup Label="Globals"> - <ProjectGuid>{CAE07175-D007-4FC3-BFE8-47B392814159}</ProjectGuid> - <RootNamespace>CompilerId@id_lang@</RootNamespace> - <Keyword>Win32Proj</Keyword> - @id_system@ - @id_system_version@ - @id_WindowsTargetPlatformVersion@ - @id_WindowsSDKDesktopARMSupport@ - </PropertyGroup> - <PropertyGroup> - @id_PreferredToolArchitecture@ - </PropertyGroup> - <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'" Label="Configuration"> - <ConfigurationType>Application</ConfigurationType> - @id_toolset@ - <CharacterSet>MultiByte</CharacterSet> - </PropertyGroup> - <!-- ============================================================ --> - <!-- == set preprocessor definitions == --> - <!-- ============================================================ --> - <PropertyGroup> - <DefineConstants></DefineConstants> - <UnknownValue>Unknown</UnknownValue> - </PropertyGroup> - <!-- Platform --> - <PropertyGroup Condition="'$(Platform)'!=''"> - <DefineConstants>$(DefineConstants);Platform$(Platform)</DefineConstants> - </PropertyGroup> - <PropertyGroup Condition="'$(Platform)'==''"> - <DefineConstants>$(DefineConstants);Platform$(UnknownValue)</DefineConstants> - </PropertyGroup> - <!-- PlatformToolset --> - <PropertyGroup Condition="'$(PlatformToolset)'!=''"> - <DefineConstants>$(DefineConstants);PlatformToolset$(PlatformToolset)</DefineConstants> - </PropertyGroup> - <PropertyGroup Condition="'$(PlatformToolset)'==''"> - <DefineConstants>$(DefineConstants);PlatformToolset$(UnknownValue)</DefineConstants> - </PropertyGroup> - <!-- ============================================================ --> - <PropertyGroup> - <OutputPath Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'">.\</OutputPath> - </PropertyGroup> - <ItemGroup> - <Compile Include="@id_src@" /> - </ItemGroup> - <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /> - <PropertyGroup> - <PostBuildEvent>if not "$(RoslynTargetsPath)"=="" if exist "$(RoslynTargetsPath)\@id_cl@" set _CSC=$(RoslynTargetsPath) -if exist "$(MSBuildToolsPath)\@id_cl@" set _CSC=$(MSBuildToolsPath) -if "%_CSC%"=="" exit -1 -%40echo CMAKE_@id_lang@_COMPILER=%_CSC%\@id_cl@</PostBuildEvent> - </PropertyGroup> -</Project>
diff --git a/share/cmake-3.18/Modules/CompilerId/VS-10.vcxproj.in b/share/cmake-3.18/Modules/CompilerId/VS-10.vcxproj.in deleted file mode 100644 index b48a332..0000000 --- a/share/cmake-3.18/Modules/CompilerId/VS-10.vcxproj.in +++ /dev/null
@@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> - <ItemGroup Label="ProjectConfigurations"> - <ProjectConfiguration Include="Debug|@id_platform@"> - <Configuration>Debug</Configuration> - <Platform>@id_platform@</Platform> - </ProjectConfiguration> - </ItemGroup> - <PropertyGroup Label="Globals"> - <ProjectGuid>{CAE07175-D007-4FC3-BFE8-47B392814159}</ProjectGuid> - <RootNamespace>CompilerId@id_lang@</RootNamespace> - <Keyword>Win32Proj</Keyword> - @id_system@ - @id_system_version@ - @id_WindowsTargetPlatformVersion@ - @id_WindowsSDKDesktopARMSupport@ - @id_CudaToolkitCustomDir@ - @id_ToolsetVCTargetsDir@ - @id_CustomGlobals@ - </PropertyGroup> - @id_toolset_version_props@ - <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" /> - <PropertyGroup> - @id_PreferredToolArchitecture@ - </PropertyGroup> - <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'" Label="Configuration"> - <ConfigurationType>Application</ConfigurationType> - @id_toolset@ - <CharacterSet>MultiByte</CharacterSet> - </PropertyGroup> - <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" /> - <ImportGroup Label="ExtensionSettings"> - @id_Import_props@ - </ImportGroup> - <PropertyGroup> - <_ProjectFileVersion>10.0.30319.1</_ProjectFileVersion> - <OutDir Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'">.\</OutDir> - <IntDir Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'">$(Configuration)\</IntDir> - <LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'">false</LinkIncremental> - </PropertyGroup> - <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|@id_platform@'"> - <ClCompile> - <Optimization>Disabled</Optimization> - <PreprocessorDefinitions>%(PreprocessorDefinitions)</PreprocessorDefinitions> - <MinimalRebuild>false</MinimalRebuild> - <BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks> - <RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary> - <PrecompiledHeader> - </PrecompiledHeader> - <WarningLevel>TurnOffAllWarnings</WarningLevel> - <DebugInformationFormat> - </DebugInformationFormat> - </ClCompile> - @id_ItemDefinitionGroup_entry@ - <Link> - <GenerateDebugInformation>false</GenerateDebugInformation> - <SubSystem>Console</SubSystem> - @id_Link_AdditionalDependencies@ - </Link> - <PostBuildEvent> - <Command>@id_PostBuildEvent_Command@</Command> - </PostBuildEvent> - </ItemDefinitionGroup> - <ItemGroup> - <@id_compile@ Include="@id_src@" /> - </ItemGroup> - <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" /> - <ImportGroup Label="ExtensionTargets"> - @id_Import_targets@ - </ImportGroup> -</Project>
diff --git a/share/cmake-3.18/Modules/CompilerId/Xcode-3.pbxproj.in b/share/cmake-3.18/Modules/CompilerId/Xcode-3.pbxproj.in deleted file mode 100644 index 6fe17e5..0000000 --- a/share/cmake-3.18/Modules/CompilerId/Xcode-3.pbxproj.in +++ /dev/null
@@ -1,114 +0,0 @@ -// !$*UTF8*$! -{ - archiveVersion = 1; - classes = { - }; - objectVersion = 45; - objects = { - - 2C18F0B615DC1E0300593670 = {isa = PBXBuildFile; fileRef = 2C18F0B415DC1DC700593670; }; - 2C18F0B415DC1DC700593670 = {isa = PBXFileReference; fileEncoding = 4; explicitFileType = @id_type@; path = @id_src@; sourceTree = "<group>"; }; - 08FB7794FE84155DC02AAC07 = { - isa = PBXGroup; - children = ( - 2C18F0B415DC1DC700593670, - ); - name = CompilerId@id_lang@; - sourceTree = "<group>"; - }; - 8DD76FA90486AB0100D96B5E = { - isa = PBXNativeTarget; - buildConfigurationList = 1DEB928508733DD80010E9CD; - buildPhases = ( - 2C18F0B515DC1DCE00593670, - 2C8FEB8E15DC1A1A00E56A5D, - ); - buildRules = ( - ); - dependencies = ( - ); - name = CompilerId@id_lang@; - productName = CompilerId@id_lang@; - productType = "@id_product_type@"; - }; - 08FB7793FE84155DC02AAC07 = { - isa = PBXProject; - buildConfigurationList = 1DEB928908733DD80010E9CD; - compatibilityVersion = "Xcode 3.1"; - developmentRegion = English; - hasScannedForEncodings = 1; - knownRegions = ( - en, - ); - mainGroup = 08FB7794FE84155DC02AAC07; - projectDirPath = ""; - projectRoot = ""; - targets = ( - 8DD76FA90486AB0100D96B5E, - ); - }; - 2C8FEB8E15DC1A1A00E56A5D = { - isa = PBXShellScriptBuildPhase; - buildActionMask = 2147483647; - files = ( - ); - inputPaths = ( - ); - outputPaths = ( - ); - runOnlyForDeploymentPostprocessing = 0; - shellPath = /bin/sh; - shellScript = "echo \"GCC_VERSION=$GCC_VERSION\" ; echo \"ARCHS=$ARCHS\""; - showEnvVarsInLog = 0; - }; - 2C18F0B515DC1DCE00593670 = { - isa = PBXSourcesBuildPhase; - buildActionMask = 2147483647; - files = ( - 2C18F0B615DC1E0300593670, - ); - runOnlyForDeploymentPostprocessing = 0; - }; - 1DEB928608733DD80010E9CD = { - isa = XCBuildConfiguration; - buildSettings = { - CODE_SIGN_IDENTITY = ""; - PRODUCT_NAME = CompilerId@id_lang@; - }; - name = Debug; - }; - 1DEB928A08733DD80010E9CD = { - isa = XCBuildConfiguration; - buildSettings = { - ONLY_ACTIVE_ARCH = YES; - CODE_SIGNING_REQUIRED = NO; - CONFIGURATION_BUILD_DIR = "$(BUILD_DIR)"; - SYMROOT = .; - @id_archs@ - @id_toolset@ - @id_lang_version@ - @id_clang_cxx_library@ - @id_deployment_target@ - @id_sdkroot@ - }; - name = Debug; - }; - 1DEB928508733DD80010E9CD = { - isa = XCConfigurationList; - buildConfigurations = ( - 1DEB928608733DD80010E9CD, - ); - defaultConfigurationIsVisible = 0; - defaultConfigurationName = Debug; - }; - 1DEB928908733DD80010E9CD = { - isa = XCConfigurationList; - buildConfigurations = ( - 1DEB928A08733DD80010E9CD, - ); - defaultConfigurationIsVisible = 0; - defaultConfigurationName = Debug; - }; - }; - rootObject = 08FB7793FE84155DC02AAC07; -}
diff --git a/share/cmake-3.18/Modules/DartConfiguration.tcl.in b/share/cmake-3.18/Modules/DartConfiguration.tcl.in deleted file mode 100644 index 086ba07..0000000 --- a/share/cmake-3.18/Modules/DartConfiguration.tcl.in +++ /dev/null
@@ -1,107 +0,0 @@ -# This file is configured by CMake automatically as DartConfiguration.tcl -# If you choose not to use CMake, this file may be hand configured, by -# filling in the required variables. - - -# Configuration directories and files -SourceDirectory: @PROJECT_SOURCE_DIR@ -BuildDirectory: @PROJECT_BINARY_DIR@ - -# Where to place the cost data store -CostDataFile: @CTEST_COST_DATA_FILE@ - -# Site is something like machine.domain, i.e. pragmatic.crd -Site: @SITE@ - -# Build name is osname-revision-compiler, i.e. Linux-2.4.2-2smp-c++ -BuildName: @BUILDNAME@ - -# Subprojects -LabelsForSubprojects: @CTEST_LABELS_FOR_SUBPROJECTS@ - -# Submission information -SubmitURL: @SUBMIT_URL@ - -# Dashboard start time -NightlyStartTime: @NIGHTLY_START_TIME@ - -# Commands for the build/test/submit cycle -ConfigureCommand: "@CMAKE_COMMAND@" "@PROJECT_SOURCE_DIR@" -MakeCommand: @MAKECOMMAND@ -DefaultCTestConfigurationType: @DEFAULT_CTEST_CONFIGURATION_TYPE@ - -# version control -UpdateVersionOnly: @CTEST_UPDATE_VERSION_ONLY@ - -# CVS options -# Default is "-d -P -A" -CVSCommand: @CVSCOMMAND@ -CVSUpdateOptions: @CVS_UPDATE_OPTIONS@ - -# Subversion options -SVNCommand: @SVNCOMMAND@ -SVNOptions: @CTEST_SVN_OPTIONS@ -SVNUpdateOptions: @SVN_UPDATE_OPTIONS@ - -# Git options -GITCommand: @GITCOMMAND@ -GITInitSubmodules: @CTEST_GIT_INIT_SUBMODULES@ -GITUpdateOptions: @GIT_UPDATE_OPTIONS@ -GITUpdateCustom: @CTEST_GIT_UPDATE_CUSTOM@ - -# Perforce options -P4Command: @P4COMMAND@ -P4Client: @CTEST_P4_CLIENT@ -P4Options: @CTEST_P4_OPTIONS@ -P4UpdateOptions: @CTEST_P4_UPDATE_OPTIONS@ -P4UpdateCustom: @CTEST_P4_UPDATE_CUSTOM@ - -# Generic update command -UpdateCommand: @UPDATE_COMMAND@ -UpdateOptions: @UPDATE_OPTIONS@ -UpdateType: @UPDATE_TYPE@ - -# Compiler info -Compiler: @CMAKE_CXX_COMPILER@ -CompilerVersion: @CMAKE_CXX_COMPILER_VERSION@ - -# Dynamic analysis (MemCheck) -PurifyCommand: @PURIFYCOMMAND@ -ValgrindCommand: @VALGRIND_COMMAND@ -ValgrindCommandOptions: @VALGRIND_COMMAND_OPTIONS@ -DrMemoryCommand: @DRMEMORY_COMMAND@ -DrMemoryCommandOptions: @DRMEMORY_COMMAND_OPTIONS@ -MemoryCheckType: @MEMORYCHECK_TYPE@ -MemoryCheckSanitizerOptions: @MEMORYCHECK_SANITIZER_OPTIONS@ -MemoryCheckCommand: @MEMORYCHECK_COMMAND@ -MemoryCheckCommandOptions: @MEMORYCHECK_COMMAND_OPTIONS@ -MemoryCheckSuppressionFile: @MEMORYCHECK_SUPPRESSIONS_FILE@ - -# Coverage -CoverageCommand: @COVERAGE_COMMAND@ -CoverageExtraFlags: @COVERAGE_EXTRA_FLAGS@ - -# Cluster commands -SlurmBatchCommand: @SLURM_SBATCH_COMMAND@ -SlurmRunCommand: @SLURM_SRUN_COMMAND@ - -# Testing options -# TimeOut is the amount of time in seconds to wait for processes -# to complete during testing. After TimeOut seconds, the -# process will be summarily terminated. -# Currently set to 25 minutes -TimeOut: @DART_TESTING_TIMEOUT@ - -# During parallel testing CTest will not start a new test if doing -# so would cause the system load to exceed this value. -TestLoad: @CTEST_TEST_LOAD@ - -UseLaunchers: @CTEST_USE_LAUNCHERS@ -CurlOptions: @CTEST_CURL_OPTIONS@ -# warning, if you add new options here that have to do with submit, -# you have to update cmCTestSubmitCommand.cxx - -# For CTest submissions that timeout, these options -# specify behavior for retrying the submission -CTestSubmitRetryDelay: @CTEST_SUBMIT_RETRY_DELAY@ -CTestSubmitRetryCount: @CTEST_SUBMIT_RETRY_COUNT@
diff --git a/share/cmake-3.18/Modules/Documentation.cmake b/share/cmake-3.18/Modules/Documentation.cmake deleted file mode 100644 index c297231..0000000 --- a/share/cmake-3.18/Modules/Documentation.cmake +++ /dev/null
@@ -1,74 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -Documentation -------------- - -This module provides support for the VTK documentation framework. It -relies on several tools (Doxygen, Perl, etc). -#]=======================================================================] - -cmake_policy(GET CMP0106 _Documentation_policy) - -if (_Documentation_policy STREQUAL "NEW") - message(FATAL_ERROR - "Documentation.cmake is VTK-specific code and should not be used in " - "non-VTK projects. This logic in this module is best shipped with the " - "project using it rather than with CMake. This is now an error according " - "to policy CMP0106.") -else () - -if (_Documentation_policy STREQUAL "") - # Ignore the warning if the project is detected as VTK itself. - if (NOT CMAKE_PROJECT_NAME STREQUAL "VTK" AND - NOT PROJECT_NAME STREQUAL "VTK") - cmake_policy(GET_WARNING CMP0106 _Documentation_policy_warning) - message(AUTHOR_WARNING - "${_Documentation_policy_warning}\n" - "Documentation.cmake is VTK-specific code and should not be used in " - "non-VTK projects. This logic in this module is best shipped with the " - "project using it rather than with CMake.") - endif () - unset(_Documentation_policy_warning) -endif () - -# -# Build the documentation ? -# -option(BUILD_DOCUMENTATION "Build the documentation (Doxygen)." OFF) -mark_as_advanced(BUILD_DOCUMENTATION) - -if (BUILD_DOCUMENTATION) - - # - # Check for the tools - # - find_package(UnixCommands) - find_package(Doxygen) - find_package(Gnuplot) - find_package(HTMLHelp) - find_package(Perl) - find_package(Wget) - - option(DOCUMENTATION_HTML_HELP - "Build the HTML Help file (CHM)." OFF) - - option(DOCUMENTATION_HTML_TARZ - "Build a compressed tar archive of the HTML doc." OFF) - - mark_as_advanced( - DOCUMENTATION_HTML_HELP - DOCUMENTATION_HTML_TARZ - ) - - # - # The documentation process is controlled by a batch file. - # We will probably need bash to create the custom target - # - -endif () - -endif () - -unset(_Documentation_policy)
diff --git a/share/cmake-3.18/Modules/ExternalData.cmake b/share/cmake-3.18/Modules/ExternalData.cmake deleted file mode 100644 index e5dbcd9..0000000 --- a/share/cmake-3.18/Modules/ExternalData.cmake +++ /dev/null
@@ -1,1152 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -ExternalData ------------- - -.. only:: html - - .. contents:: - -Manage data files stored outside source tree - -Introduction -^^^^^^^^^^^^ - -Use this module to unambiguously reference data files stored outside -the source tree and fetch them at build time from arbitrary local and -remote content-addressed locations. Functions provided by this module -recognize arguments with the syntax ``DATA{<name>}`` as references to -external data, replace them with full paths to local copies of those -data, and create build rules to fetch and update the local copies. - -For example: - -.. code-block:: cmake - - include(ExternalData) - set(ExternalData_URL_TEMPLATES "file:///local/%(algo)/%(hash)" - "file:////host/share/%(algo)/%(hash)" - "http://data.org/%(algo)/%(hash)") - ExternalData_Add_Test(MyData - NAME MyTest - COMMAND MyExe DATA{MyInput.png} - ) - ExternalData_Add_Target(MyData) - -When test ``MyTest`` runs the ``DATA{MyInput.png}`` argument will be -replaced by the full path to a real instance of the data file -``MyInput.png`` on disk. If the source tree contains a content link -such as ``MyInput.png.md5`` then the ``MyData`` target creates a real -``MyInput.png`` in the build tree. - -Module Functions -^^^^^^^^^^^^^^^^ - -.. command:: ExternalData_Expand_Arguments - - The ``ExternalData_Expand_Arguments`` function evaluates ``DATA{}`` - references in its arguments and constructs a new list of arguments:: - - ExternalData_Expand_Arguments( - <target> # Name of data management target - <outVar> # Output variable - [args...] # Input arguments, DATA{} allowed - ) - - It replaces each ``DATA{}`` reference in an argument with the full path of - a real data file on disk that will exist after the ``<target>`` builds. - -.. command:: ExternalData_Add_Test - - The ``ExternalData_Add_Test`` function wraps around the CMake - :command:`add_test` command but supports ``DATA{}`` references in - its arguments:: - - ExternalData_Add_Test( - <target> # Name of data management target - ... # Arguments of add_test(), DATA{} allowed - ) - - It passes its arguments through ``ExternalData_Expand_Arguments`` and then - invokes the :command:`add_test` command using the results. - -.. command:: ExternalData_Add_Target - - The ``ExternalData_Add_Target`` function creates a custom target to - manage local instances of data files stored externally:: - - ExternalData_Add_Target( - <target> # Name of data management target - ) - - It creates custom commands in the target as necessary to make data - files available for each ``DATA{}`` reference previously evaluated by - other functions provided by this module. - Data files may be fetched from one of the URL templates specified in - the ``ExternalData_URL_TEMPLATES`` variable, or may be found locally - in one of the paths specified in the ``ExternalData_OBJECT_STORES`` - variable. - - Typically only one target is needed to manage all external data within - a project. Call this function once at the end of configuration after - all data references have been processed. - -Module Variables -^^^^^^^^^^^^^^^^ - -The following variables configure behavior. They should be set before -calling any of the functions provided by this module. - -.. variable:: ExternalData_BINARY_ROOT - - The ``ExternalData_BINARY_ROOT`` variable may be set to the directory to - hold the real data files named by expanded ``DATA{}`` references. The - default is ``CMAKE_BINARY_DIR``. The directory layout will mirror that of - content links under ``ExternalData_SOURCE_ROOT``. - -.. variable:: ExternalData_CUSTOM_SCRIPT_<key> - - Specify a full path to a ``.cmake`` custom fetch script identified by - ``<key>`` in entries of the ``ExternalData_URL_TEMPLATES`` list. - See `Custom Fetch Scripts`_. - -.. variable:: ExternalData_LINK_CONTENT - - The ``ExternalData_LINK_CONTENT`` variable may be set to the name of a - supported hash algorithm to enable automatic conversion of real data - files referenced by the ``DATA{}`` syntax into content links. For each - such ``<file>`` a content link named ``<file><ext>`` is created. The - original file is renamed to the form ``.ExternalData_<algo>_<hash>`` to - stage it for future transmission to one of the locations in the list - of URL templates (by means outside the scope of this module). The - data fetch rule created for the content link will use the staged - object if it cannot be found using any URL template. - -.. variable:: ExternalData_NO_SYMLINKS - - The real data files named by expanded ``DATA{}`` references may be made - available under ``ExternalData_BINARY_ROOT`` using symbolic links on - some platforms. The ``ExternalData_NO_SYMLINKS`` variable may be set - to disable use of symbolic links and enable use of copies instead. - -.. variable:: ExternalData_OBJECT_STORES - - The ``ExternalData_OBJECT_STORES`` variable may be set to a list of local - directories that store objects using the layout ``<dir>/%(algo)/%(hash)``. - These directories will be searched first for a needed object. If the - object is not available in any store then it will be fetched remotely - using the URL templates and added to the first local store listed. If - no stores are specified the default is a location inside the build - tree. - -.. variable:: ExternalData_SERIES_PARSE - ExternalData_SERIES_PARSE_PREFIX - ExternalData_SERIES_PARSE_NUMBER - ExternalData_SERIES_PARSE_SUFFIX - ExternalData_SERIES_MATCH - - See `Referencing File Series`_. - -.. variable:: ExternalData_SOURCE_ROOT - - The ``ExternalData_SOURCE_ROOT`` variable may be set to the highest source - directory containing any path named by a ``DATA{}`` reference. The - default is ``CMAKE_SOURCE_DIR``. ``ExternalData_SOURCE_ROOT`` and - ``CMAKE_SOURCE_DIR`` must refer to directories within a single source - distribution (e.g. they come together in one tarball). - -.. variable:: ExternalData_TIMEOUT_ABSOLUTE - - The ``ExternalData_TIMEOUT_ABSOLUTE`` variable sets the download - absolute timeout, in seconds, with a default of ``300`` seconds. - Set to ``0`` to disable enforcement. - -.. variable:: ExternalData_TIMEOUT_INACTIVITY - - The ``ExternalData_TIMEOUT_INACTIVITY`` variable sets the download - inactivity timeout, in seconds, with a default of ``60`` seconds. - Set to ``0`` to disable enforcement. - -.. variable:: ExternalData_URL_ALGO_<algo>_<key> - - Specify a custom URL component to be substituted for URL template - placeholders of the form ``%(algo:<key>)``, where ``<key>`` is a - valid C identifier, when fetching an object referenced via hash - algorithm ``<algo>``. If not defined, the default URL component - is just ``<algo>`` for any ``<key>``. - -.. variable:: ExternalData_URL_TEMPLATES - - The ``ExternalData_URL_TEMPLATES`` may be set to provide a list of - of URL templates using the placeholders ``%(algo)`` and ``%(hash)`` - in each template. Data fetch rules try each URL template in order - by substituting the hash algorithm name for ``%(algo)`` and the hash - value for ``%(hash)``. Alternatively one may use ``%(algo:<key>)`` - with ``ExternalData_URL_ALGO_<algo>_<key>`` variables to gain more - flexibility in remote URLs. - -Referencing Files -^^^^^^^^^^^^^^^^^ - -Referencing Single Files -"""""""""""""""""""""""" - -The ``DATA{}`` syntax is literal and the ``<name>`` is a full or relative path -within the source tree. The source tree must contain either a real -data file at ``<name>`` or a "content link" at ``<name><ext>`` containing a -hash of the real file using a hash algorithm corresponding to ``<ext>``. -For example, the argument ``DATA{img.png}`` may be satisfied by either a -real ``img.png`` file in the current source directory or a ``img.png.md5`` -file containing its MD5 sum. - -Multiple content links of the same name with different hash algorithms -are supported (e.g. ``img.png.sha256`` and ``img.png.sha1``) so long as -they all correspond to the same real file. This allows objects to be -fetched from sources indexed by different hash algorithms. - -Referencing File Series -""""""""""""""""""""""" - -The ``DATA{}`` syntax can be told to fetch a file series using the form -``DATA{<name>,:}``, where the ``:`` is literal. If the source tree -contains a group of files or content links named like a series then a -reference to one member adds rules to fetch all of them. Although all -members of a series are fetched, only the file originally named by the -``DATA{}`` argument is substituted for it. The default configuration -recognizes file series names ending with ``#.ext``, ``_#.ext``, ``.#.ext``, -or ``-#.ext`` where ``#`` is a sequence of decimal digits and ``.ext`` is -any single extension. Configure it with a regex that parses ``<number>`` -and ``<suffix>`` parts from the end of ``<name>``:: - - ExternalData_SERIES_PARSE = regex of the form (<number>)(<suffix>)$ - -For more complicated cases set:: - - ExternalData_SERIES_PARSE = regex with at least two () groups - ExternalData_SERIES_PARSE_PREFIX = <prefix> regex group number, if any - ExternalData_SERIES_PARSE_NUMBER = <number> regex group number - ExternalData_SERIES_PARSE_SUFFIX = <suffix> regex group number - -Configure series number matching with a regex that matches the -``<number>`` part of series members named ``<prefix><number><suffix>``:: - - ExternalData_SERIES_MATCH = regex matching <number> in all series members - -Note that the ``<suffix>`` of a series does not include a hash-algorithm -extension. - -Referencing Associated Files -"""""""""""""""""""""""""""" - -The ``DATA{}`` syntax can alternatively match files associated with the -named file and contained in the same directory. Associated files may -be specified by options using the syntax -``DATA{<name>,<opt1>,<opt2>,...}``. Each option may specify one file by -name or specify a regular expression to match file names using the -syntax ``REGEX:<regex>``. For example, the arguments:: - - DATA{MyData/MyInput.mhd,MyInput.img} # File pair - DATA{MyData/MyFrames00.png,REGEX:MyFrames[0-9]+\\.png} # Series - -will pass ``MyInput.mha`` and ``MyFrames00.png`` on the command line but -ensure that the associated files are present next to them. - -Referencing Directories -""""""""""""""""""""""" - -The ``DATA{}`` syntax may reference a directory using a trailing slash and -a list of associated files. The form ``DATA{<name>/,<opt1>,<opt2>,...}`` -adds rules to fetch any files in the directory that match one of the -associated file options. For example, the argument -``DATA{MyDataDir/,REGEX:.*}`` will pass the full path to a ``MyDataDir`` -directory on the command line and ensure that the directory contains -files corresponding to every file or content link in the ``MyDataDir`` -source directory. In order to match associated files in subdirectories, -specify a ``RECURSE:`` option, e.g. ``DATA{MyDataDir/,RECURSE:,REGEX:.*}``. - -Hash Algorithms -^^^^^^^^^^^^^^^ - -The following hash algorithms are supported:: - - %(algo) <ext> Description - ------- ----- ----------- - MD5 .md5 Message-Digest Algorithm 5, RFC 1321 - SHA1 .sha1 US Secure Hash Algorithm 1, RFC 3174 - SHA224 .sha224 US Secure Hash Algorithms, RFC 4634 - SHA256 .sha256 US Secure Hash Algorithms, RFC 4634 - SHA384 .sha384 US Secure Hash Algorithms, RFC 4634 - SHA512 .sha512 US Secure Hash Algorithms, RFC 4634 - SHA3_224 .sha3-224 Keccak SHA-3 - SHA3_256 .sha3-256 Keccak SHA-3 - SHA3_384 .sha3-384 Keccak SHA-3 - SHA3_512 .sha3-512 Keccak SHA-3 - -Note that the hashes are used only for unique data identification and -download verification. - -.. _`ExternalData Custom Fetch Scripts`: - -Custom Fetch Scripts -^^^^^^^^^^^^^^^^^^^^ - -When a data file must be fetched from one of the URL templates -specified in the ``ExternalData_URL_TEMPLATES`` variable, it is -normally downloaded using the :command:`file(DOWNLOAD)` command. -One may specify usage of a custom fetch script by using a URL -template of the form ``ExternalDataCustomScript://<key>/<loc>``. -The ``<key>`` must be a C identifier, and the ``<loc>`` must -contain the ``%(algo)`` and ``%(hash)`` placeholders. -A variable corresponding to the key, ``ExternalData_CUSTOM_SCRIPT_<key>``, -must be set to the full path to a ``.cmake`` script file. The script -will be included to perform the actual fetch, and provided with -the following variables: - -.. variable:: ExternalData_CUSTOM_LOCATION - - When a custom fetch script is loaded, this variable is set to the - location part of the URL, which will contain the substituted hash - algorithm name and content hash value. - -.. variable:: ExternalData_CUSTOM_FILE - - When a custom fetch script is loaded, this variable is set to the - full path to a file in which the script must store the fetched - content. The name of the file is unspecified and should not be - interpreted in any way. - -The custom fetch script is expected to store fetched content in the -file or set a variable: - -.. variable:: ExternalData_CUSTOM_ERROR - - When a custom fetch script fails to fetch the requested content, - it must set this variable to a short one-line message describing - the reason for failure. - -#]=======================================================================] - -function(ExternalData_add_test target) - # Expand all arguments as a single string to preserve escaped semicolons. - ExternalData_expand_arguments("${target}" testArgs "${ARGN}") - add_test(${testArgs}) -endfunction() - -function(ExternalData_add_target target) - if(NOT ExternalData_URL_TEMPLATES AND NOT ExternalData_OBJECT_STORES) - message(FATAL_ERROR - "Neither ExternalData_URL_TEMPLATES nor ExternalData_OBJECT_STORES is set!") - endif() - if(NOT ExternalData_OBJECT_STORES) - set(ExternalData_OBJECT_STORES ${CMAKE_BINARY_DIR}/ExternalData/Objects) - endif() - set(_ExternalData_CONFIG_CODE "") - - # Store custom script configuration. - foreach(url_template IN LISTS ExternalData_URL_TEMPLATES) - if("${url_template}" MATCHES "^ExternalDataCustomScript://([^/]*)/(.*)$") - set(key "${CMAKE_MATCH_1}") - if(key MATCHES "^[A-Za-z_][A-Za-z0-9_]*$") - if(ExternalData_CUSTOM_SCRIPT_${key}) - if(IS_ABSOLUTE "${ExternalData_CUSTOM_SCRIPT_${key}}") - string(CONCAT _ExternalData_CONFIG_CODE "${_ExternalData_CONFIG_CODE}\n" - "set(ExternalData_CUSTOM_SCRIPT_${key} \"${ExternalData_CUSTOM_SCRIPT_${key}}\")") - else() - message(FATAL_ERROR - "No ExternalData_CUSTOM_SCRIPT_${key} is not set to a full path:\n" - " ${ExternalData_CUSTOM_SCRIPT_${key}}") - endif() - else() - message(FATAL_ERROR - "No ExternalData_CUSTOM_SCRIPT_${key} is set for URL template:\n" - " ${url_template}") - endif() - else() - message(FATAL_ERROR - "Bad ExternalDataCustomScript key '${key}' in URL template:\n" - " ${url_template}\n" - "The key must be a valid C identifier.") - endif() - endif() - - # Store custom algorithm name to URL component maps. - if("${url_template}" MATCHES "%\\(algo:([^)]*)\\)") - set(key "${CMAKE_MATCH_1}") - if(key MATCHES "^[A-Za-z_][A-Za-z0-9_]*$") - string(REPLACE "|" ";" _algos "${_ExternalData_REGEX_ALGO}") - foreach(algo ${_algos}) - if(DEFINED ExternalData_URL_ALGO_${algo}_${key}) - string(CONCAT _ExternalData_CONFIG_CODE "${_ExternalData_CONFIG_CODE}\n" - "set(ExternalData_URL_ALGO_${algo}_${key} \"${ExternalData_URL_ALGO_${algo}_${key}}\")") - endif() - endforeach() - else() - message(FATAL_ERROR - "Bad %(algo:${key}) in URL template:\n" - " ${url_template}\n" - "The transform name must be a valid C identifier.") - endif() - endif() - endforeach() - - # Store configuration for use by build-time script. - set(config ${CMAKE_CURRENT_BINARY_DIR}/${target}_config.cmake) - configure_file(${_ExternalData_SELF_DIR}/ExternalData_config.cmake.in ${config} @ONLY) - - set(files "") - - # Set a "_ExternalData_FILE_${file}" variable for each output file to avoid - # duplicate entries within this target. Set a directory property of the same - # name to avoid repeating custom commands with the same output in this directory. - # Repeating custom commands with the same output across directories or across - # targets in the same directory may be a race, but this is likely okay because - # we use atomic replacement of output files. - # - # Use local data first to prefer real files over content links. - - # Custom commands to copy or link local data. - get_property(data_local GLOBAL PROPERTY _ExternalData_${target}_LOCAL) - foreach(entry IN LISTS data_local) - string(REPLACE "|" ";" tuple "${entry}") - list(GET tuple 0 file) - list(GET tuple 1 name) - if(NOT DEFINED "_ExternalData_FILE_${file}") - set("_ExternalData_FILE_${file}" 1) - get_property(added DIRECTORY PROPERTY "_ExternalData_FILE_${file}") - if(NOT added) - set_property(DIRECTORY PROPERTY "_ExternalData_FILE_${file}" 1) - add_custom_command( - COMMENT "Generating ${file}" - OUTPUT "${file}" - COMMAND ${CMAKE_COMMAND} -Drelative_top=${CMAKE_BINARY_DIR} - -Dfile=${file} -Dname=${name} - -DExternalData_ACTION=local - -DExternalData_CONFIG=${config} - -P ${_ExternalData_SELF} - MAIN_DEPENDENCY "${name}" - ) - endif() - list(APPEND files "${file}") - endif() - endforeach() - - # Custom commands to fetch remote data. - get_property(data_fetch GLOBAL PROPERTY _ExternalData_${target}_FETCH) - foreach(entry IN LISTS data_fetch) - string(REPLACE "|" ";" tuple "${entry}") - list(GET tuple 0 file) - list(GET tuple 1 name) - list(GET tuple 2 exts) - string(REPLACE "+" ";" exts_list "${exts}") - list(GET exts_list 0 first_ext) - set(stamp "-hash-stamp") - if(NOT DEFINED "_ExternalData_FILE_${file}") - set("_ExternalData_FILE_${file}" 1) - get_property(added DIRECTORY PROPERTY "_ExternalData_FILE_${file}") - if(NOT added) - set_property(DIRECTORY PROPERTY "_ExternalData_FILE_${file}" 1) - add_custom_command( - # Users care about the data file, so hide the hash/timestamp file. - COMMENT "Generating ${file}" - # The hash/timestamp file is the output from the build perspective. - # List the real file as a second output in case it is a broken link. - # The files must be listed in this order so CMake can hide from the - # make tool that a symlink target may not be newer than the input. - OUTPUT "${file}${stamp}" "${file}" - # Run the data fetch/update script. - COMMAND ${CMAKE_COMMAND} -Drelative_top=${CMAKE_BINARY_DIR} - -Dfile=${file} -Dname=${name} -Dexts=${exts} - -DExternalData_ACTION=fetch - -DExternalData_CONFIG=${config} - -P ${_ExternalData_SELF} - # Update whenever the object hash changes. - MAIN_DEPENDENCY "${name}${first_ext}" - ) - endif() - list(APPEND files "${file}${stamp}") - endif() - endforeach() - - # Custom target to drive all update commands. - add_custom_target(${target} ALL DEPENDS ${files}) -endfunction() - -function(ExternalData_expand_arguments target outArgsVar) - # Replace DATA{} references with real arguments. - set(data_regex "DATA{([^;{}\r\n]*)}") - set(other_regex "([^D]|D[^A]|DA[^T]|DAT[^A]|DATA[^{])+|.") - set(outArgs "") - # This list expansion un-escapes semicolons in list element values so we - # must re-escape them below anywhere a new list expansion will occur. - foreach(arg IN LISTS ARGN) - if("x${arg}" MATCHES "${data_regex}") - # Re-escape in-value semicolons before expansion in foreach below. - string(REPLACE ";" "\\;" tmp "${arg}") - # Split argument into DATA{}-pieces and other pieces. - string(REGEX MATCHALL "${data_regex}|${other_regex}" pieces "${tmp}") - # Compose output argument with DATA{}-pieces replaced. - set(outArg "") - foreach(piece IN LISTS pieces) - if("x${piece}" MATCHES "^x${data_regex}$") - # Replace this DATA{}-piece with a file path. - _ExternalData_arg("${target}" "${piece}" "${CMAKE_MATCH_1}" file) - string(APPEND outArg "${file}") - else() - # No replacement needed for this piece. - string(APPEND outArg "${piece}") - endif() - endforeach() - else() - # No replacements needed in this argument. - set(outArg "${arg}") - endif() - # Re-escape in-value semicolons in resulting list. - string(REPLACE ";" "\\;" outArg "${outArg}") - list(APPEND outArgs "${outArg}") - endforeach() - set("${outArgsVar}" "${outArgs}" PARENT_SCOPE) -endfunction() - -#----------------------------------------------------------------------------- -# Private helper interface - -set(_ExternalData_REGEX_ALGO "MD5|SHA1|SHA224|SHA256|SHA384|SHA512|SHA3_224|SHA3_256|SHA3_384|SHA3_512") -set(_ExternalData_REGEX_EXT "md5|sha1|sha224|sha256|sha384|sha512|sha3-224|sha3-256|sha3-384|sha3-512") -set(_ExternalData_SELF "${CMAKE_CURRENT_LIST_FILE}") -get_filename_component(_ExternalData_SELF_DIR "${_ExternalData_SELF}" PATH) - -function(_ExternalData_compute_hash var_hash algo file) - if("${algo}" MATCHES "^${_ExternalData_REGEX_ALGO}$") - file("${algo}" "${file}" hash) - set("${var_hash}" "${hash}" PARENT_SCOPE) - else() - message(FATAL_ERROR "Hash algorithm ${algo} unimplemented.") - endif() -endfunction() - -function(_ExternalData_random var) - string(RANDOM LENGTH 6 random) - set("${var}" "${random}" PARENT_SCOPE) -endfunction() - -function(_ExternalData_exact_regex regex_var string) - string(REGEX REPLACE "([][+.*()^])" "\\\\\\1" regex "${string}") - set("${regex_var}" "${regex}" PARENT_SCOPE) -endfunction() - -function(_ExternalData_atomic_write file content) - _ExternalData_random(random) - set(tmp "${file}.tmp${random}") - file(WRITE "${tmp}" "${content}") - file(RENAME "${tmp}" "${file}") -endfunction() - -function(_ExternalData_link_content name var_ext) - if("${ExternalData_LINK_CONTENT}" MATCHES "^(${_ExternalData_REGEX_ALGO})$") - set(algo "${ExternalData_LINK_CONTENT}") - else() - message(FATAL_ERROR - "Unknown hash algorithm specified by ExternalData_LINK_CONTENT:\n" - " ${ExternalData_LINK_CONTENT}") - endif() - _ExternalData_compute_hash(hash "${algo}" "${name}") - get_filename_component(dir "${name}" PATH) - set(staged "${dir}/.ExternalData_${algo}_${hash}") - string(TOLOWER ".${algo}" ext) - _ExternalData_atomic_write("${name}${ext}" "${hash}\n") - file(RENAME "${name}" "${staged}") - set("${var_ext}" "${ext}" PARENT_SCOPE) - - file(RELATIVE_PATH relname "${ExternalData_SOURCE_ROOT}" "${name}${ext}") - message(STATUS "Linked ${relname} to ExternalData ${algo}/${hash}") -endfunction() - -function(_ExternalData_arg target arg options var_file) - # Separate data path from the options. - string(REPLACE "," ";" options "${options}") - list(GET options 0 data) - list(REMOVE_AT options 0) - - # Interpret trailing slashes as directories. - set(data_is_directory 0) - if("x${data}" MATCHES "^x(.*)([/\\])$") - set(data_is_directory 1) - set(data "${CMAKE_MATCH_1}") - endif() - - # Convert to full path. - if(IS_ABSOLUTE "${data}") - set(absdata "${data}") - else() - set(absdata "${CMAKE_CURRENT_SOURCE_DIR}/${data}") - endif() - get_filename_component(absdata "${absdata}" ABSOLUTE) - - # Convert to relative path under the source tree. - if(NOT ExternalData_SOURCE_ROOT) - set(ExternalData_SOURCE_ROOT "${CMAKE_SOURCE_DIR}") - endif() - set(top_src "${ExternalData_SOURCE_ROOT}") - file(RELATIVE_PATH reldata "${top_src}" "${absdata}") - if(IS_ABSOLUTE "${reldata}" OR "${reldata}" MATCHES "^\\.\\./") - message(FATAL_ERROR "Data file referenced by argument\n" - " ${arg}\n" - "does not lie under the top-level source directory\n" - " ${top_src}\n") - endif() - if(data_is_directory AND NOT IS_DIRECTORY "${top_src}/${reldata}") - message(FATAL_ERROR "Data directory referenced by argument\n" - " ${arg}\n" - "corresponds to source tree path\n" - " ${reldata}\n" - "that does not exist as a directory!") - endif() - if(NOT ExternalData_BINARY_ROOT) - set(ExternalData_BINARY_ROOT "${CMAKE_BINARY_DIR}") - endif() - set(top_bin "${ExternalData_BINARY_ROOT}") - - # Handle in-source builds gracefully. - if("${top_src}" STREQUAL "${top_bin}") - if(ExternalData_LINK_CONTENT) - message(WARNING "ExternalData_LINK_CONTENT cannot be used in-source") - set(ExternalData_LINK_CONTENT 0) - endif() - set(top_same 1) - endif() - - set(external "") # Entries external to the source tree. - set(internal "") # Entries internal to the source tree. - set(have_original ${data_is_directory}) - set(have_original_as_dir 0) - - # Process options. - set(series_option "") - set(recurse_option "") - set(associated_files "") - set(associated_regex "") - foreach(opt ${options}) - # Regular expression to match associated files. - if("x${opt}" MATCHES "^xREGEX:([^:/]+)$") - list(APPEND associated_regex "${CMAKE_MATCH_1}") - elseif(opt STREQUAL ":") - # Activate series matching. - set(series_option "${opt}") - elseif(opt STREQUAL "RECURSE:") - # Activate recursive matching in directories. - set(recurse_option "${opt}") - elseif("x${opt}" MATCHES "^[^][:/*?]+$") - # Specific associated file. - list(APPEND associated_files "${opt}") - else() - message(FATAL_ERROR "Unknown option \"${opt}\" in argument\n" - " ${arg}\n") - endif() - endforeach() - - if(series_option) - if(data_is_directory) - message(FATAL_ERROR "Series option \"${series_option}\" not allowed with directories.") - endif() - if(associated_files OR associated_regex) - message(FATAL_ERROR "Series option \"${series_option}\" not allowed with associated files.") - endif() - if(recurse_option) - message(FATAL_ERROR "Recurse option \"${recurse_option}\" allowed only with directories.") - endif() - # Load a whole file series. - _ExternalData_arg_series() - elseif(data_is_directory) - if(associated_files OR associated_regex) - # Load listed/matching associated files in the directory. - _ExternalData_arg_associated() - else() - message(FATAL_ERROR "Data directory referenced by argument\n" - " ${arg}\n" - "must list associated files.") - endif() - else() - if(recurse_option) - message(FATAL_ERROR "Recurse option \"${recurse_option}\" allowed only with directories.") - endif() - # Load the named data file. - _ExternalData_arg_single() - if(associated_files OR associated_regex) - # Load listed/matching associated files. - _ExternalData_arg_associated() - endif() - endif() - - if(NOT have_original) - if(have_original_as_dir) - set(msg_kind FATAL_ERROR) - set(msg "that is directory instead of a file!") - else() - set(msg_kind AUTHOR_WARNING) - set(msg "that does not exist as a file (with or without an extension)!") - endif() - message(${msg_kind} "Data file referenced by argument\n" - " ${arg}\n" - "corresponds to source tree path\n" - " ${reldata}\n" - "${msg}") - endif() - - if(external) - # Make the series available in the build tree. - set_property(GLOBAL APPEND PROPERTY - _ExternalData_${target}_FETCH "${external}") - set_property(GLOBAL APPEND PROPERTY - _ExternalData_${target}_LOCAL "${internal}") - set("${var_file}" "${top_bin}/${reldata}" PARENT_SCOPE) - else() - # The whole series is in the source tree. - set("${var_file}" "${top_src}/${reldata}" PARENT_SCOPE) - endif() -endfunction() - -macro(_ExternalData_arg_associated) - # Associated files lie in the same directory. - if(data_is_directory) - set(reldir "${reldata}") - else() - get_filename_component(reldir "${reldata}" PATH) - endif() - if(reldir) - string(APPEND reldir "/") - endif() - _ExternalData_exact_regex(reldir_regex "${reldir}") - if(recurse_option) - set(glob GLOB_RECURSE) - string(APPEND reldir_regex "(.+/)?") - else() - set(glob GLOB) - endif() - - # Find files named explicitly. - foreach(file ${associated_files}) - _ExternalData_exact_regex(file_regex "${file}") - _ExternalData_arg_find_files(${glob} "${reldir}${file}" - "${reldir_regex}${file_regex}") - endforeach() - - # Find files matching the given regular expressions. - set(all "") - set(sep "") - foreach(regex ${associated_regex}) - string(APPEND all "${sep}${reldir_regex}${regex}") - set(sep "|") - endforeach() - _ExternalData_arg_find_files(${glob} "${reldir}" "${all}") -endmacro() - -macro(_ExternalData_arg_single) - # Match only the named data by itself. - _ExternalData_exact_regex(data_regex "${reldata}") - _ExternalData_arg_find_files(GLOB "${reldata}" "${data_regex}") -endmacro() - -macro(_ExternalData_arg_series) - # Configure series parsing and matching. - set(series_parse_prefix "") - set(series_parse_number "\\1") - set(series_parse_suffix "\\2") - if(ExternalData_SERIES_PARSE) - if(ExternalData_SERIES_PARSE_NUMBER AND ExternalData_SERIES_PARSE_SUFFIX) - if(ExternalData_SERIES_PARSE_PREFIX) - set(series_parse_prefix "\\${ExternalData_SERIES_PARSE_PREFIX}") - endif() - set(series_parse_number "\\${ExternalData_SERIES_PARSE_NUMBER}") - set(series_parse_suffix "\\${ExternalData_SERIES_PARSE_SUFFIX}") - elseif(NOT "x${ExternalData_SERIES_PARSE}" MATCHES "^x\\([^()]*\\)\\([^()]*\\)\\$$") - message(FATAL_ERROR - "ExternalData_SERIES_PARSE is set to\n" - " ${ExternalData_SERIES_PARSE}\n" - "which is not of the form\n" - " (<number>)(<suffix>)$\n" - "Fix the regular expression or set variables\n" - " ExternalData_SERIES_PARSE_PREFIX = <prefix> regex group number, if any\n" - " ExternalData_SERIES_PARSE_NUMBER = <number> regex group number\n" - " ExternalData_SERIES_PARSE_SUFFIX = <suffix> regex group number\n" - ) - endif() - set(series_parse "${ExternalData_SERIES_PARSE}") - else() - set(series_parse "([0-9]*)(\\.[^./]*)$") - endif() - if(ExternalData_SERIES_MATCH) - set(series_match "${ExternalData_SERIES_MATCH}") - else() - set(series_match "[_.-]?[0-9]*") - endif() - - # Parse the base, number, and extension components of the series. - string(REGEX REPLACE "${series_parse}" "${series_parse_prefix};${series_parse_number};${series_parse_suffix}" tuple "${reldata}") - list(LENGTH tuple len) - if(NOT "${len}" EQUAL 3) - message(FATAL_ERROR "Data file referenced by argument\n" - " ${arg}\n" - "corresponds to path\n" - " ${reldata}\n" - "that does not match regular expression\n" - " ${series_parse}") - endif() - list(GET tuple 0 relbase) - list(GET tuple 2 ext) - - # Glob files that might match the series. - # Then match base, number, and extension. - _ExternalData_exact_regex(series_base "${relbase}") - _ExternalData_exact_regex(series_ext "${ext}") - _ExternalData_arg_find_files(GLOB "${relbase}*${ext}" - "${series_base}${series_match}${series_ext}") -endmacro() - -function(_ExternalData_arg_find_files glob pattern regex) - cmake_policy(PUSH) - cmake_policy(SET CMP0009 NEW) - file(${glob} globbed RELATIVE "${top_src}" "${top_src}/${pattern}*") - cmake_policy(POP) - set(externals_count -1) - foreach(entry IN LISTS globbed) - if("x${entry}" MATCHES "^x(.*)(\\.(${_ExternalData_REGEX_EXT}))$") - set(relname "${CMAKE_MATCH_1}") - set(alg "${CMAKE_MATCH_2}") - else() - set(relname "${entry}") - set(alg "") - endif() - if("x${relname}" MATCHES "^x${regex}$" # matches - AND NOT "x${relname}" MATCHES "(^x|/)\\.ExternalData_" # not staged obj - ) - if(IS_DIRECTORY "${top_src}/${entry}") - if("${relname}" STREQUAL "${reldata}") - set(have_original_as_dir 1) - endif() - else() - set(name "${top_src}/${relname}") - set(file "${top_bin}/${relname}") - if(alg) - if(NOT "${external_${externals_count}_file_name}" STREQUAL "${file}|${name}") - math(EXPR externals_count "${externals_count} + 1") - set(external_${externals_count}_file_name "${file}|${name}") - endif() - list(APPEND external_${externals_count}_algs "${alg}") - elseif(ExternalData_LINK_CONTENT) - _ExternalData_link_content("${name}" alg) - list(APPEND external "${file}|${name}|${alg}") - elseif(NOT top_same) - list(APPEND internal "${file}|${name}") - endif() - if("${relname}" STREQUAL "${reldata}") - set(have_original 1) - endif() - endif() - endif() - endforeach() - if(${externals_count} GREATER -1) - foreach(ii RANGE ${externals_count}) - string(REPLACE ";" "+" algs_delim "${external_${ii}_algs}") - list(APPEND external "${external_${ii}_file_name}|${algs_delim}") - unset(external_${ii}_algs) - unset(external_${ii}_file_name) - endforeach() - endif() - set(external "${external}" PARENT_SCOPE) - set(internal "${internal}" PARENT_SCOPE) - set(have_original "${have_original}" PARENT_SCOPE) - set(have_original_as_dir "${have_original_as_dir}" PARENT_SCOPE) -endfunction() - -#----------------------------------------------------------------------------- -# Private script mode interface - -if(CMAKE_GENERATOR OR NOT ExternalData_ACTION) - return() -endif() - -if(ExternalData_CONFIG) - include(${ExternalData_CONFIG}) -endif() -if(NOT ExternalData_URL_TEMPLATES AND NOT ExternalData_OBJECT_STORES) - message(FATAL_ERROR - "Neither ExternalData_URL_TEMPLATES nor ExternalData_OBJECT_STORES is set!") -endif() - -function(_ExternalData_link_or_copy src dst) - # Create a temporary file first. - get_filename_component(dst_dir "${dst}" PATH) - file(MAKE_DIRECTORY "${dst_dir}") - _ExternalData_random(random) - set(tmp "${dst}.tmp${random}") - if(UNIX AND NOT ExternalData_NO_SYMLINKS) - # Create a symbolic link. - set(tgt "${src}") - if(relative_top) - # Use relative path if files are close enough. - file(RELATIVE_PATH relsrc "${relative_top}" "${src}") - file(RELATIVE_PATH relfile "${relative_top}" "${dst}") - if(NOT IS_ABSOLUTE "${relsrc}" AND NOT "${relsrc}" MATCHES "^\\.\\./" AND - NOT IS_ABSOLUTE "${reldst}" AND NOT "${reldst}" MATCHES "^\\.\\./") - file(RELATIVE_PATH tgt "${dst_dir}" "${src}") - endif() - endif() - execute_process(COMMAND "${CMAKE_COMMAND}" -E create_symlink "${tgt}" "${tmp}" RESULT_VARIABLE result) - else() - # Create a copy. - execute_process(COMMAND "${CMAKE_COMMAND}" -E copy "${src}" "${tmp}" RESULT_VARIABLE result) - endif() - if(result) - file(REMOVE "${tmp}") - message(FATAL_ERROR "Failed to create\n ${tmp}\nfrom\n ${obj}") - endif() - - # Atomically create/replace the real destination. - file(RENAME "${tmp}" "${dst}") -endfunction() - -function(_ExternalData_download_file url file err_var msg_var) - set(retry 3) - while(retry) - math(EXPR retry "${retry} - 1") - if(ExternalData_TIMEOUT_INACTIVITY) - set(inactivity_timeout INACTIVITY_TIMEOUT ${ExternalData_TIMEOUT_INACTIVITY}) - elseif(NOT "${ExternalData_TIMEOUT_INACTIVITY}" EQUAL 0) - set(inactivity_timeout INACTIVITY_TIMEOUT 60) - else() - set(inactivity_timeout "") - endif() - if(ExternalData_TIMEOUT_ABSOLUTE) - set(absolute_timeout TIMEOUT ${ExternalData_TIMEOUT_ABSOLUTE}) - elseif(NOT "${ExternalData_TIMEOUT_ABSOLUTE}" EQUAL 0) - set(absolute_timeout TIMEOUT 300) - else() - set(absolute_timeout "") - endif() - file(DOWNLOAD "${url}" "${file}" STATUS status LOG log ${inactivity_timeout} ${absolute_timeout} SHOW_PROGRESS) - list(GET status 0 err) - list(GET status 1 msg) - if(err) - if("${msg}" MATCHES "HTTP response code said error" AND - "${log}" MATCHES "error: 503") - set(msg "temporarily unavailable") - endif() - elseif("${log}" MATCHES "\nHTTP[^\n]* 503") - set(err TRUE) - set(msg "temporarily unavailable") - endif() - if(NOT err OR NOT "${msg}" MATCHES "partial|timeout|temporarily") - break() - elseif(retry) - message(STATUS "[download terminated: ${msg}, retries left: ${retry}]") - endif() - endwhile() - set("${err_var}" "${err}" PARENT_SCOPE) - set("${msg_var}" "${msg}" PARENT_SCOPE) -endfunction() - -function(_ExternalData_custom_fetch key loc file err_var msg_var) - if(NOT ExternalData_CUSTOM_SCRIPT_${key}) - set(err 1) - set(msg "No ExternalData_CUSTOM_SCRIPT_${key} set!") - elseif(NOT EXISTS "${ExternalData_CUSTOM_SCRIPT_${key}}") - set(err 1) - set(msg "No '${ExternalData_CUSTOM_SCRIPT_${key}}' exists!") - else() - set(ExternalData_CUSTOM_LOCATION "${loc}") - set(ExternalData_CUSTOM_FILE "${file}") - unset(ExternalData_CUSTOM_ERROR) - include("${ExternalData_CUSTOM_SCRIPT_${key}}") - if(DEFINED ExternalData_CUSTOM_ERROR) - set(err 1) - set(msg "${ExternalData_CUSTOM_ERROR}") - else() - set(err 0) - set(msg "no error") - endif() - endif() - set("${err_var}" "${err}" PARENT_SCOPE) - set("${msg_var}" "${msg}" PARENT_SCOPE) -endfunction() - -function(_ExternalData_get_from_object_store hash algo var_obj var_success) - # Search all object stores for an existing object. - foreach(dir ${ExternalData_OBJECT_STORES}) - set(obj "${dir}/${algo}/${hash}") - if(EXISTS "${obj}") - message(STATUS "Found object: \"${obj}\"") - set("${var_obj}" "${obj}" PARENT_SCOPE) - set("${var_success}" 1 PARENT_SCOPE) - return() - endif() - endforeach() -endfunction() - -function(_ExternalData_download_object name hash algo var_obj var_success var_errorMsg) - # Search all object stores for an existing object. - set(success 1) - foreach(dir ${ExternalData_OBJECT_STORES}) - set(obj "${dir}/${algo}/${hash}") - if(EXISTS "${obj}") - message(STATUS "Found object: \"${obj}\"") - set("${var_obj}" "${obj}" PARENT_SCOPE) - set("${var_success}" "${success}" PARENT_SCOPE) - return() - endif() - endforeach() - - # Download object to the first store. - list(GET ExternalData_OBJECT_STORES 0 store) - set(obj "${store}/${algo}/${hash}") - - _ExternalData_random(random) - set(tmp "${obj}.tmp${random}") - set(found 0) - set(tried "") - foreach(url_template IN LISTS ExternalData_URL_TEMPLATES) - string(REPLACE "%(hash)" "${hash}" url_tmp "${url_template}") - string(REPLACE "%(algo)" "${algo}" url "${url_tmp}") - if(url MATCHES "^(.*)%\\(algo:([A-Za-z_][A-Za-z0-9_]*)\\)(.*)$") - set(lhs "${CMAKE_MATCH_1}") - set(key "${CMAKE_MATCH_2}") - set(rhs "${CMAKE_MATCH_3}") - if(DEFINED ExternalData_URL_ALGO_${algo}_${key}) - set(url "${lhs}${ExternalData_URL_ALGO_${algo}_${key}}${rhs}") - else() - set(url "${lhs}${algo}${rhs}") - endif() - endif() - string(REGEX REPLACE "((https?|ftp)://)([^@]+@)?(.*)" "\\1\\4" secured_url "${url}") - message(STATUS "Fetching \"${secured_url}\"") - if(url MATCHES "^ExternalDataCustomScript://([A-Za-z_][A-Za-z0-9_]*)/(.*)$") - _ExternalData_custom_fetch("${CMAKE_MATCH_1}" "${CMAKE_MATCH_2}" "${tmp}" err errMsg) - else() - _ExternalData_download_file("${url}" "${tmp}" err errMsg) - endif() - string(APPEND tried "\n ${url}") - if(err) - string(APPEND tried " (${errMsg})") - else() - # Verify downloaded object. - _ExternalData_compute_hash(dl_hash "${algo}" "${tmp}") - if("${dl_hash}" STREQUAL "${hash}") - set(found 1) - break() - else() - string(APPEND tried " (wrong hash ${algo}=${dl_hash})") - if("$ENV{ExternalData_DEBUG_DOWNLOAD}" MATCHES ".") - file(RENAME "${tmp}" "${store}/${algo}/${dl_hash}") - endif() - endif() - endif() - file(REMOVE "${tmp}") - endforeach() - - get_filename_component(dir "${name}" PATH) - set(staged "${dir}/.ExternalData_${algo}_${hash}") - - set(success 1) - if(found) - file(RENAME "${tmp}" "${obj}") - message(STATUS "Downloaded object: \"${obj}\"") - elseif(EXISTS "${staged}") - set(obj "${staged}") - message(STATUS "Staged object: \"${obj}\"") - else() - if(NOT tried) - set(tried "\n (No ExternalData_URL_TEMPLATES given)") - endif() - set(success 0) - set("${var_errorMsg}" "Object ${algo}=${hash} not found at:${tried}" PARENT_SCOPE) - endif() - - set("${var_obj}" "${obj}" PARENT_SCOPE) - set("${var_success}" "${success}" PARENT_SCOPE) -endfunction() - -if("${ExternalData_ACTION}" STREQUAL "fetch") - foreach(v ExternalData_OBJECT_STORES file name exts) - if(NOT DEFINED "${v}") - message(FATAL_ERROR "No \"-D${v}=\" value provided!") - endif() - endforeach() - - string(REPLACE "+" ";" exts_list "${exts}") - set(succeeded 0) - set(errorMsg "") - set(hash_list ) - set(algo_list ) - set(hash ) - set(algo ) - foreach(ext ${exts_list}) - file(READ "${name}${ext}" hash) - string(STRIP "${hash}" hash) - - if("${ext}" MATCHES "^\\.(${_ExternalData_REGEX_EXT})$") - string(TOUPPER "${CMAKE_MATCH_1}" algo) - string(REPLACE "-" "_" algo "${algo}") - else() - message(FATAL_ERROR "Unknown hash algorithm extension \"${ext}\"") - endif() - - list(APPEND hash_list ${hash}) - list(APPEND algo_list ${algo}) - endforeach() - - list(LENGTH exts_list num_extensions) - math(EXPR exts_range "${num_extensions} - 1") - foreach(ii RANGE 0 ${exts_range}) - list(GET hash_list ${ii} hash) - list(GET algo_list ${ii} algo) - _ExternalData_get_from_object_store("${hash}" "${algo}" obj succeeded) - if(succeeded) - break() - endif() - endforeach() - if(NOT succeeded) - foreach(ii RANGE 0 ${exts_range}) - list(GET hash_list ${ii} hash) - list(GET algo_list ${ii} algo) - _ExternalData_download_object("${name}" "${hash}" "${algo}" - obj succeeded algoErrorMsg) - string(APPEND errorMsg "\n${algoErrorMsg}") - if(succeeded) - break() - endif() - endforeach() - endif() - if(NOT succeeded) - message(FATAL_ERROR "${errorMsg}") - endif() - # Check if file already corresponds to the object. - set(stamp "-hash-stamp") - set(file_up_to_date 0) - if(EXISTS "${file}" AND EXISTS "${file}${stamp}") - file(READ "${file}${stamp}" f_hash) - string(STRIP "${f_hash}" f_hash) - if("${f_hash}" STREQUAL "${hash}") - set(file_up_to_date 1) - endif() - endif() - - if(file_up_to_date) - # Touch the file to convince the build system it is up to date. - file(TOUCH "${file}") - else() - _ExternalData_link_or_copy("${obj}" "${file}") - endif() - - # Atomically update the hash/timestamp file to record the object referenced. - _ExternalData_atomic_write("${file}${stamp}" "${hash}\n") -elseif("${ExternalData_ACTION}" STREQUAL "local") - foreach(v file name) - if(NOT DEFINED "${v}") - message(FATAL_ERROR "No \"-D${v}=\" value provided!") - endif() - endforeach() - _ExternalData_link_or_copy("${name}" "${file}") -else() - message(FATAL_ERROR "Unknown ExternalData_ACTION=[${ExternalData_ACTION}]") -endif()
diff --git a/share/cmake-3.18/Modules/ExternalProject-download.cmake.in b/share/cmake-3.18/Modules/ExternalProject-download.cmake.in deleted file mode 100644 index 99fb917..0000000 --- a/share/cmake-3.18/Modules/ExternalProject-download.cmake.in +++ /dev/null
@@ -1,162 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -cmake_minimum_required(VERSION 3.5) - -function(check_file_hash has_hash hash_is_good) - if("${has_hash}" STREQUAL "") - message(FATAL_ERROR "has_hash Can't be empty") - endif() - - if("${hash_is_good}" STREQUAL "") - message(FATAL_ERROR "hash_is_good Can't be empty") - endif() - - if("@ALGO@" STREQUAL "") - # No check - set("${has_hash}" FALSE PARENT_SCOPE) - set("${hash_is_good}" FALSE PARENT_SCOPE) - return() - endif() - - set("${has_hash}" TRUE PARENT_SCOPE) - - message(STATUS "verifying file... - file='@LOCAL@'") - - file("@ALGO@" "@LOCAL@" actual_value) - - if(NOT "${actual_value}" STREQUAL "@EXPECT_VALUE@") - set("${hash_is_good}" FALSE PARENT_SCOPE) - message(STATUS "@ALGO@ hash of - @LOCAL@ - does not match expected value - expected: '@EXPECT_VALUE@' - actual: '${actual_value}'") - else() - set("${hash_is_good}" TRUE PARENT_SCOPE) - endif() -endfunction() - -function(sleep_before_download attempt) - if(attempt EQUAL 0) - return() - endif() - - if(attempt EQUAL 1) - message(STATUS "Retrying...") - return() - endif() - - set(sleep_seconds 0) - - if(attempt EQUAL 2) - set(sleep_seconds 5) - elseif(attempt EQUAL 3) - set(sleep_seconds 5) - elseif(attempt EQUAL 4) - set(sleep_seconds 15) - elseif(attempt EQUAL 5) - set(sleep_seconds 60) - elseif(attempt EQUAL 6) - set(sleep_seconds 90) - elseif(attempt EQUAL 7) - set(sleep_seconds 300) - else() - set(sleep_seconds 1200) - endif() - - message(STATUS "Retry after ${sleep_seconds} seconds (attempt #${attempt}) ...") - - execute_process(COMMAND "${CMAKE_COMMAND}" -E sleep "${sleep_seconds}") -endfunction() - -if("@LOCAL@" STREQUAL "") - message(FATAL_ERROR "LOCAL can't be empty") -endif() - -if("@REMOTE@" STREQUAL "") - message(FATAL_ERROR "REMOTE can't be empty") -endif() - -if(EXISTS "@LOCAL@") - check_file_hash(has_hash hash_is_good) - if(has_hash) - if(hash_is_good) - message(STATUS "File already exists and hash match (skip download): - file='@LOCAL@' - @ALGO@='@EXPECT_VALUE@'" - ) - return() - else() - message(STATUS "File already exists but hash mismatch. Removing...") - file(REMOVE "@LOCAL@") - endif() - else() - message(STATUS "File already exists but no hash specified (use URL_HASH): - file='@LOCAL@' -Old file will be removed and new file downloaded from URL." - ) - file(REMOVE "@LOCAL@") - endif() -endif() - -set(retry_number 5) - -message(STATUS "Downloading... - dst='@LOCAL@' - timeout='@TIMEOUT_MSG@'" -) - -foreach(i RANGE ${retry_number}) - sleep_before_download(${i}) - - foreach(url @REMOTE@) - message(STATUS "Using src='${url}'") - - @TLS_VERIFY_CODE@ - @TLS_CAINFO_CODE@ - @NETRC_CODE@ - @NETRC_FILE_CODE@ - - file( - DOWNLOAD - "${url}" "@LOCAL@" - @SHOW_PROGRESS@ - @TIMEOUT_ARGS@ - STATUS status - LOG log - @USERPWD_ARGS@ - @HTTP_HEADERS_ARGS@ - ) - - list(GET status 0 status_code) - list(GET status 1 status_string) - - if(status_code EQUAL 0) - check_file_hash(has_hash hash_is_good) - if(has_hash AND NOT hash_is_good) - message(STATUS "Hash mismatch, removing...") - file(REMOVE "@LOCAL@") - else() - message(STATUS "Downloading... done") - return() - endif() - else() - string(APPEND logFailedURLs "error: downloading '${url}' failed - status_code: ${status_code} - status_string: ${status_string} - log: - --- LOG BEGIN --- - ${log} - --- LOG END --- - " - ) - endif() - endforeach() -endforeach() - -message(FATAL_ERROR "Each download failed! - ${logFailedURLs} - " -)
diff --git a/share/cmake-3.18/Modules/ExternalProject-gitupdate.cmake.in b/share/cmake-3.18/Modules/ExternalProject-gitupdate.cmake.in deleted file mode 100644 index eff39c1..0000000 --- a/share/cmake-3.18/Modules/ExternalProject-gitupdate.cmake.in +++ /dev/null
@@ -1,216 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -cmake_minimum_required(VERSION 3.5) - -execute_process( - COMMAND "@git_EXECUTABLE@" rev-list --max-count=1 HEAD - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - OUTPUT_VARIABLE head_sha - OUTPUT_STRIP_TRAILING_WHITESPACE - ) -if(error_code) - message(FATAL_ERROR "Failed to get the hash for HEAD") -endif() - -execute_process( - COMMAND "@git_EXECUTABLE@" show-ref "@git_tag@" - WORKING_DIRECTORY "@work_dir@" - OUTPUT_VARIABLE show_ref_output - ) -# If a remote ref is asked for, which can possibly move around, -# we must always do a fetch and checkout. -if("${show_ref_output}" MATCHES "remotes") - set(is_remote_ref 1) -else() - set(is_remote_ref 0) -endif() - -# Tag is in the form <remote>/<tag> (i.e. origin/master) we must strip -# the remote from the tag. -if("${show_ref_output}" MATCHES "refs/remotes/@git_tag@") - string(REGEX MATCH "^([^/]+)/(.+)$" _unused "@git_tag@") - set(git_remote "${CMAKE_MATCH_1}") - set(git_tag "${CMAKE_MATCH_2}") -else() - set(git_remote "@git_remote_name@") - set(git_tag "@git_tag@") -endif() - -# This will fail if the tag does not exist (it probably has not been fetched -# yet). -execute_process( - COMMAND "@git_EXECUTABLE@" rev-list --max-count=1 "${git_tag}" - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - OUTPUT_VARIABLE tag_sha - OUTPUT_STRIP_TRAILING_WHITESPACE - ) - -# Is the hash checkout out that we want? -if(error_code OR is_remote_ref OR NOT ("${tag_sha}" STREQUAL "${head_sha}")) - execute_process( - COMMAND "@git_EXECUTABLE@" fetch - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to fetch repository '@git_repository@'") - endif() - - if(is_remote_ref) - # Check if stash is needed - execute_process( - COMMAND "@git_EXECUTABLE@" status --porcelain - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - OUTPUT_VARIABLE repo_status - ) - if(error_code) - message(FATAL_ERROR "Failed to get the status") - endif() - string(LENGTH "${repo_status}" need_stash) - - # If not in clean state, stash changes in order to be able to perform a - # rebase or checkout without losing those changes permanently - if(need_stash) - execute_process( - COMMAND "@git_EXECUTABLE@" stash save @git_stash_save_options@ - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to stash changes") - endif() - endif() - - if("@git_update_strategy@" STREQUAL "CHECKOUT") - execute_process( - COMMAND "@git_EXECUTABLE@" checkout "${git_remote}/${git_tag}" - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to checkout tag: '${git_remote}/${git_tag}'") - endif() - else() - # Pull changes from the remote branch - execute_process( - COMMAND "@git_EXECUTABLE@" rebase "${git_remote}/${git_tag}" - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - OUTPUT_VARIABLE rebase_output - ERROR_VARIABLE rebase_output - ) - if(error_code) - # Rebase failed, undo the rebase attempt before continuing - execute_process( - COMMAND "@git_EXECUTABLE@" rebase --abort - WORKING_DIRECTORY "@work_dir@" - ) - - if(NOT "@git_update_strategy@" STREQUAL "REBASE_CHECKOUT") - # Not allowed to do a checkout as a fallback, so cannot proceed - if(need_stash) - execute_process( - COMMAND "@git_EXECUTABLE@" stash pop --index --quiet - WORKING_DIRECTORY "@work_dir@" - ) - endif() - message(FATAL_ERROR "\nFailed to rebase in: '@work_dir@'." - "\nOutput from the attempted rebase follows:" - "\n${rebase_output}" - "\n\nYou will have to resolve the conflicts manually") - endif() - - # Fall back to checkout. We create an annotated tag so that the user - # can manually inspect the situation and revert if required. - # We can't log the failed rebase output because MSVC sees it and - # intervenes, causing the build to fail even though it completes. - # Write it to a file instead. - string(TIMESTAMP tag_timestamp "%Y%m%dT%H%M%S" UTC) - set(tag_name _cmake_ExternalProject_moved_from_here_${tag_timestamp}Z) - set(error_log_file ${CMAKE_CURRENT_LIST_DIR}/rebase_error_${tag_timestamp}Z.log) - file(WRITE ${error_log_file} "${rebase_output}") - message(WARNING "Rebase failed, output has been saved to ${error_log_file}" - "\nFalling back to checkout, previous commit tagged as ${tag_name}") - execute_process( - COMMAND "@git_EXECUTABLE@" tag -a - -m "ExternalProject attempting to move from here to ${git_remote}/${git_tag}" - ${tag_name} - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to add marker tag") - endif() - - execute_process( - COMMAND "@git_EXECUTABLE@" checkout "${git_remote}/${git_tag}" - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to checkout : '${git_remote}/${git_tag}'") - endif() - - endif() - endif() - - if(need_stash) - execute_process( - COMMAND "@git_EXECUTABLE@" stash pop --index --quiet - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - # Stash pop --index failed: Try again dropping the index - execute_process( - COMMAND "@git_EXECUTABLE@" reset --hard --quiet - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - execute_process( - COMMAND "@git_EXECUTABLE@" stash pop --quiet - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - # Stash pop failed: Restore previous state. - execute_process( - COMMAND "@git_EXECUTABLE@" reset --hard --quiet ${head_sha} - WORKING_DIRECTORY "@work_dir@" - ) - execute_process( - COMMAND "@git_EXECUTABLE@" stash pop --index --quiet - WORKING_DIRECTORY "@work_dir@" - ) - message(FATAL_ERROR "\nFailed to unstash changes in: '@work_dir@'." - "\nYou will have to resolve the conflicts manually") - endif() - endif() - endif() - else() - execute_process( - COMMAND "@git_EXECUTABLE@" checkout "${git_tag}" - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - if(error_code) - message(FATAL_ERROR "Failed to checkout tag: '${git_tag}'") - endif() - endif() - - set(init_submodules "@init_submodules@") - if(init_submodules) - execute_process( - COMMAND "@git_EXECUTABLE@" submodule update @git_submodules_recurse@ --init @git_submodules@ - WORKING_DIRECTORY "@work_dir@" - RESULT_VARIABLE error_code - ) - endif() - if(error_code) - message(FATAL_ERROR "Failed to update submodules in: '@work_dir@'") - endif() -endif()
diff --git a/share/cmake-3.18/Modules/ExternalProject.cmake b/share/cmake-3.18/Modules/ExternalProject.cmake deleted file mode 100644 index aecc00b..0000000 --- a/share/cmake-3.18/Modules/ExternalProject.cmake +++ /dev/null
@@ -1,3241 +0,0 @@ -# Distributed under the OSI-approved BSD 3-Clause License. See accompanying -# file Copyright.txt or https://cmake.org/licensing for details. - -#[=======================================================================[.rst: -ExternalProject ---------------- - -.. only:: html - - .. contents:: - -Commands -^^^^^^^^ - -External Project Definition -""""""""""""""""""""""""""" - -.. command:: ExternalProject_Add - - The ``ExternalProject_Add()`` function creates a custom target to drive - download, update/patch, configure, build, install and test steps of an - external project: - - .. code-block:: cmake - - ExternalProject_Add(<name> [<option>...]) - - The individual steps within the process can be driven independently if - required (e.g. for CDash submission) and extra custom steps can be defined, - along with the ability to control the step dependencies. The directory - structure used for the management of the external project can also be - customized. The function supports a large number of options which can be used - to tailor the external project behavior. - - **Directory Options:** - Most of the time, the default directory layout is sufficient. It is largely - an implementation detail that the main project usually doesn't need to - change. In some circumstances, however, control over the directory layout - can be useful or necessary. The directory options are potentially more - useful from the point of view that the main build can use the - :command:`ExternalProject_Get_Property` command to retrieve their values, - thereby allowing the main project to refer to build artifacts of the - external project. - - ``PREFIX <dir>`` - Root directory for the external project. Unless otherwise noted below, - all other directories associated with the external project will be - created under here. - - ``TMP_DIR <dir>`` - Directory in which to store temporary files. - - ``STAMP_DIR <dir>`` - Directory in which to store the timestamps of each step. Log files from - individual steps are also created in here unless overridden by LOG_DIR - (see *Logging Options* below). - - ``LOG_DIR <dir>`` - Directory in which to store the logs of each step. - - ``DOWNLOAD_DIR <dir>`` - Directory in which to store downloaded files before unpacking them. This - directory is only used by the URL download method, all other download - methods use ``SOURCE_DIR`` directly instead. - - ``SOURCE_DIR <dir>`` - Source directory into which downloaded contents will be unpacked, or for - non-URL download methods, the directory in which the repository should be - checked out, cloned, etc. If no download method is specified, this must - point to an existing directory where the external project has already - been unpacked or cloned/checked out. - - .. note:: - If a download method is specified, any existing contents of the source - directory may be deleted. Only the URL download method checks whether - this directory is either missing or empty before initiating the - download, stopping with an error if it is not empty. All other - download methods silently discard any previous contents of the source - directory. - - ``BINARY_DIR <dir>`` - Specify the build directory location. This option is ignored if - ``BUILD_IN_SOURCE`` is enabled. - - ``INSTALL_DIR <dir>`` - Installation prefix to be placed in the ``<INSTALL_DIR>`` placeholder. - This does not actually configure the external project to install to - the given prefix. That must be done by passing appropriate arguments - to the external project configuration step, e.g. using ``<INSTALL_DIR>``. - - If any of the above ``..._DIR`` options are not specified, their defaults - are computed as follows. If the ``PREFIX`` option is given or the - ``EP_PREFIX`` directory property is set, then an external project is built - and installed under the specified prefix:: - - TMP_DIR = <prefix>/tmp - STAMP_DIR = <prefix>/src/<name>-stamp - DOWNLOAD_DIR = <prefix>/src - SOURCE_DIR = <prefix>/src/<name> - BINARY_DIR = <prefix>/src/<name>-build - INSTALL_DIR = <prefix> - LOG_DIR = <STAMP_DIR> - - Otherwise, if the ``EP_BASE`` directory property is set then components - of an external project are stored under the specified base:: - - TMP_DIR = <base>/tmp/<name> - STAMP_DIR = <base>/Stamp/<name> - DOWNLOAD_DIR = <base>/Download/<name> - SOURCE_DIR = <base>/Source/<name> - BINARY_DIR = <base>/Build/<name> - INSTALL_DIR = <base>/Install/<name> - LOG_DIR = <STAMP_DIR> - - If no ``PREFIX``, ``EP_PREFIX``, or ``EP_BASE`` is specified, then the - default is to set ``PREFIX`` to ``<name>-prefix``. Relative paths are - interpreted with respect to :variable:`CMAKE_CURRENT_BINARY_DIR` at the - point where ``ExternalProject_Add()`` is called. - - **Download Step Options:** - A download method can be omitted if the ``SOURCE_DIR`` option is used to - point to an existing non-empty directory. Otherwise, one of the download - methods below must be specified (multiple download methods should not be - given) or a custom ``DOWNLOAD_COMMAND`` provided. - - ``DOWNLOAD_COMMAND <cmd>...`` - Overrides the command used for the download step - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). If this option is specified, all other download options will - be ignored. Providing an empty string for ``<cmd>`` effectively disables - the download step. - - *URL Download* - ``URL <url1> [<url2>...]`` - List of paths and/or URL(s) of the external project's source. When more - than one URL is given, they are tried in turn until one succeeds. A URL - may be an ordinary path in the local file system (in which case it - must be the only URL provided) or any downloadable URL supported by the - :command:`file(DOWNLOAD)` command. A local filesystem path may refer to - either an existing directory or to an archive file, whereas a URL is - expected to point to a file which can be treated as an archive. When an - archive is used, it will be unpacked automatically unless the - ``DOWNLOAD_NO_EXTRACT`` option is set to prevent it. The archive type - is determined by inspecting the actual content rather than using logic - based on the file extension. - - ``URL_HASH <algo>=<hashValue>`` - Hash of the archive file to be downloaded. The argument should be of - the form ``<algo>=<hashValue>`` where ``algo`` can be any of the hashing - algorithms supported by the :command:`file()` command. Specifying this - option is strongly recommended for URL downloads, as it ensures the - integrity of the downloaded content. It is also used as a check for a - previously downloaded file, allowing connection to the remote location - to be avoided altogether if the local directory already has a file from - an earlier download that matches the specified hash. - - ``URL_MD5 <md5>`` - Equivalent to ``URL_HASH MD5=<md5>``. - - ``DOWNLOAD_NAME <fname>`` - File name to use for the downloaded file. If not given, the end of the - URL is used to determine the file name. This option is rarely needed, - the default name is generally suitable and is not normally used outside - of code internal to the ``ExternalProject`` module. - - ``DOWNLOAD_NO_EXTRACT <bool>`` - Allows the extraction part of the download step to be disabled by - passing a boolean true value for this option. If this option is not - given, the downloaded contents will be unpacked automatically if - required. If extraction has been disabled, the full path to the - downloaded file is available as ``<DOWNLOADED_FILE>`` in subsequent - steps or as the property ``DOWNLOADED_FILE`` with the - :command:`ExternalProject_Get_Property` command. - - ``DOWNLOAD_NO_PROGRESS <bool>`` - Can be used to disable logging the download progress. If this option is - not given, download progress messages will be logged. - - ``TIMEOUT <seconds>`` - Maximum time allowed for file download operations. - - ``HTTP_USERNAME <username>`` - Username for the download operation if authentication is required. - - ``HTTP_PASSWORD <password>`` - Password for the download operation if authentication is required. - - ``HTTP_HEADER <header1> [<header2>...]`` - Provides an arbitrary list of HTTP headers for the download operation. - This can be useful for accessing content in systems like AWS, etc. - - ``TLS_VERIFY <bool>`` - Specifies whether certificate verification should be performed for - https URLs. If this option is not provided, the default behavior is - determined by the ``CMAKE_TLS_VERIFY`` variable (see - :command:`file(DOWNLOAD)`). If that is also not set, certificate - verification will not be performed. In situations where ``URL_HASH`` - cannot be provided, this option can be an alternative verification - measure. - - ``TLS_CAINFO <file>`` - Specify a custom certificate authority file to use if ``TLS_VERIFY`` - is enabled. If this option is not specified, the value of the - ``CMAKE_TLS_CAINFO`` variable will be used instead (see - :command:`file(DOWNLOAD)`) - - ``NETRC <level>`` - Specify whether the ``.netrc`` file is to be used for operation. - If this option is not specified, the value of the ``CMAKE_NETRC`` - variable will be used instead (see :command:`file(DOWNLOAD)`) - Valid levels are: - - ``IGNORED`` - The ``.netrc`` file is ignored. - This is the default. - ``OPTIONAL`` - The ``.netrc`` file is optional, and information in the URL - is preferred. The file will be scanned to find which ever - information is not specified in the URL. - ``REQUIRED`` - The ``.netrc`` file is required, and information in the URL - is ignored. - - ``NETRC_FILE <file>`` - Specify an alternative ``.netrc`` file to the one in your home directory - if the ``NETRC`` level is ``OPTIONAL`` or ``REQUIRED``. If this option - is not specified, the value of the ``CMAKE_NETRC_FILE`` variable will - be used instead (see :command:`file(DOWNLOAD)`) - - *Git* - NOTE: A git version of 1.6.5 or later is required if this download method - is used. - - ``GIT_REPOSITORY <url>`` - URL of the git repository. Any URL understood by the ``git`` command - may be used. - - ``GIT_TAG <tag>`` - Git branch name, tag or commit hash. Note that branch names and tags - should generally be specified as remote names (i.e. ``origin/myBranch`` - rather than simply ``myBranch``). This ensures that if the remote end - has its tag moved or branch rebased or history rewritten, the local - clone will still be updated correctly. In general, however, specifying - a commit hash should be preferred for a number of reasons: - - - If the local clone already has the commit corresponding to the hash, - no ``git fetch`` needs to be performed to check for changes each time - CMake is re-run. This can result in a significant speed up if many - external projects are being used. - - Using a specific git hash ensures that the main project's own history - is fully traceable to a specific point in the external project's - evolution. If a branch or tag name is used instead, then checking out - a specific commit of the main project doesn't necessarily pin the - whole build to a specific point in the life of the external project. - The lack of such deterministic behavior makes the main project lose - traceability and repeatability. - - If ``GIT_SHALLOW`` is enabled then ``GIT_TAG`` works only with - branch names and tags. A commit hash is not allowed. - - ``GIT_REMOTE_NAME <name>`` - The optional name of the remote. If this option is not specified, it - defaults to ``origin``. - - ``GIT_SUBMODULES <module>...`` - Specific git submodules that should also be updated. If this option is - not provided, all git submodules will be updated. When :policy:`CMP0097` - is set to ``NEW`` if this value is set to an empty string then no submodules - are initialized or updated. - - ``GIT_SUBMODULES_RECURSE <bool>`` - Specify whether git submodules (if any) should update recursively by - passing the ``--recursive`` flag to ``git submodule update``. - If not specified, the default is on. - - ``GIT_SHALLOW <bool>`` - When this option is enabled, the ``git clone`` operation will be given - the ``--depth 1`` option. This performs a shallow clone, which avoids - downloading the whole history and instead retrieves just the commit - denoted by the ``GIT_TAG`` option. - - ``GIT_PROGRESS <bool>`` - When enabled, this option instructs the ``git clone`` operation to - report its progress by passing it the ``--progress`` option. Without - this option, the clone step for large projects may appear to make the - build stall, since nothing will be logged until the clone operation - finishes. While this option can be used to provide progress to prevent - the appearance of the build having stalled, it may also make the build - overly noisy if lots of external projects are used. - - ``GIT_CONFIG <option1> [<option2>...]`` - Specify a list of config options to pass to ``git clone``. Each option - listed will be transformed into its own ``--config <option>`` on the - ``git clone`` command line, with each option required to be in the - form ``key=value``. - - ``GIT_REMOTE_UPDATE_STRATEGY <strategy>`` - When ``GIT_TAG`` refers to a remote branch, this option can be used to - specify how the update step behaves. The ``<strategy>`` must be one of - the following: - - ``CHECKOUT`` - Ignore the local branch and always checkout the branch specified by - ``GIT_TAG``. - - ``REBASE`` - Try to rebase the current branch to the one specified by ``GIT_TAG``. - If there are local uncommitted changes, they will be stashed first - and popped again after rebasing. If rebasing or popping stashed - changes fail, abort the rebase and halt with an error. - When ``GIT_REMOTE_UPDATE_STRATEGY`` is not present, this is the - default strategy unless the default has been overridden with - ``CMAKE_EP_GIT_REMOTE_UPDATE_STRATEGY`` (see below). - - ``REBASE_CHECKOUT`` - Same as ``REBASE`` except if the rebase fails, an annotated tag will - be created at the original ``HEAD`` position from before the rebase - and then checkout ``GIT_TAG`` just like the ``CHECKOUT`` strategy. - The message stored on the annotated tag will give information about - what was attempted and the tag name will include a timestamp so that - each failed run will add a new tag. This strategy ensures no changes - will be lost, but updates should always succeed if ``GIT_TAG`` refers - to a valid ref unless there are uncommitted changes that cannot be - popped successfully. - - The variable ``CMAKE_EP_GIT_REMOTE_UPDATE_STRATEGY`` can be set to - override the default strategy. This variable should not be set by a - project, it is intended for the user to set. It is primarily intended - for use in continuous integration scripts to ensure that when history - is rewritten on a remote branch, the build doesn't end up with unintended - changes or failed builds resulting from conflicts during rebase operations. - - *Subversion* - ``SVN_REPOSITORY <url>`` - URL of the Subversion repository. - - ``SVN_REVISION -r<rev>`` - Revision to checkout from the Subversion repository. - - ``SVN_USERNAME <username>`` - Username for the Subversion checkout and update. - - ``SVN_PASSWORD <password>`` - Password for the Subversion checkout and update. - - ``SVN_TRUST_CERT <bool>`` - Specifies whether to trust the Subversion server site certificate. If - enabled, the ``--trust-server-cert`` option is passed to the ``svn`` - checkout and update commands. - - *Mercurial* - ``HG_REPOSITORY <url>`` - URL of the mercurial repository. - - ``HG_TAG <tag>`` - Mercurial branch name, tag or commit id. - - *CVS* - ``CVS_REPOSITORY <cvsroot>`` - CVSROOT of the CVS repository. - - ``CVS_MODULE <mod>`` - Module to checkout from the CVS repository. - - ``CVS_TAG <tag>`` - Tag to checkout from the CVS repository. - - **Update/Patch Step Options:** - Whenever CMake is re-run, by default the external project's sources will be - updated if the download method supports updates (e.g. a git repository - would be checked if the ``GIT_TAG`` does not refer to a specific commit). - - ``UPDATE_COMMAND <cmd>...`` - Overrides the download method's update step with a custom command. - The command may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - - ``UPDATE_DISCONNECTED <bool>`` - When enabled, this option causes the update step to be skipped. It does - not, however, prevent the download step. The update step can still be - added as a step target (see :command:`ExternalProject_Add_StepTargets`) - and called manually. This is useful if you want to allow developers to - build the project when disconnected from the network (the network may - still be needed for the download step though). - - When this option is present, it is generally advisable to make the value - a cache variable under the developer's control rather than hard-coding - it. If this option is not present, the default value is taken from the - ``EP_UPDATE_DISCONNECTED`` directory property. If that is also not - defined, updates are performed as normal. The ``EP_UPDATE_DISCONNECTED`` - directory property is intended as a convenience for controlling the - ``UPDATE_DISCONNECTED`` behavior for an entire section of a project's - directory hierarchy and may be a more convenient method of giving - developers control over whether or not to perform updates (assuming the - project also provides a cache variable or some other convenient method - for setting the directory property). - - ``PATCH_COMMAND <cmd>...`` - Specifies a custom command to patch the sources after an update. By - default, no patch command is defined. Note that it can be quite difficult - to define an appropriate patch command that performs robustly, especially - for download methods such as git where changing the ``GIT_TAG`` will not - discard changes from a previous patch, but the patch command will be - called again after updating to the new tag. - - **Configure Step Options:** - The configure step is run after the download and update steps. By default, - the external project is assumed to be a CMake project, but this can be - overridden if required. - - ``CONFIGURE_COMMAND <cmd>...`` - The default configure command runs CMake with options based on the main - project. For non-CMake external projects, the ``CONFIGURE_COMMAND`` - option must be used to override this behavior - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). For projects that require no configure step, specify this - option with an empty string as the command to execute. - - ``CMAKE_COMMAND /.../cmake`` - Specify an alternative cmake executable for the configure step (use an - absolute path). This is generally not recommended, since it is - usually desirable to use the same CMake version throughout the whole - build. This option is ignored if a custom configure command has been - specified with ``CONFIGURE_COMMAND``. - - ``CMAKE_GENERATOR <gen>`` - Override the CMake generator used for the configure step. Without this - option, the same generator as the main build will be used. This option is - ignored if a custom configure command has been specified with the - ``CONFIGURE_COMMAND`` option. - - ``CMAKE_GENERATOR_PLATFORM <platform>`` - Pass a generator-specific platform name to the CMake command (see - :variable:`CMAKE_GENERATOR_PLATFORM`). It is an error to provide this - option without the ``CMAKE_GENERATOR`` option. - - ``CMAKE_GENERATOR_TOOLSET <toolset>`` - Pass a generator-specific toolset name to the CMake command (see - :variable:`CMAKE_GENERATOR_TOOLSET`). It is an error to provide this - option without the ``CMAKE_GENERATOR`` option. - - ``CMAKE_GENERATOR_INSTANCE <instance>`` - Pass a generator-specific instance selection to the CMake command (see - :variable:`CMAKE_GENERATOR_INSTANCE`). It is an error to provide this - option without the ``CMAKE_GENERATOR`` option. - - ``CMAKE_ARGS <arg>...`` - The specified arguments are passed to the ``cmake`` command line. They - can be any argument the ``cmake`` command understands, not just cache - values defined by ``-D...`` arguments (see also - :manual:`CMake Options <cmake(1)>`). In addition, arguments may use - :manual:`generator expressions <cmake-generator-expressions(7)>`. - - ``CMAKE_CACHE_ARGS <arg>...`` - This is an alternate way of specifying cache variables where command line - length issues may become a problem. The arguments are expected to be in - the form ``-Dvar:STRING=value``, which are then transformed into - CMake :command:`set` commands with the ``FORCE`` option used. These - ``set()`` commands are written to a pre-load script which is then applied - using the :manual:`cmake -C <cmake(1)>` command line option. Arguments - may use :manual:`generator expressions <cmake-generator-expressions(7)>`. - - ``CMAKE_CACHE_DEFAULT_ARGS <arg>...`` - This is the same as the ``CMAKE_CACHE_ARGS`` option except the ``set()`` - commands do not include the ``FORCE`` keyword. This means the values act - as initial defaults only and will not override any variables already set - from a previous run. Use this option with care, as it can lead to - different behavior depending on whether the build starts from a fresh - build directory or re-uses previous build contents. - - If the CMake generator is the ``Green Hills MULTI`` and not overridden then - the original project's settings for the GHS toolset and target system - customization cache variables are propagated into the external project. - - ``SOURCE_SUBDIR <dir>`` - When no ``CONFIGURE_COMMAND`` option is specified, the configure step - assumes the external project has a ``CMakeLists.txt`` file at the top of - its source tree (i.e. in ``SOURCE_DIR``). The ``SOURCE_SUBDIR`` option - can be used to point to an alternative directory within the source tree - to use as the top of the CMake source tree instead. This must be a - relative path and it will be interpreted as being relative to - ``SOURCE_DIR``. When ``BUILD_IN_SOURCE 1`` is specified, the - ``BUILD_COMMAND`` is used to point to an alternative directory within the - source tree. - - **Build Step Options:** - If the configure step assumed the external project uses CMake as its build - system, the build step will also. Otherwise, the build step will assume a - Makefile-based build and simply run ``make`` with no arguments as the - default build step. This can be overridden with custom build commands if - required. - - ``BUILD_COMMAND <cmd>...`` - Overrides the default build command - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). If this option is not given, the default build command will - be chosen to integrate with the main build in the most appropriate way - (e.g. using recursive ``make`` for Makefile generators or - ``cmake --build`` if the project uses a CMake build). This option can be - specified with an empty string as the command to make the build step do - nothing. - - ``BUILD_IN_SOURCE <bool>`` - When this option is enabled, the build will be done directly within the - external project's source tree. This should generally be avoided, the use - of a separate build directory is usually preferred, but it can be useful - when the external project assumes an in-source build. The ``BINARY_DIR`` - option should not be specified if building in-source. - - ``BUILD_ALWAYS <bool>`` - Enabling this option forces the build step to always be run. This can be - the easiest way to robustly ensure that the external project's own build - dependencies are evaluated rather than relying on the default - success timestamp-based method. This option is not normally needed unless - developers are expected to modify something the external project's build - depends on in a way that is not detectable via the step target - dependencies (e.g. ``SOURCE_DIR`` is used without a download method and - developers might modify the sources in ``SOURCE_DIR``). - - ``BUILD_BYPRODUCTS <file>...`` - Specifies files that will be generated by the build command but which - might or might not have their modification time updated by subsequent - builds. These ultimately get passed through as ``BYPRODUCTS`` to the - build step's own underlying call to :command:`add_custom_command`. - - **Install Step Options:** - If the configure step assumed the external project uses CMake as its build - system, the install step will also. Otherwise, the install step will assume - a Makefile-based build and simply run ``make install`` as the default build - step. This can be overridden with custom install commands if required. - - ``INSTALL_COMMAND <cmd>...`` - The external project's own install step is invoked as part of the main - project's *build*. It is done after the external project's build step - and may be before or after the external project's test step (see the - ``TEST_BEFORE_INSTALL`` option below). The external project's install - rules are not part of the main project's install rules, so if anything - from the external project should be installed as part of the main build, - these need to be specified in the main build as additional - :command:`install` commands. The default install step builds the - ``install`` target of the external project, but this can be overridden - with a custom command using this option - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). Passing an empty string as the ``<cmd>`` makes the install - step do nothing. - - **Test Step Options:** - The test step is only defined if at least one of the following ``TEST_...`` - options are provided. - - ``TEST_COMMAND <cmd>...`` - Overrides the default test command - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). If this option is not given, the default behavior of the test - step is to build the external project's own ``test`` target. This option - can be specified with ``<cmd>`` as an empty string, which allows the test - step to still be defined, but it will do nothing. Do not specify any of - the other ``TEST_...`` options if providing an empty string as the test - command, but prefer to omit all ``TEST_...`` options altogether if the - test step target is not needed. - - ``TEST_BEFORE_INSTALL <bool>`` - When this option is enabled, the test step will be executed before the - install step. The default behavior is for the test step to run after the - install step. - - ``TEST_AFTER_INSTALL <bool>`` - This option is mainly useful as a way to indicate that the test step is - desired but all default behavior is sufficient. Specifying this option - with a boolean true value ensures the test step is defined and that it - comes after the install step. If both ``TEST_BEFORE_INSTALL`` and - ``TEST_AFTER_INSTALL`` are enabled, the latter is silently ignored. - - ``TEST_EXCLUDE_FROM_MAIN <bool>`` - If enabled, the main build's default ALL target will not depend on the - test step. This can be a useful way of ensuring the test step is defined - but only gets invoked when manually requested. - - **Output Logging Options:** - Each of the following ``LOG_...`` options can be used to wrap the relevant - step in a script to capture its output to files. The log files will be - created in ``LOG_DIR`` if supplied or otherwise the ``STAMP_DIR`` - directory with step-specific file names. - - ``LOG_DOWNLOAD <bool>`` - When enabled, the output of the download step is logged to files. - - ``LOG_UPDATE <bool>`` - When enabled, the output of the update step is logged to files. - - ``LOG_PATCH <bool>`` - When enabled, the output of the patch step is logged to files. - - ``LOG_CONFIGURE <bool>`` - When enabled, the output of the configure step is logged to files. - - ``LOG_BUILD <bool>`` - When enabled, the output of the build step is logged to files. - - ``LOG_INSTALL <bool>`` - When enabled, the output of the install step is logged to files. - - ``LOG_TEST <bool>`` - When enabled, the output of the test step is logged to files. - - ``LOG_MERGED_STDOUTERR <bool>`` - When enabled, stdout and stderr will be merged for any step whose - output is being logged to files. - - ``LOG_OUTPUT_ON_FAILURE <bool>`` - This option only has an effect if at least one of the other ``LOG_<step>`` - options is enabled. If an error occurs for a step which has logging to - file enabled, that step's output will be printed to the console if - ``LOG_OUTPUT_ON_FAILURE`` is set to true. For cases where a large amount - of output is recorded, just the end of that output may be printed to the - console. - - **Terminal Access Options:** - Steps can be given direct access to the terminal in some cases. Giving a - step access to the terminal may allow it to receive terminal input if - required, such as for authentication details not provided by other options. - With the :generator:`Ninja` generator, these options place the steps in the - ``console`` :prop_gbl:`job pool <JOB_POOLS>`. Each step can be given access - to the terminal individually via the following options: - - ``USES_TERMINAL_DOWNLOAD <bool>`` - Give the download step access to the terminal. - - ``USES_TERMINAL_UPDATE <bool>`` - Give the update step access to the terminal. - - ``USES_TERMINAL_CONFIGURE <bool>`` - Give the configure step access to the terminal. - - ``USES_TERMINAL_BUILD <bool>`` - Give the build step access to the terminal. - - ``USES_TERMINAL_INSTALL <bool>`` - Give the install step access to the terminal. - - ``USES_TERMINAL_TEST <bool>`` - Give the test step access to the terminal. - - **Target Options:** - ``DEPENDS <targets>...`` - Specify other targets on which the external project depends. The other - targets will be brought up to date before any of the external project's - steps are executed. Because the external project uses additional custom - targets internally for each step, the ``DEPENDS`` option is the most - convenient way to ensure all of those steps depend on the other targets. - Simply doing - :command:`add_dependencies(\<name\> \<targets\>) <add_dependencies>` will - not make any of the steps dependent on ``<targets>``. - - ``EXCLUDE_FROM_ALL <bool>`` - When enabled, this option excludes the external project from the default - ALL target of the main build. - - ``STEP_TARGETS <step-target>...`` - Generate custom targets for the specified steps. This is required if the - steps need to be triggered manually or if they need to be used as - dependencies of other targets. If this option is not specified, the - default value is taken from the ``EP_STEP_TARGETS`` directory property. - See :command:`ExternalProject_Add_Step` below for further discussion of - the effects of this option. - - ``INDEPENDENT_STEP_TARGETS <step-target>...`` - Generate custom targets for the specified steps and prevent these targets - from having the usual dependencies applied to them. If this option is not - specified, the default value is taken from the - ``EP_INDEPENDENT_STEP_TARGETS`` directory property. This option is mostly - useful for allowing individual steps to be driven independently, such as - for a CDash setup where each step should be initiated and reported - individually rather than as one whole build. See - :command:`ExternalProject_Add_Step` below for further discussion of the - effects of this option. - - **Miscellaneous Options:** - ``LIST_SEPARATOR <sep>`` - For any of the various ``..._COMMAND`` options, replace ``;`` with - ``<sep>`` in the specified command lines. This can be useful where list - variables may be given in commands where they should end up as - space-separated arguments (``<sep>`` would be a single space character - string in this case). - - ``COMMAND <cmd>...`` - Any of the other ``..._COMMAND`` options can have additional commands - appended to them by following them with as many ``COMMAND ...`` options - as needed - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). For example: - - .. code-block:: cmake - - ExternalProject_Add(example - ... # Download options, etc. - BUILD_COMMAND ${CMAKE_COMMAND} -E echo "Starting $<CONFIG> build" - COMMAND ${CMAKE_COMMAND} --build <BINARY_DIR> --config $<CONFIG> - COMMAND ${CMAKE_COMMAND} -E echo "$<CONFIG> build complete" - ) - - It should also be noted that each build step is created via a call to - :command:`ExternalProject_Add_Step`. See that command's documentation for the - automatic substitutions that are supported for some options. - -Obtaining Project Properties -"""""""""""""""""""""""""""" - -.. command:: ExternalProject_Get_Property - - The ``ExternalProject_Get_Property()`` function retrieves external project - target properties: - - .. code-block:: cmake - - ExternalProject_Get_Property(<name> <prop1> [<prop2>...]) - - The function stores property values in variables of the same name. Property - names correspond to the keyword argument names of ``ExternalProject_Add()``. - For example, the source directory might be retrieved like so: - - .. code-block:: cmake - - ExternalProject_Get_property(myExtProj SOURCE_DIR) - message("Source dir of myExtProj = ${SOURCE_DIR}") - -Explicit Step Management -"""""""""""""""""""""""" - -The ``ExternalProject_Add()`` function on its own is often sufficient for -incorporating an external project into the main build. Certain scenarios -require additional work to implement desired behavior, such as adding in a -custom step or making steps available as manually triggerable targets. The -``ExternalProject_Add_Step()``, ``ExternalProject_Add_StepTargets()`` and -``ExternalProject_Add_StepDependencies`` functions provide the lower level -control needed to implement such step-level capabilities. - -.. command:: ExternalProject_Add_Step - - The ``ExternalProject_Add_Step()`` function specifies an additional custom - step for an external project defined by an earlier call to - :command:`ExternalProject_Add`: - - .. code-block:: cmake - - ExternalProject_Add_Step(<name> <step> [<option>...]) - - ``<name>`` is the same as the name passed to the original call to - :command:`ExternalProject_Add`. The specified ``<step>`` must not be one of - the pre-defined steps (``mkdir``, ``download``, ``update``, ``skip-update``, - ``patch``, ``configure``, ``build``, ``install`` or ``test``). The supported - options are: - - ``COMMAND <cmd>...`` - The command line to be executed by this custom step - (:manual:`generator expressions <cmake-generator-expressions(7)>` are - supported). This option can be repeated multiple times to specify multiple - commands to be executed in order. - - ``COMMENT "<text>..."`` - Text to be printed when the custom step executes. - - ``DEPENDEES <step>...`` - Other steps (custom or pre-defined) on which this step depends. - - ``DEPENDERS <step>...`` - Other steps (custom or pre-defined) that depend on this new custom step. - - ``DEPENDS <file>...`` - Files on which this custom step depends. - - ``BYPRODUCTS <file>...`` - Files that will be generated by this custom step but which might or might - not have their modification time updated by subsequent builds. This list of - files will ultimately be passed through as the ``BYPRODUCTS`` option to the - :command:`add_custom_command` used to implement the custom step internally. - - ``ALWAYS <bool>`` - When enabled, this option specifies that the custom step should always be - run (i.e. that it is always considered out of date). - - ``EXCLUDE_FROM_MAIN <bool>`` - When enabled, this option specifies that the external project's main target - does not depend on the custom step. - - ``WORKING_DIRECTORY <dir>`` - Specifies the working directory to set before running the custom step's - command. If this option is not specified, the directory will be the value - of the :variable:`CMAKE_CURRENT_BINARY_DIR` at the point where - ``ExternalProject_Add_Step()`` was called. - - ``LOG <bool>`` - If set, this causes the output from the custom step to be captured to files - in the external project's ``LOG_DIR`` if supplied or ``STAMP_DIR``. - - ``USES_TERMINAL <bool>`` - If enabled, this gives the custom step direct access to the terminal if - possible. - - The command line, comment, working directory and byproducts of every - standard and custom step are processed to replace the tokens - ``<SOURCE_DIR>``, ``<SOURCE_SUBDIR>``, ``<BINARY_DIR>``, ``<INSTALL_DIR>`` - ``<TMP_DIR>``, ``<DOWNLOAD_DIR>`` and ``<DOWNLOADED_FILE>`` with their - corresponding property values defined in the original call to - :command:`ExternalProject_Add`. - -.. command:: ExternalProject_Add_StepTargets - - The ``ExternalProject_Add_StepTargets()`` function generates targets for the - steps listed. The name of each created target will be of the form - ``<name>-<step>``: - - .. code-block:: cmake - - ExternalProject_Add_StepTargets(<name> [NO_DEPENDS] <step1> [<step2>...]) - - Creating a target for a step allows it to be used as a dependency of another - target or to be triggered manually. Having targets for specific steps also - allows them to be driven independently of each other by specifying targets on - build command lines. For example, you may be submitting to a sub-project - based dashboard where you want to drive the configure portion of the build, - then submit to the dashboard, followed by the build portion, followed - by tests. If you invoke a custom target that depends on a step halfway - through the step dependency chain, then all the previous steps will also run - to ensure everything is up to date. - - If the ``NO_DEPENDS`` option is specified, the step target will not depend on - the dependencies of the external project (i.e. on any dependencies of the - ``<name>`` custom target created by :command:`ExternalProject_Add`). This is - usually safe for the ``download``, ``update`` and ``patch`` steps, since they - do not typically require that the dependencies are updated and built. Using - ``NO_DEPENDS`` for any of the other pre-defined steps, however, may break - parallel builds. Only use ``NO_DEPENDS`` where it is certain that the named - steps genuinely do not have dependencies. For custom steps, consider whether - or not the custom commands require the dependencies to be configured, built - and installed. - - Internally, :command:`ExternalProject_Add` calls - :command:`ExternalProject_Add_Step` to create each step. If any - ``STEP_TARGETS`` or ``INDEPENDENT_STEP_TARGETS`` were specified, then - ``ExternalProject_Add_StepTargets()`` will also be called after - :command:`ExternalProject_Add_Step`. ``INDEPENDENT_STEP_TARGETS`` have the - ``NO_DEPENDS`` option set, whereas ``STEP_TARGETS`` do not. Other than that, - the two options result in ``ExternalProject_Add_StepTargets()`` being called - in the same way. Even if a step is not mentioned in either of those two - options, ``ExternalProject_Add_StepTargets()`` can still be called later to - manually define a target for the step. - - The ``STEP_TARGETS`` and ``INDEPENDENT_STEP_TARGETS`` options for - :command:`ExternalProject_Add` are generally the easiest way to ensure - targets are created for specific steps of interest. For custom steps, - ``ExternalProject_Add_StepTargets()`` must be called explicitly if a target - should also be created for that custom step. An alternative to these two - options is to populate the ``EP_STEP_TARGETS`` and - ``EP_INDEPENDENT_STEP_TARGETS`` directory properties. These act as defaults - for the step target options and can save having to repeatedly specify the - same set of step targets when multiple external projects are being defined. - -.. command:: ExternalProject_Add_StepDependencies - - The ``ExternalProject_Add_StepDependencies()`` function can be used to add - dependencies to a step. The dependencies added must be targets CMake already - knows about (these can be ordinary executable or library targets, custom - targets or even step targets of another external project): - - .. code-block:: cmake - - ExternalProject_Add_StepDependencies(<name> <step> <target1> [<target2>...]) - - This function takes care to set both target and file level dependencies and - will ensure that parallel builds will not break. It should be used instead of - :command:`add_dependencies` whenever adding a dependency for some of the step - targets generated by the ``ExternalProject`` module. - -Examples -^^^^^^^^ - -The following example shows how to download and build a hypothetical project -called *FooBar* from github: - -.. code-block:: cmake - - include(ExternalProject) - ExternalProject_Add(foobar - GIT_REPOSITORY git@github.com:FooCo/FooBar.git - GIT_TAG origin/release/1.2.3 - ) - -For the sake of the example, also define a second hypothetical external project -called *SecretSauce*, which is downloaded from a web server. Two URLs are given -to take advantage of a faster internal network if available, with a fallback to -a slower external server. The project is a typical ``Makefile`` project with no -configure step, so some of the default commands are overridden. The build is -only required to build the *sauce* target: - -.. code-block:: cmake - - find_program(MAKE_EXE NAMES gmake nmake make) - ExternalProject_Add(secretsauce - URL http://intranet.somecompany.com/artifacts/sauce-2.7.tgz - https://www.somecompany.com/downloads/sauce-2.7.zip - URL_HASH MD5=d41d8cd98f00b204e9800998ecf8427e - CONFIGURE_COMMAND "" - BUILD_COMMAND ${MAKE_EXE} sauce - ) - -Suppose the build step of ``secretsauce`` requires that ``foobar`` must already -be built. This could be enforced like so: - -.. code-block:: cmake - - ExternalProject_Add_StepDependencies(secretsauce build foobar) - -Another alternative would be to create a custom target for ``foobar``'s build -step and make ``secretsauce`` depend on that rather than the whole ``foobar`` -project. This would mean ``foobar`` only needs to be built, it doesn't need to -run its install or test steps before ``secretsauce`` can be built. The -dependency can also be defined along with the ``secretsauce`` project: - -.. code-block:: cmake - - ExternalProject_Add_StepTargets(foobar build) - ExternalProject_Add(secretsauce - URL http://intranet.somecompany.com/artifacts/sauce-2.7.tgz - https://www.somecompany.com/downloads/sauce-2.7.zip - URL_HASH MD5=d41d8cd98f00b204e9800998ecf8427e - CONFIGURE_COMMAND "" - BUILD_COMMAND ${MAKE_EXE} sauce - DEPENDS foobar-build - ) - -Instead of calling :command:`ExternalProject_Add_StepTargets`, the target could -be defined along with the ``foobar`` project itself: - -.. code-block:: cmake - - ExternalProject_Add(foobar - GIT_REPOSITORY git@github.com:FooCo/FooBar.git - GIT_TAG origin/release/1.2.3 - STEP_TARGETS build - ) - -If many external projects should have the same set of step targets, setting a -directory property may be more convenient. The ``build`` step target could be -created automatically by setting the ``EP_STEP_TARGETS`` directory property -before creating the external projects with :command:`ExternalProject_Add`: - -.. code-block:: cmake - - set_property(DIRECTORY PROPERTY EP_STEP_TARGETS build) - -Lastly, suppose that ``secretsauce`` provides a script called ``makedoc`` which -can be used to generate its own documentation. Further suppose that the script -expects the output directory to be provided as the only parameter and that it -should be run from the ``secretsauce`` source directory. A custom step and a -custom target to trigger the script can be defined like so: - -.. code-block:: cmake - - ExternalProject_Add_Step(secretsauce docs - COMMAND <SOURCE_DIR>/makedoc <BINARY_DIR> - WORKING_DIRECTORY <SOURCE_DIR> - COMMENT "Building secretsauce docs" - ALWAYS TRUE - EXCLUDE_FROM_MAIN TRUE - ) - ExternalProject_Add_StepTargets(secretsauce docs) - -The custom step could then be triggered from the main build like so:: - - cmake --build . --target secretsauce-docs - -#]=======================================================================] - -cmake_policy(PUSH) -cmake_policy(SET CMP0054 NEW) # if() quoted variables not dereferenced -cmake_policy(SET CMP0057 NEW) # if() supports IN_LIST - -# Pre-compute a regex to match documented keywords for each command. -math(EXPR _ep_documentation_line_count "${CMAKE_CURRENT_LIST_LINE} - 4") -file(STRINGS "${CMAKE_CURRENT_LIST_FILE}" lines - LIMIT_COUNT ${_ep_documentation_line_count} - REGEX "^\\.\\. command:: [A-Za-z0-9_]+|^ +``[A-Z0-9_]+ [^`]*``$") -foreach(line IN LISTS lines) - if("${line}" MATCHES "^\\.\\. command:: ([A-Za-z0-9_]+)") - if(_ep_func) - string(APPEND _ep_keywords_${_ep_func} ")$") - endif() - set(_ep_func "${CMAKE_MATCH_1}") - #message("function [${_ep_func}]") - set(_ep_keywords_${_ep_func} "^(") - set(_ep_keyword_sep) - elseif("${line}" MATCHES "^ +``([A-Z0-9_]+) [^`]*``$") - set(_ep_key "${CMAKE_MATCH_1}") - # COMMAND should never be included as a keyword, - # for ExternalProject_Add(), as it is treated as a - # special case by argument parsing as an extension - # of a previous ..._COMMAND - if("x${_ep_key}x" STREQUAL "xCOMMANDx" AND - "x${_ep_func}x" STREQUAL "xExternalProject_Addx") - continue() - endif() - #message(" keyword [${_ep_key}]") - string(APPEND _ep_keywords_${_ep_func} - "${_ep_keyword_sep}${_ep_key}") - set(_ep_keyword_sep "|") - endif() -endforeach() -if(_ep_func) - string(APPEND _ep_keywords_${_ep_func} ")$") -endif() - -# Save regex matching supported hash algorithm names. -set(_ep_hash_algos "MD5|SHA1|SHA224|SHA256|SHA384|SHA512|SHA3_224|SHA3_256|SHA3_384|SHA3_512") -set(_ep_hash_regex "^(${_ep_hash_algos})=([0-9A-Fa-f]+)$") - -set(_ExternalProject_SELF "${CMAKE_CURRENT_LIST_FILE}") -get_filename_component(_ExternalProject_SELF_DIR "${_ExternalProject_SELF}" PATH) - -function(_ep_parse_arguments f name ns args) - # Transfer the arguments to this function into target properties for the - # new custom target we just added so that we can set up all the build steps - # correctly based on target properties. - # - # We loop through ARGN and consider the namespace starting with an - # upper-case letter followed by at least two more upper-case letters, - # numbers or underscores to be keywords. - - if(NOT DEFINED _ExternalProject_SELF) - message(FATAL_ERROR "error: ExternalProject module must be explicitly included before using ${f} function") - endif() - - set(key) - - foreach(arg IN LISTS args) - set(is_value 1) - - if(arg MATCHES "^[A-Z][A-Z0-9_][A-Z0-9_]+$" AND - NOT (("x${arg}x" STREQUAL "x${key}x") AND ("x${key}x" STREQUAL "xCOMMANDx")) AND - NOT arg MATCHES "^(TRUE|FALSE)$") - if(_ep_keywords_${f} AND arg MATCHES "${_ep_keywords_${f}}") - set(is_value 0) - endif() - endif() - - if(is_value) - if(key) - # Value - if(NOT arg STREQUAL "") - set_property(TARGET ${name} APPEND PROPERTY ${ns}${key} "${arg}") - else() - get_property(have_key TARGET ${name} PROPERTY ${ns}${key} SET) - if(have_key) - get_property(value TARGET ${name} PROPERTY ${ns}${key}) - set_property(TARGET ${name} PROPERTY ${ns}${key} "${value};${arg}") - else() - set_property(TARGET ${name} PROPERTY ${ns}${key} "${arg}") - endif() - endif() - else() - # Missing Keyword - message(AUTHOR_WARNING "value '${arg}' with no previous keyword in ${f}") - endif() - else() - set(key "${arg}") - if(key MATCHES GIT) - get_property(have_key TARGET ${name} PROPERTY ${ns}${key} SET) - endif() - endif() - endforeach() -endfunction() - - -define_property(DIRECTORY PROPERTY "EP_BASE" INHERITED - BRIEF_DOCS "Base directory for External Project storage." - FULL_DOCS - "See documentation of the ExternalProject_Add() function in the " - "ExternalProject module." - ) - -define_property(DIRECTORY PROPERTY "EP_PREFIX" INHERITED - BRIEF_DOCS "Top prefix for External Project storage." - FULL_DOCS - "See documentation of the ExternalProject_Add() function in the " - "ExternalProject module." - ) - -define_property(DIRECTORY PROPERTY "EP_STEP_TARGETS" INHERITED - BRIEF_DOCS - "List of ExternalProject steps that automatically get corresponding targets" - FULL_DOCS - "These targets will be dependent on the main target dependencies. " - "See documentation of the ExternalProject_Add_StepTargets() function in the " - "ExternalProject module." - ) - -define_property(DIRECTORY PROPERTY "EP_INDEPENDENT_STEP_TARGETS" INHERITED - BRIEF_DOCS - "List of ExternalProject steps that automatically get corresponding targets" - FULL_DOCS - "These targets will not be dependent on the main target dependencies. " - "See documentation of the ExternalProject_Add_StepTargets() function in the " - "ExternalProject module." - ) - -define_property(DIRECTORY PROPERTY "EP_UPDATE_DISCONNECTED" INHERITED - BRIEF_DOCS "Never update automatically from the remote repo." - FULL_DOCS - "See documentation of the ExternalProject_Add() function in the " - "ExternalProject module." - ) - -function(_ep_write_gitclone_script script_filename source_dir git_EXECUTABLE git_repository git_tag git_remote_name init_submodules git_submodules_recurse git_submodules git_shallow git_progress git_config src_name work_dir gitclone_infofile gitclone_stampfile tls_verify) - if(NOT GIT_VERSION_STRING VERSION_LESS 1.8.5) - # Use `git checkout <tree-ish> --` to avoid ambiguity with a local path. - set(git_checkout_explicit-- "--") - else() - # Use `git checkout <branch>` even though this risks ambiguity with a - # local path. Unfortunately we cannot use `git checkout <tree-ish> --` - # because that will not search for remote branch names, a common use case. - set(git_checkout_explicit-- "") - endif() - if("${git_tag}" STREQUAL "") - message(FATAL_ERROR "Tag for git checkout should not be empty.") - endif() - - if(GIT_VERSION_STRING VERSION_LESS 2.20 OR 2.21 VERSION_LESS_EQUAL GIT_VERSION_STRING) - set(git_clone_options "--no-checkout") - else() - set(git_clone_options) - endif() - if(git_shallow) - if(NOT GIT_VERSION_STRING VERSION_LESS 1.7.10) - list(APPEND git_clone_options "--depth 1 --no-single-branch") - else() - list(APPEND git_clone_options "--depth 1") - endif() - endif() - if(git_progress) - list(APPEND git_clone_options --progress) - endif() - foreach(config IN LISTS git_config) - list(APPEND git_clone_options --config \"${config}\") - endforeach() - if(NOT ${git_remote_name} STREQUAL "origin") - list(APPEND git_clone_options --origin \"${git_remote_name}\") - endif() - - string (REPLACE ";" " " git_clone_options "${git_clone_options}") - - set(git_options) - # disable cert checking if explicitly told not to do it - if(NOT "x${tls_verify}" STREQUAL "x" AND NOT tls_verify) - set(git_options - -c http.sslVerify=false) - endif() - string (REPLACE ";" " " git_options "${git_options}") - - file(WRITE ${script_filename} -" -if(NOT \"${gitclone_infofile}\" IS_NEWER_THAN \"${gitclone_stampfile}\") - message(STATUS \"Avoiding repeated git clone, stamp file is up to date: '${gitclone_stampfile}'\") - return() -endif() - -execute_process( - COMMAND \${CMAKE_COMMAND} -E rm -rf \"${source_dir}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to remove directory: '${source_dir}'\") -endif() - -# try the clone 3 times in case there is an odd git clone issue -set(error_code 1) -set(number_of_tries 0) -while(error_code AND number_of_tries LESS 3) - execute_process( - COMMAND \"${git_EXECUTABLE}\" ${git_options} clone ${git_clone_options} \"${git_repository}\" \"${src_name}\" - WORKING_DIRECTORY \"${work_dir}\" - RESULT_VARIABLE error_code - ) - math(EXPR number_of_tries \"\${number_of_tries} + 1\") -endwhile() -if(number_of_tries GREATER 1) - message(STATUS \"Had to git clone more than once: - \${number_of_tries} times.\") -endif() -if(error_code) - message(FATAL_ERROR \"Failed to clone repository: '${git_repository}'\") -endif() - -execute_process( - COMMAND \"${git_EXECUTABLE}\" ${git_options} checkout ${git_tag} ${git_checkout_explicit--} - WORKING_DIRECTORY \"${work_dir}/${src_name}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to checkout tag: '${git_tag}'\") -endif() - -set(init_submodules ${init_submodules}) -if(init_submodules) - execute_process( - COMMAND \"${git_EXECUTABLE}\" ${git_options} submodule update ${git_submodules_recurse} --init ${git_submodules} - WORKING_DIRECTORY \"${work_dir}/${src_name}\" - RESULT_VARIABLE error_code - ) -endif() -if(error_code) - message(FATAL_ERROR \"Failed to update submodules in: '${work_dir}/${src_name}'\") -endif() - -# Complete success, update the script-last-run stamp file: -# -execute_process( - COMMAND \${CMAKE_COMMAND} -E copy - \"${gitclone_infofile}\" - \"${gitclone_stampfile}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to copy script-last-run stamp file: '${gitclone_stampfile}'\") -endif() - -" -) - -endfunction() - -function(_ep_write_hgclone_script script_filename source_dir hg_EXECUTABLE hg_repository hg_tag src_name work_dir hgclone_infofile hgclone_stampfile) - if("${hg_tag}" STREQUAL "") - message(FATAL_ERROR "Tag for hg checkout should not be empty.") - endif() - file(WRITE ${script_filename} -" -if(NOT \"${hgclone_infofile}\" IS_NEWER_THAN \"${hgclone_stampfile}\") - message(STATUS \"Avoiding repeated hg clone, stamp file is up to date: '${hgclone_stampfile}'\") - return() -endif() - -execute_process( - COMMAND \${CMAKE_COMMAND} -E rm -rf \"${source_dir}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to remove directory: '${source_dir}'\") -endif() - -execute_process( - COMMAND \"${hg_EXECUTABLE}\" clone -U \"${hg_repository}\" \"${src_name}\" - WORKING_DIRECTORY \"${work_dir}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to clone repository: '${hg_repository}'\") -endif() - -execute_process( - COMMAND \"${hg_EXECUTABLE}\" update ${hg_tag} - WORKING_DIRECTORY \"${work_dir}/${src_name}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to checkout tag: '${hg_tag}'\") -endif() - -# Complete success, update the script-last-run stamp file: -# -execute_process( - COMMAND \${CMAKE_COMMAND} -E copy - \"${hgclone_infofile}\" - \"${hgclone_stampfile}\" - RESULT_VARIABLE error_code - ) -if(error_code) - message(FATAL_ERROR \"Failed to copy script-last-run stamp file: '${hgclone_stampfile}'\") -endif() - -" -) - -endfunction() - - -function(_ep_write_gitupdate_script script_filename git_EXECUTABLE git_tag git_remote_name init_submodules git_submodules_recurse git_submodules git_repository work_dir git_update_strategy) - if("${git_tag}" STREQUAL "") - message(FATAL_ERROR "Tag for git checkout should not be empty.") - endif() - if(NOT GIT_VERSION_STRING VERSION_LESS 1.7.6) - set(git_stash_save_options --all --quiet) - else() - set(git_stash_save_options --quiet) - endif() - - configure_file( - "${_ExternalProject_SELF_DIR}/ExternalProject-gitupdate.cmake.in" - "${script_filename}" - @ONLY - ) -endfunction() - -function(_ep_write_downloadfile_script script_filename REMOTE LOCAL timeout no_progress hash tls_verify tls_cainfo userpwd http_headers netrc netrc_file) - if(timeout) - set(TIMEOUT_ARGS TIMEOUT ${timeout}) - set(TIMEOUT_MSG "${timeout} seconds") - else() - set(TIMEOUT_ARGS "# no TIMEOUT") - set(TIMEOUT_MSG "none") - endif() - - if(no_progress) - set(SHOW_PROGRESS "") - else() - set(SHOW_PROGRESS "SHOW_PROGRESS") - endif() - - if("${hash}" MATCHES "${_ep_hash_regex}") - set(ALGO "${CMAKE_MATCH_1}") - string(TOLOWER "${CMAKE_MATCH_2}" EXPECT_VALUE) - else() - set(ALGO "") - set(EXPECT_VALUE "") - endif() - - set(TLS_VERIFY_CODE "") - set(TLS_CAINFO_CODE "") - set(NETRC_CODE "") - set(NETRC_FILE_CODE "") - - # check for curl globals in the project - if(DEFINED CMAKE_TLS_VERIFY) - set(TLS_VERIFY_CODE "set(CMAKE_TLS_VERIFY ${CMAKE_TLS_VERIFY})") - endif() - if(DEFINED CMAKE_TLS_CAINFO) - set(TLS_CAINFO_CODE "set(CMAKE_TLS_CAINFO \"${CMAKE_TLS_CAINFO}\")") - endif() - if(DEFINED CMAKE_NETRC) - set(NETRC_CODE "set(CMAKE_NETRC \"${CMAKE_NETRC}\")") - endif() - if(DEFINED CMAKE_NETRC_FILE) - set(NETRC_FILE_CODE "set(CMAKE_NETRC_FILE \"${CMAKE_NETRC_FILE}\")") - endif() - - # now check for curl locals so that the local values - # will override the globals - - # check for tls_verify argument - string(LENGTH "${tls_verify}" tls_verify_len) - if(tls_verify_len GREATER 0) - set(TLS_VERIFY_CODE "set(CMAKE_TLS_VERIFY ${tls_verify})") - endif() - # check for tls_cainfo argument - string(LENGTH "${tls_cainfo}" tls_cainfo_len) - if(tls_cainfo_len GREATER 0) - set(TLS_CAINFO_CODE "set(CMAKE_TLS_CAINFO \"${tls_cainfo}\")") - endif() - # check for netrc argument - string(LENGTH "${netrc}" netrc_len) - if(netrc_len GREATER 0) - set(NETRC_CODE "set(CMAKE_NETRC \"${netrc}\")") - endif() - # check for netrc_file argument - string(LENGTH "${netrc_file}" netrc_file_len) - if(netrc_file_len GREATER 0) - set(NETRC_FILE_CODE "set(CMAKE_NETRC_FILE \"${netrc_file}\")") - endif() - - if(userpwd STREQUAL ":") - set(USERPWD_ARGS) - else() - set(USERPWD_ARGS USERPWD "${userpwd}") - endif() - - set(HTTP_HEADERS_ARGS "") - if(NOT http_headers STREQUAL "") - foreach(header ${http_headers}) - set( - HTTP_HEADERS_ARGS - "HTTPHEADER \"${header}\"\n ${HTTP_HEADERS_ARGS}" - ) - endforeach() - endif() - - # Used variables: - # * TLS_VERIFY_CODE - # * TLS_CAINFO_CODE - # * ALGO - # * EXPECT_VALUE - # * REMOTE - # * LOCAL - # * SHOW_PROGRESS - # * TIMEOUT_ARGS - # * TIMEOUT_MSG - # * USERPWD_ARGS - # * HTTP_HEADERS_ARGS - configure_file( - "${_ExternalProject_SELF_DIR}/ExternalProject-download.cmake.in" - "${script_filename}" - @ONLY - ) -endfunction() - -function(_ep_write_verifyfile_script script_filename LOCAL hash) - if("${hash}" MATCHES "${_ep_hash_regex}") - set(ALGO "${CMAKE_MATCH_1}") - string(TOLOWER "${CMAKE_MATCH_2}" EXPECT_VALUE) - else() - set(ALGO "") - set(EXPECT_VALUE "") - endif() - - # Used variables: - # * ALGO - # * EXPECT_VALUE - # * LOCAL - configure_file( - "${_ExternalProject_SELF_DIR}/ExternalProject-verify.cmake.in" - "${script_filename}" - @ONLY - ) -endfunction() - - -function(_ep_write_extractfile_script script_filename name filename directory) - set(args "") - - if(filename MATCHES "(\\.|=)(7z|tar\\.bz2|tar\\.gz|tar\\.xz|tbz2|tgz|txz|zip)$") - set(args xfz) - endif() - - if(filename MATCHES "(\\.|=)tar$") - set(args xf) - endif() - - if(args STREQUAL "") - message(SEND_ERROR "error: do not know how to extract '${filename}' -- known types are .7z, .tar, .tar.bz2, .tar.gz, .tar.xz, .tbz2, .tgz, .txz and .zip") - return() - endif() - - file(WRITE ${script_filename} -"# Make file names absolute: -# -get_filename_component(filename \"${filename}\" ABSOLUTE) -get_filename_component(directory \"${directory}\" ABSOLUTE) - -message(STATUS \"extracting... - src='\${filename}' - dst='\${directory}'\") - -if(NOT EXISTS \"\${filename}\") - message(FATAL_ERROR \"error: file to extract does not exist: '\${filename}'\") -endif() - -# Prepare a space for extracting: -# -set(i 1234) -while(EXISTS \"\${directory}/../ex-${name}\${i}\") - math(EXPR i \"\${i} + 1\") -endwhile() -set(ut_dir \"\${directory}/../ex-${name}\${i}\") -file(MAKE_DIRECTORY \"\${ut_dir}\") - -# Extract it: -# -message(STATUS \"extracting... [tar ${args}]\") -execute_process(COMMAND \${CMAKE_COMMAND} -E tar ${args} \${filename} - WORKING_DIRECTORY \${ut_dir} - RESULT_VARIABLE rv) - -if(NOT rv EQUAL 0) - message(STATUS \"extracting... [error clean up]\") - file(REMOVE_RECURSE \"\${ut_dir}\") - message(FATAL_ERROR \"error: extract of '\${filename}' failed\") -endif() - -# Analyze what came out of the tar file: -# -message(STATUS \"extracting... [analysis]\") -file(GLOB contents \"\${ut_dir}/*\") -list(REMOVE_ITEM contents \"\${ut_dir}/.DS_Store\") -list(LENGTH contents n) -if(NOT n EQUAL 1 OR NOT IS_DIRECTORY \"\${contents}\") - set(contents \"\${ut_dir}\") -endif() - -# Move \"the one\" directory to the final directory: -# -message(STATUS \"extracting... [rename]\") -file(REMOVE_RECURSE \${directory}) -get_filename_component(contents \${contents} ABSOLUTE) -file(RENAME \${contents} \${directory}) - -# Clean up: -# -message(STATUS \"extracting... [clean up]\") -file(REMOVE_RECURSE \"\${ut_dir}\") - -message(STATUS \"extracting... done\") -" -) - -endfunction() - - -function(_ep_set_directories name) - get_property(prefix TARGET ${name} PROPERTY _EP_PREFIX) - if(NOT prefix) - get_property(prefix DIRECTORY PROPERTY EP_PREFIX) - if(NOT prefix) - get_property(base DIRECTORY PROPERTY EP_BASE) - if(NOT base) - set(prefix "${name}-prefix") - endif() - endif() - endif() - if(prefix) - set(tmp_default "${prefix}/tmp") - set(download_default "${prefix}/src") - set(source_default "${prefix}/src/${name}") - set(binary_default "${prefix}/src/${name}-build") - set(stamp_default "${prefix}/src/${name}-stamp") - set(install_default "${prefix}") - else() - set(tmp_default "${base}/tmp/${name}") - set(download_default "${base}/Download/${name}") - set(source_default "${base}/Source/${name}") - set(binary_default "${base}/Build/${name}") - set(stamp_default "${base}/Stamp/${name}") - set(install_default "${base}/Install/${name}") - endif() - get_property(build_in_source TARGET ${name} PROPERTY _EP_BUILD_IN_SOURCE) - if(build_in_source) - get_property(have_binary_dir TARGET ${name} PROPERTY _EP_BINARY_DIR SET) - if(have_binary_dir) - message(FATAL_ERROR - "External project ${name} has both BINARY_DIR and BUILD_IN_SOURCE!") - endif() - endif() - set(top "${CMAKE_CURRENT_BINARY_DIR}") - - # Apply defaults and convert to absolute paths. - set(places stamp download source binary install tmp) - foreach(var ${places}) - string(TOUPPER "${var}" VAR) - get_property(${var}_dir TARGET ${name} PROPERTY _EP_${VAR}_DIR) - if(NOT ${var}_dir) - set(${var}_dir "${${var}_default}") - endif() - if(NOT IS_ABSOLUTE "${${var}_dir}") - get_filename_component(${var}_dir "${top}/${${var}_dir}" ABSOLUTE) - endif() - set_property(TARGET ${name} PROPERTY _EP_${VAR}_DIR "${${var}_dir}") - endforeach() - - # Special case for default log directory based on stamp directory. - get_property(log_dir TARGET ${name} PROPERTY _EP_LOG_DIR) - if(NOT log_dir) - get_property(log_dir TARGET ${name} PROPERTY _EP_STAMP_DIR) - endif() - if(NOT IS_ABSOLUTE "${log_dir}") - get_filename_component(log_dir "${top}/${log_dir}" ABSOLUTE) - endif() - set_property(TARGET ${name} PROPERTY _EP_LOG_DIR "${log_dir}") - - get_property(source_subdir TARGET ${name} PROPERTY _EP_SOURCE_SUBDIR) - if(NOT source_subdir) - set_property(TARGET ${name} PROPERTY _EP_SOURCE_SUBDIR "") - elseif(IS_ABSOLUTE "${source_subdir}") - message(FATAL_ERROR - "External project ${name} has non-relative SOURCE_SUBDIR!") - else() - # Prefix with a slash so that when appended to the source directory, it - # behaves as expected. - set_property(TARGET ${name} PROPERTY _EP_SOURCE_SUBDIR "/${source_subdir}") - endif() - if(build_in_source) - get_property(source_dir TARGET ${name} PROPERTY _EP_SOURCE_DIR) - if(source_subdir) - set_property(TARGET ${name} PROPERTY _EP_BINARY_DIR "${source_dir}/${source_subdir}") - else() - set_property(TARGET ${name} PROPERTY _EP_BINARY_DIR "${source_dir}") - endif() - endif() - - # Make the directories at CMake configure time *and* add a custom command - # to make them at build time. They need to exist at makefile generation - # time for Borland make and wmake so that CMake may generate makefiles - # with "cd C:\short\paths\with\no\spaces" commands in them. - # - # Additionally, the add_custom_command is still used in case somebody - # removes one of the necessary directories and tries to rebuild without - # re-running cmake. - foreach(var ${places}) - string(TOUPPER "${var}" VAR) - get_property(dir TARGET ${name} PROPERTY _EP_${VAR}_DIR) - file(MAKE_DIRECTORY "${dir}") - if(NOT EXISTS "${dir}") - message(FATAL_ERROR "dir '${dir}' does not exist after file(MAKE_DIRECTORY)") - endif() - endforeach() -endfunction() - - -# IMPORTANT: this MUST be a macro and not a function because of the -# in-place replacements that occur in each ${var} -# -macro(_ep_replace_location_tags target_name) - set(vars ${ARGN}) - foreach(var ${vars}) - if(${var}) - foreach(dir SOURCE_DIR SOURCE_SUBDIR BINARY_DIR INSTALL_DIR TMP_DIR DOWNLOAD_DIR DOWNLOADED_FILE LOG_DIR) - get_property(val TARGET ${target_name} PROPERTY _EP_${dir}) - string(REPLACE "<${dir}>" "${val}" ${var} "${${var}}") - endforeach() - endif() - endforeach() -endmacro() - - -function(_ep_command_line_to_initial_cache var args force) - set(script_initial_cache "") - set(regex "^([^:]+):([^=]+)=(.*)$") - set(setArg "") - set(forceArg "") - if(force) - set(forceArg "FORCE") - endif() - foreach(line ${args}) - if("${line}" MATCHES "^-D(.*)") - set(line "${CMAKE_MATCH_1}") - if(NOT "${setArg}" STREQUAL "") - # This is required to build up lists in variables, or complete an entry - string(APPEND setArg "${accumulator}\" CACHE ${type} \"Initial cache\" ${forceArg})") - string(APPEND script_initial_cache "\n${setArg}") - set(accumulator "") - set(setArg "") - endif() - if("${line}" MATCHES "${regex}") - set(name "${CMAKE_MATCH_1}") - set(type "${CMAKE_MATCH_2}") - set(value "${CMAKE_MATCH_3}") - set(setArg "set(${name} \"${value}") - else() - message(WARNING "Line '${line}' does not match regex. Ignoring.") - endif() - else() - # Assume this is a list to append to the last var - string(APPEND accumulator ";${line}") - endif() - endforeach() - # Catch the final line of the args - if(NOT "${setArg}" STREQUAL "") - string(APPEND setArg "${accumulator}\" CACHE ${type} \"Initial cache\" ${forceArg})") - string(APPEND script_initial_cache "\n${setArg}") - endif() - set(${var} ${script_initial_cache} PARENT_SCOPE) -endfunction() - - -function(_ep_write_initial_cache target_name script_filename script_initial_cache) - # Write out values into an initial cache, that will be passed to CMake with -C - # Replace location tags. - _ep_replace_location_tags(${target_name} script_initial_cache) - _ep_replace_location_tags(${target_name} script_filename) - # Replace list separators. - get_property(sep TARGET ${target_name} PROPERTY _EP_LIST_SEPARATOR) - if(sep AND script_initial_cache) - string(REPLACE "${sep}" ";" script_initial_cache "${script_initial_cache}") - endif() - # Write out the initial cache file to the location specified. - file(GENERATE OUTPUT "${script_filename}" CONTENT "${script_initial_cache}") -endfunction() - - -function(ExternalProject_Get_Property name) - foreach(var ${ARGN}) - string(TOUPPER "${var}" VAR) - get_property(is_set TARGET ${name} PROPERTY _EP_${VAR} SET) - if(NOT is_set) - message(FATAL_ERROR "External project \"${name}\" has no ${var}") - endif() - get_property(${var} TARGET ${name} PROPERTY _EP_${VAR}) - set(${var} "${${var}}" PARENT_SCOPE) - endforeach() -endfunction() - - -function(_ep_get_configure_command_id name cfg_cmd_id_var) - get_target_property(cmd ${name} _EP_CONFIGURE_COMMAND) - - if(cmd STREQUAL "") - # Explicit empty string means no configure step for this project - set(${cfg_cmd_id_var} "none" PARENT_SCOPE) - else() - if(NOT cmd) - # Default is "use cmake": - set(${cfg_cmd_id_var} "cmake" PARENT_SCOPE) - else() - # Otherwise we have to analyze the value: - if(cmd MATCHES "^[^;]*/configure") - set(${cfg_cmd_id_var} "configure" PARENT_SCOPE) - elseif(cmd MATCHES "^[^;]*/cmake" AND NOT cmd MATCHES ";-[PE];") - set(${cfg_cmd_id_var} "cmake" PARENT_SCOPE) - elseif(cmd MATCHES "config") - set(${cfg_cmd_id_var} "configure" PARENT_SCOPE) - else() - set(${cfg_cmd_id_var} "unknown:${cmd}" PARENT_SCOPE) - endif() - endif() - endif() -endfunction() - - -function(_ep_get_build_command name step cmd_var) - set(cmd "") - set(args) - _ep_get_configure_command_id(${name} cfg_cmd_id) - if(cfg_cmd_id STREQUAL "cmake") - # CMake project. Select build command based on generator. - get_target_property(cmake_generator ${name} _EP_CMAKE_GENERATOR) - if("${CMAKE_GENERATOR}" MATCHES "Make" AND - ("${cmake_generator}" MATCHES "Make" OR NOT cmake_generator)) - # The project uses the same Makefile generator. Use recursive make. - set(cmd "$(MAKE)") - if(step STREQUAL "INSTALL") - set(args install) - endif() - if("x${step}x" STREQUAL "xTESTx") - set(args test) - endif() - else() - # Drive the project with "cmake --build". - get_target_property(cmake_command ${name} _EP_CMAKE_COMMAND) - if(cmake_command) - set(cmd "${cmake_command}") - else() - set(cmd "${CMAKE_COMMAND}") - endif() - set(args --build ".") - get_property(_isMultiConfig GLOBAL PROPERTY GENERATOR_IS_MULTI_CONFIG) - if(_isMultiConfig) - if (CMAKE_CFG_INTDIR AND - NOT CMAKE_CFG_INTDIR STREQUAL "." AND - NOT CMAKE_CFG_INTDIR MATCHES "\\$") - # CMake 3.4 and below used the CMAKE_CFG_INTDIR placeholder value - # provided by multi-configuration generators. Some projects were - # taking advantage of that undocumented implementation detail to - # specify a specific configuration here. They should use - # BUILD_COMMAND to change the default command instead, but for - # compatibility honor the value. - set(config ${CMAKE_CFG_INTDIR}) - message(AUTHOR_WARNING "CMAKE_CFG_INTDIR should not be set by project code.\n" - "To get a non-default build command, use the BUILD_COMMAND option.") - else() - set(config $<CONFIG>) - endif() - list(APPEND args --config ${config}) - endif() - if(step STREQUAL "INSTALL") - list(APPEND args --target install) - endif() - # But for "TEST" drive the project with corresponding "ctest". - if("x${step}x" STREQUAL "xTESTx") - string(REGEX REPLACE "^(.*/)cmake([^/]*)$" "\\1ctest\\2" cmd "${cmd}") - set(args "") - if(_isMultiConfig) - list(APPEND args -C ${config}) - endif() - endif() - endif() - else() - # Non-CMake project. Guess "make" and "make install" and "make test". - if("${CMAKE_GENERATOR}" MATCHES "Makefiles") - # Try to get the parallel arguments - set(cmd "$(MAKE)") - else() - set(cmd "make") - endif() - if(step STREQUAL "INSTALL") - set(args install) - endif() - if("x${step}x" STREQUAL "xTESTx") - set(args test) - endif() - endif() - - # Use user-specified arguments instead of default arguments, if any. - get_property(have_args TARGET ${name} PROPERTY _EP_${step}_ARGS SET) - if(have_args) - get_target_property(args ${name} _EP_${step}_ARGS) - endif() - - if(NOT "${args}" STREQUAL "") - # args could have empty items, so we must quote it to prevent them - # from being silently removed - list(APPEND cmd "${args}") - endif() - set(${cmd_var} "${cmd}" PARENT_SCOPE) -endfunction() - -function(_ep_write_log_script name step cmd_var) - ExternalProject_Get_Property(${name} log_dir) - ExternalProject_Get_Property(${name} stamp_dir) - set(command "${${cmd_var}}") - - set(make "") - set(code_cygpath_make "") - if(command MATCHES "^\\$\\(MAKE\\)") - # GNU make recognizes the string "$(MAKE)" as recursive make, so - # ensure that it appears directly in the makefile. - string(REGEX REPLACE "^\\$\\(MAKE\\)" "\${make}" command "${command}") - set(make "-Dmake=$(MAKE)") - - if(WIN32 AND NOT CYGWIN) - set(code_cygpath_make " -if(\${make} MATCHES \"^/\") - execute_process( - COMMAND cygpath -w \${make} - OUTPUT_VARIABLE cygpath_make - ERROR_VARIABLE cygpath_make - RESULT_VARIABLE cygpath_error - OUTPUT_STRIP_TRAILING_WHITESPACE - ) - if(NOT cygpath_error) - set(make \${cygpath_make}) - endif() -endif() -") - endif() - endif() - - set(config "") - if("${CMAKE_CFG_INTDIR}" MATCHES "^\\$") - string(REPLACE "${CMAKE_CFG_INTDIR}" "\${config}" command "${command}") - set(config "-Dconfig=${CMAKE_CFG_INTDIR}") - endif() - - # Wrap multiple 'COMMAND' lines up into a second-level wrapper - # script so all output can be sent to one log file. - if(command MATCHES "(^|;)COMMAND;") - set(code_execute_process " -${code_cygpath_make} -execute_process(COMMAND \${command} RESULT_VARIABLE result) -if(result) - set(msg \"Command failed (\${result}):\\n\") - foreach(arg IN LISTS command) - set(msg \"\${msg} '\${arg}'\") - endforeach() - message(FATAL_ERROR \"\${msg}\") -endif() -") - set(code "") - set(cmd "") - set(sep "") - foreach(arg IN LISTS command) - if("x${arg}" STREQUAL "xCOMMAND") - if(NOT "x${cmd}" STREQUAL "x") - string(APPEND code "set(command \"${cmd}\")${code_execute_process}") - endif() - set(cmd "") - set(sep "") - else() - string(APPEND cmd "${sep}${arg}") - set(sep ";") - endif() - endforeach() - string(APPEND code "set(command \"${cmd}\")${code_execute_process}") - file(GENERATE OUTPUT "${stamp_dir}/${name}-${step}-$<CONFIG>-impl.cmake" CONTENT "${code}") - set(command ${CMAKE_COMMAND} "-Dmake=\${make}" "-Dconfig=\${config}" -P ${stamp_dir}/${name}-${step}-$<CONFIG>-impl.cmake) - endif() - - # Wrap the command in a script to log output to files. - set(script ${stamp_dir}/${name}-${step}-$<CONFIG>.cmake) - set(logbase ${log_dir}/${name}-${step}) - get_property(log_merged TARGET ${name} PROPERTY _EP_LOG_MERGED_STDOUTERR) - get_property(log_output_on_failure TARGET ${name} PROPERTY _EP_LOG_OUTPUT_ON_FAILURE) - if (log_merged) - set(stdout_log "${logbase}.log") - set(stderr_log "${logbase}.log") - else() - set(stdout_log "${logbase}-out.log") - set(stderr_log "${logbase}-err.log") - endif() - set(code " -cmake_minimum_required(VERSION 3.15) -${code_cygpath_make} -set(command \"${command}\") -set(log_merged \"${log_merged}\") -set(log_output_on_failure \"${log_output_on_failure}\") -set(stdout_log \"${stdout_log}\") -set(stderr_log \"${stderr_log}\") -execute_process( - COMMAND \${command} - RESULT_VARIABLE result - OUTPUT_FILE \"\${stdout_log}\" - ERROR_FILE \"\${stderr_log}\" - ) -macro(read_up_to_max_size log_file output_var) - file(SIZE \${log_file} determined_size) - set(max_size 10240) - if (determined_size GREATER max_size) - math(EXPR seek_position \"\${determined_size} - \${max_size}\") - file(READ \${log_file} \${output_var} OFFSET \${seek_position}) - set(\${output_var} \"...skipping to end...\\n\${\${output_var}}\") - else() - file(READ \${log_file} \${output_var}) - endif() -endmacro() -if(result) - set(msg \"Command failed: \${result}\\n\") - foreach(arg IN LISTS command) - set(msg \"\${msg} '\${arg}'\") - endforeach() - if (\${log_merged}) - set(msg \"\${msg}\\nSee also\\n \${stderr_log}\") - else() - set(msg \"\${msg}\\nSee also\\n ${logbase}-*.log\") - endif() - if (\${log_output_on_failure}) - message(SEND_ERROR \"\${msg}\") - if (\${log_merged}) - read_up_to_max_size(\"\${stderr_log}\" error_log_contents) - message(STATUS \"Log output is:\\n\${error_log_contents}\") - else() - read_up_to_max_size(\"\${stdout_log}\" out_log_contents) - read_up_to_max_size(\"\${stderr_log}\" err_log_contents) - message(STATUS \"stdout output is:\\n\${out_log_contents}\") - message(STATUS \"stderr output is:\\n\${err_log_contents}\") - endif() - message(FATAL_ERROR \"Stopping after outputting logs.\") - else() - message(FATAL_ERROR \"\${msg}\") - endif() -else() - set(msg \"${name} ${step} command succeeded. See also ${logbase}-*.log\") - message(STATUS \"\${msg}\") -endif() -") - file(GENERATE OUTPUT "${script}" CONTENT "${code}") - set(command ${CMAKE_COMMAND} ${make} ${config} -P ${script}) - set(${cmd_var} "${command}" PARENT_SCOPE) -endfunction() - -# This module used to use "/${CMAKE_CFG_INTDIR}" directly and produced -# makefiles with "/./" in paths for custom command dependencies. Which -# resulted in problems with parallel make -j invocations. -# -# This function was added so that the suffix (search below for ${cfgdir}) is -# only set to "/${CMAKE_CFG_INTDIR}" when ${CMAKE_CFG_INTDIR} is not going to -# be "." (multi-configuration build systems like Visual Studio and Xcode...) -# -function(_ep_get_configuration_subdir_suffix suffix_var) - set(suffix "") - get_property(_isMultiConfig GLOBAL PROPERTY GENERATOR_IS_MULTI_CONFIG) - if(_isMultiConfig) - set(suffix "/${CMAKE_CFG_INTDIR}") - endif() - set(${suffix_var} "${suffix}" PARENT_SCOPE) -endfunction() - - -function(_ep_get_step_stampfile name step stampfile_var) - ExternalProject_Get_Property(${name} stamp_dir) - - _ep_get_configuration_subdir_suffix(cfgdir) - set(stampfile "${stamp_dir}${cfgdir}/${name}-${step}") - - set(${stampfile_var} "${stampfile}" PARENT_SCOPE) -endfunction() - - -function(_ep_get_complete_stampfile name stampfile_var) - set(cmf_dir ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles) - _ep_get_configuration_subdir_suffix(cfgdir) - set(stampfile "${cmf_dir}${cfgdir}/${name}-complete") - - set(${stampfile_var} ${stampfile} PARENT_SCOPE) -endfunction() - - -function(ExternalProject_Add_StepTargets name) - set(steps ${ARGN}) - if(ARGC GREATER 1 AND "${ARGV1}" STREQUAL "NO_DEPENDS") - set(no_deps 1) - list(REMOVE_AT steps 0) - endif() - foreach(step ${steps}) - if(no_deps AND "${step}" MATCHES "^(configure|build|install|test)$") - message(AUTHOR_WARNING "Using NO_DEPENDS for \"${step}\" step might break parallel builds") - endif() - _ep_get_step_stampfile(${name} ${step} stamp_file) - add_custom_target(${name}-${step} - DEPENDS ${stamp_file}) - set_property(TARGET ${name}-${step} PROPERTY _EP_IS_EXTERNAL_PROJECT_STEP 1) - set_property(TARGET ${name}-${step} PROPERTY LABELS ${name}) - set_property(TARGET ${name}-${step} PROPERTY FOLDER "ExternalProjectTargets/${name}") - - # Depend on other external projects (target-level). - if(NOT no_deps) - get_property(deps TARGET ${name} PROPERTY _EP_DEPENDS) - foreach(arg IN LISTS deps) - add_dependencies(${name}-${step} ${arg}) - endforeach() - endif() - endforeach() -endfunction() - - -function(ExternalProject_Add_Step name step) - _ep_get_complete_stampfile(${name} complete_stamp_file) - _ep_get_step_stampfile(${name} ${step} stamp_file) - - _ep_parse_arguments(ExternalProject_Add_Step - ${name} _EP_${step}_ "${ARGN}") - - get_property(exclude_from_main TARGET ${name} PROPERTY _EP_${step}_EXCLUDE_FROM_MAIN) - if(NOT exclude_from_main) - add_custom_command(APPEND - OUTPUT ${complete_stamp_file} - DEPENDS ${stamp_file} - ) - endif() - - # Steps depending on this step. - get_property(dependers TARGET ${name} PROPERTY _EP_${step}_DEPENDERS) - foreach(depender IN LISTS dependers) - _ep_get_step_stampfile(${name} ${depender} depender_stamp_file) - add_custom_command(APPEND - OUTPUT ${depender_stamp_file} - DEPENDS ${stamp_file} - ) - endforeach() - - # Dependencies on files. - get_property(depends TARGET ${name} PROPERTY _EP_${step}_DEPENDS) - - # Byproducts of the step. - get_property(byproducts TARGET ${name} PROPERTY _EP_${step}_BYPRODUCTS) - - # Dependencies on steps. - get_property(dependees TARGET ${name} PROPERTY _EP_${step}_DEPENDEES) - foreach(dependee IN LISTS dependees) - _ep_get_step_stampfile(${name} ${dependee} dependee_stamp_file) - list(APPEND depends ${dependee_stamp_file}) - endforeach() - - # The command to run. - get_property(command TARGET ${name} PROPERTY _EP_${step}_COMMAND) - if(command) - set(comment "Performing ${step} step for '${name}'") - else() - set(comment "No ${step} step for '${name}'") - endif() - get_property(work_dir TARGET ${name} PROPERTY _EP_${step}_WORKING_DIRECTORY) - - # Replace list separators. - get_property(sep TARGET ${name} PROPERTY _EP_LIST_SEPARATOR) - if(sep AND command) - string(REPLACE "${sep}" "\\;" command "${command}") - endif() - - # Replace location tags. - _ep_replace_location_tags(${name} comment command work_dir byproducts) - - # Custom comment? - get_property(comment_set TARGET ${name} PROPERTY _EP_${step}_COMMENT SET) - if(comment_set) - get_property(comment TARGET ${name} PROPERTY _EP_${step}_COMMENT) - endif() - - # Uses terminal? - get_property(uses_terminal TARGET ${name} PROPERTY _EP_${step}_USES_TERMINAL) - if(uses_terminal) - set(uses_terminal USES_TERMINAL) - else() - set(uses_terminal "") - endif() - - # Run every time? - get_property(always TARGET ${name} PROPERTY _EP_${step}_ALWAYS) - if(always) - set_property(SOURCE ${stamp_file} PROPERTY SYMBOLIC 1) - set(touch) - # Remove any existing stamp in case the option changed in an existing tree. - get_property(_isMultiConfig GLOBAL PROPERTY GENERATOR_IS_MULTI_CONFIG) - if(_isMultiConfig) - foreach(cfg ${CMAKE_CONFIGURATION_TYPES}) - string(REPLACE "/${CMAKE_CFG_INTDIR}" "/${cfg}" stamp_file_config "${stamp_file}") - file(REMOVE ${stamp_file_config}) - endforeach() - else() - file(REMOVE ${stamp_file}) - endif() - else() - set(touch ${CMAKE_COMMAND} -E touch ${stamp_file}) - endif() - - # Wrap with log script? - get_property(log TARGET ${name} PROPERTY _EP_${step}_LOG) - if(command AND log) - _ep_write_log_script(${name} ${step} command) - endif() - - if("${command}" STREQUAL "") - # Some generators (i.e. Xcode) will not generate a file level target - # if no command is set, and therefore the dependencies on this - # target will be broken. - # The empty command is replaced by an echo command here in order to - # avoid this issue. - set(command ${CMAKE_COMMAND} -E echo_append) - endif() - - set(__cmdQuoted) - foreach(__item IN LISTS command) - string(APPEND __cmdQuoted " [==[${__item}]==]") - endforeach() - cmake_language(EVAL CODE " - add_custom_command( - OUTPUT \${stamp_file} - BYPRODUCTS \${byproducts} - COMMENT \${comment} - COMMAND ${__cmdQuoted} - COMMAND \${touch} - DEPENDS \${depends} - WORKING_DIRECTORY \${work_dir} - VERBATIM - ${uses_terminal} - )" - ) - set_property(TARGET ${name} APPEND PROPERTY _EP_STEPS ${step}) - - # Add custom "step target"? - get_property(step_targets TARGET ${name} PROPERTY _EP_STEP_TARGETS) - if(NOT step_targets) - get_property(step_targets DIRECTORY PROPERTY EP_STEP_TARGETS) - endif() - foreach(st ${step_targets}) - if("${st}" STREQUAL "${step}") - ExternalProject_Add_StepTargets(${name} ${step}) - break() - endif() - endforeach() - - get_property(independent_step_targets TARGET ${name} PROPERTY _EP_INDEPENDENT_STEP_TARGETS) - if(NOT independent_step_targets) - get_property(independent_step_targets DIRECTORY PROPERTY EP_INDEPENDENT_STEP_TARGETS) - endif() - foreach(st ${independent_step_targets}) - if("${st}" STREQUAL "${step}") - ExternalProject_Add_StepTargets(${name} NO_DEPENDS ${step}) - break() - endif() - endforeach() -endfunction() - - -function(ExternalProject_Add_StepDependencies name step) - set(dependencies ${ARGN}) - - # Sanity checks on "name" and "step". - if(NOT TARGET ${name}) - message(FATAL_ERROR "Cannot find target \"${name}\". Perhaps it has not yet been created using ExternalProject_Add.") - endif() - - get_property(type TARGET ${name} PROPERTY TYPE) - if(NOT type STREQUAL "UTILITY") - message(FATAL_ERROR "Target \"${name}\" was not generated by ExternalProject_Add.") - endif() - - get_property(is_ep TARGET ${name} PROPERTY _EP_IS_EXTERNAL_PROJECT) - if(NOT is_ep) - message(FATAL_ERROR "Target \"${name}\" was not generated by ExternalProject_Add.") - endif() - - get_property(steps TARGET ${name} PROPERTY _EP_STEPS) - list(FIND steps ${step} is_step) - if(is_step LESS 0) - message(FATAL_ERROR "External project \"${name}\" does not have a step \"${step}\".") - endif() - - if(TARGET ${name}-${step}) - get_property(type TARGET ${name}-${step} PROPERTY TYPE) - if(NOT type STREQUAL "UTILITY") - message(FATAL_ERROR "Target \"${name}-${step}\" was not generated by ExternalProject_Add_StepTargets.") - endif() - get_property(is_ep_step TARGET ${name}-${step} PROPERTY _EP_IS_EXTERNAL_PROJECT_STEP) - if(NOT is_ep_step) - message(FATAL_ERROR "Target \"${name}-${step}\" was not generated by ExternalProject_Add_StepTargets.") - endif() - endif() - - # Always add file-level dependency, but add target-level dependency - # only if the target exists for that step. - _ep_get_step_stampfile(${name} ${step} stamp_file) - foreach(dep ${dependencies}) - add_custom_command(APPEND - OUTPUT ${stamp_file} - DEPENDS ${dep}) - if(TARGET ${name}-${step}) - foreach(dep ${dependencies}) - add_dependencies(${name}-${step} ${dep}) - endforeach() - endif() - endforeach() - -endfunction() - - -function(_ep_add_mkdir_command name) - ExternalProject_Get_Property(${name} - source_dir binary_dir install_dir stamp_dir download_dir tmp_dir log_dir) - - _ep_get_configuration_subdir_suffix(cfgdir) - - ExternalProject_Add_Step(${name} mkdir - COMMENT "Creating directories for '${name}'" - COMMAND ${CMAKE_COMMAND} -E make_directory ${source_dir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${binary_dir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${install_dir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${tmp_dir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${stamp_dir}${cfgdir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${download_dir} - COMMAND ${CMAKE_COMMAND} -E make_directory ${log_dir} - ) -endfunction() - - -function(_ep_is_dir_empty dir empty_var) - file(GLOB gr "${dir}/*") - if("${gr}" STREQUAL "") - set(${empty_var} 1 PARENT_SCOPE) - else() - set(${empty_var} 0 PARENT_SCOPE) - endif() -endfunction() - -function(_ep_get_git_submodules_recurse git_submodules_recurse) - # Checks for GIT_SUBMODULES_RECURSE property - # Default is ON, which sets git_submodules_recurse output variable to "--recursive" - # Otherwise, the output variable is set to an empty value "" - get_property(git_submodules_recurse_set TARGET ${name} PROPERTY _EP_GIT_SUBMODULES_RECURSE SET) - if(NOT git_submodules_recurse_set) - set(recurseFlag "--recursive") - else() - get_property(git_submodules_recurse_value TARGET ${name} PROPERTY _EP_GIT_SUBMODULES_RECURSE) - if(git_submodules_recurse_value) - set(recurseFlag "--recursive") - else() - set(recurseFlag "") - endif() - endif() - set(${git_submodules_recurse} "${recurseFlag}" PARENT_SCOPE) - - # The git submodule update '--recursive' flag requires git >= v1.6.5 - if(recurseFlag AND GIT_VERSION_STRING VERSION_LESS 1.6.5) - message(FATAL_ERROR "error: git version 1.6.5 or later required for --recursive flag with 'git submodule ...': GIT_VERSION_STRING='${GIT_VERSION_STRING}'") - endif() -endfunction() - - -function(_ep_add_download_command name) - ExternalProject_Get_Property(${name} source_dir stamp_dir download_dir tmp_dir) - - get_property(cmd_set TARGET ${name} PROPERTY _EP_DOWNLOAD_COMMAND SET) - get_property(cmd TARGET ${name} PROPERTY _EP_DOWNLOAD_COMMAND) - get_property(cvs_repository TARGET ${name} PROPERTY _EP_CVS_REPOSITORY) - get_property(svn_repository TARGET ${name} PROPERTY _EP_SVN_REPOSITORY) - get_property(git_repository TARGET ${name} PROPERTY _EP_GIT_REPOSITORY) - get_property(hg_repository TARGET ${name} PROPERTY _EP_HG_REPOSITORY ) - get_property(url TARGET ${name} PROPERTY _EP_URL) - get_property(fname TARGET ${name} PROPERTY _EP_DOWNLOAD_NAME) - - # TODO: Perhaps file:// should be copied to download dir before extraction. - string(REGEX REPLACE "file://" "" url "${url}") - - set(depends) - set(comment) - set(work_dir) - - if(cmd_set) - set(work_dir ${download_dir}) - elseif(cvs_repository) - find_package(CVS QUIET) - if(NOT CVS_EXECUTABLE) - message(FATAL_ERROR "error: could not find cvs for checkout of ${name}") - endif() - - get_target_property(cvs_module ${name} _EP_CVS_MODULE) - if(NOT cvs_module) - message(FATAL_ERROR "error: no CVS_MODULE") - endif() - - get_property(cvs_tag TARGET ${name} PROPERTY _EP_CVS_TAG) - - set(repository ${cvs_repository}) - set(module ${cvs_module}) - set(tag ${cvs_tag}) - configure_file( - "${CMAKE_ROOT}/Modules/RepositoryInfo.txt.in" - "${stamp_dir}/${name}-cvsinfo.txt" - @ONLY - ) - - get_filename_component(src_name "${source_dir}" NAME) - get_filename_component(work_dir "${source_dir}" PATH) - set(comment "Performing download step (CVS checkout) for '${name}'") - set(cmd ${CVS_EXECUTABLE} -d ${cvs_repository} -q co ${cvs_tag} -d ${src_name} ${cvs_module}) - list(APPEND depends ${stamp_dir}/${name}-cvsinfo.txt) - elseif(svn_repository) - find_package(Subversion QUIET) - if(NOT Subversion_SVN_EXECUTABLE) - message(FATAL_ERROR "error: could not find svn for checkout of ${name}") - endif() - - get_property(svn_revision TARGET ${name} PROPERTY _EP_SVN_REVISION) - get_property(svn_username TARGET ${name} PROPERTY _EP_SVN_USERNAME) - get_property(svn_password TARGET ${name} PROPERTY _EP_SVN_PASSWORD) - get_property(svn_trust_cert TARGET ${name} PROPERTY _EP_SVN_TRUST_CERT) - - set(repository "${svn_repository} user=${svn_username} password=${svn_password}") - set(module) - set(tag ${svn_revision}) - configure_file( - "${CMAKE_ROOT}/Modules/RepositoryInfo.txt.in" - "${stamp_dir}/${name}-svninfo.txt" - @ONLY - ) - - get_filename_component(src_name "${source_dir}" NAME) - get_filename_component(work_dir "${source_dir}" PATH) - set(comment "Performing download step (SVN checkout) for '${name}'") - set(svn_user_pw_args "") - if(DEFINED svn_username) - set(svn_user_pw_args ${svn_user_pw_args} "--username=${svn_username}") - endif() - if(DEFINED svn_password) - set(svn_user_pw_args ${svn_user_pw_args} "--password=${svn_password}") - endif() - if(svn_trust_cert) - set(svn_trust_cert_args --trust-server-cert) - endif() - set(cmd ${Subversion_SVN_EXECUTABLE} co ${svn_repository} ${svn_revision} - --non-interactive ${svn_trust_cert_args} ${svn_user_pw_args} ${src_name}) - list(APPEND depends ${stamp_dir}/${name}-svninfo.txt) - elseif(git_repository) - unset(CMAKE_MODULE_PATH) # Use CMake builtin find module - find_package(Git QUIET) - if(NOT GIT_EXECUTABLE) - message(FATAL_ERROR "error: could not find git for clone of ${name}") - endif() - - _ep_get_git_submodules_recurse(git_submodules_recurse) - - get_property(git_tag TARGET ${name} PROPERTY _EP_GIT_TAG) - if(NOT git_tag) - set(git_tag "master") - endif() - - set(git_init_submodules TRUE) - get_property(git_submodules_set TARGET ${name} PROPERTY _EP_GIT_SUBMODULES SET) - if(git_submodules_set) - get_property(git_submodules TARGET ${name} PROPERTY _EP_GIT_SUBMODULES) - if(git_submodules STREQUAL "" AND _EP_CMP0097 STREQUAL "NEW") - set(git_init_submodules FALSE) - endif() - endif() - - get_property(git_remote_name TARGET ${name} PROPERTY _EP_GIT_REMOTE_NAME) - if(NOT git_remote_name) - set(git_remote_name "origin") - endif() - - get_property(tls_verify TARGET ${name} PROPERTY _EP_TLS_VERIFY) - if("x${tls_verify}" STREQUAL "x" AND DEFINED CMAKE_TLS_VERIFY) - set(tls_verify "${CMAKE_TLS_VERIFY}") - endif() - get_property(git_shallow TARGET ${name} PROPERTY _EP_GIT_SHALLOW) - get_property(git_progress TARGET ${name} PROPERTY _EP_GIT_PROGRESS) - get_property(git_config TARGET ${name} PROPERTY _EP_GIT_CONFIG) - - # For the download step, and the git clone operation, only the repository - # should be recorded in a configured RepositoryInfo file. If the repo - # changes, the clone script should be run again. But if only the tag - # changes, avoid running the clone script again. Let the 'always' running - # update step checkout the new tag. - # - set(repository ${git_repository}) - set(module) - set(tag ${git_remote_name}) - configure_file( - "${CMAKE_ROOT}/Modules/RepositoryInfo.txt.in" - "${stamp_dir}/${name}-gitinfo.txt" - @ONLY - ) - - get_filename_component(src_name "${source_dir}" NAME) - get_filename_component(work_dir "${source_dir}" PATH) - - # Since git clone doesn't succeed if the non-empty source_dir exists, - # create a cmake script to invoke as download command. - # The script will delete the source directory and then call git clone. - # - _ep_write_gitclone_script(${tmp_dir}/${name}-gitclone.cmake ${source_dir} - ${GIT_EXECUTABLE} ${git_repository} ${git_tag} ${git_remote_name} ${git_init_submodules} "${git_submodules_recurse}" "${git_submodules}" "${git_shallow}" "${git_progress}" "${git_config}" ${src_name} ${work_dir} - ${stamp_dir}/${name}-gitinfo.txt ${stamp_dir}/${name}-gitclone-lastrun.txt "${tls_verify}" - ) - set(comment "Performing download step (git clone) for '${name}'") - set(cmd ${CMAKE_COMMAND} -P ${tmp_dir}/${name}-gitclone.cmake) - list(APPEND depends ${stamp_dir}/${name}-gitinfo.txt) - elseif(hg_repository) - find_package(Hg QUIET) - if(NOT HG_EXECUTABLE) - message(FATAL_ERROR "error: could not find hg for clone of ${name}") - endif() - - get_property(hg_tag TARGET ${name} PROPERTY _EP_HG_TAG) - if(NOT hg_tag) - set(hg_tag "tip") - endif() - - # For the download step, and the hg clone operation, only the repository - # should be recorded in a configured RepositoryInfo file. If the repo - # changes, the clone script should be run again. But if only the tag - # changes, avoid running the clone script again. Let the 'always' running - # update step checkout the new tag. - # - set(repository ${hg_repository}) - set(module) - set(tag) - configure_file( - "${CMAKE_ROOT}/Modules/RepositoryInfo.txt.in" - "${stamp_dir}/${name}-hginfo.txt" - @ONLY - ) - - get_filename_component(src_name "${source_dir}" NAME) - get_filename_component(work_dir "${source_dir}" PATH) - - # Since hg clone doesn't succeed if the non-empty source_dir exists, - # create a cmake script to invoke as download command. - # The script will delete the source directory and then call hg clone. - # - _ep_write_hgclone_script(${tmp_dir}/${name}-hgclone.cmake ${source_dir} - ${HG_EXECUTABLE} ${hg_repository} ${hg_tag} ${src_name} ${work_dir} - ${stamp_dir}/${name}-hginfo.txt ${stamp_dir}/${name}-hgclone-lastrun.txt - ) - set(comment "Performing download step (hg clone) for '${name}'") - set(cmd ${CMAKE_COMMAND} -P ${tmp_dir}/${name}-hgclone.cmake) - list(APPEND depends ${stamp_dir}/${name}-hginfo.txt) - elseif(url) - get_filename_component(work_dir "${source_dir}" PATH) - get_property(hash TARGET ${name} PROPERTY _EP_URL_HASH) - if(hash AND NOT "${hash}" MATCHES "${_ep_hash_regex}") - message(FATAL_ERROR "URL_HASH is set to\n ${hash}\n" - "but must be ALGO=value where ALGO is\n ${_ep_hash_algos}\n" - "and value is a hex string.") - endif() - get_property(md5 TARGET ${name} PROPERTY _EP_URL_MD5) - if(md5 AND NOT "MD5=${md5}" MATCHES "${_ep_hash_regex}") - message(FATAL_ERROR "URL_MD5 is set to\n ${md5}\nbut must be a hex string.") - endif() - if(md5 AND NOT hash) - set(hash "MD5=${md5}") - endif() - set(repository "external project URL") - set(module "${url}") - set(tag "${hash}") - configure_file( - "${CMAKE_ROOT}/Modules/RepositoryInfo.txt.in" - "${stamp_dir}/${name}-urlinfo.txt" - @ONLY - ) - list(APPEND depends ${stamp_dir}/${name}-urlinfo.txt) - - list(LENGTH url url_list_length) - if(NOT "${url_list_length}" STREQUAL "1") - foreach(entry ${url}) - if(NOT "${entry}" MATCHES "^[a-z]+://") - message(FATAL_ERROR "At least one entry of URL is a path (invalid in a list)") - endif() - endforeach() - if("x${fname}" STREQUAL "x") - list(GET url 0 fname) - endif() - endif() - - if(IS_DIRECTORY "${url}") - get_filename_component(abs_dir "${url}" ABSOLUTE) - set(comment "Performing download step (DIR copy) for '${name}'") - set(cmd ${CMAKE_COMMAND} -E rm -rf ${source_dir} - COMMAND ${CMAKE_COMMAND} -E copy_directory ${abs_dir} ${source_dir}) - else() - get_property(no_extract TARGET "${name}" PROPERTY _EP_DOWNLOAD_NO_EXTRACT) - if("${url}" MATCHES "^[a-z]+://") - # TODO: Should download and extraction be different steps? - if("x${fname}" STREQUAL "x") - set(fname "${url}") - endif() - if("${fname}" MATCHES [[([^/\?#]+(\.|=)(7z|tar|tar\.bz2|tar\.gz|tar\.xz|tbz2|tgz|txz|zip))([/?#].*)?$]]) - set(fname "${CMAKE_MATCH_1}") - elseif(no_extract) - get_filename_component(fname "${fname}" NAME) - else() - # Fall back to a default file name. The actual file name does not - # matter because it is used only internally and our extraction tool - # inspects the file content directly. If it turns out the wrong URL - # was given that will be revealed during the build which is an easier - # place for users to diagnose than an error here anyway. - set(fname "archive.tar") - endif() - string(REPLACE ";" "-" fname "${fname}") - set(file ${download_dir}/${fname}) - get_property(timeout TARGET ${name} PROPERTY _EP_TIMEOUT) - get_property(no_progress TARGET ${name} PROPERTY _EP_DOWNLOAD_NO_PROGRESS) - get_property(tls_verify TARGET ${name} PROPERTY _EP_TLS_VERIFY) - get_property(tls_cainfo TARGET ${name} PROPERTY _EP_TLS_CAINFO) - get_property(netrc TARGET ${name} PROPERTY _EP_NETRC) - get_property(netrc_file TARGET ${name} PROPERTY _EP_NETRC_FILE) - get_property(http_username TARGET ${name} PROPERTY _EP_HTTP_USERNAME) - get_property(http_password TARGET ${name} PROPERTY _EP_HTTP_PASSWORD) - get_property(http_headers TARGET ${name} PROPERTY _EP_HTTP_HEADER) - set(download_script "${stamp_dir}/download-${name}.cmake") - _ep_write_downloadfile_script("${download_script}" "${url}" "${file}" "${timeout}" "${no_progress}" "${hash}" "${tls_verify}" "${tls_cainfo}" "${http_username}:${http_password}" "${http_headers}" "${netrc}" "${netrc_file}") - set(cmd ${CMAKE_COMMAND} -P "${download_script}" - COMMAND) - if (no_extract) - set(steps "download and verify") - else () - set(steps "download, verify and extract") - endif () - set(comment "Performing download step (${steps}) for '${name}'") - file(WRITE "${stamp_dir}/verify-${name}.cmake" "") # already verified by 'download_script' - else() - set(file "${url}") - if (no_extract) - set(steps "verify") - else () - set(steps "verify and extract") - endif () - set(comment "Performing download step (${steps}) for '${name}'") - _ep_write_verifyfile_script("${stamp_dir}/verify-${name}.cmake" "${file}" "${hash}") - endif() - list(APPEND cmd ${CMAKE_COMMAND} -P ${stamp_dir}/verify-${name}.cmake) - if (NOT no_extract) - _ep_write_extractfile_script("${stamp_dir}/extract-${name}.cmake" "${name}" "${file}" "${source_dir}") - list(APPEND cmd COMMAND ${CMAKE_COMMAND} -P ${stamp_dir}/extract-${name}.cmake) - else () - set_property(TARGET ${name} PROPERTY _EP_DOWNLOADED_FILE ${file}) - endif () - endif() - else() - _ep_is_dir_empty("${source_dir}" empty) - if(${empty}) - message(SEND_ERROR - "No download info given for '${name}' and its source directory:\n" - " ${source_dir}\n" - "is not an existing non-empty directory. Please specify one of:\n" - " * SOURCE_DIR with an existing non-empty directory\n" - " * DOWNLOAD_COMMAND\n" - " * URL\n" - " * GIT_REPOSITORY\n" - " * SVN_REPOSITORY\n" - " * HG_REPOSITORY\n" - " * CVS_REPOSITORY and CVS_MODULE" - ) - endif() - endif() - - get_property(log TARGET ${name} PROPERTY _EP_LOG_DOWNLOAD) - if(log) - set(log LOG 1) - else() - set(log "") - endif() - - get_property(uses_terminal TARGET ${name} PROPERTY - _EP_USES_TERMINAL_DOWNLOAD) - if(uses_terminal) - set(uses_terminal USES_TERMINAL 1) - else() - set(uses_terminal "") - endif() - - set(__cmdQuoted) - foreach(__item IN LISTS cmd) - string(APPEND __cmdQuoted " [==[${__item}]==]") - endforeach() - cmake_language(EVAL CODE " - ExternalProject_Add_Step(\${name} download - COMMENT \${comment} - COMMAND ${__cmdQuoted} - WORKING_DIRECTORY \${work_dir} - DEPENDS \${depends} - DEPENDEES mkdir - ${log} - ${uses_terminal} - )" - ) -endfunction() - -function(_ep_get_update_disconnected var name) - get_property(update_disconnected_set TARGET ${name} PROPERTY _EP_UPDATE_DISCONNECTED SET) - if(update_disconnected_set) - get_property(update_disconnected TARGET ${name} PROPERTY _EP_UPDATE_DISCONNECTED) - else() - get_property(update_disconnected DIRECTORY PROPERTY EP_UPDATE_DISCONNECTED) - endif() - set(${var} "${update_disconnected}" PARENT_SCOPE) -endfunction() - -function(_ep_add_update_command name) - ExternalProject_Get_Property(${name} source_dir tmp_dir) - - get_property(cmd_set TARGET ${name} PROPERTY _EP_UPDATE_COMMAND SET) - get_property(cmd TARGET ${name} PROPERTY _EP_UPDATE_COMMAND) - get_property(cvs_repository TARGET ${name} PROPERTY _EP_CVS_REPOSITORY) - get_property(svn_repository TARGET ${name} PROPERTY _EP_SVN_REPOSITORY) - get_property(git_repository TARGET ${name} PROPERTY _EP_GIT_REPOSITORY) - get_property(hg_repository TARGET ${name} PROPERTY _EP_HG_REPOSITORY ) - - _ep_get_update_disconnected(update_disconnected ${name}) - - set(work_dir) - set(comment) - set(always) - - if(cmd_set) - set(work_dir ${source_dir}) - if(NOT "x${cmd}" STREQUAL "x") - set(always 1) - endif() - elseif(cvs_repository) - if(NOT CVS_EXECUTABLE) - message(FATAL_ERROR "error: could not find cvs for update of ${name}") - endif() - set(work_dir ${source_dir}) - set(comment "Performing update step (CVS update) for '${name}'") - get_property(cvs_tag TARGET ${name} PROPERTY _EP_CVS_TAG) - set(cmd ${CVS_EXECUTABLE} -d ${cvs_repository} -q up -dP ${cvs_tag}) - set(always 1) - elseif(svn_repository) - if(NOT Subversion_SVN_EXECUTABLE) - message(FATAL_ERROR "error: could not find svn for update of ${name}") - endif() - set(work_dir ${source_dir}) - set(comment "Performing update step (SVN update) for '${name}'") - get_property(svn_revision TARGET ${name} PROPERTY _EP_SVN_REVISION) - get_property(svn_username TARGET ${name} PROPERTY _EP_SVN_USERNAME) - get_property(svn_password TARGET ${name} PROPERTY _EP_SVN_PASSWORD) - get_property(svn_trust_cert TARGET ${name} PROPERTY _EP_SVN_TRUST_CERT) - set(svn_user_pw_args "") - if(DEFINED svn_username) - set(svn_user_pw_args ${svn_user_pw_args} "--username=${svn_username}") - endif() - if(DEFINED svn_password) - set(svn_user_pw_args ${svn_user_pw_args} "--password=${svn_password}") - endif() - if(svn_trust_cert) - set(svn_trust_cert_args --trust-server-cert) - endif() - set(cmd ${Subversion_SVN_EXECUTABLE} up ${svn_revision} - --non-interactive ${svn_trust_cert_args} ${svn_user_pw_args}) - set(always 1) - elseif(git_repository) - unset(CMAKE_MODULE_PATH) # Use CMake builtin find module - find_package(Git QUIET) - if(NOT GIT_EXECUTABLE) - message(FATAL_ERROR "error: could not find git for fetch of ${name}") - endif() - set(work_dir ${source_dir}) - set(comment "Performing update step for '${name}'") - get_property(git_tag TARGET ${name} PROPERTY _EP_GIT_TAG) - if(NOT git_tag) - set(git_tag "master") - endif() - get_property(git_remote_name TARGET ${name} PROPERTY _EP_GIT_REMOTE_NAME) - if(NOT git_remote_name) - set(git_remote_name "origin") - endif() - - set(git_init_submodules TRUE) - get_property(git_submodules_set TARGET ${name} PROPERTY _EP_GIT_SUBMODULES SET) - if(git_submodules_set) - get_property(git_submodules TARGET ${name} PROPERTY _EP_GIT_SUBMODULES) - if(git_submodules STREQUAL "" AND _EP_CMP0097 STREQUAL "NEW") - set(git_init_submodules FALSE) - endif() - endif() - - get_property(git_update_strategy TARGET ${name} PROPERTY _EP_GIT_REMOTE_UPDATE_STRATEGY) - if(NOT git_update_strategy) - set(git_update_strategy "${CMAKE_EP_GIT_REMOTE_UPDATE_STRATEGY}") - endif() - if(NOT git_update_strategy) - set(git_update_strategy REBASE) - endif() - set(strategies CHECKOUT REBASE REBASE_CHECKOUT) - if(NOT git_update_strategy IN_LIST strategies) - message(FATAL_ERROR "'${git_update_strategy}' is not one of the supported strategies: ${strategies}") - endif() - - _ep_get_git_submodules_recurse(git_submodules_recurse) - - _ep_write_gitupdate_script(${tmp_dir}/${name}-gitupdate.cmake - ${GIT_EXECUTABLE} ${git_tag} ${git_remote_name} ${git_init_submodules} "${git_submodules_recurse}" "${git_submodules}" ${git_repository} ${work_dir} ${git_update_strategy} - ) - set(cmd ${CMAKE_COMMAND} -P ${tmp_dir}/${name}-gitupdate.cmake) - set(always 1) - elseif(hg_repository) - if(NOT HG_EXECUTABLE) - message(FATAL_ERROR "error: could not find hg for pull of ${name}") - endif() - set(work_dir ${source_dir}) - set(comment "Performing update step (hg pull) for '${name}'") - get_property(hg_tag TARGET ${name} PROPERTY _EP_HG_TAG) - if(NOT hg_tag) - set(hg_tag "tip") - endif() - if("${HG_VERSION_STRING}" STREQUAL "2.1") - message(WARNING "Mercurial 2.1 does not distinguish an empty pull from a failed pull: - http://mercurial.selenic.com/wiki/UpgradeNotes#A2.1.1:_revert_pull_return_code_change.2C_compile_issue_on_OS_X - http://thread.gmane.org/gmane.comp.version-control.mercurial.devel/47656 -Update to Mercurial >= 2.1.1. -") - endif() - set(cmd ${HG_EXECUTABLE} pull - COMMAND ${HG_EXECUTABLE} update ${hg_tag} - ) - set(always 1) - endif() - - get_property(log TARGET ${name} PROPERTY _EP_LOG_UPDATE) - if(log) - set(log LOG 1) - else() - set(log "") - endif() - - get_property(uses_terminal TARGET ${name} PROPERTY - _EP_USES_TERMINAL_UPDATE) - if(uses_terminal) - set(uses_terminal USES_TERMINAL 1) - else() - set(uses_terminal "") - endif() - - set(__cmdQuoted) - foreach(__item IN LISTS cmd) - string(APPEND __cmdQuoted " [==[${__item}]==]") - endforeach() - cmake_language(EVAL CODE " - ExternalProject_Add_Step(${name} update - COMMENT \${comment} - COMMAND ${__cmdQuoted} - ALWAYS \${always} - EXCLUDE_FROM_MAIN \${update_disconnected} - WORKING_DIRECTORY \${work_dir} - DEPENDEES download - ${log} - ${uses_terminal} - )" - ) - - if(update_disconnected) - _ep_get_step_stampfile(${name} skip-update skip-update_stamp_file) - string(REPLACE "Performing" "Skipping" comment "${comment}") - ExternalProject_Add_Step(${name} skip-update - COMMENT ${comment} - ALWAYS ${always} - EXCLUDE_FROM_MAIN 1 - WORKING_DIRECTORY ${work_dir} - DEPENDEES download - ${log} - ${uses_terminal} - ) - set_property(SOURCE ${skip-update_stamp_file} PROPERTY SYMBOLIC 1) - endif() -
