On Sun, 2014-06-22 at 08:39 +1000, Adam Murdoch wrote:
[…]
> One thing that is missing from the Gradle story at the moment is
> dependency management that works across all these domains. This is
> something we’re working on at the moment.
And then there is dynamic linking to libraries on the platform as well
as the idea of downloading dependent artefacts. If a build system forces
download and use of a library that is already resident via the platform
packaging, then it will not be a viable build framework for that
platform.
> For Gradle to be a realistic option for teams that develop native
> software only, we need to do something about performance - we need to
> make configuration time much faster, and we need to push parallel
> execution more. We’ve started on improving configuration time and this
> should lead to better paralysation too.
The former has been a bit of a problem for SCons, but not Waf and CMake.
SCons does all configuration at run time of each build, Waf and CMake
separate configuration from running a build. Of course this makes SCons
more resilient to unexpected changes. SCons, Waf, CMake just follow make
and use the -j flag to throw processors at a build problem. It is fairly
easy to parallelize compile actions given the data in the ADG
representing the build.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
