[dev] Requesting repository for constrained implementation

etc. It's not un-doable, but definitely would take API reworkings at this point. -- Jon A. Cruz jon at joncruz.org

[dev] Need maintainer to approve changes related to TinyCBOR

.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Jon A. Cruz jon at joncruz.org

[dev] CoAP - HTTP Proxy Review Request

hout thought as to how to integrate with its HTTPS support then end up with major refactoring needs on the back end again. e.g. managing root certs can either be trivial or a nightmare, all depending on the integration details. -- Jon A. Cruz jon at joncruz.org -- next part ---

[dev] Tagging 1.1.1 RC3

s any more blocking issue, otherwise I would tag RC3 today. > BR > Markus > > > _ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Jon A. Cruz jo

[dev] New Project and maintainer in IoTivity

to create config.h. Should be at least ready to play with by the end of the weekend. -- Jon A. Cruz jon at joncruz.org ? -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160707/384abf8e/attachment.html>

[dev] Windows VS2013/2015 Jenkins failures

s like a valid catch that should be reproducible on other systems. If possible the original author should check into flow to see if reproducing a failure on non-Windows is not too difficult. Full checks under valgrind could flag something. -- Jon A. Cruz jon at joncruz.org ? Links: 1. https://gerri

[dev] Review request: merge windows-port to master

orked up SCons based generation of it, including env hashed checks to update when needed. It definitely sounds like time to get that up -- Jon A. Cruz jon at joncruz.org

[dev] Review request: merge windows-port to master

some more time before merging to master. > > BR > > Jinguk Jeong Has there been any progress on this front? Other changes are starting to get backed up waiting on this, as we are accumulating more and more engineering debt the longer we wait. -- Jon A. Cruz jon at joncruz.org -

[dev] uncrustify

nts keeping some flexibility to allow for legibility of code. -- Jon A. Cruz jon at joncruz.org

[dev] responding to comments

o when fixing some point is to update a new changeset but then go back to the prior revision and reply to the individual comments with "Done" for points that have been addressed. -- Jon A. Cruz jon at joncruz.org -- next part -- An HTML attachment was scru

[dev] [cftg] RE: OCF IANA Port Number Assignment

and a belief of what a required solution is. However, the problem itself has not been clearly communicated. Can you fill in details of what the setup is, what should happen, and what is happening instead? -- Jon A. Cruz jon at joncruz.org -- next part -- An HTML attach

[dev] GCC/G++ Compiler Version on 1.0.0-RC3 Tag

1k (text/plain) > + iotivity build error-04132016.txt > 32k (text/plain) > + ATT2.txt > 1k (text/plain) -- Jon A. Cruz jon at joncruz.org

[dev] Error using CSDK logger in objective-C

ntial problem, specifically error happen in Windows or > Google test? > I need the Chang answer for iOS. I'm curious Chang issue because, we > haven't experienced DEBUG keyword issue in iOS build here. > > BR, Uze Choi > -Original Message- > From: Jon A. Cruz [mailto:j

[dev] Error using CSDK logger in objective-C

elated with other reserved keyword > beyond these two definitions, > we need to think about it again as Jon suggested. Redefine the enum with > prefix. > > Let's clarify the problem first. > > BR, Uze Choi > -Original Message- > From: Jon A. Cruz [mailto:

[dev] Error using CSDK logger in objective-C

elete > it and all copies from your system and destroy any hard copies of it. > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Jon A. Cruz jon at joncruz.org

[dev] Review to a patchset for collection payload

I'll give it another pass now (did last night and only saw a few minor follow-up items), but the main point is that since Thiago had given it consecutive -1 reviews it would be best to see if it finally corrected all of his concerns. On 03/02/2016 04:38 AM, ??? wrote: > Samsung Enterprise Porta

[dev] CSDK building without the pthread support

Hi, It looks like you're following a direction that hasn't been well exercised yet. The codebase actually has two concepts tied into the defines. The first is to use only single threaded operations. The second was to support more constrained devices. Splitting and clarifying the differences wa

[dev] Android 6.0 Marshmallow

On 02/08/2016 03:50 AM, Jack Mingaw wrote: > On 8 February 2016 at 12:43, Jack Mingaw wrote: >> Hi, >> >> Did anyone try to run iotivity on Android Marshmallow? >> >> I got : >> >> 02-08 11:27:55.986 4413-4413/com.app.fr.example E/AndroidRuntime: >> FATAL EXCEPTION: main >> Process: com.app.f

[dev] [build] Integration Build Failing & Fix

Thanks! Looks like you're about 20 minutes ahead of me. I'd gotten the issue tracked down, but didn't have a fix in yet. On 01/28/2016 02:12 PM, Trevor Bramwell wrote: > Hi all, > > The integration build [1] for IoTivity is currently failing on Jenkins > since commit:45d985aab21955892ca85fb27cc3

[dev] Need API to set static "sid" and "port number".

g the big benefit to user from UI perspective. > > How about including this issue into the Jira ticket for in this coming > 1.1.0 release? > Markus, could you help it? > > BR, Uze Choi > > *From:*iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev

[dev] Need API to set static "sid" and "port number".

One aspect here sounds like code is depending on IoTivity devices to operate like some other common servers where HTTP is on port 80, telnet is on port 23, ssh on port 22, SMTP is on port 25, etc. Compliance with company IT policies, firewall requirements, vpn rules, etc. might come into play t

[dev] Iotivity does not build on mint OS X 10.11.1

Yes, I agree. Unfortunately my Mac is stuck on an ancient version of OSX since it is 32-bit (so it's happily running Linux mostly). I can work something up in the next few days if there are any people using OSX that can test things. Thanks On 01/14/2016 04:36 AM, Poussa, Sakari wrote: > Hi, >

[dev] IoTivity Android SDKs - current min API level requires Android 5

Long term we might also want to look at some of the strategies for making things optional at load or runtime in addition to just compile time. However, getting the client side to support 18 would be a good achievement. On 12/08/2015 11:44 AM, Kourt, Tim A wrote: > > The API level 21 is dictated

[dev] IoTivity Android SDKs - current min API level requires Android 5

On 12/08/2015 12:49 AM, Philippe Coval wrote: > > > On Tue, Dec 8, 2015 at 7:39 AM, Markus Jung > wrote: > > Hi, > > currently all Android related SDKs require min API level 21, which > is Android Lollipop. > > Should we change this to a lower A

[dev] Help with a build failure

On 11/03/2015 04:08 PM, Schulhof, Gabriel wrote: > Hey! > > On Tue, Nov 3, 2015 at 10:52 PM, Jon A. Cruz wrote: >> I'm actually chasing down a bit of a solution now... >> >> there is an immediate issue in that libcoap added a generated config.h. >> Probl

[dev] Help with a build failure

__________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] question about payload coding

he buffer of the size that TinyCBOR says >>> it should be and encoding should work (provided you have the same >>> data, of course). >>> >> >> ___ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] [Call for nomination] Maintainer (Discovery & Connectivity Project)

h Patrick and Erich. The chance to expand my role supporting the project would be a great opportunity and way for me to contribute more. Thank you. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com On 10/15/2015 07:59 PM, ??? wrote: > Develope

[dev] Iotivity examples/simpleclient fails at 'PUT' or 'Observer' sporadically (<20%)

> https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] [Pat, Uze, Vijay] IoTivity 1.0.0 release schedule (RC3)

ideally tell us exactly what > is taking longer than it should. > > Pat > >> -Original Message- >> From: Jon A. Cruz [mailto:jonc at osg.samsung.com] >> Sent: Wednesday, October 07, 2015 2:25 PM >> To: myeong.jeong at samsung.com; Lankswert, Patrick; ???;

[dev] [Pat, Uze, Vijay] IoTivity 1.0.0 release schedule (RC3)

gt; ?09/28, Make ?1.0.0-RC2? release to QA > > ?10/02, QA 2nd round complete > > ?10/05, Make ?1.0.0-RC3? release to QA > > ?10/09, QA 3rd round complete > > ?10/12, Website Open > > ?10/27~29, Plug Fest #4 > > And this is the final conclusion below at the last OIC OSWG F2F meeting > regarding the mandatory features that have to be in 1.0.0. > > ?High priority features to be pushed and released ? > > ?Blockwise transfer in CoAP > > ?CoAP serialization over TCP > > ?TLS support for RA (*Conditional ? Depends on availability by 9/18*) > > ?Zigbee plugin > > *June Yong Young* > OIC Open Sourece WG Project Planning & Requirement TG Chair > > IoTivity Release Function Lead > > > Samsung Electronics Co.,Ltd. > > Software R&D Center, IoT Solution Lab. | Web & Convergence Team > > Principal Engineer > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] [Pat, Uze, Vijay] IoTivity 1.0.0 release schedule (RC3)

r the 1^st activitiy. > > *1.0.0 : ?OIC Spec 1.0 Compliant release?* > > ?Type for Release : Major release, Feature Driven, PlugFest #4 > > ?Schedule (6 weeks ahead of QA completion) (cf. Original QA request is 6 > weeks > ahead of QA start) > > ?08/28, API freeze

[dev] Jenkins for iotivity unit tests build timeout

time? > > Pat > >> -Original Message- >> From: Jon A. Cruz [mailto:jonc at osg.samsung.com] >> Sent: Wednesday, September 30, 2015 2:20 PM >> To: Lankswert, Patrick; uzchoi at samsung.com; Agrawal, Sachin >> Cc: iotivity-dev at lists.iotivity.org >> Subje

[dev] Jenkins for iotivity unit tests build timeout

a patch pending that should alleviate the test timeout problem. > > Thanks, > -Ossama > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] CT_DEFAULT doesn't work anymore

t, > 61aebb520d1cf8fc250400e2d3fa3858c7ce8c24, the discovery is greatly > delayed and the observation fails because the ocserver returns 29 > (OC_STACK_COMM_ERROR) in the response to the observe request. > > HTH, > > > > Gabriel > > [0] https://gist.github.com/gab

[dev] it happened again

; > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] portability issue

Jawid; sorry, I mistook you for a > colleague with that name) > > That's great news! > > Can you send your modifications for review into Gerrit? > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists

[dev] portability issue

sion for certain Windows platforms). -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Presence in 0.9.2

t sure of all cases, but I believe there is a change going through review now that addresses at least some resourceUri setting in error responses. https://gerrit.iotivity.org/gerrit/#/c/2454/ -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Enable logging on osx/ios

anks Jon. > > I need to update the change set. > > Is the below the correct info how to do it? > > https://www.mediawiki.org/wiki/Gerrit/Tutorial#Amending_a_change > > > Sakari > > On 8/19/15, 10:06, "Jon A. Cruz" wrote: > >> Looks mostly go

[dev] Enable logging on osx/ios

___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] bool type issue (in RC3 branch)

t;>> is bool), even though there is a code about changing state value. >>> >>> (like m_state = false to m_state = true) >>> >>> The problem is occurred not only this simpleserver/simpleclient >>> app, but also other sample app, such as roomserver/roomclient. >>> >>> >>> >>> To sum up the issue, Integer type's value is working well (I mean >> the >>> Integer value is changed well), but bool type's value isn't. >>> >>> Also, I am not sure that other types of value (except integer >>> type) would be working well or not. >>> >>> >>> >>> >>> >>> Thanks. >>> >>> >>> >>> Best Regards, >>> >>> Soyoung Youn. >>> >>> >>> >>> >>> >>> >>> >>> ___ >>> iotivity-dev mailing list >>> iotivity-dev at lists.iotivity.org >>> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> >> >> >> >> >> ?. >> >> >> >> ??? ?? >> >> >> >> >> >> >> > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] warnings!

ins doesn't complain about warnings. > > John > > -Original Message- > From: Jon A. Cruz [mailto:jonc at osg.samsung.com] > Sent: Monday, August 03, 2015 3:35 PM > To: Keane, Erich; Light, John J > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev

[dev] [Android] JNI local reference table overflow (CA)

n the Bluetooth interface will lead to > unexpected behavior? > > > Here are some logs of my application for this issue: > http://pastie.org/10319711 > > > Thanks! > > > > Best Regard, === Yu-Hsin Hung, > Electrical Engineering and Computer Science Undergraduate Honors Program, > National Chiao-Tung Universiry, Hsinchu 300, Taiwan > (Phone) +886911012113 > (Email) hungys at hotmail.com (Website) http://hungys.logdown.com/ === > > > > > > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] warnings!

ead, fwrite, fclose, >> unlink }; >> >> OCRegisterPersistentStorageHandler(&ps); >> >> >> >> But this seems more fragile since the ordering matters. >> >> >> >> Is there a C initialization method I?m missing? >> &

[dev] Jenkins tests done with dependencies

> > office: Lilienthalstra?e 15, 85579 Neubiberg Germany > phone:+49 (89) 89899 - 7179 > e-mail: hauke.mehrtens at lantiq.com > > > > > ___________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] GCC/G++ Version

//lists.iotivity.org/mailman/listinfo/iotivity-dev > ___________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] GCC/G++ Version

mpiler_support?s[]=gcc<https://wiki.iotivity.org/compiler_support?s%5b%5d=gcc> > > Thanks, > > Joey Morrow So, does that mean we've officially dropped support for Ubuntu 12.04 LTS? -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Iotivity C stack APIs missing from website/documentation

covers the needed INPUT from both. Coordinating the names and "pages" is the area to look at. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] "expat" library download problem

> >> -Original Message- >> From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- >> bounces at lists.iotivity.org] On Behalf Of Jon A. Cruz >> Sent: Monday, July 20, 2015 10:07 AM >> To: yh_.joo at samsung.com; Zhang, Caiwen; iotivity-dev at lists.

[dev] "expat" library download problem

**SAMSUNG ELECTRONICS CO., LTD.*** > > * M**o**bi**le**+82.10.3794.8718* > > * E_mail********yh_.joo at samsung.com* > <mailto:yh_.joo at samsung.com><mailto:yh_.joo at samsung.com> > > * > > ** > > * > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Static Analysis

hould be some thought given to what might be the appropriate responsible disclosure policies. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] IoTivity in OpenWrt with build variables from environment

XXFLAGS. So one might hypothetically do something like CC=/home/person/custom_xcc/cc CFLAGS='-v -O9 --magic' scons (I believe the reason we need to explicitly consider all this is that SCons is a toolkit to allow us to make a build system, as opposed to pre-canned build systems like autot

[dev] Proposal for IP Adapter and request for feedback

ous networking abstraction IIRC. I'm trying to remember details from when I looked into this a few months back. One key is that ip aliasing is the outdated way to achieve it, so we are looking at multiple ways to get multiple IPs. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] HashTag: FixMe

hould check to see if it has something before trying to download it. So if the source/build were changed to use gtest the way its developers intended then that would be one less issue for you to be hitting. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] HashTag: FixMe

t to do such-and-such". If you are asking due to the first issue (which your later mail seems to indicate) then the proper solution would probably be for us to fix the broken tests so that building all tests won't need to be disabled. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] HashTag: FixMe

'OCHeaderOptionTest.cpp']) > > -Alias("unittests", [unittests]) > + Alias("unittests", [unittests]) > + > + env.AppendTarget('unittests') > > -env.AppendTarget('unittests') > -if env.get('TEST') == '1

[dev] To add payload length in CAInfo_t for block-wise transfer.

ngs for buffers. There are some significant differences and you've hit upon some of them. This had been pointed out several times in code reviews, and should have been followed-up on already. The JIRA ticket can help with that. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] HashTag: FixMe

n what makes good build-time tests vs. longer ones. So by building things that aren't always run you can do things like ensure API changes don't break all the handy tests you started with. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] circular includes causing warning on jenkins

;s a C11 feature. > The build machines are using the documented Ubuntu 12.04 baseline and that includes gcc 4.6.3 as it's mainline compiler. Not getting to use all the latest-and-greatest features is one annoying aspect to keeping code more portable. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] removal of the android_api branch

issues (though removing a commit definitely does). It starts to head off into areas similar to using the 'obliterate' command in Perforce (hint: that one should be an extreme exception to common practice). I seem to recall that a pre or post commit hook might do the job of preventing

[dev] Simple client/server in C

-apn > netstat.after, and no diff. > What networking topology do you have? Perhaps it's trying to use Ethernet when you only have WiFi interfaces up, or vice versa. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] support of "char" datatype

r rather than std::vector. Use of 'char' makes me thing of random 8-bit character strings in an unspecified encoding. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] GLib removal and thread-pool implementation-

ists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> ___ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotiv

[dev] CA into master merging question

gt; > Could anyone explain what purpose of this code? > > > > BR, Uze Choi > > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] glib

gt;>> The threading architecture of CA was written assuming profligate use >>> of independent threads, so extricating IoTivity from glib's clutches >>> will require much restructuring. >>> >>> John >>> >>> -Original Message----

[dev] Java package name: why com.iotivity not org.iotivity?

basically told that the code started with that domain/packaging and they were not taking the time to change existing code. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] glib

x27;ll probably run >> > into the same problems on many platforms with dubious c++11 support. > Right. > The C++11 support probably can't be used here. I'd thought about this for a moment, but glib is being used in the C-only realm of the code. It makes sense to keep that part more minimal. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] OCProcess & event loop

On 04/07/2015 04:17 PM, Thiago Macieira wrote: > On Tuesday 07 April 2015 15:46:54 Jon A. Cruz wrote: >> Pushing out so that the hosting app can call an appropriate select() >> equivalent then push into the stack as needed can eliminate the need for >> internal threading an

[dev] OCProcess & event loop

On 04/07/2015 03:56 PM, Thiago Macieira wrote: > On Tuesday 07 April 2015 15:23:24 Keane, Erich wrote: >> Our biggest CPU intensity currently is watching the ethernet/wifi >> adapters for change and JSON parsing/generation. Otherwise we are >> pretty low-hit. > > In an ideal world, "watching" sho

[dev] OCProcess & event loop

ow my hat in the remove glib camp too. >>>> >>>> On 4/7/15, 5:28 PM, "Light, John J" wrote: >>>> >>>>> " or since we're using glib anyway, GMainLoop?" >>>>> >>>>> I would prefer we move in the direction of weaning ourselves from >>>>> glib rather than using it more, since we are aiming at tiny processors. >>>>> >>>>> I believe there are simple solutions to the event loop issue that >>>>> don't require hammers. >>>>> >>>>> John >>>>> >>>>> >>> >> > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] API Doc on Website

heir unified approach is that Java developers get consistent documentation no matter what project or libraries they are working with. We definitely should keep that aspect. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Jenkins build timeout plugin

ning prior to code review. We could set the Jenkins build-timeout >> plugin to catch cases where the build runs for 30 minutes or more >> because someone forgot to use ?timeout ?k?, but should have. That is >> well outside the current 6 sigma build time range, and could be >> adjusted upwards if builds start taking significantly longer. >> >> >> >> Bill. >> >> >> >> >> ___ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Proposing Keyword Dictionary for the IoTivity Project

have > the resource >but if the other IoTivity stack outside > the > process has the resource >then it's remote resource. > > > > *Jung-hyun Oh. * > > **IoT Solution Lab. |*SW R&D Center *| SAMSUNG ELECTRONICS CO.,LTD > > *Mobile +82-10-9890-6731 *| Beyond your imagination, Always > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Documentation tools

merge the output of those > tools together into the final Doxygen file. > > BR, Uze Choi > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Lankswert, Patrick > Sent: Wednesday, Marc

[dev] Fwd: Re: Re: [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature

ers I wanted to be sure to address. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Fwd: Re: Re: [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature

ifferent ways to ramp up the unit testing. Then the question of pushing for more Test Driven Development (TDD) practices might also be examined. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Documentation tools

to the pertinent sections of generated documentation. Are there any reasons we shouldn't pick up the use of these two? Of course they will only be required for actual documentation builds and not for the core product. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jo

[dev] Blocker issue for Arduino builds

equire all developers to run builds for multiple targets before submitting a code change. Thus *all* developers contributing to IoTivity should be running the arduino builds. This should be combined with the consideration that it is not practical to expect all developers to have arduino hardwar

[dev] Blocker issue for Arduino builds

yACM0": No such file or directory Eavrdude: butterfly_recv(): programmer is not responding scons: *** [out/arduino/avr/release/resource/csdk/stack/samples/arduino/SimpleClientServer/ocserver/install_cmd] Error 1 scons: building terminated because of errors. Compilation exited abnormally with

[dev] Blocker issue for Arduino builds

recipe for confusion and bugs. On 03/18/2015 11:56 PM, Jon A. Cruz wrote: > If that's the solution, then it should really be the default. > > We need to be sure that all devs can run it easily, and also that the > build servers won't have any problems. > > On 03/18/2015

[dev] Blocker issue for Arduino builds

invoking scons build to skip uploading. > > For ex: > > scons TARGET_OS=arduino TARGET_TRANSPORT=ETHERNET TARGET_ARCH=avr > BOARD=megaADK > ARDUINO_HOME= *UPLOAD=false* > > Regards > > Abhishek Sharma > > --- *Original Message* --- > > *Sender*

[dev] Blocker issue for Arduino builds

de. https://jira.iotivity.org/browse/IOT-405 -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Scons config causing unit tests to fail

Sakthivel wrote: > > Jon, > Please post a change set with your fix. We will review and test it. > Thanks, > =Sam > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of Jon A. Cruz >

[dev] Scons config causing unit tests to fail

LINKFLAGS to LIBS in the linux scons script, or is anyone else up to speed on fixing scons files? -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Iotivity build server to run unit test with every build

On 03/11/2015 11:31 AM, Jon A. Cruz wrote: > On 03/11/2015 11:22 AM, Samidurai, Sakthivel wrote: >> Developers can run the same tests by passing TEST=1 in the command line >> option for scons when building locally. >> >> We have been migrated to Scons. >> >>

[dev] Iotivity build server to run unit test with every build

follow-up off-list. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Iotivity build server to run unit test with every build

Scons/1096/console. > > We would like to hear your inputs. > What's the current state on how developers should run the same tests when building locally? Have things been migrated to Scons, or is it still a mix of makefiles? -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Minimum compiler versions

required compiler versions? -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] [Simulator req. collecting]: [oswg] [Action Request] Final Action Item (with Deadline and Owner) after OSWG F2F Meeting in Santa Clara

ven useful in the past is a simple tool that digests capture files. Use wireshark or some command-line tool to capture, then later examine the captures with something else. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Host field ignored in findResource

> > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of Jon A. Cruz > Sent: Wednesday, February 25, 2015 3:11 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Host fie

[dev] Host field ignored in findResource

t is > not possible to specify which WiFi interface to use. > Ok. I'd just like to be sure it's on the record that the last constraint can be a major blocker. Most of my dev systems have multiple interfaces and I'm often not operating from the base one listed. This is also e

[dev] Thread-safety solution for the ITVTContext

tom. Or... we could at the least ensure that our internal wrappers are used in a way such that a public API for locking can be exposed. That sounds like a helpful separation. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Library names for IoTivity

h of the new ones. Thus we can start with the single library, but with a LEAN_AND_MEAN, or MINIMAL config option that turns off both single-threaded and C++ code plus disabling the build of a dynamic lib. And end-user/developer convenience would be the strong point in favor of the single unified lib. --

[dev] Ripping out the threads

lly the key. The end code normally won't be really any larger or more heavyweight, but just a little more cleanly organized (reduce globals, static function variables, etc). Proper abstraction can allow for clients with more needs to hook in additional implementation or details. One example I know if is if a hosting client is using LibCurl there might be need for some context. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] Comment blocks at beginnings of files

g IoTivity code feel more secure about the level of professionalism of the codebase. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] ISG meeting minutes (30 Jan, 2015)

ic term of "dynamic library" then. I'd like to quickly confirm then that the following will be in-scope for IoTivity (eventually): * .so dynamic library for Linux * .dylib dynamic library for OS X * .so loadable module/bundle for OS X * .dll dynamic library for MS Windows -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

[dev] ISG meeting minutes (30 Jan, 2015)

erally would be a need to support interesting combinations of static & dynamic on many fronts (static library linked to dynamic runtime, static library linked to static runtime...) So we might need to split the C into one or more DLLs and the C++ into one or more static libs. -- Jon A. Cruz - Seni

[dev] API Naming convention for IoTivity

swer then what we'd like them to be? >From some of my experience, using #include "iotivity/ocstack.h" #include "iotivity/Api.h" is better than #include "iotivity/ocstack.h" #include "iotivity/OCApi.h" It can help with setting up diffe

[dev] Breakage with transport codes

is an intentional choice of the OIC standard, or is it merely an implementation oversight in IoTivity code? If it is the latter, then it should not be too hard for me to get a patch to correct it. Thanks. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com

  1   2   >