Skip to content

Latest commit

 

History

History
69 lines (54 loc) · 2.37 KB

HowToSetEnv.md

File metadata and controls

69 lines (54 loc) · 2.37 KB
Raw

Manual Setup Build Environment

This document describes the steps involved in setting up the build environment.

Contents

Get the toolchain

Install the OS specific toolchain. Supported OS types are "linux" and "mac".
Get the binaries and libraries from gcc-arm-none-eabi-6-2017-q1-update-OS Type.tar.bz2 to build. Unzip the gcc-arm-none-eabi-6-2017-q1-update-OS Type.tar.bz2 and export the path as shown below:

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

Note The recommended toolchain is fully working on 64 bit machines.

Get the source code

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

How to Build

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.

Configuration Sets

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.