Current supported platforms are Linux, NuttX, Tizen and TizenRT
OSX 10.10 as development host
- Build for x86 / Linux: Ubuntu 14.04 is used as a base platform.
- Build for Raspberry Pi 2 / Linux
- Build for Raspberry Pi 3 / Tizen
- Build for Stm32f4 / NuttX
- Build for ARTIK053 / TizenRT
- Build for ARTIK530 / Tizen
- Build for OpenWrt (non-tested)
- Build for Windows (experimental)
- Current supporting
- STM32F4-Discovery + BB
- Raspberry Pi 2
- Raspberry Pi 3
- Samsung ARTIK 053
- Samsung ARTIK 530
We will support the correct behavior of APIs for above environments. However, since IoT.js is targeting various kind IoT devices and platforms, single implementation cannot be the best practice for every environments. Therefore embedders should be in charge of optimization for their own environments. For more details on optimization, see the Optimization Tips page.
There is a script to help you build IoT.js called "build.py" in source repository. Run tools/build.py --help command to check all of the build options.
tools/build.py --clean--clean Clean build directory before build (default: False).
--no-snapshot Disable snapshot generation for IoT.js. It is useful for debugging sessions.
--profile PROFILE Specify the module profile file for IoT.js. It is used for enable and disable modules. See also "How to write a new module"
--run-test [{full,quiet}] Execute tests after build, optional argument specifies the level of output for the test runner.
--jerry-debugger Enable JerryScript debugger, so JavaScript could can be investigated with an available debugger client (eg.: Python Debugger Console or IoT.js Code). See also "Use JerryScript Debugger".
--js-backtrace {ON,OFF} Enable/disable backtrace information of JavaScript code (default: ON in debug and OFF in release build).