On Tue, Feb 25, 2014 at 1:00 PM, Zsolt Kúti <la.ti...@gmail.com> wrote:
> Hello, > > > On Sun, Feb 23, 2014 at 5:15 PM, Daz DeBoer <darrell.deb...@gradleware.com > > wrote: > >> Hi >> Thanks for taking the time to investigate. It certainly does look like >> you have a bootstrap problem! The 'native-platform' build now requires a >> newer version of Gradle that 1.10 : I'm guessing that the debug log you >> posted is using 1.10? >> > Yes, 1.10 was used. > > > >> >> You'll need to use the gradle wrapper to build native-platform, or at >> least grab a recent nightly build and try that (http://gradle.org/nightly). >> Can you try one of these mechanisms, with the jnidispatch.so hack that >> worked for earlier versions? >> > Tried 1.11. It failed with a different error. > Then nightly build of 22.02 did it! > Cool. So you're using the nightly build, hacked to use an old native-platform dll? What exactly do you need to do to get Gradle to run. (This might help others who hit a similar bootstrap problem). > Not surprisingly almost all tests failed. > > >> >> Once you are able to successfully build (and run the tests for) >> native-platform, we can work on getting it fixed so that it produces >> something the works correctly on FreeBSD, and then include that in >> Gradle-1.12. >> >> Thanks I need this help, especially because IDEA (13.x) fails when > applying gradle project import (using nightly gradle version), so IDE > support is missing for the time being. I am going to try to recreate them > from local cache by hand. > > > Looking at the code I see Linux class and I think this is probably an > appropriate starting point to base FreeBSD support on. > I modified build.gradle and Platform.class by adding FreeBSD specific > parts that follow those of Linux. > Can you fork the project on Github so we can see the code? Then I might be able to provide some pointers. > Running tests gives apparently just one failed: > > :processTestResources UP-TO-DATE > :testClasses UP-TO-DATE > :test > > net.rubygrapefruit.platform.FileSystemsTest > can query filesystem details > FAILED > java.lang.UnsatisfiedLinkError at FileSystemsTest.groovy:34 > > > 30 tests completed, 1 failed, 1 skipped > :test FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':test'. > > There were failing tests. See the report at: > file:///usr/home/kuti/projekt/native-platform/build/reports/tests/index.html > We'll need to see the actual test results from the HTML report. Stack trace in particular. Thanks for working on this. cheers Daz
