Difference between revisions of "Installing EMAC OE 4.0 SDK"

From wiki.emacinc.com
Jump to: navigation, search
 
(22 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
{{todo|Polish|Michael Gloff|project=oe 4,mg}}
+
{{todo|SEOKWREV (11.15.13-15:12->KY+);(11.15.13-19:30->MD+);(02.12.14-13:25->MD-);(02.13.14-11:25->MG+);(02.26.14-18:00->MG+);(03.04.14-16:10->BS-);(03.10.14-11:50->MD+);(03.19.14-16:25->BS+);(04.14.14-14:30->BS+)|Michael Gloff|project=oe 4, mg,ky,md,bs,SEOKWREV}}
  
−
{{EMAC OE SDK Conventions}}
+
{{#seo:
 +
|title=Installing EMAC OE 4.0 SDK
 +
|titlemode=append
 +
|keywords=Installing EMAC SDK,EMAC 4.0 SDK
 +
|description=How to install 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.
  
−
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.
+
{{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.}}
  
−
{{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's sake.}}
+
== Required tools ==
 +
The following is a generic list of tools that need to be installed on a development machine to fully use the SDK. The method to install these tools varies according to the distribution of Linux used.
 +
* Web browser (recommended: [https://www.mozilla.org/en-US/firefox/new/ Mozilla Firefox] or [https://www.google.com/intl/en/chrome/browser/ Google Chrome])
 +
* C/C++ compiler and debugger
 +
* wput
 +
* minicom
 +
* ssh client
 +
* Archiving tool. These options are available:
 +
** Graphical: [http://utils.kde.org/projects/ark/ Ark] for KDE, [http://fileroller.sourceforge.net/ File Roller] for GNOME
 +
** CLI: [http://www.gnu.org/software/tar/ Tar] is standard
  
−
== Required tools ==
+
{{mbox | type = notice | style = margin-top: 1em; |  text = For systems using the APT system for package management, like Debian and Ubuntu, a [ftp://ftp.emacinc.com/Controllers/Development_Kits/EMAC_Open_Tools/Linux/emac_oe4_sdk_apt_packages package list] can be downloaded from EMAC's ftp site  and installed by typing: <syntaxhighlight lang="bash">
−
* Web browser (recommended [https://www.mozilla.org/en-US/firefox/new/ Mozilla Firefox], [https://www.gnu.org/software/gnuzilla/ Gnuzilla Icecat], [http://www.konqueror.org/download/ KDE Konqueror])
+
developer@ldc:~$ wget ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/emac_oe4_sdk_apt_packages
−
* Archiving tool. There are two options available:
+
developer@ldc:~$ sudo apt-get install $(cat emac_oe4_sdk_apt_packages)  
−
** Graphical tools ([[Ark]] for KDE, [[File Roller]] for GNOME)
+
</syntaxhighlight>
−
** CLI tool ([[tar]] is standard)
+
}}
−
* <code>dialog</code> required for CLI use of SDK ([[see the developer's website]]).
 
  
 
== Recommendations ==
 
== Recommendations ==
−
The following are some recommended install opations
+
The following are some recommended install options:
 
* The SDK should be kept in the user's home directory. For example,  
 
* The SDK should be kept in the user's home directory. For example,  
 +
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
# /path/to/sdk/ might expand to something like
+
# /path/to/sdk/ might be located on the filesystem at:
−
/home/user_name/cust_software/
+
/home/user_name/EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/
 
</syntaxhighlight>
 
</syntaxhighlight>
−
To clarify, this is the location where <code>EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/</code> will end up.
+
 
 +
This is the location where the downloaded SDK eg. <code>EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/</code> 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.
 
* The default SDK root folder name should be kept at its default name since this preserves the version information for the EMAC OE SDK.
  
Line 27: Line 43:
  
 
<cl>
 
<cl>
−
1. 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.
+
1. Download the SDK. The latest version can be found on the EMAC ftp site: [ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/EMAC-OE-arm-linux-gnueabi-SDK_4.0-latest.tar.bz2 Standard ] or [ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/EMAC-OE-arm-linux-gnueabi-SDK_4.0-qt-latest.tar.bz2 with Qt]. Be sure to download the SDK that matches the architecture of your target system.  
 
* Uncompress the SDK.
 
* 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.
+
  * 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:  
 
  * Alternatively, you can uncompress the archive from the CLI using tar:  
 +
 
  <syntaxhighlight lang="bash">
 
  <syntaxhighlight lang="bash">
−
  developer@ldc:~$ cd /target/directory
+
  developer@ldc:~$ cd /install/directory
 
  developer@ldc:~$ bzip2 -cd /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2 | tar xvf -
 
  developer@ldc:~$ bzip2 -cd /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2 | tar xvf -
 
  </syntaxhighlight>
 
  </syntaxhighlight>
−
This will produce a subdirectory within the target directory:
+
 
 +
The list of extracted files will be output to the screen. This may take a minute to complete.
 
  <syntaxhighlight lang="bash">
 
  <syntaxhighlight lang="bash">
 
  developer@ldc:~$ ls
 
  developer@ldc:~$ ls
 
  </syntaxhighlight>
 
  </syntaxhighlight>
 +
 +
A subdirectory within the installation directory will be created containing the SDK:
 
  <syntaxhighlight lang="console">
 
  <syntaxhighlight lang="console">
 
  ...
 
  ...
Line 47: Line 67:
  
 
== Next Steps ==
 
== Next Steps ==
−
Once the EMAC SDK is installed, the next step is to [[Configuring_EMAC_OE_SDK]].
+
Once the EMAC SDK is installed, the next step is to [[Configuring_EMAC_OE_4.0_SDK | configure the SDK ]].
  
−
[[Category:EMAC OE SDK]]
+
<!--[[Category:EMAC OE SDK]]-->

Latest revision as of 16:30, 6 June 2017

TODO: {{#todo:SEOKWREV (11.15.13-15:12->KY+);(11.15.13-19:30->MD+);(02.12.14-13:25->MD-);(02.13.14-11:25->MG+);(02.26.14-18:00->MG+);(03.04.14-16:10->BS-);(03.10.14-11:50->MD+);(03.19.14-16:25->BS+);(04.14.14-14:30->BS+)|Michael Gloff|oe 4, mg,ky,md,bs,SEOKWREV}}

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

The following is a generic list of tools that need to be installed on a development machine to fully use the SDK. The method to install these tools varies according to the distribution of Linux used.

For systems using the APT system for package management, like Debian and Ubuntu, a package list can be downloaded from EMAC's ftp site and installed by typing: 
developer@ldc:~$ wget ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/emac_oe4_sdk_apt_packages
developer@ldc:~$ sudo apt-get install $(cat emac_oe4_sdk_apt_packages)

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: Standard or with Qt. 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:~$ bzip2 -cd /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2 | tar xvf -
    The list of extracted files will be output to the screen. This may take a minute to complete. 
     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=5436"