<div dir="ltr">On Thu, Sep 19, 2013 at 7:39 PM, Alexander Neundorf <span dir="ltr"><<a href="mailto:neundorf@kde.org" target="_blank">neundorf@kde.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thursday 19 September 2013, Alex Merry wrote:<br>
> On 19/09/13 17:00, Aleix Pol wrote:<br>
> > Hi,<br>
> > We should decide what we do with the add_plugin macro. Should I install<br>
> > it as kf5_add_plugin from KCoreAddons? Do we want something different or<br>
> > better?<br>
><br>
> Would e-c-m be the right place for it?<br>
<br>
</div>Depends on what it does.<br>
IMO, if it is generally useful, and has no KDE dependencies, yes.<br>
If it is only useful for KDE, it might go into kde-modules and get a KDEish<br>
prefix. But this is actually not wanted.<br>
<br>
But I think Stephens plan is to get rid of those macros and use plain cmake<br>
instead, i.e. add_library(... MODULE ...), as with add_executable() and<br>
add_library().<br>
<div class="HOEnZb"><div class="h5"><br>
Alex<br>
_______________________________________________<br>
Kde-frameworks-devel mailing list<br>
<a href="mailto:Kde-frameworks-devel@kde.org">Kde-frameworks-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-frameworks-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kde-frameworks-devel</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra">Ah, right. So maybe I can just change those to add_library(MODULE) and forget about macros, right?</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Aleix</div></div>