Hi Chris Due to the size and complexity of the gradle build, we rely on the concept of "build types" to define different ways to execute the build. Very rarely (if ever) do developers run "./gradlew build".
The build types are defined in the main build.gradle file. The most complete build I would generally run would be './gradlew developerBuild' Regarding the specific failure you're seeing: in the past couple of days we've switched some of our CI builds to require all supported C++ tool chains to be installed in order to run. During the process of implementing this, there was a time that _all_ executions of ':cpp:integTest' required _all_ supported tool chains (gcc3, gcc4 for *nix). This has now been changed so that only gcc4 is required for a regular build, and gcc3 is only required for a 'platformBuild'. Please keep trying to get a successful build, using './gradlew developerBuild', and if you have a test that's consistently failing, let us know. Daz On 11 July 2013 00:05, Chris Doré <oesoluti...@gmail.com> wrote: > Hi all, > > I'm just starting out with Gradle development and I'm having a difficult > time getting a successful build. > > Over the last few weeks I've been keeping up to date with the latest > commits and every build I've run has always failed in some type of > integration test (doing ./gradlew build). Just as an example, my most > recent failure is: > > :cpp:integTest > > org.gradle.nativecode.language.cpp.CLanguageIntegrationTest > > initializationError [g++ 3] FAILED > java.lang.RuntimeException > > > Some info: > $ ./gradlew --version > > ------------------------------------------------------------ > Gradle 1.7-rc-1 > ------------------------------------------------------------ > > Build time: 2013-07-02 14:56:30 UTC > Build number: none > Revision: 9a7199efaf72c620b33f9767874f0ebced135d83 > > Groovy: 1.8.6 > Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012 > Ivy: 2.2.0 > JVM: 1.6.0_51 (Apple Inc. 20.51-b01-457) > OS: Mac OS X 10.7.5 x86_64 > > Is there just something wrong with my environment, or should I be adopting > a different workflow of some type? > > > Here's hoping I can get past these hurdles and focus my effort on > something better, > Chris > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
