From: Christian Gagneraud <chgans@gna.org>
To: poky@yoctoproject.org
Subject: Re: content of build/tmp/work folder?
Date: Sun, 06 Nov 2011 13:06:08 +0000 [thread overview]
Message-ID: <4EB68640.4080809@gna.org> (raw)
In-Reply-To: <CANv1b=0WaEi032+aBYPstKwvG6C-QD3aXbEa-947k_P_7aiLYA@mail.gmail.com>
On 06/11/11 08:48, 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
> beagleboard-poky-linux-gnueabi
> i686-nativesdk-pokysdk-linux
> qemux86-poky-linux
> armv5te-poky-linux-gnueabi
> i586-poky-linux
> i686-pokysdk-linux
> armv7a-vfp-neon-poky-linux-gnueabi
> i686-linux
> qemuarm-poky-linux-gnueabi
>
> 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?
>
> A rough explanation would be very helpful.
"all" stands for all architectures, it contains stuff like python, perl,
etc... which are architecture independent.
"beagleboard" and "qemuarm" are machine specific, "armv5te" and "i586"
are architecture specific.
Chris
>
> --
> Regards
> Matthias Dübon
>
> Ingenieurbüro Dübon
> Eberhardstr. 18
> 72072 Tuebingen
> Germany
>
> http://www.ing-duebon.de <http://www.ing-duebon.de/>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
Chris
next prev parent reply other threads:[~2011-11-06 13:06 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 [this message]
2011-11-06 13:19 ` Richard Purdie
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=4EB68640.4080809@gna.org \
--to=chgans@gna.org \
--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.