You can get rid of most of the disk usage by deleting the work directory (but
see below) I suspect that if you are done, stamps, pkgdata, and probably cache
are also unnecessary. You'll only need cross and staging if you want to build
things for it, and rootfs is is probably tar.gz'ed (or something) under deploy.
To simply use the files you only need deploy, to compile you need cross and
staging. So far as I understand it, anyway.
> 2) If I am building a different kernel (like MontaVista), using 'make'
> instead of 'bitbake', I can configure the kernel using "make gconfig" to
> edit the .config file. Is there a similar mechanism using bitbake, or do
> I need to edit the config files (which I think are stored as
> 'defconfig') by hand?
>
> 3) Is there an automatic way to extract the kernel source from bitbake
> into a tree that is buildable via the standard kernel build tools using
> "make", or is that not something that is designed to be possible?
Bitbake ends up using the standard kernel build process, it just copies a
completed .config file shipped along with the build recipe. My kernel files
are found under tmp/work/beagleboard-angstrom-linux-gnueabi/linux-omap-*/git
In principal you can modify the config file as you normally would and rebuild.
You can use
bitbake -c compile -f linux
bitbake linux (or bitbake console-image to rebuild the whole thing)
Or if you want to build yourself, you can bitbake devshell to get a shell
script that can be source'd to provide OE environment variables and macros.
The result is in tmp/deploy/glibc/addons.
--
Justin Love
Creative Electronics & Software
650 Sundown Road
South Elgin, IL 60177
Phone (847) 695-0023
FAX (847) 695-0483