From: <openembedded@rkmorris.us>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Build Directory inside conf
Date: Tue, 24 Aug 2010 13:33:16 -0500 [thread overview]
Message-ID: <1282674796964487500@rkmorris.us> (raw)
In-Reply-To: <AANLkTimHMk2JCmk-f7v+f20oOCLimFmvmMOXHNAXWbZV@mail.gmail.com>
That makes sense - thanks!
One more question then, as this isn't mentioned in the "Getting Started" section of the Wiki - do I need to configure this? I ask because I'm having issues with my build results right now (kernel is fine, initrd is hanging).
Thanks again,... Russell
On Tue, Aug 24, 2010 01:21 PM, Chris Larson <clarson@kergoth.com> wrote:
> On Tue, Aug 24, 2010 at 9:41 AM, <openembedded@rkmorris.us> wrote:
>
> > Hi,
> > Maybe we're not talking about the same thing ... but to confirm - inside
> > the conf directory there is a build directory, with the file "Power
> > Macintosh-darwin.conf" inside. Is this really supposed to be part of the
> > "official" build?
>
>
> No, we're talking about exactly the same thing. "build" in this context is
> referring to the *build machine*, not a "build" as in the output from
> running bitbake.
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From dp@xora.org.uk Tue Aug 24 22:18:32 2010
Received: from www.xora.org.uk ([80.68.91.202] helo
next prev parent reply other threads:[~2010-08-24 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 3:11 Build Directory inside conf openembedded
2010-08-24 13:53 ` Chris Larson
2010-08-24 16:41 ` openembedded
[not found] ` <AANLkTimHMk2JCmk-f7v+f20oOCLimFmvmMOXHNAXWbZV@mail.gmail.com>
2010-08-24 18:33 ` openembedded [this message]
2010-08-24 21:14 ` Chris Larson
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=1282674796964487500@rkmorris.us \
--to=openembedded@rkmorris.us \
--cc=openembedded-devel@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 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.