Re: [RFC] make building working zaurus images easier

[Marcin Juszkiewicz <openembedded@hrw.one.pl>]

Dnia czwartek, 26 lipca 2007, Koen Kooi napisał:

> Building a working zaurus image is tedious since you have *manually*
> rename a bunch of files before the on-board flashing software will
> accept it.

+2 from me

> I therefore want to propose 2 small scripts that can be run as
> EXTRA_IMAGECMD to make life a lot easier for both developers and users:
>
> [beware of line wrapping]
>
> For c7x0:

For c7x0/poodle/tosa you mean ;)

For collie:

cd ${DEPLOY_DIR_IMAGE}
mkdir ${IMAGE_NAME}-installkit/
cp `ls zImage-2* | sort -b | uniq |tail -n1` ${IMAGE_NAME}-installkit/zImage.bin 
cp `ls ${IMAGE_NAME}.rootfs*jffs2 | sort -b | uniq |tail -n1` ${IMAGE_NAME}-installkit/initrd.bin
tar czf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit.tar.bz2 ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/
rm -rf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/

Also we should use gzip compression for installkit tarballs as this will
allow users to unpack them on devices (gzip is in busybox).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

 BSD is what you get when a bunch of Unix hackers sit down to try to port
 a Unix system to the PC. Linux is what you get when a bunch of PC hackers
 sit down and try to write a Unix system for the PC.