| Red Hat Docs > Manuals > EDK Manuals > |
|
Red Hat Embedded DevKit (EDK) provides a programming model for embedded systems in an integrated development environment (IDE), Source-NavigatorTM. Source-Navigator helps build projects for embedded systems. Such embedded systems range from strikingly simple systems like a microwave oven to incredibly complex ones such as a control system for a nuclear power plant. You wouldn't expect the control system for a nuclear plant to warm your dinner any more than you would expect your microwave to be the primary source for your email messages. With the EDK, you can create applications to meet such specific expectations. You will still perform much of your development for an executable application on your desktop for the target to use. The importance of the EDK is its dynamic interface and its seamless integration of the process of creating a project.
The process of creating a project requires: a kernel that is compliant with both host and target, a network filesystem for the host and target (since an embedded target does not typically include a hard drive for accessing files or directories), and a unified process to verify that the finished project actually works. With the EDK, you create, edit, compile, build, debug, test, and run a project, scanning your source code and loading the extracted information into the Source-Navigator project database. The resulting executable application then emerges for developing projects and for meeting the primary goal of the EDK, providing for more compatibility, versatility and sustainabilty of applications in a unifiying way for embedded environments. See Glossary if any of these terms are unfamiliar.
With the concepts that the documentation conveys, you can begin exploring your own software projects.
This documentation is for experienced Linux developers who have an interest in developing for embedded systems.
In addition to Getting Started, see the Red Hat EDK User's Guide from the Source-Navigator Help menu and the HTML documentation describing the following GNUPro Toolkit components of the EDK.
For other background knowledge, see the following documentation.
For the project's history, see http://sourceware.cygnus.com/elix/
For more information on Red Hat, see http://www.redhat.com
For more information on Linux, see http://www.linux.org
For Linux documentation, see http://www.linuxdoc.org
For more specific information on Linux, especially if you are new to using Linux, see http://www.linuxnewbie.org
This documentation uses the following conventions.
Throughout the documentation, you will find callouts. IMPORTANT! gives essential hints in the documentation. WARNING! helps you avoid problems such as damaged files or system or programming errors. NOTE further elaborates on a subject.
'%' indicates a command prompt in this documentation. A command prompt may different in some examples, depending on the system and tools in use; with the debugger and its console's command-line window, '(gdb)' is the prompt.
For input or output which is too long to fit on a line, the documentation uses a backslash (\) to signify the UNIX convention for a linefeed that would not interrupt a process. The backslash is not part of the actual source code.
This documentation uses the following conventions for commands, filenames, and other program-specific subjects.
Italicized text indicates content with emphasis, such as for first use of terminology or for subtitles of books in volume sets.
Bold text indicates content requiring extra emphasis, such as for warnings as well as for showing keystrokes, keys on your keyboard (such as Ctrl, Del, or Enter) or menu choices. The Ctrl keys and the Meta keys are often indicated in the text by C- and M-, respectively; Meta (or M-) indicates the diamond-shaped key.
Bold italicized text indicates content requiring additional emphasis, such as for very important instructions as well as for titles of volumes or additional documentation.
Typewriter-text indicates content that is an an example of onscreen input, such as PATH=/usr/bin/local or other literal bits of text from a program, such as filenames or source code. See the source code in Code.
Typewriter-text in bold indicates content that is an example of a program's output, such as a command prompt (see the example error message using a '%' prompt in Code).
Typewriter-text in italics indicates content that is an example of input that you substitute. For instance, the documentation may read "To remove filename from a directory, type rm filename; replace filename with an actual file name."
|
%
gcc -print-search-dirs |