EMAC OE SDK Introduction

Table 1: Conventions
/download/directory/	The directory to which the SDK archive will be downloaded.
/path/to/sdk/	The directory to which the SDK will be extracted.
EMAC-OE-arm-linux-gnueabi-SDK_XX.YY.rZZ.tar.bz2 EMAC-OE-arm-linux-gnueabi-SDK_XX.YY	XX - the SDK major version YY - the SDK minor version ZZ - the SDK current revision
target_program	The program executable created to run on the target device.
developer@ldc:~$	Prompt and commands to be run on a development machine that will run compliation tasks.
root@emac-oe:~#	Prompt and commands to be run on a target machine.

The EMAC Open Embedded SDK is distributed in an archive that can be extracted and used from a Linux shell or imported into Eclipse as a ready-to-develop project. The archive contains a hardware-specific SDK which must be set up using the EMAC OE SDK Configuration page.

Each SDK includes the C/C++ header files and libraries compatible with the target hardware. It also includes the C/C++ cross-compiler toolchain components necessary to compile and debug custom application code. Understanding the details of this toolchain is not necessary for the application developer. However, the setup is simple enough for those with an intermediate knowledge of GNU/Linux development to understand and modify the configuration to suit application-specific needs if, necessary.

To learn how to put these features into use, see the links below.