Doc: Make info about managing projects more generic

The details are described in the listed topics.

Change-Id: I243eb8dc102ef42030a1a2e1b28af2679e6ca631
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
This commit is contained in:
Leena Miettinen
2018-06-25 10:28:12 +02:00
parent 77c260e14c
commit ef40f8445e
2 changed files with 13 additions and 15 deletions

View File

@@ -39,9 +39,9 @@
\image creator_managingprojects.png
One of the major advantages of \QC is that it allows a team of developers
to share a project across different development platforms with a common tool
for development and debugging.
One of the major advantages of \QC is that it allows a team of designers and
developers to share a project across different development platforms with a
common tool for design, development, and debugging.
\list
@@ -55,21 +55,14 @@
\li \l{Using Version Control Systems}
The recommended way to set up a project is to use a version control
system. Store and edit only project source files and build system
configuration files (for example, .pro and .pri files for qmake).
Do not store files generated by the build system or \QC, such as
makefiles, .pro.user, and object files.
system. Store and edit only project source files and configuration
files. Do not store generated files.
\li \l{Configuring Projects}
\QC allows you to specify separate build settings for each
development platform. By default, \l{glossary-shadow-build}
{shadow builds} are used to keep the build specific files separate
from the source. You can create separate versions of project files
to keep platform-dependent code separate. You can use qmake
\l{Adding Platform Specific Source Files}
{scopes} to select the file to process depending on which platform
qmake is run on.
Installation programs and project wizards create default
configurations for \QC and your projects. You can modify
the settings in the Projects mode.
\li \l{Managing Sessions}

View File

@@ -75,6 +75,11 @@
\uicontrol General, and enter a period (.) in the
\uicontrol {Default build directory} field.
You can create separate versions of project files to keep platform-dependent
code separate. You can use qmake \l{Adding Platform Specific Source Files}
{scopes} to select the file to process depending on which platform qmake is
run on.
\include creator-projects-cmake-building.qdocinc cmake build configuration
\section1 Starting External Processes