Juan Quintela 36bd9e3c8b migration-test: Only generate a single target architecture ... Several changes: - We only allow generate header "inside" the tree. Why? Because we need to connit the result, so it makes no sense to generate them on the build dir. - We only generate a single target each time. Getting all the cross-compilers correctly is an impossible task. So know you do: make -C tests/migration $target (native) make CROSS_PREFIX=foo- -C tests/migratiion $target (cross) And you are done. - If we are building out of tree, we have no data about if we are cross-compile or whatever. So instead of guess what is happening, just do what I pointed on previous point. Signed-off-by: Juan Quintela <quintela@redhat.com> Message-Id: <20180913132313.11370-1-quintela@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>		2018-10-11 19:58:26 +01:00
..
aarch64	tests: Add migration test for aarch64	2018-10-11 18:12:47 +01:00
guestperf	Revert "tests: migration/guestperf Python 2.6 argparse compatibility"	2018-10-03 23:08:51 -03:00
i386	tests/migration: Support cross compilation in generating boot header file	2018-09-26 13:19:03 +01:00
s390x	tests/migration: Enable the migration test on s390x, too	2018-10-11 19:58:21 +01:00
.gitignore
guestperf-batch.py
guestperf-plot.py
guestperf.py
Makefile	migration-test: Only generate a single target architecture	2018-10-11 19:58:26 +01:00
migration-test.h	tests/migration: Enable the migration test on s390x, too	2018-10-11 19:58:21 +01:00
stress.c	Clean up includes	2018-02-09 05:05:11 +01:00