2014-08-03 19:52:23 +02:00
|
|
|
include_external_msproject
|
|
|
|
--------------------------
|
|
|
|
|
|
|
|
Include an external Microsoft project file in a workspace.
|
|
|
|
|
2019-11-11 23:01:05 +01:00
|
|
|
.. code-block:: cmake
|
2014-08-03 19:52:23 +02:00
|
|
|
|
|
|
|
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
|
2019-11-11 23:01:05 +01:00
|
|
|
named ``[projectname]``. This can be used in the :command:`add_dependencies`
|
2015-11-17 17:22:37 +01:00
|
|
|
command to make things depend on the external project.
|
2014-08-03 19:52:23 +02:00
|
|
|
|
2015-11-17 17:22:37 +01:00
|
|
|
``TYPE``, ``GUID`` and ``PLATFORM`` are optional parameters that allow one to
|
2019-11-11 23:01:05 +01:00
|
|
|
specify the type of project, id (``GUID``) of the project and the name of
|
2014-08-03 19:52:23 +02:00
|
|
|
the target platform. This is useful for projects requiring values
|
2016-07-09 11:21:54 +02:00
|
|
|
other than the default (e.g. WIX projects).
|
2017-07-20 19:35:53 +02:00
|
|
|
|
2021-09-14 00:13:48 +02:00
|
|
|
.. versionadded:: 3.9
|
|
|
|
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.
|