Native code in Gradle: this changes everything

The addition of native code support has been a major focus of the Gradle development team over the past 12 months. But this work has gone far beyond allowing Gradle to simply compile and link native binaries. With a rich software component model, the introduction of rule-based configuration and enhancements to dependency management, developing an application with C++ can provide a sneak peek into the future of Gradle.

In this presentation, we will explore some of the key concepts and paradigms that underpin the native binary support in Gradle, and how these changes will benefit you in the future, whether you're developing with Java, C++, Scala or Android.

About Daz DeBoer

Daz has been a core member of the Gradle Inc. engineering team for over 6 years, helping take Gradle from an early-adopters tool into the mainstream. Over this time, he has been deeply involved in the delivery of a number of key features, including the improved dependency resolution cache, parallel build execution, and support for building native apps with Gradle.

Most recently, Daz has driven the design and implementation of 'Composite Builds' support in Gradle, providing a flexible mechanism for combining multiple Gradle builds into a single composite.

More About Daz »

About Adam Murdoch

Adam's many interests include build and deployment automation, automated software quality systems, web applications, networking, security projects, and software development process improvement. Building software since 1993, he has held technical leadership positions in Australia, the UK, and the US.

An early adopter and contributor to Gradle, Adam is now leading the Gradle development. Adam's role at Gradle Inc. includes working with the Gradle.org community and Gradle clients to help leverage the Gradle tool, improving software quality and simplifying application development and deployment.

More About Adam »