Hi Trevor, I fear the scons implementation in the service directory may be wrong wrt. these variables. I am certain this is the case because the resource directory has a dependency on all of these same exact variables and then dependencies are defined in common area (ie. the root of the repo; pre-service and pre-resource directories invocation of scons).
Thanks, Joey -----Original Message----- From: Trevor Bramwell [mailto:[email protected]] Sent: Friday, July 31, 2015 10:40 AM To: Morrow, Joseph L Cc: <h.marappa at samsung.com>; Keane, Erich; iotivity-dev at lists.iotivity.org Subject: Re: [dev] [simulator] Need Jenkins support for building native code Joey, There was a previous request for setting JAVA_HOME on the build servers, which was completed. I just updated the android build to output JAVA_HOME at the beginning of their run so we can verify it has properly been set. I'm not sure how having the variable explicitly set on the commandline would change things, unless scons isn't properly configured? Since the builds complain about ANDROID_NDK and ANDROID_GRADLE, these might be a better place to look, though they do say 'the default path will be used'. Regards, Trevor Bramwell On Fri, Jul 31, 2015 at 02:17:20PM +0000, Morrow, Joseph L wrote: > +Trevor Bramwell (IoTivity Systems Admin) > > Trevor, > > I believe that the services directory is not utilizing the extlibs directory > when JAVA_HOME is not specified on the command line. If JAVA_HOME is not > specified, then services directory should use IoTivity/extlibs/android/* (eg. > IoTivity/extlibs/android/sdk/android-sdk_r24.2 after invoking > IoTivity/extlibs/android/sdk/SConscript). Otherwise, the system environment > variable "JAVA_HOME" (or sdk.dir in gradle.properties) should already have > been set and is currently in use by Gradle in the resource directory. > > Harish Kumara M, > > Since these scons variables, gradle variables, and system environment > variables work for the resource directory, please consider reviewing the > SConscripts at the following locations: > > IoTivity/extlibs/android/sdk/SConscript > IoTivity/extlibs/android/ndk/SConscript > IoTivity/extlibs/android/gradle/SConscript > IoTivity/android/android-api/ > IoTivity/build_common/SConscript > IoTivity/build_common/android/SConscript > > Since these are based out of the root of the repo and are not 'resource > directory' specific, the 'service directory' should also be referencing the > outputs of these SConscript to avoid redundancy within the IoTivity project. > > Thanks, > > Joey Morrow > > On Jul 30, 2015, at 11:11 PM, Harish Kumara Marappa <h.marappa at > samsung.com<mailto:h.marappa at samsung.com>> wrote: > > > Hi Erich, > > > > This mail is about Jenkins build failure occurred in change set > https://gerrit.iotivity.org/gerrit/#/c/1986/ (simulator branch). We need > support of Jenkins build system for resolving this error. > > As part of simulator project we need to build JNI files which are used in > eclipse plugin project. Currently scons build environment does not provide > JDK information while building IoTivity for Linux platform. > > In our local systems we are managing the building by passing JAVA_HOME=<path > to jdk> for scons command, But the same code will failed to build in Jenkins > as build system unaware of JDK information. > > Jenkins should invoke scons command with JAVA_HOME=<path to jdk> argument so > that dependency on JNI will be resolved while building for Linux platform. > > > > command we are using for build is scons > JAVA_HOME=/usr/lib/jvm/java-7-openjdk-i386 > > > > > > Regards, > > Harish Kumara M > > +91-9008675643 > > > > > > [cid:Z5JE7EUABGFC at namo.co.kr] > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
