summaryrefslogtreecommitdiffstats
path: root/doc/FAQ/tools.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>2006-08-23 19:23:30 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>2006-08-23 19:23:30 +0000
commitd8f0aa16bc4fb1db2ca0cffb0df9b497092ffc91 (patch)
treec8416ee60fa013cc5fbb4d499eee3708e9200537 /doc/FAQ/tools.t
parent2006-08-23 Joel Sherrill <joel@OARcorp.com> (diff)
downloadrtems-d8f0aa16bc4fb1db2ca0cffb0df9b497092ffc91.tar.bz2
2006-08-23 Joel Sherrill <joel@OARcorp.com>
* Makefile.am, configure.ac, index.html.in: FAQ should now be completely in the Wiki. * FAQ/.cvsignore, FAQ/FAQ.texi, FAQ/Makefile.am, FAQ/basic.t, FAQ/bsp.t, FAQ/build45.t, FAQ/concepts.t, FAQ/debug.t, FAQ/endoftime.t, FAQ/entry, FAQ/freesw.t, FAQ/hwdebugaids.t, FAQ/projects.t, FAQ/stamp-vti, FAQ/tools.t, FAQ/version.texi, common/timemac.texi, common/timetbl.t, common/timing.t: Removed.
Diffstat (limited to 'doc/FAQ/tools.t')
-rw-r--r--doc/FAQ/tools.t71
1 files changed, 0 insertions, 71 deletions
diff --git a/doc/FAQ/tools.t b/doc/FAQ/tools.t
deleted file mode 100644
index 4af175bcc9..0000000000
--- a/doc/FAQ/tools.t
+++ /dev/null
@@ -1,71 +0,0 @@
-@c
-@c COPYRIGHT (c) 1988-2002.
-@c On-Line Applications Research Corporation (OAR).
-@c All rights reserved.
-@c
-@c $Id$
-@c
-
-@chapter General Development Tool Hints
-
-The questions in this category are related to the GNU development tools
-in a non-language specific way.
-
-@section What is GNU?
-
-Take a look at @uref{http://www.gnu.org,http://www.gnu.org} for information on the GNU Project.
-
-@section How do I generate a patch?
-
-The RTEMS patches to the development tools are generated using a
-command like this
-
-@example
-diff -N -P -r -c TOOL-original-image TOOL-with-changes >PATCHFILE
-@end example
-
-where the options are:
-
-@itemize @bullet
-
-@item -N and -P take care of adding and removing files (be careful not to
-include junk files like file.mybackup)
-
-@item -r tells diff to recurse through subdirectories
-
-@item -c is a context diff (easy to read for humans)
-
-@end itemize
-
-Please look at the generated PATCHFILE and make sure it does not
-contain anything you did not intend to send to the maintainers.
-It is easy to accidentally leave a backup file in the modified
-source tree or have a spurious change that should not be
-in the PATCHFILE.
-
-If you end up with the entire contents of a file in the patch
-and can't figure out why, you may have different CR/LF scheme
-in the two source files. The GNU open-source packages usually have
-UNIX style CR/LF. If you edit on a Windows platform, the line
-terminators may have been transformed by the editor into Windows
-style.
-
-@section How do I apply a patch?
-
-Patches generated with the @code{diff} program are fed into the
-@code{patch} program as follows:
-
-@example
-patch -p1 <PATCHFILE
-@end example
-
-where the options are:
-
-@itemize @bullet
-
-@item -pNUM tells @code{patch} to strip off NUM slashes from the
-pathname.
-
-@end itemize
-
-If @code{patch} prompts for a file to patch, you may need to adjust NUM.