summaryrefslogtreecommitdiffstats
path: root/tools/releasetools/img_from_target_files.py
Commit message (Collapse)AuthorAgeFilesLines
* img_from_target_files: Skip oem.img in fastboot image creationBrint E. Kriebel2016-04-181-6/+3
| | | | | | | | We don't need this package to be included in fastboot images, so skip it when we are creating fastboot images. Change-Id: I1e0676f5cbf7468088e6997f83ae845578864668 Ticket: CYNGNOS-936
* build: Create a oem image when BOARD_OEMIMAGE_FILE_SYSTEM_TYPE is definedDiogo Ferreira2016-04-151-0/+6
| | | | | | | | | | This adds the capability of generating a OEM image with the build and adding it to target files when BOARD_OEMIMAGE_FILE_SYSTEM_TYPE is set. Change-Id: I6c596d58d9d5ece1a261d953eeb8c60eac30e642 Ticket: CYNGNOS-936 (cherry picked from commit 1966a9e7c22b95eb4c16be6aee7adf43cb6ce118)
* py3: update all the thingsAnthony King2016-01-041-9/+11
| | | | Change-Id: I5e11b46b7c2f7f8760d6c0e713ca99c1e88b7cd3
* img_from_target_files: Imports added to fix the scriptJessica Wagantall2015-12-041-0/+4
| | | | Change-Id: Ib9e43c9d0a067106f5d554b7ea2fa414ce93a55b
* build: Fix extra userdata generationBrint E. Kriebel2015-11-071-0/+2
| | | | | | | | | | | | | | | | | Image generation has been combined into the target file script and requires the prefix parameter to work properly. This also needs to be called properly when creating fastboot packages. Change-Id: I1f716cc375ffe401d5f18487330fc9bb809ff3b4 Ticket: OPO-191 build: Fix extra userdata generation some more Use the prefix variable when placing the file in the target files package. Change-Id: Ia4b795416b58c493c3ea91b964e3b6f4cdf0fef1 Ticket: OPO-191
* releasetools: Add radio images to fastboot packagesBrint E. Kriebel2015-10-061-0/+26
| | | | | | | | Fastboot packages should include radio images, if they exist. Also generate a flash-radio.sh file if a filesmap file exists to indicate the partition that a radio image should be flashed to. Change-Id: I8f603b1509a5c1b55fee1cb6f6a49a7efb8cc594
* Wrap zipfile.write(), writestr() and close()Tao Bao2015-05-081-9/+4
| | | | | | | | | | In order to work around the zip 2GiB limit, we need to wrap the related functions in zipfile. Calls to those functions should always be replaced with calls to the wrappers instead. Bug: 18015246 Change-Id: I499574cee51ec4804bc10cbefe0b17940afed918 (cherry picked from commit 2ed665a033c587b276b1615516e5354e2ace47cd)
* Make releasetools pylint clean.Dan Albert2015-03-241-11/+3
| | | | | | | | This caught a few bugs/syntax errors (a few character classes were not escaped properly in regex patterns, some indentation was illegal, etc). Change-Id: I50637607524e68c4fb9cad7167f58a46b8d26b2c
* Allow system images larger than 2GiB, pt. 2Greg Hackmann2015-03-231-0/+6
| | | | | | | | | | | We need to patch zipfile during close() too, because it refers to the ZIP64 file size threshold when writing out the central directory Bug: 18015246 Bug: 19888174 Change-Id: I1b49d653d0831fcc2106808f86c929d7a2b22ff3 Signed-off-by: Greg Hackmann <ghackmann@google.com>
* Allow system images larger than 2GiB.Dan Albert2015-03-191-5/+7
| | | | | | | | | | | | | | | | | | | | | | Python 2.7's zipfile implementation wrongly thinks that zip64 is required for files larger than 2GiB. We can work around this by adjusting their limit. Note that `zipfile.writestr()` will not work for strings larger than 2GiB. The Python interpreter sometimes rejects strings that large (though it isn't clear to me exactly what circumstances cause this). `zipfile.write()` must be used directly to work around this. This mess can be avoided if we port to python3. The bug (b/19364241) in original commit has been fixed. Bug: 18015246 Bug: 19364241 Bug: 19839468 (cherry picked from commit cd082d4bfe917b2e6b97436839cbbbc67c733c83) Change-Id: I7b5cc310e0a9ba894533b53cb998afd5ce96d8c6
* save file block allocations in target_filesDoug Zongker2014-08-121-0/+1
| | | | | | | | | make_ext4fs can now output a file listing the blocks used for each file in the image. Request this file and save it in the target_files; it will be used for future improvements to block OTAs. Bug: 16984795 Change-Id: Id1e60465e3b5a9d126a7934b4d089cf34d8fec44
* store images in target-filesDoug Zongker2014-07-311-211/+63
| | | | | | | | | | | | | | | | | | | | | | Store sparse images in the target-files, and use those (when they're available) for building block OTAs. - New script add_img_to_target_files is added to make the images and add them to the IMAGES/ subdir in the target-files. It gets run from the Makefile when building a target-files. - img_from_target_files becomes mostly vestigial: it creates the img.zip by just copying the images out of the target-files. (It still knows how to build images for use on older target-files.) - ota_from_target_files uses images from the target-files in preference to rebuilding images from the source files. - sign_apk_target_files builds images and includes them in its output target files (even if the input target-files didn't have them). Bug: 16488065 Change-Id: I444e0d722d636978209467ffc01750a585c6db75
* releasetools: only allow yaffs to have no userdata image size (fix build)JP Abgrall2014-06-261-2/+3
| | | | | | | | | | In the past, there was an exception for ext-base fs types to deal with the lack of image size. Back then it was only yaffs and ext*. So now we explicitely only allow yaffs to have no userdata image size. Change-Id: Ie354ee6222a58228dbcce2c6934971a0737422af Signed-off-by: JP Abgrall <jpa@google.com>
* full support for OTA of vendor partitionsDoug Zongker2014-06-161-50/+40
| | | | | | | | | | | | | | | | | | Make vendor partition a first-class member of the OTA system (for target_files that contain a VENDOR/ subdirectory). Build vendor images in a way that is compatible with block-based OTA. Support updating the vendor partition in both full and incremental, block and file OTAs. In most cases this is handled by refactoring the existing code to handle the system partition to handle either, and then calling it twice. Currently we don't support incremental OTAs from a target-files without a VENDOR subdirectory to one with one, or vice versa. To add or remove a vendor partition a full OTA will need to be done. Bug: 15544685 Change-Id: I9cb9a1267060bd9683a9bea19b43a26b5a43800d
* use fs_config and file_contexts from target_filesDoug Zongker2014-06-161-1/+10
| | | | | | | | When building images, we want to use the file_contexts and fs_config data contained in the target_files zip, rather than whatever happens to be in the current client. Change-Id: I13df2405898039f5a9b4bb4837147e76b31b068a
* Allow to build the update.zip for emulator build.Ying Wang2014-06-031-5/+8
| | | | | | | | img_from_target_files.py just skipps the boot.img and recovery.img since there is no kernel or recovery.fstab for emulator. Bug: 15383279 Change-Id: I4035193e6ab933194ff1417dfae4eab963fe5301
* Reopen temporary system image to avoid stale data.Geremy Condra2014-05-131-2/+1
| | | | | | | | | | | | NamedTemporaryFile's aggressive caching behavior can cause an issue where changes made by another process aren't visible even after the fseek() below or a flush(). To avoid this, simply open the file again and read from the fresh version. This fixes an issue where verity metadata written by append2simg doesn't become visible to img_from_target_files. Change-Id: I291fb3a95d5b532218ac6205ecc9e9b4f3a36bd4
* handle don't care regions in the system imageDoug Zongker2014-03-031-2/+21
| | | | | | | | | | | | | The system partitions has regions that we shouldn't write and can't depend on the contents of. Adds a new script to generate a map of these regions (using the sparse image as input), and include the map in the package zip so it can be used when writing or patching the system partition. Also fixes a bug where the wrong SELinux file contexts are used when generating incrementals. Change-Id: Iaca5b967a3b7d1df843c7c21becc19b3f1633dad
* Merge "Add support for block incremental OTAs"Geremy Condra2014-02-201-7/+10
|\
| * Add support for block incremental OTAsGeremy Condra2014-02-201-7/+10
| | | | | | | | Change-Id: Ie72015e34ed8d7595a5c74c8df41cba73275afab
* | bump releasetools python requirement to 2.7Doug Zongker2014-02-181-2/+2
|/ | | | | | | These scripts already use some post-2.4 features, so let's make it official: Python 2.7 is needed to run them. Change-Id: I256e9ed99b0b62abe4e22a7b1f811acb7419e88e
* make full OTAs block basedDoug Zongker2014-02-041-0/+279
Instead of writing individual files and fixing up their metadata, make full OTAs contain a system image and simply write it to the block device. This is only done for target-files that already contain the recovery flashing information, older target-files still get a file-based full OTA. Bug: 12893978 Change-Id: If7586083c8f275e24fec49d260af5b5aff4a0a88
generated by cgit v1.1 at 2025-01-08 16:22:58 +0000