summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKavindra Devi Palaraja <kavindra.palaraja@nokia.com>2009-08-03 15:58:12 +0200
committerThorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>2009-09-25 12:38:31 +0200
commit66bc31a3bc7c5755a4cfd8adcb795ceb25a83db9 (patch)
treee30d079f241dcfecb7436978e41ffda09610ffb8
parentd7f89d5dd93bf8a25460c74f484151f3b893fdf9 (diff)
downloadqt-creator-66bc31a3bc7c5755a4cfd8adcb795ceb25a83db9.tar.gz
Doc - More Cleanups
Reviewed-By: TrustMe (cherry picked from commit 86798b4d0d3fa92fffcfb90764968c82f96ec30a)
-rw-r--r--doc/qtcreator.qdoc32
1 files changed, 17 insertions, 15 deletions
diff --git a/doc/qtcreator.qdoc b/doc/qtcreator.qdoc
index e9904b4b12..e12c0fa467 100644
--- a/doc/qtcreator.qdoc
+++ b/doc/qtcreator.qdoc
@@ -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 there.
+ 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 contains 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 highlighter.
+ In \guiGeneric Project} mode, Qt Creator will not modify any project
+ settings, so the above is merely a hint for code completion and syntax
+ highlighting.
*/