Geoffroy, The Iotivity recipe uses Yocto?s scons class and requires that scons be present in your Yocto build sysroot. The Yocto project comes with two recipes (python-scons and python-scons-native) which set this up for you. Unfortunately, this wasn?t a documented fact by the Yocto Project but I had figured it out with some exploration and separately ran ?bitbake python-scons? and ?bitbake python-scons-native? to bring in scons.
It slipped my mind when I prepared the README, and one or more people who have successfully built Iotivity on Yocto seemed to know what to do. So, thanks for pointing this out. I?d rather we not rely on scons from the host OS and instead continue to use Yocto?s scons build for consistency sake. In the meanwhile, I will either update the README or set the two scons recipes as build time dependencies. Thanks, -Kishen. On 2/9/15, 8:47 AM, "Lankswert, Patrick" <patrick.lankswert at intel.com> wrote: >Geoffroy, > >Ah. Passing on to Bernie in OTC. > >Bernie, > >This gentleman has a patch that I think that you can get to the right >place. > >Pat > >-----Original Message----- >From: VanCutsem, Geoffroy >Sent: Monday, February 09, 2015 11:32 AM >To: Lankswert, Patrick; Prasad, Sudarshan; iotivity-dev at lists.iotivity.org >Subject: RE: Bug in the iotivity_0.9.0.bb recipe (meta-oic) > >Thanks Sudarshan and Patrick for your answers. > >I have seen the wiki pages on wiki.iotivity.org but the code (well, it's >_just_ the recipe actually) that needs patching is in meta-oic which is >hosted on the yoctoproject.org website. It is not clear to me if that >means >the bug should be filed on the Yocto bugzilla instance (and a patch pushed >directly there) or whether this should go through the IoTivity Gerrit >review >system (but I don't see how I could push that review to the IoTivity >Gerrit >instance)? > >Thanks, >Geoffroy > >----------------------------------------------- >Intel Corporation NV/SA >Kings Square, Veldkant 31 >2550 Kontich >RPM (Bruxelles) 0415.497.718. >Citibank, Brussels, account 570/1031255/09 > > >> -----Original Message----- >> From: Lankswert, Patrick >> Sent: Monday, February 09, 2015 5:27 PM >> To: Prasad, Sudarshan; VanCutsem, Geoffroy; >> iotivity-dev at lists.iotivity.org >> Subject: RE: Bug in the iotivity_0.9.0.bb recipe (meta-oic) >> >> Geoffroy, >> >> As a rule of thumb, it is always nice to have a Jira ticket if the >> description or history of a problem will not fit in a git commit >>comment. >> >> In this case, I think that submitting the changeset to gerrit for >> review is suffice. >> >> Thanks! >> >> Pat >> >> -----Original Message----- >> From: iotivity-dev-bounces at lists.iotivity.org >> [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Prasad, >> Sudarshan >> Sent: Monday, February 09, 2015 11:21 AM >> To: VanCutsem, Geoffroy; iotivity-dev at lists.iotivity.org >> Subject: Re: [dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic) >> >> Hi Geoffroy, >> >> Thanks for fixing the bug. >> >> This link has set of instructions for development workflow -- >> https://wiki.iotivity.org/. >> Specifically, to submit a change -- >> https://wiki.iotivity.org/submitting_to_gerrit >> >> If you want to create a bug or look for the same, we use JIRA -- >> https://jira.iotivity.org/secure/Dashboard.jspa >> >> Please let me know if you have any clarifications. >> >> Thanks, >> Sudarshan Prasad | Software Development Engineer | Intel >> Corporation >> >> -----Original Message----- >> From: iotivity-dev-bounces at lists.iotivity.org >> [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of >> VanCutsem, Geoffroy >> Sent: Monday, February 09, 2015 3:56 AM >> To: iotivity-dev at lists.iotivity.org >> Subject: [dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic) >> >> Hi, >> >> I was trying to build IoTivity for Edison by following the README in >> http://git.yoctoproject.org/cgit/cgit.cgi/meta-oic/tree/README?h=maste >> r. I was initially facing an issue because 'scons' was not available >> in the sysroot (see [2] for the log output). This can easily be fixed >> by the following patch [1], is there a quick guide on how I can submit >that change? >> (Also, I couldn't find any bug report for this but can create one if >> needed). >> >> Cheers, >> Geoffroy >> >> [1] Patch that fixes the 'scons' issue when building iotivity for >> Edison diff --git a/recipes-core/iotivity/iotivity_0.9.0.bb >> b/recipes-core/iotivity/iotivity_0.9.0.bb >> index 14bc6ad..0a0e3bc 100644 >> --- a/recipes-core/iotivity/iotivity_0.9.0.bb >> +++ b/recipes-core/iotivity/iotivity_0.9.0.bb >> @@ -1,5 +1,3 @@ >> -inherit scons >> - >> SUMMARY = "Iotivity framework and SDK by the Open Interconnect >> Consortium." >> DESCRIPTION = "IoTivity is an open source software framework enabling >> seamless device-to-device connectivi HOMEPAGE = >> "https://www.iotivity.org/"; >> @@ -16,6 +14,8 @@ SRC_URI[cereal.md5sum] = >> "2d9adeb49a2cb54f259c601d34d2d959" >> SRC_URI[cereal.sha256sum] = >> "33dfeed8f6345a4dff42e1057a79b1d5303624a4a3bdb362f9c17a0048c811e >> e" >> SRCREV_cereal = "7121e91e6ab8c3e6a6516d9d9c3e6804e6f65245" >> >> +inherit scons >> + >> python () { >> EXTRA_OESCONS = "" >> IOTIVITY_TARGET_ARCH = d.getVar("TARGET_ARCH", True) >> >> [2] Log of the failure when scons is not found: >> NOTE: recipe iotivity-0.9.0-r0: task do_compile: Started Log data >>follows: >> | DEBUG: Executing shell function do_compile >> | /home/gvancuts/Scaricati/edison-src/build/tmp/work/core2-32-poky-lin >> | ux >> | /iotivity/0.9.0-r0/temp/run.do_compile.7518: line 104: >> | /home/gvancuts/Scaricati/edison-src/build/tmp/sysroots/x86_64-linux/ >> | us >> | r/bin/scons: No such file or directory >> | ERROR: scons build execution failed. >> | WARNING: >> /home/gvancuts/Scaricati/edison-src/build/tmp/work/core2-32-poky- >> linux/iotiv >> ity/0.9.0-r0/temp/run.do_compile.7518:1 exit 1 from >> | exit 1 >> | ERROR: Function failed: do_compile (log file is located at >> | /home/gvancuts/Scaricati/edison-src/build/tmp/work/core2-32-poky-lin >> | ux >> | /iotivity/0.9.0-r0/temp/log.do_compile.7518) >> NOTE: recipe iotivity-0.9.0-r0: task do_compile: Failed >> DEBUG: Teardown for bitbake-worker >> NOTE: Tasks Summary: Attempted 538 tasks of which 537 didn't need to >> be rerun and 1 failed. >> >> Summary: 1 task failed: >> >> /home/gvancuts/iotivity/meta-oic/recipes-core/iotivity/iotivity_0.9.0. >> bb, >> do_compile >> Summary: There was 1 ERROR message shown, returning a non-zero exit >> code. >> >> ----------------------------------------------- >> Intel Corporation NV/SA >> Kings Square, Veldkant 31 >> 2550 Kontich >> RPM (Bruxelles) 0415.497.718. >> Citibank, Brussels, account 570/1031255/09 >> >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
