Re: Adding Python files to be autoloaded for a particular architecture

Christian Biesinger
2020-07-17T22:10:30Z

On Fri, Jul 17, 2020 at 5:03 PM Reuben Thomas via Gdb
<gdb@sourceware.org> wrote:
>
> On Fri, 17 Jul 2020 at 22:42, Joel Brobecker <brobecker@adacore.com> wrote:
>
> > > This seems to be a suitable candidate for SYSTEM_GDBINIT_FILES. But if I
> > > simply add a file to `SYSTEM_GDBINIT_FILES` in
> > > `gdb/data-directory/Makefile.in`, and then configure with
> > >
> > > --with-system-gdbinit-dir=$pkgdatadir/system-gdbinit
> >
> > 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.
>
> 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.

FWIW I kinda think that directory should be renamed. Maybe
contrib/gdbinit, or sample-gdbinit, or something.

> 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?

You could certainly add new rules modeled after the system-gdbinit
ones in gdb/data-directory/Makefile.in?

Christian