review.tizen.org Git - platform/upstream/iotivity.git/log

Allow add MOM DOXM attribute

MOM DOXM attribute can be added via svrdbeditor

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/310
(cherry picked from commit 1ce338a37a447e42c23a86d64d9e96c6646a9217)

Change-Id: I02cc8714d6c2ac418cb2d99c77c3c0e2220ebbf3
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Install missed header files by the build time reducing

Change-Id: Ided34d8b62455f9d48b54f8362bda8497dec2654
Signed-off-by: Amit KS <amit.s12@samsung.com>

Edit Doxm MOM attribute

Added Edit mom functionality to svrdbeditor tool

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/307
(cherry picked from commit 86952a25462ae462e52af83368c153c00b4e8374)

Change-Id: Ieff8984afb72bdbad80281ed44967bfa8ac55440
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-07-18)

Change-Id: Ic28205c52f6ffb421856a41dce21f5773651682c
Signed-off-by: Amit KS <amit.s12@samsung.com>

SQLite OS specific support (#304)

Change SQL requests for WHERE statements with blob params.
(Details in [IOT-2775])

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/304
(cherry picked from commit 988f01a5cc090ef21dfde89352ceb47dd7be70bc)

Change-Id: If87ae5503fb2961601376bfd405c7949c1a5c28a
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-07-04)

Change-Id: Id715c564d0c8404dca74f69fbad277ea7d7357fd
Signed-off-by: Amit KS <amit.s12@samsung.com>

[CONPRO-1272] Disable the Multicast Action in Mobile Network Case.

Starting multicast server on all identified interfaces results in resource loss as many of identified interfaces may not have Multicast capability. It make sense to start multicast server on only active wifi connected interface for android platform.

This patch handles -
1. Create UDP sockets(Unicast and Multicast) and join multicast group only when there on active WiFi connection.
2. Whenever the WiFi connection comes up, UDP sockets will be closed, created, and joined to multicast group.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/296
(cherry picked from commit ce73d5846ecb99fb04e87860b94afbaeff0ddcb4)

Change-Id: Ib3586d77d3c0e96c990e3fb5a398e78b29a20be8
Signed-off-by: Amit KS <amit.s12@samsung.com>

RPK: add length check

RPK master key length check and logging added

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/303
(cherry picked from commit c8d7cb113be986ad53aa1b498280530277597187)

Change-Id: Ia9d5a974476fee3d9fc64a2267c3b8db8ff3f7b4
Signed-off-by: Oleksii Beketov <ol.beketov@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

[CONPRO-1300] Crash in CAdeinitSslAdapter

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/299
(cherry picked from commit eb86d2e103dc826d90bbb364f45616e903d6d312)

Change-Id: I2db227c9d418b68a423e742fca3cd74e8d8c8105
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-06-27)

Change-Id: Ifb00f0b5683c938b94c710836900d0ed6ab6cfcc
Signed-off-by: Amit KS <amit.s12@samsung.com>

Memory leak for equal cred contents

Fix the issue in AddCredential api

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/300
(cherry picked from commit 0538b11eb0600edbf18bc43af4c3493369f99e09)

Change-Id: I0211724897f604ba88dcfb33147cb219a502ef65
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

RPK OTM (#295)

Raw public key OTM added from client side

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/295
(cherry picked from commit bc07c41689f3f835cb14b9e8ad70c2298fa6c839)

Change-Id: Iafeb8d467c821eca3ad350eced73f57637349a71
Signed-off-by: Oleksii Beketov <ol.beketov@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Crash in OCProcessPresence (#298)

* [CONPRO-1285]Crash in OCProcessPresence

There is a issue after freeing the clientcb
we are again accessing it.It can possibly crash.

So, to avoid this scenario we are using LL_FOREACH_SAFE
to iterate the list

Signed-off-by: agrkush <kush.agrawal@samsung.com>
* Update ocstack.c

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/298
(cherry picked from commit 578c6918d40d5bded028266ceb3a4aaf68d33623)

Change-Id: Id514a242e34d7a20df2845c09a757b3d26c9604a
Signed-off-by: Amit KS <amit.s12@samsung.com>

Install missed header files by the build time reducing patchset

Change-Id: I4b184eaf5d61a7cdb8c0893f45973709854be3a2
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>

Applying remove re-build command patchset in the public spec file

In the build section, scons build is done. So we can use the result
on the install section without rebuild using scons.

Change-Id: I70a72fff2f8ea6c2309d5eba438e142f8fbab587
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-06-13)

Change-Id: Icd6f0c7e1f2c7295b125b86739533e18e131ed5b
Signed-off-by: Amit KS <amit.s12@samsung.com>

Remove re-build command in the install section

In the build section, scons build is done. So we can use the result
on the install section without rebuild using scons.

Change-Id: I33d47209d0898d703dcedba6bfd00a91d959c9b6
Signed-off-by: Amit KS <amit.s12@samsung.com>

Crash in CATerminate

The variable caglobals.tcp.terminate is used to signal the
receiver thread to stop. However using a volatile variable
to synchronize between threads is undefined behaviour as
per the C/C++ standards. In this particular case due to
cache coherence behaviour on SMP mobile(especially ARM)
multi core processors, the receiver thread is not guaranteed
to see the change to the terminate variable as soon as
adapter is terminated and this delay could cause an ANR.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/290
(cherry picked from commit 38101be161271b68cee847748d71fb4ded73bc5a)

Change-Id: I10cc6b0e540c4f3e68b6019f8ca8a6ebfc43b1b0
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Add missing stack errors to android code

Add missing OCStackResult enum values to errorcode.java file
and JniUtils.h.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/291
(cherry picked from commit e2545fc58de379f686ac60c43cffb1d032620c77)

Change-Id: Iebba2b63ed1805f1c1bed09aaa1e4f3792ea220a
Signed-off-by: harish_kumar <harish.191@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Fix build error dlog string

Patch was tested

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/289
(cherry picked from commit b1c8909fa7626bb06f8579aca6a3fb7cdb3ccef4)

Change-Id: I53374ee8c2ce97b51d76f85cb65aabdfb8c950bf
Signed-off-by: v.riznyk <v.riznyk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-05-02)

Change-Id: I7d952ce967acdcd9fe305e5c00d48b1311982c30
Signed-off-by: Amit KS <amit.s12@samsung.com>

Clearing pending exceptions in JNI env

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/287
(cherry picked from commit 312f0a735dea35925da0d80a916d0d9cf542932e)

Change-Id: I2830f50706a5818375745a406d3ff4b7f8ecdb1c
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-04-25)

Change-Id: I1b9d298f47b7be8efadb90d1c327467fc7b5e5fe
Signed-off-by: Amit KS <amit.s12@samsung.com>

Added Samsung Specific Property(sso list) for easy setup

Following Samsung Specific Property is added :
Resource: Device Configuration (rt = "oic.r.devconf")
Property Name: SSO List Information
Key: "x.com.samsung.ssolist"
Type: String (JSON value with array of string internally).
Access Mode: Read Only
Description: SSO List information

Changes made at Mediator and Enrollee Side (Samsung specific source).

Linux Sample apps updated and verified (Samsung Specific Sample Apps).

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/284
(cherry picked from commit 26aec98b390c57957416dff8c3e9a920299aad8a)

Change-Id: Ib5143bb96488820b01404c2ec68dcf04c9f6a02c
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Disable TCP server role

TCP server is used only in client role to connect to
cloud server. A critical vulnerability is reported when
ifw-thing process in TV connects to other device via
TCP(D2D) which can compromise the Policy engine. Therefore
disable TCP server role based on build configuration.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/286
(cherry picked from commit fbd41449a05001403bcf60169a3c780d97001e7a)

Change-Id: I2434f29644e74260b5dc032e5001ce5a60058f89
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>

Merge "Update Snapshot(2018-04-18)" into tizen_4.0_tv

Merge "Creating socket everytime when network bearer changes (#285)" into tizen_4.0_tv

Merge "Replace tizen BLE internal APIs with public" into tizen_4.0_tv

Update Snapshot(2018-04-18)

Change-Id: Id834fe66fe00466bc78ea4624b471201008f7b70
Signed-off-by: Amit KS <amit.s12@samsung.com>

Creating socket everytime when network bearer changes (#285)

[CONPRO-1269] Creating socket everytime when network bearer changes

Socket was created only once but changed the logic for creating on every network change
When we are switching WifiAP or disconnect/connect again then we are not able to send unicast data from android side . It gives network unreachable error. So to avoid that we are closing and creating sockets again.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/285
(cherry picked from commit 285875048bda46b6ac1a742c25849d70234d7cd1)

Change-Id: I6829f8e83d64905fd97de0340da0e4c1abf37972
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Replace tizen BLE internal APIs with public

Tizen 4.0 build fails in case BLE internal API's are used,
therefore replace them with public API's. All changes are
made under the preprocess define TIZEN_4

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/282
(cherry picked from commit d66f237dc92c15a515332d0416f769d8e856bfe9)

Change-Id: I451a6519edfaa792862819d59693500ff46b50ce
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Fix Asan build errors (#281)

Remove duplicate variables
multiple definition of `g_ESEasySetupResource'
multiple definition of `g_ESDevConfResource'
multiple definition of `g_ESCoapCloudConfResource'
multiple definition of `g_ESWiFiConfResource'

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/281
(cherry picked from commit 0cbbcfa65ff14d751dd1193f75b7c20269e26991)

Change-Id: I91fdf2dee60c86fa24e98a622456722eca20d526
Signed-off-by: Oleg Ogurtsov <o.ogurtsov@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>

[CONPRO-1269] Creating socket everytime when network bearer changes

Socket was created only once but changed the logic for creating on every network change

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/280
(cherry picked from commit eaa97ac11871f5536ca12e7ab2f9c848b4d99afd)

Change-Id: I991d1d91c352f52baf7379b693ff2df2aaf9ee61
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-04-12)

Change-Id: I0c59fd76abaff03921c5ebc8cab75344087c998d
Signed-off-by: Amit KS <amit.s12@samsung.com>

Crash in OCProcessPresence()

1. Set presence to NULL incase allocation of timeout
array fails. This ensures that OCProcessPresence does
not process this cbNode, thereby preventing possible
NULL dereference of timeout.
2. Do not send request if timeout has reached/exceeded
the PresenceTimeOutSize. This prevents a possible buffer
overrun in accessing the timeout array.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/279
(cherry picked from commit 22079af2bd0f22a80b98c3b17469c3b8ed601ede)

Change-Id: I6a16c6675236518c008a88c590264dedea698a3a
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-04-05)

Change-Id: Iff9df44b5097021dcecaa93ff6ec3fdd3d0a3cfe
Signed-off-by: Amit KS <amit.s12@samsung.com>

Unset gatt callback in network monitor

Gatt connection state changed callback is set in the
network monitor (calenwmonitor.c) but is unset in the
gatt client (caleclient.c). Move this to network
monitor instead

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/278
(cherry picked from commit 961ff08710e7acd99277a335f7d9eeca2f68c16e)

Change-Id: I9ee9da268d63fe0d379e4596c901552b10ceb0f1
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

"have choice" error of libmbedtls.so

delete +%{_libdir}/libmbedtls.so from iotivity-devel

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/277
(cherry picked from commit 3cd231da7e03a322dd10fbfee0b15582647c191e)

Change-Id: I0833cd20927f4a3b5a62eb3c7835b78d89c2235a
Signed-off-by: Oleksiy Volkov <a.volkov@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>

Update Snapshot(2018-03-28)

Change-Id: If8b1d9096a336ab4cbdbbc996bf2b6a396adbecf
Signed-off-by: Amit KS <amit.s12@samsung.com>

Synchronized observe notification using mutex.

As InProcClientWrapper class creates separate thread for every
obseve callback, There is a chance that more than one thread enter
ObserveCache object and trying to modify m_attributes. More over
same m_attributes is being passed out or RE layer by const reference,
so application is using same member object m_attributes. Mutex allows
only one thread to modify m_attributes.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/276
(cherry picked from commit c87d0d4b14d22349c3563e7cd316d323d068e2ab)

Change-Id: I54c80a6ea9751b8d9f78720121bee949d336ce4f
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

[CONPRO-1212] Removing invocation of lock_guard destructor.

std::lock_guard follows RAII for std::mutex. Invoking
std::lock_guard<std::mutex>::~lock_guard() makes unlock
call twice on underlying mutex. As per the API documentation
calling unlock from thread which does not own lock results in
undefined behaviour.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/243
(cherry picked from commit fc681e089d3bbbbd16f90ad05d53208f9a1602d1)

Change-Id: Iaf21d318f5fa46daf2bcc17f0f07ffe9aa887b9d
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>

Update Snapshot(2018-03-21)

Change-Id: Ia9b1148b62386f521c769a97e1d873cd34a04d0a
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>

[CONPRO-1251]Updated typo error

Changed interface declaration in ocobserve.h

Change-Id: I47a49d2371cf098084ac23b53ad48d32a0119ab4
Signed-off-by: Kush <kush.agrawal@samsung.com>

Update Snapshot(2018-03-07)

Change-Id: Icc2692241f81dd8d7aa06ba779e2270d1c6ab750
Signed-off-by: Amit <amit.s12@samsung.com>

Update Snapshot(2018-02-28)

Change-Id: Ie839b5c1dee0a1a559d04b20a40f549b48e8da6f
Signed-off-by: Amit <amit.s12@samsung.com>

Update snapshot(2018-02-21)

Change-Id: Iacc9ec43b82dce33ed378010a9eb19bd24fdd0ac
Signed-off-by: Amit <amit.s12@samsung.com>

Update snapshot(2018-02-14)

Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Change-Id: Ib7a9cb7e25ead6027b56011a9d8c3cc42c3fdb6d

Update snapshot(2018-02-07)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: If60dc7547c9e14e80d7fbdccc4a86be0ef7d082b

Update snapshot(2018-01-31)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I2a12ea6904874b5158458d4882688709a0158575

Update snapshot(2018-01-24)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ib5c6f3801761bdf022ebf8a56291e104cc5e6e4d

Update snapshot(2018-01-17)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I0d71eee704b1b6e88d483b6c2771e5cce6750886

Update snapshot(2018-01-10)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I8e376f3660a9b36ae8ffcba30ca591293be6f913

[CONPRO-1181] Continue De-Initialize BLE even some BLE-API fails as per fw guidelines

- manually patched from below pull request because of VD PVR schedule

- [UPDATE] https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/226

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I88e508f7a1f2ce449e397cace30ea10128522d7d

[CONPRO-1181] Continue De-Initialize BLE even some BLE-API fails as per fw guidelines

- manually patched from below pull request because of VD PVR schedule

- https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/226

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Iab0a3e521043b5716495a332cf38b061acc9cd90

Update snapshot(2018-01-04)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I4f4ee78d3bd2474fcbabc5a2abd41b9ea10b55d2

[CONPRO-1176] iotivity crash during CAReceiveMessage

- manually patched from below pull request because of VD PVR schedule

- https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/215
Signed-off-by: kmook <kmook.choi@samsung.com>
Change-Id: I58811d5a50211aeaddf06c5cdab751a5ca31b8eb

[CONPRO-1172] allocates too much memory

- rollback a patch to solve segmentation fault issue

- https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/206(rollback)

Change-Id: Ie822028ec2469e87d96bbf72a25b0019fb5e8b65
Signed-off-by: kmook <kmook.choi@samsung.com>

[CONPRO-1172] allocates too much memory

- manually patched from below 2 pull requests because of VD PVR schedule
- https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/206
- https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/209

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I71e81ee3c74c0a31623e5713352a44afd123a846

Update snapshot(2017-12-20)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I04303750581f9349f4694ba903c8e2f6379c91d4

Update snapshot(2017-12-14)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Iec053ef8f5cc87812aec9c884b1e811f85682de7

Update snapshot(2017-12-06)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Idef59156a36f5d2e636a7487f140f8c236f5bf8d

Update snapshot(2017-11-29)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ife7d3cee9f401c54bcc48923e330fda7f78f064e

Update snapshot(2017-11-23)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I1f1159259819400edca8bc384bbc8c883168abbf

Update snapshot(2017-11-14)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ic39e3e0fcc79a7cf38d00721cfe9fcfafce0b3c6

Update snapshot(2017-11-08)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Icbbce23a651f542fe2bf3c98ba4eb3d6bb96274a

Update snapshot(2017-11-02)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ie9cb19fca33409447339e50e9c5f07e6f11aaf1a

Update snapshot(2017-10-25)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ib6b6b8772dd1e136c49393b0dafb8f721d6a42fc

Update snapshot(2017-10-11)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I0682f26c3c6d0989210a8b7ddfac1485cc10671b

Update snapshot(2017-10-04)

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: If984cf1623bb9bd5dbb4d68920404e0513828f86

replace : iotivity -> iotivity-sec

Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I2832a4cf81d6a312442a5548fa4baa7a8959d7cc

Remove unused pkg dependancy

Change-Id: I310c2e37d0a94c3c9cf3191b8162abc873ceb316

delete wifi API and pkg config in tizen.

since IoTivity already use Tizen Connectivity Manager API instead of wifi API.
it should be removed in this and there.

Change-Id: I9a61d7d4d323fe83e988c792284179c099bc2855
Signed-off-by: jihwan.seo <jihwan.seo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17079
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Conflicts:
resource/csdk/connectivity/build/tizen/scons/SConscript
resource/csdk/stack/samples/tizen/build/scons/SConscript

Change-Id: I401a44313a3a48fd7bfc5ca9c8519ec1186a8083

[IOT-1643] Fix illegal memory access - Don't return local string

the std::string ret is a local varaible and is destroyed when the
what() member function returns.

Put the return string into the m_whatMessage variable. Since
'what()' member function is a const function it can not modify the
member variable m_whatMessage so it is generated in the
ResourceInitException constructor.

Issue found using static analysis tool.

Change-Id: I907b984f35dee59b2f300afe6a640b15a26f020f
Signed-off-by: George Nash <george.nash@intel.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15035
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Larry Sachs <larry.j.sachs@intel.com>
Reviewed-by: Habib Virji <habib.virji@samsung.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>

Update spec file (in tools)

Change-Id: I3840a6b3b10070df30e66ca0de8852d0ea76264e

Update License

Change-Id: I47861f7f52f61ef1f5dbda201564f058560d3688

IOT-1877 : start presence issue

When called OCStartPresence() second, OCStartPresence() returns error.
Fixed presenceState variable to OC_PRESENCE_UNINITIALIZED.

Change-Id: I089c826f4105eb3aaf835a8feda4c10b848ebd5d
Signed-off-by: ChaJiWon <jw_wonny.cha@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17623
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Way Vadhanasin <wayvad@microsoft.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
(cherry picked from commit 2f11e9592a7374ce28082a523b0c367a6d31baee)
Reviewed-on: https://gerrit.iotivity.org/gerrit/17775

Moved a requestId declaration in OCServerRequest

we should not add attributes after payload as they get overwritten
when payload content gets copied over.

Change-Id: I0c8a430f92c2196d3f9c816e9ba9d16fd44d88e4
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17015
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>

Fixed memory leak on OCSetDeviceInfo and CARetransmissionDestroy

Change-Id: Ic53ae0759020fa26f5f70425d3dab09ff5e7d375
Signed-off-by: Jaewook Jung <jw0213.jung@samsung.com>
Signed-off-by: jihwan.seo <jihwan.seo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17167
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jaehyun Cho <jaehyun3.cho@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>

fix the easy-setup mediator SConscript

Change-Id: If484c27c7336608326af35f3e0aebeac4e4a580a

Fixed double free issue when destroying endpoint

- after destroying memory, set NULL value to prevent double free
- add the usage of oc_mutex_lock() when block data is updated

Change-Id: I78d0d46e37333e099ec737ac4500a2f388d58c4e
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15447
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>

tizen: Enable CLOUD and ship ES lib (downstream)

Sync with upstream's spec

Change-Id: I84ce3dd94e1a90f13f0ff875221ca50600000001
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/I84ce3dd94e1a90f13f0ff875221ca5061828618e
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>

tizen: Enable CLOUD and ship ES lib

Change-Id: I84ce3dd94e1a90f13f0ff875221ca5061828618e
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/I84ce3dd94e1a90f13f0ff875221ca5061828618e
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16965
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

tizen: Use mediator richsdk lib

Change-Id: Ib63db28697925b02349da82c5feabc1334a39ba2
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/Ib63db28697925b02349da82c5feabc1334a39ba2
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16963
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Tested-by: Uze Choi <uzchoi@samsung.com>

[4.0] Unification: Remove Profile Build Dependency & Prepare 4.0 Build

This is for Tizen 4.0.
- Removed profile build dependency.
- Prepare for Tizen 4.0 build.

a. Remove profile build dependency
- This commit completely removes the build dependencies on Tizen profile.

b. Prepare for Tizen 4.0 build
- We have assumed that Tizen 4.0 code is going to be more similar with 3.0
   than 2.0. Please do not rely on string '==' compare for version check.
   And, refer to the official macros that are defined in Project Config.
   https://build.tizen.org/project/prjconf?project=<project_name>

@To maintainer:
Please, keep a spec file syntax that was written at an official webpage.
https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/\
RPM_Guide/ch-specfile-syntax.html
First, if you want to use a comparison operator in %if, don't use
a double-quotes. Second, RPM macro does not support a floating-point
number for the comparison operator.

Change-Id: I8904a25e5e24f6e1bdbd460e434ad563695a3001
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>

tizen: Use easy-setup mediator

Change-Id: I2b0681b70218613c0df0d82e0f46fdc61668296e
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>

build: Install provisioning ESException.h

Add ESException.h to 'inc' folder and a list of install target headers

Change-Id: Ib0b7e7bbab9cf5d8f7cc0c69e223d966e4b055b0
Signed-off-by: Jihun Ha <jihun.ha@samsung.com>
Origin: https://gerrit.iotivity.org/gerrit/#/c/16521/
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>

easy-setup: Rename header to EasySetup.hpp

Prevent potential name clash on case insensitive filesystems:

./service/easy-setup/mediator/richsdk/inc/EasySetup.h
./service/easy-setup/enrollee/inc/easysetup.h

Mediator one is C++ so we rename it to .hpp

Change-Id: I6d784378b5065b162d06abb2338bf70e0147d864
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16479
Reviewed-by: George Nash <george.nash@intel.com>
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>
(cherry picked from commit 98b92dae54a9244e1947937fcf7432ac38956659)
Origin: https://gerrit.iotivity.org/gerrit/#/c/16481/
pp

build: Ship provisionning headers

New headers should be installed if part of public API:

- OCProvisionningManager.hpp
- OCCloudProvisioning.hpp

Change-Id: I29a322f2dae9b0d978cdd05d4ca3ad71729d1923
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Origin: https://gerrit.iotivity.org/gerrit/#/c/16531/

fix the build error when appcliation build resource encapsulation

- add the missing header file in installed target header

Change-Id: I71b65d6df422bd758e543118c2580ac770213399
Signed-off-by: JooseokPark <jooseok.park@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16461
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Tested-by: Uze Choi <uzchoi@samsung.com>

revise the spec file for ES

- tizen: avoid to duplicate headers
- Rely on pkg-config instead.

Change-Id: I5944d59bb08d8aeeda617f0af5ba95ae9e76e9cc

tizen: avoid to duplicate headers

Rely on pkg-config instead.

Change-Id: Ieff754b33a21015a17fc9a8d107ee29f1376dfa1
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16449
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

build: Add ES NS paths to pkg-config

Public easy-setup and notification headers,
are copied in 2 level depths directory.

Change-Id: I7c9fd3a4bd1143c5ea05e7902292af23cf5e8934
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16447
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

build: Install easy-setup headers

It look like project public headers
are installed to 2 level depth
subdirectories (service/$domain/*.h*)

Change-Id: Ia7a66caf5381d24b56f0c5ac1a91929eff9ba7d7
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16445
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

build: Install notification headers

It look like project public headers
are installed to 2 level depth
subdirectories (service/$domain/*.h*)

Change-Id: I36ab613ff6aaf7d960e6ba1e94263f8cfdf7c559
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16443
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

Fix the notification service SConscript

- when application use the notification service, build error occurs.
- i.e) /usr/include/service/notification/NSConsumerInterface.h:35:22: fatal error: NSCommon.h: No such file or directory
- Although NSConsumerInterface.h includes NSCommon.h, NSCommon.h file is not installed in SConscript.
- So, need to add NSCommon.h in installed header

Change-Id: I2f28f84504d68c5506c89513d74adcdf32d2bbfc
Signed-off-by: JooseokPark <jooseok.park@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16427
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>
(cherry picked from commit e4eca38246a40013530b7df74c1b369960c88897)
Reviewed-on: https://gerrit.iotivity.org/gerrit/16459
Tested-by: Uze Choi <uzchoi@samsung.com>

merge tizen_3.0 to tizen branch

Change-Id: Ib7f30f0231385d4f6c2d2cee8ff430ad6ed6b6ac

tizen: Replace speedpython by python-accel

Tizen toolchain provide same functionality with python-accel's macro

Also Chan Lee from Tizen toolchain project reported:
{
Speedpython macro sometimes cause some build problem

Speedpython macro is parsed when spec parsing time
and it includes other macro in its own.
(I mean, %{build_hostarch} macro)

And when the OBS project config updates,
OBS sometimes cannot sync-up the changes perfectly.

It this case, build error occurs when we use speedpython macro.

It seems OBS limitation but,
we can avoid this problem by using other macro
which provides same functionality.
}

Change-Id: I265220b5e1f2dcb1956ef546a799a94eb460dd88
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>

[Tizen]change flag which used for detect ip changed
change netlink interface flags to addr flags
which used for detect network IPv4/6 changed

Change-Id: I827db082879aafdc3e8bd688917180af09531ab2
Signed-off-by: bg.chun <bg.chun@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15595
Reviewed-by: Hyuna Jo <hyuna0213.jo@samsung.com>
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>

[IOT-1671] Fixed base layer terminate logic

- ObserverList should be removed before destroying ResourceList
to avoid the error of dangling pointer. because ResourceObserver
object includes a resource handle which is memory address allocated
when resource is created.
- Add function to unset network monitoring callback when OCStop()
is called.

bug: https://jira.iotivity.org/browse/IOT-1671
Change-Id: I8a367a24a2100c97bf612db26bc41db5f47f2feb
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15499
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>