I was overriding PRODUCT_SYSTEM_DEFAULT_PROPERTIES (with ":=" instead of
"+=") which breaks the build process.
Pozdrawiam
Tomasz Witke
sob., 1 gru 2018 o 01:43 Sunny Raj napisał(a):
> Can you justify what you did to fix it?
>
> On Wednesday, 6 December 2017 02:06:29 UTC+5:30, Tomasz Witke wrot
Can you justify what you did to fix it?
On Wednesday, 6 December 2017 02:06:29 UTC+5:30, Tomasz Witke wrote:
>
> Found the reason. I was using PRODUCT_SYSTEM_DEFAULT_PROPERTIES := in
> device tree after including core_minimal.mk. Thanks for pointing me to
> runtime_libart.mk!
>
>
> W dniu ponied
Found the reason. I was using PRODUCT_SYSTEM_DEFAULT_PROPERTIES := in
device tree after including core_minimal.mk. Thanks for pointing me to
runtime_libart.mk!
W dniu poniedziałek, 4 grudnia 2017 16:06:17 UTC+1 użytkownik Tomasz Witke
napisał:
>
> Well, I checked it twice, and values in runtim
Well, I checked it twice, and values in runtime_libart.mk are present, and
I follow core_minimal.mk. Digging deeper I notices that, boot frameworks
are 0 bytes in size. What could possible happen?
kyvaith@ubuntu:~/android-x86/out/target/product/x86/dex_bootjars/system/framework/x86$
ls -la
tot
The -Xms and -Xmx options being passed to dex2oat by the build are blank.
The build system gets the values to use there from
https://android.googlesource.com/platform/build/+/b8e08222d9798c4f39d4d2c37bcd111bbc02f2ba/target/product/runtime_libart.mk?pli=1#62,
which is included by
https://android.goo
Everything was good til yesterday. I do't know what is going on..
[ 0% 23/12072] target dex2oat:
out/target/product/atv/dex_bootjars/system/framework/x86/boot.art
FAILED: out/target/product/atv/dex_bootjars/system/framework/x86/boot.art
/bin/bash -c "(mkdir -p
out/target/product/atv/symbols/sy
