diff options
Diffstat (limited to 'qmake/doc/src/qmake-manual.qdoc')
| -rw-r--r-- | qmake/doc/src/qmake-manual.qdoc | 111 |
1 files changed, 65 insertions, 46 deletions
diff --git a/qmake/doc/src/qmake-manual.qdoc b/qmake/doc/src/qmake-manual.qdoc index 58441064ad..dedb491959 100644 --- a/qmake/doc/src/qmake-manual.qdoc +++ b/qmake/doc/src/qmake-manual.qdoc @@ -657,9 +657,9 @@ qmake knows about many of these features, which can be accessed via specific variables that only take effect on the platforms where they are relevant. - \section1 Mac OS X + \section1 OS X and iOS - Features specific to this platform include support for creating universal + Features specific to these platforms include support for creating universal binaries, frameworks and bundles. \section2 Source and Binary Packages @@ -681,7 +681,7 @@ qmake is able to automatically generate build rules for linking against frameworks in the standard framework directory on - Mac OS X, located at \c{/Library/Frameworks/}. + OS X, located at \c{/Library/Frameworks/}. Directories other than the standard framework directory need to be specified to the build system, and this is achieved by appending linker options to the @@ -722,14 +722,14 @@ and \l{QMAKE_FRAMEWORK_VERSION} variables. By default, the values used for these variables are obtained from the \l{TARGET} and \l{VERSION} variables. - See \l{Qt for Mac OS X - Deployment} for more information about + See \l{Qt for OS X - Deployment} for more information about deploying applications and libraries. \section2 Creating and Moving Xcode Projects - Developers on Mac OS X can take advantage of the qmake support for Xcode + Developers on OS X can take advantage of the qmake support for Xcode project files, as described in - \l{Qt is Mac OS X Native#Development Tools}{Qt is Mac OS X Native}, + \l{Qt is OS X Native#Development Tools}{Qt is OS X Native}, by running qmake to generate an Xcode project from an existing qmake project file. For example: @@ -1026,7 +1026,7 @@ See \l{Platform Notes#Visual Studio Manifest Files}{Platform Notes} for more information about the options for embedding manifest files. - The following options take an effect only on Mac OS X: + The following options take an effect only on OS X: \table \header \li Option \li Description @@ -1360,7 +1360,7 @@ Indicates the header file for creating a precompiled header file, to increase the compilation speed of a project. Precompiled headers are currently only supported on some platforms - (Windows - all MSVC project types, Mac OS X - Xcode, Makefile, + (Windows - all MSVC project types, Apple - Xcode, Makefile, Unix - gcc 3.3 and up). \target PWD @@ -1409,7 +1409,7 @@ \target QMAKE_BUNDLE_DATA \section1 QMAKE_BUNDLE_DATA - \note This variable is used on Mac OS X only. + \note This variable is used on OS X and iOS only. Specifies the data that will be installed with a library bundle, and is often used to specify a collection of header files. @@ -1431,7 +1431,7 @@ \section1 QMAKE_BUNDLE_EXTENSION - \note This variable is used on Mac OS X only. + \note This variable is used on OS X and iOS only. Specifies the extension to be used for library bundles. This allows frameworks to be created with custom extensions instead of the @@ -1649,7 +1649,7 @@ \section1 QMAKE_FRAMEWORK_BUNDLE_NAME - \note This variable is used on Mac OS X only. + \note This variable is used on OS X and iOS only. In a framework project, this variable contains the name to be used for the framework that is built. @@ -1663,9 +1663,9 @@ \target QMAKE_FRAMEWORK_VERSION \section1 QMAKE_FRAMEWORK_VERSION - \note This variable is used on Mac OS X only. + \note This variable is used on OS X and iOS only. - For projects where the build target is a Mac OS X framework, this variable + For projects where the build target is an OS X or iOS framework, this variable is used to specify the version number that will be applied to the framework that is built. @@ -1739,10 +1739,10 @@ \target QMAKE_INFO_PLIST \section1 QMAKE_INFO_PLIST - \note This variable is used on Mac OS X platforms only. + \note This variable is used on OS X and iOS platforms only. Specifies the name of the property list file, \c{.plist}, you - would like to include in your Mac OS X application bundle. + would like to include in your OS X and iOS application bundle. In the \c{.plist} file, you can define some variables, e.g., @EXECUTABLE@, which qmake will replace with the actual executable name. Other variables @@ -1996,16 +1996,16 @@ \section1 QMAKE_MAC_SDK - This variable is used on Mac OS X when building universal binaries. + This variable is used on OS X when building universal binaries. \section1 QMAKE_MACOSX_DEPLOYMENT_TARGET - This variable only takes effect when building on Mac OS X. On that + This variable only takes effect when building on OS X. On that platform, the variable will be forwarded to the MACOSX_DEPLOYMENT_TARGET environment variable, which is interpreted by the compiler or linker. For more information, see the - \l{Qt for Mac OS X - Deployment#Mac OS X Version Dependencies}{Deploying - an Application on Mac OS X} document. + \l{Qt for OS X - Deployment#OS X Version Dependencies}{Deploying + an Application on OS X} document. \section1 QMAKE_MAKEFILE @@ -2071,6 +2071,39 @@ qmake or \l{#QMAKESPEC}{qmake.conf} and rarely needs to be modified. + \section1 QMAKE_SONAME_PREFIX + + If defined, the value of this variable is used as a path to be prepended to + the built shared library's \c SONAME identifier. The \c SONAME is the + identifier that the dynamic linker will later use to reference the library. + In general this reference may be a library name or full library path. On OS + X and iOS, the path may be specified relatively using the following + placeholders: + + \table + \header \li Placeholder \li Effect + \row \li @rpath + \li Expands to paths defined by LC_RPATH mach-o commands in + the current process executable or the referring libraries. + \row \li @executable_path + \li Expands to the current process executable location. + \row \li @loader_path + \li Expands to the referring executable or library location. + \endtable + + In most cases, using \c @rpath is sufficient and recommended: + + \snippet code/doc_src_qmake-manual.pro 183 + + However, the prefix may be also specified using different placeholders, or + an absolute path, such as one of the following: + + \snippet code/doc_src_qmake-manual.pro 184 + + For more information, see + \l{https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/dyld.1.html}{dyld} + documentation on dynamic library install names. + \section1 QMAKE_TARGET Specifies the name of the project target. The value of this @@ -2417,13 +2450,6 @@ \li architecture \li The target architecture. Defaults to \c VCPROJ_ARCH. \row - \li arguments - \li Allows arguments to be passed to the executable. - \row - \li author - \li Package author. Defaults to \c{Default package author}. - This option is only available for Windows Phone. - \row \li background \li Tile background color. Defaults to \c{green}. \row @@ -2432,7 +2458,7 @@ \row \li capabilities_device \li Specifies device capabilities to add to the capability list - (location, webcam, and so on). This option is not available on Windows Phone. + (location, webcam, and so on). \row \li default_language \li The default language code of the application. Defaults to "en". @@ -2447,10 +2473,6 @@ \li Tile foreground (text) color. Defaults to \c{light}. This option is only available for Windows Store apps on Windows 8 and Windows RT. \row - \li genre - \li Package genre. Defaults to \c{apps.normal}. - This option is only available for Windows Phone. - \row \li iconic_tile_icon \li Image file for the \c{iconic} tile template icon. Default provided by the mkspec. @@ -2463,10 +2485,6 @@ \li The unique ID of the app. Defaults to reusing the existing generated manifest's UUID, or generates a new UUID if none is present. \row - \li languages - \li A list of additional language codes supported by the application. This list - is empty by default. - \row \li logo_large \li Large logo image file. Default provided by the mkspec. \row @@ -2482,12 +2500,17 @@ \li name \li The name of the package as displayed to the user. Defaults to TARGET. \row + \li phone_product_id + \li The GUID of the product. Defaults to the value of WINRT_MANIFEST.identity. (Windows Phone only) + \row + \li phone_publisher_id + \li The GUID of the publisher. Defaults to an invalid GUID. (Windows Phone only) + \row \li publisher \li Display name of the publisher. Defaults to \c{Default publisher display name}. \row \li publisher_id - \li On Windows 8 or Windows RT, the publisher's distinguished name (default: \c{CN=MyCN}). - On Windows Phone, the publisher's UUID (default: invalid UUID string). + \li The publisher's distinguished name (default: \c{CN=MyCN}). \row \li splash_screen \li Splash screen image file. Default provided by the mkspec. @@ -2506,12 +2529,8 @@ \code WINRT_MANIFEST.publisher = MyCompany WINRT_MANIFEST.logo_store = someImage.png - winphone { - WINRT_MANIFEST.capabilities += ID_CAP_LOCATION ID_CAP_NETWORKING - } else { - WINRT_MANIFEST.capabilities += internetClient - WINRT_MANIFEST.device_capabilities += location - } + WINRT_MANIFEST.capabilities += internetClient + WINRT_MANIFEST.device_capabilities += location \endcode Additionally, an input manifest file can be specified by using WINRT_MANIFEST. @@ -4110,7 +4129,7 @@ \li nmake \li Visual Studio projects (VS 2008 and later) \endlist - \li Mac OS X + \li OS X and iOS \list \li Makefile \li Xcode @@ -4481,7 +4500,7 @@ them uses project-specific variables to customize output files. Platform-specific variables are not described here. For more information, - see \l{Qt for Windows - Deployment} and \l{Qt for Mac OS X}. + see \l{Qt for Windows - Deployment} and \l{Qt for OS X}. \target Application \section1 Building an Application @@ -4630,7 +4649,7 @@ \endlist The target file name for the library is platform-dependent. For example, on - X11 and Mac OS X, the library name will be prefixed by \c lib. On Windows, + X11, OS X, and iOS, the library name will be prefixed by \c lib. On Windows, no prefix is added to the file name. \target Plugin |