Hi, On Mon, 2020-06-15 at 11:29 +0000, mikko.rap...@bmw.de wrote: > On Wed, Jun 03, 2020 at 10:12:37AM +0200, Jan Luebbe wrote: > > As the PACKAGECONFIG variable has a large influence on the > > resulting > > package sizes and dependencies, it's useful to capture it in the > > recipe-level buildhistory. This makes it straightforward to analyze > > the > > impact of PACKAGECONFIG changes on the resulting image size. > > Thanks, this is a good idea! I would print using full PACKAGECONFIG > name to avoid any confusion.
Note that Richard has already merged this in master. I thought it was pretty clear when looking at if from the package context in the buildhistory. I wouldn't mind renaming it to PACKAGECONFIG, it there's agreement that it would be clearer. > And this reminds me that DISTRO_FEATURES isn't logged into > buildhistory either afaik... Might be useful, but DISTRO_FEATURES is relatively high-level so there's usually not much details you can optimize. Jan > A generic approach for adding more variables to buildhistory would be > nice.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139498): https://lists.openembedded.org/g/openembedded-core/message/139498 Mute This Topic: https://lists.openembedded.org/mt/74645612/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
