summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorMartin Borg <martin.borg@enea.com>2016-02-25 16:08:04 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-28 11:33:03 +0000
commit5f82d17ac63f6d5b55f7b8d019c239620ab54596 (patch)
treef973ef675bf491b2db9da032ec00c54ea4fa8893 /scripts
parentb41862d33488d77f3b7c1e897490ea5cb2a35f67 (diff)
downloadpoky-5f82d17ac63f6d5b55f7b8d019c239620ab54596.tar.gz
automake: set test-driver path relative to top_builddir
automake offers auxiliary tools and is capable to install and prepare the setup for those. test-driver, a log driver used by parallel testsuite harness in ptests, is one of those tools. By default it looks that automake prepare environment for testing relative $top_srcdir. But in Yocto following changed: - build folder was separated - $top_srcdir is not anymore defined as relative path, now can be relative or absolute So now in Yocto the Makefile from src/tests contains absolute path of $top_srcdir for test-driver which is an unexisting path at runtime. We need to have relative path for test-driver in Makefile to work on target. $top_builddir can guarantee this path. Originally submitted by Adrian Calianu <adrian.calianu@enea.com> (From OE-Core rev: e9db0ae11d95f3c375b27d5c10606efd8b568fbf) Signed-off-by: Martin Borg <martin.borg@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions