This image is a working OE build environment inside a QEMU disk image.
Thanks to offroadgeek for hosting:
https://www.oesf.org/howto/downloads/OE-Bit...MU-20050617.zipRequirements:- QEMU pc emulator
For Windows For Linux- A PC that can spare 256MB RAM to run the guest image
- A Disk that can spare 6GB+ space
- A day or so to build a Zaurus opie-image
- An SSH client is highly recommended (i.e.
PuTTY)
To set-up:On windows:
- Unzip into the QEMU directory (i.e. C:\Program Files\QEMU)
- start-oe-bitbake-QEMU.bat
- once "login: " appears you can SSH as user/pass: oe/oe
- read the login message / readme file (same file)
Other notes:I recommend you replace the oe-configure.sh script with the one attached to this posting (i.e. use
FileZilla to SFTP it to localhost), but it is not essential if you don't mind setting up the compile output partition yourself.
Compiled Z image output ends up in a deploy subdirectory of oe-build/build... (do a find ~/oe-build | grep deploy for exact path)
It's slow the first time through (i.e. ~18-24hrs to build everything for opie-image) but at least you can watch it doing it's thing and once built only new/unbuilt packages need to be rebuilt the next run. I'd be curious to know how fast someone can bitbake opie-image on a Linux host with KQEMU accelerator installed.
Cheers,
-Ironstorm
PS: thanks to those in IRC who help with answers to my silly questions and especially to offroadgeek for hosting.
