qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aliguori@linux.vnet.ibm.com, mdroth@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 1/5] guest tools: add iso/tarball generator for guest tools
Date: Mon, 22 Aug 2011 12:09:16 -0500	[thread overview]
Message-ID: <1314032960-23474-2-git-send-email-mdroth@linux.vnet.ibm.com> (raw)
In-Reply-To: <1314032960-23474-1-git-send-email-mdroth@linux.vnet.ibm.com>

This script runs a series of tool-specific builds/configuration, each of
which should result in a self-contained installation directory at
$iso_root/projects/<project>, with a script or executable called
"install.linux". The script/executable must be runnable on standard
distros, so a basic shell script to kick off the install logic for the
guest is preferred.

When run in the guest, the install harness will iterate through these
projects, cd'ing into $iso_root/projects/<project> and executing the
"install.linux" script.

Windows support will be added later in a similar manner.

Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
---
 scripts/build-guest-iso.sh |   46 ++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 46 insertions(+), 0 deletions(-)
 create mode 100755 scripts/build-guest-iso.sh

diff --git a/scripts/build-guest-iso.sh b/scripts/build-guest-iso.sh
new file mode 100755
index 0000000..c8fbee8
--- /dev/null
+++ b/scripts/build-guest-iso.sh
@@ -0,0 +1,46 @@
+#!/bin/sh
+
+tmp=${tmp:-"/tmp"}
+qemu_dir=${qemu_dir:-$PWD}
+concurrency=${concurrency:-4}
+output_dir=${output_dir:-$PWD}
+
+if [ -e $qemu_dir/VERSION ]; then
+    version=`cat $qemu_dir/VERSION`
+else
+    echo qemu source directory not found
+    exit 1
+fi
+
+package=qemu-guest-tools-${version}${version_extra}
+iso_root=$tmp/$package
+build_dir=$tmp/qemu_iso_build
+projects_dir=$iso_root/projects
+mkdir -p $projects_dir
+mkdir -p $build_dir
+rm -rf $iso_root/* $build_dir/*
+
+cp -r $qemu_dir/guest-tools-iso/* $iso_root
+cd $build_dir
+
+# BUILD PROJECTS
+
+# qemu-ga
+
+# --enable-io-thread is just a workaround on RHEL5 for lack of signalfd()
+# support (which configure complains about). we don't use either
+$qemu_dir/configure --enable-guest-agent --extra-cflags="-m32" --enable-io-thread
+make -j$concurrency qemu-ga
+cp qemu-ga $projects_dir/qemu-ga/qemu-ga.linux.x86
+make distclean
+
+$qemu_dir/configure --enable-guest-agent
+make -j$concurrency qemu-ga
+cp qemu-ga $projects_dir/qemu-ga/qemu-ga.linux.x86_64
+make distclean
+
+# GENERATE GUEST TOOLS ISO/TARBALL
+
+cd $tmp
+tar zpvcf $output_dir/$package.tar.gz $package
+mkisofs -o $output_dir/$package.iso $package
-- 
1.7.0.4

  reply	other threads:[~2011-08-22 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 17:09 [Qemu-devel] [RFC] QEMU Guest Tools ISO Follow-up Michael Roth
2011-08-22 17:09 ` Michael Roth [this message]
2011-08-22 17:09 ` [Qemu-devel] [PATCH 2/5] guest tools: installer harness Michael Roth
2011-08-22 17:09 ` [Qemu-devel] [PATCH 3/5] guest tools: qemu-ga, debian init files Michael Roth
2011-08-22 17:09 ` [Qemu-devel] [PATCH 4/5] guest tools: qemu-ga, redhat init scripts Michael Roth
2011-08-22 17:09 ` [Qemu-devel] [PATCH 5/5] guest tools: installer for qemu-ga Michael Roth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1314032960-23474-2-git-send-email-mdroth@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).