Commit f50ccdd4 authored by Kishen Maloor's avatar Kishen Maloor

Renamed ...-Constrained to ...-Lite in old docs

Change-Id: If7d7fc233809064eba60524df4a51c6a9fcce541
Signed-off-by: Kishen Maloor's avatarKishen Maloor <kishen.maloor@intel.com>
parent f2707a37
This diff was suppressed by a .gitattributes entry.
Getting Started
---------------
IoTivity-Constrained is a lightweight implementation of the
IoTivity-Lite is a lightweight implementation of the
`Open Connectivity Foundation <https://openconnectivity.org/>`_ (OCF) standards
for the Internet of Things (IoT).
......@@ -23,21 +23,21 @@ commercial-friendly Apache v2 license.
Contents
--------
- `IoTivity-Constrained Architecture`_
- `IoTivity-Lite Architecture`_
- `Project directory structure`_
- `Setup source tree`_
- `Building sample applications on Linux`_
- `Framework configuration`_
IoTivity-Constrained Architecture
IoTivity-Lite Architecture
---------------------------------
.. image:: IoTivityConstrained-Arch.png
.. image:: IoTivityLite-Arch.png
:scale: 100%
:alt: IoTivity-Constrained Architecture
:alt: IoTivity-Lite Architecture
:align: center
IoTivity-Constrained's design presents the following features:
IoTivity-Lite's design presents the following features:
- **OS agnostic core**: This cross-platform core (written in pure C)
encompasses the APIs, OCF resource model, protocol, security features,
......@@ -178,7 +178,7 @@ Building sample applications on Windows
---------------------------------------
A Visual Studio project file can be found in
``port/windows/vs2015/IoTivity-Constrained.sln``. Open the solution file in
``port/windows/vs2015/IoTivity-Lite.sln``. Open the solution file in
Visual Studio 2015 or newer. If the version of Visual Studio is newer a prompt
should pop up asking if you would like to upgrade the visual studio project
files. Agree to upgrade the files.
......
......@@ -4,4 +4,4 @@
make SERVER=1 <additional options you normally pass; eg. TARGET=...)
This selects the apps/server_contiki sample.
Specify CLIENT=1 instead to select the apps/client_contiki sample.
Add DEBUG=1 to include debug output from IoTivity-Constrained.
Add DEBUG=1 to include debug output from IoTivity-Lite.
......@@ -10,7 +10,7 @@
3) Perform the build:
make
Add DEBUG=1 to include debug output from IoTivity-Constrained.
Add DEBUG=1 to include debug output from IoTivity-Lite.
4) Launch the demo:
./server 1
......
......@@ -3,7 +3,7 @@
2) Perform the build:
Run export BOARD=native && make CLIENT=1 (or make SERVER=1)
CLIENT=1/SERVER=1 selects the client_riot/server_riot sample.
Add DEBUG=1 to include debug output from IoTivity-Constrained.
Add DEBUG=1 to include debug output from IoTivity-Lite.
3) Setup a tap interface:
sudo ip tuntap add tap0 mode tap user ${USER}
......
......@@ -54,7 +54,7 @@ static struct sockaddr_in6 dtls_addr6;
#define MY_DTLS_PORT (56789)
#endif /* OC_SECURITY */
static oc_endpoint_t *eps;
/* For synchronizing the network receive thread with IoTivity-Constrained's
/* For synchronizing the network receive thread with IoTivity-Lite's
* event loop.
*/
static struct k_sem sem;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment