Naming sheme from moc output

[Christian Ehrlicher]

> --- Ursprüngliche Nachricht ---
> Von: David Faure <faure at kde.org>
> An: kde-buildsystem at kde.org
> Betreff: Re: Naming sheme from moc output
> Datum: Fri, 21 Oct 2005 11:12:20 +0200
> 
> On Thursday 20 October 2005 21:14, Christian Ehrlicher wrote:
> > Hello once again,
> > 
> > I've a question about the moc naming sheme. Why is it different to
> qmake?
> > Qt/qmake:
> > moc file.h -> moc_file.cpp
> > moc file.cpp -> file.moc
> 
> But I think qmake also supports moc file.h -> file.moc when included by
> .cpp nowadays?
Yes. with a modified mkspecs/features/moc.prf. Maybe when trolltech tweaks
this file, you can specify your own moc pre- and suffix in your makefile to
get the same behaviour like kde.
> > Kde/bksys/automake
> > moc file.h -> file.moc
> > moc file.cpp -> file_moc.cpp
> 
> Actually it's more like
> am_edit/unsermake
>   moc file.h -> file.moc if included from .cpp, otherwise file_moc.cpp
>   qobjects in file.cpp -> not supported
> 
> bksys
>   (I'm not sure; probably what you said)
> 
> I work on Qt-only projects, and I very much dislike that grep hits
> moc_file.cpp files too
> (I know, doesn't happen with srcdir!=builddir or a moc dir, but with qmake
> the support for 
> a moc dir broke in Qt4 (in our case)). ".moc" is really fine. And it's
> also what every
> KDE developer is used to, now, you also have to take that into account :-)
Yes for sure :)
I was just interested for the reasons.

Thx,
Christian

-- 
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner