Difference between revisions of "Installing EMAC OE 4.0 SDK"
| Line 1: | Line 1: | ||
Before beginning installation of the SDK, it is important to prepare the development system with the tools necessary to get the job done. These tools can either be command line interface (CLI) or graphical utilities. Both options are described in this guide. | Before beginning installation of the SDK, it is important to prepare the development system with the tools necessary to get the job done. These tools can either be command line interface (CLI) or graphical utilities. Both options are described in this guide. | ||
| − | {| class="wikitable" style="float: right; padding: 5px; margin: 10px; width: 500px;" | + | {| class="wikitable" style="float: right; padding: 5px; margin: 10px; margin-left: 20px; width: 500px;" |
!colspan="2"|Table 1: Conventions | !colspan="2"|Table 1: Conventions | ||
|- | |- | ||
Revision as of 13:09, 6 May 2013
Before beginning installation of the SDK, it is important to prepare the development system with the tools necessary to get the job done. These tools can either be command line interface (CLI) or graphical utilities. Both options are described in this guide.
| Table 1: Conventions | |
|---|---|
/download/directory/ |
Placeholder indicating the directory to which the SDK archive will be downloaded. |
/path/to/sdk/ |
Placeholder indicating the directory to which the SDK will be extracted. |
EMAC-OE-arm-linux-gnueabi-SDK_XX.YY.rZZ.tar.bz2EMAC-OE-arm-linux-gnueabi-SDK_XX.YY
|
XX is the major version YY is the minor version ZZ is the current revision The major and minor version numbers will match the version of OE for which the SDK is created. |
 | The SDK archive and directory names will differ based on which SDK is being installed. For example, the toolchain binary names will reflect the target CPU architecture. What is shown in this guide is for demonstration's sake. |
Required tools
- Web browser (recommended Mozilla Firefox, Gnuzilla Icecat, KDE Konqueror)
- Archiving tool. There are two options available:
- Graphical tools (Ark for kde, File Roller for gnome)
- CLI tool (tar is standard)
dialogrequired for CLI use of SDK. (See the developer's website.)
Recommendations
The following are some recommended install opations
- The SDK should be kept in the user's home directory. For example,
# /path/to/sdk/ might expand to something like
/home/user_name/cust_software/
To clarify, this is the location where EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/ will end up.
- The default SDK root folder name should be kept at its default name since this preserves the version information for the EMAC OE SDK.
