Re: [android-building] Need help exposing library / class paths in AOSP P (Android 9) from my own .jar file inside vendor

['Colin Cross' via Android Building]

You can set PRODUCT_BOOT_JARS in your product makefile to add a jar to the
bootclasspath, but I'd suggest providing it as a library that the apps that
need it can load.

On Mon, Apr 15, 2019 at 8:06 AM Elliott Mazzuca  wrote:

> I tried to give a specific title and i will elaborate a bit more:
>
> *What i am trying to do is expose the classes that are inside my jar file
> so they are on the default class path.*
>
> I have a sample app to test if this is working that i created that would
> uses these classes.  But they don't appear in the images class path.  so i
> get a "ClassNotFound Exception" when i try to instantiate.
>
>
>
>
> I have a custom .Jar file where i have my own package, lets call
> it com.sample.myCustomLibrary
>
> This jar file is created in the vendor space in AOSP P (android 9) using
> an Android.bp file.
>
>
> inside my Android.bp file, i have a "java_library"
>
> that looks like this:
>
> // myCustomLibrary.jar
> java_library {
> name: "com.sample.myCustomLibrary",
> owner: "sampleOwner",
> installable: true,
>
>
>
>
> javacflags = [
> "-Xmaxwarns 999",
> ],
>
>
> srcs: [
> "lib/src/main/java/**/*.java",
> ],
>
>
> dxflags: [// not sure if i need this, but it
> didn't work
> "--core-library",
> "--multi-dex",
> ],
>
>
> optimize: {
> proguard_flags_files: [
> "lib/src/main/proguard-rules.pro",
> ],
> },
>
>
>
>
> vendor: true,  // not sure if i need this but it didn't work
> dex_preopt: {  // not sure if i need this but it didn't work
> app_image: true,
> },
> }
>
>
>
>
>
> I also added some of the classes to "preloaded-classes"  under
> frameworks/base/config/preloaded-classes
>
>
> When i create a new AOSP build, i can see that the classes that i put into
> this "preloaded-classes" file are not exposed:
>
>
> W/Zygote: Class not found for preloading:
> com.sample.myCustomLibrary.sampleClass1
> W/Zygote: Class not found for preloading:
> com.sample.myCustomLibrary.sampleClass2
> W/Zygote: Class not found for preloading:
> com.sample.myCustomLibrary.sampleClass3
>
> and i added the package to the
> /build/make/core/tasks/check_boot_jars/package_whitelist.txt
>
> com\.sample\.myCusomLibrary
>
> though i can't get my classes inside my pacakge to show up on the default
> class path.
>
> Any ideas on the missing steps i need to take?
>
> thanks!
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Need help exposing library / class paths in AOSP P (Android 9) from my own .jar file inside vendor

['Colin Cross' via Android Building]

PRODUCT_BOOT_JARS can't be set in your Android.mk, it has to be set in your
product makefiles that are selected by your lunch target.

On Mon, Apr 15, 2019 at 11:20 AM Elliott Mazzuca  wrote:

> Thaks for the fast reply Colin!
>
> I tried adding the suggested change into my local Android.mk file and now
> i get the following issue:
>
> vendor//sample/mycustomelib/apk/anotherSampelFolder/*Android.mk:20*:
> error: cannot assign to readonly variable: PRODUCT_BOOT_JARS
>
>
> why is this considered a readonly variable?  is there a prerequisite step
> i need to do before setting this?
>
> thanks again!
>
> On Monday, April 15, 2019 at 12:48:37 PM UTC-4, Colin Cross wrote:
>>
>> You can set PRODUCT_BOOT_JARS in your product makefile to add a jar to
>> the bootclasspath, but I'd suggest providing it as a library that the apps
>> that need it can load.
>>
>> On Mon, Apr 15, 2019 at 8:06 AM Elliott Mazzuca 
>> wrote:
>>
>>> I tried to give a specific title and i will elaborate a bit more:
>>>
>>> *What i am trying to do is expose the classes that are inside my jar
>>> file so they are on the default class path.*
>>>
>>> I have a sample app to test if this is working that i created that would
>>> uses these classes.  But they don't appear in the images class path.  so i
>>> get a "ClassNotFound Exception" when i try to instantiate.
>>>
>>>
>>>
>>>
>>> I have a custom .Jar file where i have my own package, lets call
>>> it com.sample.myCustomLibrary
>>>
>>> This jar file is created in the vendor space in AOSP P (android 9) using
>>> an Android.bp file.
>>>
>>>
>>> inside my Android.bp file, i have a "java_library"
>>>
>>> that looks like this:
>>>
>>> // myCustomLibrary.jar
>>> java_library {
>>> name: "com.sample.myCustomLibrary",
>>> owner: "sampleOwner",
>>> installable: true,
>>>
>>>
>>>
>>>
>>> javacflags = [
>>> "-Xmaxwarns 999",
>>> ],
>>>
>>>
>>> srcs: [
>>> "lib/src/main/java/**/*.java",
>>> ],
>>>
>>>
>>> dxflags: [// not sure if i need this, but
>>> it didn't work
>>> "--core-library",
>>> "--multi-dex",
>>> ],
>>>
>>>
>>> optimize: {
>>> proguard_flags_files: [
>>> "lib/src/main/proguard-rules.pro",
>>> ],
>>> },
>>>
>>>
>>>
>>>
>>> vendor: true,  // not sure if i need this but it didn't work
>>> dex_preopt: {  // not sure if i need this but it didn't work
>>> app_image: true,
>>> },
>>> }
>>>
>>>
>>>
>>>
>>>
>>> I also added some of the classes to "preloaded-classes"  under
>>> frameworks/base/config/preloaded-classes
>>>
>>>
>>> When i create a new AOSP build, i can see that the classes that i put
>>> into this "preloaded-classes" file are not exposed:
>>>
>>>
>>> W/Zygote: Class not found for preloading:
>>> com.sample.myCustomLibrary.sampleClass1
>>> W/Zygote: Class not found for preloading:
>>> com.sample.myCustomLibrary.sampleClass2
>>> W/Zygote: Class not found for preloading:
>>> com.sample.myCustomLibrary.sampleClass3
>>>
>>> and i added the package to the
>>> /build/make/core/tasks/check_boot_jars/package_whitelist.txt
>>>
>>> com\.sample\.myCusomLibrary
>>>
>>> though i can't get my classes inside my pacakge to show up on the
>>> default class path.
>>>
>>> Any ideas on the missing steps i need to take?
>>>
>>> thanks!
>>>
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, vis

Re: [android-building] How to do a make clean for a single module

['Colin Cross' via Android Building]

Try rm -rf out/soong/.intermediates//

On Wed, Apr 17, 2019 at 10:05 PM Peter Stephens  wrote:

> I need to clean out my module so that I can do static analysis on the
> code.  The analysis too needs to "observe" a build for my module.  How is
> this achieved with the new (soong) build system?
>
> - Pete
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] android.jar does not contain all the class files?

['Colin Cross' via Android Building]

android.jar only contains classes that are part of the public SDK.  You can
see the AOSP source for UiAutomationConnection.java at
https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/UiAutomationConnection.java
.
The @hide annotation in the javadoc marks it as a private platform API,
which is why it is not visible in android.jar.

On Fri, May 3, 2019 at 1:37 PM  wrote:

> I downloaded the offical SDK and unzip it. What I am interested in is
> UiAutomationConnection.java(.class) but I do not see it. However, I do see
> UiAutomation.class. Any thoughts?
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Add prebuilt jar to system image - android 9.0

['Colin Cross' via Android Building]

What is in the jar, class files or dex files?

On Tue, May 7, 2019 at 12:42 PM Vinayak Soni 
wrote:

> Hi Colin,
>
> How to write an Android.bp for a prebuilt jar that needs to be added to
> PRODUCT_BOOT_JARS?
>
> Thanks,
> Vinayak
>
> On Monday, March 18, 2019 at 3:36:17 PM UTC-7, Colin Cross wrote:
>>
>> The basics on Android.bp files are documented at
>> https://android.googlesource.com/platform/build/soong/+/master/README.md,
>> and the documentation on the module types and their properties is at
>> https://ci.android.com/builds/latest/branches/aosp-build-tools/targets/linux/view/soong_build.html
>> .
>>
>> On Mon, Mar 18, 2019 at 2:52 PM KarenL  wrote:
>>
>>> I actually have everything in vendor and I'd prefer to keep it there.
>>> I'm not sure how to include whats in vendor in framework.jar.
>>> This is the structure of the stuff I have in vendor that I would like to
>>> include.
>>> vendor/xxx/lib -> the prebuilt jars are here
>>> vendor/xxx/src/com/aaa/bbb/ccc => the source files are here
>>>
>>> Question: Should I add an Android.bp to vendor/xxx/
>>> It sounds like that should contain the java_import section you already
>>> mentioned.
>>> How do I include the source files in the new Android.bp?
>>>
>>> Question: How do I reference this not module from Android.bk in
>>> frameworks/base/Android.bp?
>>>
>>> Is there any documentation on how to set up Android.bp files. I've been
>>> looking around and I cant find anything.
>>>
>>> I need the extra classes because I'm adding a new system service to the
>>> build that I'm making.
>>>
>>> Thank you again for your help.
>>>
>>>
>>>
>>> On Monday, March 18, 2019 at 2:33:13 PM UTC-7, Colin Cross wrote:

 All of that is up to you.  All Android.bp files found in the tree are
 parsed, so you can create a directory anywhere (maybe under vendor/ so you
 can minimize changes to AOSP files).  Put the prebuilt jars in that
 directory too.

 static_libs takes a list of module names.
 android.hardware.radio-V1.0-java is a module created
 by hardware/interfaces/radio/1.0/Android.bp.  The modules can be defined
 anywhere in the tree.

 Taking a step back, what are you trying to accomplish?  Why do you need
 extra classes in framework.jar?  Maybe it would be better to keep them
 outside framework.jar but add them to the default classpath using
 PRODUCT_BOOT_JARS?  Or ship them as a separate shared library that apps can
 opt into loading?

 On Mon, Mar 18, 2019 at 1:34 PM KarenL  wrote:

> What directory should my prebuilt jars go into? Where are the pother
> static_libs, like android.hardware.radio-V1.0-java, picked up from?
> Where do I add this new Android.bp with the below content?
>
> All I want to add to framework.jar are 2 prebuilt jars and 2 source
> files. Do I need to create a new folder structure under frameworks/base 
> for
> these? If so - what does that structure look like.
>
> Thank you for your help.
>
>
>
> On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:
>>
>> You need to use java_import modules to create a module for the jars.
>> Something like:
>>
>> java_import {
>> name: "my_prebuilt_jars",
>> jars: [
>> "my_prebuilt_jar1.jar",
>> "my_prebuilt_jar2.jar",
>> ],
>> }
>>
>> Then you can add to static_libs:
>> "my_prebuilt_jars"
>>
>> On Mon, Mar 18, 2019 at 12:35 PM KarenL  wrote:
>>
>>> Hi
>>>
>>> I would like to add a couple of prebuilt jars and some source files
>>> to the Android 9 aosp image that I"m building.
>>> With lower versions of Android I've added these easily to
>>> frameworks.jar. This was straight forward to do when framework.jar was
>>> built using a make file. Its a lot less clear how to do this using
>>> blueprint files and soong.
>>>
>>> This is what I've tried and its not enough.
>>>
>>> Add a new folder to frameworks/base for my source files:
>>> frameworks/base/myfolder/java/com/xxx
>>>
>>> Edit the Android.bp file in frameworks/base and add source files to
>>> the "srcs" list
>>> "myfolder/java/com/xxx/source1.java"
>>> "myfolder/java/com/xxx/source2.java"
>>>
>>> Edit the "static_libs" list and add my prebuilt jars
>>> "prebuilt_jar1",
>>> "prebuilt_jar2",
>>>
>>> I'm not sure where to put these prebuilt jars.
>>> Do they go somewhere inside myfolder? Where are the other static
>>> libs in this list picked up from?
>>> Do I need to create .bp files inside myfolder to build this new part?
>>>
>>> Do you have any suggestions as to how to add prebuilt jars to
>>> Android 9.
>>>
>>> Thanks for your help.
>>> Karen
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>>

Re: [android-building] avbtool: command not found

['Colin Cross' via Android Building]

Did you run source build/envsetup.sh and lunch as described at
https://source.android.com/setup/build/building?

On Wed, May 8, 2019 at 9:02 AM Michael Burrows 
wrote:

> Hey guys. My computer with ubuntu crashed which resulted in me not being
> able to run avbtool command
>
> I have my AOSP folder named AOSP.
>
> I run the *make avbtool *command inside that folder as follows:
>
> /AOSP$ make avbtool
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=9
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.18.0-17-generic-x86_64-Ubuntu-18.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PQ2A.190305.002
> OUT_DIR=out
> 
> ninja: no work to do.
> ninja: no work to do.
> No need to regenerate ninja file
> No need to regenerate ninja file
>
> ninja: no work to do.
>
> When I try using the avbtool to get information about my system.img
>
> *AOSP$  avbtool info_image --image system.img *
> avbtool: command not found
>
> running the ls command shows avbtool.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/31b3b212-22ce-48ea-a327-89c38842389f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRQ0%3D9rfikhTmj8HXp%2BBnAxR-8EB42_Yn08qGuzAimCf5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Add prebuilt jar to system image - android 9.0

['Colin Cross' via Android Building]

You can probably use something like:

java_import {
name: "mylibrary-jar",
jars: ["mylibrary.jar"],
}

java_library {
name: "mylibrary",
static_libs: ["mylibrary-jar"],
installable: true,
}

On Mon, May 13, 2019 at 6:36 PM Vinayak Soni 
wrote:

> Classes.
>
> On Tuesday, May 7, 2019 at 1:22:15 PM UTC-7, Colin Cross wrote:
>>
>> What is in the jar, class files or dex files?
>>
>> On Tue, May 7, 2019 at 12:42 PM Vinayak Soni  wrote:
>>
>>> Hi Colin,
>>>
>>> How to write an Android.bp for a prebuilt jar that needs to be added to
>>> PRODUCT_BOOT_JARS?
>>>
>>> Thanks,
>>> Vinayak
>>>
>>> On Monday, March 18, 2019 at 3:36:17 PM UTC-7, Colin Cross wrote:

 The basics on Android.bp files are documented at
 https://android.googlesource.com/platform/build/soong/+/master/README.md,
 and the documentation on the module types and their properties is at
 https://ci.android.com/builds/latest/branches/aosp-build-tools/targets/linux/view/soong_build.html
 .

 On Mon, Mar 18, 2019 at 2:52 PM KarenL  wrote:

> I actually have everything in vendor and I'd prefer to keep it there.
> I'm not sure how to include whats in vendor in framework.jar.
> This is the structure of the stuff I have in vendor that I would like
> to include.
> vendor/xxx/lib -> the prebuilt jars are here
> vendor/xxx/src/com/aaa/bbb/ccc => the source files are here
>
> Question: Should I add an Android.bp to vendor/xxx/
> It sounds like that should contain the java_import section you already
> mentioned.
> How do I include the source files in the new Android.bp?
>
> Question: How do I reference this not module from Android.bk in
> frameworks/base/Android.bp?
>
> Is there any documentation on how to set up Android.bp files. I've
> been looking around and I cant find anything.
>
> I need the extra classes because I'm adding a new system service to
> the build that I'm making.
>
> Thank you again for your help.
>
>
>
> On Monday, March 18, 2019 at 2:33:13 PM UTC-7, Colin Cross wrote:
>>
>> All of that is up to you.  All Android.bp files found in the tree are
>> parsed, so you can create a directory anywhere (maybe under vendor/ so 
>> you
>> can minimize changes to AOSP files).  Put the prebuilt jars in that
>> directory too.
>>
>> static_libs takes a list of module names.
>> android.hardware.radio-V1.0-java is a module created
>> by hardware/interfaces/radio/1.0/Android.bp.  The modules can be defined
>> anywhere in the tree.
>>
>> Taking a step back, what are you trying to accomplish?  Why do you
>> need extra classes in framework.jar?  Maybe it would be better to keep 
>> them
>> outside framework.jar but add them to the default classpath using
>> PRODUCT_BOOT_JARS?  Or ship them as a separate shared library that apps 
>> can
>> opt into loading?
>>
>> On Mon, Mar 18, 2019 at 1:34 PM KarenL  wrote:
>>
>>> What directory should my prebuilt jars go into? Where are the pother
>>> static_libs, like android.hardware.radio-V1.0-java, picked up from?
>>> Where do I add this new Android.bp with the below content?
>>>
>>> All I want to add to framework.jar are 2 prebuilt jars and 2 source
>>> files. Do I need to create a new folder structure under frameworks/base 
>>> for
>>> these? If so - what does that structure look like.
>>>
>>> Thank you for your help.
>>>
>>>
>>>
>>> On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:

 You need to use java_import modules to create a module for the
 jars.  Something like:

 java_import {
 name: "my_prebuilt_jars",
 jars: [
 "my_prebuilt_jar1.jar",
 "my_prebuilt_jar2.jar",
 ],
 }

 Then you can add to static_libs:
 "my_prebuilt_jars"

 On Mon, Mar 18, 2019 at 12:35 PM KarenL  wrote:

> Hi
>
> I would like to add a couple of prebuilt jars and some source
> files to the Android 9 aosp image that I"m building.
> With lower versions of Android I've added these easily to
> frameworks.jar. This was straight forward to do when framework.jar was
> built using a make file. Its a lot less clear how to do this using
> blueprint files and soong.
>
> This is what I've tried and its not enough.
>
> Add a new folder to frameworks/base for my source files:
> frameworks/base/myfolder/java/com/xxx
>
> Edit the Android.bp file in frameworks/base and add source files
> to the "srcs" list
> "myfolder/java/com/xxx/source1.java"
> "myfolder/java/com/xxx/source2.java"
>
> Edit the "static_libs" list and add my p

Re: [android-building] Re: Why did you name it Soong, Kati, Ninja ?

['Colin Cross' via Android Building]

Soong is from Noonian Soong
, who built Androids.
I don't remember what Kati means, it's not Star Trek related (the project
predates Soong), I think it's a play on words in Japanese.

On Wed, May 15, 2019 at 11:41 AM 'Glenn Kasten' via Android Building <
android-building@googlegroups.com> wrote:

> Kati  and Soong
>  appear to be
> from Star Trek.
> I assume that Ninja comes from here
> 
> :-)
>
> On Tuesday, May 14, 2019 at 10:13:28 PM UTC-7, CK RYU wrote:
>>
>> Hi,
>>
>>
>>
>> I have question about the soong build system.
>>
>>
>>
>> I want to know why did you name it Soong, Kati, Ninja?
>>
>> Is the name meaningful?'
>>
>>
>>
>> Thanks,
>>
>>
>>
>> CK.RYU
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/d8d519db-c921-41dc-b353-d92f0fbe1602%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRQUnee7z%3DX7SPJR7XiZ9GOamGQ44GxGot5d32kTLFK8Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Building an old specific commit in one AOSP project

['Colin Cross' via Android Building]

You can download the manifest_*.xml file from any build from the date that
you want, then use repo sync -m /tmp/manifest_*.xml to sync the revisions
from that manifest.

On Fri, Jun 28, 2019 at 7:56 AM Alex  wrote:

> Hi folks,
>
> I did not find any related post to my question so I decided to create one.
> However, feel free to link any relevant post I may have missed.
>
> Problem: I would like to build one project in AOSP at a very specific
> commit.
>
> The procedure:
>
>- Find the commit ID
>- Find the appropriate manifest branch (git tag --contains $COMMIT_ID
>) in the appropriate project in the mirror
>- Init the manifest branch from the mirror
>- Checkout the project at $COMMIT_ID
>- Source build/envsetup.sh and do a *mma*
>
>
> However, if this procedure mostly works, sometimes you have a problem
> because the dependencies of your project as not synced and the build fail.
>
> Since Google on its CI (
> https://ci.android.com/builds/branches/aosp-master/grid ) always build
> the tree with the last commit on each repo, the idea was to checkout *every
> *project in AOSP at the date of the commit I want to build (e.g.
> $COMMIT_ID is 15.06.2019, let's checkout every project at this date).
> However, this *fails* because some project are not synced (during the
> sync from the mirror) with their history (e.g prebuilts tools).
>
> I also tried to checkout the master branch from the AOSP mirror but the
> problem remains (e.g. clone-depth of some project is still 1).
>
> My question is rather easy: how do one build a specific commit in one of
> AOSP project.
>
>
> Ps : If you want to reproduce the problem, you may try to build commit 
> 830cb39cb2a0f1bf6704d264e2a5c5029c175dd7
> from platform/system/bt on branch android-9.0.0_r17 .
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/a5befb35-0739-434b-8964-b5ecdfa00eb0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRTScOYrfOLcMuMMZxtuouRHmz7v97iAKWpd3VzQKFSsCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Building an old specific commit in one AOSP project

['Colin Cross' via Android Building]

That change likely arrived in AOSP as part of the lollipop release drop, so
there are no more fine-grained builds available.

On Mon, Jul 1, 2019 at 8:05 AM Alex  wrote:

> This idea is great but it works only if the project has been built by the
> CI with head the targeted commit.
> However, in most cases the CI did not build every changes (I'm looking at
> a commit from 2015)
>
> For example:
> Project: frameworks/av
> CommitId: aa4da6fa7ca2454f0713de0a5a583b5b8160166
>
> The commit is merged in the master branch with the commit
> bacd813565c77010485b7f487630a079ef2a6899.
> Still, *frameworks/av *was not built with this head, the two closest
> (built by the CI) are ~700 files changed
>
> $ git log -1 --pretty="%H %aD" b70b09c9f96e78a45332c93a0eadd99cf6fe9645
> b70b09c9f96e78a45332c93a0eadd99cf6fe9645 Fri, 21 Aug 2015 00:58:17 +
> $ git log -1 --pretty="%H %aD" bacd813565c77010485b7f487630a079ef2a6899
> bacd813565c77010485b7f487630a079ef2a6899 Fri, 21 Aug 2015 17:30:09 +
> $ git log -1 --pretty="%H %aD" 84c1e5a90348afca09be0745ab731880d740e10d
> 84c1e5a90348afca09be0745ab731880d740e10d Fri, 21 Aug 2015 21:13:58 +
>
> $ git --no-pager diff --shortstat
> b70b09c9f96e78a45332c93a0eadd99cf6fe9645
> bacd813565c77010485b7f487630a079ef2a6899
>  721 files changed, 74085 insertions(+), 21394 deletions(-)
>
> $ git --no-pager diff --shortstat
> bacd813565c77010485b7f487630a079ef2a6899
> 84c1e5a90348afca09be0745ab731880d740e10d
>  721 files changed, 21414 insertions(+), 74059 deletions(-)
>
> So from either manifest file, it is not possible to build the specific
> commit because the changes are not synchronised with the rest of AOSP.
> Any idea that could solve this problem ?
>
>
> Le vendredi 28 juin 2019 18:33:28 UTC+2, Colin Cross a écrit :
>>
>> You can download the manifest_*.xml file from any build from the date
>> that you want, then use repo sync -m /tmp/manifest_*.xml to sync the
>> revisions from that manifest.
>>
>> On Fri, Jun 28, 2019 at 7:56 AM Alex  wrote:
>>
>>> Hi folks,
>>>
>>> I did not find any related post to my question so I decided to create
>>> one. However, feel free to link any relevant post I may have missed.
>>>
>>> Problem: I would like to build one project in AOSP at a very specific
>>> commit.
>>>
>>> The procedure:
>>>
>>>- Find the commit ID
>>>- Find the appropriate manifest branch (git tag --contains
>>>$COMMIT_ID ) in the appropriate project in the mirror
>>>- Init the manifest branch from the mirror
>>>- Checkout the project at $COMMIT_ID
>>>- Source build/envsetup.sh and do a *mma*
>>>
>>>
>>> However, if this procedure mostly works, sometimes you have a problem
>>> because the dependencies of your project as not synced and the build fail.
>>>
>>> Since Google on its CI (
>>> https://ci.android.com/builds/branches/aosp-master/grid ) always build
>>> the tree with the last commit on each repo, the idea was to checkout *every
>>> *project in AOSP at the date of the commit I want to build (e.g.
>>> $COMMIT_ID is 15.06.2019, let's checkout every project at this date).
>>> However, this *fails* because some project are not synced (during the
>>> sync from the mirror) with their history (e.g prebuilts tools).
>>>
>>> I also tried to checkout the master branch from the AOSP mirror but the
>>> problem remains (e.g. clone-depth of some project is still 1).
>>>
>>> My question is rather easy: how do one build a specific commit in one of
>>> AOSP project.
>>>
>>>
>>> Ps : If you want to reproduce the problem, you may try to build commit 
>>> 830cb39cb2a0f1bf6704d264e2a5c5029c175dd7
>>> from platform/system/bt on branch android-9.0.0_r17 .
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/android-building/a5befb35-0739-434b-8964-b5ecdfa00eb0%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/

Re: [android-building] Android.bp files for interlinked subdirectories

['Colin Cross' via Android Building]

Each module should have export_include_dirs: ["inc"], and then anything
that links against it will get those headers.

On Thu, Aug 8, 2019 at 9:50 AM Mohammed Shakir  wrote:

> Hi Sir/Madam,
>
> I am working on a project where multiple interlinked modules are present.
> I am trying to make it compile.
>
> For example, my directory structure is like below.
>
> Root
> |
> |---> Android.bp
> |
> |---> Module1
> | |
> | |---> Android.bp
> | |
> | |---> inc
> | |
> | |---> src
> | |
> | |---> SubModule
> |   |
> |   |---> Android.bp
> |   |
> |   |---> inc
> |   |
> |   |---> src
> |
> |---> Module2
> | |
> | |---> Android.bp
> | |
> | |---> inc
> | |
> | |---> src
> |
> |---> Module3
>   |
>   |---> Android.bp
>   |
>   |---> inc
>   |
>   |---> src
>
>
> In my case, all three modules linked to each other, so they need to share
> their header files with each other.
>
> I have tried to use *include_dirs: ["inc", "SubModule/inc",
> "../Module2/inc", "../Module3/inc"] *in the Android.bp of Module1, I got '
> *module"MyTestApplication" variant "android_common": Path is outside
> directory*'
>
> Could you please check in to it and give a proper method on how to include
> these directories to my Makefile.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/1b012337-ca35-4c4e-84e5-cb0550a27d33%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSoJzydrMvLiTZOCa6oc-%3DE-mZji%2BuWtpzpX6iTcuChYQ%40mail.gmail.com.

Re: [android-building] Adding HIDL service to vendor with prebuilt libraries (Android P)

['Colin Cross' via Android Building]

Likely libTest.so is built incorrectly and xxx.hardware.test@1.0-service is
ending up with an incorrect DT_NEEDED entry.  Can you show the output of
objdump -x lib/libTest.so and objdump -x
$OUT/vendor/bin/hw/xxx.hardware.test@1.0-service?  My guess is that SONAME
in libTest.so is "out/target/product/xxx/obj/lib/libTest.so" and that gets
copied into NEEDED in xxx.hardware.test@1.0-service.

On Thu, Aug 8, 2019 at 9:50 AM Tore Offermann <
tore.offerm...@tara-systems.de> wrote:

> Hello everyone,
>
> I am currently fighting adding a vendor HIDL service with prebuilt
> libraries on Android Pie.
>
> The HIDL service is created in vendor/...
> It depends on some prebuilt libraries.
>
> The prebuilt libraries are added to the Makefile for the service as
> follows:
>
> include $(CLEAR_VARS)
> LOCAL_PROPRIETARY_MODULE := true
> LOCAL_MODULE_SUFFIX := .so
> LOCAL_MODULE_CLASS := SHARED_LIBRARIES
> LOCAL_MODULE := libTest
> LOCAL_SRC_FILES := lib/libTest.so
> #include $(BUILD_PREBUILT)
>
> During android make the library is correctly copied to /vendor/lib and
> after I flash the device the lib is also available in that folder.
>
> I added the lib to the HIDL service makefile:
>
> include $(CLEAR_VARS)
>
> LOCAL_MODULE := xxx.hardware.test@1.0-service
> LOCAL_PROPRIETARY_MODULE := true
> LOCAL_MODULE_CLASS := EXECUTABLES
> LOCAL_MODULE_RELATIVE_PATH := hw
> LOCAL_INIT_RC := xxx.hardware.t...@1.0-service.rc
> LOCAL_CFLAGS := -Werror
>
> LOCAL_SRC_FILES := service.cpp
>
> LOCAL_C_INCLUDES := $(subst ${ANDROID}/,,$(LOCAL_C_INCLUDES))
>
>
> LOCAL_SHARED_LIBRARIES := \
> xxx.hardware.test@1.0 \
> libhidlbase \
> libhidltransport \
> libbase \
> liblog \
> libutils \
> libTest
>
> include $(BUILD_EXECUTABLE)
>
> No issues during make, but after I start the device the linker complains
> with:
>
> 08-08 10:13:34.014  6814  6814 F linker  : CANNOT LINK EXECUTABLE
> "/vendor/bin/hw/xxx.hardware.test@1.0-service": library
> "out/target/product/xxx/obj/lib/libTest.so" not found
>
> Not sure how this can happen?
> I would suppose that the linker should check for the lib in /vendor/lib.
>
> Could it have something to do with:
>
> LOCAL_PRELINK_MODULE := false
>
> Thanks in advance!
>
> BR,
> Tore
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/d6699eb8-3c08-4ac1-8e74-fb8634b1bd1f%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSmfp3KRh5OyauULYjbOyZhwjvb%3Dr2xWnY89y%2BAZdB_8A%40mail.gmail.com.

Re: [android-building] Re: Build on master branch: failed to find module "fizz-buzz" variant "linux_glibc_x86_64_dylib"

['Colin Cross' via Android Building]

Thanks for the reports, this should be fixed by
https://android-review.googlesource.com/c/platform/build/soong/+/1113046.

On Tue, Sep 3, 2019 at 7:03 AM 张光刘  wrote:

> me too...
> /Volumes/Aosp  make -j12
> 
> PLATFORM_VERSION_CODENAME=R
> PLATFORM_VERSION=R
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_OS=darwin
> HOST_OS_EXTRA=Darwin-18.6.0-x86_64-10.14.5
> HOST_BUILD_TYPE=release
> BUILD_ID=PI
> OUT_DIR=out
> 
> [ 33% 1/3] test android/soong/rust
> FAILED: out/soong/.bootstrap/soong-rust/test/test.passed
> out/soong/.bootstrap/bin/gotestrunner -p ./build/soong/rust -f
> out/soong/.bootstrap/soong-rust/test/test.passed --
> out/soong/.bootstrap/soong-rust/test/test -test.short
> --- FAIL: TestDefaultCrateName (0.05s)
> panic: failed to find module "fizz-buzz" variant
> "linux_glibc_x86_64_dylib".
> all modules: [fizz-buzz(darwin_x86_64_dylib)
> libarena_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libarena_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libfmt_macros_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libfmt_macros_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libgraphviz_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libgraphviz_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libserialize_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libserialize_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libstd_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libstd_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_ext_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_ext_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_pos_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_pos_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libterm_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libterm_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libtest_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libtest_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)] [recovered]
> panic: failed to find module "fizz-buzz" variant
> "linux_glibc_x86_64_dylib".
> all modules: [fizz-buzz(darwin_x86_64_dylib)
> libarena_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libarena_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libfmt_macros_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libfmt_macros_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libgraphviz_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libgraphviz_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libserialize_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libserialize_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libstd_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libstd_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_ext_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_ext_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_pos_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_pos_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libsyntax_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libsyntax_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libterm_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libterm_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)
> libtest_x86_64-unknown-linux-gnu(darwin_x86_64_dylib)
> libtest_x86_64-unknown-linux-gnu(android_arm64_armv8-a_dylib)]
>
> goroutine 4 [running]:
> testing.tRunner.func1(0xc000166300)
> prebuilts/go/darwin-x86/src/testing/testing.go:830 +0x392
> panic(0x1418d60, 0xc0002b4720)
> prebuilts/go/darwin-x86/src/runtime/panic.go:522 +0x1b5
> android/soong/android.(*TestContext).ModuleForTests(0xc206c0,
> 0x14a50cf, 0x9, 0x14ae8dd, 0x18, 0x1ca782a906d9, 0x11f71f0)
> /Volumes/Aosp/build/soong/android/testing.go:92 +0x3ff
> android/soong/rust.TestDefaultCrateName(0xc000166300)
> /Volumes/Aosp/build/soong/rust/rust_test.go:119 +0x7f
> testing.tRunner(0xc000166300, 0x14c2380)
> prebuilts/go/darwin-x86/src/testing/testing.go:865 +0xc0
> created by testing.(*T).Run
> prebuilts/go/darwin-x86/src/testing/testing.go:916 +0x35a
> 19:07:38 soong bootstrap failed with: exit status 1
>
> 在 2019年8月31日星期六 UTC+8上午1:37:38，Quang Hòa Trần写道：
>>
>> Hi there,
>>
>> I tried building the recent master branch on MacOS 10.14.5 and it was
>> failed with the error as follows:
>>
>> PLATFORM_VERSION_CODENAME=R
>>
>> PLATFORM_VERSION=R
>>
>> TARGET_PRODUCT=aosp_arm
>>
>> TARGET_BUILD_VARIANT=eng
>>
>> TARGET_BUILD_TYPE=release
>>
>> TARGET_ARCH=arm
>>
>> TARGET_ARCH_VARIANT=armv7-a-neon
>>
>> TARGET_CPU_VARIANT=generic
>>
>> HOST_ARCH=x86_64
>>
>> HOST_OS=darwin
>>
>> HOST_OS_EXTR

Re: [android-building] Need help exposing library / class paths in AOSP P (Android 9) from my own .jar file inside vendor

['Colin Cross' via Android Building]

Follow the instructions in the error and it will give you a ton more
information, buried in it will be which classes it is failing to find:
ART_BOOT_IMAGE_EXTRA_ARGS="--runtime-arg -verbose:verifier" m

On Fri, Sep 6, 2019 at 7:07 AM Chari Veera 
wrote:

> Hello Colin,
>
> I am able to add my jar to PRODUCT_BOOT_JARS, but I am facing following
> error. Do I miss anything?
>
>
> Parsing
> out/target/product/msm8953_64/obj/ETC/vendor_sepolicy.cil_intermediates/vendor_policy_raw.cil
>
> [ 59% 7673/12956] target dex2oat:
> out/target/product/msm8953_64/dex_bootjars/system/framework/arm64/boot.art
>
> FAILED:
> out/target/product/msm8953_64/dex_bootjars/system/framework/arm64/boot.art
>
> /bin/bash -c "(mkdir -p
> out/target/product/msm8953_64/symbols/system/framework/arm64/ ) && (rm -f
> out/target/product/msm8953_64/dex_bootjars/system/framework/arm64//*.art
> out/target/product/msm8953_64/dex_bootjars/system/framework/arm64//*.oat
> out/target/product/msm8953_64/dex_bootjars/system/framework/arm64//*.art.rel
> ) && (rm -f
> out/target/product/msm8953_64/symbols/system/framework/arm64//*.art ) &&
> (rm -f out/target/product/msm8953_64/symbols/system/framework/arm64//*.oat
> ) && (rm -f
> out/target/product/msm8953_64/symbols/system/framework/arm64//*.art.rel )
> && (ANDROID_LOG_TAGS=\"*:e\" out/host/linux-x86/bin/dex2oatd --runtime-arg
> -Xms64m   --runtime-arg -Xmx64m   --compiler-filter=speed-profile
> --profile-file=out/target/product/msm8953_64/dex_bootjars/system/framework/boot.prof
>
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/com.nxp.nfc.nq_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/qcom.fmradio_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/com.qualcomm.qti.camera_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/QPerformance_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/UxPerformance_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/core-oj_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/core-libart_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/conscrypt_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/voip-common_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/ims-common_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/android.hidl.base-V1.0-java_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/android.hidl.manager-V1.0-java_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/qolib_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/framework-oahl-backward-compatibility_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/tcmiface_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/WfdCommon_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/oem-services_intermediates/javalib.jar
> --dex-file=out/target/common/obj/JAVA_LIBRARIES/telephony-ext_intermediates/javalib.jar
>   --dex-location=/system/framework/com.nxp.nfc.nq.jar
> --dex-location=/system/framework/qcom.fmradio.jar
> --dex-location=/system/framework/com.qualcomm.qti.camera.jar
> --dex-location=/system/framework/QPerformance.jar
> --dex-location=/system/framework/UxPerformance.jar
> --dex-location=/system/framework/core-oj.jar
> --dex-location=/system/framework/core-libart.jar
> --dex-location=/system/framework/conscrypt.jar
> --dex-location=/system/framework/okhttp.jar
> --dex-location=/system/framework/bouncycastle.jar
> --dex-location=/system/framework/apache-xml.jar
> --dex-location=/system/framework/ext.jar
> --dex-location=/system/framework/framework.jar
> --dex-location=/system/framework/telephony-common.jar
> --dex-location=/system/framework/voip-common.jar
> --dex-location=/system/framework/ims-common.jar
> --dex-location=/system/framework/android.hidl.base-V1.0-java.jar
> --dex-location=/system/framework/android.hidl.manager-V1.0-java.jar
> --dex-location=/system/framework/qolib.jar
> --dex-location=/system/framework/framework-oahl-backward-compatibility.jar
> --dex-location=/system/framework/android.test.base.jar
> --dex-location=/system/framework/tcmiface.jar
> --dex-location=/system/framework/WfdComm

Re: [android-building] Not booting after adding app to priv-app

['Colin Cross' via Android Building]

It's hard to tell without logs (you can get adb access for early crashes
like this by pre-installing an ADB public key using PRODUCT_ADB_KEYS), but
my guess is you need to add something to
https://android.googlesource.com/platform/frameworks/base/+/master/data/etc/privapp-permissions-platform.xml?pli=1
 or
https://android.googlesource.com/device/google/marlin/+/master/permissions/privapp-permissions-marlin.xml

On Mon, Sep 9, 2019 at 7:01 AM Vishnu M J 
wrote:

> Hi,
>
> I have been trying to add a apk to priv-app.
>
> Following are the steps i did:
>
> Made a folder named Testapk in packages/apps
> Copied apk to folder with name Testapk.apk
> In same directory, created an Android.mk file with following contents:
>
> LOCAL_PATH := $(call my-dir)
>
>
> include $(CLEAR_VARS)
>
>
> LOCAL_MODULE_TAGS := optional
>
>
> LOCAL_MODULE := Testapk
>
>
> LOCAL_CERTIFICATE := PRESIGNED
>
>
> LOCAL_SRC_FILES := Testapk.apk
>
>
> LOCAL_MODULE_CLASS := APPS
>
>
> LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)
>
>
> LOCAL_PRIVILEGED_MODULE := true
>
>
> TARGET_OUT_DATA_APPS_PRIVILEGED := $(TARGET_OUT_DATA)/priv-app
>
>
> include $(BUILD_PREBUILT)
>
>
> Then, added Testapk to core.mk
>
>
> Build is successful and i can see my apk in priv-app folder in
> out/target/product/sailfish/system/priv-app. After flashing, the device
> wont boot up. Its stuck on Android logo.
>
>
> (I am using google pixel-sailfish. Branch is android-9.0.0_r33)
>
> (On adding apk to system/apps, i can boot and the apk works fine)
>
>
> Can someone help me on this???
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/78f67bd6-2e90-40ea-81a8-1a4f1644b8a0%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSqLEhfK1V_V4gVO7fYwSKnj35%3DWCTMAEMfE6n9mSjqNw%40mail.gmail.com.

Re: [android-building] Android.bp accessibility

['Colin Cross' via Android Building]

Soong cannot access variables defined in Make.

For variables defined in Android.bp files this is documented at
https://android.googlesource.com/platform/build/soong/+/master/README.md#variables
:
"Variables are scoped to the remainder of the file they are declared in, as
well as any child blueprint files."


On Fri, Oct 4, 2019 at 9:57 AM REGURI AKANKSHA 
wrote:

> Is there any case that  Android.bp can access variables declared in other
> files.
> say a variable "platform" is declared in some .mk file Can Android.bp now
> use that variable "platform"
> As per my knowledge it's "no" but I want to make sure about this
> Thanks in advance
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/0b6fc82b-4d66-4ad4-b0d1-3fbb4f192a22%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRTwNDjBZe-2BxFLBD36k47s%3D41St9KauOxEXNxX6Qvh4g%40mail.gmail.com.

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

['Colin Cross' via Android Building]

Use a single module, and put the differences into multilib lib32/lib64
clauses:

multilib: {
lib32: {
srcs: ["foo32.c"],
},
lib64: {
srcs: ["foo32.c"],
},
},

On Wed, Oct 9, 2019 at 1:09 PM REGURI 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?
> Thanks in advance
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/63c8a7f0-b53a-473c-82d6-f623df2fa8cf%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRS76XHJ0M9XjV12_n%2Bt2yMR4kgc5q6AGfQZ7vQgtS80pw%40mail.gmail.com.

Re: [android-building] Benchmarktest64 directory

['Colin Cross' via Android Building]

Likely an oversight.  It has been this way for benchmarks defined in Make
since 2016.  Maybe the benchmark test runners are running as root?

On Thu, Oct 10, 2019 at 10:22 AM Paul Elliott  wrote:

> Hi all,
>
> Prior to android 9, all benchmarks and test suites were generally built
> into /data/nativetest(64), however recently in Android 9, some (but not
> all) tests have been ending up getting built into /data/benchmarktest(64),
> due to a change aligning soong with make -
> https://android-review.googlesource.com/c/platform/build/soong/+/479681
>
> This would be fine, however due to its lack of inclusion
> in system/core/libcutils/fs_config.cpp, this folder is created without any
> permissions whatsoever.
>
> I have checked this is still the case in Android 10, and indeed master. Is
> this an oversight, or am I missing something?
>
> Thanks in advance,
>
> Paul.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/989e4b75-4366-4b18-b534-dd12f2c022a4%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRQPB4gBrfymm13k4452OtihHL9urzQMjXzgp6WFO6jH%3DA%40mail.gmail.com.

Re: [android-building] Benchmarktest64 directory

['Colin Cross' via Android Building]

How are you getting the benchmarks on to the device?  In my testing (`m
libjavacore-benchmarks`, `adb sync data` they are marked executable.

On Fri, Oct 11, 2019 at 10:49 AM Paul Elliott  wrote:

> Hi Colin,
>
> The curious bit is that even as root I am having to change the tests
> inside benchmarktest(64) to be executable because they too have no
> permissions, which is why I was curious about this as it clearly breaks
> automation for us, and therefore likely for anyone else. We could
> potentially submit a patch for this to add the directory to fs_config.cpp,
> however given the lack of mention by anyone else, was unsure if we were
> missing something, basically.
>
> Paul.
>
> On Thursday, October 10, 2019 at 9:12:11 PM UTC+1, Colin Cross wrote:
>>
>> Likely an oversight.  It has been this way for benchmarks defined in Make
>> since 2016.  Maybe the benchmark test runners are running as root?
>>
>> On Thu, Oct 10, 2019 at 10:22 AM Paul Elliott  wrote:
>>
>>> Hi all,
>>>
>>> Prior to android 9, all benchmarks and test suites were generally built
>>> into /data/nativetest(64), however recently in Android 9, some (but not
>>> all) tests have been ending up getting built into /data/benchmarktest(64),
>>> due to a change aligning soong with make -
>>> https://android-review.googlesource.com/c/platform/build/soong/+/479681
>>>
>>> This would be fine, however due to its lack of inclusion
>>> in system/core/libcutils/fs_config.cpp, this folder is created without any
>>> permissions whatsoever.
>>>
>>> I have checked this is still the case in Android 10, and indeed master.
>>> Is this an oversight, or am I missing something?
>>>
>>> Thanks in advance,
>>>
>>> Paul.
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/android-building/989e4b75-4366-4b18-b534-dd12f2c022a4%40googlegroups.com
>>> 
>>> .
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/fce01460-04f9-49a1-b73b-f4c89c8a4ab4%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSUvHonrEz3eoUPi%2Bj%2B3uSsqJE2gVFyq7s3PABrYs-xiw%40mail.gmail.com.

Re: [android-building] Benchmarktest64 directory

['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 fine though.

On Tue, Oct 15, 2019 at 8:27 AM Paul Elliott  wrote:

> 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 you getting the benchmarks on to the device?  In my testing (`m
>> libjavacore-benchmarks`, `adb sync data` they are marked executable.
>>
>> On Fri, Oct 11, 2019 at 10:49 AM Paul Elliott  wrote:
>>
>>> Hi Colin,
>>>
>>> The curious bit is that even as root I am having to change the tests
>>> inside benchmarktest(64) to be executable because they too have no
>>> permissions, which is why I was curious about this as it clearly breaks
>>> automation for us, and therefore likely for anyone else. We could
>>> potentially submit a patch for this to add the directory to fs_config.cpp,
>>> however given the lack of mention by anyone else, was unsure if we were
>>> missing something, basically.
>>>
>>> Paul.
>>>
>>> On Thursday, October 10, 2019 at 9:12:11 PM UTC+1, Colin Cross wrote:

 Likely an oversight.  It has been this way for benchmarks defined in
 Make since 2016.  Maybe the benchmark test runners are running as root?

 On Thu, Oct 10, 2019 at 10:22 AM Paul Elliott  wrote:

> Hi all,
>
> Prior to android 9, all benchmarks and test suites were generally
> built into /data/nativetest(64), however recently in Android 9, some (but
> not all) tests have been ending up getting built into
> /data/benchmarktest(64), due to a change aligning soong with make -
> https://android-review.googlesource.com/c/platform/build/soong/+/479681
>
> This would be fine, however due to its lack of inclusion
> in system/core/libcutils/fs_config.cpp, this folder is created without any
> permissions whatsoever.
>
> I have checked this is still the case in Android 10, and indeed
> master. Is this an oversight, or am I missing something?
>
> Thanks in advance,
>
> Paul.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to android-...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/989e4b75-4366-4b18-b534-dd12f2c022a4%40googlegroups.com
> 
> .
>
 --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/android-building/fce01460-04f9-49a1-b73b-f4c89c8a4ab4%40googlegroups.com
>>> 
>>> .
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web vis

Re: [android-building] Unable to download content during build

['Colin Cross' via Android Building]

Network connections are blocked using nsjail by default, as they break
build hermeticity.
https://android.googlesource.com/platform/build/soong/+/master/ui/build/sandbox_linux.go#161
is
where it is enforced, you can disable it by
setting BUILD_BROKEN_USES_NETWORK := true in your BoardConfig.mk.

On Wed, Oct 16, 2019 at 10:15 AM Michael Goffioul <
michael.goffi...@gmail.com> wrote:

> Thanks, I figured it must be somehow block. What I would like to
> understand is _how_ this is achieved technically.
>
>
> On Wed, Oct 16, 2019 at 12:58 PM 'Wesolowski, Krzysztof' via Android
> Building  wrote:
>
>> It's blocked by sandboxing of build system, isolating that only repo
>> content is used. Probably wget or external connections are blocked.
>>
>> BR, K
>>
>> Get Outlook for Android 
>>
>> --
>> *From:* android-building@googlegroups.com <
>> android-building@googlegroups.com> on behalf of Michael Goffioul <
>> michael.goffi...@gmail.com>
>> *Sent:* Tuesday, October 15, 2019 9:58:18 PM
>> *To:* Android Building 
>> *Subject:* [android-building] Unable to download content during build
>>
>> 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 build system runs fine. Can somebody describe the mechanism at
>> play here, and maybe points to source files where the restriction is
>> implemented?
>>
>> Thanks,
>> Michael.
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>> 
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/403e25aa-3db5-499a-a7f7-e05814b66fa6%40googlegroups.com
>> 
>> .
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/VE1P174MB00787459500593F9D0B659AC91920%40VE1P174MB0078.EURP174.PROD.OUTLOOK.COM
>> 
>> .
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/CAB-99LsvY8ffMGZhOTmGEn_gmyd8sGnXyhtX84zoqAxy%2B93DFw%40mail.gmail.com
> 

Re: [android-building] Build error: There is insufficient memory for the Java Runtime Environment to continue.

['Colin Cross' via Android Building]

You'll need to pass a lower -j value to m.  The parallelism selection only
takes the number of CPUs into account, and not the total memory.  This is
something we are looking to improve on.

On Fri, Oct 18, 2019 at 8:46 AM Zelong  wrote:

> zelong@zelong-ThinkPad-T430:/media/zelong/2828a0f1-cc41-4428-854d-a7a18c59f5c6/android_source$
> m
> 
> PLATFORM_VERSION_CODENAME=R
> PLATFORM_VERSION=R
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.15.0-65-generic-x86_64-Ubuntu-16.04.6-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QT
> OUT_DIR=out
> 
> [ 47% 627/1310] //packages/apps/CarrierConfig:CarrierConfig r8
> FAILED:
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex/CarrierConfig.jar
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/proguard_dictionary
> rm -rf
> "out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex"
> && mkdir -p
> "out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex"
> && rm -f
> "out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/proguard_dictionary"
> && out/soong/host/linux-x86/bin/r8-compat-proguard -JXX:OnError='cat
> hs_err_pid%p.log' -JXX:CICompilerCount=6 -JXX:+UseDynamicNumberOfGCThreads
> -injars
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/javac/CarrierConfig.jar
> --output
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex
> --force-proguard-compatibility --no-data-resources -printmapping
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/proguard_dictionary
> --min-api 1  -libraryjars
> out/soong/.intermediates/libcore/mmodules/core_platform_api/core.platform.api.stubs/android_common/turbine-combined/core.platform.api.stubs.jar:out/soong/.intermediates/libcore/core-lambda-stubs/android_common/turbine-combined/core-lambda-stubs.jar
> -libraryjars
> out/soong/.intermediates/frameworks/base/ext/android_common/turbine-combined/ext.jar:out/soong/.intermediates/frameworks/base/framework/android_common/turbine-jarjar/framework.jar:out/soong/.intermediates/frameworks/base/media/updatable_media_stubs/android_common/turbine-combined/updatable_media_stubs.jar:out/soong/.intermediates/frameworks/opt/telephony/telephony-common/android_common/turbine-jarjar/telephony-common.jar
> -forceprocessing -include build/make/core/proguard.flags -include
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/gen/proguard.options
> -include packages/apps/CarrierConfig/proguard.flags -dontoptimize
> -dontobfuscate --debug && touch
> "out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/proguard_dictionary"
> && out/soong/host/linux-x86/bin/soong_zip --ignore_missing_files -L 0 -o
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex/classes.dex.jar
> -C
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex
> -f
> "out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex/classes*.dex"
> && out/soong/host/linux-x86/bin/merge_zips -D -stripFile "**/*.class"
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex/CarrierConfig.jar
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/dex/classes.dex.jar
> out/soong/.intermediates/packages/apps/CarrierConfig/CarrierConfig/android_common/javac/CarrierConfig.jar
> OpenJDK 64-Bit Server VM warning: INFO:
> os::commit_memory(0xaef0, 272629760, 0) failed; error='Not
> enough space' (errno=12)
> #
> *# There is insufficient memory for the Java Runtime Environment to
> continue.*
> *# Native memory allocation (mmap) failed to map 272629760 bytes for
> committing reserved memory.*
> *# An error report file with more information is saved as:*
> *#
> /media/zelong/2828a0f1-cc41-4428-854d-a7a18c59f5c6/android_source/hs_err_pid3639.log*
> #
> # -XX:OnError="cat hs_err_pid%p.log"
> #   Executing /bin/sh -c "cat hs_err_pid3639.log" ...
> os::fork_and_exec failed: Not enough space (ENOMEM=12)
> [ 48% 631/1310] R8:
> out/target/common/obj/APPS/Dialer_intermediates/dex/classes.dex
> Stripped invalid locals information from 1 method.
> In
> ./out/target/common/obj/APPS/Dialer_intermediates/classes.jar:android/support/v7/widget/Toolbar.class:
>   Methods with invalid locals information:
>   void android.support.v7.widget.Toolbar.onLayout(boolean, int, int, int,
> int)
>   Type information in locals-table is inconsistent. Cannot con

Re: [android-building] OpenJDK 8 or OpenJDK 9 for AOSP 10: which one?

['Colin Cross' via Android Building]

The source for Android 10 includes prebuilt java toolchains used for
compiling the platform in prebuilts/jdk/jdk8 and prebuilts/jdk/jdk9, so
there should be no need to provide any OpenJDK version.

The platform always uses javac from OpenJDK9 to compile
(prebuilts/jdk/jdk9/linux-x86/bin/javac), OpenJDK8 is EOL upstream.
Those comments are about selecting what language features are being
targeted by the OpenJDK 9 toolchain.  In Android 10, we default to passing
-source 1.8 -target 1.8 to javac to target OpenJDK8 language features,
unless you set EXPERIMENTAL_USE_OPENJDK9=true on the command line, which
will default to passing -source 1.9 -target 1.9.  There is no reason to do
this in Android 10, as there is no platform support for Java language 9
features.  In master you can use EXPERIMENTAL_JAVA_LANGUAGE_LEVEL_9=true to
get the same effect.

On Thu, Oct 24, 2019 at 7:40 AM John W. Blue  wrote:

> Hello,
>
>
>
> I read here:
>
>
>
>
> https://android.googlesource.com/platform/build/+/refs/tags/android-10.0.0_r6/core/java_common.mk
>
>
>
> # TODO(ccross): allow 1.9 for current and unbundled once we have SDK
> system modules
>
> LOCAL_JAVA_LANGUAGE_VERSION := 1.8
>
>   else
>
> # DEFAULT_JAVA_LANGUAGE_VERSION is 1.8, unless TARGET_OPENJDK9 in which
> case it is 1.9
>
>
>
> So is OpenJDK 8 the recommended version or is OpenJDK 9?  And is
> java_common.mk file the only way to tell?
>
>
>
> John
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/68b4db88bc69402a9b2a89458fe3258e%40mail.rrcic.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSU7KTJMfnRDAs6o0hCpKdbX3fY%2BrSY6Lw-gf0eC%3DJT1w%40mail.gmail.com.

Re: [android-building] OpenJDK 8 or OpenJDK 9 for AOSP 10: which one?

['Colin Cross' via Android Building]

Correction, EXPERIMENTAL_JAVA_LANUAGE_LEVEL_9=true is the default in
master, and is moving to required with
https://android-review.googlesource.com/c/platform/build/soong/+/1151196.

On Thu, Oct 24, 2019 at 3:32 PM Colin Cross  wrote:

> The source for Android 10 includes prebuilt java toolchains used for
> compiling the platform in prebuilts/jdk/jdk8 and prebuilts/jdk/jdk9, so
> there should be no need to provide any OpenJDK version.
>
> The platform always uses javac from OpenJDK9 to compile
> (prebuilts/jdk/jdk9/linux-x86/bin/javac), OpenJDK8 is EOL upstream.
> Those comments are about selecting what language features are being
> targeted by the OpenJDK 9 toolchain.  In Android 10, we default to passing
> -source 1.8 -target 1.8 to javac to target OpenJDK8 language features,
> unless you set EXPERIMENTAL_USE_OPENJDK9=true on the command line, which
> will default to passing -source 1.9 -target 1.9.  There is no reason to do
> this in Android 10, as there is no platform support for Java language 9
> features.  In master you can use EXPERIMENTAL_JAVA_LANGUAGE_LEVEL_9=true to
> get the same effect.
>
> On Thu, Oct 24, 2019 at 7:40 AM John W. Blue  wrote:
>
>> Hello,
>>
>>
>>
>> I read here:
>>
>>
>>
>>
>> https://android.googlesource.com/platform/build/+/refs/tags/android-10.0.0_r6/core/java_common.mk
>>
>>
>>
>> # TODO(ccross): allow 1.9 for current and unbundled once we have SDK
>> system modules
>>
>> LOCAL_JAVA_LANGUAGE_VERSION := 1.8
>>
>>   else
>>
>> # DEFAULT_JAVA_LANGUAGE_VERSION is 1.8, unless TARGET_OPENJDK9 in which
>> case it is 1.9
>>
>>
>>
>> So is OpenJDK 8 the recommended version or is OpenJDK 9?  And is
>> java_common.mk file the only way to tell?
>>
>>
>>
>> John
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/68b4db88bc69402a9b2a89458fe3258e%40mail.rrcic.com
>> 
>> .
>>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRS2t%2BY4uOGQa09597qg6xmZ7yES3OViRmOA8uwzaKebhQ%40mail.gmail.com.

Re: [android-building] Build starts slowly and get stuck

['Colin Cross' via Android Building]

I would expect using the NTFS for the out directory is the problem.  You
can get soong_build to dump stack traces of where it is stuck with `killall
-QUIT soong_build`.

Does the build get further if you put the OUT_DIR on your SSD?  Try `m
nothing`, which will parse all the build files but not build anything so it
shouldn't use too much disk space.


On Wed, Nov 13, 2019 at 2:20 PM Glanda  wrote:

> I have a problem to build my AOSP. And "lunch" and "m" takes quite a long
> time (1 or 2 minutes) to start, but I'm mainly here for the other issue.
> There is no Error or something else, the build only gets stuck.
>
> Here is where it get stuck:
>
> 
> PLATFORM_VERSION_CODENAME=R
> PLATFORM_VERSION=R
> TARGET_PRODUCT=full_a5y17lte
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-5.0.0-32-generic-x86_64-Ubuntu-18.04.3-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QD1A.190821.011
> OUT_DIR=out
> 
> [ 0% 0/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> (time) out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>
> When the build starts after the 1-2 minutes my CPU useage is on all 6
> cores for a short time fully utilized. Then the CPU useage is normal.
> I already made one build attempt for 3 hours, it didn't help.
>
> Note: My out directory is linked with a folder of an Raid 0 partition from
> 3 HDDs, NTFS formated. I use it because my SSD with the AOSP is to small.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/d085eb8e-563c-4dad-a75f-1cb425da2267%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRRejC5gX3FnFTBO2t%3DNGb5MoQxH2Gh2TyH6EPceEmZA8w%40mail.gmail.com.

Re: [android-building] Can't build on darwin: module "libcras_sys" variant "darwin_x86_64_rlib": depends on disabled module "libdata_model"

['Colin Cross' via Android Building]

That error was fixed by
https://android-review.googlesource.com/c/platform/external/adhd/+/1168284

On Fri, Nov 15, 2019 at 2:56 PM Brian Duff  wrote:

> I just repo synced, and can no longer build on darwin (building on linux
> works fine)
>
> $ . build/envsetup.sh
> $ make -j aapt2
> 
> PLATFORM_VERSION_CODENAME=R
> PLATFORM_VERSION=R
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_OS=darwin
> HOST_OS_EXTRA=Darwin-18.7.0-x86_64-10.14.6
> HOST_BUILD_TYPE=release
> BUILD_ID=QD1A.190821.011
> OUT_DIR=out
> 
> [100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> FAILED: out/soong/build.ninja
> out/soong/.bootstrap/bin/soong_build -t -l
> out/.module_paths/Android.bp.list -b out/soong -n out -d
> out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o
> out/soong/build.ninja Android.bp
> error: external/adhd/cras/client/cras-sys/Android.bp:1:1: module
> "libcras_sys" variant "darwin_x86_64_rlib": depends on disabled module
> "libdata_model"
> error: external/adhd/cras/client/cras-sys/Android.bp:1:1: module
> "libcras_sys" variant "darwin_x86_64_rlib": depends on disabled module
> "libdata_model"
> 11:44:37 soong bootstrap failed with: exit status 1
>
>  failed to build some targets (38 seconds) 
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/5d43514b-a5bc-4aa1-bcaa-cee691b4e2ef%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRRdXqAdh7%3DMJvTNEi9zWePf3jficmoB9W81f%3DJDXcLFRA%40mail.gmail.com.

Re: [android-building] Lots of 'Disallowed PATH tool "manpath"...' when building Android Q

['Colin Cross' via Android Building]

I was able to reproduce this on Fedora 30, it's something to do with the
environment BASH_ENV=/usr/share/Modules/init/bash, which is causing
arbitrary bash code that can use any binary to be run on every
non-interactive bash shell startup.

On Mon, Nov 18, 2019 at 9:50 AM Michael Goffioul 
wrote:

> Yes, I've already looked into that, but there's not much of a trace, e.g.:
>
> 2019/11/18 11:22:34.837088 build/soong/ui/build/sandbox_linux.go:86:
> [prebuilts/build-tools/linux-x86/bin/nsjail -H android-build -e -u nobody
> -g nobody -B / --disable_clone_newcgroup -- /bin/bash -c if [ $(hostname)
> == "android-build" ]; then echo "Android" "Success"; else echo Failure; fi]
> 2019/11/18 11:22:34.877084 build/soong/ui/build/path.go:105: Disallowed
> PATH tool "manpath" used: []string{"manpath"}
> 2019/11/18 11:22:34.877237 build/soong/ui/build/path.go:107: See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
>
> I've a feeling that it's coming from bash itself. I've looked into the
> local and system profile/bashrc and anything I could think of, but I can't
> really pinpoint where it's coming from.
>
> On Mon, Nov 18, 2019 at 12:40 PM 'Dan Willemsen' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> If you check out/soong.log, there should be trace logs that include the
>> parent processes all the way up to ninja.
>>
>> It sounds like one of the existing tools that we allow through is always
>> trying to call manpath? Let me know what you find, we've definitely been
>> shrinking this list on master.
>>
>> - Dan
>>
>> On Thu, Nov 14, 2019 at 3:54 PM Michael Goffioul <
>> michael.goffi...@gmail.com> wrote:
>>
>>> I'm using Fedora 30 to build AOSP. Since Android Q, when building, the
>>> terminal output is littered with hundreds of messages like the following:
>>>
>>> 17:23:06 Disallowed PATH tool "manpath" used: []string{"manpath"}
>>> 17:23:06 See
>>> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
>>> for more information.
>>>
>>> I've looked almost everywhere, but I can't find where "manpath" is
>>> actually used. Has anybody encountered the same problem?
>>>
>>> Thanks,
>>> Michael.
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-building@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-building+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-building+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/android-building/c9a8a0ea-2492-4e7f-9816-11b9b91f6696%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/CALQgHd%3DmqvANYjYSZyP_1%3DtbMgoddYSLEMTkn3NuUTJF_qML7A%40mail.gmail.com
>> 
>> .
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/CAB-99LtJOhcEKr8m_nExyByvOzb_opZxJvk4xovia7d-oYkhdA%40mail.gmail.com
> 

Re: [android-building] cant build aosp src (oreo 8.1.0 r3), always fails (tried different targets)

['Colin Cross' via Android Building]

See https://groups.google.com/g/android-building/c/0kzPnw3akxg

On Wed, Nov 20, 2019 at 4:07 PM Eliane Fonseca 
wrote:

> when building aosp android-8.1.0_r3 always fails, trying to build with
> emulator on a low-spec pc (and i have installed all required components per
> the android compiling instructions), here is the latest console output:
>
> (the target product was mini_emulator_x86 but i also tried aosp_x86 with
> the same error and I had to modify the build ID because it was causing
> another error "too long build fingerprint")
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=8.1.0
> TARGET_PRODUCT=mini_emulator_x86
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=x86
> TARGET_ARCH_VARIANT=x86
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-5.0.0-36-generic-x86_64-with-Ubuntu-18.04-bionic
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=OC-MR1
> OUT_DIR=out
> 
> ninja: no work to do.
> [1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> out/build-mini_emulator_x86.ninja is missing, regenerating...
> [680/995] including ./system/sepolicy/Android.mk ...
> ./system/sepolicy/Android.mk:111: warning: BOARD_SEPOLICY_VERS not
> specified, assuming current platform version
> [995/995] including ./tools/tradefederation/core/Android.mk ...
> platform_testing/build/tasks/tests/instrumentation_metric_test_list.mk:
> warning: continuous_instrumentation_metric_tests: Unknown installed file
> for module perf-setup.sh
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> RecyclerViewTests
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> SettingsFunctionalTests
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> LauncherFunctionalTests
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> EmergencyInfoTests
> platform_testing/build/tasks/tests/native_metric_test_list.mk: warning:
> continuous_native_metric_tests: Unknown installed file for module
> perf-setup.sh
> [  2% 1493/57217] target  C: sh <= external/mksh/src/eval.c
> external/mksh/src/eval.c:634:21: warning: implicit conversion from 'int'
> to 'char' changes value from 192 to -64 [-Wconstant-conversion]
> *dp++ = 0x80 | '@';
>   ~ ~^
> 1 warning generated.
> [  2% 1509/57217] target  C: sh_vendor <= external/mksh/src/eval.c
> external/mksh/src/eval.c:634:21: warning: implicit conversion from 'int'
> to 'char' changes value from 192 to -64 [-Wconstant-conversion]
> *dp++ = 0x80 | '@';
>   ~ ~^
> 1 warning generated.
> [  3% 1916/57217] target  C:
> e2fsdroid_st...l/e2fsprogs/contrib/android/block_range.c
> In file included from external/e2fsprogs/contrib/android/block_range.c:3:
> In file included from external/e2fsprogs/contrib/android/block_range.h:5:
> In file included from external/e2fsprogs/lib/ext2fs/ext2fs.h:71:
> external/e2fsprogs/lib/ext2fs/ext2_types.h:30:9: warning: '__bitwise'
> macro redefined [-Wmacro-redefined]
> #define __bitwise
> ^
> bionic/libc/kernel/uapi/linux/types.h:25:9: note: previous definition is
> here
> #define __bitwise __bitwise__
> ^
> 1 warning generated.
> [  3% 1917/57217] target  C:
> e2fsdroid_st...al/e2fsprogs/contrib/android/block_list.c
> In file included from external/e2fsprogs/contrib/android/block_list.c:1:
> In file included from external/e2fsprogs/contrib/android/block_list.h:4:
> In file included from external/e2fsprogs/contrib/android/fsmap.h:11:
> In file included from external/e2fsprogs/lib/ext2fs/ext2fs.h:71:
> external/e2fsprogs/lib/ext2fs/ext2_types.h:30:9: warning: '__bitwise'
> macro redefined [-Wmacro-redefined]
> #define __bitwise
> ^
> bionic/libc/kernel/uapi/linux/types.h:25:9: note: previous definition is
> here
> #define __bitwise __bitwise__
> ^
> 1 warning generated.
> [  3% 1918/57217] target  C:
> e2fsdroid_st...xternal/e2fsprogs/contrib/android/fsmap.c
> In file included from external/e2fsprogs/contrib/android/fsmap.c:1:
> In file included from external/e2fsprogs/contrib/android/fsmap.h:11:
> In file included from external/e2fsprogs/lib/ext2fs/ext2fs.h:71:
> external/e2fsprogs/lib/ext2fs/ext2_types.h:30:9: warning: '__bitwise'
> macro redefined [-Wmacro-redefined]
> #define __bitwise
> ^
> bionic/libc/kernel/uapi/l

Re: [android-building] Error when building android 9 source (ubuntu 18.04)

['Colin Cross' via Android Building]

Signal 4 is SIGILL, meaning the binary contained an illegal instruction.
Parts of the ART build assume that the host CPU supports at least SSE4.2
and POPCNT (
https://cs.android.com/android/platform/superproject/+/master:art/build/Android.bp;l=188).
What CPU are you building on?

On Wed, Dec 18, 2019 at 11:35 AM Eliane Fonseca 
wrote:

> The error message is attached below. It always fails at this point, with
> the same exact error message. The error is:
>
> [ 4% 809/19992] Hidden API:
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> FAILED:
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> /bin/bash -c "(rm -f
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> ) && (cp
> \"out/soong/.intermediates/frameworks/base/test-base/android.test.base/android_common/dex/android.test.base.jar\"
> \"out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar\"
> ) && (rm -rf
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> ) && (mkdir -p
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> ) && (unzip -q
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> 'classes*.dex' -d
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> ) && (find
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> -name \"classes*.dex\" | sort | sed 's/^/--dex=/' | xargs
> out/host/linux-x86/bin/hiddenapi
> --light-greylist=out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt
> --dark-greylist=out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt
> --blacklist=out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt ) &&
> (out/soong/host/linux-x86/bin/soong_zip -o
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar
> -C
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> -D
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi
> ) && (out/soong/host/linux-x86/bin/merge_zips -D -zipToNotStrip
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar
> -stripFile \"classes*.dex\"
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
> out/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar
> out/soong/.intermediates/frameworks/base/test-base/android.test.base/android_common/dex/android.test.base.jar
> )" xargs: out/host/linux-x86/bin/hiddenapi: terminated by signal 4
>
> PS. I posted this isssue on Stack Overflow but they closed my thread and
> asked me to post here.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/3e4a52ba-a9bd-4fbb-805b-35e8ea56ae44%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRSXpztQThCV2Kai5JKDOmLd9EC9i8HkmmXVGZRMGNzgVA%40mail.gmail.com.

Re: [android-building] mm including n number of files

['Colin Cross' via Android Building]

In Q and earlier, `mm` builds and installs the modules in the current
directory and usually subdirectories, but does not build or install
dependencies outside the current directory, but `mma` will build and
install modules in the current directory and their dependencies.  In AOSP
master `mm` is an alias for `mma`, so it will build and install
dependencies.

On Mon, Jan 6, 2020 at 10:09 AM Pranitha Reddy <
pranitha.alugube...@gmail.com> wrote:

> Hello sir,
>
> mm command is used for building and installing all the modules in the
> current directory, My query is why does it includes all the Android.mk
> present in other directories(not the current one). Does mm command installs
> both modules and their dependencies?
>
> Thanks in advance!!
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/f6021264-4662-421e-81e0-2a9bef8ee104%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRRejVW1%2BCUw5JoQUYg4MLZ_YG%3Deaa_Od-y5oPFDo0X2GQ%40mail.gmail.com.

Re: [android-building] “compatibility.mk” in aosp of vts building means

['Colin Cross' via Android Building]

COMPATIBILITY.* variables are set here:
https://cs.android.com/android/platform/superproject/+/master:build/make/core/definitions.mk;l=2899?q=file:build%2Fmake%20COMPATIBILITY%5C
.
You normally add modules to android-vts.zip by setting LOCAL_TEST_SUITES :=
vts in an Android.mk file or test_suites: ["vts"] in an Android.bp file.

On Thu, Jan 16, 2020 at 9:23 AM xiang tianyu 
wrote:

> hellp ,can you help me with this problem about "compatibility.mk" of vts
> building system.
>
>
> the source code of "compatibility.mk" is in aosp code ,it's path is
> "build/make/core/tasks/tools/compatibility.mk"
>
>
> there is a line in "compatibility.mk" which is "test_artifacts :=
> $(COMPATIBILITY.$(test_suite_name).FILES)"
>
>
> I try to change the $(test_suite_name) ,but it can not package files to
> android-vts.zip,how does the COMPATIBILITY work?
>
>
> I can not find the defination of COMPATIBILITY.
>
>
> wish your help ,thank you
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/769ed951-666c-44f6-baff-cc2da905518b%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRRANUya7Y5ap%3DzOsZvawAwpjPomppKZH8fB-jxRt2nhvg%40mail.gmail.com.

Re: [android-building] Generate external/llvm Intrinsics.gen and Attributes.inc on android10

['Colin Cross' via Android Building]

Those files are generated by the llvm_tblgen modules in
external/llvm/Android.bp.  You'll find their outputs at:
out/soong/.intermediates/external/llvm/llvm-gen-attributes/gen/llvm/IR/Attributes.inc
out/soong/.intermediates/external/llvm/llvm-gen-intrinsics/gen/llvm/IR/Intrinsics.gen

As a hack you could copy those files to the places where the Android.mk
files create them, just be aware they will not be updated if you make
changes to the source files and rebuild.  You could also try reverting the
change that removed generating those files in Make:
commit 7ebb1e3516ebd630aa3fe94f9b4cca2c2dbb09ae
Author: Dan Willemsen 
Date:   Thu Nov 1 00:16:34 2018 -0700

Disable tblgen in Make

The last user of these have been removed. simpleperf is still using
LLVM_HOST_BUILD_MK and LLVM_DEVICE_BUILD_MK, so these can't all be
removed yet.

Test: treehugger
Change-Id: I0b3966fa5630e9795a1e7d7b9658f9a2bcad5271

You'll likely have better success building opt, llvm-link and llc using
Android.bp files than trying to get the old Android.mk files to work though.

On Mon, Mar 2, 2020 at 12:49 PM Paschalis Mpeis 
wrote:

> Hi there,
>
> I am building some tools from *external/llvm*, specifically *opt*,
> *llvm-link*, and* llc*.
> For this, I revived the relevant Android.mk from previous commits
> (for each of the tools, and a relevant portion at
> external/llvm/Android.mk).
> They are normally picked up by the soong build system, and I can for
> example call: `m opt`.
>
> However, these tools depend on *two intermediates*:
>
>-
>
> target/product//gen/EXECUTABLES/opt_intermediates/llvm/IR/Attributes.inc
>-
>
> target/product//gen/EXECUTABLES/opt_intermediates/llvm/IR/Intrinsics.gen
>
> I have enabled FORCE_BUILD_LLVM_COMPONENTS (see here
> 
> )
> and I can see there are relevant entries for what I want at lines: 148
> 
>  and  154
> 
> .
>
> So, is my question is: is there a way to generate those 2 intermediate
> files using the existing Android.bp setup on android10-release branch
> 
> ?
>
> Cheers,
> Paschalis
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/6e937488-80cb-42c8-b15c-087cafb7c400%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRT279w0e%2BT%2B3o2zEQBc0JFEo6gEjfgrJjiLq%3DSXpZ25MQ%40mail.gmail.com.

Re: [android-building] make android images Bad page map in process soong_build

['Colin Cross' via Android Building]

This looks like a similar issue we saw in 2017 on build servers running
kernel 3.13.0, we haven't seen it recently. Try updating your kernel.

On Thu, May 14, 2020 at 7:56 PM Minghui Ma  wrote:

> hi all
>  i make android images on ubuntu  but sometimes the server hang, I found
> the log from /var/log/kern.log like below:
>
> May 13 22:39:49 buildsrv-198 kernel: [562085.261803] BUG: Bad rss-counter
> state mm:88126ec7bb80 idx:1 val:1
> May 13 22:51:50 buildsrv-198 kernel: [562801.158633] general protection
> fault:  [#2] SMP
> May 13 22:51:50 buildsrv-198 kernel: [562801.249985] Modules linked in:
> iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat
> nf_conntrack ip_tables x_tables esn_cfs(OF) binfmt_misc ipmi_devintf dcdbas
> x86_pkg_temp_thermal coretemp kvm_intel kvm mxm_wmi crct10dif_pclmul
> crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul
> glue_helper ablk_helper cryptd lpc_ich mei_me mei shpchp ipmi_si wmi
> acpi_power_meter mac_hid lp parport tg3 ahci ptp libahci megaraid_sas
> pps_core
> May 13 22:51:50 buildsrv-198 kernel: [562801.547292] CPU: 49 PID: 196401
> Comm: GC Thread#33 Tainted: GF   B DO 3.13.0-32-generic #57-Ubuntu
> May 13 22:51:50 buildsrv-198 kernel: [562801.647136] Hardware name: Dell
> Inc. PowerEdge R730xd/0WCJNT, BIOS 2.8.0 005/17/2018
> May 13 22:51:50 buildsrv-198 kernel: [562801.746548] task:
> 8800273917f0 ti: 880134d46000 task.ti: 880134d46000
> May 13 22:51:50 buildsrv-198 kernel: [562801.845820] RIP:
> 0010:[]  [] down_read_trylock+0x9/0x30
> May 13 22:51:50 buildsrv-198 kernel: [562801.946341] RSP:
> :880134d476c8  EFLAGS: 00010282
> May 13 22:51:50 buildsrv-198 kernel: [562802.046345] RAX: 
> RBX: 881267e68080 RCX: 880134d47828
> May 13 22:51:50 buildsrv-198 kernel: [562802.146566] RDX: 
> RSI: 0001 RDI: 80122b41290e
> May 13 22:51:50 buildsrv-198 kernel: [562802.246571] RBP: 880134d476c8
> R08: 000c R09: 
> May 13 22:51:50 buildsrv-198 kernel: [562802.346575] R10: 88107fffbf00
> R11: 0013 R12: 881267e68081
> May 13 22:51:50 buildsrv-198 kernel: [562802.446796] R13: ea0027b91000
> R14: 80122b41290e R15: 880134d47808
> May 13 22:51:50 buildsrv-198 kernel: [562802.547263] FS:
> 7f93b9169700() GS:88203ed0() knlGS:
> May 13 22:51:50 buildsrv-198 kernel: [562802.649305] CS:  0010 DS: 
> ES:  CR0: 80050033
> May 13 22:51:50 buildsrv-198 kernel: [562802.751346] CR2: 821b4840
> CR3: 0001170ea000 CR4: 003407e0
> May 13 22:51:50 buildsrv-198 kernel: [562802.854774] DR0: 
> DR1:  DR2: 
> May 13 22:51:50 buildsrv-198 kernel: [562802.957740] DR3: 
> DR6: fffe0ff0 DR7: 0400
> May 13 22:51:50 buildsrv-198 kernel: [562803.060107] Stack:
> May 13 22:51:50 buildsrv-198 kernel: [562803.161742]  880134d476f8
> 81184b45 ea0027b91000 
> May 13 22:51:50 buildsrv-198 kernel: [562803.266012]  880134d47900
> 881267e68081 880134d47768 81184d9f
> May 13 22:51:50 buildsrv-198 kernel: [562803.370635]  ea0031a71b80
> 880134d47828 880134d47828 
> May 13 22:51:50 buildsrv-198 kernel: [562803.473982] Call Trace:
> May 13 22:51:50 buildsrv-198 kernel: [562803.574946]  []
> page_lock_anon_vma_read+0x55/0x110
> May 13 22:51:50 buildsrv-198 kernel: [562803.675928]  []
> page_referenced+0x19f/0x310
> May 13 22:51:50 buildsrv-198 kernel: [562803.775281]  []
> shrink_page_list+0x45c/0xa60
> May 13 22:51:50 buildsrv-198 kernel: [562803.873599]  []
> shrink_inactive_list+0x1c2/0x530
> May 13 22:51:50 buildsrv-198 kernel: [562803.971592]  []
> shrink_lruvec+0x355/0x6f0
> May 13 22:51:50 buildsrv-198 kernel: [562804.068770]  []
> shrink_zone+0x66/0x1a0
> May 13 22:51:50 buildsrv-198 kernel: [562804.164644]  []
> do_try_to_free_pages+0xe0/0x540
> May 13 22:51:50 buildsrv-198 kernel: [562804.260438]  []
> try_to_free_pages+0xec/0x180
> May 13 22:51:50 buildsrv-198 kernel: [562804.356260]  []
> __alloc_pages_nodemask+0x7d6/0xb80
> May 13 22:51:50 buildsrv-198 kernel: [562804.452624]  []
> alloc_pages_vma+0x9a/0x140
> May 13 22:51:50 buildsrv-198 kernel: [562804.549125]  []
> do_huge_pmd_anonymous_page+0x10b/0x410
> May 13 22:51:50 buildsrv-198 kernel: [562804.646384]  []
> handle_mm_fault+0x198/0xf00
> May 13 22:51:50 buildsrv-198 kernel: [562804.743674]  []
> ? wake_up_state+0x10/0x20
> May 13 22:51:50 buildsrv-198 kernel: [562804.841042]  []
> ? wake_futex+0x66/0x90
> May 13 22:51:50 buildsrv-198 kernel: [562804.937896]  []
> __do_page_fault+0x184/0x560
> May 13 22:51:50 buildsrv-198 kernel: [562805.034942]  []
> ? acct_account_cputime+0x1c/0x20
> May 13 22:51:50 buildsrv-198 kernel: [562805.132337]  []
> ? account_user_time+0x8b/0xa0
> May 13 22:51:50 buildsrv-198 kernel: [562805.229542]  []
> ? vti

Re: [android-building] how to debug soong?

['Colin Cross' via Android Building]

See
https://android.googlesource.com/platform/build/soong/+/master/README.md#running-soong-in-a-debugger

On Thu, Aug 6, 2020 at 6:14 PM Chen Wang  wrote:

> hello,
> I want to setup env to debug soong code to see what is happening when
> runSoong. Is there any guide/manual on how to setup this? Thanks in adv.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/2a78af86-8058-4c4e-b6e4-fa9be93d3766n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRT6iBYQhpxri5Li%3Dn-grGBnVwVLMCWGB-%3DeXNR_YWTHug%40mail.gmail.com.

Re: [android-building] how to build Android.bp Build Docs?

['Colin Cross' via Android Building]

You can see the latest version from AOSP master at
https://ci.android.com/builds/latest/branches/aosp-build-tools/targets/linux/view/soong_build.html,
or if you've completed a build locally the docs should be
at $OUT_DIR/soong/docs/soong_build.html.

On Fri, Aug 7, 2020 at 9:28 AM Chen Wang  wrote:

> hello,
> when I google aosp build related articles on internet, I got this
> https://note.qidong.name/demo/soong_build/, I think it should be
> constructed from the aosp sourcecode but I don't know how to make this with
> the latst version (10)？
> Anybody can help direct me on this？ Thanks in advance.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/139c8de2-93fc-4944-99b7-a93624217ba0n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRQfM7UEkqKL0ysr8Naqcr0eNBYDURfxA%3DKL9MwpquxPww%40mail.gmail.com.