-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
===============================================================================
+== NOTICE - Transition to SCONS ==
+===============================================================================
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+===============================================================================
== Rich Stack & Lite Stack ==
===============================================================================
-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
**Linux**
-------------------------------------------------------------------------------
To make octbstack.a in release mode:
+//----------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//----------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//----------------------------------------------------------------------
#1. build "connectivity" project
- execute make command in "connectivity/build/" folder.
license. Please refer to LICENSE.GPL oder LICENSE.BSD for further
details.
+NOTICE - TRANSITION TO SCONS
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
BUILD STEPS FOR INTEL OC STACK
Use below command to build libcoap:
Build notes
//-------------------------------------------------
+// NOTICE - Transition to SCONS
+//-------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//-------------------------------------------------
// Linux
//-------------------------------------------------
To enable logging, ensure that
+//---------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//---------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//---------------------------------------------------------------------
+
loggertests.cpp contain several logger tests that can be used in an Android JNI app.
androidloggertestoutput.txt is a file capture from running loggertests.cpp in an Android JNI app.
#==============================================================================
+# NOTICE - Transition to SCONS
+#==============================================================================
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+#==============================================================================
# Build instructions for Linux
#==============================================================================
+-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
+
# To build the ocmalloc google unit test for Linux:
# First
+-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
+
To compile for Linux or Android, include ocsocket.c and ocsocket.h in your project.
Look at the Makefile in ocsocket/test/linux and ocsocket/test/android for compilation dependencies.
Build notes
//-------------------------------------------------
+// NOTICE - Transition to SCONS
+//-------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//-------------------------------------------------
// Linux
//-------------------------------------------------
To build, run
-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
**Arduino** -- Must be built with the same BUILD mode declared as octbstack.a.
-------------------------------------------------------------------------------
When an Arduino SimpleClientServer application is running, it outputs logs to
-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
**Arduino** -- Must be built with the same BUILD mode declared as octbstack.a.
-------------------------------------------------------------------------------
When an Arduino SimpleClientServer application is running, it outputs logs to
+//---------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//---------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//---------------------------------------------------------------------
+
stacktests.cpp is a unit test of the APIs in ocstack.c.
It uses Google Test for the unit tests. Note that
the unit tests are only to test the functionality of
+//---------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//---------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//---------------------------------------------------------------------
+
stacktests.cpp contain several stack tests that can be used in an Android JNI app.
Note: to enable the logger for Android, TB_LOG should be defined in the ./jni/Android.mk file as
+//---------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//---------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//---------------------------------------------------------------------
+
ArduinoStackTest.cpp contains several logger tests and can be used in an
Arduino sketch.
+-------------------------------------------------------------------------------
+ NOTICE - Transition to SCONS
+-------------------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+-------------------------------------------------------------------------------
+
To run the oc_logger C sample app, first build liboctbstack.a
cd <root>/csdk
+//---------------------------------------------------------------------
+// NOTICE - Transition to SCONS
+//---------------------------------------------------------------------
+
+The IoTivity build system is transitioning to SCONS. Although the
+makefiles are still available (until v1.0) and some developers are
+still using them, they are currently no longer supported. To learn more
+about building using SCONS see Readme.scons.txt in the repository root
+directory. The build steps used in continuous integration can be found
+in auto_build.sh which is also in the the repository root directory.
+
+//---------------------------------------------------------------------
+
tests.cpp contains unittests for C++ APIs. It uses Google Test for the unit
tests. Note that the unit tests are only to test the functionality of OCApi.h.
It is not a system or end-to-end test.