diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2020-02-13 16:27:02 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2020-02-13 16:27:03 -0500 |
| commit | 06b3c5bdb018262d7c09cda9d4637015c7ebe779 (patch) | |
| tree | f993098885934d494acfcd5bf7e4203701437b88 /missing | |
| parent | 8f432634a53e91a1026dc81dbf3e70a7cd45c724 (diff) | |
| download | gdb-06b3c5bdb018262d7c09cda9d4637015c7ebe779.zip gdb-06b3c5bdb018262d7c09cda9d4637015c7ebe779.tar.gz gdb-06b3c5bdb018262d7c09cda9d4637015c7ebe779.tar.bz2 | |
gdbsupport: rename source files to .cc
This patch renames the .c source files in gdbsupport to .cc.
In the gdb directory, there is an argument against renaming the source
files, which is that it makes using some git commands more difficult to
do archeology. Some commands have some kind of "follow" option that
makes git try to follow renames, but it doesn't work in all situations.
Given that we have just moved the gdbsupport directory, that argument
doesn't hold for source files in that directory. I therefore suggest
renaming them to .cc, so that they are automatically recognized as C++
by various tools and editors.
The original motivation behind this is that when building gdbsupport
with clang, I get:
CC agent.o
clang: error: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Werror,-Wdeprecated]
In the gdb/ directory, we make clang happy by passing "-x c++". We
could do this in gdbsupport too, but I think that renaming the files is
a better long-term solution.
gdbserver still does its own build of gdbsupport, so a few changes in
its Makefile are necessary.
gdbsupport/ChangeLog:
* Makefile.am: Rename source files from .c to .cc.
(CC, CFLAGS): Don't override.
(AM_CFLAGS): Rename to ...
(AM_CXXFLAGS): ... this.
* Makefile.in: Re-generate.
* %.c: Rename to %.cc.
gdbserver/ChangeLog:
* Makefile.in: Rename gdbsupport source files from .c to .cc.
Diffstat (limited to 'missing')
0 files changed, 0 insertions, 0 deletions