This repository contains code for creating an IoTivity-lite server emulator with GUI running on the the host OS. The examples include support for the glade GUI generator tool and GTK.
Currently, this has only been tested on IoTivity-lite and Ubuntu linux, but other platforms may work with slight modification.
There is currently one sample project.
- dimlight - This project creates a graphical dimmable light bulb that can be turned off or on and can be set to a dimming level between 0% and 100%. There are actually only 4 different brightness pictures, but the code will support any number of pictures if you have better graphics.
To install all the samples described above, just type the following command.
This command will do a number of things:
-
Clone the Emulator-Code repository (which includes all the sample code described above). Each sample subdirectory includes the following files:
- Makefile: A Makefile description file that will manage the compiling and linking of the project.
- .json: The JSON device description file that is the input to DeviceBuilder and describes all the resources available on the device. Each of these resources will show up in the source code and introspection file created by DeviceBuilder.
- .c: The C code that includes all the resources plus the code to interface to the glade GUI. This code can be copied over the C code created by DeviceBuilder when the gen2.sh script is run in order to control the hardware.
- Glade source and graphics that will generate the GUI.
-
The following variables MUST be set to point to the directories related to the OCF implementation you want to use in order to run the convenience scripts described below.
- OCFPATH - This is the absolute directory where the OCF implementation is installed and where all the convenience scripts are found. (This is typically /home/my_user_name/iot or /home/my_user_name/iot-lite)
- OCFSUBPATH - This is just the final part of OCFPATH, but it is necessary as a way to get the set_implementaion.sh script to work correctly. (This is typically /iot or /iot-lite)
- PATH - This is the normal search PATH, but it will have OCFPATH prepended to it so the scripts can be found.
-
source set_implementation.sh (/iot or /iot-lite) - This will switch the implementation of OCF to use (IoTivity or IoTivity-lite right now). It sets some environment variables that MUST be set for all of the scripts. IT IS CRITICAL to use the "source" command to run this script. That makes it work in the current bash context rather that a temporary one.
A number of convenience scripts have been written to make the development cycle easier.
- Run the following development cycle as needed
- create_project project_name - create a new project and name it anything you want.
- This isn't a script, but you need to "cd project_name" to run all the other scripts.
- Copy the setup.sh from the directory of the sample you want to install into the current project directory. (In the Emulator-Code repository)
- ./setup.sh - This will load all the necessary stuff to build and run the sample project.
- edit_input2.sh - edit the device description input file (project_name.json) if necessary.
- gen2.sh - generate the code, introspection file, PICS file, and onboarding file from the device description file.
- build2.sh - compile and link everything
- edit_code2.sh - edit the server source code if necessary.
- reset2.sh - reset the sever to RFOTM by copying a fresh onboarding file
- run2.sh - run the currently compiled server in the appropriate directory
- To test the project, you will need to run a client. Here are some options.
- Discover, onboard and control the server using OTGC
- Discover, onboard and control the server using DeviceSpy
- Test the server using CTT
- If you want to modify the glade GUI, run glade and open the following file:
- project_name/bin/glade/window_main.glade