Commits · 72abe3c14b31dfc28ab67a504fa9f6a7979f8159 · IoTivity / iotivity-lite

15 Jun, 2018 1 commit

Make st regarding logic to library. · 72abe3c1

Jaehyun Cho authored Jun 05, 2018

To st_things modules use commonly, it need to
make that library. Make st_framework module in service
layer, and move st_app modules to there.

To make prebuilt library for st-app-fw, use make_prebuilt.py
script in tools folder. thil will copy dependency header in
prebuilt folder and copy library about st-app-fw(libst-app-framwork.a)
Detailed usage can check in make_prebuilt.py script file.

Please Add build option ST_APP_FW to build st-app-fw library.

-------------------------------
Test Case
  st_app (out of box)
     Create Soft-AP  : OK
     Provisioning : OK
     Controlled by ST android app :OK
  st_app (setup is done)  -  OK
  st_app (with reset)  - OK

Change-Id: Ie44b7053a69afe9ad230ecde1655f252bdd45ae7
Signed-off-by: Jaehyun Cho <jaehyun3.cho@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/25629Tested-by: IoTivity Jenkins <jenkins-daemon@iotivity.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

72abe3c1

02 Jun, 2018 1 commit

freertos: Build st_app (with stubbed parts) · b164bbbc

Philippe Coval authored May 30, 2018

IMHO, this should be refactored to split generic and platform parts,

I think that files from:
  ./apps/st_app/${port}
Should be relocated into:
  ./api/
And then plaform specific code should be in:
  ./port/${port}
Or eventually:
  ./extra/port/${port}
if not used by lib internals,
just to make app developer easier.

Change-Id: I3b0a5e952f4678a3c2d3c568085df2575cc4eeda
Bug: https://jira.iotivity.org/browse/LITE-8
Origin: https://gerrit.iotivity.org/gerrit/#/c/25547/Signed-off-by: Philippe Coval <p.coval@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/25547Tested-by: IoTivity Jenkins <jenkins-daemon@iotivity.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

b164bbbc