Let me explain why I'm trying to use scons directly and not with bitbake:

I have created a server based on the simpleserver example. Everything works
perfectly on my raspberry board. Then I recompiled my server for another
board but it throws an exception (bad_alloc) from inside IoTivity library
(have traced the code and found the line of code, it tries to allocate some
memory and returns NULL, so the library throws std::bad_alloc, although
there is approximately 700MB free memory)

Since the simpleserver sample works my next thought was to take the source
code and without modifications replace my code with the one from
simpleserver and then if it worked to start updating it portion by portion
to find the problem). BUT after bitbake and trying on the board I get
exactly the same bad_alloc exception with the simpleserver

As I don't have any other way of compiling my server (unfortunately cannot
compile on the board), I thought of using scons. My software compiles and
works perfectly on my Ubuntu host machine, so the next logical move was to
use scons to cross-compile hence the need to use boost library







On 30 August 2017 at 11:36, Philippe Coval <philippe.co...@osg.samsung.com>
wrote:

>
>
> On 30/08/17 10:30, Iosif Hamlatzis wrote:
> > I am trying to cross-compile IoTivity (with scons) for yocto but have
> > problems with boost library
> >
> >
> (...)
> > scons TARGET_OS=yocto TARGET_ARCH=arm TC_ARCH=arm
> > TC_PREFIX=arm-poky-linux-gnueabi-
> > TC_PATH=~/certh-release-bsp/SGW_T/tmp/sysroots/x86_64-
> linux/usr/bin/cortexa9hf-vfp-neon-poky-linux-gnueabi
> > -c VERBOSE=true
> >
> >
> You need to use bitbake not call scons TARGET_OS=yocto directly,
>
> See instructions on:
> https://wiki.iotivity.org/yocto
>
> If you use master you'll see an error, I am about to fix later today.
>
> Hope this help
>
> --
> mailto:philippe.co...@osg.samsung.com gpg:0x467094BC
> https://blogs.s-osg.org/author/pcoval/
>
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev@lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to