All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbaking a recipe which refers to a missing bbclass
Date: Sat, 14 Oct 2006 12:07:49 +1000	[thread overview]
Message-ID: <20061014020749.GA6061@twibble.org> (raw)
In-Reply-To: <1160736375.21755.86.camel@gandalf.tm.informatik.uni-frankfurt.de>

On Fri, Oct 13, 2006 at 12:46:15PM +0200, Michael 'Mickey' Lauer wrote:
> Am Dienstag, den 10.10.2006, 15:31 +0200 schrieb Nicolas FR:
> > I have noticed that when bitbaking a recipe which refers to a missing
> > .bbclass definition, there where no warning / error.
> > 
> > For example let's say I try to bitbake example.bb which has:
> > "inherits qt3x11"
> > 
> > if qt3x11 is missing in my /opt/OE/mybranch/classes/
> > then no warning / error is isued.
> 
> This is probably an artifact of the 'inherit' and the 'include'
> statement sharing code.
> I would like to propose 'inherit' to behave like 'require'.

Yep, I'd certainly support that.

In my case I had named my new class "cpan_build.bb" and it took me ages to
figure out why it wouldn't work... should have been .bbclass of course but
I'm just sooo0 used to calling things .bb!

-- 
 Jamie Lenehan <lenehan@twibble.org>



      parent reply	other threads:[~2006-10-14  2:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 13:31 Bitbaking a recipe which refers to a missing bbclass Nicolas FR
2006-10-10 22:06 ` Jamie Lenehan
2006-10-10 22:44   ` Justin Patrin
2006-10-13 10:46 ` Michael 'Mickey' Lauer
2006-10-13 10:53   ` Nicolas FR
2006-10-14  2:07   ` Jamie Lenehan [this message]

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=20061014020749.GA6061@twibble.org \
    --to=lenehan@twibble.org \
    --cc=openembedded-devel@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.