[yocto] What criteria are categorized? (tmp/work/...)

윤영석 earwigz at naver.com
Mon Nov 28 21:08:27 PST 2016

I want to split the package that belongs to host and target in one recipes. 
-----Original Message-----
From: "Paul Eggleton"<paul.eggleton at linux.intel.com> 
To: "윤영석"<earwigz at naver.com>; 
Cc: <yocto at yoctoproject.org>; 
Sent: 2016-11-29 (화) 13:15:12
Subject: Re: [yocto] What criteria are categorized? (tmp/work/...)
On Tue, 29 Nov 2016 11:47:40 윤영석 wrote:
> After poky the build, i look at the tmp/work folder.
> I can see these folders.
> All-poky-linux / i586-poky-linux / qemux86-poky-linux / x86_64-linux /
> What is the classification of each folder?

That directory level corresponds to MULTIMACH_TARGET_SYS, whose value is
"${PACKAGE_ARCH}${TARGET_VENDOR}-${TARGET_OS}". The first variable
PACKAGE_ARCH has a default value of "${TUNE_PKGARCH}" which makes a recipe
architecture-specific by default. PACKAGE_ARCH is often set in the recipe
in two common cases:

1) Recipes which are packaging something that is not architecture-specific -
these should "inherit allarch" which will automatically set
PACKAGE_ARCH = "all". Note that in this situation you should use
"inherit allarch" rather than setting PACKAGE_ARCH yourself since that is
not the only thing that the allarch class takes care of.

2) Recipes which are packaging something that is machine-specific - these
should set PACKAGE_ARCH = "${MACHINE_ARCH}".

Additionally, recipes that are building for the build host rather than the
target machine (*-native) or for the SDK (nativesdk-*) get different values
for  MULTIMACH_TARGET_SYS as well, but this is accomplished by inheriting
the native or nativesdk classes or using BBCLASSEXTEND to create a variant
of the recipe for one or both.

> What options should I set in recipes?

Can you be more precise about what you want to do?



Paul Eggleton
Intel Open Source Technology Centre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161129/9612657b/attachment.html>

More information about the yocto mailing list