TizenRT is lightweight RTOS-based platform to support low-end IoT devices.
Please find project details at Wiki especially documentations page.

Quick Start
Supported Board / Emulator
Configuration Sets

Get the build in binaries and libraries, gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2
Untar the gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2 and export the path like

tar xvjf gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2
export PATH=<Your Toolchain PATH>:$PATH

Be aware that recommanded toolchain is fully working on 64bits machine.

git clone https://github.com/Samsung/TizenRT.git
cd TizenRT
TIZENRT_BASEDIR="$PWD"

Configure the build from $TIZENRT_BASEDIR/os/tools directory

cd os/tools
./configure.sh <board>/<configuration_set>

The configuration file is named defconfig,
and resides under the relative path <board>/<configuration_set> rooted at build/configs.
To check the different <board>/<configuration_set> combinations supported, type below:

./configure.sh --help

After configuring above, configuration can be modified through make menuconfig from $TIZENRT_BASEDIR/os.

cd ..
make menuconfig

Refer kconfig-frontend installation to use menuconfig.

Finally, initiate build by make from $TIZENRT_BASEDIR/os.

make

Built binaries are in $TIZENRT_BASEDIR/build/output/bin.

See Clean commands to clean built files.
See Trouble Shooting to resolve any issue on TizenRT usages.

Here are supported boards and emulator list.
Refer belows to know board-specifc environments, programming method and board information.

ARTIK053 [details]

ARTIK053S [details]

ARTIK055S [details]

CY4390X [details]

SIDK_S5JT200 [details]

QEMU [details]

To build a TizenRT application, use the default configuration files named defconfig under build/configs/<board>/<configuration_set> folder.
To customize your application with specific configuration settings, using the menuconfig tool is recommended at os folder as shown:

make menuconfig

Please keep in mind that we are actively working on board configurations, and will be posting our updates on the README files under each config.