On Wed, 2013-01-02 at 07:10 +1100, Adam Murdoch wrote: > On 02/01/2013, at 1:41 AM, Russel Winder wrote: > > > I wonder if the C++ plugin should also deal with D and mixed D/C++/C > > systems? > > At some point it might. We don't have any plans to do this at the > moment. However, something we'd like to do is to rework the c++ > plugins so that they don't assume that native executables and > libraries must be built from C++ source files, and also to open up the > compiler adapter API so that you can provide your own implementation. > This way, someone could put together a D plugin, which hooks in D > language support into the appropriate places.
Mixing C, C++, Fortran and D in a single system has to be the goal if Gradle is to make any headway in the native code arena. Also mixed Java and C/C++ systems, which is a use case for some SCons users, the Java bit of which is handled badly by SCons. The current Gradle model is that there is source to be built and "dependencies". Gradle basically implies that a dependency is a jar that can be found in a repository somewhere. SCons et al. treat dependency as a relationship between an item of source and an item of created thing. This latter view fails dismally for Java, Groovy and (especially) Scala – also I suspect Kotlin and definitely Ceylon (*). It is though the standard model for C, C++ and Fortran. D sits somewhere in between. Is there a way of adding a X.cpp → X.o → X type dependency as DAG building (as per SCons, Waf, etc.) or does Gradle not really support this style of build management? (*) Is anyone working on a Gradle plugin for Ceylon? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
