From: Michael D <me@md-5.net>
To: buildroot@busybox.net
Subject: [Buildroot] Addition of packages: libvirt & qemu (target)
Date: Mon, 03 Mar 2014 20:48:47 +1100 [thread overview]
Message-ID: <53144FFF.10702@md-5.net> (raw)
Hi guys,
First up, thanks for buildroot, its a really cool tool, and I've enjoyed
using it thus far. After some discussion on IRC with y_morin, I'd like
to put forward that the libvirt package is added, and that qemu is
adapted to support being installed on the target as well. libvirt is a
fairly standard autotools package, and shouldn't require much work,
although I did notice ./configure checked for some host qemu binaries.
You can see Yann's work on libvirt and target-qemu here:
https://gitorious.org/buildroot/buildroot/source/e09cf6e8d412cfd6163358fc7f58c83f44cc0a38:package/libvirt
https://gitorious.org/buildroot/buildroot/source/14ac053363188981cf7fb78b589a9e27fb464483:package/qemu
and my inexperienced, hackjob work over here, updates the packages to
their latest versions and removes unneeded depends:
https://github.com/md-5/Multiplicity/tree/master/package
libvirt requires the following depends to work:
host-pkgconf lvm2 libnl libxml2 yajl
In order for the configure script to detect yajl properly, it needs a
(e)glibc toolchain. This is due to yajl requiring -lm, which is not
linked into the test binary. A better solution than requiring (e)glibc
would be to patch libvirt's ./configure to link in -lm for the yajl
test. Yann's work on libvirt also depends on
libgcrypt and gnutls
which I assume add extra features. Ideally libvirt's depend section
should be updated if these (and any other feature enhancing) packages
are selected.
Building Qemu for the target on the other hand is quite a bit more
complex due to the sheer number of configuration options available. In
particular it depends on a x86 based toolchain with threads, and
host-pkgconf host-python libglib2 pixman
I'm reasonably sure Qemu can compile and run on other arches, however
Yann has not included support for this. Ideally the final package in
buildroot would only require these 4 libraries to build, additional
depends and features should be added with their necessary options and
installed if desired (util-linux, some sound libraries, and a lot of
graphics libraries for jpg/png manipulation).
Anyway, enough of me talking, it would be great to see these two
packages become properly integrated into buildroot, and I am hoping
someone can manage it.
If it helps sweeten the deal, I'll be more than happy to donate some
beer money to the successful contributors, or donate to the buildroot
project. I'll also be more than happy to make sure these packages stay
updated and working.
Thanks
Michael Dardis
next reply other threads:[~2014-03-03 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 9:48 Michael D [this message]
2014-03-05 6:48 ` [Buildroot] Addition of packages: libvirt & qemu (target) Arnout Vandecappelle
2014-03-06 6:44 ` Michael D
2014-03-06 8:15 ` Jeremy Rosen
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=53144FFF.10702@md-5.net \
--to=me@md-5.net \
--cc=buildroot@busybox.net \
/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