This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> In order to achieve that, configure.ac and Makefile.in will be
Yao> created in common/ dir.

Is there a way we can avoid this?  Each configure carries some weight:
more maintenance (especially if they must be fixed in parallel), more
size, and slower build speeds.

Historically, IIUC, gdbserver had its own because it could be configured
and built separately.  But, this won't seem to be true once your patches
go in.

I see that common/Makefile.in doesn't have automatic dependency
tracking.  I think it should, especially if we are planning to move more
and more code there.  This would be simpler with a single configure :-)

FWIW, I'd like to get rid of testsuite/**/configure someday.  And, if we
can't configure gdbserver separately, then gdbserver/configure as well.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]