Hi all, what exactly is responsible for creating the tqmoc targets in automake tools? or where can I read more about it?
thanks
I have following case
make[4]: Entering directory '/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/obj-x86_64-linux-gnu/kdebluetooth/libkbluetooth' rm -rf serviceselectionwidgetbase.h; /usr/bin/uic-tqt -L /opt/trinity/lib/trinity/plugins/designer -nounload /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidgetbase.ui | /usr/bin/perl -pi -e "s,public TQWizard,public KWizard,g; s,#include <ntqwizard.h>,#include <kwizard.h>,g; s,public QWizard,public KWizard,g; s,#include <qwizard.h>,#include <kwizard.h>,g" >> serviceselectionwidgetbase.h ; -i used with no filenames on the command line, reading from STDIN. /usr/bin/tmoc serviceselectionwidgetbase.h -o serviceselectionwidgetbase.moc rm -f serviceselectionwidgetbase.cpp echo '#include <kdialog.h>' > serviceselectionwidgetbase.cpp echo '#include <tdelocale.h>' >> serviceselectionwidgetbase.cpp /usr/bin/uic-tqt -L /opt/trinity/lib/trinity/plugins/designer -nounload -tr tr2i18n -i serviceselectionwidgetbase.h /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidgetbase.ui
serviceselectionwidgetbase.cpp.temp ; ret=$?; \
/usr/bin/perl -pe "s,tr2i18n( "" ),QString::null,g" serviceselectionwidgetbase.cpp.temp | /usr/bin/perl -pe "s,tr2i18n( "", "" ),QString::null,g" | /usr/bin/perl -pe "s,image([0-9 [0-9]*)_data,img$1_serviceselectionwidgetbase,g" | /usr/bin/perl -pe "s,: TQWizard(,: KWizard(,g; s,: QWizard(,: KWizard(,g;" >> serviceselectionwidgetbase.cpp ;\ rm -f serviceselectionwidgetbase.cpp.temp ;\ if test "$ret" = 0; then echo '#include "serviceselectionwidgetbase.moc"' >> serviceselectionwidgetbase.cpp; else rm -f serviceselectionwidgetbase.cpp ; exit $ret ; fi /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/inputmanager.h -o inputmanager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/manager.h -o manager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidget.h -o serviceselectionwidget.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/obexsession.h -o obexsession.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/passkeyagent.h -o passkeyagent.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/hcidefault.h -o hcidefault.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/obexmanager.h -o obexmanager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/authagent.h -o authagent.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/adapter.h -o adapter.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/rfcommsocket.h -o rfcommsocket.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/inputdevice.h -o inputdevice.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/namerequest.h -o namerequest.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/servicediscovery.h -o servicediscovery.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/hcisocket.h -o hcisocket.moc creating libkbluetooth_la.all_cpp.cpp ... /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth -I../.. -I/opt/trinity/include -I/usr/share/tqt3/include -I. -include tqt.h -I/usr/include/dbus-1-tqt -I. -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o libkbluetooth_la.all_cpp.lo libkbluetooth_la.all_cpp.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth -I../.. -I/opt/trinity/include -I/usr/share/tqt3/include -I. -include tqt.h -I/usr/include/dbus-1-tqt -I. -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c libkbluetooth_la.all_cpp.cpp -fPIC -DPIC -o .libs/libkbluetooth_la.all_cpp.o In file included from libkbluetooth_la.all_cpp.cpp:4:0: /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/dbusinit.cpp:71:24: fatal error: dbusinit.moc: No such file or directory #include "dbusinit.moc" ^ compilation terminated. Makefile:692: recipe for target 'libkbluetooth_la.all_cpp.lo' failed
On 2016/12/06 04:47 AM, deloptes wrote:
Hi all, what exactly is responsible for creating the tqmoc targets in automake tools? or where can I read more about it?
thanks
I have following case
make[4]: Entering directory '/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/obj-x86_64-linux-gnu/kdebluetooth/libkbluetooth' rm -rf serviceselectionwidgetbase.h; /usr/bin/uic-tqt -L /opt/trinity/lib/trinity/plugins/designer -nounload /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidgetbase.ui | /usr/bin/perl -pi -e "s,public TQWizard,public KWizard,g; s,#include <ntqwizard.h>,#include <kwizard.h>,g; s,public QWizard,public KWizard,g; s,#include <qwizard.h>,#include <kwizard.h>,g" >> serviceselectionwidgetbase.h ; -i used with no filenames on the command line, reading from STDIN. /usr/bin/tmoc serviceselectionwidgetbase.h -o serviceselectionwidgetbase.moc rm -f serviceselectionwidgetbase.cpp echo '#include <kdialog.h>' > serviceselectionwidgetbase.cpp echo '#include <tdelocale.h>' >> serviceselectionwidgetbase.cpp /usr/bin/uic-tqt -L /opt/trinity/lib/trinity/plugins/designer -nounload -tr tr2i18n -i serviceselectionwidgetbase.h /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidgetbase.ui
serviceselectionwidgetbase.cpp.temp ; ret=$?; \
/usr/bin/perl -pe "s,tr2i18n( "" ),QString::null,g" serviceselectionwidgetbase.cpp.temp | /usr/bin/perl -pe "s,tr2i18n( "", "" ),QString::null,g" | /usr/bin/perl -pe "s,image([0-9 [0-9]*)_data,img$1_serviceselectionwidgetbase,g" | /usr/bin/perl -pe "s,: TQWizard(,: KWizard(,g; s,: QWizard(,: KWizard(,g;" >> serviceselectionwidgetbase.cpp ;\ rm -f serviceselectionwidgetbase.cpp.temp ;\ if test "$ret" = 0; then echo '#include "serviceselectionwidgetbase.moc"' >> serviceselectionwidgetbase.cpp; else rm -f serviceselectionwidgetbase.cpp ; exit $ret ; fi /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/inputmanager.h -o inputmanager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/manager.h -o manager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/serviceselectionwidget.h -o serviceselectionwidget.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/obexsession.h -o obexsession.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/passkeyagent.h -o passkeyagent.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/hcidefault.h -o hcidefault.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/obexmanager.h -o obexmanager.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/authagent.h -o authagent.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/adapter.h -o adapter.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/rfcommsocket.h -o rfcommsocket.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/inputdevice.h -o inputdevice.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/namerequest.h -o namerequest.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/servicediscovery.h -o servicediscovery.moc /usr/bin/tmoc /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/hcisocket.h -o hcisocket.moc creating libkbluetooth_la.all_cpp.cpp ... /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth -I../.. -I/opt/trinity/include -I/usr/share/tqt3/include -I. -include tqt.h -I/usr/include/dbus-1-tqt -I. -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o libkbluetooth_la.all_cpp.lo libkbluetooth_la.all_cpp.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I/opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth -I../.. -I/opt/trinity/include -I/usr/share/tqt3/include -I. -include tqt.h -I/usr/include/dbus-1-tqt -I. -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c libkbluetooth_la.all_cpp.cpp -fPIC -DPIC -o .libs/libkbluetooth_la.all_cpp.o In file included from libkbluetooth_la.all_cpp.cpp:4:0: /opt/software_x64/KDE/bluetooth/kdebluetooth-1.0_beta8/./kdebluetooth/libkbluetooth/dbusinit.cpp:71:24: fatal error: dbusinit.moc: No such file or directory #include "dbusinit.moc" ^ compilation terminated. Makefile:692: recipe for target 'libkbluetooth_la.all_cpp.lo' failed
moc files are created by tqmake before the actual compilation. You need to add the the Q_OBJECT "declaration" inside a class to get the moc file generated. See here for more info: https://www.trinitydesktop.org/docs/qt3/object.html Cheers Michele
Michele Calgaro wrote:
moc files are created by tqmake before the actual compilation. You need to add the the Q_OBJECT "declaration" inside a class to get the moc file generated. See here for more info: https://www.trinitydesktop.org/docs/qt3/object.html Cheers Michele
Thanks Michele, I was thinking that TQ_OBJECT is the correct one for TDE, at least compiler did not complain. I also think that whole dbus should be moved to dbus-1-tqt, what is your opinion? ATM the classes in kbluetooth are wrappers around dbus. Also what are the plans for supporting gdbus? I discussed time ago with SyncEvolution and they stated gdbus is the preferred one? I'm just asking, so that what I do holds for the future.
Thanks and regards
On Tuesday 06 of December 2016 08:50:47 deloptes wrote:
Michele Calgaro wrote:
moc files are created by tqmake before the actual compilation. You need to add the the Q_OBJECT "declaration" inside a class to get the moc file generated. See here for more info: https://www.trinitydesktop.org/docs/qt3/object.html Cheers Michele
Thanks Michele, I was thinking that TQ_OBJECT is the correct one for TDE, at least compiler did not complain. I also think that whole dbus should be moved to dbus-1-tqt, what is your opinion? ATM the classes in kbluetooth are wrappers around dbus. Also what are the plans for supporting gdbus? I discussed time ago with SyncEvolution and they stated gdbus is the preferred one? I'm just asking, so that what I do holds for the future.
Thanks and regards
In connection with this you might find useful:
http://bugs.trinitydesktop.org/show_bug.cgi?id=2673
On 2016/12/06 04:56 PM, Slávek Banko wrote:
On Tuesday 06 of December 2016 08:50:47 deloptes wrote:
Michele Calgaro wrote:
moc files are created by tqmake before the actual compilation. You need to add the the Q_OBJECT "declaration" inside a class to get the moc file generated. See here for more info: https://www.trinitydesktop.org/docs/qt3/object.html Cheers Michele
Thanks Michele, I was thinking that TQ_OBJECT is the correct one for TDE, at least compiler did not complain. I also think that whole dbus should be moved to dbus-1-tqt, what is your opinion? ATM the classes in kbluetooth are wrappers around dbus. Also what are the plans for supporting gdbus? I discussed time ago with SyncEvolution and they stated gdbus is the preferred one? I'm just asking, so that what I do holds for the future.
Thanks and regards
In connection with this you might find useful:
See the bug indicated by Slavek for more info about TQ_OBJECT/Q_OBJECT.
Regarding gdubs, I think (and I am quite sure I already sent some email to your previous question some months ago) it would be hard to move to gdbus since this originated from the gnome world. Of course final decision is up to Tim, but I would be surprise if he decides to ditch dbus-tqt for gdbus.
Cheers Michele
Michele Calgaro wrote:
See the bug indicated by Slavek for more info about TQ_OBJECT/Q_OBJECT.
I read it, yes it is very good explained.
Regarding gdubs, I think (and I am quite sure I already sent some email to your previous question some months ago) it would be hard to move to gdbus since this originated from the gnome world. Of course final decision is up to Tim, but I would be surprise if he decides to ditch dbus-tqt for gdb
Ah I suspected that g is there for gnome but I was not sure. Well so it is also self explaining.
Anyway, thanks for the information. Both was pretty instructive.
regards