public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bootimg/image: Enhance bootimg to respect RM_OLD_IMAGE
Date: Sat, 30 Jan 2016 10:54:50 +0000	[thread overview]
Message-ID: <1454151290.10340.82.camel@linuxfoundation.org> (raw)
In-Reply-To: <1454117651.22677.6.camel@ranerica-desk01>

On Fri, 2016-01-29 at 17:34 -0800, Ricardo Neri wrote:
> [Resending from an email subscribed to the oe list...]
> On Sun, 2016-01-17 at 11:16 +0000, Richard Purdie wrote:
> > @@ -294,7 +286,10 @@ python do_bootimg() {
> >          bb.build.exec_func('build_efi_cfg', d)
> >      bb.build.exec_func('build_hddimg', d)
> >      bb.build.exec_func('build_iso', d)
> > +    bb.build.exec_func('create_symlinks', d)
> When I try to use bootimg.bbclass I get the following warning:
> 
> WARNING: Function create_symlinks doesn't exist
> 
> This is because create_symlinks is defined in image.bbclass but
> bootimg.bbclass does not inherit from it. Should it be the case? Or
> the
> definiton of create_symlinks should be moved to a separate file?

I guess the key question is whether anyone is using bootimg.bbclass
without using image.bbclass, or whether that is even
possible/practical?

Was this an existing setup that broke?

Cheers,

Richard


  reply	other threads:[~2016-01-30 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 11:16 [PATCH] bootimg/image: Enhance bootimg to respect RM_OLD_IMAGE Richard Purdie
2016-01-30  1:34 ` Ricardo Neri
2016-01-30 10:54   ` Richard Purdie [this message]
2016-01-31 20:58     ` Ricardo Neri

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=1454151290.10340.82.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    /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