1
/****************************************************************************
3
** Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies).
4
** Contact: http://www.qt-project.org/legal
6
** This file is part of the Qt Build Suite.
8
** Commercial License Usage
9
** Licensees holding valid commercial Qt licenses may use this file in
10
** accordance with the commercial license agreement provided with the
11
** Software or, alternatively, in accordance with the terms contained in
12
** a written agreement between you and Digia. For licensing terms and
13
** conditions see http://qt.digia.com/licensing. For further information
14
** use the contact form at http://qt.digia.com/contact-us.
16
** GNU Lesser General Public License Usage
17
** Alternatively, this file may be used under the terms of the GNU Lesser
18
** General Public License version 2.1 as published by the Free Software
19
** Foundation and appearing in the file LICENSE.LGPL included in the
20
** packaging of this file. Please review the following information to
21
** ensure the GNU Lesser General Public License version 2.1 requirements
22
** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
24
** In addition, as a special exception, Digia gives you certain additional
25
** rights. These rights are described in the Digia Qt LGPL Exception
26
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
28
****************************************************************************/
30
\contentspage index.html
31
\previouspage module-cpp.html
32
\page export-item.html
33
\nextpage filetagger-item.html
37
An \c Export item can appear inside a \l{Product Item}. The properties attached to it will
38
take effect in all products that depend on the product inside which the product module is defined.
39
As an example, consider these two products:
44
Depends { name: "cpp" }
55
The sources in product B will be able to use headers from product A without specifiying
56
the full path to them, because the include path has been made known to the compiler via
59
\note This relationship is transitive, so a product C depending on product B will also
60
get the include paths via A's product module.