qt -> tqt conversion:

qtlib -> tqtlib
libqt -> libtqt
QTLIB -> TQTLIB
LIBQT -> LIBTQT

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
pull/4/head
Michele Calgaro 6 years ago
parent ff63338d18
commit 9f5d59f336
Signed by: MicheleC
GPG Key ID: 2A75B7CA8ADED5CF

@ -94,7 +94,7 @@ the directories where you choose to install Qt.
At this point you have binaries created in $QTDIR (eg. $QTDIR/lib/
contains libqt.so). If, however, you would like to have your Qt
contains libtqt.so). If, however, you would like to have your Qt
installed in a non-local installation you can run configure with
options splitting TQt into different areas for example:
@ -117,7 +117,7 @@ the directories where you choose to install Qt.
If you have problems running the example programs, e.g. messages like
can't load library 'libqt.so.3'
can't load library 'libtqt.so.3'
you probably need to put a reference to the qt library in a
configuration file and run /sbin/ldconfig as root on your system.

@ -117,7 +117,7 @@ General
name is still kept as 'input' for backward compatibility
- Changed XIM input method to a plugin instead of directly link into
libqt
libtqt
- Plugin directory has been changed from $QTDIR/plugins/input/ to
$QTDIR/plugins/inputmethods/. Replace install directory with new

4
configure vendored

@ -1903,8 +1903,8 @@ Configure options:
* -release ........... Compile and link TQt with debugging turned off.
-debug ............. Compile and link TQt with debugging turned on.
* -shared ............ Create and use a shared TQt library (libqt.so).
-static ............ Create and use a static TQt library (libqt.a).
* -shared ............ Create and use a shared TQt library (libtqt.so).
-static ............ Create and use a static TQt library (libtqt.a).
* -no-gif ............ Do not compile in GIF reading support.
-qt-gif ............ Compile in GIF reading support.

@ -76,8 +76,8 @@ The library is in provided by the following platform specific files:
\table
\header \i Platform \i File
\row \i Windows \i \c qt[version].dll
\row \i Unix/Linux \i \c libqt[version].so
\row \i Mac \i \c libqt[version].dylib
\row \i Unix/Linux \i \c libtqt[version].so
\row \i Mac \i \c libtqt[version].dylib
\endtable
\e version includes the three version numbers. For threaded builds the

@ -162,10 +162,10 @@ you're using, or make links to the libraries in a standard directory like
<tt>/usr/local/lib</tt>:
<p> <pre>
cd /usr/local/lib
ln -s /opt/qt-2.3.1/lib/libqt.so.2 .
ln -s /opt/qt-2.3.1/lib/libtqt.so.2 .
ln -s /opt/qt-2.3.1/lib/libtqt-mt.so.2 .
ln -s /opt/qt-2.3.1/lib/libqutil.so.1 .
ln -s /opt/qt-3.0.0/lib/libqt.so.3 .
ln -s /opt/qt-3.0.0/lib/libtqt.so.3 .
ln -s /opt/qt-3.0.0/lib/libtqui.so.1 .
</pre>

@ -74,8 +74,8 @@ path.
<p> <center><table cellpadding="4" cellspacing="2" border="0">
<tr bgcolor="#a2c511"> <th valign="top">Platform <th valign="top">File
<tr bgcolor="#f0f0f0"> <td valign="top">Windows <td valign="top"><tt>qt[version].dll</tt>
<tr bgcolor="#d0d0d0"> <td valign="top">Unix/Linux <td valign="top"><tt>libqt[version].so</tt>
<tr bgcolor="#f0f0f0"> <td valign="top">Mac <td valign="top"><tt>libqt[version].dylib</tt>
<tr bgcolor="#d0d0d0"> <td valign="top">Unix/Linux <td valign="top"><tt>libtqt[version].so</tt>
<tr bgcolor="#f0f0f0"> <td valign="top">Mac <td valign="top"><tt>libtqt[version].dylib</tt>
</table></center>
<p> <em>version</em> includes the three version numbers. For threaded builds the
version is prefixed with <em>-mt</em>.

@ -60,9 +60,9 @@ user invokes it).
</h2>
<a name="2"></a><p> A lot of CPU and memory is used by the ELF linking process. You can
make significant savings by using a static build of your application
suite. This means that rather than having a dynamic library (<tt>libqte.so</tt>) and a collection of executables which link dynamically to
suite. This means that rather than having a dynamic library (<tt>libtqte.so</tt>) and a collection of executables which link dynamically to
that library, you build all the applications into a single executable
and statically link that with a static library (<tt>libqt.a</tt>). This
and statically link that with a static library (<tt>libtqt.a</tt>). This
improves start-up time, and reduces memory usage, at the expense of
flexibility (to add a new application, you must recompile the single
executable) and robustness (if one application has a bug, it might

@ -106,9 +106,9 @@ configured with the -static option, then in order to be able to
launch TQt applications from the Finder you must place the relevant
libraries in a directory where they can be found. We recommend
making these symbolic links (if you have configured TQt with -thread
please change the libqt below with libtqt-mt):
please change the libtqt below with libtqt-mt):
<p> <pre>
ln -sf $QTDIR/lib/libqt.3.dylib /usr/lib
ln -sf $QTDIR/lib/libtqt.3.dylib /usr/lib
ln -sf $QTDIR/lib/libtqui.1.dylib /usr/lib
</pre>
@ -117,10 +117,10 @@ case, precede each command with <tt>sudo'</tt>, e.g. <tt>sudo ln -s ...</tt>). I
you use sudo you'll be prompted for the administrator password.
<p> If you do not have administrator access, or you would prefer to do
a user install (rather than system install) of the libraries you
can do (if you have configured TQt with -thread please change the libqt
can do (if you have configured TQt with -thread please change the libtqt
below with libtqt-mt):
<p> <pre>
ln -sf $QTDIR/lib/libqt.3.dylib $HOME/lib
ln -sf $QTDIR/lib/libtqt.3.dylib $HOME/lib
ln -sf $QTDIR/lib/libtqui.1.dylib $HOME/lib
</pre>

@ -112,7 +112,7 @@ If you have problems, see
similar at this point if you are using shared libraries.
<p> If you have problems running the example programs, e.g. messages like
<pre>
can't load library 'libqt.so.2'
can't load library 'libtqt.so.2'
</pre>
you probably need to put a reference to the qt library in a

@ -781,8 +781,8 @@ class TQDataStream;
//
// Feature subsetting
//
// Note that disabling some features will produce a libqt that is not
// compatible with other libqt builds. Such modifications are only
// Note that disabling some features will produce a libtqt that is not
// compatible with other libtqt builds. Such modifications are only
// supported on TQt/Embedded where reducing the library size is important
// and where the application-suite is often a fixed set.
//

@ -152,7 +152,7 @@ where you choose to install Qt.
If you have problems running the example programs, e.g. messages like
\code
can't load library 'libqt.so.2'
can't load library 'libtqt.so.2'
\endcode
you probably need to put a reference to the qt library in a
configuration file and run \c /sbin/ldconfig as root on your system.
@ -271,10 +271,10 @@ the directories where you choose to install Qt.
launch TQt applications from the Finder you must place the relevant
libraries in a directory where they can be found. We recommend
making these symbolic links (if you have configured TQt with -thread
please change the libqt below with libtqt-mt):
please change the libtqt below with libtqt-mt):
\code
ln -sf $QTDIR/lib/libqt.3.dylib /usr/lib
ln -sf $QTDIR/lib/libtqt.3.dylib /usr/lib
ln -sf $QTDIR/lib/libtqui.1.dylib /usr/lib
\endcode
@ -284,11 +284,11 @@ the directories where you choose to install Qt.
If you do not have administrator access, or you would prefer to do
a user install (rather than system install) of the libraries you
can do (if you have configured TQt with -thread please change the libqt
can do (if you have configured TQt with -thread please change the libtqt
below with libtqt-mt):
\code
ln -sf $QTDIR/lib/libqt.3.dylib $HOME/lib
ln -sf $QTDIR/lib/libtqt.3.dylib $HOME/lib
ln -sf $QTDIR/lib/libtqui.1.dylib $HOME/lib
\endcode
\endlist

@ -207,10 +207,10 @@ you're using, or make links to the libraries in a standard directory like
\code
cd /usr/local/lib
ln -s /opt/qt-2.3.1/lib/libqt.so.2 .
ln -s /opt/qt-2.3.1/lib/libtqt.so.2 .
ln -s /opt/qt-2.3.1/lib/libtqt-mt.so.2 .
ln -s /opt/qt-2.3.1/lib/libqutil.so.1 .
ln -s /opt/qt-3.0.0/lib/libqt.so.3 .
ln -s /opt/qt-3.0.0/lib/libtqt.so.3 .
ln -s /opt/qt-3.0.0/lib/libtqui.so.1 .
\endcode

@ -567,9 +567,9 @@ The following guidelines will improve CPU performance:
A lot of CPU and memory is used by the ELF linking process. You can
make significant savings by using a static build of your application
suite. This means that rather than having a dynamic library (\c
libqte.so) and a collection of executables which link dynamically to
libtqte.so) and a collection of executables which link dynamically to
that library, you build all the applications into a single executable
and statically link that with a static library (\c libqt.a). This
and statically link that with a static library (\c libtqt.a). This
improves start-up time, and reduces memory usage, at the expense of
flexibility (to add a new application, you must recompile the single
executable) and robustness (if one application has a bug, it might

@ -59,7 +59,7 @@ QMAKE_LIBS_DYNLOAD = -llibdl
QMAKE_LIBS_X11 = -llibXext -llibX11 -llibm
QMAKE_LIBS_X11SM = -llibSM -llibICE
QMAKE_LIBS_NIS = -llibnsl
QMAKE_LIBS_QT = -llibqt
QMAKE_LIBS_QT = -llibtqt
QMAKE_LIBS_QT_THREAD = -llibtqt-mt
QMAKE_LIBS_OPENGL = -llibGLU -llibGL -llibXmu
QMAKE_LIBS_OPENGL_QT = -llibGL -llibXmu

@ -1545,7 +1545,7 @@ UnixMakefileGenerator::pkgConfigFixPath(TQString path) const
}
void
UnixMakefileGenerator::writePkgConfigFile() // ### does make sense only for libqt so far
UnixMakefileGenerator::writePkgConfigFile() // ### does make sense only for libtqt so far
{
TQString fname = pkgConfigFileName(), lname = fname;
int slsh = lname.findRev(Option::dir_sep);

@ -27,9 +27,9 @@ static TQCString findLibrary()
|| getenv( "QT_NO_KDE_INTEGRATION" )[ 0 ] == '0' )
{
#ifdef USE_LIB64_PATHES
return "/opt/kde3/lib64/kde3/plugins/integration/libqtkde";
return "/opt/kde3/lib64/kde3/plugins/integration/libtqtkde";
#else
return "/opt/kde3/lib/kde3/plugins/integration/libqtkde";
return "/opt/kde3/lib/kde3/plugins/integration/libtqtkde";
#endif
}
return "";

@ -21,8 +21,8 @@ win32-borland {
}
linux-*:version_script {
QMAKE_LFLAGS += -Wl,--version-script=libqt.map
TARGETDEPS += libqt.map
QMAKE_LFLAGS += -Wl,--version-script=libtqt.map
TARGETDEPS += libtqt.map
}
KERNEL_CPP = kernel

@ -749,8 +749,8 @@ class TQDataStream;
//
// Feature subsetting
//
// Note that disabling some features will produce a libqt that is not
// compatible with other libqt builds. Such modifications are only
// Note that disabling some features will produce a libtqt that is not
// compatible with other libtqt builds. Such modifications are only
// supported on TQt/Embedded where reducing the library size is important
// and where the application-suite is often a fixed set.
//

@ -4,8 +4,8 @@
/*
Empty leaves all features enabled. See doc/html/features.html for choices.
Note that disabling some features will produce a libqt that is not
compatible with other libqt builds. Such modifications are only
Note that disabling some features will produce a libtqt that is not
compatible with other libtqt builds. Such modifications are only
supported on TQt/Embedded where reducing the library size is important
and where the application-suite is often a fixed set.
*/

Loading…
Cancel
Save