Difference between revisions of "EMAC OE SDK Introduction"
(initial move from docuwiki) |
m |
||
| Line 5: | Line 5: | ||
To learn how to put these features into use, see the links below. | To learn how to put these features into use, see the links below. | ||
| − | + | <references> | |
| − | |||
* [[Install EMAC OE SDK]] | * [[Install EMAC OE SDK]] | ||
* [[Configure EMAC OE SDK]] | * [[Configure EMAC OE SDK]] | ||
| Line 15: | Line 14: | ||
* [[Building Existing Projects]] | * [[Building Existing Projects]] | ||
* [[Debugging with gdbserver]] | * [[Debugging with gdbserver]] | ||
| + | </references> | ||
Revision as of 12:10, 6 May 2013
The EMAC Open Embedded SDK is distributed in an archive that can be extracted and used from a Linux shell or imported into Eclipse as a ready-to-develop project. The archive contains a hardware-specific SDK which must be set up using the EMAC OE SDK Configuration page.
Each SDK includes the C/C++ header files and libraries compatible with the target hardware. It also includes the C/C++ cross-compiler toolchain components necessary to compile and debug custom application code. Understanding the details of this toolchain is not necessary for the application developer. However, the setup is simple enough for those with an intermediate knowledge of GNU/Linux development to understand and modify the configuration to suit application-specific needs if, necessary.
To learn how to put these features into use, see the links below.
