[dev] Control-manager build issues in iotivity

- bounces at lists.iotivity.org] On Behalf Of Venkayamma Dudipally Sent: Monday, June 29, 2015 6:28 PM To: iotivity-dev at lists.iotivity.org; iotivity-dev-request at lists.iotivity.org Subject: [dev] Control-manager build issues in iotivity Hi All, While we are trying to build the Control

[dev] Control-manager build issues in iotivity

a Dudipally; iotivity-dev at lists.iotivity.org; iotivity-dev-request at lists.iotivity.org Subject: RE: [dev] Control-manager build issues in iotivity Hi Venky, Control Manager has been released in IoTivity 0.9.0 version which does not have Scons environment. For more detail, you can refer t

[dev] Control-manager build issues in iotivity

Hi All, While we are trying to build the Control-manager service, It's not linking the libraries base and uuid in RESTframework and there are no libraries present (path in Sconscript file to link the base and uuid libraries) . There is no SConscript and Source files to create libraries. We wrot

[dev] Control Manager

Markus, I understand and I am leaving it with Uze to drive that issue. Pat From: Markus Jung [mailto:markus.j...@samsung.com] Sent: Thursday, January 29, 2015 7:48 PM To: Lankswert, Patrick; Uze Choi; iotivity-dev at lists.iotivity.org Subject: Re: Re: [dev] Control Manager Hello Pat, I

[dev] Control Manager

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: 201501300948142_QKNMBDIF.gif Type: image/gif Size: 13168 bytes Desc: not avai

[dev] Control Manager

) [mailto:uzc...@samsung.com] Sent: Wednesday, January 28, 2015 7:46 PM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Control Manager Hi Pat, As I mentioned several times, Due to not code generation issue but resource model alignment issue, I would not merge the

[dev] Control Manager

es at lists.iotivity.org] On Behalf Of Lankswert, Patrick Sent: Thursday, January 29, 2015 4:50 AM To: 'iotivity-dev at lists.iotivity.org' Subject: Re: [dev] Control Manager Uze, If we are in agreement, how do you want to proceed regarding pulling the control-manager into master? Pat

[dev] Control Manager

Manager Thiago, I see your point. Pat -Original Message- From: Macieira, Thiago Sent: Tuesday, January 27, 2015 12:40 PM To: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager On Tuesday 27 January 2015 15:25:16 Lankswert, Patrick wrote: > Thi

[dev] Control Manager

> -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Keane, Erich > Sent: Tuesday, January 27, 2015 9:49 > To: Macieira, Thiago > Cc: iotivity-dev at lists.iotivity.org > Subje

[dev] Control Manager

Thiago, I see your point. Pat -Original Message- From: Macieira, Thiago Sent: Tuesday, January 27, 2015 12:40 PM To: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager On Tuesday 27 January 2015 15:25:16 Lankswert, Patrick wrote: > Thi

[dev] Control Manager

I come down with Thiago here. From a contributor's perspective, generated code is bad enough. However, if I have patch that I'm preparing to submit a pull request/code review for, and the project re-generates existing code, you've just made my patch likely unmergeable or even impossible to submit

[dev] Control Manager

the above scenario, the tool is irrelevant, yes? Pat -Original Message- From: Macieira, Thiago Sent: Tuesday, January 27, 2015 12:10 PM To: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager Hi Pat I don't agree with your conclusion #2.

[dev] Control Manager

at lists.iotivity.org Subject: RE: [dev] Control Manager Pat, Having looked at the generated files in Control Manager, I now understand Uze's mails better, we may well be able to live with choice #2 (live with generated code, but never generate it again.) Here is why I believe this:

[dev] Control Manager

of this issue. John -Original Message- From: Lankswert, Patrick Sent: Monday, January 26, 2015 10:20 AM To: Light, John J; uzchoi at samsung.com; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Control Manager John, You can find a bulk of them in by looking for the &#x

[dev] Control Manager

...@lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Monday, January 26, 2015 8:48 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager On Tuesday 27 January 2015 10:12:19 ??? wrote: > As like Jay's comment in the next mail from you, Tool is just what > help the code

[dev] Control Manager

On Tuesday 27 January 2015 15:25:16 Lankswert, Patrick wrote: > Thiago, > > I am not sure that we are disagreeing. I see only one public form, the > contributed code. > > Consider the case, that I contribute a bundle of source that may or may not > come from a code generator. If I contribute more

[dev] Control Manager

6, 2015 8:48 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Control Manager > > On Tuesday 27 January 2015 10:12:19 ??? wrote: > > > As like Jay's comment in the next mail from you, Tool is just what > > help the code made easily. > > If peop

[dev] Control Manager

code example? Would you make it clear? BR, Uze Choi -Original Message- From: Lankswert, Patrick [mailto:patrick.lanksw...@intel.com] Sent: Monday, January 26, 2015 11:40 PM To: uzchoi at samsung.com; Light, John J; Macieira, Thiago; iotivity-dev at lists. iotivity.org Subject: RE: [dev]

[dev] Control Manager

Hi, everyone :) I would like to choose #2 with additional comments on it. Generally, we do use tools to do something quickly or not to add human-errors. Meaning, a tool is nothing a logic which helps us to create something we need. Therefore, I think we need to more focus on for what reason this t

[dev] Control Manager

On Tuesday 27 January 2015 10:12:19 ??? wrote: > As like Jay's comment in the next mail from you, Tool is just what help the > code made easily. > If people can make the code without tool, I feel we don't need to mandate > the tool contributed. > We need to aware that the strict contribution policy

[dev] Control Manager

amsung.com; Lankswert, Patrick; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Control Manager Uze Choi, Please point out the files in Control Manager that are generated. John Light -Original Message- From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Sunda

[dev] Control Manager

Subject: RE: [dev] Control Manager Hi John/Pat, First of all, the generated source code in Control Manager probably not be changed or extended soon, I believe. Then Let's exclude the Control Manager example from this discussion. Regardless the acceptance of generated code in Control Ma

[dev] Control Manager

project? Pat -Original Message- From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Sunday, January 25, 2015 10:28 PM To: Light, John J; Lankswert, Patrick; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Control Manager Hi John/Pat, First of all, the generated

[dev] Control Manager

nuary 24, 2015 2:37 AM To: Lankswert, Patrick; uzchoi at samsung.com; Macieira, Thiago; iotivity- dev at lists.iotivity.org Subject: RE: [dev] Control Manager Pat, Uze, I am having trouble understanding Uze Choi's comments, so I will suggest interpretations in the hope of coming to a common un

[dev] Control Manager

janvier 2015 18:36 To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager On Thursday 22 January 2015 16:55:03 Lankswert, Patrick wrote: > A large portion of the code was created by a code generator. The code > generator currently cannot be released as open source. The c

[dev] Control Manager

On Monday 26 January 2015 10:59:53 Stephane Lejeune wrote: > Who is(/are) the final author(/s) or right holders of the generated code? > (Does the tool owner become inadvertently a contributor ... ) It depends on the tool. Usually, the output of tools bears the same licence as the original source

[dev] Control Manager

: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org; Macieira, Thiago; uzchoi at samsung.com Subject: Re: [dev] Control Manager That seems acceptable to me. I'd definitely like a chance to SEE the generated code (or have it pointed out to me!) so we can judge viability of #2 (since it seems

[dev] Control Manager

ts.iotivity.org] On Behalf Of Lankswert, Patrick Sent: Friday, January 23, 2015 7:42 AM To: uzchoi at samsung.com; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager To all, Vijay and I have talked to the owner regarding the plan for the code generation to

[dev] Control Manager

> BTW, the next order of business is dependency handling. > > Pat > > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of ???(Uze Choi) > Sent: Thursday, January 22, 2015 8:41 PM

[dev] Control Manager

riginal Message- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ???(Uze Choi) Sent: Thursday, January 22, 2015 8:41 PM To: Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager Hi All, Here Code

[dev] Control Manager

ev at lists.iotivity.org Subject: Re: [dev] Control Manager On Thursday 22 January 2015 10:55:37 Keane, Erich wrote: > I agree with John. If at all possible, #1 would be awesome, and it > would be worth exploring what it would take to make it public/free. > > #2 is definitely someth

[dev] Control Manager

ivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Light, John J Sent: Thursday, January 22, 2015 11:05 AM To: Keane, Erich Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager Another option is a bit more involved, but it might b

[dev] Control Manager

: Thursday, January 22, 2015 10:56 AM To: Light, John J Cc: iotivity-dev at lists.iotivity.org; Macieira, Thiago Subject: Re: [dev] Control Manager I agree with John. If at all possible, #1 would be awesome, and it would be worth exploring what it would take to make it public/free. #2 is definitely

[dev] Control Manager

Light > > > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Thursday, January 22, 2015 9:36 AM > To: iotivity-dev at lists.iotivity.org > Subject: Re:

[dev] Control Manager

tor. John Light -Original Message- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Thursday, January 22, 2015 9:36 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Control Manager On Thursday 22 J

[dev] Control Manager

To all, The Control Manager feature on the control-manager branch provides a resource model and API built atop the IoTivity stack for accessing appliances. Teams at Samsung and Intel did an amazing job putting this together. The code base is ready for final review and merging into master. Howev

[dev] Control Manager

On Thursday 22 January 2015 10:55:37 Keane, Erich wrote: > I agree with John. If at all possible, #1 would be awesome, and it > would be worth exploring what it would take to make it public/free. > > #2 is definitely something I would be OK with, but if the generated code > isn't very maintaina

[dev] Control Manager

On Thursday 22 January 2015 16:55:03 Lankswert, Patrick wrote: > A large portion of the code was created by a code generator. The code > generator currently cannot be released as open source. The concern a number > of people have is that this code base cannot be modified by the open source > commun