aboutsummaryrefslogtreecommitdiffstats
path: root/doc/qtcreatordev/src/getting-and-building.qdoc
blob: f45f3814cbcf77aab89799ca919947a1aded570d (plain)
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
// Copyright (C) 2016 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only

/*!
    \page getting-and-building.html
    \title Getting Qt and \QC

    To create and build a \QC plugin, you need a compatible version of Qt,
    and either a \QC package (released or snapshot) or your own \QC build.

    There are several reasons why you might want to do your own build of \QC,
    like using the most current development version and being able to tweak \QC
    at one or the other place. But it is not strictly necessary for creating
    plugins. The \QC packages contain a \uicontrol {Plugin Development}
    component that enables plugin development with the \QC contained in the
    package.

    \section1 Getting Qt

    Prebuilt \QC packages usually use the latest stable release of Qt.
    See the exact Qt version that a \QC package was built with in its
    \uicontrol {About \QC} dialog.

    The minimum requirements for building \QC are stated in the \l{README.md} and
    near the top of the \l{cmake/QtCreatorAPI.cmake} file in the sources.

    You can get prebuilt Qt packages from \l{Qt Downloads}. If you want to use Qt
    as provided by your Linux distribution, you need to make sure that all Qt development
    packages and private header packages are also installed.

    \section1 Getting \QC

    \section2 Installing a Prebuilt Package

    The prebuilt \QC packages contain a \uicontrol {Plugin Development}
    component that contains the CMake files, headers and other files
    that you need to build a plugin. It is not installed by default, so make
    sure to select the component when installing \QC.

    When developing your plugin, point the \c {CMAKE_PREFIX_PATH} to the
    installation location of \QC, or the \QC app on macOS.

    Get prebuilt packages either from \l{\QOI}, or a standalone \QC installer
    either for a \l{\QC Releases}{released \QC version} or a \l{\QC Snapshots}
    {development snapshot}.

    \section2 Building \QC

    You can get the \QC sources for a specific version either by using one of
    the released source bundles or by cloning the sources from the Git repository
    \l{qt-creator.git}. If you intend to contribute to \QC itself, use the
    repository from our Gerrit review tool, as described in \l{Setting up Gerrit}.

    See the \l{README.md} included in the sources for details on building \QC.

    When developing your plugin, point the \c {CMAKE_PREFIX_PATH} to the
    build location of \QC.
*/