Having laid the groundwork, we can now:
* In make-flight, for the rumpuserxen builds, set the runvars that
specify which xen.git bits etc. to build. (We pass qemuu now,
because we intend that eventually we will want to build that too.)
* In ts-rumpuserxen-build, record the locations of the app-tools
configure and make wrappers in the runvars which will be honoured by
ts-xen-build. Thus ts-xen-build in rumpuserxen build jobs will use
these app-tools and do a rump cross build.
* Add a ts-xen-build step to the build-rumpuserxen recipe, passing
`tools' as the target to build.
ts-rumpuserxen-build does not generate a formal set of build outputs.
Instead, the ts-xen-build step references the files generated by
ts-rumpuserxen-build directly (and is told where to find them via the
new command prefix runvars).
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
---
v2: Improve commit message.
tree_rumpuserxen=$TREE_RUMPUSERXEN \
${TREEVCS_RUMPUSERXEN:+treevcs_rumpuserxen=}${TREEVCS_RUMPUSERXEN} \
revision_rumpuserxen=$REVISION_RUMPUSERXEN \
+ tree_xen=$TREE_XEN \
+ tree_qemuu=$TREE_QEMU_UPSTREAM \
+ revision_xen=$REVISION_XEN \
+ revision_qemuu=$REVISION_QEMU_UPSTREAM \
tree_rumpuserxen_rumpsrc=$TREE_RUMPUSERXEN_RUMPSRC \
${TREEVCS_RUMPUSERXEN_RUMPSRC:+treevcs_rumpuserxen_rumpsrc=}${TREEVCS_RUMPUSERXEN_RUMPSRC}
# rumpsrc-related runvars needed only for old rumpuser-xen
proc run-job/build-rumpuserxen {} {
run-ts . = ts-rumpuserxen-build
+ run-ts . = ts-xen-build + host tools
}
proc prepare-build-host {} {
END
}
+sub recordtools() {
+ my $apptool = "$rux/app-tools/rumpxen-app";
+ store_runvar('cmdprefix_configure', "$apptool-configure");
+ store_runvar('cmdprefix_make', "$apptool-make");
+}
+
sub install() {
my $destdir="dist/usr/local/lib/xen/rump-kernel";
target_cmd_build($ho, 300, $builddir, <<END);
checkout();
massage();
build();
+recordtools();
install();
built_stash($ho, $builddir, 'dist', 'rumpuserxendist');