remaining comments on current BSP developers guide
(again, someone up the food chain can decide what's worth
processing.)
1.6.1 Common Features
* "Both tools [yocto-bsp and yocto-kernel] reside in the scripts/ subdirectory of the Source Directory." no, they don't, they're in meta-yocto/scripts/, so simply sourcing oe-init-build-env isn't sufficient to add them to the search path, is it? (i'm guessing it used to be, but no longer.)
1.6.2 Creating a new BSP Layer ...
$ yocto-bsp list karch
Architectures available:
qemu
x86_64
i386
powerpc
arm
mips but if you run that, you get the additional arch "layer". where's
that coming from? is it a holdover from before there was a yocto-layer command? i never noticed that before now.
* "Assuming you have sourced the environment ..." Again, you don't get these utilities in your PATH by sourcing the environment, you need to do that manually.
* "...pressing enter and providing an invalid response..." um, what is that supposed to say?
* Point 6. Do you actually need to include the meta-yocto and meta-yocto-bsp layers in this new layer's bblayers.conf file? I don't see why but maybe I'm missing something obvious.
* also, typo "BBLAYERS = ?"
i think that's everything.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 3 lines · Robert P. J. Day
(again, someone up the food chain can decide what's worth processing.)
Thanks for all your comments - I'll submit some patches to the docs when I get a chance, but see below..
Quoted 8 lines
1.6.1 Common Features
* "Both tools [yocto-bsp and yocto-kernel] reside in the
scripts/subdirectory of the Source Directory." no, they don't, they're in meta-yocto/scripts/, so simply sourcing oe-init-build-env isn't sufficient to add them to the search path, is it? (i'm guessing it used to be, but no longer.)
Not sure what you're looking at to see that. This is what I have:
[trz@empanada dylan-cur]$ pwd/home/trz/yocto/dylan-cur
[trz@empanada dylan-cur]$ ls
bitbake LICENSE meta-intel meta-yocto-bsp README build meta meta-skeleton oe-init-build-env README.hardware documentation meta-hob meta-yocto poky-extras scripts
[trz@empanada dylan-cur]$ ls -al meta-yocto
total 24
drwxrwxr-x. 6 trz trz 4096 Apr 17 11:31 .
drwxrwxr-x. 14 trz trz 4096 Apr 17 14:20 ..
drwxrwxr-x. 2 trz trz 4096 Apr 17 11:31 classes drwxrwxr-x. 3 trz trz 4096 Apr 17 11:31 conf drwxrwxr-x. 5 trz trz 4096 Apr 17 11:31 recipes-core drwxrwxr-x. 3 trz trz 4096 Apr 17 11:31 recipes-kernel
[trz@empanada dylan-cur]$ ls -al scripts/yocto* -rwxrwxr-x. 1 trz trz 5302 Apr 17 11:31 scripts/yocto-bsp -rwxrwxr-x. 1 trz trz 12957 Apr 17 11:31 scripts/yocto-kernel -rwxrwxr-x. 1 trz trz 4840 Apr 17 11:31 scripts/yocto-layer
No scripts/ in meta-yocto, etc. So things should work as expected with sourcing oe-init-build-env, etc.
Quoted 11 lines
1.6.2 Creating a new BSP Layer ...
$ yocto-bsp list karch Architectures available: qemu x86_64 i386 powerpc arm mips
Quoted 4 lines
but if you run that, you get the additional arch "layer". where's
that coming from? is it a holdover from before there was a yocto-layer command? i never noticed that before now.
Right, that's a bug - 'layer' does come from the new yocto-layer command and shouldn't be there..
Quoted 4 lines
* "Assuming you have sourced the environment ..." Again, you don't get these utilities in your PATH by sourcing the environment, you need to do that manually.
See above..
Tom
Quoted 13 lines
* "...pressing enter and providing an invalid response..." um, what is that supposed to say?
* Point 6. Do you actually need to include the meta-yocto and meta-yocto-bsp layers in this new layer's bblayers.conf file? I don't see why but maybe I'm missing something obvious.
* also, typo "BBLAYERS = ?"
i think that's everything.
rday
Quoted 11 lines · Tom Zanussi
Quoted 8 lines · Robert P. J. Day
1.6.1 Common Features
* "Both tools [yocto-bsp and yocto-kernel] reside in the
scripts/subdirectory of the Source Directory." no, they don't, they're in meta-yocto/scripts/, so simply sourcing oe-init-build-env isn't sufficient to add them to the search path, is it? (i'm guessing it used to be, but no longer.)
Quoted 8 lines
Not sure what you're looking at to see that. This is what I have:
[trz@empanada dylan-cur]$ pwd
/home/trz/yocto/dylan-cur
[trz@empanada dylan-cur]$ lsbitbake LICENSE meta-intel meta-yocto-bsp README build meta meta-skeleton oe-init-build-env README.hardware documentation meta-hob meta-yocto poky-extras scripts
ah, i see, that's because i have a mega-directory of layers and
don't check out meta-yocto or meta-yocto-bsp into the same directory as oe-core. you obviously check out "poky", which puts everything in one place under scripts/. but the yocto-* utilities are technically part of the meta-yocto "layer". perhaps that should be made clear.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Robert,
Fixed the two points below in the doc. See http://www.yoctoproject.org/docs/1.4/bsp-guide/bsp-guide.html.
Thanks again,
Scott
Quoted 34 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Robert P. J. Day
Sent: Monday, April 22, 2013 9:00 AM
To: Yocto discussion list
Subject: [yocto] remaining comments on current BSP developers guide(again, someone up the food chain can decide what's worth
processing.)1.6.1 Common Features
* "Both tools [yocto-bsp and yocto-kernel] reside in the
scripts/subdirectory of the Source Directory." no, they don't, they're in meta-yocto/scripts/, so simply sourcing oe-init-build-env isn't sufficient to add them to the search path, is it? (i'm guessing it used to be, but no longer.)1.6.2 Creating a new BSP Layer ...
$ yocto-bsp list karch Architectures available: qemu x86_64 i386 powerpc arm mipsbut if you run that, you get the additional arch "layer". where's
that coming from? is it a holdover from before there was a yocto-layer command? i never noticed that before now.
Quoted 6 lines
* "Assuming you have sourced the environment ..." Again, you don't get these utilities in your PATH by sourcing the environment, you need to do that manually.
* "...pressing enter and providing an invalid response..." um, what is that supposed to say?
Poor wording - changed to "Pressing enter without supplying anything on the command line or pressing enter with an invalid response causes...."
Quoted 6 lines
* Point 6. Do you actually need to include the meta-yocto and meta-yocto-bsp layers in this new layer's bblayers.conf file? I don't see why but maybe I'm missing something obvious.
* also, typo "BBLAYERS = ?"
Fixed typo.
Quoted 18 lines
i think that's everything.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.caTwitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday========================================================================
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto