This file is indexed.

/usr/share/qt5/doc/qtquickcontrols2/qtquickcontrols2-deployment.html is in qtquickcontrols2-5-doc-html 5.9.5-0ubuntu2.

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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- qtquickcontrols2-deployment.qdoc -->
  <title>Deploying Qt Quick Controls 2 Applications | Qt Quick Controls 2 5.9</title>
  <link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
  <script type="text/javascript">
    document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
    // loading style sheet breaks anchors that were jumped to before
    // so force jumping to anchor again
    setTimeout(function() {
        var anchor = location.hash;
        // need to jump to different anchor first (e.g. none)
        location.hash = "#";
        setTimeout(function() {
            location.hash = anchor;
        }, 0);
    }, 0);
  </script>
</head>
<body>
<div class="header" id="qtdocheader">
  <div class="main">
    <div class="main-rounded">
      <div class="navigationbar">
        <table><tr>
<td >Qt 5.9</td><td ><a href="qtquickcontrols2-index.html">Qt Quick Controls 2</a></td><td >Deploying Qt Quick Controls 2 Applications</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right">Qt 5.9.5 Reference Documentation</td>
        </tr></table>
      </div>
    </div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#deploying-an-application-with-several-styles">Deploying an Application with Several Styles</a></li>
<li class="level1"><a href="#static-builds">Static Builds</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Deploying Qt Quick Controls 2 Applications</h1>
<span class="subtitle"></span>
<!-- $$$qtquickcontrols2-deployment.html-description -->
<div class="descr"> <a name="details"></a>
<p>Deployment of Qt Quick Controls 2 applications is very similar to deployment of other types of Qt applications. However, there are a few factors to consider.</p>
<a name="deploying-an-application-with-several-styles"></a>
<h2 id="deploying-an-application-with-several-styles">Deploying an Application with Several Styles</h2>
<p>Suppose you have an application that will be deployed to both Android and Windows devices. To ensure that only the minimum set of files that are necessary for the application to run are deployed to each device, you can use file selectors. For example, your directory structure could look like this:</p>
<pre class="cpp">

  resources<span class="operator">.</span>qrc
  main<span class="operator">.</span>qml
  <span class="operator">+</span>windows<span class="operator">/</span>MyPage<span class="operator">.</span>qml
  <span class="operator">+</span>windows<span class="operator">/</span>qtquickcontrols2<span class="operator">.</span>conf
  <span class="operator">+</span>android<span class="operator">/</span>MyPage<span class="operator">.</span>qml
  <span class="operator">+</span>android<span class="operator">/</span>qtquickcontrols2<span class="operator">.</span>conf

</pre>
<p>In the project above, <code>main.qml</code> would import <code>QtQuick.Controls</code>, for example, but shouldn't import, say, <code>QtQuick.Controls.Material</code>. Any code that is style-specific is moved out into separate files; just as we've done for <code>MyPage.qml</code>.</p>
<p>The <code>+windows/qtquickcontrols2.conf</code> file would contain configuration options specific to the Universal style:</p>
<pre class="cpp">

  <span class="operator">[</span>Controls<span class="operator">]</span>
  Style<span class="operator">=</span>Universal

  <span class="operator">[</span>Universal<span class="operator">]</span>
  Theme<span class="operator">=</span>Dark
  Accent<span class="operator">=</span>Red

</pre>
<p>The <code>+android/qtquickcontrols2.conf</code> file would contain configuration options specific to the Material style:</p>
<pre class="cpp">

  <span class="operator">[</span>Controls<span class="operator">]</span>
  Style<span class="operator">=</span>Material

  <span class="operator">[</span>Material<span class="operator">]</span>
  Theme<span class="operator">=</span>Light
  Accent<span class="operator">=</span>Brown

</pre>
<a name="static-builds"></a>
<h2 id="static-builds">Static Builds</h2>
<p>For dynamically built applications, it is not necessary to import a specific style that should be usable by that application. For statically built applications, Qt's build system must be involved to ensure that QML plugins function as expected. Specifically, <code>qmake</code> uses <code>qmlimportscanner</code> to scan the QML files in your application for import statements. For this reason, any styles that should be usable by a statically built application must explicitly import that style. Where the import occurs is up to the developer, but it is recommended to follow the approach mentioned in the <a href="qtquickcontrols2-deployment.html#deploying-an-application-with-several-styles">Deploying an Application with Several Styles</a> section, so that only the minimum set of files that are necessary for a particular device are deployed.</p>
</div>
<p><b>See also </b>Deploying Qt Applications.</p>
<!-- @@@qtquickcontrols2-deployment.html -->
        </div>
       </div>
   </div>
   </div>
</div>
<div class="footer">
   <p>
   <acronym title="Copyright">&copy;</acronym> 2017 The Qt Company Ltd.
   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>    Qt and respective logos are trademarks of The Qt Company Ltd.     in Finland and/or other countries worldwide. All other trademarks are property
   of their respective owners. </p>
</div>
</body>
</html>