Hello Richard,

Yes, but variants have set SDK_EXT_TYPE=full. Can't say about the pure
poky eSDK, but with our layers, size is different. Let's say 2/3 of the
"working" one.

Do you really need locked-sigs.inc from both variant? I guess, you only
need to know if some entries are missing and not the values. If yes,
then I have to build the old "working" on based on dunfell.


Regards,
Andrej

On Tue, 2022-06-28 at 11:16 +0100, Richard Purdie wrote:
> On Tue, 2022-06-28 at 07:55 +0000, Valek, Andrej wrote:
> > Hello Richard and Alex,
> > 
> > Richard:
> > We tried to revert the commits which you mentioned and it didn't
> > work.
> > 
> > Alex:
> > Yes, is fully reproducible on latest master.
> > 
> > bitbake core-image-minimal -c populate_sdk_ext
> > 
> > eSDK installed via: poky-glibc-x86_64-core-image-minimal-
> > cortexa15t2hf-
> > neon-qemuarm-toolchain-ext-4.1+snapshot.sh
> > 
> > . environment-setup-cortexa15t2hf-neon-poky-linux-gnueabi
> > devtool modify busybox
> > 
> > Sstate summary: Wanted 14 Local 0 Mirrors 0 Missed 14 Current 6 (0%
> > match, 30% complete)
> > 
> > So it started a compilation of missing components. We are assuming,
> > that eSDK will include all build deps for all components in the
> > image
> > and not just a deps for image itself.
> 
> Ok. To confirm, SDK_EXT_TYPE is set to full in both cases? Could you
> share the locked-sigs.inc file from both? I'd like to understand if
> the
> tools are there but not being used or whether they're really not
> there
> at all. Is there much of a size difference between the two eSDKs?
> 
> I suspect some kind of bisection to track down the change causing the
> issue will be necessary unfortunately but at least that test case is
> relatively straightforward...
> 
> Cheers,
> 
> Richard
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167370): 
https://lists.openembedded.org/g/openembedded-core/message/167370
Mute This Topic: https://lists.openembedded.org/mt/92019337/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to