[PATCH] Also install data-directory into the build directory as computed by relocate_gdb_directory
Mon Oct 8 20:24:00 GMT 2012
On Mon, Oct 8, 2012 at 1:13 PM, Khoo Yit Phang <firstname.lastname@example.org> wrote:
> On Oct 8, 2012, at 12:33 PM, Doug Evans wrote:
>> On Sat, Oct 6, 2012 at 12:02 PM, Khoo Yit Phang <email@example.com> wrote:
>>> I prefer just installing data-directory into $BUILDDIR/share/data-directory, which is simple and works as long as gdb isn't configured with --bindir, --exec-prefix, and/or --with-gdb-datadir that are too unusual. It should cover most purposes of running gdb from the build directory, since I don't see much reason to change --bindir, --exec-prefix, and/or --with-gdb-datadir if gdb won't be installed, unless for testing those flags, in which case gdb will likely have to be installed anyways. Does anyone currently have a use case I'm missing?
>> I'm not entirely comfortable with having normal makes (as in "make
>> all") create files outside of its build directory (and by this I mean
>> $obj/gdb/../anything). [And obviously I'm not including "make
>> install" here. :-)]
>> I'd prefer passing -bd (for build directory), for example.
>> [Not the best name choice since -b specifies the serial port baud
>> rate. -bt for build tree, and -B are alternatives.]
>> I could also go with a configure option to create a second gdb binary
>> for use in the build tree.
>> I would never use it, but as long as those that want it agree to
>> maintain it, 'tis ok with me.
>> Neither the testsuite, nor anything else, can depend on it - it would
>> just be for developer convenience sake.
> What about a configure option to enable "make all" to install to $obj/gdb/../share/gdb? With ample warnings about caveats, and for developer convenience only, of course.
It's still having "make all" install something outside of gdb's build dir.
I won't object if someone else approves, but I'll be happy to remove
it if it ever bitrots or becomes problematic. :-)
More information about the Gdb-patches