experimental.rst 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. CMake Experimental Features Guide
  2. *********************************
  3. The following is a guide to CMake experimental features that are
  4. under development and not yet included in official documentation.
  5. See documentation on `CMake Development`_ for more information.
  6. .. _`CMake Development`: README.rst
  7. Features are gated behind ``CMAKE_EXPERIMENTAL_`` variables which must be set
  8. to specific values in order to enable their gated behaviors. Note that the
  9. specific values will change over time to reinforce their experimental nature.
  10. When used, a warning will be generated to indicate that an experimental
  11. feature is in use and that the affected behavior in the project is not part of
  12. CMake's stability guarantees.
  13. Export Package Dependencies
  14. ===========================
  15. In order to activate support for this experimental feature, set
  16. * variable ``CMAKE_EXPERIMENTAL_EXPORT_PACKAGE_DEPENDENCIES`` to
  17. * value ``1942b4fa-b2c5-4546-9385-83f254070067``.
  18. This UUID may change in future versions of CMake. Be sure to use the value
  19. documented here by the source tree of the version of CMake with which you are
  20. experimenting.
  21. When activated, this experimental feature provides the following:
  22. * The ``install(EXPORT)`` and ``export(EXPORT)`` commands have experimental
  23. ``EXPORT_PACKAGE_DEPENDENCIES`` arguments to generate ``find_dependency``
  24. calls automatically.
  25. * Details of the calls may be configured using the ``export(SETUP)``
  26. command's ``PACKAGE_DEPENDENCY`` argument.
  27. * The package name associated with specific targets may be specified
  28. using the ``CMAKE_EXPORT_FIND_PACKAGE_NAME`` variable and/or
  29. ``EXPORT_FIND_PACKAGE_NAME`` target property.
  30. Export |CPS| Package Information
  31. ================================
  32. In order to activate support for this experimental feature, set
  33. * variable ``CMAKE_EXPERIMENTAL_EXPORT_PACKAGE_INFO`` to
  34. * value ``7fa7d13b-8308-4dc7-af39-9e450456d68f``.
  35. This UUID may change in future versions of CMake. Be sure to use the value
  36. documented here by the source tree of the version of CMake with which you are
  37. experimenting.
  38. When activated, this experimental feature provides the following:
  39. * The experimental ``export(PACKAGE_INFO)`` and ``install(PACKAGE_INFO)``
  40. commands are available to export package information in the |CPS|_ format.
  41. See :command:`install(PACKAGE_INFO)` for a complete overview of the command.
  42. Export |CPS| Package Information for ``install(EXPORT)``
  43. """"""""""""""""""""""""""""""""""""""""""""""""""""""""
  44. In order to activate support for this experimental feature, set
  45. * variable ``CMAKE_EXPERIMENTAL_EXPORT_PACKAGE_INFO`` to
  46. * value ``b80be207-778e-46ba-8080-b23bba22639e``.
  47. * variable ``CMAKE_EXPERIMENTAL_MAPPED_PACKAGE_INFO`` to
  48. * value ``ababa1b5-7099-495f-a9cd-e22d38f274f2``.
  49. These UUIDs may change in future versions of CMake. Be sure to use the values
  50. documented here by the source tree of the version of CMake with which you are
  51. experimenting.
  52. When activated, this experimental feature provides the following:
  53. * Setting ``CMAKE_INSTALL_EXPORTS_AS_PACKAGE_INFO`` enables generation of
  54. package information in the |CPS|_ format via the ``install(EXPORT)`` command.
  55. Find/Import |CPS| Packages
  56. ==========================
  57. In order to activate support for this experimental feature, set
  58. * variable ``CMAKE_EXPERIMENTAL_FIND_CPS_PACKAGES`` to
  59. * value ``e82e467b-f997-4464-8ace-b00808fff261``.
  60. This UUID may change in future versions of CMake. Be sure to use the value
  61. documented here by the source tree of the version of CMake with which you are
  62. experimenting.
  63. When activated, this experimental feature provides the following:
  64. * The :command:`find_package` command will also search for packages which are
  65. described using |CPS|_. Refer to the :command:`find_package` documentation
  66. for details.
  67. C++ ``import std`` support
  68. ==========================
  69. In order to activate support for ``import std`` in C++23 and newer targets,
  70. set
  71. * variable ``CMAKE_EXPERIMENTAL_CXX_IMPORT_STD`` to
  72. * value ``d0edc3af-4c50-42ea-a356-e2862fe7a444``.
  73. This UUID may change in future versions of CMake. Be sure to use the value
  74. documented here by the source tree of the version of CMake with which you are
  75. experimenting. It must be set before the ``CXX`` toolchain is discovered by
  76. CMake, usually as part of a :command:`project` call.
  77. When activated, this experimental feature provides the following:
  78. * The :prop_tgt:`CXX_MODULE_STD` target property and its initializing variable
  79. :variable:`CMAKE_CXX_MODULE_STD`.
  80. * Targets with the property set to a true value and at least ``cxx_std_23``
  81. may use ``import std;`` in any scanned C++ source file.
  82. .. _CPS: https://cps-org.github.io/cps/
  83. .. |CPS| replace:: Common Package Specification
  84. Build database support
  85. ======================
  86. In order to activate support for exporting build databases, set
  87. * variable ``CMAKE_EXPERIMENTAL_EXPORT_BUILD_DATABASE`` to
  88. * value ``73194a1d-c0b5-41b9-9190-a4512925e192``.
  89. This UUID may change in future versions of CMake. Be sure to use the value
  90. documented here by the source tree of the version of CMake with which you are
  91. experimenting.
  92. When activated, this experimental feature provides the following:
  93. * The :prop_tgt:`EXPORT_BUILD_DATABASE` target property and its initializing
  94. variable :variable:`CMAKE_EXPORT_BUILD_DATABASE` and environment variable
  95. :envvar:`CMAKE_EXPORT_BUILD_DATABASE`.
  96. * Targets with the property set to a true value will have their C++ build
  97. information exported to the build database.
  98. Instrumentation
  99. ===============
  100. In order to activate support for the :command:`cmake_instrumentation` command,
  101. set
  102. * variable ``CMAKE_EXPERIMENTAL_INSTRUMENTATION`` to
  103. * value ``ec7aa2dc-b87f-45a3-8022-fe01c5f59984``.
  104. To enable instrumentation at the user-level, files should be placed under
  105. either
  106. ``<CMAKE_CONFIG_DIR>/instrumentation-ec7aa2dc-b87f-45a3-8022-fe01c5f59984`` or
  107. ``<CMAKE_BINARY_DIR>/.cmake/instrumentation-ec7aa2dc-b87f-45a3-8022-fe01c5f59984``.
  108. To include instrumentation data in CTest XML files (for submission to CDash),
  109. you need to set the following environment variables:
  110. * ``CTEST_USE_INSTRUMENTATION=1``
  111. * ``CTEST_EXPERIMENTAL_INSTRUMENTATION=ec7aa2dc-b87f-45a3-8022-fe01c5f59984``
  112. Software Bill Of Materials |SBOM|
  113. =================================
  114. In order to activate support for the :command:`install(SBOM)` command,
  115. set
  116. * variable ``CMAKE_EXPERIMENTAL_GENERATE_SBOM`` to
  117. * value ``ca494ed3-b261-4205-a01f-603c95e4cae0``.
  118. This UUID may change in future versions of CMake. Be sure to use the value
  119. documented here by the source tree of the version of CMake with which you are
  120. experimenting.
  121. When activated, this experimental feature provides the following:
  122. * The experimental ``export(SBOM)`` and ``install(SBOM)`` commands are
  123. available to generate a Software Bill of Materials or "SBOM" for the current
  124. project. See :command:`install(SBOM)` for a complete overview of the command.