source: rtems-docs/porting/development_tools.rst @ 969e60e

5
Last change on this file since 969e60e was 7497f5e, checked in by Joel Sherrill <joel@…>, on 10/28/16 at 20:57:11

porting: Review and tidy up multiple formatting issues.
  • Property mode set to 100644
File size: 1.1 KB
Line 
1.. comment SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. COMMENT: COPYRIGHT (c) 1988-2002.
4.. COMMENT: On-Line Applications Research Corporation (OAR).
5.. COMMENT: All rights reserved.
6
7Development Tools
8#################
9
10When porting RTEMS to a new CPU architecture, one will have to have a
11development environment including compiler, assembler, linker, and
12debugger.  The GNU development tool suite used by RTEMS supports most
13modern CPU families.  Often all that is required is to add RTEMS
14configurations for the target CPU family.  RTEMS targets for the GNU tools
15usually start life as little more than aliases for existing embedded
16configurations.  At this point in time, ELF is supported on most of the
17CPU families with a tool target of the form CPU-elf.  If this target is
18not supported by all of the GNU tools, then it will be necessary to
19determine the configuration that makes the best starting point regardless
20of the target object format.
21
22Porting and retargetting the GNU tools is beyond the scope of this manual.
23The best advice that can be offered is to look at the existing RTEMS
24targets in the tool source and use that as a guideline.
Note: See TracBrowser for help on using the repository browser.