Fixing output of new automoc macro

Andreas Pakulat apaku at
Wed Jul 4 18:56:33 CEST 2007

On 04.07.07 18:39:20, Matthias Kretz wrote:
> On Wednesday 04 July 2007, Andreas Pakulat wrote:
> > b) Its too long. It contains the full absolute path of the header and
> > the moc file. IMHO it should be just the filename or if possible the
> > relative path of the .h to the CMakeLists.txt (i.e. for things in
> > kdeui it would be widget/foobar.h)
> I like to see all the information there. If it's a relative path it could be 
> in the src or build dir. And if it doesn't show what file it's creating the 
> moc from you don't know whether it's creating it from the .h or the .cpp 
> file.

Who cares? The normal cmake output is explicitly short so you're not
cluttered with uninteresting details the important thing is that a .moc
file is generated. Same thing for .ui files or even compilation of
source files. Such extended information can be shown in VERBOSE mode,
but IMHO not in standard mode. Its at least two lines in a standard
terminal and that is close to unreadable, at least I find that
unreadable so the information is useless for me anyway because I don't
look at it.


You will be reincarnated as a toad; and you will be much happier.

More information about the Kde-buildsystem mailing list