[YOCTO #4196] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=4196 The description field in the recipe was changed to match the package. Signed-off-by: mulhern <mulhern@...> ---

This patch changes the description field to match the package. The following changes since commit 4f2821cb7b01ca11249154d1d071bc267dbf4f85: removed rpm dependency on redhat-security (2013-08-01

Umm... Is 'dylan' a meaningful answer? Ooo, interesting. 'bitbake -e' all by itself gives me this: ---- # $UBOOT_MACHINE # set

The files are in tmp/work/.../foo_1.0-r1/packages-split/foo, and also in tmp/work/.../foo_1.0-r1/image, and the package is listed in that text file. And the logs show no errors. This smells like one

Interesting, did you verify that the files are in the tmp/work/.../foo/packages-split/foo directory. You can also look in the tmp/work/.../gumstix-foo-pyygtk-image/1.0-r0/installed_pkgs.txt file to

Not what I would expect, if you bbappend was in play correctly, here is my example: # $UBOOT_MACHINE [4 operations] # set /srv/hdd/poky/meta/conf/machine/include/tune-ppce300c3.inc:13 #

My top level recipe uses IMAGE_INSTALL to add a bunch of packages, including one whose name matches the name of the recipe that's being processed but whose output is being ignored. This is exactly

Thank you for replying: Correct. Umm... Actually, no I dont: --- $ bitbake -e [ ...blah, blah, blah...] # $UBOOT_MACHINE # set

Where do you add your recipe's generated packages to the image, this could be in your custom image with an RDEPENDS or via something in local.conf like CORE_IMAGE_EXTRA_INSTALL_append = "

But you did indirectly, I have to assume that your default MACHINE is set for "ourboard" and what's happened here is when the bbappend was added, your setting of UBOOT_MACHINE_ourboard is an override

I've done exactly this in a different Yocto-based project, and it worked. Now I'm trying to do the same thing in a Gumstix build, and it's not working. I have a dumb little recipe that merely copies

Two months ago I never heard of Yocto -- now I are one. I'm attempting to create a layer and pile of recipes that will allow us to adapt Freescale's i.MX support to our custom board. Right now

Hello all, Some one know if there is any meta that support xmlsec? xmlsec source: http://www.aleksey.com/xmlsec/ Thanks for all Help. -- Raul Rosetto Muñoz

You can start by building a reference image e.g. core-image-basic and then add the packages as you want extra I would encourage to read through the

Hi, Using the Yocto Project 1.4, I want to build the packages like ssh, telnet, alias and other library packages for arm. I am not getting an idea how I should have to add those

The weekly build should be available soon at: http://autobuilder.yoctoproject.org/pub/nightly/20130813-3 Known issues: - Both eclipse buildouts are using the wrong repo. I'll have the issue fixed in

Ok, thanks - mainly wanted to make sure I was following a best practice of sorts. On Aug 13, 2013, at 5:39 PM, Khem Raj <raj.khem@...> wrote:

there isn't one. Its not as common a case to abstract out into a class additionally when you have such recipes then the install paths aren't standard either so adding do_install to recipe and doing it

I have some scripts I'd like to copy to the target to a simple folder, e.g. /lib/foo Ideally I'd like to just create a simple recipe something like this: SRC_URI = "file://lib/foo/foo.sh"inherit

Hi Anders - we are still in the planning stages for Dev Day. I'll be sure to announce on this list as soon as we get anything established, hopefully later this week. For those planning travel, if we