Please log in to watch this conference skillscast.
One of the biggest challenges in build automation is creating builds that span multiple languages and platforms. When it comes to native applications we have an interesting situation, tools like autoconf and Make are mature, but they are difficult to integrate with other pieces of a large multi-language build automation platform. What Gradleware plans to do with our C/C++ support is bring the same approach we’ve applied to Java, Scala, Groovy, and Android to native applications giving C and C++ first-class support in Gradle.
Other build tools hack native support into a model that was designed for Java. Instead of providing a rich DSL for declaring dependencies and configuration information in a way that is tailored to native applications you have to dance around a system that thinks build automation ends at “build my jar”. It doesn’t, and Gradle is aiming for something different. We don’t just want to make native builds better for people creating multi-language builds. We want Gradle to be a contender for stand-alone native builds.
This session will cover the following topics:
Gradle’s unique features for C/C++ builds. What can Gradle do that other build systems cannot?
Learn how to use Gradle to build binaries from C/C++, how to test them, and how to share them with other teams.
Find out about how Gradleware plans to solve some of the interesting challenges of building things from C/C++ and other native languages.
Come along and hear why you should use Gradle for your C/C++ projects.
YOU MAY ALSO LIKE:
Creating a world-class C++ Build System
Adam's many interests include build and deployment automation, automated software quality systems, web applications, networking, security projects, and software development process improvement.