Installing EMAC OE 4.0 SDK
Before beginning installation of the SDK, it is important that the development system has the required tools. These tools can either be command line interface (CLI) or graphical utilities. Both options are described in this guide.
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 purposes only. |
Required tools
- Web browser (recommended: Mozilla Firefox or Google Chrome)
- Archiving tool. These options are available:
- Graphical: Ark for KDE, File Roller for GNOME
- CLI: Tar is standard
Recommendations
The following are some recommended install options:
- The SDK should be kept in the user's home directory. For example,
# /path/to/sdk/ might be located on the filesystem at:
/home/user_name/EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/
This is the location where the downloaded SDK eg. 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 EMAC ftp site. Be sure to download the SDK that matches the architecture of your target system.
-
Uncompress the SDK.
-
Using a graphical archiving tool, double click the archive file and click extract. 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 /install/directory developer@ldc:~$ tar -xjvf /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2
developer@ldc:~$ ls
A subdirectory within the installation directory will be created containing the SDK:
... EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/ ...
-
Next Steps
Once the EMAC SDK is installed, the next step is to configure the SDK .