feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Make info about managing projects more generic

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files

23
doc/src/projects/creator-projects-overview.qdoc
View File

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

5
doc/src/projects/creator-projects-settings-build.qdoc
View File

@@ -75,6 +75,11 @@
\uicontrol General, and enter a period (.) in the \uicontrol General, and enter a period (.) in the
\uicontrol {Default build directory} field. \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 \include creator-projects-cmake-building.qdocinc cmake build configuration
\section1 Starting External Processes \section1 Starting External Processes