[android-building] Unable to download content during build

2019-10-15 Thread Michael Goffioul
I have several custom modules that download content (if not already present) during build, with wget. This uses additional rules in the corresponding Android.mk files. These used to work in Pie, but in Q the rule fail with "Name or service not found". Running the exact same command outside the

[android-building] Re: Android.bp to support architectural files

2019-10-15 Thread Akanksha
Thank you On Thursday, October 10, 2019 at 1:39:51 AM UTC+5:30, Akanksha wrote: > > Suppose say a module has name - x and compile_multilib =32 and other > module has name - x and compile_multilib = 64. When executed this would > result in module duplication? How can this duplication be solved?

Re: [android-building] Benchmarktest64 directory

2019-10-15 Thread 'Colin Cross' via Android Building
That's not surprising, none of our internal workflows involve flashing the built userdata.img, as that would effectively wipe all the data on the device. We always use adb push (that's what the atest tool does) or adb sync to run tests and benchmarks. I think a patch to update fs_config would be

[android-building] Re: repo 1.26 cause AOSP sync break..

2019-10-15 Thread jw wang
Hi Mr. Li following are the information, any wrong doing ? LC_PAPER=lzh_TW LC_ADDRESS=lzh_TW LC_MONETARY=lzh_TW LC_NUMERIC=lzh_TW LC_TELEPHONE=lzh_TW LC_IDENTIFICATION=lzh_TW LANG=en_US.UTF-8 LC_MEASUREMENT=lzh_TW LC_TIME=lzh_TW LC_NAME=lzh_TW On Tuesday, October 15, 2019 at 12:46:33 AM UTC+

[android-building] How to add relative path for srcs:[] in Android.bp

2019-10-15 Thread ____
hello, say in a Android.bp file srcs:["../../../a.cpp"] I am getting the error Path is outside directory "../../../a.cpp"? How to overcome this? Later I tried declaring Android.bp in to a parent folder so that srcs:["a.cpp"] but then , FAILED: build/make/core/base_rules.mk:325: error: /gps-noshi

Re: [android-building] Benchmarktest64 directory

2019-10-15 Thread Paul Elliott
Hi Colin, We're just building the data image and loading that, not using adb sync, which potentially explains the differences. If I look at the data image I can definitely see that the permissions are wrong. Paul. On Monday, October 14, 2019 at 11:22:28 PM UTC+1, Colin Cross wrote: > > How are