From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Zafrullah Syed <zafrullahmehdi@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Hello world-Checksum error
Date: Tue, 04 Jun 2013 14:57:49 +0100 [thread overview]
Message-ID: <4896833.vPV5cWFueY@helios> (raw)
In-Reply-To: <CAAGt+t3VoPRzymiJKG5kwEXeD=SPDWO1KTa2AqE6QHG5t0XTyw@mail.gmail.com>
On Tuesday 04 June 2013 15:42:06 Zafrullah Syed wrote:
> On Tue, Jun 4, 2013 at 3:26 PM, Paul Eggleton <paul.eggleton@linux.intel.com
> wrote:
> > 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.
>
> I think yes. I usually give just *source oe-init-build-env *command, this
> is how i used earlier and failed. May be that is the reason it has created
> another build directory in /poky.
> What should be the command before building? i guess this(
> TEMPLATECONF=meta-gumstix-extras/conf
> source ./poky/oe-init-build-env ). so, every time i just need to give
> TEMPLATECONF command before building?
You need to run oe-init-build-env at the start of every session yes, but you
shouldn't need to specify TEMPLATECONF except when you first create the build
directory. The important thing is you need to be in the same directory when
you run oe-init-build-env *or* specify the path to the build directory as a
parameter.
> Lastly, my meta-bebot directory should be as following ?
>
> /poky
> --meta-bebot
> --conf
> --layer.conf
> --recipes-bebot
> --hello
> --hello.bb
If you have recipes-bebot under meta-bebot, yes.
> and meta-bebot path should be set in bblayers.conf file?
Yes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-04 13:57 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
2013-06-04 13:42 ` Zafrullah Syed
2013-06-04 13:57 ` Paul Eggleton [this message]
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=4896833.vPV5cWFueY@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.