aboutsummaryrefslogtreecommitdiff
path: root/gdb/proc-why.c
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2014-10-01 11:18:22 +0100
committerPedro Alves <palves@redhat.com>2014-10-01 12:08:40 +0100
commitdb74e4ba014f9ee96e8c8587534811c91c4d8ebb (patch)
tree1abefa77bb59d5ca09dc4c5c22124921db16b9f5 /gdb/proc-why.c
parentd63f2f8402c38d106b8508f324da6a5277471a2d (diff)
downloadgdb-db74e4ba014f9ee96e8c8587534811c91c4d8ebb.zip
gdb-db74e4ba014f9ee96e8c8587534811c91c4d8ebb.tar.gz
gdb-db74e4ba014f9ee96e8c8587534811c91c4d8ebb.tar.bz2
features/Makefile: Make 'make cfiles' default to generating all C files
This makes it easier to rebuild all GDB's generated target description C files. It also clarifies the comments a bit. One might think we need a GDB configured for the particular arquitecture (--target=foo). But a build that includes support for the target description is sufficient. (GDB rejects target descriptions that explicitly specify the architecture, with an <architecture> element, if the architecture is unknown.) Tested that "make clean-cfiles" deletes all .c files under src/gdb/features/, and that "make cfiles" generates them all without error, and that diffing the newly generated C files against master comes out an empty diff. gdb/ 2014-10-01 Pedro Alves <palves@redhat.com> * features/Makefile: Update comments. (XMLTOC): List all xml files we build C files from. (clean-cfiles): New rule.
Diffstat (limited to 'gdb/proc-why.c')
0 files changed, 0 insertions, 0 deletions