From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <mike.looijmans@topic.nl>
Cc: <peter@berginkonsult.se>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] linux-libc-headers - how to handle for older kernels?
Date: Mon, 2 Dec 2019 09:33:33 +0000 [thread overview]
Message-ID: <20191202093333.GI3527@hiutale> (raw)
In-Reply-To: <aa713358-4ec7-5215-25f6-ef13f513c97f@topic.nl>
Hi,
On Mon, Dec 02, 2019 at 09:28:03AM +0000, Mike Looijmans wrote:
> One solution I can think of is to put the header into it's own
> recipe/repository and then refer to it like any other library would. Refer to
> that recipe from the module (or kernel) recipe that needs it. This way you
> have your header in a single maintainable location and dependencies properly
> taken care of.
>
> If that's not something you could live with, share your recipes, since vague
> problem descriptions will only get you vague solutions...
This is the problem I see with multiple BSPs. In the end for every one of them
the best solution is to fork linux-libc-headers.
Adding custom recipes to export headers for every BSP kernel is not scaling so well.
Sharing the BSPs and hacks around them would be nice but they are not public sadly :(
Cheers,
-Mikko
next prev parent reply other threads:[~2019-12-02 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 21:57 linux-libc-headers - how to handle for older kernels? Peter Bergin
2019-12-02 9:01 ` [yocto] " Mikko Rapeli
2019-12-02 9:13 ` Mike Looijmans
2019-12-02 9:19 ` Mikko Rapeli
2019-12-02 9:28 ` Mike Looijmans
2019-12-02 9:33 ` Mikko Rapeli [this message]
2019-12-02 14:01 ` Adrian Bunk
2019-12-02 14:09 ` Mikko Rapeli
2019-12-02 13:44 ` Bruce Ashfield
2019-12-03 7:59 ` Peter Bergin
2019-12-03 15:28 ` Bruce Ashfield
2019-12-04 7:46 ` Peter Bergin
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=20191202093333.GI3527@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=mike.looijmans@topic.nl \
--cc=peter@berginkonsult.se \
--cc=yocto@lists.yoctoproject.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.