1. 09 Mar, 2018 1 commit
  2. 02 Mar, 2018 1 commit
  3. 14 Feb, 2018 1 commit
  4. 12 Feb, 2018 1 commit
  5. 09 Feb, 2018 2 commits
  6. 08 Feb, 2018 1 commit
  7. 07 Feb, 2018 1 commit
    • Mats Wichmann's avatar
      Drop use of two deprecated defines · 0636dca4
      Mats Wichmann authored
      Per the header ocstackconfig.h, two defines are
      deprecated with replacement. Change the single file
      which still uses the old names.  The header comment:
       * Maximum length of the Manufacturer name supported by the server
       * for manufacturer name.
       * @deprecated use MAX_PLATFORM_NAME_LENGTH instead.
       * Maximum length of the URL to the Manufacturer details supported by
       * the server.
       * @deprecated use MAX_PLATFORM_URL_LENGTH instead.
      Change-Id: I40ae198120de175750447996ebd43bed9ec25fa8
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
  8. 06 Feb, 2018 2 commits
  9. 02 Feb, 2018 1 commit
  10. 01 Feb, 2018 2 commits
  11. 29 Jan, 2018 4 commits
  12. 25 Jan, 2018 2 commits
    • Mats Wichmann's avatar
      Build gtest output paths correctly · a4e14b93
      Mats Wichmann authored
      Currently, when the run_tests function is called twice from the
      the same scons script (that is, the script has more than one unit
      test binary to register), the GTEST_OUTPUT environment variable
      becomes malformed.  This is because the string to add is added
      to a list instead of just being appended as a string.  The result
      is that while all the test output binaries are expected to go to
      BUILD_DIR/test_out, in these cases they go deep down underneath
      that directory.  Here are the unexpected paths in an unmodified
      testing run:
      The :xml: is intended as a tag used to signal gtest, it is never
      supposed to be part of the real filesystem path.
      Note fix was already proposed as part of
      https://gerrit.iotivity.org/gerrit/#/c/22275/ but since it's a
      distinct error with a very simple fix, wanted to get it pushed
      through by itself while that one is under consideration.
      Change-Id: I05c57d54034686a7c77c783eab758e7f501e86ea
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      (cherry picked from commit 0d010e4b)
    • Sushil Yadav's avatar
      Remove unused TIZEN package capi-network-wifi. · de6c5089
      Sushil Yadav authored
      The following change has been merged in the master.
      Pushing the change one the 1.3-rel branch as suggested by Phil.
      Change-Id: I8d4b8b97d93521174273e08aa9202e6008e6abfe
      Signed-off-by: default avatarSushil Yadav <sushil.ky@samsung.com>
      Reviewed-by: default avatarJooseok Park <jooseok.park@samsung.com>
      Reviewed-by: default avatarPhil Coval <philippe.coval@osg.samsung.com>
      Reviewed-by: default avatarUze Choi <uzchoi@samsung.com>
      Reviewed-by: default avatarAshok Babu Channa <ashok.channa@samsung.com>
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23347/
  13. 24 Jan, 2018 1 commit
  14. 19 Jan, 2018 2 commits
  15. 18 Jan, 2018 1 commit
  16. 17 Jan, 2018 1 commit
  17. 15 Jan, 2018 1 commit
  18. 12 Jan, 2018 1 commit
  19. 11 Jan, 2018 2 commits
  20. 08 Jan, 2018 1 commit
  21. 02 Jan, 2018 6 commits
  22. 19 Dec, 2017 1 commit
  23. 18 Dec, 2017 1 commit
    • George Nash's avatar
      IOT-582 Android build generate universal APK · 4b4a289f
      George Nash authored
      Two major modifications:
      1) The aar file no longer adds the TARGET_ARCH to the
      name of the file. The aar file contains all of the
      architectures that were built upto that point. This
      has been the case for quite a while so the architecture
      in the name only indicated the build that created the
      aar file not the contents of the aar file.
      2) When APK files are built it will try to build all
      possible architectures as well as the universal APK
      Bug: https://jira.iotivity.org/browse/IOT-582
      Change-Id: I11f5db9f4cb8c634afe4417b280e5feec6c3d7e9
      Signed-off-by: George Nash's avatarGeorge Nash <george.nash@intel.com>
  24. 13 Dec, 2017 1 commit
    • Philippe Coval's avatar
      resource: Fix occlientbasicops to support coaps · 0f2ae826
      Philippe Coval authored
      The fix is to do querry only on resource's address (to use CoAPs channel)
      Observed issue was:
        ./occlientbasicops -u 0 -c 0 -d 1 -p 0 -t 2
        INFO: occlientbasicops: Callback Context for GET query recvd successfully
        INFO: occlientbasicops: StackResult: OC_STACK_UNAUTHORIZED_REQ
        INFO: occlientbasicops: SEQUENCE NUMBER: 16777216
        INFO: PayloadLog: NULL Payload
        INFO: occlientbasicops: =============> Get Response
      I fixed it to:
        INFO: occlientbasicops: StackResult: OC_STACK_OK (...)
        INFO: PayloadLog: Payload Type: Representation (...)
        INFO: PayloadLog:     URI:/a/led (...)
        INFO: PayloadLog:             state(bool):false (...)
      Extra note, it look like the parse function is never returning false.
      Change-Id: Id3e48c8a04453e87a09e7636ead9a9f64c499d44
      Bug: https://jira.iotivity.org/browse/IOT-2390
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23637/Signed-off-by: default avatarPhilippe Coval <philippe.coval@osg.samsung.com>
      (cherry picked from commit f6394a48)
  25. 11 Dec, 2017 1 commit
  26. 08 Dec, 2017 1 commit