hi

i tried build yocto project(for tizen, for raspberrypi).

and these way is hard..

so i build iotivity on rpi3, with $scons TARGET_ARCH=arm TEST=0 RELEASE=0 then 
move files to rpi0.
run ocserver(rpi3) occlient(rpi0), it runs quite well.

anyway i have question about this.
1. when build iotivity with $scons TARGET_ARCH=arm TEST=1 RELEASE=0, a error 
occured in valgrind test.
2. on x86_64 system, ubuntu 16.04 LTS(VMWARE).
   i build iotivity same command, but diffrent error occured.
  " examples/OICMIDDLE/client.cpp:1:0: error: bad value (armv5te) for 
-march=switch"

BR,
jaehwan kim


-----Original Message-----
From: "Philippe Coval"<philippe.co...@osg.samsung.com> 
To: <iotivity-dev at lists.iotivity.org>; 
Cc: 
Sent: 2017-05-15 (?) 17:18:43
Subject: Re: [dev] RPI zero build problem






    On 15/05/17 06:55, ??? wrote:




        hi.



    Hi







        so run iotivity on rpi0 that need yocto or tizen?



    To run tizen you need tizen yocto 

    (I only have work in progress tree, but I can share that)



    So better get started with yocto's poky





        im tring build yocto image, but hard to configuration.





    Maybe this page is more details



    https://blogs.s-osg.org/run-iotivity-artik-yocto/



    Just replace meta-artik with meta-raspberrypi





        i saw this page(https://wiki.iotivity.org/yocto).



        i want know is it right append meta-rasberrypi in BBlayers?

        and local.conf MACHINE = raspberrypi?



    MACHINE=raspberrypi0 is what you want





        i already do it, and can't recognize raspberrypi string..



        problem is setting up
            BBlayer and local conf file. 

        please give
            me some idea. 







    You can edit wiki and insert "TODO"

    where it's not clear I will explain more



    Good luck



    -- 
mailto:philippe.coval at osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/





-------------- next part --------------
HTML ?????? ??????????????...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170517/122be529/attachment.html>

Reply via email to