aboutsummaryrefslogtreecommitdiff
path: root/gas
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@adacore.com>2015-12-22 13:28:41 +0400
committerJoel Brobecker <brobecker@adacore.com>2015-12-24 09:25:45 +0400
commitab8314b3d99625c9a2125d39f4f3e74bf9e49cce (patch)
tree1a6d69ea86a2d16be481342c753ea432c43b275d /gas
parent64ac34cf666e2f6b47ee4d4ad8d57e8edac8514e (diff)
downloadgdb-ab8314b3d99625c9a2125d39f4f3e74bf9e49cce.zip
gdb-ab8314b3d99625c9a2125d39f4f3e74bf9e49cce.tar.gz
gdb-ab8314b3d99625c9a2125d39f4f3e74bf9e49cce.tar.bz2
[testsuite/Ada] stop using project files when building test programs
The current approach when building Ada programs for testing is based on the use of a project file (testsuite/gdb.ada/gnat_ada.gpr). To do that, we pass a number of additional arguments to target_compile, one of them being the project file (via "-P/path/to/gnat_ada.gpr"). This used to work well-enough, but AdaCore is currently working towards removing project-file support from gnatmake (the prefered tool for using project files is gprbuild). So, we need to either switch the compilation to gprbuild, or stop using project files. First, using gprbuild is not always what users will be using to build their applications. So having the option of using gnatmake provides more flexibility towards exactly reproducing past bugs. If we ever need a testcase that requires the use of gprbuild, then I believe support for a new target needs to be added to dejagnu's target_compile. Also, the only real reason behind using a project file in the first place is that we wanted to make it easy to specify the directory where all compilation artifacts get stored. This is a consequence of the organization choice we made for gdb.ada to keep each testcase well organized. It is very easy to achieve that goal without using project files. This is therefore what this patch does: It change gdb_compile_ada to build any program using gnatmake without using a project file (by temporarily changing the current working directory). There is a small (beneficial) side-effect; in the situation where GDB is built in-tree, gnatmake is called as... % gnatmake [...] unit.adb ... which means that the debugging info in unit.o will say contain a filename whose name is 'unit.adb', rather than '/path/to/unit.adb'. This also better matches what users might typically do. But the side- effect is that the unit name in the GDB output is not always a full path. This patch tweaks a couple of testcases to make the path part optional. gdb/testsuite: * lib/ada.exp (target_compile_ada_from_dir): New function. (gdb_compile_ada): Reimplement avoiding the use of project files. * gdb.ada/gnat_ada.gpr: Delete. * gdb.ada/cond_lang.exp: Adjust test to make path before filename optional. * gdb.ada/small_reg_param.exp: Likewise. Tested on x86_64-linux, with both in-tree and out-of-tree builds.
Diffstat (limited to 'gas')
0 files changed, 0 insertions, 0 deletions