Targets such as sdk_google_phone_{x86,arm,...}-sdk
have wrong size and sha1sum in the repo-sys-img.xml,
because the sdk_repo.mk file incorrectly over-writes
the final images zip.
bug: 20927015
Change-Id: I151c8759c299d4a943f00ca2734ef65dea727262
Change the sdk_repo rule to generate a system-image zip package and its
corresponding XML for the addon.
Change-Id: I3c2318d2085362f62784415713b44cc8fe97ea9c
This allows to have a different rule to generate the source.properties
based on the templates and place them in a directory that depends on
the current target CPU ABI. In turn this prevents the build from
mixing different source.props when building different targets.
Change-Id: I4a1d9f47426c94f376947ddae8be9f5549331616
This makes sure that sdk-repo-*.zip doesn't exist to
avoid merging into an existing one.
Also fix a warning when generating the repo.xml files.
Change-Id: I645ad13936b83c5c33bd84c046b60b77488b9113
The latest version of the repository XSD changes:
- archive attributes (os/arch) are now element (host-os)
- system images are not longer in the repository.xml and
get their own XML file.
Change-Id: If5820a84d5c754b816b17b5713bbdb2597736eff
The makefile for sdk_repo looks for the repository/addon XSD files in the tree,
these paths needed to be adjusted due to the recent reorganization.
Change-Id: I50120542f78dc72da51b4d5377214c064ec68c01
When building the sources.zip for the SDK Repository,
the --exec-zip argument seems to be have been lost with
recent merges. Without this flag, the sources.zip is
not valid on some platforms.
Change-Id: I589df3d6df7890e0fccf568a03a76e6985ecb534
This generates a repository in either v5 or v6 and adjusts
the name/vendor attributes accordingly.
This extracts the support extra in a separate 'repo-extras.xml'
which has an addon.xsd type instead of being a repository.xsd.
Requires sdk.git change Ib0363f06 to build properly.
Change-Id: I250fe7a3ec0dfa490778ae747a1a8f4e536bb395
This adds support for "templates" source.properties files that can
inherit the platform version/codename/api level from the build.
The purpose is for a given build to always generate SDK files that
match the platform generated in the same branch.
Change-Id: Id623bbef45a04d953da8eade7e8c34c77709f9c3
Also fix packaging of system image (it had an extra root
directory in it, e.g. it was packaging android-4/armeabi-v7a/
instead of just armeabu-v7a/)
Change-Id: I0254b2680168d25103222f8871b2af37a7406b58
Also:
- in the images_*_source.props, we can't have the platform
version name (the human readable string). It's not a valid
property of the XML.
- disable the included-abi in the platform.
Change-Id: I3db62fde5e436bbe8f8e69eb1495ca4e6b954ba2
When the "sdk_repo" modified is used during the SDK build,
this also generates the repository.xml and addon.xml files
for the new SDK repository packages and places them in
the DIST_DIR.
Example usage:
make -j 16 PRODUCT-sdk-sdk showcommands sdk_repo dist DIST_DIR=/dist/sdk
make -j 16 PRODUCT-google_sdk-sdk_addon showcommands sdk_repo dist DIST_DIR=/dist/addon
Change-Id: Ibaad66f4b1cc476a4146afde7087a10a0557f74c
When the build is invoked with the fake target "sdk_repo" and
a main target of sdk, win_sdk or sdk_addon, we now create
packages in DIST_DIR that can directly be used to populate the
SDK Repository.
This is quite close to how we actually distribute the SDK.
Change-Id: I01c729eff4dbc1eccbc7c5b1869f329363f1ce07
