Skip to content
Snippets Groups Projects
Commit 0ed8a3cc authored by Brad King's avatar Brad King Committed by Kitware Robot
Browse files

Merge topic 'doc-IMPORTED_LOCATION' into release-3.20


08a25e49 Help: Clarify IMPORTED_LOCATION documentation

Acked-by: default avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !5968
parents daba4a02 08a25e49
No related branches found
No related tags found
No related merge requests found
......@@ -4,12 +4,12 @@ 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``
executables this is the location of the executable file. 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
shared library. For application bundles on macOS this is the location of
the executable file inside ``Contents/MacOS`` within the bundle folder.
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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment