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

Doc: restructure doc according to developer workflow

Browse Source 
Add and remove illustrations.
Add landing pages.

Change-Id: I927d62aee9dc43814ef7f4d7424a83eee2af156b
Reviewed-by: Erik Verbruggen <erik.verbruggen@nokia.com>
This commit is contained in:
Leena Miettinen
2011-12-13 11:52:47 +01:00
parent aeebb26ef1
commit 88e29febba
85 changed files with 1794 additions and 1153 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -33,102 +33,52 @@
\title Managing Projects
To set up a project, you first have to decide what kind of an application
you want to develop. Do you want a user interface based on:
\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.
\list
\o Qt Quick
\o HTML5
\if defined(qcmanual)
\o Qt widgets
\endif
\endlist
For a Qt Quick or HTML5 project, you also have a choice of the language to
implement the application logic: C++ or JavaScript.
You can also create other kinds of projects, such as Qt console
applications, shared or static C++ libraries, or subprojects.
You can use wizards to create and import projects. The wizards prompt you
to enter the settings needed for that particular type of project and create
the necessary files for you. You can add your own custom wizards to
standardize the way subprojects and classes are added to a project.
The wizards set up projects to use the Qt build tool, qmake. It is a
cross-platform system for build automation that helps simplify the build
process for development projects across different platforms. qmake
automates the generation of build configurations so that only a few lines
of information are needed to create each configuration. For more
information about qmake, see the
\l{http://qt.nokia.com/doc/4.7/qmake-manual.html}{qmake Manual}.
You can modify the build and run settings for qmake projects in the
\gui Projects mode.
Alternatively, you can use the CMake build automation system and set up the
projects manually. In addition, you can import generic projects that do not
use qmake or CMake. This allows you to use \QC as a code editor. For
generic projects, \QC ignores your build system.
\if defined(qcmanual)
To develop applications for Symbian devices, you use qmake and the local
Symbian compiler (on Windows) or qmake and a compilation service at
Nokia Developer (on Linux and Mac OS) to build the applications for the
Symbian devices target. The interface to the compilation service,
Remote Compiler, is installed as a part of the \QSDK. For more information,
see \l{Building with Remote Compiler}.
\endif
You can install mobile device \l{glossary-development-target}{targets}
as part of the \QSDK. The build and run settings for the
installed targets are set up automatically. However, you might need to
install and configure some additional software on the devices to be able to
connect to them from the development PC.
You can use sessions to store personal data, such as bookmarks and
breakpoints that are usually not of interest to other developers working on
the same projects. Sessions allow you to quickly switch between projects
when you work on several projects.
The following sections describe how to manage projects:
\list
\o \l{Creating Projects}
\o \l{Opening Projects}
\o \l{Adding Libraries to Projects}
To set up a project, you first have to decide what kind of an
application you want to develop: do you want a user interface based
on Qt Quick or HTML5 or Qt widgets. Second, you have to choose the
language to implement the application logic: C++ or JavaScript.
\o \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.
\o \l{Configuring Projects}
\list
\o \l{Specifying Build Settings}
\list
\o \l{Adding Qt Versions}
\o \l{Adding Tool Chains}
\endlist
\o \l{Specifying Run Settings}
\o \l{Specifying Editor Settings}
\o \l{Specifying Code Style Settings}
\o \l{Specifying Dependencies}
\endlist
\if defined(qcmanual)
\o \l{Connecting Maemo Devices}
\o \l{Connecting MeeGo Harmattan Devices}
\o \l{Connecting Generic Linux Devices}
\o \l{Connecting Symbian Devices}
\endif
\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{http://qt.nokia.com/doc/4.7/qmake-tutorial.html#adding-platform-specific-source-files}
{scopes} to select the file to process depending on which platform
qmake is run on.
\o \l{Managing Sessions}
Items such as open files, breakpoints, and evaluated expressions
are stored in sessions. They are not considered to be part of
the information shared across platforms.
\endlist
For advanced options, see the following topics:
\section1 Related Topics
\list
\o \l{Adding New Custom Wizards}
\o \l{Setting Up a CMake Project}
\o \l{Setting Up a Generic Project}
\o \l{Using Other Build Systems}
\endlist
*/