From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] libcacard: use the library?
Date: Thu, 18 Jun 2015 11:07:53 +0200 [thread overview]
Message-ID: <87bngd2xli.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <55827EC2.9080302@redhat.com> (Paolo Bonzini's message of "Thu, 18 Jun 2015 10:18:10 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 18/06/2015 10:11, Michael Tokarev wrote:
>> 18.06.2015 11:09, Paolo Bonzini пишет:
>>> On 17/06/2015 22:15, Michael Tokarev wrote:
>>>> 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
>>>
>>> More like autoreconf -fvi.
>>
>> My 10-minute expirience with auto*tools did't go that far :)
>
> You got everything else right, though. Kudos.
>
>>>> configure Makefile.in -- my small version based on what qemu ./configure
>>>> currently does.
>>>
>>> Doesn't have dependency tracking. That's already a no-no I think.
>>
>> Well, it is trivial to add. For a first cut it works.
>
> And then it will be something else with cross-compilation, or something
> else. Let's just use autotools and call it a day...
In my experience, the Autotools are the worst build system, except for
all the others.
Libtool is particularly horrible. But when you actually have the
problem it solves (building shared libraries on almost every rotten OS
known to man), you're in a particularly horrible place already.
So, Paolo's recommendation seconded.
next prev parent reply other threads:[~2015-06-18 9:08 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
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 [this message]
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=87bngd2xli.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=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.