qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <janine.schneider@fau.de>
To: "'Stefan Hajnoczi'" <stefanha@gmail.com>
Cc: 'qemu-devel' <qemu-devel@nongnu.org>,
	'qemu block' <qemu-block@nongnu.org>
Subject: AW: Integration of qemu-img
Date: Thu, 23 Apr 2020 12:53:48 +0200	[thread overview]
Message-ID: <008a01d6195d$78280570$68781050$@fau.de> (raw)
In-Reply-To: <CAJSP0QVeEZmSps3R8Hg+j=-BZR7_+FeOkm+m12A=gMULosP3Sg@mail.gmail.com>

Hy again,

okay so now we have an easy way out just in case.
But I still want to build an DLL and/or a shared library for integration into the tool. I want the tool to be platform independent and I was already able to build qemu-img as cross build with mingw64. Does anybody have experience in building a qemu library or tried it already?
The tool I want to integrate qemu in is published under GPL itself. And if I am able to build qemu as library I will share it with the community and everybody interested in having it.

Best,
Janine

-----Ursprüngliche Nachricht-----
Von: Stefan Hajnoczi <stefanha@gmail.com> 
Gesendet: Donnerstag, 23. April 2020 12:41
An: janine.schneider@fau.de
Cc: qemu-devel <qemu-devel@nongnu.org>; qemu block <qemu-block@nongnu.org>
Betreff: Re: Integration of qemu-img

On Thu, Apr 23, 2020 at 11:20 AM <janine.schneider@fau.de> wrote:
> this requires the user of the application to install qemu first right?
> If this is the case then this is unfortunately not an option. The user 
> shall not be bothered with installing anything else then the tool.

Hi Janine,
Please use Reply-All to keep the email CC list in tact.  That way qemu-devel@nongnu.org will receive our replies and the discussion will stay on the mailing list.  Thanks!

It's common for applications to consist of more than a single executable file.  They could have shared libraries, data files, or other executables like qemu-img.exe.  You can distribute qemu-img.exe together with your application as part of a zip file or installer.

Regardless of whether you ship qemu-img.exe or build a library, please check QEMU's software license so that you can follow the terms of the GPL open source license.

Stefan



  reply	other threads:[~2020-04-23 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00fc01d61256$35f849c0$a1e8dd40$@fau.de>
2020-04-16  7:50 ` Integration of qemu-img Markus Armbruster
2020-04-22 16:18   ` Stefan Hajnoczi
     [not found]     ` <006e01d61958$de787120$9b695360$@fau.de>
2020-04-23 10:40       ` Stefan Hajnoczi
2020-04-23 10:53         ` janine.schneider [this message]
2020-04-23 11:03           ` Daniel P. Berrangé

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='008a01d6195d$78280570$68781050$@fau.de' \
    --to=janine.schneider@fau.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).