Date   

Re: does meta-intel/meta-tlk layer require a README.sources file?

Burton, Ross <ross.burton@...>
 

On 26 November 2012 20:44, Tom Zanussi <tom.zanussi@...> wrote:
The meta-tlk layer isn't a BSP layer - it's a layer used to add the
'time limited kernel' feature to images built from a meta-intel BSP
layer and distributed with that layer e.g. in the downloadable tarballs
available on the Yocto downloads page.

It's a meta-intel-only layer and has no meaning unless coupled with a
meta-intel BSP layer, which does always includes a README.sources of its
own, and so doesn't itself need one.
It's probably worth adding basically this as the README so that anyone
who comes across it knows what it is.

Ross


Re: Best way to support multiple versions of Poky?

Anders Darander
 

* Burton, Ross <ross.burton@...> [121126 14:58]:

On 26 November 2012 13:55, Jerrod Peach <peachj@...> wrote:
build-bundle (git repo with our layers + tools)
|
+-- meta-ourstuff (git submodule, i.e. separate repo locked to a specific
version within build-bundle)
+-- poky (another submodule)
|
+-- poky BB files (i.e. within meta, meta-yocto, etc.)
Guacamayo does something similar, although meta-outstuff isn't a
submodule of build-bundle.
At ChargeStorm we're using a similar scheme to Guacamayo, i.e. we have
our repo with our recipes, bsp's, distro config etc. in our own
meta-*-directories. And the we have oe-core, meta-oe, and/or poky and
whatever layers we're using as submodules.

Being able to branch a "next" branch that switched the poky revision
to the danny RC instead of denzil was very convenient.
Indeed, and also to be able to create a next branch halfway between
denzil and danny, to be able to port / adapt some recipe that required
bigger changes at about the same time those occured in poky-master (or
oe-core master).

Thus, I'm pretty satisfied with our structure for the moment, though
everything can be improved.

Cheers,
Anders

--
Anders Darander
ChargeStorm AB / eStorm AB


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

On Mon, Nov 26, 2012 at 6:52 PM, Trevor Woerner <twoerner@...> wrote:
I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel =
"linux-yocto-rt"" line might be the culprit.
No, it is not related, this problem doesn't need any fancy
configuration features. This problem is reproducible
with just the plain qemux86 machine and the core-image-minimal image.
Also, before my latest tests I pulled
the latest git repo.

To reproduce this problem:

- use the latest git repositories
- run "source poky/oe-init-build-env qemux86"
- make no modifications to conf/bblayers.conf
- make no changes to conf/local.conf
- run "bitbake core-image-minimal"

After that completes successfully add the following line to your
conf/local.conf:

IMAGE_INSTALL_append = " trace-cmd"

- re-run the build "bitbake core-image-minimal"

This should complete successfully. When it does, modify the last line
of conf/local.conf to be:

IMAGE_INSTALL_append = " trace-cmd bash"

- try re-running the build now "bitbake core-image-minimal". It fails
for me as I have detailed in my previous emails.

If I manually do:

$ bitbake bash
$ bitbake core-image-minimal

everything succeeds and my image contains 'bash'. But something tells
me there's a bug in there somewhere.


some questions when writing recipes

"Liu <treebody@...>
 

Dear all,
    I'm learning how to write a recipe recently and I wrote a recipe to build a package from source code.And now I want to add an function to the recipe to make it just unpack the binary and libraries which generated from source code.It seems like the functions "make from src" and "make from extract binaries" in Makefiles.But then I am faced with a question is that how do I tell some recipes to build from src and some just to unpack binaries.
     For example,package C depends on A and B.I bitbake C ,but I want to build A from src code which means do a list of tasks like do_compile,do_install.Meanwhile I want to build B just from binaries which means only unpack the binaries and libraries to the right directory.So is there any good solutions when all wrote in one recipe? Another question is that can I pass a parameter to bitbake using the command like "bitbake C parameter" ?
Best wishes!
----------------------Liu


Re: Wiki Main page terrible sparse

Jeff Osier-Mixon <jefro@...>
 

Hi Maxin - it would be good to coordinate your effort with the rest of
the community. Can you let us know what you have in mind before
starting?

Also, please let me know if you have trouble with access. I don't see
any account requests being held.

thanks

On Fri, Nov 23, 2012 at 6:16 AM, Maxin John <Maxin.John@...> wrote:
Hi Alex,
Hello all,
I can't help but notice that the main page of the Yocto Wiki looks somewhat underwhelming compared to the new site face.
Can we please have a volunteer to update and beautify a bit the main page ?
I am interested in this task. I have already sent a request for access to the Yocto Wiki.

I'd think that we need to list current 1.4 pages, add/verify links to all main sections, and the Yocto logo, etc...
We can discuss the list of activities in this mailing-list or in irc (nickname: maxin)

Cheers,
Alex
Best Regards,
Maxin
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

Thank you so much for having a crack at this. Your results have allowed me to dig a bit deeper into this issue.

I'm still trying to narrow down the exact issue but here's what I have so far.

I'm working with the git repository, but I've been playing around with this for about a week, so I'm not 100% up to date. Specifically I'm using:

master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5

Starting with that repository I follow the regular steps:

$ poky/oe-init-build qemux86

then I edit the conf/local.conf to end up with the following (virtually no changes, just the lines at the end):

PARALLEL_MAKE = "-j 8"
MACHINE ??= "qemux86"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
CONF_VERSION = "1"

BB_DANGLINGAPPENDS_WARNONLY = "yes"
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"

then I perform

$ bitbake core-image-minimal

everything goes well. I then add the following line to the end of my conf/local.conf

IMAGE_INSTALL_append = " trace-cmd"

and run

$ bitbake core-image-minimal

everything builds just fine.

Then I modify that last line as follows:

IMAGE_INSTALL_append = " trace-cmd bash"

now when I try to build I get:

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "i586"
TARGET_OS         = "linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3+snapshot-20121126"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta             
meta-yocto       
meta-yocto-bsp    = "master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information)
ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668
Log data follows:
| DEBUG: Executing shell function do_rootfs
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/qemux86...
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/i586...
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all...
|    total:               1      0.000000 MB      2.930406 secs
|    fingerprint:      1104      0.032554 MB      0.063469 secs
|    install:           368      0.000000 MB      0.878790 secs
|    digest:            736      5.357010 MB      0.027508 secs
|    signature:         736      0.000000 MB      1.443277 secs
|    dbadd:             368      0.000000 MB      0.866237 secs
|    dbget:           12620      0.000000 MB      0.018020 secs
|    dbput:             368      3.063072 MB      0.541058 secs
|    readhdr:          3681      6.087218 MB      0.010347 secs
|    hdrload:          1929     10.076294 MB      0.012106 secs
|    hdrget:          70812      0.000000 MB      0.081749 secs
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all...
| Processing packagegroup-core-boot...
| Processing trace-cmd...
| Processing bash...
| Unable to resolve package bash
| ERROR: some packages were missing
| ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information)
ERROR: Task 7 (/home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1443 tasks of which 1442 didn't need to be rerun and 1 failed.
No currently running tasks (1442 of 1444)

Summary: 1 task failed:
  /home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Can anyone reproduce this? It doesn't make sense.

Initially when I first saw this problem, I had been using building "core-image-rt" so I thought it had something to do with that image. But my tests from today seem to indicate that it doesn't since I was able to reproduce my problem with "core-image-minimal" too.

I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"" line might be the culprit.


Re: IMAGE_INSTALL_append workflow

Robert P. J. Day
 

On Mon, 26 Nov 2012, Aws Ismail wrote:

Have you also tried this?

IMAGE_INSTALL_append += "foo"
GAAAAAHHHHHH!!! :-)

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Yocto Project Technical Team Meeting

Liu, Song <song.liu@...>
 

When: Tuesday, November 27, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed
 
Note: The GMT offset above does not reflect daylight saving time adjustments.
 
*~*~*~*~*~*~*~*~*~*
 
We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):
 
 
Conference details
Conference name: Yocto Technical Team
Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants: 30
Duration: 60 minutes
Participant passcode: 76994298
Dial-in number: 1.972.995.7777
US Toll Free number: 1.877.561.6828
BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298#
  Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.
Local and Global Access Numbers
 
Country Dial-in number
Australia: 1800 636 843
Czech Republic: 242 430 350
China (Beijing): From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai): From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen): From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities): From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark: 8060 1400
Finland: 09 41333477
France: 0497 275888
Germany: 08161 803232
Holland: 030 2417490
India: BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel: 09 790 6715
Italy: 039 69061234 (039 is local city code not country code)
Japan: From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia: From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway: 2 295 8744
Philippines: From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore: From IP phone dial 3894777
Outside TI use 6389 4777
South Korea: From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden: 08 58755577
Taiwan: From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey: Landline Only dial 0811 288 0001
then enter 877 633 1123
UK: 01604 663003
US: 972 995 7777 or 1877 561 6828
 
Recurring conferences
First scheduled conference: Tue Jun 26, 2012
Recurrence frequency: Weekly - Every 1 week(s) on Tuesday
Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
 
 
 
 


Yocto Project Technical Team Meeting

Liu, Song <song.liu@...>
 

When: Occurs every Tuesday effective 6/26/2012 until 6/18/2013 from 8:00 AM to 9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed
 
Note: The GMT offset above does not reflect daylight saving time adjustments.
 
*~*~*~*~*~*~*~*~*~*
 
We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):
 
 
Conference details
Conference name: Yocto Technical Team
Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants: 30
Duration: 60 minutes
Participant passcode: 76994298
Dial-in number: 1.972.995.7777
US Toll Free number: 1.877.561.6828
BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298#
  Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.
Local and Global Access Numbers
 
Country Dial-in number
Australia: 1800 636 843
Czech Republic: 242 430 350
China (Beijing): From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai): From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen): From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities): From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark: 8060 1400
Finland: 09 41333477
France: 0497 275888
Germany: 08161 803232
Holland: 030 2417490
India: BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel: 09 790 6715
Italy: 039 69061234 (039 is local city code not country code)
Japan: From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia: From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway: 2 295 8744
Philippines: From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore: From IP phone dial 3894777
Outside TI use 6389 4777
South Korea: From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden: 08 58755577
Taiwan: From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey: Landline Only dial 0811 288 0001
then enter 877 633 1123
UK: 01604 663003
US: 972 995 7777 or 1877 561 6828
 
Recurring conferences
First scheduled conference: Tue Jun 26, 2012
Recurrence frequency: Weekly - Every 1 week(s) on Tuesday
Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
 
 
 
 


Agenda: Yocto Project Technical Team Meeting - Tuesday, November 27, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Liu, Song <song.liu@...>
 

Agenda:
 
* Opens collection - 5 min (Song)
* Yocto 1.4 status - 20 min (Song/team)
* SWAT team rotation: Ross -> LaurentiuP
* Opens - 10 min
* Team Sharing - 20 min


-----Original Appointment-----

We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto
IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html

Conference details
Conference name:
Yocto Technical Team
Conference date/start time:
Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants:
30
Duration:
60 minutes
Participant passcode:
76994298
Dial-in number:
1.972.995.7777
US Toll Free number:
1.877.561.6828
BlackBerry users, click this link to join your conference as a participant:
1.972.995.7777x76994298#
 
Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.

Local and Global Access Numbers


Country
Dial-in number
Australia:
1800 636 843
Czech Republic:
242 430 350
China (Beijing):
From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai):
From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen):
From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities):
From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark:
8060 1400
Finland:
09 41333477
France:
0497 275888
Germany:
08161 803232
Holland:
030 2417490
India:
BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel:
09 790 6715
Italy:
039 69061234 (039 is local city code not country code)
Japan:
From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia:
From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway:
2 295 8744
Philippines:
From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore:
From IP phone dial 3894777
Outside TI use 6389 4777
South Korea:
From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden:
08 58755577
Taiwan:
From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey:
Landline Only dial 0811 288 0001
then enter 877 633 1123
UK:
01604 663003
US:
972 995 7777 or 1877 561 6828

Recurring conferences
First scheduled conference:
Tue Jun 26, 2012
Recurrence frequency:
Weekly - Every 1 week(s) on Tuesday
Recurrence ends:
End on Fri Jun 21, 2013, 10:40 AM CDT


Re: IMAGE_INSTALL_append workflow

Aws Ismail <aws.ismail@...>
 

On 11/26/2012 02:04 PM, Eren Türkay wrote:
On Mon, Nov 26, 2012 at 10:47:31AM -0500, Trevor Woerner wrote:
I'm kinda surprised nobody jumped in on this one; either my question
is so silly it isn't worth anyone's time, or I'm the only one who
wants to add packages to an image after a full build. I know my
question has nothing to do with trace-cmd specifically, adding any
package after a full build results in the same problem.
I don't think you are the first person who wants to add a package to image after
the image has been built :)

The obvious problem would have been leading spaces in IMAGE_INSTALL_append but
you explicitly stated its correct. Normally, the class that's responsible for
image creation (image.bbclass) depends on the packages defined in IMAGE_INSTALL
so that the packages are built before the image creation begins.

image.bbclass, line 9
---------------------
RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL}
${ROOTFS_BOOTSTRAP_INSTALL}"

On irc (#oe), Eric Benard tried IMAGE_INSTALL_append = " trace-cmd" after a full
build and reported that it built fine. I'm CCing him.
Have you also tried this?

IMAGE_INSTALL_append += "foo"

Aws\

I believe that it will be better to include your <image> file and the files that
you changed so that it will be easier to debug. Mentioning your layers,
configuration, version of Yocto you use will also be helpful.

Regards,
Eren



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


-- 


Re: does meta-intel/meta-tlk layer require a README.sources file?

Tom Zanussi <tom.zanussi@...>
 

On Sat, 2012-11-24 at 07:59 -0500, Robert P. J. Day wrote:
more annoying pedantry, but from what i read in the current yocto
BSP manual, a BSP layer *requires* a README.sources file, but there is
no such file in the meta-intel/meta-tlk layer, although i can
appreciate that that layer isn't *really* a BSP definition. or is it?
The meta-tlk layer isn't a BSP layer - it's a layer used to add the
'time limited kernel' feature to images built from a meta-intel BSP
layer and distributed with that layer e.g. in the downloadable tarballs
available on the Yocto downloads page.

It's a meta-intel-only layer and has no meaning unless coupled with a
meta-intel BSP layer, which does always includes a README.sources of its
own, and so doesn't itself need one.

The purpose of the README.sources also really only has meaning relative
to a generated image distributed with a layer - it tells the user where
he or she can find the sources that were used to generate the image that
was downloaded as part of the BSP.

I'm cc:ing the originators of those files in case they might have
anything to add or can correct me if my assumptions about those files
are wrong...

can someone clarify this? is there a clear explanation as to what
is required for a simple *layer* and what is required for an actual
BSP definition?
The BSP Developer's Guide says what should go into a BSP layer. I don't
know of anything that says what should go into a 'simple layer' other
than what's needed from a functional standpoint. I suppose it would
make sense in general to have layers follow the same basic layout as the
main oe-core metadata, and I guess they mostly do these days already,
but since layers are a general mechanism that mean different things to
different people, I don't know that it's possible to require much beyond
functionality.

For BSPs, the purpose of a layer is to both document and distribute a
test image or two, to allow the user to find the sources that were used
to build the image, and to build the image on his or her own, which is
what drove the specific requirements for BSP layers as described in the
BSP Developer's Guide...

Tom


rday


Re: my wiki page for using OE and meta-ti layer to build for panda ES

Robert P. J. Day
 

On Mon, 26 Nov 2012, Evade Flow wrote:

Love it! Any chance you could add an 'Advanced' or 'Next Steps'
section that shows how to go beyond a minimal build? Like, how to get
a working Qt stack into a custom image on the PandaBoard?

On Wed, Nov 21, 2012 at 2:44 PM, Robert P. J. Day <rpjday@...> wrote:

not strictly related to yocto but i figured some folks might be
interested in a recipe for using OE and the meta-ti layer to build a
bootable system for a panda ES:

http://www.crashcourse.ca/wiki/index.php/OE-Core%2C_meta-ti_and_the_PandaBoard_ES
by the way, would anyone using that very board like to confirm that
my recipe so far at that wiki page is correct? just what's there --
is there anything that can be added or tweaked? thanks.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: my wiki page for using OE and meta-ti layer to build for panda ES

Robert P. J. Day
 

On Mon, 26 Nov 2012, Evade Flow wrote:

Love it! Any chance you could add an 'Advanced' or 'Next Steps'
section that shows how to go beyond a minimal build? Like, how to get
a working Qt stack into a custom image on the PandaBoard?

On Wed, Nov 21, 2012 at 2:44 PM, Robert P. J. Day <rpjday@...> wrote:

not strictly related to yocto but i figured some folks might be
interested in a recipe for using OE and the meta-ti layer to build a
bootable system for a panda ES:

http://www.crashcourse.ca/wiki/index.php/OE-Core%2C_meta-ti_and_the_PandaBoard_ES

feedback welcome.
at some point, yes, but just to be clear about what i'm trying to
do, while i'm happy to share my findings, i'm documenting solely stuff
that is of use to *me* and the boards i'm using -- in the case above,
the pandaboard ES (Rev B1). and while the original panda is a
perfectly fine board, it's not what i'm using so i'm not going to
invest any time in it.

also, before someone suggests i post this stuff at one of common
wikis (elinux.org, etc.), that's also a fine idea but i'm keeping this
stuff at my site out of pure self-interest -- it brings in visitors so
i can promote my training business. totally selfish. capitalism. :-)

all that out of the way, if anyone out there is also working on the
board i'm using and wants to share what they've done or point to sites
that have working recipes for this board, i'll be more than happy to
add that to my wiki page(s). obviously, this list should be
restricted to yocto-related content to not wander too far afield.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: IMAGE_INSTALL_append workflow

Eren Türkay <eren@...>
 

On Mon, Nov 26, 2012 at 10:47:31AM -0500, Trevor Woerner wrote:
I'm kinda surprised nobody jumped in on this one; either my question
is so silly it isn't worth anyone's time, or I'm the only one who
wants to add packages to an image after a full build. I know my
question has nothing to do with trace-cmd specifically, adding any
package after a full build results in the same problem.
I don't think you are the first person who wants to add a package to image after
the image has been built :)

The obvious problem would have been leading spaces in IMAGE_INSTALL_append but
you explicitly stated its correct. Normally, the class that's responsible for
image creation (image.bbclass) depends on the packages defined in IMAGE_INSTALL
so that the packages are built before the image creation begins.

image.bbclass, line 9
---------------------
RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL}
${ROOTFS_BOOTSTRAP_INSTALL}"

On irc (#oe), Eric Benard tried IMAGE_INSTALL_append = " trace-cmd" after a full
build and reported that it built fine. I'm CCing him.

I believe that it will be better to include your <image> file and the files that
you changed so that it will be easier to debug. Mentioning your layers,
configuration, version of Yocto you use will also be helpful.

Regards,
Eren

--
. 73! DE TA1AET
http://erenturkay.com/


Re: my wiki page for using OE and meta-ti layer to build for panda ES

Evade Flow <evadeflow@...>
 

Love it! Any chance you could add an 'Advanced' or 'Next Steps'
section that shows how to go beyond a minimal build? Like, how to get
a working Qt stack into a custom image on the PandaBoard?

On Wed, Nov 21, 2012 at 2:44 PM, Robert P. J. Day <rpjday@...> wrote:

not strictly related to yocto but i figured some folks might be
interested in a recipe for using OE and the meta-ti layer to build a
bootable system for a panda ES:

http://www.crashcourse.ca/wiki/index.php/OE-Core%2C_meta-ti_and_the_PandaBoard_ES

feedback welcome.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

I'm kinda surprised nobody jumped in on this one; either my question
is so silly it isn't worth anyone's time, or I'm the only one who
wants to add packages to an image after a full build. I know my
question has nothing to do with trace-cmd specifically, adding any
package after a full build results in the same problem.

It would certainly seem odd that the yocto workflow assumes you always
know 100% ahead of time which packages you want in your final image. I
know when I was playing around with Hob this wasn't an issue: I would
simply add the new packages and Hob would build them and add them to
the image.

From what I have seen from skimming the documentation, the
documentation talks at length about how to add a new package to the
configuration, but it doesn't say what commands to issue after
modifying the config files. Obviously running "bitbake <image>" alone
doesn't work.

On Fri, Nov 23, 2012 at 1:27 PM, Trevor Woerner <twoerner@...> wrote:
There have been many emails and lots of documentation describing how
to add a package to a build, and that's all great.

Today I was playing around with an image I had already built and
decided I wanted to add a new package to the mix: trace-cmd. I added "
trace-cmd" (with the required leading space) to IMAGE_INSTALL_append
and re-ran my "bitbake <image>" command.

It failed:

Unable to resolve package trace-cmd

If I perform:

$ bitbake trace-cmd

and then

$ bitbake <image>

it works fine. What am I missing?

As it turns out, if I knew before my first build that I wanted
trace-cmd, I could have just added it as described above and
everything would have worked as well.

Best regards,
Trevor


Re: Best way to support multiple versions of Poky?

Burton, Ross <ross.burton@...>
 

On 26 November 2012 13:55, Jerrod Peach <peachj@...> wrote:
build-bundle (git repo with our layers + tools)
|
+-- meta-ourstuff (git submodule, i.e. separate repo locked to a specific
version within build-bundle)
+-- poky (another submodule)
|
+-- poky BB files (i.e. within meta, meta-yocto, etc.)
Guacamayo does something similar, although meta-outstuff isn't a
submodule of build-bundle.

Being able to branch a "next" branch that switched the poky revision
to the danny RC instead of denzil was very convenient.

Ross


Re: Best way to support multiple versions of Poky?

Jerrod Peach <peachj@...>
 

On Thu, Nov 22, 2012 at 3:35 AM, Chris Tapp <opensource@...> wrote:
I'm just getting round to moving from 'denzil' to 'danny'. I've got a layer that makes some changes to a few recipes through bbappend files.

However, 'danny' has bumped a few of these to a new version (which is good) which means I now have bbappend files that get a 'there is no matching bb file' errors when I try to build. This is easy to fix (generally just rename the bbappend to match the new version), but I would like the layer to be able to work with older versions of Poky - mainly in case I need to make changes to an existing project that hasn't be verified under 'danny'.

What's the best way to do this? All I can think of is to have another set of layers to use when building against a specific poky version:

meta-mystuff
|
+--poky-versions
   |
   +--denzil-specific
   +--danny-specific
   +--etc

Is there a more elegant solution?

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

I don't know what sort of version control (if any) you're using around "meta-mystuff", so what I'm about to suggest may not be directly applicable to you.  Also, note that we have not actually deployed the scheme we've developed at our company yet (so there may be some reason it doesn't work that we haven't thought of yet), but here's the directory/repo structure we think will work for our code:

build-bundle (git repo with our layers + tools)
|
+-- meta-ourstuff (git submodule, i.e. separate repo locked to a specific version within build-bundle)
+-- poky (another submodule)
   |
   +-- poky BB files (i.e. within meta, meta-yocto, etc.)

When we release code, we'll create a tag in build-bundle.  If the released code needs to diverge from the state of our master, we'll branch, then tag.  Either way, if you want to build old code, you check out the tag and build it.  That should "just work" because what we see as the tools (i.e. everything in the poky directory) are being version-controlled along-side everything we've added, including .bbappend files in our layers that modify .bb files in the poky layer.  Of course, if you need to modify an old release, you'd branch off the release you wanted to modify.  So, if "denzil" is the current version and you need to modify a release created with "danny", you simply branch from that release, and all your .bbappend files and tools will be correct for the "danny" version of the Yocto tools.


Re: [PATCH resend][opkg-utils] opkg.py/opkg-build: fix creation of tar archives

Burton, Ross <ross.burton@...>
 

On 26 November 2012 13:19, Burton, Ross <ross.burton@...> wrote:
On 10 November 2012 09:33, Tomas Frydrych <tf+lists.yocto@...> wrote:
Could this be also applied to the danny branch (and perhaps even denzil)?
This was present in the Danny release. For Denzil you'd have to ask Scott...
Apologies, I was grepping the wrong branch...

*Now* it's locally in danny-next.

Ross