From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] libcacard: add libcacard.la target
Date: Mon, 16 May 2011 14:06:11 +0200 [thread overview]
Message-ID: <4DD11333.6020908@redhat.com> (raw)
In-Reply-To: <4DD0FD3C.20707@redhat.com>
Hi,
> Usually programs that are fully autoconf-iscated will ship a subset of
> libtool sources in the tarball, build a custom version at configure
> time, and invoke it from the Makefile via ./libtool. This has the
> advantage that only the maintainer needs to have libtool installed. OTOH
> we do not use Autoconf and I think this contributes to 99% of the bad
> name for Autoconf, so it's not something we want.
Another option would be to not use autoconf at all. Building ELF shared
libs isn't that difficuilt these days. Question is whenever there is
any non-ELF platform we care about (Windows maybe?).
cheers,
Gerd
next prev parent reply other threads:[~2011-05-16 12:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 15:40 [Qemu-devel] [PATCH 0/2] add libcacard shared object target Alon Levy
2011-05-15 15:40 ` [Qemu-devel] [PATCH 1/2] configure: add libdir and --libdir Alon Levy
2011-05-15 15:40 ` [Qemu-devel] [PATCH 2/2] libcacard: add libcacard.la target Alon Levy
2011-05-16 7:00 ` Paolo Bonzini
2011-05-16 10:25 ` Alon Levy
2011-05-16 10:32 ` Paolo Bonzini
2011-05-16 12:06 ` Gerd Hoffmann [this message]
2011-05-16 12:07 ` Paolo Bonzini
2011-05-16 12:14 ` Alon Levy
2011-05-16 12:18 ` Paolo Bonzini
2011-05-16 13:25 ` [Qemu-devel] [PATCH] " Alon Levy
2011-05-16 13:28 ` Anthony Liguori
2011-05-16 13:59 ` Paolo Bonzini
2011-05-16 17:37 ` Alon Levy
2011-05-16 14:44 ` Paolo Bonzini
2011-05-16 18:06 ` Alon Levy
2011-05-16 17:40 ` Alon Levy
2011-05-17 12:03 ` Alon Levy
2011-05-17 12:32 ` Alon Levy
[not found] ` <20110518034240.GL7083@playa.tlv.redhat.com>
2011-05-18 7:16 ` Paolo Bonzini
2011-05-18 8:49 ` Alon Levy
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=4DD11333.6020908@redhat.com \
--to=kraxel@redhat.com \
--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 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).