From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Yocto <yocto@yoctoproject.org>
Subject: Undefining a variable in a recipe?
Date: Thu, 01 May 2014 10:42:51 +0100 [thread overview]
Message-ID: <5362171B.8010000@dynamicdevices.co.uk> (raw)
Hi,
I have an issue with the build of an old u-boot (2009.08) which is
failing a check in poky as both UBOOT_CONFIG and UBOOT_MACHINE are being
defined for some reason.
poky/meta/classes/uboot-config.bbclass
ubootmachine = d.getVar("UBOOT_MACHINE", True)
ubootconfigflags = d.getVarFlags('UBOOT_CONFIG')
..
if ubootmachine and ubootconfigflags:
raise bb.parse.SkipPackage("You cannot use UBOOT_MACHINE and
UBOOT_CONFIG at the same time.")
I have a .bbappend on the original u-boot recipe and could solve the
problem by undefining UBOOT_MACHINE if I could work out how to do this
in the .bbappend
I've tried setting it to None or an empty string, and I tried an
anonymous python function but those approaches didn't help,
e.g. (in the .bbappend
UBOOT_MACHINE = ""
or
UBOOT_MACHINE = None
or
python __anonymous () {
bb.data.delVar('UBOOT_MACHINE_imx6qsabresd')
}
I could just copy the original recipe from metal-fsl-arm into my own
layer and change it there I guess but I'd like to understand how to
achieve this with a .bbappend if it is possible as it seems cleaner.
Many thanks,
Alex
next reply other threads:[~2014-05-01 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 9:42 Alex J Lennon [this message]
2014-05-01 13:54 ` Undefining a variable in a recipe? 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
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=5362171B.8010000@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--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.