Ok so you target OS is Fedora, About uuid I support fedora has packaged it
I havent done any crosscompilation for this system, but I would suggest 1st to try to build on device or build a package on a desktop fedora system, if it helps you can get inspiration from spec file in tools/tizen I recently made it "linux" compatible... Keep in touch On Fri, Oct 28, 2016 at 2:51 PM, Aakash KAUSHAL <aakash.kaushal at legrand.us> wrote: > HI Philippe, > > > > Thanks for help. > > I am compiling iotivity on Ubuntu 16.0. > > Using Cross compiler is -linux-gnueabi compiler which support build for > our target Artik 520 - ARM Cortex A7 processer. > > scons TARGET_OS=linux TARGET_ARCH=arm TARGET_TRANSPORT=IP SECURED=0 > RELEASE=1 TC_PREFIX=arm-linux-gnueabi- TC_PATH=/usr/arm-linux-gnueabi/bin > > I want to build binary on ubuntu and want to run(sample example or my > wraaper.o ) on Fedora which is present on Artik 520. So for that i using > iotivity link > > https://wiki.iotivity.org/iotivity_porting_to_arm_based_ > platforms?s[]=arm&s[]=based&s[]=platforms > > Current issue i am facing in step 4 in which they mention for UUID-arm. I > followed all steps , but i am not aware which is the required SConscripts i > have add step 4 lines. > > I hope my understanding is correct. > > BR > > Aakash kaushal > > > > > > > > > > *From:* Philippe Coval [mailto:philippe.coval.pro at gmail.com] > *Sent:* Friday, October 28, 2016 1:16 AM > *To:* Aakash KAUSHAL > *Cc:* iotivity-dev at lists.iotivity.org > *Subject:* Re: [dev] Iotivity Wiki Cross Compilation Query- port IoTivity > to arm based platforms > > > > Hi > > I can try to help you > > because I managed to use iotivity on ARTIK10 too (Tizen or Yocto), > > can you tell us which OS are you targeting ? > > Meanwhile, you'll find some hints at : > > https://wiki.iotivity.org/hardware > https://wiki.iotivity.org/os > > > > On Thu, Oct 27, 2016 at 11:00 PM, Aakash KAUSHAL < > aakash.kaushal at legrand.us> wrote: > > Hi team, > > > > Need help on this. > > > > BR > > Aakash kaushal > > > > *From:* Morrow, Joseph L [mailto:joseph.l.morrow at intel.com] > *Sent:* Thursday, October 27, 2016 3:20 PM > *To:* Aakash KAUSHAL > *Subject:* RE: Iotivity Wiki Cross Compilation Query- port IoTivity to > arm based platforms > > > > Hi Aakash, > > > > You can write to iotivity-dev at lists.iotivity.org. This email reflector > puts you in touch with the IoTivity developer community. > > > > Thanks, > > > > Joey Morrow > > > > *From:* Aakash KAUSHAL [mailto:aakash.kaushal at legrand.us > <aakash.kaushal at legrand.us>] > *Sent:* Thursday, October 27, 2016 12:12 PM > *To:* Morrow, Joseph L <joseph.l.morrow at intel.com> > *Subject:* Iotivity Wiki Cross Compilation Query- port IoTivity to arm > based platforms > > > > Hi Joseph, > > > > Greetings > > > > I am new to iotivity and following the iotivity wiki guidelines for > understanding and building framework. > > > > I am not able to get the correct person to contact for the iotivity > guideline provide. Found you email id so mailing you on this. Please ignore > if your are not the correct point of contact. Please let me know to > whom/how to contact for any Iotivity issue. > > > > > > *AIM - For ARM Cross Compilation. We are following the below Iotivity > link. * > > > > https://wiki.iotivity.org/iotivity_porting_to_arm_based_ > platforms?s[]=arm&s[]=based&s[]=platforms > > > > Described below Step 4 as mention in the link . > > > > We are using arm-linux-gnueabi compiler which support build for our tager > Artik 520 - ARM Cortex A7 processer. > > > > > > *4) Download the UUID Header/Libraries for arm architecture from Internet > or from linkuuid-arm.zip. Place the UUID Headers/Libraries inside IoTivity > folder (For Eg: iotivity/extlibs/). Update the CPPPATH/LIBPATH for UUID > Headers/Libraries in required SConscript* > > > > - As describe above i have followed the steps. Issue is the > uuid-arm folder doesn't have any defulat SConscript when unzip(only header > and lib folder) and it *is not Cleary mention which is the required > SConscript to add below lines*. The uuid.so is present in the uuid-arm > lib folder. > > - below are the lines which are mention need to be added. > > - i am confused on this which will be the required Sconscripts and > how to debug this. Kindle help on this. > > > > For E.g.: env.AppendUnique(CPPPATH = [ '<uuid header path>']) > > env.AppendUnique(LIBPATH = ['<uuid Library Path>']) > > env.AppendUnique(LIBS = ['uuid']) > > {{:arm_uuid_path.png?200|}} -----> > This line itself is a syntax error to add anywhere. > > > > Build Command > > > > scons TARGET_OS=linux TARGET_ARCH=arm TARGET_TRANSPORT=IP SECURED=0 > RELEASE=1 TC_PREFIX=arm-linux-gnueabi- TC_PATH=/usr/arm-linux-gnueabi/bin > > > > ERROR > > > > scons: Building targets ... > > scons: building associated VariantDir targets: out/linux/arm/release > Linking out/linux/arm/release/resource/csdk/connectivity/ > src/libconnectivity_abstraction.so > > /usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: > cannot find -luuid > > collect2: error: ld returned 1 exit status > > scons: *** [out/linux/arm/release/resource/csdk/connectivity/ > src/libconnectivity_abstraction.so] Error 1 > > scons: building terminated because of errors > > > > Thanks for cooperation. > > > > BR > > Aakash Kaushal > > > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints ? ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > ?tre divulgu?es. Si vous n'?tes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > imm?diatement ? son exp?diteur, et de d?truire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autoris?e, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > *Se d?sabonner: *Si vous souhaitez ?tre retir? de notre liste de > diffusion, s'il vous pla?t envoyer vos coordonn?es ? > CASL.unsubscribe at legrand.ca <casl.unsubscribe at legrand.ca> et indiquer > quels sont les messages que vous ne souhaitez plus recevoir. > > > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > *Unsubscribe:* If you would like to be removed from our mailing list, > please send your contact information to CASL.unsubscribe at legrand.ca > <casl.unsubscribe at legrand.ca> and indicate what messages you no longer > wish to receive. > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints ? ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > ?tre divulgu?es. Si vous n'?tes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > imm?diatement ? son exp?diteur, et de d?truire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autoris?e, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > *Se d?sabonner: *Si vous souhaitez ?tre retir? de notre liste de > diffusion, s'il vous pla?t envoyer vos coordonn?es ? > CASL.unsubscribe at legrand.ca <casl.unsubscribe at legrand.ca> et indiquer > quels sont les messages que vous ne souhaitez plus recevoir. > > > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > *Unsubscribe:* If you would like to be removed from our mailing list, > please send your contact information to CASL.unsubscribe at legrand.ca > <casl.unsubscribe at legrand.ca> and indicate what messages you no longer > wish to receive. > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > > > -- > > -- > https://wiki.tizen.org/wiki/User:Pcoval > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints ? ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > ?tre divulgu?es. Si vous n'?tes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > imm?diatement ? son exp?diteur, et de d?truire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autoris?e, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > *Se d?sabonner: *Si vous souhaitez ?tre retir? de notre liste de > diffusion, s'il vous pla?t envoyer vos coordonn?es ? > CASL.unsubscribe at legrand.ca <casl.unsubscribe at legrand.ca> et indiquer > quels sont les messages que vous ne souhaitez plus recevoir. > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > *Unsubscribe:* If you would like to be removed from our mailing list, > please send your contact information to CASL.unsubscribe at legrand.ca > <casl.unsubscribe at legrand.ca> and indicate what messages you no longer > wish to receive. > -- -- https://wiki.tizen.org/wiki/User:Pcoval -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161028/d14d8cf0/attachment.html>
