qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: QEMU Devel Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Is there a way to package QEMU binaries?
Date: Tue, 12 Jun 2018 14:52:29 +0800	[thread overview]
Message-ID: <20180612065229.GB15344@xz-mi> (raw)
In-Reply-To: <20180612064119.GC29380@lemon.usersys.redhat.com>

On Tue, Jun 12, 2018 at 02:41:19PM +0800, Fam Zheng wrote:
> On Tue, 06/12 14:24, Peter Xu wrote:
> > Hi,
> > 
> > For example, I wanted to compile QEMU once and install it on multiple
> > systems.  What would be the suggested way to do so?
> > 
> > Is there something similar to "make bin-rpmpkg" for Linux?
> > 
> > Thanks in advance,
> 
> No. The big question is the libraries. Even if you create the rpm, the libraries
> that you have linked against are not necessarily available on the systems you
> install. This means you either list all possible libraries as required in the
> rpm spec, which is a waste, or the list is generated dynamically, which is not
> trivial. For example, you can easily build QEMU against a custom glib, but it's
> very tricky to generate an rpm from it that works on other systems.

That's true.  But my question was actually specific to when the
systems are sharing basically the same environment (kernel, library
versions, etc.).  A simple solution is that on each system I install
qemu official package then the dependencies will all be there, then I
install my custom package (which will possibly install the binaries
under /usr/local) and I run the customized binary.

> 
> For development, maybe it's easier to combine git and Ansible.

I would prefer avoid using git and compiling stuff, if there is a
way. :)

-- 
Peter Xu

  reply	other threads:[~2018-06-12  6:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  6:24 [Qemu-devel] Is there a way to package QEMU binaries? Peter Xu
2018-06-12  6:41 ` Fam Zheng
2018-06-12  6:52   ` Peter Xu [this message]
2018-06-12  7:01     ` Fam Zheng
2018-06-12  7:41       ` Peter Xu
2018-06-12  7:53         ` Liviu Ionescu
2018-06-13  3:48           ` Peter Xu
2018-06-12 11:34       ` Laszlo Ersek
2018-06-12 11:29   ` Laszlo Ersek
2018-06-13  3:46     ` Peter Xu
2018-06-12  8:52 ` Peter Maydell
2018-06-13  4:02   ` Peter Xu
2018-06-13  9:28     ` Daniel P. Berrangé
2018-06-14  2:55       ` Peter Xu
2018-06-14  8:14         ` Daniel P. Berrangé
2018-06-14 10:50           ` Peter Maydell
2018-06-14 11:03             ` Peter Xu
2018-06-14 12:58               ` Alex Bennée

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=20180612065229.GB15344@xz-mi \
    --to=peterx@redhat.com \
    --cc=famz@redhat.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).