[dev] Android build fails in 1.3-rel branch

2017-04-12 Thread Nash, George 
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; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Android build fails in 1.3-rel branch

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.
Here are two things to try.
1st
Do a clean build
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 -c
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1

If that does not work manually clean the build output and try again sometimes 
the scons clean misses something that should have been cleaned and this solves 
the problem. If you have another build linux or tizen this will wipe out the 
build output for those OS if you may want to be more selective than this. 
Sometimes just deleting the .sconsign.dblite file will fix the issue but I 
normally just rebuild everything.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 ?c
$> rm -fr out #delete the output directory
$> rm .sconsign.dblite #delete scons?s database file that it uses for tracking 
which files need a rebuild.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1



From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf 
Of ???
Sent: Tuesday, April 11, 2017 4:46 AM
To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at 
lists.iotivity.org>
Subject: Re: [dev] Android build fails in 1.3-rel branch


Hi All.



Below problem can be resolved by https://gerrit.iotivity.org/gerrit/#/c/18701/ 
patch.

However, I've encountered other problem as below:



jhha85:~/workspace/iotivity$<mailto:hha85 at 
jhha85-Linux-System:~/workspace/iotivity$> scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch
linux2
Creating ANDROID_HOME for Android SDK
ANDROID_HOME = 
/home/jhha85/workspace/iotivity/extlibs/android/sdk/android-sdk-linux

*** Info **
*Android NDK path isn't set, the default will be used. You can set*
* environment variable ANDROID_NDK or add it in command line as:  *
*  # scons ANDROID_NDK= ...  *
***

*** Info **
*Android Gradle path isn't set, the default will be used. You can set *
* environment variable ANDROID_GRADLE or add it in command line as:   *
*  # scons ANDROID_GRADLE= ...*
***

Copied IoTivity version of config.h to 
/home/jhha85/workspace/iotivity/extlibs/mbedtls/mbedtls/include/mbedtls/config.h
Checking for POSIX Thread Support...yes
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch

scons: *** Two environments with different actions were specified for the same 
target: libcjson_cJSON.o
File "/home/jhha85/workspace/iotivity/extlibs/cjson/SConscript", line 31, in 


Anyone who can resolve the problem?



Thank you.



Best Regards,



Jihun Ha (???/???, Ph.D.)

IoT, IoTivity, OIC | IoT Lab

Software R Center | Samsung Electronics Co., Ltd

Mobile +82 10 2533 7947

jihun.ha at samsung.com | jhha85 at gmail.com





- Original Message -

Sender : ??? mailto:jihun.ha at samsung.com>> Senior 
Engineer/IoT Lab(S/W??)/????

Date : 2017-04-11 16:14 (GMT+9)

Title : [dev] Android build fails in 1.3-rel branch



Hi. All.



I'm trying to build iotivity for Android platform but encountering a failure as 
below:

jhha85:~/workspace/iotivity$<mailto:jhha85 at 
jhha85-Linux-System:~/workspace/iotivity$> scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
AttributeError: 'SConsEnvironment' object has no attribute 'Download':
  File "/home/jhha85/workspace/iotivity/SConstruct", line 28:
SConscript('build_common/SConscript')
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 614:
return method(*args, **kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 551:

[dev] Android build fails in 1.3-rel branch

2017-04-11 Thread Nash, George 
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.
Here are two things to try.
1st
Do a clean build
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 -c
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1

If that does not work manually clean the build output and try again sometimes 
the scons clean misses something that should have been cleaned and this solves 
the problem. If you have another build linux or tizen this will wipe out the 
build output for those OS if you may want to be more selective than this. 
Sometimes just deleting the .sconsign.dblite file will fix the issue but I 
normally just rebuild everything.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 ?c
$> rm -fr out #delete the output directory
$> rm .sconsign.dblite #delete scons?s database file that it uses for tracking 
which files need a rebuild.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1


From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ???
Sent: Tuesday, April 11, 2017 4:46 AM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Android build fails in 1.3-rel branch


Hi All.



Below problem can be resolved by https://gerrit.iotivity.org/gerrit/#/c/18701/ 
patch.

However, I've encountered other problem as below:



jhha85:~/workspace/iotivity$<mailto:hha85 at 
jhha85-Linux-System:~/workspace/iotivity$> scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch
linux2
Creating ANDROID_HOME for Android SDK
ANDROID_HOME = 
/home/jhha85/workspace/iotivity/extlibs/android/sdk/android-sdk-linux

*** Info **
*Android NDK path isn't set, the default will be used. You can set*
* environment variable ANDROID_NDK or add it in command line as:  *
*  # scons ANDROID_NDK= ...  *
***

*** Info **
*Android Gradle path isn't set, the default will be used. You can set *
* environment variable ANDROID_GRADLE or add it in command line as:   *
*  # scons ANDROID_GRADLE= ...*
***

Copied IoTivity version of config.h to 
/home/jhha85/workspace/iotivity/extlibs/mbedtls/mbedtls/include/mbedtls/config.h
Checking for POSIX Thread Support...yes
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch

scons: *** Two environments with different actions were specified for the same 
target: libcjson_cJSON.o
File "/home/jhha85/workspace/iotivity/extlibs/cjson/SConscript", line 31, in 


Anyone who can resolve the problem?



Thank you.



Best Regards,



Jihun Ha (???/???, Ph.D.)

IoT, IoTivity, OIC | IoT Lab

Software R Center | Samsung Electronics Co., Ltd

Mobile +82 10 2533 7947

jihun.ha at samsung.com | jhha85 at gmail.com





- Original Message -

Sender : ???  Senior Engineer/IoT Lab(S/W??)/

Date : 2017-04-11 16:14 (GMT+9)

Title : [dev] Android build fails in 1.3-rel branch



Hi. All.



I'm trying to build iotivity for Android platform but encountering a failure as 
below:

jhha85:~/workspace/iotivity$<mailto:jhha85 at 
jhha85-Linux-System:~/workspace/iotivity$> scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
AttributeError: 'SConsEnvironment' object has no attribute 'Download':
  File "/home/jhha85/workspace/iotivity/SConstruct", line 28:
SConscript('build_common/SConscript')
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 614:
return method(*args, **kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 551:
return _SConscript(self.fs, *files, **subst_kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 260:
exec _file_ in call_stack[-1].globals
  File "/home/jhha85/workspace/iotivity/build_common/SConscript", line 592:
env.SConscript(target_os + '/SConscript')
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 551:
return _SConscript(self.fs, *files, **subst_kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 260:
exec _file_ in call_stack[-1].globals
  F

[dev] Android build fails in 1.3-rel branch

2017-04-11 Thread Mats Wichmann 
On 04/11/2017 02:23 PM, Nash, George wrote:
> 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.
> Here are two things to try.
> 1st
> Do a clean build
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 -c
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1
> 
> If that does not work manually clean the build output and try again sometimes 
> the scons clean misses something that should have been cleaned and this 
> solves the problem. If you have another build linux or tizen this will wipe 
> out the build output for those OS if you may want to be more selective than 
> this. Sometimes just deleting the .sconsign.dblite file will fix the issue 
> but I normally just rebuild everything.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 ?c
> $> rm -fr out #delete the output directory
> $> rm .sconsign.dblite #delete scons?s database file that it uses for 
> tracking which files need a rebuild.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1


I should note the clean targets are relatively broken: scons isn't told
about everything that is built, because some of the things happen
outside defined scons "targets".  So not the fault of scons. Not sure if
that's enough to actually affect a subsequent build, that would take
research I haven't done, but manual cleaning may be a good idea. Recent
not-directly-related but possibly interesting example: I found out a
useful #define from iotivity_config.h was missing, because
iotivity_config.h in resource/c_common is not recreated if it exists,
and nothing ever removes it (it's not a "target", just the effect of
some statements in a file); my copy was six months old and another four
or so checks had been added since).

[dev] Android build fails in 1.3-rel branch

2017-04-11 Thread 하지훈 
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL:

[dev] Android build fails in 1.3-rel branch

2017-04-11 Thread 하지훈 
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: