On Sun, Apr 12, 2020 at 6:07 PM Denys Dmytriyenko <[email protected]> wrote: > > + > > + # Generate the uboot-initial-env > > + oe_runmake -C ${S} O=${B} u-boot-initial-env > > So, why is this enabled unconditionally? Should this be in UBOOT_MAKE_TARGET? > > I use this .inc file for building different u-boot pieces by different recipes > (main u-boot, SPL, etc., etc.) controlling the build with UBOOT_MAKE_TARGET > below. Now each of those generate u-boot-initial-env and they clash in deploy.
They clash? how so? it generates different filenames so should not have a clash. > > This change is late in the cycle but it is critical in my opinion. > > > > The lack of default environment as well as the configuration for the > > tool is a regression from the previous release and this mitigates it. > > Well, I would rather live w/o env rather than unable to build u-boot at all... Please provide more information as I did not figure out what is not working by your report. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137195): https://lists.openembedded.org/g/openembedded-core/message/137195 Mute This Topic: https://lists.openembedded.org/mt/72715096/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
