diff options
| author | Martin Borg <martin.borg@enea.com> | 2016-02-25 16:08:04 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-02-28 11:32:38 +0000 |
| commit | e9db0ae11d95f3c375b27d5c10606efd8b568fbf (patch) | |
| tree | 6b056d15dedf96b617c9cd3bd4fa115a8f651436 /scripts | |
| parent | 11b0e7e1cb29fd1fbe06bdb5606a55b92ecdcc89 (diff) | |
| download | openembedded-core-e9db0ae11d95f3c375b27d5c10606efd8b568fbf.tar.gz openembedded-core-e9db0ae11d95f3c375b27d5c10606efd8b568fbf.tar.bz2 openembedded-core-e9db0ae11d95f3c375b27d5c10606efd8b568fbf.zip | |
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>
Signed-off-by: Martin Borg <martin.borg@enea.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions