This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 0/2] Let's discuss moving gdbserver to top-level
- From: Alan Hayward <Alan dot Hayward at arm dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: "gdb-patches\\@sourceware.org" <gdb-patches at sourceware dot org>, nd <nd at arm dot com>
- Date: Mon, 3 Jun 2019 10:24:39 +0000
- Subject: Re: [RFC 0/2] Let's discuss moving gdbserver to top-level
- References: <20190530213046.20542-1-tom@tromey.com>
> On 30 May 2019, at 22:30, Tom Tromey <tom@tromey.com> wrote:
>
> I've wanted to move gdbserver to the top-level for a while now. I
> think it will provide a decent benefit, mainly by letting gdb and
> gdbserver share their libiberty, gnulib, and "common" libraries --
> shaving off some build time. It also will have the nice side effect
> of simplifying gdbserver's Makefile, fixing some existing bugs.
>
> I have written the patches to do this, but before reworking them into
> submittable form, I thought I'd send a couple of initial patches and
> start a discussion.
>
> This short series removes a couple of barriers to turning "common"
> into a library. These are pretty much the only changes that could be
> sent in isolation.
>
> The rest of the series is:
>
> * Move gnulib to the top-level
> * Rename "common" to "gdbsupport" in preparation for a move
> * Move "gdbsupport" to top-level
> * Move gdbserver to top-level
> * Make gdbserver share the other top-level libraries
>
> Most of the patches are pretty mechanical. There are one or two
> hacks, primarily because this series doesn't move the "nat" directory.
>
> Let me know what you think.
Do you have a work in progress branch you could push? I think it’d be
Useful to see what things look like after all the changes.
>
> Tom
>
>