From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id ADAA3E00CF5; Wed, 15 Nov 2017 15:51:30 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [147.11.1.11 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 98A46E00C45 for ; Wed, 15 Nov 2017 15:51:28 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id vAFNpMdV026885 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Nov 2017 15:51:22 -0800 (PST) Received: from ALA-MBC.corp.ad.wrs.com ([169.254.1.97]) by ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.03.0361.001; Wed, 15 Nov 2017 15:51:21 -0800 From: "Reyna, David" To: tykwon Thread-Topic: [Toaster] The machine of the added layer does not come out. Thread-Index: AdNd4bcOq9LI+zgUQomzrRGHIscvvgAhFOkw Date: Wed, 15 Nov 2017 23:51:20 +0000 Message-ID: <5E53D14CE4667A45B9A06760DE5D13D0CF80A95E@ALA-MBC.corp.ad.wrs.com> References: <013101d35de1$ba9d1d80$2fd75880$@co.kr> In-Reply-To: <013101d35de1$ba9d1d80$2fd75880$@co.kr> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.11.157.211] MIME-Version: 1.0 Cc: "toaster@yoctoproject.org" Subject: Re: The machine of the added layer does not come out. X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 23:51:30 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_5E53D14CE4667A45B9A06760DE5D13D0CF80A95EALAMBCcorpadwrs_" --_000_5E53D14CE4667A45B9A06760DE5D13D0CF80A95EALAMBCcorpadwrs_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kwon, 1. When you import a layer, there is no meta information to fill in the lay= er features, in contrast to the normal layers that are loaded from the OE L= ayer Index. For this layer, I observe that while there is a "master" branch= for "meta-odroid", Alas, Phillipe has not yet created a "rocko" branch in = the OE Layer Index for his layer. 2. If you click on the Machine tab in this imported layer, you will see the= message "Toaster does not have machine information for the meta-odroid lay= er. Sadly, machine information cannot be obtained from builds, so this page= will remain empty." In this case you would set the Machine type directly entering the known val= ues from the layer. 3. If you click on the Recipe tab in this imported layer, you will see the = message "Toaster does not have recipe information for the meta-odroid layer= . Toaster learns about layers when you build them. If this layer provides a= ny recipes, they will be listed here after you build the meta-odroid layer.= " In this case you would enter the recipe name directly and build it, enterin= g the known values from the layer. Once you build that recipe, it will then= appear in the Recipe tab for the imported layer. I tested this by setting the Machine to "odroid-c2" and building the "atf-n= ative" recipe, and indeed "atf-native" did appear as a recipe under the cus= tom layer. I also tried the recipe "odroid-c2-init " but bitbake did not li= ke it, so there is something different with this recipe. 4. In general, when you import a layer Toaster assumes you know the content= and that you will enter the appropriate values (as you would on the comman= d line). I can consider an enhancement request to attempt to discover the m= achines, recipes, image recipes, and classes from an imported layer, but I = expect that this will be a non-trivial effort. - David From: toaster-bounces@yoctoproject.org [mailto:toaster-bounces@yoctoproject= .org] On Behalf Of tykwon Sent: Tuesday, November 14, 2017 11:17 PM To: toaster@yoctoproject.org Subject: [Toaster] The machine of the added layer does not come out. I am yocto newbie. I am using poky-rocko-18.0.0. I have a problem with the "imoport layer" as a toaster. I added meta-odroid(https://github.com/akuster/meta-odroid) as a toaster. I added meta-odroid as a toaster, but there is no machine entry. However, there are a total of 6 machiies added to my layer(meta-odroid)(htt= ps://github.com/akuster/meta-odroid/tree/master/conf/machine). How do I get the meta-odroid machine I added as an "import layer" to work p= roperly? Is there anything wrong with my setup? The figure below shows the current settings of my import layer. https://i.imgur.com/G2GkCbX.png I'm sorry I do not have enough English. :) Best regards. kwon --_000_5E53D14CE4667A45B9A06760DE5D13D0CF80A95EALAMBCcorpadwrs_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Kwon,

 

1. When you import a layer, there is no meta information to fill in the = layer features, in contrast to the normal layers that are loaded from the OE Layer Index. For this layer, I observe that while there= is a “master” branch for “meta-odroid”, Alas, Phillipe has not yet = created a “rocko” branch in the OE Layer Index for his layer.

 

2. If you click on the Machine tab in this i= mported layer, you will see the message “Toaster does not h= ave machine information for the meta-odroid layer. Sadly, machine information cannot be obtained from builds, = so this page will remain empty.”<= /o:p>

 

In this case you would set the Machine type directly entering the known = values from the layer.

3. If you click on the Recipe tab in this im= ported layer, you will see the message “Toaster does not ha= ve recipe information for the meta-odroid layer. Toaster learns about layers when you bu= ild them. If this layer provides any recipes, they will be listed here afte= r you build the meta-odroid layer.”

In this case you would enter the recipe name directly and build it, ente= ring the known values from the layer. Once you build that recipe, it will then appear in the Recipe tab for the imported layer.

 

I tested this by setting the Machine to “odroid-c2” and building the “atf-native“= ; recipe, and indeed “atf-native” did appear as a recipe under the custom layer. I= also tried the recipe “odroid-c2-init ” but bitbake did not like it, so there is= something different with this recipe.

 

4. In general, when you import a layer Toaster assumes you know the cont= ent and that you will enter the appropriate values (as you would on the command line). I can consider an enhancement request to attem= pt to discover the machines, recipes, image recipes, and classes from an im= ported layer, but I expect that this will be a non-trivial effort.

 

- David

 

Fr= om: toaster-bounces@yoctoproject.org [mailto:toaster-bounces@yoctopro= ject.org] On Behalf Of tykwon
Sent: Tuesday, November 14, 2017 11:17 PM
To: toaster@yoctoproject.org
Subject: [Toaster] The machine of the added layer does not come out.=

 =

I am yocto n= ewbie.

I am using p= oky-rocko-18.0.0.

I have a pro= blem with the "imoport layer" as a toaster.

I added meta= -odroid(https://github.c= om/akuster/meta-odroid) as a toaster.

I added meta= -odroid as a toaster, but there is no machine entry.

However, the= re are a total of 6 machiies added to my layer(meta-odroid)(https://github= .com/akuster/meta-odroid/tree/master/conf/machine).

 <= /o:p>

How do I get= the meta-odroid machine I added as an "import layer" to work pro= perly?

Is there any= thing wrong with my setup?

 <= /o:p>

The figure b= elow shows the current settings of my import layer.

https://i.imgur.com/G2GkCbX.png

 <= /o:p>

I'm sorry I = do not have enough English. :)

 <= /o:p>

Best regards= .

kwon

--_000_5E53D14CE4667A45B9A06760DE5D13D0CF80A95EALAMBCcorpadwrs_--