4.104.114.84.95
Line | |
---|
1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1998. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | @c $Id$ |
---|
7 | @c |
---|
8 | |
---|
9 | @chapter General Development Tool Hints |
---|
10 | |
---|
11 | The questions in this category are related to the GNU development tools |
---|
12 | in a non-language specific way. |
---|
13 | |
---|
14 | @section How do I generate a patch? |
---|
15 | |
---|
16 | The RTEMS patches to the development tools are generated using a |
---|
17 | command like this |
---|
18 | |
---|
19 | @example |
---|
20 | diff -N -P -r -c TOOL-original-image TOOL-with-changes >PATCHFILE |
---|
21 | @end example |
---|
22 | |
---|
23 | where the options are: |
---|
24 | |
---|
25 | @itemize @bullet |
---|
26 | |
---|
27 | @item -N and -P take care of adding and removing files (be careful not to |
---|
28 | >include junk files like file.mybackup) |
---|
29 | |
---|
30 | @item -r tells diff to recurse through subdirectories |
---|
31 | |
---|
32 | @item -c is a context diff (easy to read for humans) |
---|
33 | |
---|
34 | @end itemize |
---|
35 | |
---|
36 | Please look at the generated PATCHFILE and make sure it does not |
---|
37 | contain anything you did not intend to send to the maintainers. |
---|
38 | It is easy to accidentally leave a backup file in the modified |
---|
39 | source tree or have a spurious change that should not be |
---|
40 | in the PATCHFILE. |
---|
41 | |
---|
42 | If you end up with the entire contents of a file in the patch |
---|
43 | and can't figure out why, you may have different CR/LF scheme |
---|
44 | in the two source files. The GNU open-source packages usually have |
---|
45 | UNIX style CR/LF. If you edit on a Windows platform, the line |
---|
46 | terminators may have been transformed by the editor into Windows |
---|
47 | style. |
---|
Note: See
TracBrowser
for help on using the repository browser.