All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Zafrullah Syed <zafrullahmehdi@gmail.com>, yocto@yoctoproject.org
Subject: Re: Hello world-Checksum error
Date: Tue, 04 Jun 2013 14:26:10 +0100	[thread overview]
Message-ID: <62291455.6hREtkkLEB@helios> (raw)
In-Reply-To: <CAAGt+t100v=mrKE4gbJnGqn5ezJADUFwnxdWQ0xzK8SWqyva6g@mail.gmail.com>

On Tuesday 04 June 2013 15:19:49 Zafrullah Syed wrote:
> On Tue, Jun 4, 2013 at 12:58 PM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> > On Tuesday 04 June 2013 12:42:12 Zafrullah Syed wrote:
> > > previously, I successfully build *gumstix-console-image* and I have
> > 
> > created
> > 
> > > *meta-bebot* folder for my recipe.
> > > 
> > > My Yocto tree as follows:
> > > 
> > > Yocto
> > > 
> > >  --build
> > >  
> > >    --conf
> > >    
> > >        --bblayers.conf ( I added /home/siguser/yocto2013-05-08/poky/*
> > > 
> > > meta-bebot* \ ) path
> > > 
> > >        --local.conf ( I added IMAGE_INSTALL_append = " hello" ) under
> > > 
> > > *Additional
> > > image features*
> > > 
> > >    --downloads
> > >    --tmp
> > >    --
> > >    --
> > >  
> > >  --poky
> > >  
> > >     --bitbake
> > >     --build
> > >     --documentation
> > >     --meta
> > >     --*meta-bebot*
> > > 
> > > *        --conf*
> > > *            --bblayers.conf *(I added
> >  
> >  /home/siguser/yocto2013-05-08/poky/*
> >  
> > > meta-bebot* \ ) path
> > 
> > If I understand correctly from the above that you have put bblayers.conf
> > in
> > conf/ under your meta-bebot layer, that is not correct. bblayers.conf
> > needs to
> > be under conf/ in your build directory as usual.
> 
> my bblayers.conf file lies in  poky/meta-bebot/conf/bblayers.conf. do I
> need to remove this file and keep it in which build folder? I mean /yocto/*
> build*/conf/bblayers.conf or /yocto/*poky*/build/conf/bblayers.conf?

Yes, conf/bblayers.conf is supposed to be in the build directory; and 
whichever build directory you are actually using. The build directory can be 
anywhere, but you shouldn't really have two build directories unless you know 
what you are doing - did you perhaps run oe-init-build-env with no arguments 
in two different places? I suspect this is what has happened.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-06-04 13:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 11:46 Hello world-Checksum error Zafrullah Syed
2013-05-28 11:57 ` Satya Swaroop Damarla
2013-05-28 12:03   ` Zafrullah Syed
2013-05-28 12:05 ` Usman, Fahad
2013-05-28 12:14 ` Paul Eggleton
2013-05-28 12:32   ` Zafrullah Syed
2013-05-28 12:36     ` Erik Botö
2013-05-28 13:45       ` Zafrullah Syed
2013-05-28 13:54         ` Paul Eggleton
2013-06-04 10:42           ` Zafrullah Syed
2013-06-04 10:58             ` Paul Eggleton
2013-06-04 13:19               ` Zafrullah Syed
2013-06-04 13:26                 ` Paul Eggleton [this message]
2013-06-04 13:42                   ` Zafrullah Syed
2013-06-04 13:57                     ` Paul Eggleton
2013-06-04 19:45                       ` Zafrullah Syed
2013-06-04 20:01                         ` Michael Stickel
2013-06-04 16:19                     ` michael

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=62291455.6hREtkkLEB@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    --cc=zafrullahmehdi@gmail.com \
    /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.