<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Nov 18, 2013 at 12:50 PM, Stephen Kelly <span dir="ltr"><<a href="mailto:steveire@gmail.com" target="_blank">steveire@gmail.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Kevin Ottens wrote:<br>
> 10% chance? 50%? 80%?<br>
><br>
> Basically what's the time frame for CMake 3.<br>
<br>
</div>I'll be 90% surprised if it is not released in January, or maybe February.<br>
<div class="HOEnZb"><div class="h5"><br>
Thanks,<br>
<br>
Steve.<br>
<br>
<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">So would it be that bad to have a macro of ours that ends up being just a wrapper to qt5_wrap_ui?</div><div class="gmail_extra"><br></div><div class="gmail_extra">

Otherwise, this delays the possibility to help the ongoing porting process by extending a mandatory dependency on KDE4Support.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>