diff options
| author | Stan Shebs <shebs@apple.com> | 2013-09-16 18:00:33 +0000 |
|---|---|---|
| committer | Stan Shebs <shebs@apple.com> | 2013-09-16 18:00:33 +0000 |
| commit | 5e29d2fbf6e977efbfd125bb69ba775fddf8d03b (patch) | |
| tree | a80c6c0a1bb2dd379a4de08c39d972c39ee070c2 /gdb/README | |
| parent | 44bf49ede30dc8a0a7e286d21ea4784a0bdb0125 (diff) | |
| download | gdb-5e29d2fbf6e977efbfd125bb69ba775fddf8d03b.tar.gz | |
* README: Update references to writing code for GDB.
* configure.ac (build_warnings): Remove obsolete comment.
* configure: Regenerate.
* gdbarch.sh: Remove references to gdbint.texinfo.
* gdbarch.h: Regenerate.
* gdbtypes.c (objfile_type): Remove comments referencing internals
manual and D10V.
[gdb/doc]
Remove the internals manual gdbint.texinfo.
* Makefile.in (INFO_DEPS): Remove gdbint.info.
(PDFFILES): Remove gdbint.pdf.
(HTMLFILES): Remove gdbint/index.html.
(HTMLFILES_INSTALL): Remove gdbint.
(GDBINT_DOC_FILES): Remove.
(dvi): Remove gdbint.dvi.
(ps): Remove gdbint.ps.
* gdbint.texinfo: Remove file.
* gdb.texinfo (Maintenance Commands): Remove reference to gdbint.
Diffstat (limited to 'gdb/README')
| -rw-r--r-- | gdb/README | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/gdb/README b/gdb/README index 33516ac9ea0..d485536ecfe 100644 --- a/gdb/README +++ b/gdb/README @@ -577,15 +577,16 @@ try typing `M-x gdb RET'. Writing Code for GDB ===================== - There is a lot of information about writing code for GDB in the -internals manual, distributed with GDB in gdb/doc/gdbint.texinfo. You -can read it by hand, print it by using TeX and texinfo, or process it -into an `info' file for use with Emacs' info mode or the standalone -`info' program. + There is information about writing code for GDB in the file +`CONTRIBUTE' and at the website: + + http://www.gnu.org/software/gdb/ + +in particular in the wiki. If you are pondering writing anything but a short patch, especially -take note of the information about copyrights in the node Submitting -Patches. It can take quite a while to get all the paperwork done, so +take note of the information about copyrights and copyright assignment. +It can take quite a while to get all the paperwork done, so we encourage you to start that process as soon as you decide you are planning to work on something, or at least well ahead of when you think you will be ready to submit the patches. |