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
Also merges 3ea87ca65f
'Fix XMLNS detection in SDK Repo XSD files.'
to prevent a merge conflict later on.
Change-Id: Ib14fe820dab7a60bb5412968c146c30ec5ba81c7
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
Also merges 3ea87ca65f
'Fix XMLNS detection in SDK Repo XSD files.'
to prevent a merge conflict later on.
Change-Id: Ic9832e71456d76f849406e641792f4285ffbf649
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: I671e8ff1bc2a6e9f5c097241d65da1cfdde21154
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: I4f60d3197cac8c22027534cb7686de087ddf1a90
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: I1c4a120616697383792d7fb1b328cfcefac0b2f5
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
This removes the test that makes the SDK only strip llvm-rs-cc.exe if present.
It means the SDK will FAIL if llvm-rs-cc wasn't build successfully for Windows.
Change-Id: I4c73954c30265e71e84916976f16ae76d67a8e13
Firs this fixes a cp/rm errors that were logged when building the Windows SDK.
There errors happens because the secondary sdk/tools/patch_windows_sdk.sh
was run twice.
Next the shell script is changed to make any error fatal and actually
break the build, like it should.
In the makefile, merge Ying's fix to correctly pass showcommands.
Change-Id: Iee75e42b0b0bbba3c26858c82c933660dc6d74ae
Firs this fixes a cp/rm errors that were logged when building the Windows SDK.
There errors happens because the secondary sdk/tools/patch_windows_sdk.sh
was run twice.
Next the shell script is changed to make any error fatal and actually
break the build, like it should.
In the makefile, merge Ying's fix to correctly pass showcommands.
Change-Id: I97bbe46d705c6683e31bb701222efe6f9da71d70
