This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [buildbot] Customized build and board file
- From: Pedro Alves <palves at redhat dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>, Yao Qi <qiyaoltc at gmail dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 13 Oct 2016 20:39:18 +0100
- Subject: Re: [buildbot] Customized build and board file
- Authentication-results: sourceware.org; auth=none
- References: <CAH=s-POtRfVyinbnVnK9sh04m_5BSs+M45DJcuUJKeoRsWy9xg@mail.gmail.com> <871szt89tz.fsf@redhat.com> <CAH=s-PN6qigxOaGXuGZ0r_cPGxB=aOUMgnyiQTrmiNdE4QnLWw@mail.gmail.com> <871szk5a2s.fsf@redhat.com>
On 10/13/2016 08:21 PM, Sergio Durigan Junior wrote:
>
> So, I'm trying to decide what is the best way to use the board file. It
> needs to be placed in the gdb/testsuite/boards/ directory, right?
You can run tests against a board file that is elsewhere.
See the steps described here:
https://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_remote_cross-target_configuration
~~~
Create an empty file named site.exp.
Create a directory named boards in the same location as site.exp.
Create a file named remote-gdbserver.exp in the boards directory (see below).
Set the DEJAGNU environment variable to point to the empty site.exp.
Run the testsuite with make check-gdb RUNTESTFLAGS="--target_board remote-gdbserver".
~~~
That used to be the only way people could run tests with the
gdbserver board files before "magic" was added that made it possible
to import the files into the tree.
> But
> the way BuildBot works is by making a full clone of the repository on
> for every build. I *might* be able to upload the file to the ARM slave,
> but that would require a hack that I'm trying to avoid.
Thanks,
Pedro Alves