On Saturday 07 July 2007, Matthias Kretz wrote: > Instead of creating a <targetname>.automoc file that is added to the target I > create a <targetname>_automoc.cpp file now that is compiled and linked into > the target. This file #includes all moc files that are not included by other > source files. This way the automoc can, at make-time, decide what mocs need > to be compiled explicitly and linked into the target.
Does this solve the following problem? I renamed a header file (say foo.h to bar.h), and with the current code (foo.automoc created), I got some dependency error on foo.automoc. Thanks for your excellent work on this topic. Next step, putting moc's own code into kde4automoc? :-P Just kidding. -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
