Qt Documentation
Go to file
Mitch Curtis d336ca0186 Doc: give property assignments their own line in coding conventions
The point of the convention was that related properties should be part
of the same "block" or "group" of assignments, which can be achieved by
ensuring that they are directly above/below one another. Bunching up
assignments onto one line for a few properties should not be a
recommended practice.

Change-Id: Ie84163b3261e7138d69678e059a91c2c82b43507
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
2018-07-16 09:33:06 +00:00
dist Add changes file for Qt 5.11.1 2018-06-09 11:11:38 +00:00
doc Doc: give property assignments their own line in coding conventions 2018-07-16 09:33:06 +00:00
examples/demos/coffee Doc: Move coffeemachine examples to examples/demos 2018-06-07 11:07:19 +00:00
.gitattributes Update the git-archive export options 2012-09-03 19:51:51 +02:00
.gitignore Doc: Remove qtdemo example 2014-09-17 12:38:32 +02:00
.qmake.conf Bump version 2018-05-31 14:04:10 +02:00
.tag Update the git-archive export options 2012-09-03 19:51:51 +02:00
LICENSE.FDL Add license files mandated by (L)GPL. 2013-02-15 00:04:35 +01:00
README Adjust wiki links to the new redirect 2015-03-03 12:12:03 +00:00
qtdoc.pro Doc: Remove qtdemo example 2014-09-17 12:38:32 +02:00
sync.profile remove dependencies from sync.profile 2016-11-14 12:18:33 +00:00

README

To Generate Qt Documentation:

qtdoc contains the main Qt Reference Documentation, which includes
overviews, Qt topics, and examples not specific to any Qt module.The
configuration files are located in qtdoc/doc/config and the articles in
qtdoc/doc/src. Note that QDoc is located in qtbase.

The instructions in this file assumes that the prerequisite binaries are
compiled and in the $PATH variable.

Prerequisites:
    * qtbase exists
    * "qmake" and "qdoc" compiled and installed
    * other Qt repositories exist as needed

The Qt Reference Documentation were written with links to the released modules
for Qt 5. If the modules and repositories do not exist, then the resulting HTML
files will contain broken links.

There are two ways to build the documentation. One way is to compile the
documentation using QDoc and the configuration file (qdocconf) file. The other
way is to use qmake by running "make docs".

Section 1 Building the qdocconf File

    This method is useful for building separate projects without any
    dependencies to other projects.

    To build using the qdocconf file, run the "qdoc" binary and pass the
    qdocconf file as a parameter. "qdoc" is found in qtbase repository. A
    mandatory "outputdir" must be specified.

        $> qdoc doc/config/qtdoc.qdocconf -outputdir html

    Note that QDoc will delete the contents of the "html" output directory.

Section 2 Building using make

    QMake uses the QT_INSTALL_DOCS variable to determine where the documentation
    for Qt 5 are installed. This method is useful for linking to other Qt
    modules.

    To see where the documentation will be installed, run:
    $> qmake -query

    To generate the documentation, run:

    $> cd qtdoc  #or whichever repository's root
    $> qmake
    $> make docs

    "make docs" also works in the main Qt 5 repository. Running the command
    there will generate the documentation for Qt 5 and install them to the
    path set to the QT_INSTALL_DOCS variable.

Section 3 Building Qt Documentation

    To build the Qt module documentation along with the Qt Reference Documentation,
    run the following:

    $> cd qt5  #the main qt5.git directory
    $> make qmake_all  #creates Makefiles for each repository
    $> make docs

    To generate only HTML files, run "make html_docs" instead of "make docs"

Section 4 Packaging the Documentation

    To package the documentation for Qt Assistant, the HTML files must be
    compiled into a QCH file (.qch).

    Required binaries:
    * assistant - found in qttools
    * qhelpgenerator - found in qttools

    To compile thq qch file for each module, first enter the output directory
    which contains the .qhp file and generate the QCH file.

    $> cd qtbase/doc/qtdoc              #the default path for QT_INSTALL_DOCS for qtdoc
    $> qhelpgenerator qtdoc.qhp         #creates the QCH file called qtdoc.qch

    Alternatively, modules have a "qch_docs" target:
    $> cd qtbase
    $> make qch_docs #builds the QCH files for modules in qtbase

    The QCH file can then be loaded in Qt Assistant or Qt Creator. For Qt
    Assistant, the QCH file may be registered to automatically load it.

    $> assistant -register qtdoc.qch    #to automatically load the documentation

Section 5 More Information

For more information about Qt 5's documentation, refer to the Qt Project wiki:
http://wiki.qt.io/Qt5DocumentationProject