5
Last change
on this file since 62d58f2 was
e52906b,
checked in by Sebastian Huber <sebastian.huber@…>, on 01/09/19 at 15:14:06
|
Simplify SPDX-License-Identifier comment
|
-
Property mode set to
100644
|
File size:
1.1 KB
|
Line | |
---|
1 | .. SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | .. Copyright (C) 1988, 2002 On-Line Applications Research Corporation (OAR) |
---|
4 | |
---|
5 | Development Tools |
---|
6 | ################# |
---|
7 | |
---|
8 | When porting RTEMS to a new CPU architecture, one will have to have a |
---|
9 | development environment including compiler, assembler, linker, and |
---|
10 | debugger. The GNU development tool suite used by RTEMS supports most |
---|
11 | modern CPU families. Often all that is required is to add RTEMS |
---|
12 | configurations for the target CPU family. RTEMS targets for the GNU tools |
---|
13 | usually start life as little more than aliases for existing embedded |
---|
14 | configurations. At this point in time, ELF is supported on most of the |
---|
15 | CPU families with a tool target of the form CPU-elf. If this target is |
---|
16 | not supported by all of the GNU tools, then it will be necessary to |
---|
17 | determine the configuration that makes the best starting point regardless |
---|
18 | of the target object format. |
---|
19 | |
---|
20 | Porting and retargetting the GNU tools is beyond the scope of this manual. |
---|
21 | The best advice that can be offered is to look at the existing RTEMS |
---|
22 | targets in the tool source and use that as a guideline. |
---|
Note: See
TracBrowser
for help on using the repository browser.