diff options
| author | Dan Nicholson <dbn.lists@gmail.com> | 2009-10-10 14:17:25 -0700 |
|---|---|---|
| committer | Dan Nicholson <dbn.lists@gmail.com> | 2009-10-10 15:02:25 -0700 |
| commit | 1a194fa9aa94e0e36b498b76015f7374fdae65d3 (patch) | |
| tree | 75a55f076189e97c516a60925e050b458db4e03c /xts5 | |
| parent | 0fa0b4c102723798ca43f30d2021ebead387b673 (diff) | |
tet: Allow for executables outside of TET_ROOT by default
tet is really built around the notion that all the source, programs, data
and output will all live in a single tree. However, often times the test
programs are built and/or installed in a separate location. This can be
worked around with various environment variables or command line options,
but it would be better to build this behavior in by default.
This introduces TET_EXEC_ROOT, which specifies the base directory for tet
test programs. The tests will be found in the test suite subdirectory of
TET_EXEC_ROOT. E.g., $TET_EXEC_ROOT/xts. The default here is to have
TET_ROOT=$datadir and TET_EXEC_ROOT=$libexecdir.
Diffstat (limited to 'xts5')
| -rw-r--r-- | xts5/bin/xts-run.in | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/xts5/bin/xts-run.in b/xts5/bin/xts-run.in index a9a5f62d..32c4cabd 100644 --- a/xts5/bin/xts-run.in +++ b/xts5/bin/xts-run.in @@ -1,8 +1,6 @@ #!/bin/sh bindir="%bindir%" -libexecdir="%libexecdir%" -xtsexecdir="${libexecdir}/xts5" DEFAULT_TET_ROOT="%DEFAULT_TET_ROOT%" TCC=${TCC-tcc} @@ -65,5 +63,4 @@ if [ ! -d "$outdir" ] && ! mkdir -p "$outdir"; then exit 1 fi -"$TCC" -e -a "$xtsexecdir" -i "$outdir" -j "$outdir/journal" \ - -x "$config" xts5 $scenario +"$TCC" -e -i "$outdir" -j "$outdir/journal" -x "$config" xts5 $scenario |