summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOBATA Akio <obache@wizdas.com>2020-07-07 17:12:46 +0900
committerOBATA Akio <obache@wizdas.com>2020-07-07 17:12:46 +0900
commit5a1d03de6b56d254662b5d3a57f809907359fff0 (patch)
tree670ef5a9b28228fb403f0f464adada0d790741ec
parentf62146e0e61ca0dd15221907cc3747e0f06319de (diff)
downloadtqt3-5a1d03de6b56d254662b5d3a57f809907359fff0.tar.gz
tqt3-5a1d03de6b56d254662b5d3a57f809907359fff0.zip
Refrect qt -> tqt changes to man1
Adjust page name to the installed tool name and follow class name changes in examples. Signed-off-by: OBATA Akio <obache@wizdas.com>
-rw-r--r--doc/man/README16
-rw-r--r--doc/man/man1/tqdesigner.1 (renamed from doc/man/man1/designer.1)6
-rw-r--r--doc/man/man1/tqembed.1 (renamed from doc/man/man1/qembed.1)12
-rw-r--r--doc/man/man1/tqlinguist.1 (renamed from doc/man/man1/linguist.1)4
-rw-r--r--doc/man/man1/tqlrelease.1 (renamed from doc/man/man1/lrelease.1)20
-rw-r--r--doc/man/man1/tqlupdate.1 (renamed from doc/man/man1/lupdate.1)20
-rw-r--r--doc/man/man1/tqmoc.1 (renamed from doc/man/man1/moc.1)100
-rw-r--r--doc/man/man1/tqtconfig.1 (renamed from doc/man/man1/qtconfig.1)6
-rw-r--r--doc/man/man1/tquic.1 (renamed from doc/man/man1/uic.1)36
9 files changed, 110 insertions, 110 deletions
diff --git a/doc/man/README b/doc/man/README
index 92b2404e..ab432333 100644
--- a/doc/man/README
+++ b/doc/man/README
@@ -26,10 +26,10 @@ ORIGINS
Trolltech-Nokia original sources
(http://get.qt.nokia.com/qt/source/qt-x11-free-3.3.8b.tar.gz)
- man1/lrelease.1
- man1/lupdate.1
- man1/moc.1
- man1/uic.1
+ man1/tqlrelease.1
+ man1/tqlupdate.1
+ man1/tqmoc.1
+ man1/tquic.1
man3/*
Debian distribution
@@ -37,12 +37,12 @@ Debian distribution
qt-x11-free_3.3.8b-11.*
qt-x11-free_3.3.8b.orig.tar.gz
man1/tqtcreatecw.1
- man1/designer.1
+ man1/tqdesigner.1
man1/tqtfindtr.1
- man1/linguist.1
+ man1/tqlinguist.1
man1/maketqpf.1
man1/tqtmergetr.1
man1/msg2tqm.1
- man1/qembed.1
- man1/qtconfig.1
+ man1/tqembed.1
+ man1/tqtconfig.1
man1/tqvfb.1
diff --git a/doc/man/man1/designer.1 b/doc/man/man1/tqdesigner.1
index 32a49cb3..cb760d23 100644
--- a/doc/man/man1/designer.1
+++ b/doc/man/man1/tqdesigner.1
@@ -1,10 +1,10 @@
-.TH "qt-designer" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqtdesigner" "1" "3.0.3" "Troll Tech AS, Norway." ""
.SH "NAME"
.LP
-qt\-designer \- Visual user interface designer for Qt.
+tqtdesigner \- Visual user interface designer for TQt.
.SH "DESCRIPTION"
.LP
-Qt Designer simplifies the process of designing and
+TQt Designer simplifies the process of designing and
creating graphical user interfaces (GUI) using the
award\-winning TQt toolkit. TQt Designer is easy to learn.
There are tutorials, walkthrough examples and the
diff --git a/doc/man/man1/qembed.1 b/doc/man/man1/tqembed.1
index a9b262f1..82255a69 100644
--- a/doc/man/man1/qembed.1
+++ b/doc/man/man1/tqembed.1
@@ -1,16 +1,16 @@
-.TH "qembed" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqembed" "1" "3.0.3" "Troll Tech AS, Norway." ""
.SH "NAME"
.LP
-qembed \- Converts arbitrary files into C++ code.
+tqembed \- Converts arbitrary files into C++ code.
.SH "DESCRIPTION"
.LP
-The QEmbed tool, found in qt/tools/qembed, converts
+The TQEmbed tool, found in tqt3/tools/qembed, converts
arbitrary files into C++ code. This is useful for
including image files and other resources directly into
your application rather than loading the data from
external files.
-QEmbed can also generate uncompressed versions of images
+TQEmbed can also generate uncompressed versions of images
that can be included directly into your application,
thus avoiding both the external file and the need to
parse the image file format. This is useful for small
@@ -19,13 +19,13 @@ great gain.
.SH "SYNTAX"
-qembed [ \fIgeneral\-files\fP ] <[ \fI\-\-images image\-files \fP]>
+tqembed [ \fIgeneral\-files\fP ] <[ \fI\-\-images image\-files \fP]>
.br
general\-files
These files can be any type of file.
\-\-images image\-files
- These files must be in image formats supported by Qt.
+ These files must be in image formats supported by TQt.
.SH "AUTHORS"
.LP
diff --git a/doc/man/man1/linguist.1 b/doc/man/man1/tqlinguist.1
index d8960da9..8aeab518 100644
--- a/doc/man/man1/linguist.1
+++ b/doc/man/man1/tqlinguist.1
@@ -1,9 +1,9 @@
.TH LINGUIST 1 "28 August 2004"
.SH "NAME"
-linguist \- Translation tool for Qt.
+tqlinguist \- Translation tool for TQt.
.SH "SYNPOSIS"
-.B linguist
+.B tqlinguist
[
.I TRANSLATION
]
diff --git a/doc/man/man1/lrelease.1 b/doc/man/man1/tqlrelease.1
index 722e6f5a..fd3abacb 100644
--- a/doc/man/man1/lrelease.1
+++ b/doc/man/man1/tqlrelease.1
@@ -1,4 +1,4 @@
-.TH lrelease 1 "18 October 2001" "Trolltech AS" \" -*- nroff -*-
+.TH tqlrelease 1 "18 October 2001" "Trolltech AS" \" -*- nroff -*-
.\"
.\" Copyright (C) 2001-2007 Trolltech ASA. All rights reserved.
.\"
@@ -28,19 +28,19 @@
.\" herein.
.\"
.SH NAME
-lrelease \- generate TQt message files from TQt Linguist translation files
+tqlrelease \- generate TQt message files from TQt Linguist translation files
.SH SYNOPSIS
-.B lrelease
+.B tqlrelease
.RI "[ " options " ] " project-file
.br
-.B lrelease
+.B tqlrelease
.RI "[ " options " ] " ts-files " [ -qm " qm-file " ]"
.SH DESCRIPTION
This page documents the
.B TQt Linguist Release
tool for the TQt GUI toolkit.
.B Lrelease
-reads a qmake/tmake project file (.pro file) and converts the
+reads a tqmake/tmake project file (.pro file) and converts the
translation files (.ts files) specified in it into TQt message files
(.qm files) used by the application to translate.
.PP
@@ -59,11 +59,11 @@ Explain what is being done.
.TP
.I "-version"
Display the version of
-.B lrelease
+.B tqlrelease
and exit.
.SH USAGE
Here is an example .pro file that can be given to
-.B lrelease:
+.B tqlrelease:
.PP
.in +4
.nf
@@ -81,7 +81,7 @@ TRANSLATIONS = gnomovision_dk.ts \\
.in -4
.PP
When running
-.B lrelease
+.B tqlrelease
on this project file, the TQt message files gnomovision_dk.qm,
gnomovision_fi.qm, gnomovision_no.qm and gnomovision_se.qm will be
generated from gnomovision_dk.ts, gnomovision_fi.ts,
@@ -92,10 +92,10 @@ can also be invoked with a list of .ts files to convert:
.PP
.in +4
.nf
-lrelease gnomovision_*.ts
+tqlrelease gnomovision_*.ts
.fi
.in -4
.SH "SEE ALSO"
-.BR lupdate (1)
+.BR tqlupdate (1)
and
.BR http://doc.trolltech.com/i18n.html
diff --git a/doc/man/man1/lupdate.1 b/doc/man/man1/tqlupdate.1
index 3add01c7..32cc4e14 100644
--- a/doc/man/man1/lupdate.1
+++ b/doc/man/man1/tqlupdate.1
@@ -1,4 +1,4 @@
-.TH lupdate 1 "18 October 2001" "Trolltech AS" \" -*- nroff -*-
+.TH tqlupdate 1 "18 October 2001" "Trolltech AS" \" -*- nroff -*-
.\"
.\" Copyright (C) 2001-2007 Trolltech ASA. All rights reserved.
.\"
@@ -28,19 +28,19 @@
.\" herein.
.\"
.SH NAME
-lupdate \- update TQt Linguist translation files
+tqlupdate \- update TQt Linguist translation files
.SH SYNOPSIS
-.B lupdate
+.B tqlupdate
.RI "[ " options " ] " project-file
.br
-.B lupdate
+.B tqlupdate
.RI "[ " options " ] " source-files " -ts " ts-files
.SH DESCRIPTION
This page documents the
.B TQt Linguist Update
tool for the TQt GUI toolkit.
.B Lupdate
-reads a qmake/tmake project file (.pro file), finds the translatable
+reads a tqmake/tmake project file (.pro file), finds the translatable
strings in the specified source, header and interface files, and
updates the translation files (.ts files) specified in it. The
translation files are given to the translator who uses
@@ -63,11 +63,11 @@ Explain what is being done.
.TP
.I "-version"
Display the version of
-.B lupdate
+.B tqlupdate
and exit.
.SH USAGE
Here is an example .pro file that can be given to
-.B lupdate:
+.B tqlupdate:
.PP
.in +4
.nf
@@ -85,7 +85,7 @@ TRANSLATIONS = gnomovision_dk.ts \\
.in -4
.PP
When running
-.B lupdate
+.B tqlupdate
on this project file, the translatable strings in all the files
listed in the HEADERS, SOURCES and FORMS entries will be put in
the translation files listed in the TRANSLATIONS entry. Previous
@@ -98,10 +98,10 @@ and .ts files:
.PP
.in +4
.nf
-lupdate *.cpp *.h *.ui -ts gnomovision_dk.ts
+tqlupdate *.cpp *.h *.ui -ts gnomovision_dk.ts
.fi
.in -4
.SH "SEE ALSO"
-.BR lrelease (1)
+.BR tqlrelease (1)
and
.BR http://doc.trolltech.com/i18n.html
diff --git a/doc/man/man1/moc.1 b/doc/man/man1/tqmoc.1
index 24ed9690..cbf201a4 100644
--- a/doc/man/man1/moc.1
+++ b/doc/man/man1/tqmoc.1
@@ -1,4 +1,4 @@
-.TH moc 1 "24 June 2001" "Trolltech AS" \" -*- nroff -*-
+.TH tqmoc 1 "24 June 2001" "Trolltech AS" \" -*- nroff -*-
.\"
.\" $Id: qt/moc.1 3.3.8 edited Jan 11 14:38 $
.\"
@@ -9,28 +9,28 @@
.\"
.nh
.SH NAME
-moc \- generate TQt meta object support code
+tqmoc \- generate TQt meta object support code
.SH SYNOPSIS
-.B moc
+.B tqmoc
[-o file] [-i] [-f] [-k] [-ldbg] [-nw] [-p path] [-q path] [-v] file
.SH DESCRIPTION
This page documents the
.B Meta Object Compiler
for the TQt GUI application framework. The
-.B moc
+.B tqmoc
reads one or more C++ class declarations from a C++ header or source
file and generates one C++ source file containing meta object
information for the classes. The C++ source file generated by the
-.B moc
+.B tqmoc
must be compiled and linked with the implementation of the class (or it
can be #included into the class's source file).
.PP
If you use
-.B qmake
+.B tqmake
to create your Makefiles, build rules will be included that call the
-.B moc
+.B tqmoc
when required, so you will not need to use the
-.B moc
+.B tqmoc
directly.
.PP
In brief, the meta object system is a structure used by TQt (see
@@ -61,7 +61,7 @@ standard naming conventions.
.I "-i"
Do not generate an #include statement in the output. This may be used
to run
-.B moc
+.B tqmoc
on a C++ file containing one or more class declarations. You should then
#include the meta object code in the .cpp file (see USAGE below). If both
.I -f
@@ -77,51 +77,51 @@ Write a flood of lex debug information to stdout.
.TP
.I "-p path"
Makes
-.B moc
+.B tqmoc
prepend
.IR path /
to the file name in the generated #include statement (if one is generated).
.TP
.I "-q path"
Makes
-.B moc
+.B tqmoc
prepend
.IR path /
to the file name of qt #include files in the generated code.
.TP
.I "-v"
Displays the version of
-.B moc
-and Qt.
+.B tqmoc
+and TQt.
.PP
You can explicitly tell the
-.B moc
+.B tqmoc
not to parse parts of a header
file. It recognizes any C++ comment (//) that contains the substrings
MOC_SKIP_BEGIN or MOC_SKIP_END. They work as you would expect and you
can have several levels of them. The net result as seen by the
-.B moc
+.B tqmoc
is as if you had removed all lines between a MOC_SKIP_BEGIN and a
MOC_SKIP_END
.SH USAGE
-.B moc
+.B tqmoc
is almost always invoked by
.BR make (1),
not by hand.
.PP
-.B moc
+.B tqmoc
is typically used with an input file containing class declarations
like this:
.PP
.in +4
.nf
-class YourClass : public QObject {
+class YourClass : public TQObject {
TQ_OBJECT
TQ_PROPERTY( ... )
TQ_CLASSINFO( ... )
public:
- YourClass( QObject * parent=0, const char * name=0 );
+ YourClass( TQObject * parent=0, const char * name=0 );
~YourClass();
signals:
@@ -137,7 +137,7 @@ Here is a useful makefile rule if you only use GNU make:
.in +4
.nf
m%.cpp: %.h
- moc $< -o $@
+ tqmoc $< -o $@
.fi
.in -4
.PP
@@ -147,7 +147,7 @@ following form:
.in +4
.nf
mNAME.cpp: NAME.h
- moc $< -o $@
+ tqmoc $< -o $@
.fi
.in -4
.PP
@@ -158,7 +158,7 @@ to your SOURCES (substitute your favorite name) variable and
to your OBJECTS variable.
.PP
(While we prefer to name our C++ source files .cpp, the
-.B moc
+.B tqmoc
doesn't know that, so you can use .C, .cc, .CC, .cxx or even .c++ if
you prefer.)
.PP
@@ -170,14 +170,14 @@ a makefile rule like this:
NAME.o: mNAME.cpp
mNAME.cpp: NAME.cpp
- moc -i $< -o $@
+ tqmoc -i $< -o $@
.fi
.in -4
.PP
This guarantees that
.BR make (1)
will run the
-.B moc
+.B tqmoc
before it compiles
.IR NAME.cpp .
You can then put
@@ -192,29 +192,29 @@ where all the classes declared in that file are fully known.
Sometimes you may get linkage errors, saying that
YourClass::className() is undefined or that YourClass lacks a vtbl.
Those errors happen most often when you forget to compile the
-moc-generated C++ code or include that object file in the link
+tqmoc-generated C++ code or include that object file in the link
command.
.PP
The
-.B moc
+.B tqmoc
will warn you about a number of dangerous or illegal constructs.
.SH BUGS
The
-.B moc
+.B tqmoc
does not expand #include or #define, it simply skips any preprocessor
directives it encounters. This is regrettable, but is normally not a
problem in practice.
The
-.B moc
+.B tqmoc
does not handle all of C++. The main problem is that class templates
cannot have signals or slots. This is an important bug. Here is an
example:
.PP
.in +4
.nf
-class SomeTemplate<int> : public QFrame {
+class SomeTemplate<int> : public TQFrame {
TQ_OBJECT
....
signals:
@@ -226,35 +226,35 @@ signals:
Less importantly, the following constructs are illegal. All of them
have have alternatives which we think are usually better, so removing
these limitations is not a high priority for us.
-.SS "Multiple inheritance requires QObject to be first."
+.SS "Multiple inheritance requires TQObject to be first."
If you are using multiple inheritance,
-.B moc
+.B tqmoc
assumes that the
.B first
-inherited class is a subclass of QObject. Also, be sure that
+inherited class is a subclass of TQObject. Also, be sure that
.B only
-the first inherited class is a QObject.
+the first inherited class is a TQObject.
.PP
.in +4
.nf
-class SomeClass : public QObject, public OtherClass {
+class SomeClass : public TQObject, public OtherClass {
...
};
.fi
.in -4
.PP
This bug is almost impossible to fix; since the
-.B moc
+.B tqmoc
does not expand
#include or #define, it cannot find out which one of the base classes is a
-QObject.
+TQObject.
.SS "Function pointers cannot be arguments to signals or slots."
In most cases where you would consider that, we think inheritance is a
better alternative. Here is an example of illegal syntax:
.PP
.in +4
.nf
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
...
public slots:
@@ -270,7 +270,7 @@ You can work around this restriction like this:
.nf
typedef void (*ApplyFunctionType)( List *, void * );
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
...
public slots:
@@ -295,7 +295,7 @@ sections instead. Here is an example of the illegal syntax:
.PP
.in +4
.nf
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
...
signals:
@@ -311,16 +311,16 @@ example:
.PP
.in +4
.nf
-class Whatever : public QButtonGroup {
+class Whatever : public TQButtonGroup {
...
public slots:
- QButtonGroup::buttonPressed; // illegal
+ TQButtonGroup::buttonPressed; // illegal
...
};
.fi
.in -4
.PP
-The QButtonGroup::buttonPressed() slot is protected.
+The TQButtonGroup::buttonPressed() slot is protected.
.PP
C++ quiz: What happens if you try to upgrade a protected member
function which is overloaded?
@@ -332,7 +332,7 @@ function which is overloaded?
.SS "Type macros cannot be used for signal and slot arguments"
Since the
-.B moc
+.B tqmoc
does not expand #define, type macros that take an argument
will not work in signals and slots. Here is an illegal example:
.PP
@@ -343,7 +343,7 @@ will not work in signals and slots. Here is an illegal example:
#else
#define SIGNEDNESS(a) a
#endif
-class Whatever : public QObject {
+class Whatever : public TQObject {
...
signals:
void someSignal( SIGNEDNESS(int) ); // illegal
@@ -388,11 +388,11 @@ sections, where they belong. Here is an example of the illegal syntax:
.PP
.in +4
.nf
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
public slots:
- SomeClass( QObject *parent, const char *name )
- : QObject( parent, name ) {} // illegal
+ SomeClass( TQObject *parent, const char *name )
+ : TQObject( parent, name ) {} // illegal
...
};
.fi
@@ -402,14 +402,14 @@ public slots:
Declaring the first property within or after the public section that
contains the type definition and the respective get and set functions
does not work as expected. The
-.B moc
+.B tqmoc
will complain that it can neither
find the functions nor resolve the type. Here is an example of the
illegal syntax:
.PP
.in +4
.nf
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
public:
...
@@ -429,7 +429,7 @@ beginning of the class declaration, right after TQ_OBJECT:
.PP
.in +4
.nf
-class SomeClass : public QObject {
+class SomeClass : public TQObject {
TQ_OBJECT
TQ_PROPERTY( Priority priority READ priority WRITE setPriority )
TQ_ENUMS( Priority )
diff --git a/doc/man/man1/qtconfig.1 b/doc/man/man1/tqtconfig.1
index 2e280772..54661333 100644
--- a/doc/man/man1/qtconfig.1
+++ b/doc/man/man1/tqtconfig.1
@@ -1,10 +1,10 @@
-.TH "qtconfig" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqtconfig" "1" "3.0.3" "Troll Tech AS, Norway." ""
.SH "NAME"
.LP
-qtconfig \- Configuration tool for Qt
+tqtconfig \- Configuration tool for TQt
.SH "DESCRIPTION"
.LP
-QConfig allows for GUI based configuration of TQt and
+TQtConfig allows for GUI based configuration of TQt and
other TQt based sources.
.SH "ENVIRONMENT VARIABLES"
diff --git a/doc/man/man1/uic.1 b/doc/man/man1/tquic.1
index 194fc54f..53126fdd 100644
--- a/doc/man/man1/uic.1
+++ b/doc/man/man1/tquic.1
@@ -1,4 +1,4 @@
-.TH uic 1 "2 Aug 2001" "Trolltech AS" \" -*- nroff -*-
+.TH tquic 1 "2 Aug 2001" "Trolltech AS" \" -*- nroff -*-
.\"
.\" Copyright (C) 2000-2007 Trolltech ASA. All rights reserved.
.\"
@@ -6,15 +6,15 @@
.\" the terms and conditions described in the LICENSE file.
.\"
.SH NAME
-uic \- TQt user interface compiler
+tquic \- TQt user interface compiler
.SH SYNOPSIS
-.B uic
+.B tquic
[options] file
.SH DESCRIPTION
This page documents the
.B User Interface Compiler
for the TQt GUI toolkit. The
-.B uic
+.B tquic
reads a user interface definition (.ui) file in XML as generated by
.I TQt Designer
and creates corresponding C++ header or source files. It also
@@ -23,19 +23,19 @@ generates an image file that embeds raw image data in C++ source code.
.PP
Generate declaration:
.br
-.I "\fB uic [options] \fI<file>"
+.I "\fB tquic [options] \fI<file>"
.br
.PP
Generate implementation:
.br
-.I "\fB uic [options] -impl \fI<headerfile> <file>"
+.I "\fB tquic [options] -impl \fI<headerfile> <file>"
.br
\fI<headerfile>\fP: name of the declaration file
.br
.PP
Generate image collection:
.br
-.I "\fB uic [options] -embed \fI<project> <image1> <image2> <image3>\fP ..."
+.I "\fB tquic [options] -embed \fI<project> <image1> <image2> <image3>\fP ..."
.br
\fI<project>\fP: project name
\fI<image[1..n]>\fP: image files
@@ -43,17 +43,17 @@ Generate image collection:
.\" .PP
.\" Generate binary UI file:
.\" .br
-.\" .I "\fB uic [options] -binary \fI<file>"
+.\" .I "\fB tquic [options] -binary \fI<file>"
.\" .br
.PP
.PP
For convenience,
-.B uic
+.B tquic
can also generate declaration or implementation stubs for subclasses.
.PP
Generate subclass declaration:
.br
-.I "\fB uic [options] -subdecl \fI<subclassname> <baseclassheaderfile> <file>"
+.I "\fB tquic [options] -subdecl \fI<subclassname> <baseclassheaderfile> <file>"
.br
\fI<subclassname>\fP: name of the subclass to generate
.br
@@ -61,7 +61,7 @@ Generate subclass declaration:
.PP
Generate subclass implementation:
.br
-.I "\fB uic [options] -subimpl \fI<subclassname> <subclassheaderfile> <file>"
+.I "\fB tquic [options] -subimpl \fI<subclassname> <subclassheaderfile> <file>"
.br
\fI<subclassname>\fP: name of the subclass to generate
.br
@@ -85,11 +85,11 @@ instead of tr() for internationalization.
.TP
.I "-version"
Display the version of
-.B uic
+.B tquic
and exit.
.SH USAGE
-.B uic
+.B tquic
is almost always invoked by
.BR make (1),
rather than by hand.
@@ -99,11 +99,11 @@ Here are useful makefile rules if you only use GNU make:
.in +4
%.h: %.ui
.br
- uic $< -o $@
+ tquic $< -o $@
.br
%.cpp: %.ui
.br
- uic -impl $*.h $< -o $@
+ tquic -impl $*.h $< -o $@
.in -4
.PP
If you want to write portably, you can use individual rules of the
@@ -112,11 +112,11 @@ following form:
.in +4
NAME.h: NAME.ui
.br
- uic $< -o $@
+ tquic $< -o $@
.br
NAME.cpp: NAME.ui
.br
- uic -impl $*.h $< -o $@
+ tquic -impl $*.h $< -o $@
.in -4
.PP
You must also remember to add
@@ -126,7 +126,7 @@ to your SOURCES (substitute your favorite name) variable and
to your OBJECTS variable.
.PP
(While we prefer to name our C++ source files .cpp, the
-.B uic
+.B tquic
doesn't care, so you can use .C, .cc, .CC, .cxx or even .c++ if
you prefer.)
.PP