From: "Veeru (वीऱू)" <misterveeru@gmail.com>
To: gdb@sourceware.org
Subject: GDB source structure
Date: Fri, 01 Sep 2006 20:24:00 -0000 [thread overview]
Message-ID: <ee4c53600609011324u4170f512pe88c25064fca8579@mail.gmail.com> (raw)
In-Reply-To: <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
next parent reply other threads:[~2006-09-01 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee4c53600609011321k5a7a538fp933250cc13bb58d6@mail.gmail.com>
2006-09-01 20:24 ` Veeru (वीऱू) [this message]
2006-09-01 20:26 ` Daniel Jacobowitz
2006-09-01 20:57 ` Michael Snyder
2006-09-02 15:28 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee4c53600609011324u4170f512pe88c25064fca8579@mail.gmail.com \
--to=misterveeru@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox