From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Matthias Dübon" <mail@ing-duebon.de>
Cc: poky@yoctoproject.org
Subject: Re: content of build/tmp/work folder?
Date: Sun, 06 Nov 2011 13:19:57 +0000 [thread overview]
Message-ID: <1320585597.23708.5.camel@ted> (raw)
In-Reply-To: <CANv1b=0WaEi032+aBYPstKwvG6C-QD3aXbEa-947k_P_7aiLYA@mail.gmail.com>
On Sun, 2011-11-06 at 09:48 +0100, Matthias Dübon wrote:
> Hello everyone,
>
>
> I am just starting to dive into Poky (and embedded linux). I really
> like the concept and the idea of Yocto(resp. Poky) and up to now
> (almost) everything worked as expected. But the build/tmp/work
> directory is puzzling me.
> The handbook stated "this directory contains various subdirectories
> for each architecture". In m my working directory I found the
> following folders:
>
> all-poky-linux
These are architecture independent things like scripts/graphics/fonts.
> beagleboard-poky-linux-gnueabi
>qemux86-poky-linux
>qemuarm-poky-linux-gnueabi
These are machine specific things (you must have built for three
different machines).
> armv5te-poky-linux-gnueabi
> i586-poky-linux
>armv7a-vfp-neon-poky-linux-gnueabi
These are software built for specific architectures and specific
optimisations within those architectures.
>i686-nativesdk-pokysdk-linux
> i686-pokysdk-linux
These are parts of the SDK/toolchain (targetted at an i686 SDKMACHINE)
> i686-linux
These are "native" software designed to run on the system you're
building on.
>
> Ok, beagleboard-poky-linux-gnueabi, qemuarm-poky-linux-gnueabi, ...
> are architectures I build. But what about the others folders. What the
> meaning of all-poky-linux?
Hope that helps!
Cheers,
Richard
prev parent reply other threads:[~2011-11-06 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 8:48 content of build/tmp/work folder? Matthias Dübon
2011-11-06 13:06 ` Christian Gagneraud
2011-11-06 13:19 ` Richard Purdie [this message]
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=1320585597.23708.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mail@ing-duebon.de \
--cc=poky@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.