path: root/doc/porting/developtools.t
diff options
authorJoel Sherrill <>2016-11-15 10:37:59 -0600
committerJoel Sherrill <>2017-01-11 12:13:21 -0600
commit48a7fa31f918a6fc88719b3c9393a9ba2829f42a (patch)
tree10bf638de133099fcabe5fe713ca98a546a27ab2 /doc/porting/developtools.t
parent7a4b264574ce81d5473de6d15950464ea2cff485 (diff)
Remove texinfo format documentation. Replaced by Sphinx formatted documentation.
closes #2812.
Diffstat (limited to '')
1 files changed, 0 insertions, 23 deletions
diff --git a/doc/porting/developtools.t b/doc/porting/developtools.t
deleted file mode 100644
index a2278ae128..0000000000
--- a/doc/porting/developtools.t
+++ /dev/null
@@ -1,23 +0,0 @@
-@c COPYRIGHT (c) 1988-2002.
-@c On-Line Applications Research Corporation (OAR).
-@c All rights reserved.
-@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.