Difference between revisions of "Installing EMAC OE 4.0 SDK"

From wiki.emacinc.com
Jump to: navigation, search
m (Approved for Complete.)
Line 3: Line 3:
 
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.
 
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.
  
−
{{mbox | type = notice | style = margin-left: 0; margin-bottom: 1em; | text = 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.}}
+
{{mbox | type = notice | style = margin-bottom: 1em; | text = 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 ==
 
== Required tools ==

Revision as of 17:38, 4 December 2013

TODO: {{#todo:Polish(11.15.13-15:12->KY+);(11.15.13-19:30->MD+)|Michael Gloff|oe 4, mg,ky,md,Complete}}

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

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

  1. 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.

  2. 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

    The list of extracted files will be output to the screen. This may take a minute. 

     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 .

Retrieved from "https://wiki.emacinc.com/index.php?title=Installing_EMAC_OE_4.0_SDK&oldid=1837"