/usr/share/qt5/doc/qtdoc/macosx.html is in qt5-doc-html 5.3.2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- macosx.qdoc -->
<title>Qt for Mac OS X | QtDoc 5.3</title>
<link rel="stylesheet" type="text/css" href="style/offline.css" />
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<ul>
<li><a href="index.html">Qt 5.3</a></li>
<li>Qt for Mac OS X</li>
<li id="buildversion">
Qt 5.3.2 Reference Documentation</li>
</ul>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#downloading-and-installing-qt">Downloading and Installing Qt</a></li>
<li class="level2"><a href="#building-qt-5-from-source">Building Qt 5 from Source</a></li>
<li class="level1"><a href="#mac-os-x-versions">Mac OS X Versions</a></li>
<li class="level1"><a href="#additional-command-line-options">Additional Command-Line Options</a></li>
<li class="level1"><a href="#deploying-applications-on-mac-os-x">Deploying Applications on Mac OS X</a></li>
<li class="level1"><a href="#mac-os-x-issues">Mac OS X Issues</a></li>
<li class="level1"><a href="#where-to-go-from-here">Where to Go from Here</a></li>
</ul>
</div>
<h1 class="title">Qt for Mac OS X</h1>
<span class="subtitle"></span>
<!-- $$$macosx.html-description -->
<div class="descr"> <a name="details"></a>
<p>Mac OS X is a UNIX platform and behaves similarly to other Unix-like platforms. The main difference is that X11 is not used as the windowing system. Instead, Mac OS X uses its own native windowing system that is accessible through the Cocoa API. Application development on Mac OS X is done using Xcode, which is available from <a href="https://developer.apple.com/xcode/">https://developer.apple.com/xcode/</a>.</p>
<a name="downloading-and-installing-qt"></a>
<h2>Downloading and Installing Qt</h2>
<p>There are two ways to install Qt:</p>
<ol class="1">
<li>through the <i>Qt Installers</i> - downloads and installs Qt</li>
<li>through the <i>Qt sources</i>.</li>
</ol>
<p>You can download the Qt 5 installers and sources from the <a href="http://qt-project.org/downloads">Downloads</a> page. For more information, visit the <a href="gettingstarted.html">Getting Started with Qt</a> page.</p>
<p><b>Note: </b>Qt Enterprise packages are available from the <a href="http://qt.digia.com/Try-Buy/">Try Qt Enterprise</a> page.</p><a name="building-qt-5-from-source"></a>
<h3>Building Qt 5 from Source</h3>
<p>Below, you will find more information about building Qt from source.</p>
<ul>
<li><a href="macosx-building.html">Qt for Mac OS X - Building from Source</a> - building and installing from source</li>
</ul>
<p><b>Note: </b>Qt 5 uses Cocoa, therefore, building for Carbon is not possible.</p><a name="mac-os-x-versions"></a>
<h2>Mac OS X Versions</h2>
<p>Mac OS X 10.7 "Lion" and 10.8 "Mountain Lion" are considered <a href="supported-platforms.html#reference-configurations">reference configurations</a>, meaning they are tested by a continuous integration (CI) system. Qt 5 applications may be deployed to Mac OS X versions 10.6 "Snow Leopard", but support is limited.</p>
<p>Qt can be built for either x86 or x86_64. 64-bit is used by default. To select a 32-bit build, use the <tt>macx-clang-32</tt> or <tt>macx-g++32</tt> mkspec. This is selectable at configure time:</p>
<pre class="cpp"><span class="operator">.</span><span class="operator">/</span>configure <span class="operator">-</span>platform macx<span class="operator">-</span>clang<span class="operator">-</span><span class="number">32</span></pre>
<p>The Qt build system does not support building unversal binaries directly. Instead, use the <tt>lipo</tt> tool to glue two Qt builds together.</p>
<p><b>Note: </b>Qt 5 does not support Mac OS X on PowerPC.</p><p><b>Note: </b>Static builds are not tested.</p><a name="additional-command-line-options"></a>
<h2>Additional Command-Line Options</h2>
<p>On the command-line, applications can be built using <tt>qmake</tt> and <tt>make</tt>. Optionally, <tt>qmake</tt> can generate project files for Xcode with <tt>-spec macx-xcode</tt>. If you are using the binary package, <tt>qmake</tt> generates Xcode projects by default; use <tt>-spec macx-gcc</tt> to generate makefiles. For example:</p>
<pre class="cpp">qmake <span class="operator">-</span>spec macx<span class="operator">-</span>xcode project<span class="operator">.</span>pro</pre>
<p>Configuring with <tt>-spec macx-xcode</tt> generates an Xcode project file from project.pro. With <a href="../qmake/qmake-manual.html#qmake">qmake</a> you do not have to worry about rules for Qt's preprocessors (<a href="moc.html#moc">moc</a> and <a href="uic.html#uic">uic</a>) since <a href="../qmake/qmake-manual.html#qmake">qmake</a> automatically handles them and ensures that everything necessary is linked into your application.</p>
<p>Qt does not entirely interact with the development environment (for example plugins to set a file to "mocable" from within the Xcode user interface).</p>
<p>The result of the build process is an application bundle, which is a directory structure that contains the actual application executable. The application can be launched by double-clicking it in Finder, or by referring directly to its executable from the command line, for example, <tt>myApp.app/Contents/MacOS/myApp</tt>.</p>
<p>If you wish to have a command-line tool that does not use the GUI for example, <tt>moc</tt>, <tt>uic</tt> or <tt>ls</tt>, you can tell qmake to disable bundle creation from the <tt>CONFIG</tt> variable in the project file:</p>
<pre class="cpp">CONFIG <span class="operator">-</span><span class="operator">=</span> app_bundle</pre>
<a name="deploying-applications-on-mac-os-x"></a>
<h2>Deploying Applications on Mac OS X</h2>
<p>In general, Qt supports building on one Mac OS X version and deploying to earlier or later Mac OS X versions. You can build on 10.7 Lion and run the same binary on 10.6. The recommended way is to build on the latest version and deploy to an earlier Mac OS X version.</p>
<p>Mac OS X applications are typically deployed as self-contained application bundles. The application bundle contains the application executable as well as dependencies such as the Qt libraries, plugins, translations and other resources you may need. Third party libraries like Qt are normally not installed system-wide; each application provides its own copy.</p>
<p>A common way to distribute applications is to provide a compressed disk image (.dmg file) that the user can mount in Finder. The deployment tool, <tt>macdeployqt</tt> (available from the Mac OS X installers), can be used to create the self-contained bundles, and optionally also create a .dmg archive. Applications can also be distributed through the Mac App store. Qt 5 aims to stay within the app store sandbox rules. macdeployqt (bin/macdeployqt) can be used as a starting point for app store deployment.</p>
<ul>
<li><a href="macosx-deployment.html">Qt for Mac OS X - Deployment</a></li>
</ul>
<a name="mac-os-x-issues"></a>
<h2>Mac OS X Issues</h2>
<p>The page below covers specific issues and recommendations for creating Mac OS X applications.</p>
<ul>
<li><a href="macosx-issues.html">Qt for Mac OS X - Specific Issues</a></li>
</ul>
<a name="where-to-go-from-here"></a>
<h2>Where to Go from Here</h2>
<p>We invite you to explore the rest of Qt. We prepared overviews to help you decide which APIs to use and our examples demonstrate how to use our API.</p>
<ul>
<li><a href="overviews-main.html">Qt Overviews</a> - list of topics about application development</li>
<li><a href="qtexamplesandtutorials.html">Examples and Tutorials</a> - code samples and tutorials</li>
<li><a href="reference-overview.html">Qt Reference Pages</a> - a listing of C++ and QML APIs</li>
</ul>
<p>Qt's vibrant and active community site, <a href="http://qt-project.org">http://qt-project.org</a> houses a wiki, a forum, and additional learning guides and presentations.</p>
</div>
<!-- @@@macosx.html -->
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2014 Digia Plc and/or its
subsidiaries. Documentation contributions included herein are the copyrights of
their respective owners.<br> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br> Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
|