From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id DE167E00DE6; Thu, 24 Sep 2015 08:45:26 -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,HTML_MESSAGE 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] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from lnsystems.lincoln.ln-systems.com (post.ln-systems.com [62.49.123.66]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 526A0E00708 for ; Thu, 24 Sep 2015 08:45:20 -0700 (PDT) Received: from LNSYSCH2 (firewall-ext.lincoln.ln-systems.com [62.49.123.65]) by lnsystems.lincoln.ln-systems.com (8.13.1/8.13.1) with ESMTP id t8OFgRjr012520 for ; Thu, 24 Sep 2015 16:42:30 +0100 From: "Colin Helliwell" To: Date: Thu, 24 Sep 2015 16:45:15 +0100 Organization: LN Systems Limited Message-ID: <027601d0f6e0$03e682d0$0bb38870$@LN-Systems.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdD2wnoeheQTZ4rQQe+romr9DeWwCQ== Subject: Getting bitbake to use 'local' versions of local.conf/bblayers.conf X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: colin.helliwell@LN-Systems.com List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 15:45:26 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0277_01D0F6E8.65AAEAD0" Content-Language: en-gb ------=_NextPart_000_0277_01D0F6E8.65AAEAD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit We have an automated build which pulls our own layers & amendments from our version control system. We don't really want (need?) to have a full *unpacked* Yocto in the repository too, so we have just the Fido tarball in there, and unpack this as the first step of the build. But, we then need to copy our local.conf and bblayers.conf across into the (transient) build directory. Is there a way to tell bitbake to override the default ones (in build/local/) with ours? I did see that it's maybe possible to set up variables for the 'oe-init-build-env' script, but I think this will still copy them into build/local/ - what we want is to leave them in place (so if we make any changes they will remain under, and trackable by, the version control) ------=_NextPart_000_0277_01D0F6E8.65AAEAD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We have an = automated build which pulls our own layers & amendments from our = version control system. We don’t really want (need?) to have a = full *unpacked* Yocto in the repository too, so we have just the Fido = tarball in there, and unpack this as the first step of the = build.

But, we then need to copy our = local.conf and bblayers.conf across into the (transient) build = directory. Is there a way to tell bitbake to override the default ones = (in build/local/) with ours?  I did see that it’s maybe = possible to set up variables for the ‘oe-init-build-env’ = script, but I think this will still copy them into build/local/  - = what we want is to leave them in place (so if we make any changes they = will remain under, and trackable by, the version = control)

 

------=_NextPart_000_0277_01D0F6E8.65AAEAD0--