Difference between revisions of "Installing EMAC OE 4.0 SDK"
(→Procedure) |
|||
| Line 45: | Line 45: | ||
... | ... | ||
EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/ | EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/ | ||
| − | + | ... | |
</syntaxhighlight> | </syntaxhighlight> | ||
== Next Steps == | == Next Steps == | ||
Once the EMAC SDK is installed, the next step is to [[configure it]]. | Once the EMAC SDK is installed, the next step is to [[configure it]]. | ||
Revision as of 16:45, 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.
Procedure
- Download the SDK. The latest version can be found on the public EMAC FTP site. Be sure to download the SDK that matches the architecture of your target system. Contact EMAC if unsure.
- Uncompress the SDK.
- Using a graphical archiving tool, uncompress the archive files to the chosen development directory. If you need assistance with this, please see the documentation for your graphical archiving tool.
- Alternatively, you can uncompress the archive from the CLI using tar:
developer@ldc:~$ cd /target/directory
developer@ldc:~$ bzip2 -cd /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2 | tar xvf -
This will produce a subdirectory within the target directory:
developer@ldc:~$ ls
...
EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/
...
Next Steps
Once the EMAC SDK is installed, the next step is to configure it.
