Ragul,
You should be able to limit you build to only use IP transport
scons TARGET_TRANSPORT=IP
George
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Ragul Bhagwanth
Sent: Tuesday, April 19, 2016 10:16 PM
To: iotivity-dev at
I am happy for any feedback and questions.
George
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Wednesday, November 30, 2016 10:24 AM
To: Durbha, Viswanath ; MATTIA ANTONINI
Cc: iotivity-dev at lists.iotivity.org
I the work on the generic java bindings was **merged** with master yesterday:
- https://jira.iotivity.org/browse/IOT-1089
- https://gerrit.iotivity.org/gerrit/#/c/14931/
This change moves around all of the java related code. Since there is a java
implementation for almost
into it.
For the time being if you want to use java on Linux specify TARGET_TRANSPORT=IP
George
From: Thiago Moura [mailto:thiago...@gmail.com]
Sent: Tuesday, December 13, 2016 3:06 PM
To: Nash, George
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] generic java support merged with master
[mailto:jaehong...@samsung.com]
Sent: Tuesday, December 13, 2016 3:39 PM
To: Nash, George ; Thiago Moura
Cc: iotivity-dev at lists.iotivity.org
Subject: RE: Re: [dev] generic java support merged with master
Hi, George.
I saw change yesterday and I was a bit confused.
But your email solved my
There is no plan to merge it into the 1.2-rel branch. We never planned on
merging it into the 1.2-rel branch. This is clearly a feature for the next
release.
George
From: ??? (Uze Choi) [mailto:uzc...@samsung.com]
Sent: Tuesday, December 13, 2016 5:32 PM
To: Nash, George ; jaehong.jo
If anyone else continues to have this type of problems after running
$ sudo apt-get install \
build-essential git scons libtool autoconf \
valgrind doxygen
Please let us know. I will make sure the installation of dh-autoreconf is added
to the build dependencies listed in the wiki.
Phil
Currently building android on windows is not a supported configuration. This
does not mean it cannot be done it just means you are likely the first to
attempt this.
If the only thing you need is the S-SDK I would suggest trying
scons resource/csdk
I don?t think boost is needed to build the
Device specification.
This greatly simplified my code since I no longer need to wait for multiple
callbacks to create a full representation of the light.
George
From: ???(Uze Choi) [mailto:uzc...@samsung.com]
Sent: Friday, June 3, 2016 12:11 AM
To: Nash, George ; iotivity-dev
To change the LogLevel enum values to use a prefix was not hard but it
is a really large change **6692** lines of code changed due to adding
the OC_ prefix. ?I made the change and pushed it up to gerrit. If we
are seriouse about making this sort of change then all we need is a
JIRA ticket. ? Note
at 00:14 +, Nash, George wrote:
> To change the LogLevel enum values to use a prefix was not hard but
> it
> is a really large change **6692** lines of code changed due to adding
> the OC_ prefix. ?I made the change and pushed it up to gerrit. If we
> are seriouse about making this
> Because I am running ./auto_build with sudo. But sudo reset those env.
> I?ve try to run ./auto_build without sudo, it will gives me boost_thread
> error, don?t know what that means.
Did you build the first time using sudo scons? You probably have something
build that now only has sudo
This comes down to one of the core design ideas of SCons. A scons script
should be able to run on any system regardless of the environmental state of
that system. For this reason scons starts up a subshell and discards ALL
environment variables. This can be annoying since it can cause scons
The fix for gtest is considered a temporary fix. Google moved gtest from
code.google.com to github.com/google. When it was moved to github, file names
and code structure was changed just enough that it would no longer build.
By downloading from a mirror that maintained the old code structure
...@microsoft.com]
Sent: Monday, November 7, 2016 8:52 AM
To: Nash, George ; philippe.coval at osg.samsung.com;
iotivity-dev at lists.iotivity.org
Cc: aakash.kaushal at legrand.us
Subject: RE: [dev] Req- wiki.iotivity.org/android_build_instructions- Python
Build error
Is there a JIRA ticket tracking this issue
original email. Feel free
to add comments to the ticket and clean it up if needed.
George Nash
From: Aakash KAUSHAL [mailto:aakash.kaus...@legrand.us]
Sent: Monday, November 7, 2016 9:10 AM
To: Nash, George ; Kevin Kane ; philippe.coval at osg.samsung.com; iotivity-dev at
lists.iotivity.org; dthaler
November 8, 2016 11:42 AM
To: nikhil.a7 at samsung.com; Nash, George
Cc: iotivity-dev at lists.iotivity.org
Subject: RE: [dev] Running JUnit for android_api
George,
Can you response to these questions?
Thanks,
-Rick
From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivit
the generic-java branch and give it a try. Let me
know if you have any questions.
George Nash
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Thursday, October 6, 2016 12:06 PM
To: iotivity-dev
, 2016 2:56 PM
To: Nash, George
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Generic Java Bindings [IOT-1089]
Hi George,
On Fri, Nov 11, 2016 at 09:37:49PM +, Nash, George wrote:
> We are almost ready to merge the changes back in with master. As
> stated in the earlier em
This error is coming from the Jenkins xUnit plugin
(https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin) it is not from any
in the scons scripts.
You may need to work with Trevor from the linux foundation to figure this issue
out.
George
From: iotivity-dev-bounces at lists.iotivity.org
I am working on updating the SCons scripts to pull the gtest framework from
github instead of the mirror that we are currently using.
(https://jira.iotivity.org/browse/IOT-1517)
I have a solution checked into gerrit:
https://gerrit.iotivity.org/gerrit/#/c/14381/
I currently don't have access to
Back in September there was a discussion regarding security. There was a lot
of discussion regarding the use of the SECURED flag. At the time I volunteered
to update the SCons scripts to use SECURED flag by default instead of
defaulting to not using the SECURED flag. (See IOT-1320
I want to move away from the `autoconf` build that we are currently using. It
has not been supported by the google test framework since version 1.4 of google
test. I was trying to get the framework move over to github while making the
smallest change to our scripts as possible. I was going
The generic-java branch has not merged into master yet. Due to some bugs on
the master branch we were not able to verify the work to a level we felt
comfortable merging yet.
I hope to have a merge commit really soon. I want it merged this week but it
may take longer. The change touches a lot
Error seen this morning here.
https://build.iotivity.org/ci/job/iotivity-verify-tizen/4041/console
Let me know if you need any additional information
George Nash
-- next part --
An HTML attachment was scrubbed...
URL:
12:18 PM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Generic Java Bindings [IOT-1089]
On 10/06/2016 01:05 PM, Nash, George wrote:
> Larry Sachs, Rick Bell and myself will be taking ownership of the IOT-1089
> task of creating a Generic Java language bindings.
...
>
anywhere else if everything else
was working like it should.
George
From: Ward, Robert [mailto:robert.w...@landisgyr.com]
Sent: Thursday, October 13, 2016 9:27 AM
To: Nash, George ; Macieira, Thiago ; iotivity-dev at lists.iotivity.org
Subject: RE: [dev] Compile iotivity
? I have seen this error
TARGET_ARCH shows the following architectures. x86, x86_64, armeabi,
armeabi-v7a, armeabi-v7a-hard, and arm64-v8a
So far I have limited my android builds to x86, x86_64 and armeabi.
Do we expect android to build for any of the other architectures listed
(armeabi-v7a, armeabi-v7a-hard, and
Issue 1: Google has shut down the googlecode link and moved google test to
github.
Solution:
In extlibs/gtest/SConscript change
- gtest_url = 'https://googletest.googlecode.com/files/gtest-1.7.0.zip'
+ gtest_url =
'https://github.com/google/googletest/archive/release-1.7.0.zip'
github in the future. I
think someone mentioned moving to 1.8.0 which may not be a bad idea.
George
-Original Message-
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Thursday, September 1, 2016 11:33 AM
I am a little concerned that removing the android_x86 build will leave us open
for hard to find issues down the line.
ARM and x86 are a very different architectures. Do we believe all the x86
problems for android will be found by the Linux builds?
I also think that we don't need to build three
I am running into errors when building the code using VS2015.
When it tries to build the provisioningdatabasemanager.obj it fails saying it
cannot find sqlite3.h
I am able to reproduce this failure locally from `master` but I don't know why
it is happening. Is anyone looking into VS2015 build
I 100% agree that the default value in scons should be change to from SECURE=0
to SECURE=1 as a minimum.
When I saw the original email asking to have the secure flag changed on almost
every build that tells me the default should be change.
I will change the default value in the scons script I
I created A Jira ticket to change the default flag for SECURED from '0' to '1'
https://jira.iotivity.org/browse/IOT-1320
I have created the change and committed it:
https://gerrit.iotivity.org/gerrit/#/c/12085/
The Android and Arduino builds would not build when the SECURED=1 flag was
used. I
To: Nash, George
Cc: Dave Thaler ; Gregg Reynolds ; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] SECURE build flag setting as default configuration
On quarta-feira, 21 de setembro de 2016 15:02:15 PDT Nash, George wrote:
> 20:02:51 *** Er
AllJoyn decides to use security when the BusObject (AllJoyn?s equivalent to
IoTivity?s resource) is registered with the BusAttachment
BusAttachment.RegisterBusObject(myObj, securityFlag)
If the security flag is false no authentication is needed to access the object.
No ACLs are needed for the
If you already have the gtest-1.7.0.zip file downloaded and in the extlibs
folder it will not attempt to download it again. I have seen this error once
in a while also. I was able to sold it by making sure the boost_thread and
boost_system libraries were in the list of LIBS in the scons
I am seeing the same issue. From everything that I know about doxygen the
documentation should be produced for the functions as long as the @file
annotation is found in the file. Or, the EXTRACT_ALL tag is set to yes. The
files do have that annotation and the tag is set to yes. I don't know
IAR is one of the most successful commercial embedded development
environments. For this reason it would be great to add support for IAR to at
least iotivity-constrained. Unfortunately IAR is a commercial product which
means it unavailable to a large portion of the developers currently
Inline [geo]
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Gregg Reynolds
Sent: Thursday, April 6, 2017 12:47 PM
To: Daniel Mihai
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Public and Experimental Public C APIs
Christian,
I am not sure that I am the right person for the Build System. If I do become
the lead for Build Systems I will need to develop a lot more contacts. :) I am
well versed in the build system for most of the OSs but so far I have not been
the lead for any of that work.
Also what is
For the first error the fix is quite easy I have filed a Jira ticket for that
issue and will have a patch submitted shortly
https://jira.iotivity.org/browse/IOT-2029
I have not been able to reproduce the second issue.
I have seen this type of issue when old build products are causing an error.
Jihun Ha,
Give https://gerrit.iotivity.org/gerrit/#/c/18739/ a try it should fix both
your issues.
George
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Tuesday, April 11, 2017 1:23 PM
To: jihun.ha at samsung.com
I had replied much earlier to Mats original post but I sent to just Mats not
the dev list.
My response was:
Jenkins is building and running the test with both SECURED=1 and SECURED=0.
If you check the auto_build.py script which is used by Jenkins to build.
First scons -c is called
Then scons
Thiago,
I am not completely sure what error you are seeing.
Could you give us an example of what you are getting as well as what you are
expecting so we can track down the issue you are seeing.
If it is a new error introduced by
https://gerrit.iotivity.org/gerrit/#/c/19061/ we definitely want
I have been trying to get an understanding of IoTivity provisioning.
To test my understanding I decided to mess with the ACLs for the simpleserver
simpleclient samples. So I modified the oic_svr_db_server.json file with some
different values.
I deleted the already existing
I was seeing the same problem yesterday as well. I could not figure out the
source of the problem I ended up manually deleting and re-checking out multiple
folders to make sure any old build output was not messing up the build.
I ran the following (**be aware if you have uncommitted work in
Hwang, Yunhee (Eunice),
There currently is no support for arm 64bit builds. So far everyone has been
using the 32-bit build.
I looked on master it looks like there is an TARGET_ARC=arm64-v8a option. It
does indeed properly setup the scripts to use the aarch64 build tools.
There are some build
nt. Use
the path and name of your intended CBOR file as the second argument.
I would still really appreciate an example of a permissive ACL *.json file that
I could use.
George
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Na
Thanks Mats and Max,
I was really starting to wonder if I had missed something in the Android builds
with the recent work I have been doing.
George Nash
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Max Kholmyansky
Sent:
I think you have already started adding me to the reviews. Please keep adding
me.
Thanks for the work. The changes you have done are simple cleanup, that was
definitely needed.
George N.
-Original Message-
From: iotivity-dev-bounces at lists.iotivity.org
I encountered this issue when using IoTivity on Fedora Linux. For some reason
it takes about 3 times longer to initialize when calling OCInit than on Ubuntu.
I was never able to figure out why.
I work around the issue by increasing the time for the deadman timer.
Open up
Wouter,
I have been trying to improve the doxygen documentation.
https://gerrit.iotivity.org/gerrit/#/c/17569/ - Fixed documentation warnings
for cpp-docs
https://gerrit.iotivity.org/gerrit/#/c/17543/ - Fixed documentation warnings
for c-docs
Although those two commits cleaned up the warnings
When you built the code did you get an output similar to this?
* Info
* Either 'Android API 21' is not installed or 'Android SDK Build Tools *
* 20.0.0' is not installed. The Android SDK Manager will now open.
The generic java was merged with master early January.
Here is the wiki page:
https://wiki.iotivity.org/generic_java_binding
The Java Binding has also been part of the Jenkins build for a while.
Unfortunately they are non-voting builds. Meaning if they fail the build can
still pass
Very few of Java API Methods had Android specific code. There are a small
collection of files that did have android specific code. That split into a
different directory structure based. Depending on what the TARGET_OS is
specified the correct code is chosen.
For testing we are relying a lot
Mats,
I am glad that you have brought up some of these issues. I disagree that the
efficient doxygen comments page sounds mandatory. However, all of the
suggestions probably are best to be followed.
(a)Based on recent commits that I have made. There is definitely a strong
desire to use
files in ../../csdk/security/include/internal
Let me know if I should update the list of INPUT files for the Doxyfile.
George
From: ??? (Uze Choi) [mailto:uzc...@samsung.com]
Sent: Tuesday, March 21, 2017 8:29 PM
To: Nash, George ; 'C.J. Collier' ; 'Mats Wichmann'
Cc: 'IoTivity Developer List
rials"? If not I am sure I can come up with something.
-Original Message-
From: Mats Wichmann [mailto:m...@wichmann.us]
Sent: Wednesday, March 22, 2017 9:07 AM
To: Nash, George ; uzchoi at samsung.com; 'C.J.
Collier'
Cc: 'IoTivity Developer List'
Subject: Re: [dev] IoTivity documentation
Thanks Ashok,
I will update the Doxyfile with this information.
George
From: Ashok Babu Channa [mailto:ashok.cha...@samsung.com]
Sent: Thursday, March 23, 2017 4:23 AM
To: '??? (Uze Choi)' ; Nash, George ; 'C.J. Collier' ; 'Mats Wichmann'
Cc: 'IoTivity Developer List'
Subject: RE: [dev
Prathamesh,
SCons is not finding the cl command. It is not finding your copy of visual
studio. Do you have Visual Studio installed? It is a pre-request for building.
What scons command are you using to build?
Try using ?run build?
It is a *.bat file that calls scons with the correct options
Christian,
I took the time to work through all of the tickets that were in the filter. I
was able to close a few of the issues as fixed, will not fix, or cannot
reproduce.
If the 119 issues that still show up in the filter I saw 19 that maybe should
be looked at again.
There were a lot of
that they hold less
importance for the project.
George
From: Christian Gran [mailto:g...@lynxtechnology.com]
Sent: Friday, March 24, 2017 2:01 AM
To: Dave Thaler ; Nash, George ; iotivity-dev at lists.iotivity.org; Philippe Coval
Subject: Re: Jira cleanup
Hi,
thanks Dave and George
Prathamesh Ranade,
Scons is not finding the Visual Studio community version. I personally don?t
have the same setup so there are just things to try I don?t know if they will
work. They range in the order of what I think is the easy to hardest.
1) Check that you are using the latest
to solve your problem.
Sorry for the slow response I was at the OCF plugfest most of last week.
George
From: Thiago Moura [mailto:thiago...@gmail.com]
Sent: Monday, April 24, 2017 4:19 PM
To: Nash, George
Cc: iotivity-dev
Subject: Re: [dev] Java + Endpoint information
Hi George
It's
I missed some code in the commit. It?s passing the build now.
I also tested the code by adding it to the simpleclient sample (not committed).
Everything seems to be working as expected.
George
From: Thiago Moura [mailto:thiago...@gmail.com]
Sent: Tuesday, May 2, 2017 4:45 AM
To: Nash, George
Margaret,
I split the documentation into two sections API documentation and Wiki
documentation. I am prepared to be a mentor for API related documentation but I
am not prepared to do the same for wiki related changes.
If someone feels they would be willing to mentor with wiki related changes
...@wichmann.us]
Sent: Wednesday, May 3, 2017 12:54 PM
To: Nash, George ; LaBrecque, Margaret
; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] prelim list of areas where IoTivity needs new contributors
On 05/03/2017 01:17 PM, Nash, George wrote:
> Margaret,
>
> I split the documentation
I have been using scons for years and I have seen very few instances that using
'/' for path has caused issues.
Also you can get the root file for a path anytime using env.Dir("#"). This
returns a scons node if you need the string a string you can
Call str(env.Dir('#')).
In general I am happy
> Does it make sense to try to set things up so sconscripts are called only
> once? or is that wasted effort?
Scripts that build output or download external tools make since to only call
once. Calling these scripts multiple times may cause the build to be repeated
or multiple downloads. At a
Gregg I think it would be a great change to move to using site_scons. You even
made a draft change a long time ago.
https://gerrit.iotivity.org/gerrit/#/c/8597/
That change was trying to do multiple things in one commit so it was hard to
get maintainers to accept.
On that change I suggested
Jenkins unit test build has been failing intermittently (around 10%) with the
following failure.
[Valgrind] Ending the valgrind analysis.
Build step 'Publish Valgrind results' changed build result to FAILURE
This was caused by an invalid memory read/write failure.
A fix has been merged for
72 matches
Mail list logo
