Re: [dev] IoTivity Development on Raspberry Pi* 3 and Server/Client Problem

On 04/17/2018 04:11 AM, 구자훈 wrote: Hello, and Thanks to your answer. I think I lacked my current environment and explanation of the questions. Sorry.. I followed the instructions in the [IoTivity Development on Raspberry Pi* 3] document and confirmed that turning the LED on and off using

Re: [dev] IoTivity and LoRaWAN

On 06/04/18 12:02, Roland Kromes wrote: > Hy all, > > I would like to know if there any way to integrate IoTivity with LoRaWAN ? > > Thanks > Best regards, > > Roland Kromes  > > Hi Roland, I know that IoTivity and LoRa was mentioned a couple of time in this list, so I listed relevant thread at

Re: [dev] ESP8266 for Arduino

On Thu, Mar 15, 2018 at 3:29 PM, Mats Wichmann wrote: > you should be able to find some info in the wiki by sesrching. > Hi, See history of patch linked from: https://wiki.iotivity.org/hardware#mcu Regards -- gpg:0x467094BC xmpp:philippe.coval@gmail.com https://wiki.tizen.org/wiki/User:Pco

Re: [dev] clear distinction of what is below and above the APIs

On 03/12/2018 05:58 AM, Dwarkaprasad Dayama wrote: Hi Mats, I just took pen and started going through all emails for this topic. As you mentioned, different things have been presented in form of opinion. Hence linking them is difficult. Before I move ahead with creating a new chapter in W

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 07:55 PM, Heldt-Sheller, Nathan wrote: Hi Phil, I agree your change has merits and I understand the motive... it was very bad to have the "reference" .dat files out of sync with their source .json files, and no way for devs to know. However: Instead, I recommend adding a spe

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 07:36 PM, Thiago Macieira wrote: On Monday, 5 March 2018 10:17:56 PST Philippe Coval wrote: Yes I introduced this "keep json and dat synched feature", in master while 1.3-rel was branched Please don't do that. You should not modify checked-in files unles

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 07:06 PM, Steve Saunders (CableLabs) wrote: Here is how 1.3 behaves with respect to .dat files. (...) Somethings is different between 1.3 builds vs. current master RE generating .dat files during build. Yes I introduced this "keep json and dat synched feature", in master while

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 03:31 PM, Wouter van der Beek (wovander) wrote: Sounds like an issue.. to be reported ;) The python works great for creating the introspection files as part of the DeviceBuilder tool chain and works fine with the CTT. I have tried to use exactly the same sequence for the secur

Re: [dev] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status

On Fri, Jan 12, 2018 at 3:26 AM, Chanho Park wrote: > Hi Philippe, > > On Thu, 11 Jan 2018 at 7:11 PM Philippe Coval com> wrote: > >> >> On 11/01/18 02:30, Chanho Park wrote: >> > Hi Philippe, >> > > > > Okay. I’ll test them when you rese

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 02:19 PM, Wouter van der Beek (wovander) wrote: We can use python to do the cbor conversion.. Hi, On non swagger files json2cbor does more than the conversion, this is also a way to test the tool we're shipping and track differences (or regression) IMHO, It could be renamed

Re: [dev] .dat files not being .gitignored?

On 03/05/2018 05:49 AM, Heldt-Sheller, Nathan wrote: > > Hi Devs, > > > > It seems the various .dat files are no longer being .gitignored.  Since they are not in the /out dir, but are still rebuilt by scons, shouldn’t they be left out?  Is there a reason for this? > > > > Thanks, > Nathan Hi

Re: [dev] Is anybody getting successful Jenkins build?

Hi, Yes, for a couple of weeks Jenkins is not working as it used to be, meanwhile track: https://jira.iotivity.org/browse/IOT-2279 -- mailto:philippe.co...@osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/ ___ iotivity-dev mailin

Re: [dev] coding conventions: header file naming?

On 02/27/2018 12:45 AM, Gregg Reynolds wrote: On Mon, Feb 26, 2018 at 5:33 PM, Philippe Coval <mailto:philippe.co...@osg.samsung.com>> wrote: On 02/27/2018 12:24 AM, Thiago Macieira wrote: On segunda-feira, 26 de fevereiro de 2018 14:26:12 PST Philippe Co

Re: [dev] coding conventions: header file naming?

On 02/27/2018 12:24 AM, Thiago Macieira wrote: On segunda-feira, 26 de fevereiro de 2018 14:26:12 PST Philippe Coval wrote: I remember I renamed some C++ headers to .hpp suffix because filenames were clashing on case insensitive FS We can rename those few again, but make sure it'

Re: [dev] coding conventions: header file naming?

On 02/26/2018 08:42 PM, Mats Wichmann wrote: is there any point to setting up a naming convention for C++ header files? currently we have a few that are named .hpp (the convention I gather was proposed by the Boost folks), and a bunch named .h. that makes it seem like it's just the whim of the p

Re: [dev] clear distinction of what is below and above the APIs

On 02/23/18 00:27, Wouter van der Beek (wovander) wrote: Nice! Thx But why is this info living outside the IOTivity documentation? because it's not related to iotivity's internal, it was done for validation and demo purposes, to make sure iotivity was usuable in production context (insta

Re: [dev] clear distinction of what is below and above the APIs

On 02/22/18 16:19, Wouter van der Beek (wovander) wrote: Hi All, Hi Wouter ! Related to this, I am will be working on application level code, e.g. using the IOTivity API. I like to contribute this code to IOTivity or other open source project. of course you can create your own repo I w

Re: [dev] how to build iotivity samples

On 02/16/2018 04:04 PM, Mats Wichmann wrote: Just to get some clarity on this ... Yesterday I proposed fixes for a few buffer size problems reported by static analysis (valgrind). In commenting, George Nash noted that in some cases I had added oic_string.h in order to use OICStrcpy, but that o

Re: [dev] How to check whether libs are generated from build with SECURED=1 FLAG

On 07/02/18 09:39, Sun Lifeng 孙立峰 (690) wrote: > > Hi, dev > >   > > For IoTivity 1.3.1, I have 3 libs named as liboc.so, > liboc_logger_core.so, liboc_logger.so, libocpmapi.so, > libocprovision.so and liboctbstack.so. > libocpmapi will not be built if security wasn't enabled >   > > Unfortunately

Re: [dev] TinyCBOR 0.5 release

On 31/01/18 15:03, Mats Wichmann wrote: > On 01/31/2018 03:14 AM, Wouter van der Beek (wovander) wrote: >> Hi Thiago, >> >> Nice! >> >> Will this be github submodule in IOTivity, e.g. so that one does not have to >> do an separate github pull to get this code? >> Currently this is quite annoying t

[dev] solved, Re: TinyCBOR 0.5 beta1 release

On 24/01/18 01:09, Nash, George wrote: > Thiago feel free to add me (...) > -Original Message- > From: iotivity-dev-boun...@lists.iotivity.org > [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Tuesday, January 23, 2018 1:03 PM > To: iotivity-dev@li

[dev] [meta-oic][PATCH resend 5/5] Add recipe for IoTivity 1.3.1

Note that fail on warning flag has been added, and can be used in .bbappend if needed after reporting bugs: http://wiki.iotivity.org/report Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- Origin: https://github.com/tizenteam/meta-oic/tree/sandbox/pcoval/on

[dev] [meta-oic][PATCH resend 4/5] iotivity-sensorboard: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0003-server-Port-to-iotivity-1.2.0.patch | 68 ++ .../files/0004-build-Use-pkg-config.patch | 48 +++ .../iotivity-sensorboard_1.0.0.bb | 11 3 files changed, 127

[dev] [meta-oic][PATCH resend 3/5] iotivity-simple-client: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0002-build-Use-pkg-config.patch | 43 ++ .../iotivity-simple-client_1.1.0.bb| 8 +++- 2 files changed, 50 insertions(+), 1 deletion(-) create mode 100644 recipes-apps/iotivity-simple

[dev] [meta-oic][PATCH resend 2/5] Add recipe for IoTivity 1.3.0

Note that SECURITY is now enabled but might cause issues on some examples. Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README | 2 +- ...ging-Return-false-boolean-instead-of-enum.patch | 40 ++ recipes-core

[dev] [meta-oic][PATCH resend 1/5] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

: \ undefined reference to `coap_write_block_opt' Note that problem is also about to be fixed upstream directly in scons files. Bug: https://jira.iotivity.org/browse/IOT-2651 Relate-to: https://gerrit.iotivity.org/gerrit/#/c/22355/ Thanks-to: Mikko Ylinen Signed-off-by: Philippe Coval --- recipes

Re: [dev] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status

On 11/01/18 02:30, Chanho Park wrote: > Hi Philippe, > Hi Chanho Park, HNY to you > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes > in your github tree[1]. Yes they are still under review, did you test them ? Maybe I should resend them, now. > I wonder why you don’t post

Re: [dev] Sample codes in C++ for Security Resource Manager

On 05/01/18 05:24, UDAY M.S wrote: > > Hi > > The sample codes demonstrating the discovery and handling of requests to secured resources available in  location iotivity/resource/csdk/stack/samples/linux/secure uses the 'C' API's of IoTivity. > > Are there any sample codes which demonstrate the usag

Re: [dev] Proposed API guidelines

On 03/01/18 23:44, Gregg Reynolds wrote: > > > On Wed, Jan 3, 2018 at 3:49 PM, Dave Thaler > wrote: > > Below > >   > > *From:* Gregg Reynolds [mailto:d...@mobileink.com > ] > *Sent:* Tuesday, January 2, 2018 9:46 PM >

[dev] [meta-oic][PATCH 5/5] Add recipe for IoTivity 1.3.1

Note that fail on warning flag has been added, and can be used in .bbappend if needed after reporting bugs: http://wiki.iotivity.org/report Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README | 2 +- recipes-core/iotivity

[dev] [meta-oic][PATCH 4/5] iotivity-sensorboard: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0003-server-Port-to-iotivity-1.2.0.patch | 68 ++ .../files/0004-build-Use-pkg-config.patch | 48 +++ .../iotivity-sensorboard_1.0.0.bb | 11 3 files changed, 127

[dev] [meta-oic][PATCH 2/5] Add recipe for IoTivity 1.3.0

Note that SECURITY is now enabled but might cause issues on some examples. Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README | 2 +- ...ging-Return-false-boolean-instead-of-enum.patch | 40 ++ recipes-core

[dev] [meta-oic][PATCH 3/5] iotivity-simple-client: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0002-build-Use-pkg-config.patch | 43 ++ .../iotivity-simple-client_1.1.0.bb| 8 +++- 2 files changed, 50 insertions(+), 1 deletion(-) create mode 100644 recipes-apps/iotivity-simple

[dev] [meta-oic][PATCH 1/5] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

: \ undefined reference to `coap_write_block_opt' Note that problem is also about to be fixed upstream directly in scons files. Bug: https://jira.iotivity.org/browse/IOT-2651 Relate-to: https://gerrit.iotivity.org/gerrit/#/c/22355/ Thanks-to: Mikko Ylinen Signed-off-by: Philippe Coval --- recipes

Re: [dev] updating on iotivity target cleanups, etc.

Hi, May I also share that now users can rely on scons install to install in standardized paths (on gnu/unix/linux tizen etc) Headers go into /usr/include/iotivity (some are marked experimental: https://wiki.iotivity.org/api ) Examples and dat files are also installed in: /usr/lib/iotivity/ M

Re: [dev] About SECURED mode

On 11/12/17 17:10, Mats Wichmann wrote: > On 12/11/2017 02:04 AM, Sun Lifeng 孙立峰 (690) wrote: >> Hi, dev, >> >> For IoTivity project, about SECURED mode, for my understanding, I should >> generate dat file for the SVR database. Am I right? yes you need to write ACL in json and then compile it c

Re: [dev] gerrit workflow: are we not getting enough patch reviews?

On 07/12/17 20:22, Mats Wichmann wrote: > If you do a query like this: > > https://gerrit.iotivity.org/gerrit/#/q/status:open+project:iotivity+is:mergeable+AND++NOT+label:Code-Review%253D-1+AND++NOT+label:Code-Review%253D-2++AND+NOT+label:Verified%253D-1 > yes, that's a lot, feel free to add me as

Re: [dev] forgot my login cred in gerrit.iotivity.org

On 06/12/17 15:48, rami alshafi wrote: > > any idea how to recover my logi creds for the gerrit.iotivity.org site? > > Thanks, > > -Rami > Hi Rami, I am seeing you there as: Rami Alshafi Can you log in https://identity.linuxfoundation.org/ ? -- mailto:philippe.co...@osg.samsung.com gpg:0x467

Re: [dev] IoTivity 1.3.1-RC6 tag announcement

Hi everyone, On 04/12/17 15:29, Mats Wichmann wrote: > On 11/30/2017 11:56 PM, ABITHA S wrote: >> Dear All, >> >> I am glad to announce that *RC6* tagging is done on *1.3-rel* branch. >> >> With *1.3.1-RC6* there was a failure related to Random PIN based OTM, which >> has >> been fixed. >> >> P

Re: [dev] [yocto] Undefined reference build error on rocko branch

On 04/12/17 08:00, Geonho Kim wrote: > I met now below error message when I had built iotivity 1.2.1 on yocto > rocko branch. > I'm not sure whether that is now issued problem or it happended only > my PC. > > > | > /home/xxx/yocto/yocto-rocko/305-build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi

Re: [dev] build iotivity on openwrt.

On 29/11/17 09:08, RAIN via iotivity-dev wrote: > Dear All, > > > i saw this page [dev] IoTivity 1.2.0 build for openwrt > > (...) > the error message is very long... > > iotivity need download other github source, is t

Re: [dev] build issues on windows with rel1.3

On 22/11/17 12:48, Wouter van der Beek (wovander) wrote: > Ok created congratulation ;) > Still can't log in... > wavd...@gmail.com is my alias on the net... Your login should be a word not an email Can you log in : https://identity.linuxfoundation.org BTW, I just edited this page: https://wik

Re: [dev] build issues on windows with rel1.3

On 22/11/17 12:06, Wouter van der Beek (wovander) wrote: > > Hi Phil, > >  > > ERROR_ON_WARN=False  Nope does not work… Well it should > -i make sure that it continues compiling but the link stage does not work, since objects are missing. It looks like a windows specific case, I can help on lin

Re: [dev] build issues on windows with rel1.3

On 22/11/17 11:22, Wouter van der Beek (wovander) wrote: > > Hi > Hi Wooter >   > > I know that an action was done to fix warnings and flag them as issues.. > > However this has an drawback that I can’t compile the stack on windows: > Then please report a bug to be reproduced, It would help   >

Re: [dev] [Iotivity-maintainers] request for 1.3-rel code freeze

On 21/11/17 11:28, ABITHA S wrote: > > Dear Phil, Hi Abitha, > >  > > Post security issues are addressed, testing is in progress for confirming stability of the code. Below is the summary of present status. (...) > 2. CTT update for testing optional features are in progress and we are awaiting u

Re: [dev] request for 1.3-rel code freeze

On 05/11/17 01:55, Heldt-Sheller, Nathan wrote: > > Hi folks, > Hi everyone, > >   > > As we are just about to tag 1.3-rel RC5, > good, I've tried to build on various system I am supporting, so far so good, but some may expect problem due to scons versions but it's not a blocker, and I will push mo

Re: [dev] Build Problem when modify the code of simpleserver

On 10/11/17 18:40, Mats Wichmann wrote: > On 11/10/2017 05:16 AM, 翟墨 wrote: >> Dear developers: >>Hi! I built iotivity-1.2.1 both on Raspberry 3. I want to modify the >> code of simpleserver to operate the gpio to control the led light state. This is the good way to check, 1st time blinkin

Re: [dev] issues when build iotivity for raspberry pi

On 09/11/17 14:59, 翟墨 wrote: > Dear developer: >        I tried to build Iotivity-1.3_rel with arg TARGET_ARCH=arm on > Rapberry 3 Model B as said , I don't thing TARGET_ARCH=arm is needed when building on device > instead of linux, you mean on you host ? > and it built successfully. Good > How

Re: [dev] issues when build iotivity for raspberry pi

On 05/11/17 06:30, 翟墨 wrote: > Dear develops: >         Hi! I followed the guidance > in https://wiki.iotivity.org/build_iotivity_for_raspberry_pi, to build > iotivity for raspberry pi 3 with raspbian jessie OS. When I built > with scons TARGET_ARCH=arm in home/pi/iotivity-1.3.0,  I met an error:

Re: [dev] About the difference PUT and POST action

On 31/10/17 09:24, sunlf wrote: > > Hi, devs, > > > > For C++ API, here are 2 functions, PUT and POST. > > > > What’s the difference between these 2? Thanks for asking, because it's not obvious, It worth to be confirmed, but I am not sure there is a direct mapping from 4 CRUD ops to POST, GET, PUT

Re: [dev] help : make cbor(.dat file)

Please tell which file are you running and make sure it configured to use persistant storage (to overload fopen) Like the top example at : https://wiki.iotivity.org/examples Maybe other examples should be fixed or not built when SECURITY is enabled Hope this help

Re: [dev] Iotivity1.3.0 communication issues in simple server-client module

On 16/10/17 10:28, ­SHASHI RAJ PANDEY(대학원 컴퓨터공학과) wrote: > Dear Sir/Madam, > > Warm greetings. > > We are deploying *Iotivity1.3.0* in between Ubuntu host and > RaspberryPi3 for an academic purpose.The build was successful in > Ubuntu14.04. However , the ./simpleclient ./simpleserver modules > ca

Re: [dev] iotivity 1.3-rel and CTT

On 13/10/17 08:18, jinhong kim wrote: > Hello all > > I am porting iotivity 1.3-rel to my OS. > > Which OS if I am not too curious ? Let it know at: https://wiki.iotivity.org/os (...) > So i want reference iotivity 1.3-rel linux example(server role). This page is explaining about supported exampl

Re: [dev] Selectively turn unit tests on/off

On 05/10/17 19:13, Nash, George wrote: > As Mats already pointed out you cannot filter from the scons script. Once > they are built you can run them individually. yes, You can run a specific test on specific configuration: scons LOGGING=1 VERBOSE=1 TEST=1 RELEASE=false SECURED=1 resource/csd

Re: [dev] About centos system

On 02/10/17 11:14, VanCutsem, Geoffroy wrote: > >> From: iotivity-dev-boun...@lists.iotivity.org >> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ??? >> Sent: Saturday, September 30, 2017 11:06 AM >> To: iotivity-dev@lists.iotivity.org >> Cc: su...@haierubic.com; liuwe...@qq.com

Re: [dev] Feature list request for Iotivity 1.3.1 release.

On 11/09/17 11:57, ABITHA S wrote: Samsung Enterprise Portal mySingle Hi IoTivity developers, In Order to achieve the release milestone in October with the High level Mission for Iotivity 1.3.1 being OCF1.3 certification Compliant as confirmed from OCF F2F meeting. According to the Iotivi

[dev] [meta-oic][PATCH 1/3] Add recipe for IoTivity 1.3.0

Note that SECURITY is not enable to enable smooth transition. to next version which should provide better support (including examples). Signed-off-by: Philippe Coval --- README | 2 +- ...ging-Return-false-boolean-instead-of-enum.patch | 40

[dev] [meta-oic][PATCH 3/3] iotivity-sensorboard: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- Origin: https://github.com/tizenteam/meta-oic/tree/sandbox/pcoval/on/master/review .../files/0003-server-Port-to-iotivity-1.2.0.patch | 68 ++ .../files/0004-build-Use-pkg-config.patch | 48

[dev] [meta-oic][PATCH 2/3] iotivity-simple-client: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0002-build-Use-pkg-config.patch | 43 ++ .../iotivity-simple-client_1.1.0.bb| 8 +++- 2 files changed, 50 insertions(+), 1 deletion(-) create mode 100644 recipes-apps/iotivity-simple

[dev] [meta-oic][PATCH v2] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

: \ undefined reference to `coap_write_block_opt' Note that problem is also about to be fixed upstream directly in scons files. Bug: https://jira.iotivity.org/browse/IOT-2651 Relate-to: https://gerrit.iotivity.org/gerrit/#/c/22355/ Thanks-to: Mikko Ylinen Signed-off-by: Philippe Coval --- O

[dev] [meta-oic][PATCH] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

: \ undefined reference to `coap_write_block_opt' Note that problem is also about to be fixed upstream directly in scons files. Bug: https://jira.iotivity.org/browse/IOT-2651 Relate-to: https://gerrit.iotivity.org/gerrit/#/c/22355/ Thanks-to: Mikko Ylinen Signed-off-by: Philippe Coval --- O

Re: [dev] 答复: One question about client finding resouces

ut when I wrote a client, it shows that no playload can be > found. Do you have any ideas about this? > > > > Thanks > > > > Jason Sun > > > > > > *发件人:*Philippe Coval [mailto:philippe.co...@osg.samsung.com] > *发送时间:*2017年9月1日17:09 > *收件人:*sunl

Re: [dev] One question about client finding resouces

On 01/09/17 09:04, sunlf wrote: > > Hi Devs > > > > I met a problem while coding OCF app. > > > > I created resources using C language with attached file > Server.c . But, I can’t find the resource created by Server > with C++ code with attached file Client.cpp. > > > > If I using C

Re: [dev] problem cross-compiling IoTivity

On 30/08/17 11:01, Iosif Hamlatzis wrote: > 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. on which OS ? how was it built ? > Then I recompiled my server for

Re: [dev] problem cross-compiling IoTivity

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

Re: [dev] failed bitbake meta-java

On 29/08/17 10:11, Iosif Hamlatzis wrote: > After fixing checksums and patches for icedtea7-native/2.1.3-r1.0 the > image starts compiling but I get a few errors. My host machine > is Ubuntu 14.04.5 under VirtualBox > > > > > | >&2 echo "*** This OS is not supported:" `uname -a`; exit 1; > | ***

[dev] jenkins outage

Hi, I am observing today, that jenkins is not queuing new jobs and fail to trigger them individually, have you found the root cause of this issue that already happened before: https://jira.iotivity.org/browse/IOT-2279 If not maybe a watchdog could be a desirable workaround to restart it autom

Re: [dev] Server throws exception (not on all boards)

On 23/08/17 12:01, Iosif Hamlatzis wrote: I'm testing on two different boards. A raspberry pi3 (with no problem) and also was given another board by Televes with main processor Dual i.MX6 Lite (this one has the problem) Both of them running yocto. On the raspberry I installed yocto, ok then

Re: [dev] Server throws exception (not on all boards)

On 23/08/17 11:42, Iosif Hamlatzis wrote: I've tried every sample that comes with IoTivity to compile with bitbake and test the servers with my development board What dev board are you using ? We know that those boards are working fine: http://wiki.iotivity.org/hardware and all throw the same

Re: [dev] build sys

On 15/08/17 22:19, Gregg Reynolds wrote: On Aug 15, 2017 9:13 AM, "Thiago Macieira" > wrote: On Monday, 14 August 2017 19:37:17 PDT Gregg Reynolds wrote: > On Aug 14, 2017 8:53 PM, "Thiago Moura" mailto:thiago...@gmail.com>> wrote: > > Talking

Re: [dev] generated .dat files

On 22/07/17 20:18, Mats Wichmann wrote: On 07/21/2017 11:53 AM, Philippe Coval wrote: On 21/07/17 19:34, Nash, George wrote: If I understand right. Currently the json2cbor program does not have support for cross compilation. For this reason we still need to have dat files checked into the

Re: [dev] generated .dat files

On 21/07/17 19:34, Nash, George wrote: If I understand right. Currently the json2cbor program does not have support for cross compilation. For this reason we still need to have dat files checked into the code base for cross compilation situations. Yes I did this on purpose to avoid inconsisten

Re: [dev] Static Analysis Tool

On 21/07/17 11:30, Pramod H G wrote: Hi, I have a question on which tool to be used for static analysis 1) Sonar Qube Interesting, but the web service is not available now :( https://sonarcloud.io/ 2) Coverity AFAIK coverify used manually from time to time, and fix code accordingly BTW

Re: [dev] 3axis sensor

On 20/07/17 19:15, Iosif Hamlatzis wrote: Is there a sample/example for IoTivity with "oic.r.sensor.threeaxis.json" similar to "oic.r.switch.binary.json" In the various examples you access always a simple variable (bool, int etc) but I want to find out how to access an object like the array

Re: [dev] git.iotivity.org????

On 19/07/17 19:00, Morrow, Joseph L wrote: > Hi Phillipe, > > Can you try to ping the Helpdesk on this? Hi Joseph, I've been confirmed that this ticket is still open and under investigation by LF: Reported as "IoTivity Helpdesk #43006 AutoReply: git unsync & jenkins health" > It’s been a wee

Re: [dev] many IoTivity samples broken with security

On 14/07/17 22:50, Gregg Reynolds wrote: On Jul 14, 2017 3:38 PM, "Heldt-Sheller, Nathan" > wrote: Hi Gregg, I agree that sample apps have to be maintained, so yes they should be fixed, when they are discovered to be broken. I think they

Re: [dev] git.iotivity.org????

Thanks Joseph, for notifying this, this is annoying but not blocking us as gerrit is still working. Also it looks like jenkins is not fully functional today, I have also forwarded it to jira and helpdesk, Track: https://jira.iotivity.org/browse/IOT-2279 And will try to reach LF on IRC if pro

Re: [dev] Hi, Can you tell me how to see OIC_LOG_V messages?

On 12/07/17 17:55, Mats Wichmann wrote: On 07/11/2017 12:43 AM, 강태규 wrote: for example at Arduino's ocserver.cpp OIC_LOG_V(INFO, TAG, "Stack: %u Heap: %u", (unsigned int)&tmp, (unsigned int)__brkval); OIC_LOG_V(INFO, TAG, "Unallocated Memory between heap and stack: %u",

Re: [dev] Problem in Makefile bitbaking server.cpp in Yocto

On 12/07/17 12:04, Natalia Theologou wrote: Hello all, I am following the template of iotivity-simple-client inside recipes-apps in order to bitbake my custom simple server and simple client. The client succeeds in bitbaking but the server has the errors: Again, please report bug for suppo

[dev] Cross compile Iotivity for arm

was ${@bb.fetch.get_checksum_file_list(d)} which triggered >>>>>>> exception ValueError: need more than 1 value to unpack > Thank you. > > > *From:* Philippe Coval > *Sent:* Monday, July 10, 2017 4:50 PM > *To:* Natalia Theologou; iotivity-dev at lists

[dev] Cross compile Iotivity for arm

of Yocto and with the > http://git.yoctoproject.org/cgit/cgit.cgi/meta-oic/commit/?h=1.2.0&id=028a5c234fb9fe51b39db339f7d4250fba978198 > > > ---- > *From:* iotivity-dev-bounces at lists.iotivity.org > on behalf of Philippe Coval > > *Sent:* Monday, July 10, 2017 11:25 AM > *To:

[dev] Cross compile Iotivity for arm

On 08/07/17 17:42, Natalia Theologou wrote: > > Hello, > > > I am trying to cross compile iotivity for arm architecture. I am > getting the error that it can not find boost_thread. > > I found out that I have to cross compile all the libs that I > want (boost, gtest0 from a previous thread. > >

[dev] build.iotivity.org = 504 Gateway Time-out -- Re: jenkins completely broken

Hi, Back to title of email, it look that jenkins is offline again, I've noted some info at: https://jira.iotivity.org/browse/IOT-2279 and also send notice to helpdesk. Don't hesitate to comment that upper link, to avoid cross communication. On 16/06/17 01:11, Thiago Macieira wrote: > On Monday

[dev] Weird crash in specific ubuntu version [16.04 - 64-bit]

On 14/06/17 12:48, Jay Sharma wrote: > > Hi All, > > I am facing a weird crash while running gtest cases in IoTivity. > > I was trying to run the *rcs_common_test *of the RE service on > different machines: > Hi Jay, yea I observed that RE is not stable, so I also reported stability issues at:

[dev] jenkins completely broken

On 13/06/17 17:17, Mats Wichmann wrote: > On 06/13/2017 08:30 AM, Kevin Kane via iotivity-dev wrote: >> We've explored splitting the patch into multiple chunks before, and decided >> it was a bad idea. The only value it appears to add is making the patch >> files more human-readable, but it com

[dev] solution to Re: jenkins completely broken

On 13/06/17 06:51, Thiago Macieira wrote: > On segunda-feira, 12 de junho de 2017 17:34:04 PDT Mats Wichmann wrote: >> as far as I can see, the push to mbedtls 2.4.2 broke the patch that is >> applied on top of that repository. I'm seeing 100% of the builders fail >> now, with these sorts of mess

[dev] architecture based problem

On 07/06/17 08:35, Shubhendu yadav wrote: > Sir > > as i was building in the main directory of iotivity using scons in > artik10 it is giving me error regarding 'armv7l' on the artik > board.Please suggest some solution > Hi, Are you building on device for fedora 22 ? Maybe you can try to cross

[dev] note on sconscript cleanups

Thank Mats for your help on that, this is appreciated, I think master is the good place to prepare next release, 1.4-rel or 2.0-rel ? But I am a bit reluctant to change all in 1.3-rel, unless there is valid reason to do that (regressions etc). and it needs to be tracked off course. Last advice, a

[dev] proper iotivity installation

On 18/05/17 15:35, Peter Hatina wrote: > Hello folks, Hi Peter, > > can you help me install IoTivity into an arbitrary path (eg. /opt)? Until > now, I haven't found any simple way how to do it. on which OS? > > I am looking for something similar: > > # make DESTDIR=/path/for/installation install

[dev] sampleserver help

On 18/05/17 01:44, rami alshafi wrote: > > Hello, > Hi, I am not a security expert but I am also curious about supported examples, I have observed some kind of regression on some of them (compared to 1.2-rel branch), but as I saw many ongoing work on security domain I didn't dare to report a ti

[dev] jenkins stability and status ?

Hi, It look like jenkins is not working anymore: queue is empty at: https://build.iotivity.org/ci/ while we have unverified patches pending at : https://gerrit.iotivity.org/gerrit/#/q/status:open+project:iotivity+is:mergeable+AND++NOT+label:Code-Review%253D-1+AND++NOT+label:Code-Review%253D-2++A

[dev] RPI zero build problem

On 17/05/17 11:06, ??? wrote: > > 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. > > an

[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

[dev] Bitbake meta oic layer

On 13/05/17 16:25, Natalia Theologou wrote: > > Hello, > > > I need a help if anyone knows. > > I have added meta-oic layer to sources folder. When I bitbake-layers > show-layers I can see the meta-oic layer. > > I only need to bitbake the layer just to smart install the rpm files > to a board.

[dev] IoTivity 1.2.0 Unit Test Build - Linking Error

ified%253D-1 Sorry for the noise. On Fri, May 12, 2017 at 4:29 PM, Philippe Coval < philippe.coval at osg.samsung.com> wrote: > On 15/11/16 07:50, Morrow, Joseph L wrote: > > Hi All! >> > Hi Joseph > > I have just tried to build IoTivity with GCC/G++ 4.6.4 on a 64-b

[dev] RPI zero build problem

On 12/05/17 17:11, Mats Wichmann wrote: > On 05/11/2017 10:43 PM, ??? wrote: >> hello. >> >> any body build&run iotivity on RPI zero? >> im tring this and get some error. >> >> if you do this, share a tip. >> >> BR, >> Jaehwan kim > I know some people have built for RPi (maybe not the zero

[dev] IoTivity 1.2.0 Unit Test Build - Linking Error

On 15/11/16 07:50, Morrow, Joseph L wrote: > Hi All! Hi Joseph > I have just tried to build IoTivity with GCC/G++ 4.6.4 on a 64-bit Ubuntu > 16.04 machine. It should be supported, I added some tips in: https://wiki.iotivity.org/os#ubuntu_1604_lts > I made sure to make sure I have all the depend

[dev] Error :- boost_thread library

On 06/03/17 09:31, Philippe Coval wrote: > > On 06/03/17 05:04, Katewal Pooja Deepaksing wrote: >> Hi, >> >> I clone the IoTivity code and checkout with the one of the branch, >> and I am getting the below mentioned error, >> >> ERROR :- &q

[dev] svr db, static provisioning - help needed

On 23/04/17 18:18, Thiago Moura wrote: > Hi Alex. Thanks for looking into it. > (...) > Anyway, I think this is not the right approach on making breaking > changes (asking if anyone will be affected). > IoTivity has a really weird release cycle. If it follows a semantic > versioning developers ar

[dev] iotvity compile error!

On 26/04/17 09:31, sxlyq at sina.com wrote: > Hi, guys: > >I am compiling the source code on Ubuntu 12.04, 12.04 is end of life isnt it ? For community at least according to: https://www.ubuntu.com/info/release-end-of-life Is it possible for you to upgrade to current LTS (14/15) as listed at

  1   2   3   >