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
86798b4d
Commit
86798b4d
authored
15 years ago
by
Kavindra Devi Palaraja
Browse files
Options
Downloads
Patches
Plain Diff
Doc - More Cleanups
Reviewed-By: TrustMe
parent
c79e8079
No related branches found
Branches containing commit
No related tags found
Tags containing commit
Loading
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/qtcreator.qdoc
+17
-15
17 additions, 15 deletions
doc/qtcreator.qdoc
with
17 additions
and
15 deletions
doc/qtcreator.qdoc
+
17
−
15
View file @
86798b4d
...
...
@@ -1530,26 +1530,28 @@ Click here to continue where you left creator last time", or something similar p
\section1 CMake Projects
In CMake, libraries are usually detected using the \c{FIND_PACKAGE()} macro.
A couple of them are already being shipped with CMake, they can be found in
the \c{Modules} directory of your CMake installation. If you provide
libraries on your own, you will need to provide your own \c{FindFoo.cmake}
file. Refer to the \l{http://vtk.org/Wiki/CMake_FAQ#Writing_FindXXX.cmake_files}
{CMake FAQ} for details.
In CMake, libraries are usually detected using the \c{FIND_PACKAGE()}
macro. A couple of them are already being shipped with CMake, they can be
found in the \c{Modules} directory of your CMake installation. If you
provide libraries on your own, you will need to provide your own
\c{FindFoo.cmake} file. Refer to the
\l{http://vtk.org/Wiki/CMake_FAQ#Writing_FindXXX.cmake_files}{CMake FAQ}
for details.
As with qmake project, syntax completion and highlighting should work if
you can sucessfully build and link against the external library.
As with \c qmake projects, syntax completion and highlighting should work
if you can sucessfully build and link against the external library.
\section1 Generic Projects
If you import a project using the \e{Generic Projects} function, Qt Creator
will
create a file called \c{<projectname>.includes} in your project root
directory. It will
contain all project subdirectories
it that was able to find relevant header files in.
Simply add your include pathes
t
here.
If you import a project using the \e{Generic Projects} function, Qt Creator
will
create a file called \c{<projectname>.includes} in your project root
directory. This file
contain
s
all project subdirectories
which Qt Creator
could find relevant headers for.
Simply add your include pathes here.
Note that in
Generic Project mode, Qt Creator will
refrain from touching any
project
settings, so the above is merely a hint for
the
code completion and
the syntax
highlight
er
.
In \gui
Generic Project
}
mode, Qt Creator will
not modify any project
settings, so the above is merely a hint for code completion and
syntax
highlight
ing
.
*/
...
...
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