On 07/09/2017 01:12 AM, Gregg Reynolds wrote: > On Jul 9, 2017 1:59 AM, "Natalia Theologou" <natalia_th92 at hotmail.com> > wrote: > > > I have also followed these advice. > > https://wiki.iotivity.org/iotivity_porting_to_arm_based_platforms > > I am running: > > ... > > SECURED=0 RELEASE=1 > > is that legal? >
you can build however you want... If you wanted to take a device with iotivity to get OCF certification, it has to be in secured mode only, but that's an OCF rule, not an iotivity rule. I took a look at the cross-build setup earlier today and I'm not really happy with how it's set up - e.g. this check for boost happens, and aborts the build, before things get to the point where boost is built, which the build does know how to do. It has also already built gtest and not used cross-compilation for that, so there seem to be some holes. I'm suspicious that target=linux triggers some assumptions that are not true for a cross-build environment, whereas if building for android, that setup has been debugged. I'll try to poke at that some more if others don't already have solutions. If you're having luck building, some notes would be helpful - the wiki page has some pretty old assumptions in it as well.
