Hello, When I compile tqtinterface under Slackware64 13.37 (KDE4 is installed, no Qt3) with Qt4 support, it produces a wrong tqt.pc: ========== $ cmake ../dependencies/tqtinterface/ -DCMAKE_INSTALL_PREFIX=/opt/trinity -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_QT4=ON -DQTDIR=/opt/qt -DQT_LIBRARY_DIRS=/opt/qt/lib -DBUILD_ALL=ON -DLIB_SUFFIX=64 ========== followed by make -j5 and standard installation (via Slackware packages) produces the following /usr/lib64/pkgconfig/tqt.pc: ========== prefix=/opt/trinity exec_prefix=${prefix} libdir=${prefix}/lib64 includedir=${prefix}/include/tqt
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc uic_executable=
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/qt4 -I${includedir} -include tqt.h =========== The uic_executable is not defined, causing arts failing to build. =========== $ which uic /usr/bin/uic =========== shows that uic is really installed on my system.
Le Thu, 5 May 2011 20:20:14 +0200, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Hello, When I compile tqtinterface under Slackware64 13.37 (KDE4 is installed, no Qt3) with Qt4 support, it produces a wrong tqt.pc: ========== $ cmake ../dependencies/tqtinterface/ -DCMAKE_INSTALL_PREFIX=/opt/trinity -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_QT4=ON -DQTDIR=/opt/qt -DQT_LIBRARY_DIRS=/opt/qt/lib
-DBUILD_ALL=ON -DLIB_SUFFIX=64
followed by make -j5 and standard installation (via Slackware packages) produces the following /usr/lib64/pkgconfig/tqt.pc: ========== prefix=/opt/trinity exec_prefix=${prefix} libdir=${prefix}/lib64 includedir=${prefix}/include/tqt
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc uic_executable=
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/include/qt4 -I${includedir} -include tqt.h
The uic_executable is not defined, causing arts failing to build.
$ which uicopt/trinity/include/tqt/Qt/qglobal.h /usr/bin/uic =========== shows that uic is really installed on my system.
Also, it installs includes in locations such as /opt/trinity/include/tqt/Qt/qglobal.h while /opt/trinity/include/tqt/tqt.h #include's such headers as <tqt4/Qt/qglobal.h> (the tqt/Qt/*.h installed headers are Qt4-related ones for sure since there are Qt3-compatibility headers such as /opt/trinity/include/tqt/Qt/q3cstring.h).
Le Thu, 5 May 2011 20:20:14 +0200, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Hello, When I compile tqtinterface under Slackware64 13.37 (KDE4 is installed, no Qt3) with Qt4 support, it produces a wrong tqt.pc: ========== $ cmake ../dependencies/tqtinterface/ -DCMAKE_INSTALL_PREFIX=/opt/trinity -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_QT4=ON -DQTDIR=/opt/qt -DQT_LIBRARY_DIRS=/opt/qt/lib
-DBUILD_ALL=ON -DLIB_SUFFIX=64
followed by make -j5 and standard installation (via Slackware packages) produces the following /usr/lib64/pkgconfig/tqt.pc: ========== prefix=/opt/trinity exec_prefix=${prefix} libdir=${prefix}/lib64 includedir=${prefix}/include/tqt
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc uic_executable=
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/include/qt4 -I${includedir} -include tqt.h
The uic_executable is not defined, causing arts failing to build.
$ which uicopt/trinity/include/tqt/Qt/qglobal.h /usr/bin/uic =========== shows that uic is really installed on my system.
Also, it installs includes in locations such as /opt/trinity/include/tqt/Qt/qglobal.h while /opt/trinity/include/tqt/tqt.h #include's such headers as <tqt4/Qt/qglobal.h> (the tqt/Qt/*.h installed headers are Qt4-related ones for sure since there are Qt3-compatibility headers such as /opt/trinity/include/tqt/Qt/q3cstring.h).
TQt4 has not even reached alpha yet; these kinds of (relatively minor) problems are fully expected.
The primary focus at the moment is on the CMake conversion and getting the Trinity modules to build against the TQt4 packages that are automatically built under Ubuntu.
Tim
Le Thu, 5 May 2011 13:37:36 -0500, "Timothy Pearson" kb9vqf@pearsoncomputing.net a écrit :
Le Thu, 5 May 2011 20:20:14 +0200, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Hello, When I compile tqtinterface under Slackware64 13.37 (KDE4 is installed, no Qt3) with Qt4 support, it produces a wrong tqt.pc: ========== $ cmake ../dependencies/tqtinterface/ -DCMAKE_INSTALL_PREFIX=/opt/trinity -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_QT4=ON -DQTDIR=/opt/qt -DQT_LIBRARY_DIRS=/opt/qt/lib
-DBUILD_ALL=ON -DLIB_SUFFIX=64
followed by make -j5 and standard installation (via Slackware packages) produces the following /usr/lib64/pkgconfig/tqt.pc: ========== prefix=/opt/trinity exec_prefix=${prefix} libdir=${prefix}/lib64 includedir=${prefix}/include/tqt
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc uic_executable=
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/include/qt4 -I${includedir} -include tqt.h
The uic_executable is not defined, causing arts failing to build.
$ which uicopt/trinity/include/tqt/Qt/qglobal.h /usr/bin/uic =========== shows that uic is really installed on my system.
Also, it installs includes in locations such as /opt/trinity/include/tqt/Qt/qglobal.h while /opt/trinity/include/tqt/tqt.h #include's such headers as <tqt4/Qt/qglobal.h> (the tqt/Qt/*.h installed headers are Qt4-related ones for sure since there are Qt3-compatibility headers such as /opt/trinity/include/tqt/Qt/q3cstring.h).
TQt4 has not even reached alpha yet; these kinds of (relatively minor) problems are fully expected.
I have finally managed to manage arts CMake to pass the TQt sanity test. Just FYI, here is what I have done after having installed tqtinterface: -make a /opt/trinity/include/tqt/tqt4 -> /opt/trinity/include/tqt symlink -change /usr/lib64/trinity/tqt.pc with the following modifications: ========== --- tqt.pc 2011-05-05 19:58:50.000000000 +0200 +++ tqt-correct.pc 2011-05-05 21:15:35.944199349 +0200 @@ -5,11 +5,11 @@
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc -uic_executable= +uic_executable=/usr/bin/uic
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 -Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui -Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/qt4 -I${includedir} -include tqt.h +Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui -lQt3Support +Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/qt4 -I/opt/trinity/include -I${includedir} -include tqt.h ========== Don't know why the flags and uic_executable are fscked up, neither why QT_NO_COMPAT is defined while the main tqt.h #include's q3*.h stuff (but perhaps the latter is right, I don't know).
The primary focus at the moment is on the CMake conversion and getting the Trinity modules to build against the TQt4 packages that are automatically built under Ubuntu.
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 05 May 2011 22:26:58 /dev/ammo42 wrote: [...]
-change /usr/lib64/trinity/tqt.pc with the following modifications:
--- tqt.pc 2011-05-05 19:58:50.000000000 +0200 +++ tqt-correct.pc 2011-05-05 21:15:35.944199349 +0200 @@ -5,11 +5,11 @@
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc -uic_executable= +uic_executable=/usr/bin/uic
It's wrong, TQt4 is not using Qt4's uic, but it's own version (ui files still Qt3 and cannot be parsed by qt4-uic).
Le Thu, 5 May 2011 22:30:40 +0300, Serghei Amelian serghei@thel.ro a écrit :
On Thursday 05 May 2011 22:26:58 /dev/ammo42 wrote: [...]
-change /usr/lib64/trinity/tqt.pc with the following modifications:
--- tqt.pc 2011-05-05 19:58:50.000000000 +0200 +++ tqt-correct.pc 2011-05-05 21:15:35.944199349 +0200 @@ -5,11 +5,11 @@
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc -uic_executable= +uic_executable=/usr/bin/uic
It's wrong, TQt4 is not using Qt4's uic, but it's own version (ui files still Qt3 and cannot be parsed by qt4-uic).
Thank you for the advice :) -uic_executable=/usr/bin/uic +uic_executable=/opt/trinity/bin/uic-tqt
Le Thu, 5 May 2011 13:37:36 -0500, "Timothy Pearson" kb9vqf@pearsoncomputing.net a écrit :
Le Thu, 5 May 2011 20:20:14 +0200, /dev/ammo42 mickeytintincolle@yahoo.fr a écrit :
Hello, When I compile tqtinterface under Slackware64 13.37 (KDE4 is installed, no Qt3) with Qt4 support, it produces a wrong tqt.pc: ========== $ cmake ../dependencies/tqtinterface/ -DCMAKE_INSTALL_PREFIX=/opt/trinity -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_QT4=ON -DQTDIR=/opt/qt -DQT_LIBRARY_DIRS=/opt/qt/lib
-DBUILD_ALL=ON -DLIB_SUFFIX=64
followed by make -j5 and standard installation (via Slackware packages) produces the following /usr/lib64/pkgconfig/tqt.pc: ========== prefix=/opt/trinity exec_prefix=${prefix} libdir=${prefix}/lib64 includedir=${prefix}/include/tqt
tmoc_executable=/opt/trinity/bin/tmoc moc_executable=/usr/bin/moc uic_executable=
Name: TQt Description: Interface and abstraction library for Qt and Trinity Version: 3.5.13 Libs: -L${libdir} -ltqt -L/usr/lib64 -lQtCore -lQtGui Cflags: -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/include/qt4 -I${includedir} -include tqt.h
The uic_executable is not defined, causing arts failing to build.
$ which uicopt/trinity/include/tqt/Qt/qglobal.h /usr/bin/uic =========== shows that uic is really installed on my system.
Also, it installs includes in locations such as /opt/trinity/include/tqt/Qt/qglobal.h while /opt/trinity/include/tqt/tqt.h #include's such headers as <tqt4/Qt/qglobal.h> (the tqt/Qt/*.h installed headers are Qt4-related ones for sure since there are Qt3-compatibility headers such as /opt/trinity/include/tqt/Qt/q3cstring.h).
TQt4 has not even reached alpha yet; these kinds of (relatively minor) problems are fully expected.
The primary focus at the moment is on the CMake conversion and getting the Trinity modules to build against the TQt4 packages that are automatically built under Ubuntu.
Here is the patch needed to build arts with TQt4: Index: qtmcop/qiomanager.cc =================================================================== --- qtmcop/qiomanager.cc (révision 1230499) +++ qtmcop/qiomanager.cc (copie de travail) @@ -156,9 +156,9 @@ else { if(blocking) - tqApp->processOneEvent(); + qApp->processOneEvent(); else - tqApp->processEvents(0); + qApp->processEvents(0); } }
Index: qtmcop/qiomanager_p.h =================================================================== --- qtmcop/qiomanager_p.h (révision 1230499) +++ qtmcop/qiomanager_p.h (copie de travail) @@ -40,7 +40,7 @@
class QIOWatch : public TQObject { Q_OBJECT - TQ_OBJECT +// TQ_OBJECT protected: TQSocketNotifier *qsocketnotify; int _fd; @@ -62,7 +62,7 @@
class QTimeWatch : public TQObject { Q_OBJECT - TQ_OBJECT +// TQ_OBJECT protected: TQTimer *timer; TimeNotify *_client;
artsd runs, but I didn't test it further for now. Is TQ_OBJECT really useful now ? It's not defined by TQt4 and defined to nothing by TQt3.
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
/dev/ammo42 -
Serghei Amelian -
Timothy Pearson