Due to the way that weston-ini-conf generates the weston.ini for the target, bitbake/OpenEmbedded are unable to automatically determine that it needs to mark the resulting package as machine-specific, so does not. This results in the wrong sstate file being found to be valid and we ship an incorrect weston.ini in images.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            jsmoeller Jan-Simon Moeller
            tmrini Thomas Rini
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: