[ANNOUNCE] automoc4 from kdesupport now supported for building KDE
kretz at kde.org
Mon Jun 16 17:13:41 CEST 2008
On Thursday 05 June 2008, Alexander Neundorf wrote:
> On Thursday 29 May 2008, Matthias Kretz wrote:
> > On Thursday 29 May 2008, Alexander Neundorf wrote:
> > > On Wednesday 28 May 2008, Matthias Kretz wrote:
> > > > I tried add_custom_target and it won't work in the automoc macros
> > > > because there needs to be a dependency from the main target to the
> > > > automoc target. And that cannot be added from the automoc macro
> > > > because the main target is not defined at this point.
> > > >
> > > > add_custom_command(TARGET has the same problem.
> > > >
> > > > It would be possible to use add_custom_target and require the user to
> > > > add the dependency between the two targets himself. In the KDE4_
> > > > macros we could do that...
> Yes, there it wouldn't be a problem.
> Except that it is a bit slower, right ?
It's hard to profile. But it certainly has to read and write a lot more files
if you double the number of targets in a project. It should be noticable on
big modules like kdelibs and kdebase. Small modules won't notice it, I think.
> Do you think this would be acceptable for other projects ?
It being slower or the need to add a dependency rule for a target that fell
from the sky?
Hmm, perhaps the target could be made explicit:
kde4_add_library/executable/plugin would hide all that.
Matthias Kretz (Germany) <><
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20080616/1f0fdd5d/attachment.pgp
More information about the Kde-buildsystem