Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kevin Tian <kevin.tian@intel.com>
Cc: paul.eggleton@linux.intel.com, poky@pokylinux.org
Subject: Re: [PATCH 2/3] kernel.bbclass: rename do_deploy and add vardepsexclusive accordingly
Date: Thu, 16 Dec 2010 15:29:17 +0000	[thread overview]
Message-ID: <1292513357.26558.4007.camel@rex> (raw)
In-Reply-To: <0d30dc$kfrh4k@orsmga001.jf.intel.com>

On Thu, 2010-12-16 at 16:56 +0800, Kevin Tian wrote:
> rename do_deploy to kernel_do_deploy and export it. Then add exclusive
> list for two variables it refers to:
> 
> +kernel_do_deploy[vardepsexclude] = "DATETIME"
> +KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"
> 
> This avoids the last road block linux-yocto for sstate.

Shouldn't this just need only the 

KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"

change?

Cheers,

Richard

> Signed-off-by: Kevin Tian <kevin.tian@intel.com>
> ---
>  meta/classes/kernel.bbclass |    4 +++-
>  meta/conf/distro/poky.conf  |    2 ++
>  2 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index bb76285..341809a 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -474,7 +474,7 @@ addtask sizecheck before do_install after do_compile
>  KERNEL_IMAGE_BASE_NAME ?= "${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}-${DATETIME}"
>  KERNEL_IMAGE_SYMLINK_NAME ?= "${KERNEL_IMAGETYPE}-${MACHINE}"
>  
> -do_deploy() {
> +kernel_do_deploy() {
>  	install -m 0644 arch/${ARCH}/boot/${KERNEL_IMAGETYPE} ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
>  	if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
>  		tar -cvzf ${DEPLOYDIR}/modules-${KERNEL_VERSION}-${PR}-${MACHINE}.tgz -C ${D} lib
> @@ -504,6 +504,8 @@ do_deploy[dirs] = "${DEPLOYDIR} ${B}"
>  
>  addtask deploy before do_package after do_install
>  
> +EXPORT_FUNCTIONS do_deploy
> +
>  # perf must be enabled in individual kernel recipes
>  PACKAGES =+ "perf"
>  FILES_perf = "${bindir}/* \
> diff --git a/meta/conf/distro/poky.conf b/meta/conf/distro/poky.conf
> index 95ca097..735e0c0 100644
> --- a/meta/conf/distro/poky.conf
> +++ b/meta/conf/distro/poky.conf
> @@ -145,3 +145,5 @@ BB_SIGNATURE_HANDLER = "basic"
>  BB_HASHTASK_WHITELIST = "(.*-cross$|.*-native$|.*-cross-initial$|.*-cross-intermediate$|^virtual:native:.*|^virtual:nativesdk:.*)"
>  BB_HASHBASE_WHITELIST = "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL TERM USER"
>  patch_do_patch[vardepsexclude] = "DATE SRCDATE"
> +kernel_do_deploy[vardepsexclude] = "DATETIME"
> +KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"




  reply	other threads:[~2010-12-16 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  8:56 [PATCH 2/3] kernel.bbclass: rename do_deploy and add vardepsexclusive accordingly Kevin Tian
2010-12-16 15:29 ` Richard Purdie [this message]
2010-12-17  1:01   ` Tian, Kevin
2010-12-16 15:39 ` Richard Purdie
2010-12-17  1:02   ` Tian, Kevin

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=1292513357.26558.4007.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kevin.tian@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@pokylinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox