summaryrefslogtreecommitdiffstats
path: root/doc/html/qtmac-as-native.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/qtmac-as-native.html')
-rw-r--r--doc/html/qtmac-as-native.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/qtmac-as-native.html b/doc/html/qtmac-as-native.html
index 0bd5d76d2..3eb7ad1a2 100644
--- a/doc/html/qtmac-as-native.html
+++ b/doc/html/qtmac-as-native.html
@@ -111,14 +111,14 @@ accessiblity, and hopefully a host of assistive devices.
between their development toolkit and the platform's developer
tools (for example MSVC, gmake, etc). TQt/Mac supports both Unix
style Makefiles, and ProjectBuilder/Xcode project files by using
-the qmake tool. For example:
+the tqmake tool. For example:
<p> <pre>
- qmake -spec macx-pbuilder project.pro
+ tqmake -spec macx-pbuilder project.pro
</pre>
-<p> will generate an Xcode project file from project.pro. With qmake
+<p> will generate an Xcode project file from project.pro. With tqmake
you do not have to worry about rules for TQt's preprocessors (tqmoc
-and tquic) since qmake automatically handles them and ensures that
+and tquic) since tqmake automatically handles them and ensures that
everything necessary is linked into your application.
<p> TQt does not entirely interact with the development environment (for
example plugins to set a file to 'mocable' from within the Xcode