diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-10-06 19:36:28 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-10-06 19:36:28 +0000 |
commit | 33cd2d43a18851aafdcb6bbdeebab679d8ab1c86 (patch) | |
tree | 922af6f1c7b54db14ca9218950a3730771a37ed7 /doc/porting/developtools.t | |
parent | Added $(LINK_LIBS) to linking gcc command so paranoia would link. (diff) | |
download | rtems-33cd2d43a18851aafdcb6bbdeebab679d8ab1c86.tar.bz2 |
New manual. First version to CVS. Just starting to see if it builds.
Diffstat (limited to '')
-rw-r--r-- | doc/porting/developtools.t | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/porting/developtools.t b/doc/porting/developtools.t new file mode 100644 index 0000000000..25098732a0 --- /dev/null +++ b/doc/porting/developtools.t @@ -0,0 +1,18 @@ +@chapter 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. + |