Adding Python files to be autoloaded for a particular architecture

[Joel Brobecker]

> > You can try with --with-system-gdbinit=xxx instead.
> >
> 
> Thanks, but surely --with-system-gdbinit is designed for the system
> administrator? For example, on Debian, the supplied gdb is configured with
> --with-system-gdbinit=/etc/gdb/gdbinit. I don't want to conflict with this
> usage.

I don't think you can categorize the intended user of each option.
They just do different things.

> We can probably delete these two files, if no one else finds them useful
> > anymore. But I don't think you really want to use GDB's system-gdbinit
> > as a system-gdbinit-dir; generally speaking, my understand of the
> > directory provided in the GDB sources is that it's a collection of
> > files that are not necessarily meant to always be relevant.
> 
> Ah, OK, so I should instead configure with a different
> --with-system-gdbinit-dir? But how can I get my files installed in that
> directory? It seems like this is not something I can do with gdb's build
> system.
> 
> So should I be using a different route to get an architecture support file
> always installed and loaded?

Thinking out loud (I do not know all the details off the top of my head),
I see a couple of ways:
  - You use a subdirectory of system-gdbinit, and then configure GDB
    to use that subdirectory
  - You create one file that the sources all the other files you need,
    and then configure GDB to use that file as the system-gdbinit.

-- 
Joel