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.

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.

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

Have you also tried this?

IMAGE_INSTALL_append += "foo"

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

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

-- 

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?

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?

rday

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

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.

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.

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.)

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...