Hi Trevor, Sooner, I?ll request this change into Jenkins Job setting. Additionally, let me explain the android build fragmentation. All like not so useful for various options. What is the rm option? we need to pick up single profile from each architecture below.
https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-ble/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-bt/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-ip/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-rm_and_ble/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-rm_and_bt/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi-rm_and_ip/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-ble/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-bt/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-ip/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-rm_and_ble/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-rm_and_bt/5/ : SUCCESS https://build.iotivity.org/ci/job/iotivity-verify-android_x86-rm_and_ip/5/ : SUCCESS BR, Uze Choi From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Monday, September 19, 2016 9:32 PM To: iotivity-dev at lists.iotivity.org Subject: SECURE build flag setting as default configuration Hi All, Currently SECURED = 0/1 is used for IoTivity compile option. But even if SECURED = 1, we can configure the resource creation with secure or non-secure. related API is OCPlatform.registerResource(?? uint8_t OC_SECURE) or OCCreateResource(?. uint8_t OC_SECURE). So that Jenkins build configuration need to be modified as follows (Arduino, Ubuntu will keep to have SECURED=0 flag build) linux_secured ? no changed linux_unsecured ? no changed linux_arduino ? no changed linux_unsecured_with_tcp (SECURED = 0 ) ? linux_secured_with_tcp (SECURED = 1) android (SECURED = 0) ? android (SECURED = 1) tizen (SECURED = 0) ? android (SECURED = 1) windows-vs2013 (SECURED = 0) ? windows-vs2013 (SECURED = 1) windows-vs2015 (SECURED = 0) ? windows-vs2015 (SECURED = 1) unit_test (SECURED = 0) ? unit_test (SECURED = 1) simulator (SECURED = 0, WITH_TCP=0) ? simulator (SECURED = 1, WITH_TCP=1) I checked the Sample code in the base Layer , in case of build (Secure = true), non-secure resource will be created by default and secure resource can be created by modifying some line of code. For the service layer code, following are required. - Easy Setup (already has the secure resource setting, ESInitEnrollee (true/false, ?) - Scene Manager (Not yet, need SceneList.initializeSecureResource( )) - Resource Encapsulation (already has the secure resource setting, Builder.setSecureFlag(true/false) - Resource Container (not yet, need xml configuration for this) - Notification Service (already has the secure resource setting, NSProviderConfig.resourceSecurity = true/false, C++/Android are required to have it) - resource directory (implementing now, OCRDStart() ? CHPInitialize(bool secure)) - coap-http proxy (implementing now, CHPInitialize() ? CHPInitialize(bool secure) - Simulator (not yet, need UI setting) - resource hosting (not yet, code is not maintained) Please give any feedback if you have prior to this change. BR, Uze Choi (Release Function Lead) -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160919/948bdb08/attachment.html>
