Lots of people (myself included) have said, I'd love to help make OZ better but don't have the time or know-how to set-up the build environment.
This mini-project attempts to help by making it as easy as running a QEMU virtual machine, logging in and typing 'bitbake oe-image'.
Requirements: - QEMU for
Windows or
Linux- My Debian BitBake QEMU image (using
Azureus):
magnet:?xt=urn:btih:7YPQB3DWM3ARTZE3JL4FMLKL7FT7MT5H
(this file will grow to be ~5.5GB as you build) Note: This image file will likely be updated/replaced very soon.
- A fast computer would be helpful...
Instructions- Uncompress the disk image (you can use
7-zip on Windows)
- Start QEMU with using the image file as your -hda
- I used 192MB, but you could proably get away with 96 to 128MB of QEMU RAM
- Optional: use -redir tcp:22::22 with QEMU and then you can ssh to localhost and get into the image using
PuTTY, if you have an SSHd running on localhost either turn it off or change the port parameter mapping to something else.
- login with bitbake/bitbake
- edit ~/bb/build/conf/local.conf -> uncomment line TARGET_OS="linux" and save
- cd ~/bb/build
- bitbake oe-image
- in Windows I recommend using task manager to set the QEMU.exe task to low priority, then minimize and check back with QEMU every half an hour to see how it's progressing... (it takes a long time to initially pull all the bb packages to local cache)
Update - May 30:Bitbake 1.3.0 requires almost 256MB exactly to work as a build environment... this is much reduced from the previous 700MB (RAM+SWAP) that was previously required...
Things move much faster when SWAP can be avoided on QEMU...
Hopefully, I'll be able to get a better bitbake image done soon... just trying a build with the ASSUME_PROVIDES="virtual/gcc-arm-linux-2.95" as per the suggestion in this bug (This bug (
http://bugs.openembedded.org/show_bug.cgi?id=29 ) has kept me from building successfully lately, but hopefully adding), if this succeeds I'll clean and pack this image.