24 Jan
2012
24 Jan
'12
7:06 p.m.
On Tue, 24 Jan 2012 10:47:27 -0800 (PST)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
Do you use the
right moc ? I don't know how the new TQt3 works but if
the qt3 moc is used and nothing is done after that the generated .moc
file will use Q* classes rather than TQ* classes.
dcopclient.cpp:2288 contains the following:
#include <dcopclient.moc>
So the failure is in that moc file. I don't pretend to
understand moc files (yet), but I believe the moc files are
created by the qt3 compiler.
kstyle.cpp:2370 contains #include "kstyle.moc". So once
again the problem is a moc file.
I can manually edit these moc files to add a "T" prefix to any
undeclared "Q" functions referenced in the error messages. Then
manually runmake again (outside my build script) and the errors stop.
Of course, I then run into a new set of similar errors. I can repeat
this process with success but there is no way to automate the process.
I think I have narrowed the problem to how the moc files are being
created. I don't know whether that is related to TQT_REAL_TQT.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)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