[Development] CMake Workshop Summary

[Jean-Michaël Celerier]

> It is not bad, but it is not great either :-). For example one needs to
_link_
QtCore before compilation on other things can be started, it is quite
visible
on an under-powered machines, where linking takes time.

I think that this would still generally be the case with CMake, there are
longstanding issues opened about it :
https://gitlab.kitware.com/cmake/cmake/issues/15555
https://gitlab.kitware.com/cmake/cmake/issues/17528

Best,
Jean-Michaël


On Mon, Feb 25, 2019 at 9:32 AM Christian Kandeler <Christian.Kandeler at qt.io>
wrote:

> On Mon, 25 Feb 2019 08:13:29 +0000
> Jedrzej Nowacki <Jedrzej.Nowacki at qt.io> wrote:
>
> > On Friday, February 22, 2019 7:18:36 AM CET Thiago Macieira wrote:
> > > But do note that our parallelism isn't that bad right now.
> >
> > It is not bad, but it is not great either :-). For example one needs to
> _link_
> > QtCore before compilation on other things can be started, it is quite
> visible
> > on an under-powered machines, where linking takes time. Similar,
> redundant
> > synchronization point is on the module level.
>
> Also, the examples could have per-app granularity and just start building
> as soon as the respective module is ready,
>
>
> Christian
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20190225/936b8030/attachment.html>