From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] insane: add checking to standardize how .bbappend files do FILESEXTRAPATHS
Date: Fri, 25 Jul 2014 11:25:32 -0600 [thread overview]
Message-ID: <53D2930C.8090709@mlbassoc.com> (raw)
In-Reply-To: <d36bfea1e3c7402098ff8913d473900c8b11eb71.1406085105.git.hongxu.jia@windriver.com>
On 2014-07-22 21:33, Hongxu Jia wrote:
> When adding patches or config files from bbappend files, it requires
> the use of FILESEXTRAPATHS, which has been an issue and failure point
> for people starting to work with bitbake and oe-core.
>
> We add checking to standardize how to use FILESEXTRAPATHS. Only the
> format of:
> FILESEXTRAPATHS_append := ":${THISDIR}/Your_Files_Path" or
> FILESEXTRAPATHS_prepend := "${THISDIR}/Your_Files_Path:"
> is acceptable.
>
> [YOCTO #5412]
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/classes/insane.bbclass | 13 +++++++++++++
> meta/classes/utils.bbclass | 2 ++
> meta/conf/bitbake.conf | 2 ++
> 3 files changed, 17 insertions(+)
>
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index b26216e..6b1c9ad 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -1022,6 +1022,19 @@ python () {
> # Check various variables
> ###########################################################################
>
> + # Checking ${FILESEXTRAPATHS}
> + extrapaths = (d.getVar("FILESEXTRAPATHS", True) or "")
> + if '__default' not in extrapaths.split(":"):
> + msg = "FILESEXTRAPATHS-variable, must always use _prepend (or _append)\n"
> + msg += "type of assignment, and don't forget the colon.\n"
> + msg += "Please assign it with the format of:\n"
> + msg += " FILESEXTRAPATHS_append := \":${THISDIR}/Your_Files_Path\" or\n"
> + msg += " FILESEXTRAPATHS_prepend := \"${THISDIR}/Your_Files_Path:\"\n"
> + msg += "in your bbappend file\n\n"
> + msg += "Your incorrect assignment is:\n"
> + msg += "%s\n" % extrapaths
> + bb.fatal(msg)
It sure would have been nice (even polite?) to make this a warning when first
added. As is, it's going to break a lot of builds and it will be very tedious
to fix since the parser will die on the first one it finds :-(
> +
> if d.getVar('do_stage', True) is not None:
> bb.fatal("Legacy staging found for %s as it has a do_stage function. This will need conversion to a do_install or often simply removal to work with OE-core" % d.getVar("FILE", True))
>
> diff --git a/meta/classes/utils.bbclass b/meta/classes/utils.bbclass
> index 0ee13e0..0f2a484 100644
> --- a/meta/classes/utils.bbclass
> +++ b/meta/classes/utils.bbclass
> @@ -312,6 +312,8 @@ def explode_deps(s):
> def base_set_filespath(path, d):
> filespath = []
> extrapaths = (d.getVar("FILESEXTRAPATHS", True) or "")
> + # Remove default flag which was used for checking
> + extrapaths = extrapaths.replace("__default:", "")
> # Don't prepend empty strings to the path list
> if extrapaths != "":
> path = extrapaths.split(":") + path
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index f4870d5..6a0cf7a 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -311,6 +311,8 @@ FILES_${PN}-locale = "${datadir}/locale"
> FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE'))}"
> # FILESPATH is set in base.bbclass
> #FILESPATH = "${FILE_DIRNAME}/${PF}:${FILE_DIRNAME}/${P}:${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/${BP}:${FILE_DIRNAME}/${BPN}:${FILE_DIRNAME}/files:${FILE_DIRNAME}"
> +# This default was only used for checking
> +FILESEXTRAPATHS ?= "__default:"
>
> ##################################################################
> # General work and output directories for the build system.
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-07-25 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 3:33 [PATCH V3 0/1] insane: add checking to standardize how .bbappend files do FILESEXTRAPATHS Hongxu Jia
2014-07-23 3:33 ` [PATCH 1/1] " Hongxu Jia
2014-07-25 17:25 ` Gary Thomas [this message]
2014-07-25 18:35 ` Richard Purdie
2014-07-25 19:02 ` Gary Thomas
2014-07-25 8:22 ` [PATCH V3 0/1] " Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-07-21 6:17 [PATCH V2 " Hongxu Jia
2014-07-21 6:17 ` [PATCH 1/1] " Hongxu Jia
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=53D2930C.8090709@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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.