This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
GDB source structure
- From: "Veeru (àààà)" <misterveeru at gmail dot com>
- To: gdb at sourceware dot org
- Date: Fri, 1 Sep 2006 13:24:19 -0700
- Subject: GDB source structure
- References: <ee4c53600609011321k5a7a538fp933250cc13bb58d6@mail.gmail.com>
Hi Dan,
The set of files is reaching close to 600 in number in that directory.
At this point,
even doing an ls is difficult, forget separating out different
architectures and operating systems.
Some file names have the architecture or OS name in them but even that
usage is not consistent.
It would be far easier for folks interested in only a part of the
distribution to be able to focus
on the files that they are interested in.
I do believe though that if there is a method to the madness, it is up
to the newbies to learn it.
So, is there a method to the file structure?
Thanx!
Veeru
--
On Fri, Sep 01, 2006 at 11:04:22AM -0700, Veeru wrote:
Hi!
I have been looking at gdb lately. I come from a background of large system
software projects like compilers. I find it difficult at times to navigate
through the code simply because we appear to have everything within one
directory.
If you have questions about GDB, please use the GDB mailing list at
sourceware.org.
http://www.eyrie.org/~eagle/faqs/questions.html
Have we considered code refactoring using sub-directories, especially to
separate out architectures and operating systems in a way that one can only
concentrate on the stack he wants?
We've always decided in the past that it was not worth the
inconvenience and confusion of reorganizing.
--
Daniel Jacobowitz
CodeSourcery