Conf notes

Conf notes

[Laszlo Papp]

Hi,

I have just put a conf notes file into my own layer, but when I source
the oe-init-build-env script, I am still getting the notes from Yocto
rather than my customized.

What am I doing wrong? I see this in the ./scripts/oe-setup-builddir file:

TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}

and other references, but I have not pin the issue down just yet.

Cheers, L.

Re: Conf notes

[Nicolas Dechesne]

On Fri, Feb 21, 2014 at 8:06 PM, Laszlo Papp <lpapp@kde.org> wrote:
>
> I have just put a conf notes file into my own layer, but when I source
> the oe-init-build-env script, I am still getting the notes from Yocto
> rather than my customized.
>
> What am I doing wrong? I see this in the ./scripts/oe-setup-builddir file:
>
> TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}
>
> and other references, but I have not pin the issue down just yet.

are you setting TEMPLATECONF variable? if so, how?

also, if you provide conf-notes.txt you need to provide
local.conf.sample and bblayers.conf.sample.

if TEMPLATECONF is set, it will use these files:

    OECORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"
    OECORELOCALCONF="$TEMPLATECONF/local.conf.sample"
    OECORENOTESCONF="$TEMPLATECONF/conf-notes.txt"

Re: Conf notes

[Laszlo Papp]

On Mon, Feb 24, 2014 at 6:34 AM, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
> On Fri, Feb 21, 2014 at 8:06 PM, Laszlo Papp <lpapp@kde.org> wrote:
>>
>> I have just put a conf notes file into my own layer, but when I source
>> the oe-init-build-env script, I am still getting the notes from Yocto
>> rather than my customized.
>>
>> What am I doing wrong? I see this in the ./scripts/oe-setup-builddir file:
>>
>> TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}
>>
>> and other references, but I have not pin the issue down just yet.
>
> are you setting TEMPLATECONF variable? if so, how?

cat setup.sh
#!/bin/bash

TEMPLATECONF=meta-foo/conf . oe-init-build-env

> also, if you provide conf-notes.txt you need to provide
> local.conf.sample and bblayers.conf.sample.
>
> if TEMPLATECONF is set, it will use these files:
>
>     OECORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"
>     OECORELOCALCONF="$TEMPLATECONF/local.conf.sample"
>     OECORENOTESCONF="$TEMPLATECONF/conf-notes.txt"

ls ./meta-foo/conf/
bblayers.conf.sample  conf-notes.txt  distro  layer.conf
local.conf.sample  site.conf.sample

Re: Conf notes

[Nicolas Dechesne]

On Mon, Feb 24, 2014 at 10:35 AM, Laszlo Papp <lpapp@kde.org> wrote:
>> are you setting TEMPLATECONF variable? if so, how?
>
> cat setup.sh
> #!/bin/bash
>
> TEMPLATECONF=meta-foo/conf . oe-init-build-env

hmm. do you get any error message?

meta-foo needs to be a folder in OEROOT (along with 'meta' folder), or
TEMPLATECONF can be an absolute path otherwise, as you can see from
this code snippet (from oe-setup-builddir)

    if ! (test -d "$TEMPLATECONF"); then
    # Allow TEMPLATECONF=meta-xyz/conf as a shortcut
    if [ -d "$OEROOT/$TEMPLATECONF" ]; then
        TEMPLATECONF="$OEROOT/$TEMPLATECONF"
    fi

Re: Conf notes

[Laszlo Papp]

On Mon, Feb 24, 2014 at 10:28 AM, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
> On Mon, Feb 24, 2014 at 10:35 AM, Laszlo Papp <lpapp@kde.org> wrote:
>>> are you setting TEMPLATECONF variable? if so, how?
>>
>> cat setup.sh
>> #!/bin/bash
>>
>> TEMPLATECONF=meta-foo/conf . oe-init-build-env
>
> hmm. do you get any error message?

Nope, I have been using this construction for several weeks now. The
local and bblayer samples have been extracted properly into the build
folder, so in that sense, there is no infrastructural change
introduced in here, just yet another file added in the folder.

> meta-foo needs to be a folder in OEROOT (along with 'meta' folder), or
> TEMPLATECONF can be an absolute path otherwise, as you can see from
> this code snippet (from oe-setup-builddir)

Yes, meta-foo is beside meta.

Re: Conf notes

[Nicolas Dechesne]

On Mon, Feb 24, 2014 at 12:47 PM, Laszlo Papp <lpapp@kde.org> wrote:
>> hmm. do you get any error message?
>
> Nope, I have been using this construction for several weeks now. The
> local and bblayer samples have been extracted properly into the build
> folder, so in that sense, there is no infrastructural change
> introduced in here, just yet another file added in the folder.

well, i don't see what can possibly go wrong then... especially if
layers.conf.sample and bblayer sample files work fine... maybe adding
"set -x" in the script would reveal something..

nico

Re: Conf notes

[Laszlo Papp]

On Mon, Feb 24, 2014 at 12:49 PM, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
> On Mon, Feb 24, 2014 at 12:47 PM, Laszlo Papp <lpapp@kde.org> wrote:
>>> hmm. do you get any error message?
>>
>> Nope, I have been using this construction for several weeks now. The
>> local and bblayer samples have been extracted properly into the build
>> folder, so in that sense, there is no infrastructural change
>> introduced in here, just yet another file added in the folder.
>
> well, i don't see what can possibly go wrong then... especially if
> layers.conf.sample and bblayer sample files work fine... maybe adding
> "set -x" in the script would reveal something..

1) I use dylan if that matters.

2) cat ../meta-foo/conf/conf-notes.txt
Common targets are:
    core-image-minimal
    foo

You can also run generated qemu images with a command like 'runqemu qemux86'

3) set -x output

++ TEMPLATECONF=meta-foo/conf
++ . oe-init-build-env
+++ '[' -z '' ']'
+++ '[' xbash = x./oe-init-build-env ']'
+++ '[' -n oe-init-build-env ']'
++++ dirname oe-init-build-env
+++ OEROOT=.
++++ readlink -f .
+++ OEROOT=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1
+++ export OEROOT
+++ . /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts/oe-buildenv-internal
++++ '[' -z /home/lpapp/Projects/Yocto/poky-dylan-9.0.1 ']'
++++ '[' x = x ']'
++++ '[' x = x ']'
++++ BDIR=build
++++ expr build : '/.*'
+++++ pwd
++++ BUILDDIR=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build
++++ unset BDIR
++++ BITBAKEDIR=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/
+++++ readlink -f /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/
++++ BITBAKEDIR=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake
+++++ readlink -f /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build
++++ BUILDDIR=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build
++++ test -d /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake
++++ PATH=/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/bin/:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/bin/:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/bin/:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/bin/:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts:/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/bitbake/bin/:/usr/lib/colorgcc/bin/:/home/lpapp/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
++++ unset BITBAKEDIR
++++ export BUILDDIR
++++ export PATH
++++ export 'BB_ENV_EXTRAWHITE=MACHINE DISTRO TCMODE TCLIBC http_proxy
ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID
SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS
PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD
SOCKS5_USER'
++++ BB_ENV_EXTRAWHITE='MACHINE DISTRO TCMODE TCLIBC http_proxy
ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID
SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS
PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD
SOCKS5_USER'
+++ /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/scripts/oe-setup-builddir
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a
different MACHINE (target hardware) or enable parallel build options to take
advantage of multiple cores for example. See the file for more information as
common configuration options are commented.

The Yocto Project has extensive documentation about OE including a
reference manual
which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/

You had no conf/bblayers.conf file. The configuration file has been created for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

The Yocto Project has extensive documentation about OE including a
reference manual
which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/



### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-toolchain-sdk
    adt-installer
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

+++ '[' -n /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build ']'
+++ cd /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build
+++ unset OEROOT
+++ unset BBPATH
++ printf '\033_%s@%s:%s\033\' lpapp wheezy
'~/Projects/Yocto/poky-dylan-9.0.1/build'

Re: Conf notes

[Gary Thomas]

On 2014-02-24 05:49, Nicolas Dechesne wrote:
> On Mon, Feb 24, 2014 at 12:47 PM, Laszlo Papp <lpapp@kde.org> wrote:
>>> hmm. do you get any error message?
>>
>> Nope, I have been using this construction for several weeks now. The
>> local and bblayer samples have been extracted properly into the build
>> folder, so in that sense, there is no infrastructural change
>> introduced in here, just yet another file added in the folder.
> 
> well, i don't see what can possibly go wrong then... especially if
> layers.conf.sample and bblayer sample files work fine... maybe adding
> "set -x" in the script would reveal something..

I just tried this with the latest master and it is only looking in
the meta-yocto layer even though there is a conf-notes.txt in one of
my local layers as well.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Conf notes

[Nicolas Dechesne]

On Mon, Feb 24, 2014 at 2:15 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> I just tried this with the latest master and it is only looking in
> the meta-yocto layer even though there is a conf-notes.txt in one of
> my local layers as well.

hmm. i just tried too. i create meta-layer with:

$ find meta-mylayer/
meta-mylayer/
meta-mylayer/conf
meta-mylayer/conf/conf-notes.txt
meta-mylayer/conf/bblayers.conf.sample
meta-mylayer/conf/layer.conf
meta-mylayer/conf/local.conf.sample
meta-mylayer/conf/site.conf.sample

then, if I run

$ TEMPLATECONF=meta-mylayer/conf . oe-init-build-env bbb

It is working fine:

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
       my-custom-image

You can also run generated qemu images with a command like 'runqemu qemux86'

I tried with up-to-date poky, e.g.

commit a1faa7df2a0972fa631d3aee98c59f6b0e8eb43c
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Mon Feb 24 12:57:38 2014 +0000

Re: Conf notes

[Gary Thomas]

On 2014-02-24 06:40, Nicolas Dechesne wrote:
> On Mon, Feb 24, 2014 at 2:15 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I just tried this with the latest master and it is only looking in
>> the meta-yocto layer even though there is a conf-notes.txt in one of
>> my local layers as well.
> 
> hmm. i just tried too. i create meta-layer with:
> 
> $ find meta-mylayer/
> meta-mylayer/
> meta-mylayer/conf
> meta-mylayer/conf/conf-notes.txt
> meta-mylayer/conf/bblayers.conf.sample
> meta-mylayer/conf/layer.conf
> meta-mylayer/conf/local.conf.sample
> meta-mylayer/conf/site.conf.sample
> 
> then, if I run
> 
> $ TEMPLATECONF=meta-mylayer/conf . oe-init-build-env bbb
> 
> It is working fine:

Indeed, that does work, but only for the first time of if you specify TEMPLATECONF.

I often have build trees that live for a very long time (think months) and I'll
do something like this:
  TEMPLATECONF=my-layer/conf . ${POKY}/oe-init-build-env <somedir>
then later, e.g. after a reboot of my build host, I do just this:
  . ${POKY}/oe-init-build-env <somedir>
This renews the build setting for that setup just fine, but in this case, I'll
get the default "conf-notes.txt", not my layer specific ones.

> 
> ### Shell environment set up for builds. ###
> 
> You can now run 'bitbake <target>'
> 
> Common targets are:
>        my-custom-image
> 
> You can also run generated qemu images with a command like 'runqemu qemux86'
> 
> I tried with up-to-date poky, e.g.
> 
> commit a1faa7df2a0972fa631d3aee98c59f6b0e8eb43c
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Mon Feb 24 12:57:38 2014 +0000
> 

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Conf notes

[Laszlo Papp]

On Mon, Feb 24, 2014 at 1:40 PM, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
> On Mon, Feb 24, 2014 at 2:15 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I just tried this with the latest master and it is only looking in
>> the meta-yocto layer even though there is a conf-notes.txt in one of
>> my local layers as well.
>
> hmm. i just tried too. i create meta-layer with:
>
> $ find meta-mylayer/
> meta-mylayer/
> meta-mylayer/conf
> meta-mylayer/conf/conf-notes.txt
> meta-mylayer/conf/bblayers.conf.sample
> meta-mylayer/conf/layer.conf
> meta-mylayer/conf/local.conf.sample
> meta-mylayer/conf/site.conf.sample
>
> then, if I run
>
> $ TEMPLATECONF=meta-mylayer/conf . oe-init-build-env bbb
>
> It is working fine:
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake <target>'
>
> Common targets are:
>        my-custom-image
>
> You can also run generated qemu images with a command like 'runqemu qemux86'
>
> I tried with up-to-date poky, e.g.
>
> commit a1faa7df2a0972fa631d3aee98c59f6b0e8eb43c
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Mon Feb 24 12:57:38 2014 +0000

It works with dylan, too?

Re: Conf notes

[Nicolas Dechesne]

On Mon, Feb 24, 2014 at 3:09 PM, Laszlo Papp <lpapp@kde.org> wrote:
> It works with dylan, too?

yep. same output using:

commit e2bb4a70a99a057d45316bbac65d6044ea54c484
Author: Chen Qi <Qi.Chen@windriver.com>
Date:   Sat Nov 16 03:19:55 2013 +0000

    subversion: fix build problem when sysroot contains '-D' or '-I'

Re: Conf notes

[Nicolas Dechesne]

On Mon, Feb 24, 2014 at 2:50 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> It is working fine:
>
> Indeed, that does work, but only for the first time of if you specify TEMPLATECONF.
>
> I often have build trees that live for a very long time (think months) and I'll
> do something like this:
>   TEMPLATECONF=my-layer/conf . ${POKY}/oe-init-build-env <somedir>
> then later, e.g. after a reboot of my build host, I do just this:
>   . ${POKY}/oe-init-build-env <somedir>
> This renews the build setting for that setup just fine, but in this case, I'll
> get the default "conf-notes.txt", not my layer specific ones.

right, this is expected. TEMPLATECONF needs to be set each time you
source the init scripts.

Re: Conf notes

[Laszlo Papp]

On Mon, Feb 24, 2014 at 2:13 PM, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
> On Mon, Feb 24, 2014 at 3:09 PM, Laszlo Papp <lpapp@kde.org> wrote:
>> It works with dylan, too?
>
> yep. same output using:
>
> commit e2bb4a70a99a057d45316bbac65d6044ea54c484
> Author: Chen Qi <Qi.Chen@windriver.com>
> Date:   Sat Nov 16 03:19:55 2013 +0000
>
>     subversion: fix build problem when sysroot contains '-D' or '-I'

Right, we use 9.0.0, so it is not the same. This would be the same:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=dylan-9.0.0

I have tried it now at least 5-10 times, including full build
directory removal. It just does not work.

Fwiw, we do not depend on the yocto layer at all; only core. Not sure
if that matters.

Re: Conf notes

[Laszlo Papp]

Hmm, I think something bizarre happened on my end. It seems that my
file is lacking the `OECORENOTESCONF="$TEMPLATECONF/conf-notes.txt"`
line. That would explain all this, however this is present in dylan,
even in 9.0.0.

It seems to be that it was not present in denzil though. It is
possible that some corruption occurred during the migration from
denzil to dylan for us. I cannot possibly explain it for the moment
because I just decompressed the poky tarball, and I think that was it.
I mean, I would probably recall something silly, but not in this
case... So, my memory is either very bad, or it is something else. I
will let you know if I figure this out.

Thank you for your time and patience.