On Fri, Jan 7, 2022 at 6:19 PM Richard Purdie < [email protected]> wrote:
> On Fri, 2022-01-07 at 13:24 -0800, Saul Wold wrote: > > Move the do_strip() functionality to a more common location in the > > package split_and_strip_files() flow. This makes it possible for the > > extended packaging data to be generated correctly for the kernel and > > kernel modules. The KERNEL_IMAGE_STRIP_EXTRA_SECTIONS is reused in > > the runstrip() part of package stripping. > > > > Signed-off-by: Saul Wold <[email protected]> > > --- > > meta/classes/kernel.bbclass | 35 +++-------------------------------- > > 1 file changed, 3 insertions(+), 32 deletions(-) > > As I mentioned in previous mails, I think this will mean the do_deploy > output > will change and become unstripped which may cause a problem for some > platforms. > > We likely need to keep a strip task but call the new strip function from > it? > > I personally think this is a reasonable direction apart from that though, > at > least in principle. > Agreed. It looks ok to me as well, with us making sure that do_deploy can remain as it was. Bruce > > Cheers, > > Richard > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#160278): https://lists.openembedded.org/g/openembedded-core/message/160278 Mute This Topic: https://lists.openembedded.org/mt/88271781/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
