From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libvpx should not inherit autotools
Date: Thu, 07 Oct 2010 09:16:47 +0200 [thread overview]
Message-ID: <i8js4v$ocr$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTiknm8zsMUOFVfRXcZOGxitgjZPy8WxnnaU6hvMQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-10-10 08:26, Khem Raj wrote:
> On Wed, Oct 6, 2010 at 10:59 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> Hi Koen
>>
>> libvpx recipes are inheriting autotools while it seems to me that they
>> should not. Yes it does have a configure script but its not autoconf
>> generated but a hand written one
>> and there are no other traces of autoconf or automake and stuff that
>> goes with normal automake autoconf build systems.
>>
>> Would you take a look at it ?
>
> something like attached would work. What do you think ?
That works for me, I was just too lazy to create the do_compile and
do_install :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMrXPfMkyGM64RGpERAu6qAJ9N6gQM1etGUzSsClL/TRYXYiTKsQCfZTRD
D2oDrFbvVot3RDKPS7DdEko=
=l+C2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-10-07 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 5:59 libvpx should not inherit autotools Khem Raj
2010-10-07 6:26 ` Khem Raj
2010-10-07 7:16 ` Koen Kooi [this message]
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='i8js4v$ocr$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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