From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/6] Add new IMAGE_CLASSES variable for classes for image generation
Date: Thu, 06 Oct 2011 00:53:22 +0100 [thread overview]
Message-ID: <1317858811.6398.36.camel@ted> (raw)
In-Reply-To: <CAEsOVNeNerChRP+bA8D354J2M+og5TPkWO9e_83rNLLbRZS4Jw@mail.gmail.com>
On Wed, 2011-10-05 at 22:52 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Oct 4, 2011 at 5:03 PM, Matthew McClintock <msm@freescale.com> wrote:
> > -inherit image_types
> > +IMAGE_CLASESS ??= ""
> > +inherit image_types ${IMAGE_CLASSES}
>
> So this does not work properly, I thought I tested it but... need to
> do something like this:
>
> IMAGE_CLASSES = "image_types"
> inherit ${IMAGE_CLASSES}
>
> then let the user added via
>
> IMAGE_CLASESS += "image_types_uboot"
>
> then there will always be something that is expanded to avoid this issue:
>
> ERROR: Could not inherit file classes/$IMAGE_CLASSES.bbclass
> | ETA: --:--:--
> ERROR: Command execution failed: Exited with 1
Its not expanding the variables? :/ This happened even when
IMAGE_CLASSES had a value before the inherit?
> or
>
> ERROR: Could not inherit file classes/.bbclass
> | ETA: --:--:--
> ERROR: Command execution failed: Exited with 1
I'd be prepared to call this last one a bitbake bug...
Cheers,
Richard
next prev parent reply other threads:[~2011-10-05 23:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 22:03 [PATCH 1/6] Fix mdadm for powerpc64 Matthew McClintock
2011-10-04 22:03 ` [PATCH 2/6] Fix perl for powerpc64 build Matthew McClintock
2011-10-05 11:46 ` Richard Purdie
2011-10-05 19:04 ` McClintock Matthew-B29882
2011-10-07 15:52 ` Richard Purdie
2011-10-07 16:07 ` McClintock Matthew-B29882
2011-10-04 22:03 ` [PATCH 3/6] Add new IMAGE_CLASSES variable for classes for image generation Matthew McClintock
2011-10-05 22:52 ` McClintock Matthew-B29882
2011-10-05 23:53 ` Richard Purdie [this message]
2011-10-06 0:25 ` McClintock Matthew-B29882
2011-10-11 16:44 ` McClintock Matthew-B29882
2011-10-04 22:03 ` [PATCH 4/6] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE Matthew McClintock
2011-10-05 13:25 ` Richard Purdie
2011-10-04 22:03 ` [PATCH 5/6] Fix sysprof for powerpc64 Matthew McClintock
2011-10-05 0:05 ` Khem Raj
2011-10-05 6:44 ` McClintock Matthew-B29882
2011-10-05 11:35 ` Richard Purdie
2011-10-05 16:46 ` Khem Raj
2011-10-05 16:48 ` McClintock Matthew-B29882
2011-10-05 17:06 ` Khem Raj
2011-10-05 17:10 ` Saul Wold
2011-10-05 18:30 ` Phil Blundell
2011-10-05 18:41 ` McClintock Matthew-B29882
2011-10-05 19:13 ` Khem Raj
2011-10-04 22:03 ` [PATCH 6/6] Bring libnl up to date with meta-openebedded Matthew McClintock
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=1317858811.6398.36.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.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.