From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Question about kernel.bbclass and staging kernel headers
Date: Tue, 05 Oct 2010 09:05:43 +0200 [thread overview]
Message-ID: <i8eio7$61v$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=RrOCP9UgOD+J_E8Sr3RTiNQBnwnBK9HiSLLe6@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05-10-10 08:36, Dmitry Fink wrote:
> Hi,
> I've noticed that kernel.bbclass has a bunch of logic for manually copying
> kernel headers into the staging area
> (with a lot of logic for handling symlinks and different locations of asm
> and arch folders in different kernel version),
> I was wondering if there is a special reason for doing that instead of just
> runninig "oe_runmake headers_install" like
> linux-libc-headers recipes do.
We have a number of recipes that use private kernel api and need more
headers than headers_install installs :(
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMqs5GMkyGM64RGpERAgfZAKCvr+v0z9Paav5wuUFPKZJcp8/1MwCeIBJ8
9fZ+6dhhXljiGUpD9nkgk+s=
=yGk2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-10-05 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 6:36 Question about kernel.bbclass and staging kernel headers Dmitry Fink
2010-10-05 7:05 ` 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='i8eio7$61v$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 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.