| commit | 69897e94fd996ff92ad3df09bb82dae18add0320 | |
| author | Mooffie <mooffie@gmail.com> | |
| Sun, 8 Jan 2017 11:28:39 +0000 (8 13:28 +0200) | ||
| committer | Mooffie <mooffie@gmail.com> | |
| Sun, 15 Jan 2017 18:10:01 +0000 (15 20:10 +0200) | ||
| tree | ea0f50c3722a757e5b656ba8d253adfe77921d52 | treesnapshot (tar.gz zip) |
| parent | 0fdcfa6aa444144f81e0e63e94b88c8422e959bb | commitdiff |
Ticket #3753: extfs: tester: let test scripts easily access configure-time parameters.
We introduce a mechanism by which tests can easily access configure-time
parameters (like @PERL@, @AWK@, ...).
It works by "sourcing" a file named config.sh (residing in the build tree):
. "$MC_TEST_EXTFS_CONFIG_SH"
$PERL -e 'print "hello"'
(Although config.sh has a shell syntax, Perl and Python programs too can
benefit from it, because it can be sourced into an .env_vars file and the
values exported from there.)
Of course, one can also use the traditional method, of *.in files listed in
configure.ac, but the mechanism introduced here is a more comfortable approach.
Signed-off-by: Mooffie <mooffie@gmail.com>
We introduce a mechanism by which tests can easily access configure-time
parameters (like @PERL@, @AWK@, ...).
It works by "sourcing" a file named config.sh (residing in the build tree):
. "$MC_TEST_EXTFS_CONFIG_SH"
$PERL -e 'print "hello"'
(Although config.sh has a shell syntax, Perl and Python programs too can
benefit from it, because it can be sourced into an .env_vars file and the
values exported from there.)
Of course, one can also use the traditional method, of *.in files listed in
configure.ac, but the mechanism introduced here is a more comfortable approach.
Signed-off-by: Mooffie <mooffie@gmail.com>