AoF Install Packager script

[GoogleCodeExporter]

Created a script which will do the following:

it requires to get the path to the installer and AoF tree.
it assumes you compiled your source and binaries were created
it will validate the locations and check if the binaries are there
the files will be copied to /tmp and /tmp/boot dir
a checksum is calculated
a tarball is created
and the tmp copied files are removed again

This could help us all to create packaged installer tarballs like we use for 
daily and weekly builds.

I've tested myself step by step and it works correctly on my system.

Not very happy with the name of the script, though.

Niels.

Original issue reported on code.google.com by niels.he...@gmail.com on 16 Sep 2010 at 8:12

Attachments:

• PackageInstaller.sh

[GoogleCodeExporter]

Original comment by niels.he...@gmail.com on 16 Sep 2010 at 8:12

[GoogleCodeExporter]

I suggest to commit this script to the installer branch. Let's move on...

Original comment by niels.he...@gmail.com on 20 Sep 2010 at 8:15

[GoogleCodeExporter]

Committed, thanks! It doesn't work for non-cupcake branches, because the 
"freerunner" path is hard-coded and should be "fr" for other branches. You 
could either try both variants or use the TARGET_PRODUCT variable (which is 
what the build uses.

Original comment by scarhill on 22 Sep 2010 at 3:11

• Changed state: FeedbackPending

[GoogleCodeExporter]

Thanks for the valuable feedback, Jim.  Very good point indeed. I've only been 
working and testing on the Cupcake branch...
I will update the script to use the TARGET_PRODUCT variable and/or probe for 
the dirs if the variable is not set.

Update coming up, so status is again "started".

Original comment by niels.he...@gmail.com on 22 Sep 2010 at 8:33

• Changed state: Started

[GoogleCodeExporter]

Script ready for testing with TARGET_PRODUCT enhancements and froyo, but have 
an issue with the expected files... 

Froyo compiled and now I'm looking for the kernel.img file, which does not 
appear to exist.

I was expecting to see it under out/target/product/fr

The files uImage zImage and Image do exist under 
out/target/product/fr/obj/KERNEL/arch/arm/boot

Same question goes for the system.img and userdata.img files which I could not 
find under Froyo out/target/product/fr.

Any idea where I should be getting these three files from?

Thanks.

Niels.

Original comment by niels.he...@gmail.com on 23 Sep 2010 at 9:47

[GoogleCodeExporter]

I'm not sure why you're not getting a kernel built, but I updated some things 
tonight, so try a repo sync and let me know what happens

Original comment by scarhill on 24 Sep 2010 at 3:00

[GoogleCodeExporter]

Did a repo sync and compiled again. No issues and make ends fine. Same as 
before, but still no kernel.img, userdata.img and system.img files.

When doing a find ./ -name ".img" from my froyo build root I could only find 
ramdisk.img. Where do we need to get those other img files from?

Thanks,

Niels.

Original comment by niels.he...@gmail.com on 24 Sep 2010 at 10:54

[GoogleCodeExporter]

Again repo sync and make

Files have been created. Script successfully tested against froyo and cupcake. 
Should be good to go.

Give it a spin.

Original comment by niels.he...@gmail.com on 27 Sep 2010 at 10:22

Attachments:

• PackageInstaller.sh

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by niels.he...@gmail.com on 27 Sep 2010 at 10:34

Attachments:

• PackageInstaller.sh

[GoogleCodeExporter]

Updated and pushed

Original comment by scarhill on 28 Sep 2010 at 2:35

• Changed state: FeedbackPending