Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Q
qt-creator
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tobias Hunger
qt-creator
Commits
cc95132a
Commit
cc95132a
authored
16 years ago
by
Thorbjørn Lindeijer
Browse files
Options
Downloads
Patches
Plain Diff
Made a start on improving the generic project documentation
parent
10721dc3
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/qtcreator.qdoc
+42
-4
42 additions, 4 deletions
doc/qtcreator.qdoc
with
42 additions
and
4 deletions
doc/qtcreator.qdoc
+
42
−
4
View file @
cc95132a
...
@@ -1428,12 +1428,50 @@
...
@@ -1428,12 +1428,50 @@
Since Qt Creator 1.1, generic projects are supported, in addition to
Since Qt Creator 1.1, generic projects are supported, in addition to
\c qmake projects. In other words, you can import existing projects that
\c qmake projects. In other words, you can import existing projects that
do not use \c qmake or \c CMake and
Qt Creator will simply ignore your
do not use \c qmake or \c CMake and Qt Creator will simply ignore your
build system.
build system.
This feature lets you use Qt Creator as a code editor. You can build your
This feature lets you use Qt Creator as a code editor. You can change the
project by modifying the \c make command in the \gui{Project Settings}
way your project is built by modifying the \c make command on the
page.
\gui{Project Settings} page.
Since Qt Creator has no way of knowing which files belong to your project,
or which include directories and defines you're passing to your compiler,
the generic project allows you to specify this information manually.
\section1 Specifying which files belong to your project
The list of files belonging to a generic project is specified in the
\c{.files} file. Qt Creator adds any files that it recognizes when you
first create the generic project. If you want to add additional files, or
need to add/remove files later, edit the .files file in Qt Creator. Your
project tree will be refreshed on saving this file.
If you frequently need to update this file, for example after updating
from a source control system, you may want to write a small script that
updates the file for you. At the moment Qt Creator needs to be restarted
when the file is modified externally, in order to pick up the changes.
\section1 Specifying the include paths
The include paths are specified in the \c{.includes} file.
\section1 Specifying the defines
The defines are specified in the \c{.config} file. This is basically a
regular C++ file that is prepended to all your source files when they are
being parsed, but you should generally only use it to add lines like the
following:
#define NAME value
\section1 Creating a run configuration
Qt Creator can't automatically determine which executable it should run.
Hence, set up a custom executable run configuration in the Projects mode,
using the + button. Specify the name, executable, optionally some
arguments. The working directory is $BUILDDIR by default, which should
generally work fine.
*/
*/
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment