This is the mail archive of the
mailing list for the GDB project.
Re: Move gdbsupport to the top level
- From: Tom Tromey <tom at tromey dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Tom Tromey <tom at tromey dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Fri, 12 Jul 2019 07:05:13 -0600
- Subject: Re: Move gdbsupport to the top level
- References: <email@example.com> <CA+=Sn1=EHOoz=-5iOhbMP7OSYhJqQKNaojrAnR7mwpoPjoM0Xw@mail.gmail.com>
>>>>> "Andrew" == Andrew Pinski <firstname.lastname@example.org> writes:
Andrew> On Thu, Jul 11, 2019 at 2:03 PM Tom Tromey <email@example.com> wrote:
>> This patch moves the gdbsupport directory to the top level. This is
>> the next step in the ongoing project to move gdbserver to the top
>> The bulk of this patch was created by "git mv gdb/gdbsupport gdbsupport".
>> This patch then adds a build system to gdbsupport and wires it into
>> the top level. Then it changes gdb to use the top-level build.
Andrew> Isn't the top-level makefile also synced with GCC's (and newlib's)?
Andrew> Where GCC is techincally
Andrew> the maintainer of it?
Last time around I checked in the patches locally first and then I sent
I don't mind doing it the other way, if that's important for some
reason, but it's still better to get sign-off from the gdb side before
committing to doing it.