1MACOSX_PACKAGE_LOCATION
2-----------------------
3
4Place a source file inside a Application Bundle
5(:prop_tgt:`MACOSX_BUNDLE`), Core Foundation Bundle (:prop_tgt:`BUNDLE`),
6or Framework Bundle (:prop_tgt:`FRAMEWORK`).  It is applicable for macOS
7and iOS.
8
9Executable targets with the :prop_tgt:`MACOSX_BUNDLE` property set are
10built as macOS or iOS application bundles on Apple platforms.  Shared
11library targets with the :prop_tgt:`FRAMEWORK` property set are built as
12macOS or iOS frameworks on Apple platforms.  Module library targets with
13the :prop_tgt:`BUNDLE` property set are built as macOS ``CFBundle`` bundles
14on Apple platforms.  Source files listed in the target with this property
15set will be copied to a directory inside the bundle or framework content
16folder specified by the property value.  For macOS Application Bundles the
17content folder is ``<name>.app/Contents``.  For macOS Frameworks the
18content folder is ``<name>.framework/Versions/<version>``.  For macOS
19CFBundles the content folder is ``<name>.bundle/Contents`` (unless the
20extension is changed).  See the :prop_tgt:`PUBLIC_HEADER`,
21:prop_tgt:`PRIVATE_HEADER`, and :prop_tgt:`RESOURCE` target properties for
22specifying files meant for ``Headers``, ``PrivateHeaders``, or
23``Resources`` directories.
24
25If the specified location is equal to ``Resources``, the resulting location
26will be the same as if the :prop_tgt:`RESOURCE` property had been used. If
27the specified location is a sub-folder of ``Resources``, it will be placed
28into the respective sub-folder. Note: For iOS Apple uses a flat bundle layout
29where no ``Resources`` folder exist. Therefore CMake strips the ``Resources``
30folder name from the specified location.
31