diff options
author | Amar Takhar <amar@rtems.org> | 2016-01-16 19:08:48 -0500 |
---|---|---|
committer | Amar Takhar <verm@darkbeer.org> | 2016-05-02 20:51:23 -0400 |
commit | 6733466adf26030f781c2779747472150238cadd (patch) | |
tree | 3d04d21658ddf18562cefa4d9c8f18dd1d6b4459 /porting/development_tools.rst | |
parent | Fix markup (diff) | |
download | rtems-docs-6733466adf26030f781c2779747472150238cadd.tar.bz2 |
Split document into seperate files by section.
Diffstat (limited to 'porting/development_tools.rst')
-rw-r--r-- | porting/development_tools.rst | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/porting/development_tools.rst b/porting/development_tools.rst new file mode 100644 index 0000000..87c6b15 --- /dev/null +++ b/porting/development_tools.rst @@ -0,0 +1,25 @@ +Development Tools +################# + +When porting RTEMS to a new CPU architecture, one will have to have a +development environment including compiler, assembler, linker, and +debugger. The GNU development tool suite used by RTEMS supports most +modern CPU families. Often all that is required is to add RTEMS +configurations for the target CPU family. RTEMS targets for the GNU tools +usually start life as little more than aliases for existing embedded +configurations. At this point in time, ELF is supported on most of the +CPU families with a tool target of the form CPU-elf. If this target is +not supported by all of the GNU tools, then it will be necessary to +determine the configuration that makes the best starting point regardless +of the target object format. + +Porting and retargetting the GNU tools is beyond the scope of this manual. +The best advice that can be offered is to look at the existing RTEMS +targets in the tool source and use that as a guideline. + +.. COMMENT: COPYRIGHT (c) 1988-2002. + +.. COMMENT: On-Line Applications Research Corporation (OAR). + +.. COMMENT: All rights reserved. + |