RFC: automoc changes

[Alexander Neundorf]

On Sunday 05 November 2006 20:48, you wrote:
> Am Sonntag, 5. November 2006 13:48 schrieb Alexander Neundorf:
> > BUT you now have to use the kde4_add_* functions.
>
> Just being curious: If I want to develop a kde4 app/lib, is there any
> compelling use case not to use the kde4_* macros?

Maybe because somebody is an experienced cmake user and knows what 
add_executable() does but doesn't know what kde4_add_executable() does.
Or he wants to do the RPATH handling himself.
Bascially my idea was that these functions are really only thin convenience 
wrappers around the original cmake commands, with this new behaviour they are 
becoming a bit more than just a thin wrapper.

> Concerning the options, I'd simply expect the kde4_* macros perform
> everything needed to compile and link my kde4 app/lib, so I'm in favour of
> an automatic moc-step.
>
> For the total amount of freedom, wouldn't it be possible to combine (1),
> (2) and (3)? I. e. default to whatever KDE4_AUTOMOC say, *or* always use
> moc if overridden by kde4_add_executable(kblub AUTOMOC ${mySrcs} ), *or*
> never use moc if overriden by kde4_add_executable(kblah NO_AUTMOC
> ${myOtherSrcs} ).

Yes, possible. But I'd prefer to have to implement only one of them.

Bye
Alex
-- 
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net