Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake -b busted again?
Date: Wed, 29 Jun 2011 16:07:20 +0100	[thread overview]
Message-ID: <1309360040.2551.56.camel@phil-desktop> (raw)
In-Reply-To: <A0B5F234-A33C-47D6-AD2E-D6E37479333C@dominion.thruhere.net>

On Wed, 2011-06-29 at 16:55 +0200, Koen Kooi wrote:
> Op 29 jun 2011, om 16:54 heeft Phil Blundell het volgende geschreven:
> 
> > On Wed, 2011-06-29 at 15:48 +0100, Phil Blundell wrote:
> >> Using bitbake master from today, I'm now getting this error whenever I
> >> try to do "bitbake -b anything.bb":
> > 
> > Actually, it looks like I was just unlucky/unskilled in my choice of
> > recipes when I tested.  It does in fact work for at least some files;
> > there must be something about the ones I was trying to begin with that
> > is upsetting it.  I'll investigate further.
> 
> Try bitbake -b /full/path/to/recipe, that seems to make things work for me.

It seems that the main problem I was having was that (coincidentally in
light of the earlier gst discussion) the recipe I was trying to build
was unluckily named and being skipped because base.bbclass thought I
wasn't licensed to use it.

The code which detects commerciality is somewhat simple-minded and just
does a straight regex search for ${PN} within ${COMMERCIAL_LICENSE}, so
if your recipe happens to be called "fmp" (for example) it will match
against ffmpeg and you will lose.

I think this has probably just started to bite me because I recently
started using default-distrovars.inc.  Possibly that was a dim plan on
my part.

p.





  reply	other threads:[~2011-06-29 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 14:48 bitbake -b busted again? Phil Blundell
2011-06-29 14:54 ` Phil Blundell
2011-06-29 14:55   ` Koen Kooi
2011-06-29 15:07     ` Phil Blundell [this message]
2011-06-29 15:11       ` Phil Blundell
2011-08-10 10:48         ` Phil Blundell
2011-08-10 13:26           ` Richard Purdie
2011-08-11 11:51             ` Phil Blundell
2011-08-11  6:44           ` Martin Jansa
2011-08-11 12:03             ` Richard Purdie
2011-08-11 12:21               ` Martin Jansa

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=1309360040.2551.56.camel@phil-desktop \
    --to=pb@pbcl.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox