And adjust a few things while I'm at it

Co-authored-by: Michael Bestas <mkbestas@gmail.com>
Change-Id: I9972653845c64aab944d0289d9357361e2feb344

* Makes defaults available to other places than just bootanimation

Change-Id: I6865bdd08e7f3d9370ce8578691f52204d57fde7

Change-Id: I49301cf09f79d617868ac3d445d243020b587c9d

Change-Id: Ib0b363c3e0545cb0c86dc69dd1a75f82dd777e59

If the build is invoked off-tree, like:

    . build/envsetup.sh
    export OUT_DIR=/some/other/dir/out
    export DIST_DIR=/some/other/dir/dist
    breakfast chagalllte
    mka \
        target-files-package dist

the bootanimation.zip is correctly generated in $OUT_DIR.

However, if the user overrides directories after breakfast, i.e:

    . build/envsetup.sh
    breakfast chagalllte
    mka \
        OUT_DIR=/some/other/dir/out \
        DIST_DIR=/some/other/dir/dist \
        target-files-package dist

the destination path of intermediate bootanimation.zip is still
controlled by $ANDROID_PRODUCT_OUT which is set by build/envsetup.sh.
This leads to a copy error and a failed build.

The fix overrides $ANDROID_PRODUCT_OUT by the always-known PRODUCT_OUT
(make variable defined in build/core/envsetup.mk), making it error-prone
to environment variable declaration.

Also, the "sh" invocation is replaced with generic make-variable
$(shell).

Change-Id: Ic94d1b538fc01946b628f9b5d776548a03acde97
Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

* Generic AOSP devices don't set it and we don't really
  want to fork them just to set the bootanimation size.

Change-Id: I684454ae07348ee29c832f86f56bcfbd4f627b4d

Change-Id: Ic102e49d39a12116e9a0b25accf0ef81520c495f

Change-Id: I2df13091f5d62b552ef434aef1a389f4fe1249e0

This reverts commit 430f569d.

Change-Id: I99c4245625629940d83fe535fbdb79fe1b9b4887

Change-Id: If1605830592dd6cfccd0a06d94736f4e5e09eb7d

We're no longer using convert, but mogrify.

Change-Id: Ifd58527b49e5548dd94b35a8cf0ffa4ad5196804

Fixes bootanimation generation for Darwin/BSD.

Change-Id: Id9e38bcb9db7b550f22bda1250dbb515599e8f93

Some systems seem to have with the convert command as-is:
convert: Cannot write PNG8 or color-type 3; colormap is NULL

Because we are writing PNG8, there area a max of 256 colors total.
Explicitly telling convert to stay under the max fixes the issue.

Change-Id: I595fb4503396ca20226ea76bf7b15ed9878752fd

Change-Id: I6f2b38a64629f918b79d28ba8b1d0d6535901142

 * Make it run at 60 FPS
 * Slow down the pace to make it more relaxed

Change-Id: I563b09da875c53f1cd456606ee7a6200e8841bb1

Make sure that any changes to the boot animation can be picked up
and rebuilt by running 'mka bootanimation.zip'.

Change-Id: Ice10e919df4c1b651c5c5dbb9700cab38eeac748

Change-Id: Iff2087eb97aee5e586eecf3898f0066d99bc885c

This reverts commit e2ec4c60.

* New build server(s) will be able to support this

Change-Id: I990297e6db7aa6076199bb6344328e704b1d4ebe

The servers do not have ImageMagick installed right now,
breaking the automated builds.

Revert this for now.

This reverts the following commits:
840e7814 bootanim: Use a for loop to make part# folders
ce5405d1 Fix wrong bootanimation.zip from mkdir .../part{0..2}
6179d949 cm: Build bootanimation.zip
67ddf372 cm: Rework boot animation generation

Change-Id: I63fc43da9b1a6afea5f791e879f0bfc9a385d98d

Change-Id: Iec90f3521e589de4e8352c0349e1a0751d65d989

For some reason the mkdir command:
mkdir -p $ANDROID_PRODUCT_OUT/obj/BOOTANIMATION/bootanimation/part{0..2}
creates a directory part{0..2} instead of three separate directories.
Non-fatal build errors and a 386 byte bootanimation.zip file result.
This explicitly creates each directory.

Change-Id: Ia6ae0e4f64521992de8cc34a376af3eaac5c8819

Keep the largest bootanimation extracted
and resize it at build-time.

Change-Id: Iee32f18440ff955d13ed85b273e97cbd540721fc