On 12/10/2012 06:05 PM, Alan DuBoff wrote:
On Mon, 10 Dec 2012, Alan DuBoff wrote:
As a test I'm building a systemd image to see if it builds the modules
tarball, which I believe it will...
Nope, didn't do that...no tarball...but it did build an image.
Odd thing is that I remember that being created when I first did a
virtual/kernel, so maybe I need to clean the virtual kernel and build it
again.
The do_deploy step is what actually copies the kernel to the images
directory. You can force this to happen again with:
bitbake virtual/kernel -c deploy
Not sure if you need a -f in there too (which would force the step to
run regardless of sstate stamp status).
I think something about the fact that the same kernel is often re-used
for several rootfs images for the same MACHINE is why we're more careful
about over-writing the kernel in the images directory. That's my guess.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
