Re: [rfa/rfc] Build libcommon.a for gdb and gdbserver

Pedro Alves
2011-02-23T20:50:21Z

On Wednesday 23 February 2011 20:28:02, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> Pedro> I wasn't objecting. I agree with going back. We're
> Pedro> seeing more trouble than benefit from configure+Makefile
> Pedro> under common/ at this point. But I'd prefer to do an actual
> Pedro> revert, just to make sure we don't inadvertently leave
> Pedro> something behind or forget something.
>
> I realized my note may not have been totally clear -- I just realized I
> didn't really know what I was doing, and unlike other areas where I
> don't know what I am doing, in this one I don't have a pressing need to
> learn, I was just noodling around to little purpose. I have to get back
> to the stuff I'm really supposed to be doing :)

Noooooooooooo. :-)

> Concretely, I tend to agree about reverting but I am not committed to
> it. I think forward motion and enthusiasm is more important than the
> extra configury or whatever.

Indeed. But sometimes we need to take a step back. Nothing wrong
with that! 1 step back, 10 steps forward, and we learn in the
process.

Thinking forward, I was wondering about having a
configure.common fragment under common/ that's
sourced by both gdb/configure.ac and gdbserver/configure.ac.
In it, we'd have some AC_CHECK_HEADERS and other checks
necessary for the files under common/, and we'd export
a COMMON_OBJS variable with all the common objects, or
some such. We'd have no common.a library that's not
really common, still get rid of the extra configure, and
have one single place to add objects to.

But maybe we should only come back to this once
we do have more files under common/, and maintaining the
two configure/Makefiles reveals being a burden?
Or wait for changing this area again until 7.3 is branched?

--
Pedro Alves