This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Add ARI directory to gdb sources
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 16 May 2012 07:44:20 -0700
- Subject: Re: [RFC] Add ARI directory to gdb sources
- References: <003901cd3337$66ac7b10$34057130$@muller@ics-cnrs.unistra.fr>
> The question of the location where we should add this script in gdb
> source arose. Joel suggested to put it directly into gdb directory.
Yeah, I didn't say it, but I agree it was a poor suggestion,
especially in light of:
> But after looking at the suggestion, it appears that you can't just
> use gdb_ari.sh alone, the update-web-ari script also uses
> gdb_find.sh script for instance, and a modified version of this
> update-web-air should probably also be added.
Here's what I think: Everything that generates is required to generate
the HTML code should be moved to the GDB directory. gdb/ari/ seems
fine to me, but others might want to comment. Unless the location
is critical to the implementation, which I hope it won't be, you
can start working on the move and submit patches. It should be
relatively easy to change the names if other suggestions appear.
On a user-interface level, it would be nice if the script that generates
the HTML was callable from out of tree, a little like configure.
I could create the HTML is a directory called "ari" located in
the current directory, for instance...
> writing as unofficial ARI maitainer
As far as I am concerned, you are the official ARI Maintainer :).
We'll make that official-official as soon as the code is moved
to the GDB repository by adding a section in the MAINTAINERS file.
--
Joel