Re: [CMake] QT4_WRAP_CPP and Implicit Dependencies

2012-10-12 Thread Andreas Pakulat
Hi, in addition to that, moc does not support ifdef'ing of code it needs to look at (it does not have a preprocessor at all, only knows a few select define's), so there can also not be a case of Dum.h setting defines which cause moc to generate different code for Main.h. I'd say qmake is just too

Re: [CMake] QT4_WRAP_CPP and Implicit Dependencies

2012-10-12 Thread Clinton Stimpson
If you run moc on Main.h, which includes Dum.h, moc doesn't even open "Dum.h" to scan its contents. That tells me there is no way that moc would be required to rescan Main.h if Dum.h is modified. Clint On Oct 10, 2012, at 10:32 PM, Miller, Frank wrote: > Greetings, > > Suppose we have a head

[CMake] QT4_WRAP_CPP and Implicit Dependencies

2012-10-10 Thread Miller, Frank
Greetings, Suppose we have a header file, Dum.h, that is included by another header file, Main.h, and Main.h needs to be processed with the qt moc tool. When Dum.h changes, should we rerun moc on Main.h? QMake says yes. CMake, using QT4_WRAP_CPP, says no. I am inclined to believe qmake on this o