From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B35D1E0091F; Sun, 30 Nov 2014 22:45:00 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,UC_GIBBERISH_OBFU autolearn=no version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.0 UC_GIBBERISH_OBFU Multiple instances of "word VERYLONGGIBBERISH * word" Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9A802E00837 for ; Sun, 30 Nov 2014 22:44:51 -0800 (PST) Received: from [192.168.1.10] (unknown [68.38.40.177]) by smtp.webfaction.com (Postfix) with ESMTP id 30DF159A3A50 for ; Mon, 1 Dec 2014 06:44:51 +0000 (UTC) Message-ID: <547C0E61.3000900@mindchasers.com> Date: Mon, 01 Dec 2014 01:44:49 -0500 From: Bob Cochran User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "meta-freescale@yoctoproject.org" Subject: meta-fsl-ppc: question on the use of appending MACHINEOVERRIDES instead of prepending... X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 06:45:00 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, It's fairly common to see the use of file overrides in meta-fsl-ppc bbappend files so a customized conf file can get picked up during a build. In the paths below, qoriq-ppc is a MACHINEOVERRIDE: ./recipes-core/init-ifupdown/init-ifupdown/qoriq-ppc ./recipes-core/udev/udev-extraconf/qoriq-ppc ./virtualization-layer/recipes-extended/libvirt/libvirt/qoriq-ppc FILESPATH is built using FILESOVERRIDES, and FILESOVERIDES is constructed as follows: "${TRANSLATED_TARGET_ARCH}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}" Overrides are applied from right to left when constructing FILESPATH; therefore, overrides to the right have higher precedence. In various meta-fsl-ppc conf/*.inc files, MACHINEOVERRIDES are added using appends, which sets the override to the right of the MACHINE being built, which was set in local.conf. In my case (where t1040rdb-64b is my MACHINE): FILESOVERRIDES="powerpc64:t1:t1040:t1040rdb-64b:qoriq-ppc:e5500-64b:poky" Therefore, if I put a file under ./recipes-core/init-ifupdown/init-ifupdown/t1040rdb-64b, it will be searched after ./recipes-core/init-ifupdown/init-ifupdown/qoriq-ppc or not at all. Also, a file under e5500-64b will be found before the same file under qoriq-ppc. I don't think this is what we want, since a less specific folder is being picked up before a more specific folder. Please let me know if I'm wrong about something here. If not, can we make a change? Thanks, Bob