From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id D9039E00E46; Fri, 29 Apr 2016 00:24:32 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.analogue-micro.com (mail.analogue-micro.com [217.144.149.242]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 699F4E00E42 for ; Fri, 29 Apr 2016 00:24:26 -0700 (PDT) Received: by mail.analogue-micro.com (Postfix, from userid 999) id E3DAA68A01B; Fri, 29 Apr 2016 08:24:25 +0100 (BST) Received: from zeus.mlbassoc.com (unknown [10.8.0.2]) by mail.analogue-micro.com (Postfix) with ESMTP id A9BE168A019; Fri, 29 Apr 2016 08:24:24 +0100 (BST) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by zeus.mlbassoc.com (Postfix) with ESMTP id 4708E67403F7; Fri, 29 Apr 2016 09:24:24 +0200 (CEST) To: Paul Eggleton References: <5722E217.40108@mlbassoc.com> <1690881.tSgHQ4Xn3V@peggleto-mobl.ger.corp.intel.com> <5722F9D8.2080202@mlbassoc.com> <1564642.UuUWA349Vz@peggleto-mobl.ger.corp.intel.com> From: Gary Thomas Message-ID: <57230C27.6030900@mlbassoc.com> Date: Fri, 29 Apr 2016 09:24:23 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1564642.UuUWA349Vz@peggleto-mobl.ger.corp.intel.com> Cc: yocto@yoctoproject.org Subject: Re: Change in override behavior? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 07:24:32 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2016-04-29 09:16, Paul Eggleton wrote: > On Fri, 29 Apr 2016 08:06:16 Gary Thomas wrote: >> On 2016-04-29 07:08, Paul Eggleton wrote: >>> On Fri, 29 Apr 2016 06:24:55 Gary Thomas wrote: >>>> I used to be able to use something like this: >>>> VARIABLE = "xyz" >>>> >>>> and maybe in a .bbappend use >>>> >>>> VARIABLE_mymachine = "xyzzy" >>>> >>>> where 'mymachine' is in OVERRIDES, which resulted in >>>> >>>> VARIABLE = "xyzzy" >>>> >>>> This doesn't seem to work the same today, what I get is >>>> >>>> VARIABLE = "xyz" >>>> VARIABLE_mymachine = "xyzzy" >>>> >>>> Has this changed (recently)? Why? How to I make use of overrides? >>>> >>>> Note: I'm using the latest Poky master (a9b503b26) updated 2016-04-28 >>> >>> When you say this is what you're seeing, how are you checking this? >>> bitbake -e ? Which part of that output are you looking at? >>> >>> You *will* now see VARIABLE_mymachine in bitbake -e output even if >>> "mymachine" is in OVERRIDES - that's because the overridden values stay >>> in the datastore instead of a "finalisation" step eliminating them, in >>> order to allow OVERRIDES to be changed dynamically (possibly multiple >>> times) and still get the datastore contents you expect. That change was >>> made in the 2.0 release (jethro). However That should not affect the >>> final value of VARIABLE if "mymachine" is in OVERRIDES however. Are you >>> sure you are seeing what you think you're seeing? If so, is the bbappend >>> in fact being applied? Because if what you describe was really happening >>> then pretty much the entire system would be broken. I just checked a >>> similar case here and I see the expected results. >> >> Yes, I am using 'bitbake -e | grep ^VARIABLE' to look at this. >> >> In my main recipe, I have this: >> SOME_OTHER_VARIABLE ?= "${MACHINE}" >> and my .bbappend for that recipe has these lines: >> SOME_OTHER_VARIABLE_my-target-A = "something-else1" >> SOME_OTHER_VARIABLE_my-target-B = "something-else2" >> and local.conf has >> MACHINE="my-target-B" >> >> With Yocto 2.0 (Poky ceeb52a2544) I get this: >> SOME_OTHER_VARIABLE = "something-else2" >> SOME_OTHER_VARIABLE_my-target-A = "something-else1" >> SOME_OTHER_VARIABLE_my-target-B = "something-else2" >> >> With today's (Poky a9b503b26) I get this: >> SOME_OTHER_VARIABLE = "my-target-B" >> SOME_OTHER_VARIABLE_my-target-A = "something-else1" >> SOME_OTHER_VARIABLE_my-target-B = "something-else2" >> >> I also use this mechanism to set COMPATIBLE_MACHINE a lot and >> that doesn't seem to be working the same either. >> >> Am I doing something incorrectly (and just got away with it for years)? >> >> n.b. If you're interested, I can share the .bb/.bbappend files >> with you privately (I can't put them on the public list) > > Ah, one thing... do your machine names have uppercase characters in them (as > your pseudo-examples above do)? If so that was a 2.1 change; anything that is > to be used as an override must now be lower case (so DISTRO, MACHINE, etc.) Indeed, my machine names do have an upper case letter in them. Any suggestions for how to handle this (short of renaming everything which would be a HUGE chore)? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------