From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
yocto <yocto@yoctoproject.org>
Subject: Re: Undefining a variable in a recipe?
Date: Fri, 02 May 2014 15:08:54 +0100 [thread overview]
Message-ID: <5363A6F6.5040507@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAP9ODKpg3+SyhU9+KPqPgUyKSGb1pU2_601cK8eq1-b-KG_Hcg@mail.gmail.com>
On 02/05/2014 14:25, Otavio Salvador wrote:
> On Fri, May 2, 2014 at 10:23 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Fri, May 2, 2014 at 10:11 AM, Alex J Lennon
>> <ajlennon@dynamicdevices.co.uk> wrote:
>>> Or indeed, would be not be reasonable to modify the uboot-config.bbclass
>>> such that
>>> it tested for and discarded empty strings in UBOOT_MACHINE / UBOOT_CONFIG
>>> which would seem to be a more complete test and would eliminate the
>>> problem ?
>> Like: http://privatepaste.com/8046479967
> Fixed: http://privatepaste.com/3ffec754d4
>
Otavio, thanks for that. Python is not my métier and I had assumed that
the check on 'if ubootmachine' and so forth would check for definition
rather than be a check on a zero length string.
However given Paul's pointer on Python I've revisited this,
"if len(x) > 0", "if len(x)", and "if x" are all equivalent tests for empty strings in Python"
I had tried setting UBOOT_CONFIG = "" and UBOOT_MACHINE = "" as that's
what I saw used in the getVar(). This which didn't work for me, and I
wrongly assuming this was because of the test.
If instead I set the appended machine type, e.g.
UBOOT_MACHINE_im6qsabresd = "", then that works (!) I guess it's being
copied across somewhere.
So thanks again for the advice. I think we've cracked it :)
Cheers,
Alex
next prev parent reply other threads:[~2014-05-02 14:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 9:42 Undefining a variable in a recipe? Alex J Lennon
2014-05-01 13:54 ` Paul Eggleton
2014-05-01 17:34 ` Alex J Lennon
2014-05-01 17:54 ` Otavio Salvador
2014-05-01 18:34 ` Alex J Lennon
2014-05-02 5:24 ` Alex J Lennon
2014-05-02 12:56 ` Otavio Salvador
2014-05-02 13:01 ` Alex J Lennon
2014-05-02 13:07 ` Otavio Salvador
2014-05-02 13:11 ` Alex J Lennon
2014-05-02 13:23 ` Otavio Salvador
2014-05-02 13:25 ` Otavio Salvador
2014-05-02 14:08 ` Alex J Lennon [this message]
2014-05-02 15:24 ` Otavio Salvador
2014-05-02 15:46 ` Alex J Lennon
2014-05-02 16:55 ` Otavio Salvador
2014-05-02 17:18 ` Alex J Lennon
2014-05-02 13:28 ` Paul Eggleton
2014-05-02 13:35 ` Alex J Lennon
2014-05-02 13:45 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5363A6F6.5040507@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.