Folks, Currently opkg-utils is hosted on svn.openmoko.org, that host seems to be failing and is not a reliable upstream. We have a copy of opkg-utils under git.yoctoproject.org (captured the last

I use the attached script to automate this - it puts the files in the correct format (modulo a little path massaging if necessary). What I do when I run across these problems is this: % bitbake

Thanks for a clear explanation. This is an area I'm sure my customers will struggle with. I think another problem I was having was the recipe was called helloworld, but the application seems to be

In this case, the LIC_FILES_CHKSUM is storing the md5sum of the COPYING file, which is stored in the top-level directory of the extracted sources. So manually download the hello version you are

Now I have gotten by the fetching but the license file information in the .bb file from the example is incorrect. I can't see from the Reference manual License section enough information for me to

Duh! Now that makes sense. Sorry for being so dense. That's what happens when your been programing since Fortran was at the 1.0 level. Brain goes soft. Jim A

If you look in: ftp://ftp.gnu.org/gnu/hello/ you'll see which versions are available. Rename your recipe filename to reflect the version you wish to use, for example helloworld_2.7.bb The part of

I got the layer created like you said, but the test had a fetch problem and it just locked up there. Had to control-C out of it. Console below: jim@ubuntu-x64:/build/mycdv-minimal$ bitbake

On 01/26/2012 01:55 PM, Scott Garman wrote: I got the layer created like you said, but the test had a fetch problem and it just locked up there. Had to control-C out of it. Console

Every distro defines their own policies for images and there ought to be differences its normal.

Hi Jim, The best way to do this is to create your own layer, and keep all of your customizations there. You'd put this in a directory, say meta-jfa with something like the

I'm not building minimal. I built core-image-minimal and it truly was minimal. Nothing in /usr/lib! Next I build core-image-base. Most of the Angstrom & Arago images I've build that were

From: Kishore Bodke <kishore.k.bodke@...> Add smp feature to linux-yocto-rt_3.0. Signed-off-by: Kishore Bodke <kishore.k.bodke@...> --- .../linux/linux-yocto-rt_3.0.bbappend

From: Kishore Bodke <kishore.k.bodke@...> Hi, The patch is for enabling the smp feature for the rt kernel build for the Cedartrail BSP. Please pull into master. Thanks Kishore. The

http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#usingpoky-configuring-LIC_FILES_CHKSUM

Because you asked to build an absolutely minimal root file system. In this case, it's expected that you don't want to have opkg available. If you still want this very minimal system *and* opkg, just

Not necessarily. The way our rootfs construction works, it has to be done via some package management backend, but many people don't want/need it in their final image. FYI some image recipes default

OK, I want to hear that story :) Regards, Brian

I'm trying to understand the concept of creating a recipe and having it included in the build I do. For example, suppose I want to create the meta-intel/meta-cedartrail BSP with the

this means thats what format you want for package to be spitted out. weather you want online (on device) package management is a different story