All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: Correct procedure for rebuilding after a git pull
Date: Wed, 03 Oct 2012 14:37:22 +0100	[thread overview]
Message-ID: <506C3F92.4050309@communistcode.co.uk> (raw)
In-Reply-To: <CANFv2EkD5NtRvbe2-fNnmt8df66HAu2r=hzCMBm-Zw4EeidBHw@mail.gmail.com>

On 03/10/12 14:27, James Abernathy wrote:
>
>
> On Wed, Oct 3, 2012 at 9:21 AM, Burton, Ross <ross.burton@intel.com 
> <mailto:ross.burton@intel.com>>wrote:
>
>     On 3 October 2012 14:05, James Abernathy <jfabernathy@gmail.com
>     <mailto:jfabernathy@gmail.com>> wrote:
>     > Now I see a bunch of patches pushed to Denzil branch and I want
>     to test
>     > them.  My build directory is untouched since the successful
>     build before.
>     > What do I do to rebuild my project to include the latest
>     patches.  I've
>     > tried things like "bitbake -c cleansstate core-image-cdv-media"
>     before the
>     > new "bitbake core-image-cdv-media" and I've tried just rebaking
>     by itself.
>     > Something always fails.  I've learned that to really test I have to
>     > completely delete my build directory saving only my local.conf and
>     > bblayer.conf.
>
>     Just git pull ; bitbake should work -- all of the packages that
>     changed will rebuild without any problems.
>
>     That's the theory, and everyone who works against oe-core/poky master
>     does this ever day (including me).
>
>     Can you give an example of something that fails?
>
>     The most recent patch update to Denzil included some Cedartrail
>     BSP updates to the CDV PVR driver.  I was traveling last week and
>     I was out of date on my poky and meta-intel by at least that
>     long.  Monday was the pull.  So when the rebuild happened, I got a
>     cdv-pvr driver configuration error.  I didn't look into why
>     because of my experience of this taking longer than a complete
>     rebuild.  So I deleted the build directory and did the rebuild. 
>     And I didn't get the error on the rebuild.  Everything still works
>     fine for me on that BSP.
>
> Jim A
>
>     Ross
>
>

I also use this work flow. If something goes wrong with a particular 
package then I will -c cleansstate failed-package and then start the 
build again. This usually fixes it.

Regards,

>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--



  reply	other threads:[~2012-10-03 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 13:05 Correct procedure for rebuilding after a git pull James Abernathy
2012-10-03 13:21 ` Burton, Ross
2012-10-03 13:27   ` James Abernathy
2012-10-03 13:37     ` Jack Mitchell [this message]
2012-10-03 13:37       ` Burton, Ross
2012-10-03 13:42         ` Jack Mitchell
2012-10-03 14:11           ` Khem Raj

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=506C3F92.4050309@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=yocto@yoctoproject.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.