trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

What controls generation of '.moc' files?

From: "David C. Rankin" <drankinatty@...>
Date: Fri, 23 Mar 2012 11:03:49 -0500
Guys,

   I am trying to understand build failures in tdeaddons, tdegames and tdetoys 
(and probably all other autoconf sources). Each of the packages fails during 
make of the very first file that requires a .moc file:

   tdeaddons:

make[4]: Entering directory
`/build/src/tdeaddons/kaddressbook-plugins/xxports/kworldclock'
<snip>
geo_xxport.cpp:114:26: fatal error: geo_xxport.moc: No such file or directory 
compilation terminated.


   tdegames:

make[3]: Entering directory `/build/src/tdegames/libtdegames/highscore'
<snip>
kconfigrawbackend.cpp:21:33: fatal error: kconfigrawbackend.moc: No such file 
or directory compilation terminated.


   tdetoys:

make[3]: Entering directory `/build/src/tdetoys/amor'
<snip>
amordialog.cpp:35:26: fatal error: amordialog.moc: No such file or directory 
compilation terminated.

   In all 3 cases, the first time the build looks for a .moc file, it is not 
there. I am completely lost on this one. I have re-read HowToBuild, I have 
search for "moc files not generated" and all I find is a reference to a cmake 
QT_AUTOMOC flag that isn't relevant to autoconf.

   How are the moc files generated? Is there some flag I can set or add that 
would show what is going on? Need help here...

-- 
David C. Rankin, J.D.,P.E.