Interesting. Our biggest hurdle to any potential larger adoption is our mixed C/C++/Java codebase - I've only been able to apply gradle for pure Java projects only.
We have some fairly complex C/C++ native, cross-platform and cross-compiler situations to deal with, and that led to the development of "abuild", a build system that effectively manages multi-architecture builds for C/C++ and has evolved to better support Java builds via groovy (based upon conventions, but with flexibility to adjust things - sound familiar?) http://www.abuild.org http://www.abuild.org/files/doc/html/abuild-manual.html The C/C++ support is actually leveraging gnu make and autoconf, but there is significant logic above those layers that deals with wiring things up in the first place. The primary author of abuild definitely understands the details of complex C/C++ builds and I'll be sure to inform him of the alpha cpp subproject within gradle. He very recently expressed some interest in porting abuild as a gradle plugin (although his time constraints are considerable right now). He would be a valuable person to have examining the evolving capabilities and desired requirements of the cpp subproject. -Spencer --- On Wed, 7/13/11, Peter Niederwieser <[email protected]> wrote: Russel Winder wrote: > > What is really needed to give the project serious momentum is to find an > organization which needs to create mixed JVM/C/C++/D systems that wants > to use Gradle and that can provide resource either by developer time or > cash to contract developer time. > This part is already solved.
