All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Pixley <rich.pixley@palm.com>
To: "openembedded-devel@openembedded.org"
	<openembedded-devel@openembedded.org>
Subject: Re: bitbake vs incremental builds
Date: Thu, 19 Jun 2008 18:03:08 -0700	[thread overview]
Message-ID: <485B01CC.3000701@palm.com> (raw)
In-Reply-To: <1213862302.5018.2.camel@dax.rpnet.com>

Richard Purdie wrote:
> It wasn't done for a long time simply because nobody had taken the time
> to implement it. It has however recently been implemented, simply set:
>
> BB_STAMP_POLICY = "full"
> or
> BB_STAMP_POLICY = "whitelist"
>
> Whitelist allows you to exempt certain packages from stamp checking, see
> packaged-staging.bbclass for an example.
This isn't working for me simply by taking a top of tree bitbake and 
shoving it into my environment.  However, my OE environment is over a 
year old and is moderately hacked locally.

I tried to write a trivial test case, but I got bogged down.  It's not 
at all clear to me what one would need to do to use bitbake in some 
environment other than OE.  I was hoping it would be simple to just 
write an empty conf/bitbake.conf and a couple of a.bb and b.bb files 
with a depending on b, but 2hrs later I'm still confused.

So this isn't working for me and I don't see an easy way to debug it.  
Any suggestions?

--rich



  parent reply	other threads:[~2008-06-20  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 22:40 bitbake vs incremental builds Rich Pixley
2008-06-19  7:58 ` Richard Purdie
2008-06-19 16:57   ` K. Richard Pixley
2008-06-19 17:30     ` Cliff Brake
2008-06-20  1:03   ` Rich Pixley [this message]
2008-06-20  9:44     ` Richard Purdie
2008-06-23 18:23       ` Rich Pixley
2008-06-25 22:28   ` Rich Pixley
2008-06-26 20:53     ` rebuild confusion Rich Pixley

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=485B01CC.3000701@palm.com \
    --to=rich.pixley@palm.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.