Sounds good, let me know if you run into any issue! I have generated a new Edison image with the iotivity stuff in it yesterday, is there any simple sanity test I can run to confirm that the iotivity binaries are functional?
Cheers, Geoffroy > -----Original Message----- > From: Maloor, Kishen > Sent: Monday, February 09, 2015 8:45 PM > To: VanCutsem, Geoffroy; Lankswert, Patrick; Prasad, Sudarshan; iotivity- > dev at lists.iotivity.org; Keany, Bernie > Subject: Re: [dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic) > > Geoffroy, > > > That is something I didn't know you could do - pretty cool :) > I will test this out and update the recipe upstream. > > Thank You! > -Kishen. > > On 2/9/15, 11:02 AM, "VanCutsem, Geoffroy" > <geoffroy.vancutsem at intel.com> > wrote: > > >Hi Kishen, > > > >> -----Original Message----- > >> From: Maloor, Kishen > >> Sent: Monday, February 09, 2015 7:18 PM > >> To: Lankswert, Patrick; VanCutsem, Geoffroy; Prasad, Sudarshan; > >>iotivity- > >> dev at lists.iotivity.org; Keany, Bernie > >> Subject: Re: [dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic) > >> > >> 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. > >I did not have to do that as soon as I fixed the location of your > >'inherit scons' statement in the recipe. > > > >> > >> 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. > >You're not using the host OS scons as soon as the 'inherit scons' > >statement is in the right place in the recipe. Yocto will build it for > >you and put it in your sysroot. > > > >> > >> In the meanwhile, I will either update the README or set > >> the two scons recipes as build time dependencies. > >No need for that, the scons class exists and is functional, you just need > >to move the 'inherit scons' statement further down the recipe so it is > >correctly picked up by bitbake. This is what my patch below does. > > > >Cheers, > >Geoffroy > > > >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] = > >"33dfeed8f6345a4dff42e1057a79b1d5303624a4a3bdb362f9c17a0048c811 > ee" > >SRCREV_cereal = "7121e91e6ab8c3e6a6516d9d9c3e6804e6f65245" > > > >+inherit scons > >+ > >python () { > > EXTRA_OESCONS = "" > > IOTIVITY_TARGET_ARCH = d.getVar("TARGET_ARCH", True) > > > > > >----------------------------------------------- > >Intel Corporation NV/SA > >Kings Square, Veldkant 31 > >2550 Kontich > >RPM (Bruxelles) 0415.497.718. > >Citibank, Brussels, account 570/1031255/09 > > ----------------------------------------------- Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09
