From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] libcacard: use the library?
Date: Wed, 17 Jun 2015 23:15:28 +0300 [thread overview]
Message-ID: <5581D560.3080601@msgid.tls.msk.ru> (raw)
In-Reply-To: <5581C9E2.70103@redhat.com>
17.06.2015 22:26, Paolo Bonzini wrote:
> On 17/06/2015 20:25, Michael Tokarev wrote:
[]
>> Ok. I wrote small configure script (just a simple shell script,
>> no auto*tools, since the configuration of it is stright-forward,
>> we just need to check libglib and libnss versions using pkg-config
>> and check if libtool works) and a small Makefile for libcacard.
>
> Thanks, can you put a git repo somewhere? I'll autoconfiscate it, in
> the meanwhile you can perhaps look at adding submodule support similar
> to pixman?
I tried autoconf&automake&libtool. It is a HugeMess, I disliked it.
So I rewrote it as a simple shell script.
The result of both attempts is available at http://www.corpit.ru/mjt/tmp/libcacard/
There are 4 files in there:
configure.ac Makefile.am -- auto*shit version, requires bootstrap like
libtoolize && aclocal && automake --foreign --add-missing && autoconf
configure Makefile.in -- my small version based on what qemu ./configure
currently does.
(note: running bootstrap above will override configure and Makefile.in).
That's about autoconfiscate.
Speaking of git repo -- we already have a git repo for it as part of
qemu tree. The only thing needed is to make a "subtree" with one or
another version of configure. Plus decide which version number it will
have, and how it will be used in qemu.
>> Now the question is what to do with it? How to make it external
>> and where to put it? What to use for its version? How to migrate
>> to its usage in qemu?
>>
>> I propose to put it in a separate git repository on qemu project
>> site and remove it from qemu source, since it is definitely not a
>> hard requiriment to have smartcard support. Or maybe we can keep
>> it for a release in qemu source, adding it as a submodule, with
>> a tweak to be able to use external lib instead of embedded copy
>> if external is available.
I think we should just drop in-tree support for it in qemu-2.6,
disabling cacard support if external libcacard is not available.
And until that time, keep it in-tree in qemu.
Thanks,
/mjt
next prev parent reply other threads:[~2015-06-17 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 9:44 [Qemu-devel] libcacard: use the library? Michael Tokarev
2015-04-27 9:49 ` Daniel P. Berrange
2015-04-27 9:54 ` Michael Tokarev
2015-04-27 10:00 ` Peter Maydell
2015-04-27 10:37 ` Paolo Bonzini
2015-06-17 18:25 ` Michael Tokarev
2015-06-17 19:26 ` Paolo Bonzini
2015-06-17 20:15 ` Michael Tokarev [this message]
2015-06-18 8:09 ` Paolo Bonzini
2015-06-18 8:11 ` Michael Tokarev
2015-06-18 8:18 ` Paolo Bonzini
2015-06-18 9:07 ` Markus Armbruster
2015-06-18 9:27 ` Daniel P. Berrange
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=5581D560.3080601@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.