Re: [android-building] Adding dependencies for Header Libraries

['Dan Willemsen' via Android Building]

Why does a header library need another module to be compiled first? It's
not actually compiling anything. I'm assuming you actually want to export
the dependencies that generated some header files? Depending on the full
compilation of a dependency will cause your builds to be more linear (and
thus slower).

If you're generating headers, adding them to LOCAL_GENERATED_SOURCES will
add the appropriate dependencies. They need to be in the proper location in
order for the include directories to be handled anyways.

There is LOCAL_EXPORT_C_INCLUDE_DEPS, but unless you're doing something
really weird, you shouldn't need to do that. If you're just re-exporting
another module's generated header files, that module should be setting up
the exported dependencies, and we'll automatically pass those along.


In Soong, this is a bit more standardized, as you're rarely writing the
explicit rules. Anything that looks like a genrule (implements
SourceFileGenerator
<https://android.googlesource.com/platform/build/soong/+/master/genrule/genrule.go#58>)
can be used in generated_headers / export_generated_headers:

cc_library_headers {
name: "my_header_library",
...
generated_headers: ["my_genrule_type_module"],
export_generated_headers: ["my_genrule_type_module"],
}

- Dan

On Wed, Oct 16, 2019 at 9:58 AM Vinayak Soni 
wrote:

> Hi,
>
> Suppose my header library depends on another module to be compiled first.
> For other modules, you can add LOCAL_ADDITIONAL_DEPENDENCIES but that does
> not work for HEADER_LIBRARIES. Is there a way this can be done?
>
> TIA,
> Vinayak
>
> --
> --
> 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/8735b4b2-0a0c-4a0c-a422-88d2b5037330%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/8735b4b2-0a0c-4a0c-a422-88d2b5037330%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DGrwTMkzQt1BdJB%2BjPJqZnyDjBo-QvfqNc_4Vfr3wZMA%40mail.gmail.com.

Re: [android-building] sub_dir unrecognized property

['Dan Willemsen' via Android Building]

LOCAL_MODULE_PATH wasn't strictly necessary in make either -- if you had
set `LOCAL_PROPRIETARY_MODULE := true` like the `proprietary: true` in the
Android.bp, it would get installed into the correct location. The
`androidmk` tool tries to auto-fix some cases of LOCAL_MODULE_PATH, but it
can't understand everything. So the `prebuilt_etc` module that you wrote
should install into /vendor/etc/location.pem (or /system/vendor if there's
no vendor partition).

What will break is the "../" in the src field -- we don't allow references
outside of the current directory and its subdirectories in Soong. We
require the directory with the sources to opt-into being used by others,
either by directly defining the modules, or by defining filegroup modules
that can be used in the src[s] fields via ":myfilegroup" (colon-prefixed
module name). This way we can actually let you control who uses files
within your directory (via visibility), and tools like `mma` and `atest`
are more likely to be able to handle "build/test everything in this
directory" properly.

- Dan

On Thu, Oct 17, 2019 at 9:35 AM Akanksha  wrote:

> Hello, I am trying to convert Android.mk to Android.bp files here is a
> sample .mk module
>
> include $(CLEAR_VARS)
> LOCAL_MODULE:= location.pem
> LOCAL_MODULE_OWNER  := x
> LOCAL_MODULE_TAGS   := optional
> LOCAL_MODULE_CLASS  := ETC
> LOCAL_SRC_FILES :=
> ../../.././target/product/msmnile/vendor/etc/location.pem
> LOCAL_MODULE_PATH   := $(PRODUCT_OUT)/$(TARGET_COPY_OUT_VENDOR)/etc
> include $(BUILD_PREBUILT)
>
> when i Convert this to
>
> prebuilt_etc {
> name: "location.pem",
> owner: "x",
>
> src: "../../.././target/product/msmnile/vendor/etc/location.pem",
> proprietary: true,
>
> }  it works fine but when included sub_dir inplace of LOCAL_MODULE_PATH I
> am getting "sub_dir " unrecognized property
>
> How to change LOCAL_MODULE_PATH module descriptor in Android.bp,
> 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/051f8105-57ee-4f3a-aabe-3359dec9142d%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/051f8105-57ee-4f3a-aabe-3359dec9142d%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnaa9XvJphVbXE9F4Zxr3U7YAZemA26_DUCr4V8czvnZQ%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

We don't allow references outside of the current directory and its
subdirectories in Soong. We require the directory with the sources to
opt-into being used by others, either by directly defining the modules, or
by defining filegroup modules that can be used in the src[s] fields via
":myfilegroup" (colon-prefixed module name). This way we can actually let
you control who uses files within your directory (via visibility), and
tools like `mma` and `atest` are more likely to be able to handle
"build/test everything in this directory" properly.

So in this case, either move the Android.bp up to the parent path (which
usually makes sense for parents, or for apps that have "src" / "jni" /
"res" dirs, as we do automatically look for files in the same directory for
some things), or define a filegroup in the parent and use it below (this
can be more useful if the same file is used by multiple children, though it
may make more sense to use a static library or something more specific).

That error is that you have multiple definitions of the same module, and is
unlikely to be related to just moving an Android.bp upwards (unless it was
below a `soong_namespace {}` definition, but that means you weren't using
that Android.bp in the first place).

- Dan


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

> hello,
> say in a Android.bp file srcs:["../../../a.cpp"]
> I am getting the error Path is outside directory "../../../a.cpp"? How to
> overcome this?
>
> Later I tried declaring Android.bp in to a parent folder so that
> srcs:["a.cpp"] but then ,
> FAILED:
> build/make/core/base_rules.mk:325: error: /gps-noship/cacert_location:
> MODULE.TARGET.ETC.cacert_location.pem already defined by /prebuilt_HY11.
> 02:01:45 ckati failed with: exit status 1
>
>  failed to build some targets (02:16 (mm:ss)) 
>
> How to overcome these?
> 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/75ea2ea6-f85b-4577-a98c-1fd42f867150%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/75ea2ea6-f85b-4577-a98c-1fd42f867150%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DXqqOGRCSHorr1UFV%3Dok%3DLHqEGmRrru9vGP%2BswDiZTxw%40mail.gmail.com.

Re: [android-building] writing header libraries in Android.bp

['Dan Willemsen' via Android Building]

COPY_HEADERS is deprecated in Make, and unsupported in Soong. Use a header
library instead. That may require re-arranging your source tree, or
creating a directory full of symlinks, as we don't support rewriting the
directory structures the same was as COPY_HEADERS, you just export
everything under a directory.

I had written some about this in our best practices doc:
https://android.googlesource.com/platform/build/soong/+/master/docs/best_practices.md#headers

- Dan

On Mon, Oct 14, 2019 at 9:46 AM REGURI AKANKSHA 
wrote:

> How to write headers in Android.bp?
>
> say Android.mk has header of this type
> include $(CLEAR_VARS)
> LOCAL_COPY_HEADERS_TO := x
> LOCAL_COPY_HEADERS:= y
> LOCAL_PROPRIETARY_MODULE := z
> include $(BUILD_COPY_HEADERS)
>
> How to write such headers in Android.bp? i know that LOCAL_COPY_HEADERS is
> deprecated in Soong, but have no idea of how to write to Android.bp
> 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/2ac5ecc7-d171-4d9e-9a6c-a92fd9612cfa%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/2ac5ecc7-d171-4d9e-9a6c-a92fd9612cfa%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmv%2BqMn8%2BdhaXDWZvn_n%2BaTCmu67PJ8tiuuK4KufDtSPA%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

Here's an example of using a filegroup for this --
cts/hostsidetests/media/common/**/*.java is used by two modules under
cts/hostsidetests/media/app/...

So we've got the filegroup that defines all the files in the common
directory:
cts/hostsidetests/media/Android.bp
<https://android.googlesource.com/platform/cts/+/5e4cf896152ad4ef4218f180800dc864ba16e84c/hostsidetests/media/Android.bp#38>
filegroup {
name: "CtsMediaSessionTestCommon",
srcs: ["common/**/*.java"],
}

And then used in the srcs list with ":CtsMediaSessionTestCommon":
cts/hostsidetests/media/app/MediaSessionTest/Android.bp
<https://android.googlesource.com/platform/cts/+/5e4cf896152ad4ef4218f180800dc864ba16e84c/hostsidetests/media/app/MediaSessionTest/Android.bp>
android_test_helper_app {
name: "CtsMediaSessionHostTestApp",
defaults: ["cts_defaults"],
test_suites: [
"cts",
"vts",
"general-tests",
],
srcs: [
"src/**/*.java",

*":CtsMediaSessionTestCommon",*],
static_libs: [
"androidx.test.rules",
"compatibility-device-util-axt",
],
sdk_version: "test_current",
min_sdk_version: "26",
}

In this case, it may have been possible to instead refactor the common file
into a library that would be used instead (and then only compiling the
files once instead of 2 times), but both would function.

- Dan

On Thu, Oct 17, 2019 at 3:08 PM REGURI AKANKSHA 
wrote:

> Thanks,Dan I was able to tackle the above error. I am new to these things.
> Can u explain this  filegroup with an example, like by defining some
> module, that would be really helpful
> Thanks in advance
>
> On Thu, Oct 17, 2019 at 10:19 PM 'Dan Willemsen' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> We don't allow references outside of the current directory and its
>> subdirectories in Soong. We require the directory with the sources to
>> opt-into being used by others, either by directly defining the modules, or
>> by defining filegroup modules that can be used in the src[s] fields via
>> ":myfilegroup" (colon-prefixed module name). This way we can actually let
>> you control who uses files within your directory (via visibility), and
>> tools like `mma` and `atest` are more likely to be able to handle
>> "build/test everything in this directory" properly.
>>
>> So in this case, either move the Android.bp up to the parent path (which
>> usually makes sense for parents, or for apps that have "src" / "jni" /
>> "res" dirs, as we do automatically look for files in the same directory for
>> some things), or define a filegroup in the parent and use it below (this
>> can be more useful if the same file is used by multiple children, though it
>> may make more sense to use a static library or something more specific).
>>
>> That error is that you have multiple definitions of the same module, and
>> is unlikely to be related to just moving an Android.bp upwards (unless it
>> was below a `soong_namespace {}` definition, but that means you weren't
>> using that Android.bp in the first place).
>>
>> - Dan
>>
>>
>> On Tue, Oct 15, 2019 at 8:27 AM   wrote:
>>
>>> hello,
>>> say in a Android.bp file srcs:["../../../a.cpp"]
>>> I am getting the error Path is outside directory "../../../a.cpp"? How
>>> to overcome this?
>>>
>>> Later I tried declaring Android.bp in to a parent folder so that
>>> srcs:["a.cpp"] but then ,
>>> FAILED:
>>> build/make/core/base_rules.mk:325: error: /gps-noship/cacert_location:
>>> MODULE.TARGET.ETC.cacert_location.pem already defined by /prebuilt_HY11.
>>> 02:01:45 ckati failed with: exit status 1
>>>
>>>  failed to build some targets (02:16 (mm:ss)) 
>>>
>>> How to overcome these?
>>> 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 t

Re: [android-building] Re: How to install prebuilt_apps?

['Dan Willemsen' via Android Building]

The best thing to do is to leave them in Android.mk for now, converting
them next year when you integrate the R release (which is what master will
be).

- Dan

On Fri, Oct 25, 2019, 8:31 AM seekers here  wrote:

> Thanks Dan.
> I am using a branch of Android Q code. So Now whats the solution for this
> issue? How to convert APPS module class
>
> On Fri, Oct 25, 2019 at 12:30 PM 'Dan Willemsen' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> Which branch are you using? `android_app_import` is the module type, but
>> it didn't make it into Android Q(10), it's only in master.
>>
>> - Dan
>>
>> On Wed, Oct 23, 2019 at 7:52 AM REGURI AKANKSHA 
>> wrote:
>>
>>> I tried above think, but I am getting Androidmk translation errors like
>>> unsupported include etc..
>>>
>>>
>>> On Tue, Oct 22, 2019 at 9:38 PM shankar kumar yellapu <
>>> shankarkumaryel...@gmail.com> wrote:
>>>
>>>>
>>>> androidmk Android.mk > Android.bp
>>>>
>>>> Run the above command from your android build tree after doing source 
>>>> build/envsetup.sh
>>>>
>>>> https://android.googlesource.com/platform/build/soong/
>>>>
>>>> Regards,
>>>> Shankar
>>>>
>>>>
>>>> On Sunday, October 20, 2019 at 10:09:55 PM UTC+5:30, seeker wrote:
>>>>>
>>>>> Hello, Im trying to convert .mk to .bp files. I am struck how to
>>>>> convert below module class!!
>>>>>
>>>>> include $(CLEAR_VARS)
>>>>> LOCAL_MODULE:= x
>>>>> LOCAL_MODULE_CLASS  := APPS
>>>>> LOCAL_SRC_FILES := --
>>>>> LOCAL_MODULE_PATH   := -
>>>>> include $(BUILD_PREBUILT)
>>>>>
>>>>> How to install prebuilt_apps for Android.bp?
>>>>> 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/368b0077-b371-464e-97ac-d10c2f100033%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/android-building/368b0077-b371-464e-97ac-d10c2f100033%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> --
>>> --
>>> 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/CA%2BVoWj5o%3DuBtfA6YaOda_RcUeiHUb2uOgZas_Y7JWnMqf%3DeDyA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/android-building/CA%2BVoWj5o%3DuBtfA6YaOda_RcUeiHUb2uOgZas_Y7JWnMqf%3DeDyA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> --
>> 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://

Re: [android-building] sub_dir as module descriptor

['Dan Willemsen' via Android Building]

Where are you trying to use sub_dir? (which module type? at the top level?)
It's only supported on some of the prebuilt module types (and sh_binary).
For some other module types, relative_install_path is used instead
(cc_binary, cc_library, etc)

You can see the documentation about supported properties here:
https://ci.android.com/builds/latest/branches/aosp-build-tools/targets/linux/view/soong_build.html
(this is based on master, if you're working on Q, not everything here may
work -- there's a local copy in $OUT_DIR/soong/docs/soong_build.html).

- Dan

On Fri, Oct 25, 2019 at 12:52 AM seeker  wrote:

> Hello,
> How to introduce sub_dir as a module descriptor for Android.bp?
> Whenever I introduce sub_dir, I am always getting this error: sub_dir
> unrecognized property. How to overcome 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/d732a44d-3f82-4dd1-9d00-15a10142579e%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/d732a44d-3f82-4dd1-9d00-15a10142579e%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnkiyr%2BSKAB3AgEuGYSOae4kS4bEhhZLPyjSdGFVd0yDg%40mail.gmail.com.

Re: [android-building] Re: Java error building AOSP 10

['Dan Willemsen' via Android Building]

Yep, I've reproduced this on minimal installs of both ArchLinux and Ubuntu.
`apt install fontconfig` fixes it on Ubuntu. On Arch, I had to install
fontconfig and a font (I tried ttf-droid) before it started working.

- Dan

On Sat, Nov 23, 2019 at 7:41 PM Daniel Fullmer  wrote:

> I believe I've encountered this error in the past. I was able to work around
> this by installing freetype / fontconfig (can't recall if one or both are
> necessary).
>
> On Saturday, November 23, 2019 at 9:15:36 PM UTC-5, Brian Moore wrote:
>>
>>
>> I've been building AOSP for my pixel devices for a few versions now, but
>> I'm running into an issue in the release of Android 10.
>>
>> I'm working with 10.0.0 r10, building for Pixel 3 (blueline).
>> I have the Google and QCom vendor binaries in the vendor/ tree, just as
>> I've always done.
>> I do a normal build process as shown in the attached file, and it always
>> fails at the same point.
>>
>> I broke down the cluster of commands that it was failing on, and found it
>> was this specific statement throwing the error:
>>
>> java -jar out/host/linux-x86/framework/RecoveryImageGenerator.jar 
>> --image_width
>> $((1080 - 10)) --text_name recovery_installing --font_dir out/target/
>> product/blueline/obj/PACKAGING/recovery_font_files_intermediates 
>> --resource_dir
>> bootable/recovery/tools/recovery_l10n/res/ --output_file out/target/
>> product/blueline/obj/PACKAGING/recovery_text_res_intermediates//installing_text.png
>> --center_alignment
>>
>> I found that if I ran this part of the build with Java 8 instead of Java
>> 9 (by modifying my default PATH), it worked.
>> But using Java 8 for the entire build causes other errors, and from what
>> I have read, Android 10 is supposed to be built with Java 9 only.
>>
>> The only thing that I'm doing differently than with builds of previous
>> versions of Android is that I am building without the vendor/opengapps
>> tree, because OpenGapps hasn't created a repository for Android 10.
>> However, I'm pretty sure that Google apps are not required just for a stock
>> AOSP build.
>>
>> Any idea what the problem could be?  I'm thinking I must have some
>> configuration wrong on my end, because I'm basically building the
>> unmodified source directly from Google.
>>
> --
> --
> 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/308ada71-a2f5-4f66-8e29-8fa76abce1ea%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/308ada71-a2f5-4f66-8e29-8fa76abce1ea%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DdHB2kh8Q7b9jBuxBjdvzbWS-dcyHqEUHYWx1%2BN5MdSA%40mail.gmail.com.

Re: [android-building] AOSP sepolicy_tests_intermediates/sepolicy_tests error on building using MAC Catalina

['Dan Willemsen' via Android Building]

If you're trying to build android 10 (and not master), your best bet would
be to run a VM with Linux in order to build -- it very well may be a faster
build, and it will be a lot closer to what actually ships. The Mac build
works well enough for development, but it's not as complete as the Linux
build, and tends to require older Mac versions (the Mac version that was
out when the Android version was being developed -- in this case, Android
10 should work fine with 10.14, but not 10.15).

It looks like it's crashing because libc++ is being embedded twice into the
process (once as a shared library, then statically in the dlopened
libsepolwrap.so). I've got a fix here:
https://android-review.googlesource.com/c/platform/system/sepolicy/+/1173528

- Dan

On Sat, Nov 23, 2019 at 6:15 PM Dr. Dhanyu Eshaka  wrote:

> No moved back to Mojave . MAC OSX 10.14
> I think those errors has to do with Python compatibility issue or
> libsepolwrap.dylib conflict with Catalina
>
> Please let me know if you fix this. I am curious to know
>
> - Dhanyu
>
>
>
> On Fri, Nov 22, 2019 at 7:11 AM Jianwu Gao  wrote:
>
>> Hi
>> I got same errors，not fixed yet
>> Have you fix this issue?
>>
>> Dr. Dhanyu Eshaka  于2019年11月18日周一 上午1:23写道：
>>
>>> After updating MAC OSX to 10.15.1 (Catalina) I get the following errors
>>> on sepolicy.
>>>
>>> The target build device is Pixel 3a XL ( android-10.0.0_r10)
>>>
>>> I need to resolve this ASAP. Any help would be appreciated.
>>>
>>> [ 77% 78861/101937] build
>>> out/target/product/bonito/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
>>>
>>> FAILED:
>>> out/target/product/bonito/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
>>>
>>> /bin/bash -c "(out/host/darwin-x86/bin/sepolicy_tests -l
>>> out/host/darwin-x86/lib64/libsepolwrap.dylib  -f
>>> out/target/product/bonito/obj/ETC/plat_file_contexts_intermediates/plat_file_contexts
>>> -f
>>> out/target/product/bonito/obj/ETC/vendor_file_contexts_intermediates/vendor_file_contexts
>>> -p out/target/product/bonito/obj/ETC/sepolicy_intermediates/sepolicy )
>>> && (touch
>>> out/target/product/bonito/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
>>> )"
>>>
>>> /bin/bash: line 1:  8780 Segmentation fault: 11  (
>>> out/host/darwin-x86/bin/sepolicy_tests -l
>>> out/host/darwin-x86/lib64/libsepolwrap.dylib -f
>>> out/target/product/bonito/obj/ETC/plat_file_contexts_intermediates/plat_file_contexts
>>> -f
>>> out/target/product/bonito/obj/ETC/vendor_file_contexts_intermediates/vendor_file_contexts
>>> -p out/target/product/bonito/obj/ETC/sepolicy_intermediates/sepolicy )
>>>
>>> 06:54:50 ninja failed with: exit status 1
>>>
>>> --
>>> --
>>> 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/3abf0458-046d-4e69-8faf-fa483941e10b%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/3abf0458-046d-4e69-8faf-fa483941e10b%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> --
>> 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
>&

Re: [android-building] Java error building AOSP 10

['Dan Willemsen' via Android Building]

That's strange, I've got no idea why you're hitting it, but that we haven't
seen it anywhere else.

I've filed https://issuetracker.google.com/145064117 with my findings so
far.

- Dan

On Sat, Nov 23, 2019 at 6:15 PM Brian Moore  wrote:

>
> I've been building AOSP for my pixel devices for a few versions now, but
> I'm running into an issue in the release of Android 10.
>
> I'm working with 10.0.0 r10, building for Pixel 3 (blueline).
> I have the Google and QCom vendor binaries in the vendor/ tree, just as
> I've always done.
> I do a normal build process as shown in the attached file, and it always
> fails at the same point.
>
> I broke down the cluster of commands that it was failing on, and found it
> was this specific statement throwing the error:
>
> java -jar out/host/linux-x86/framework/RecoveryImageGenerator.jar 
> --image_width
> $((1080 - 10)) --text_name recovery_installing --font_dir out/target/
> product/blueline/obj/PACKAGING/recovery_font_files_intermediates 
> --resource_dir
> bootable/recovery/tools/recovery_l10n/res/ --output_file out/target/
> product/blueline/obj/PACKAGING/recovery_text_res_intermediates//installing_text.png
> --center_alignment
>
> I found that if I ran this part of the build with Java 8 instead of Java 9
> (by modifying my default PATH), it worked.
> But using Java 8 for the entire build causes other errors, and from what I
> have read, Android 10 is supposed to be built with Java 9 only.
>
> The only thing that I'm doing differently than with builds of previous
> versions of Android is that I am building without the vendor/opengapps
> tree, because OpenGapps hasn't created a repository for Android 10.
> However, I'm pretty sure that Google apps are not required just for a stock
> AOSP build.
>
> Any idea what the problem could be?  I'm thinking I must have some
> configuration wrong on my end, because I'm basically building the
> unmodified source directly from Google.
>
> --
> --
> 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/e5f6f455-2fb9-4d26-bb8e-a0fecece260f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/e5f6f455-2fb9-4d26-bb8e-a0fecece260f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmUf1z6uo%3DM9Hp%2Bep%2B6KsqP2Cg8FviB9%2BVjhO9Xd-ar6w%40mail.gmail.com.

Re: [android-building] Android.bp file copy issue

['Dan Willemsen' via Android Building]

The same definition would be a problem in Android.mk too -- in fact, this
warning is coming from the makefile system (since the makefile system still
handles installation for both Make and Soong).

It looks like inside Google, we're not defining `prebuilt_etc` or
`BUILD_PREBUILT` definitions for this file, instead we're installing it via
PRODUCT_COPY_FILES in your product configuration. That way every product
can choose how to install that file.

Or you could "hide" one of the modules from Make using soong namespaces,
only turning on the one that you want for a particular device. Then make
will only create a single installation rule. (I haven't tried it, but it
should work -- this is how we handle more complicated modules that need to
be different per device)

- Dan

On Wed, Oct 9, 2019 at 3:58 PM 'Kyle Cai' via Android Building <
android-building@googlegroups.com> wrote:

> Thanks Dan for the reply. Yes I do see the warning msgs you pointed out.
>
> Now the question is how should I fix this given that the destination file
> has to be google.xml? I believe previously with .mk files this was not an
> issue?
>
> Thanks in advance.
>
> Kyle
>
> On Wednesday, October 9, 2019 at 1:24:32 PM UTC-7, Dan Willemsen wrote:
>>
>> Modules must have unique output names, as the installation rules are
>> always defined. You should be seeing warnings during the build startup
>> about duplicate rules for target:
>>
>> build/make/core/base_rules.mk:481: warning: overriding commands for
>> target `out/target/product//product/etc/sysconfig/google.xml'
>> build/make/core/base_rules.mk:481: warning: ignoring old commands for
>> target `out/target/product//product/etc/sysconfig/google.xml'
>>
>> That's saying that there are two ways to build a specific installation
>> file, and we may pick one or the other (fairly arbitrarily, and sometimes
>> using a mix of the two rules).
>>
>> - Dan
>>
>> On Wed, Oct 9, 2019 at 1:09 PM 'Kyle Cai' via Android Building <
>> android-...@googlegroups.com> wrote:
>>
>>> Hi,
>>>
>>> I'm not sure if this is the right place to ask about android.bp files.
>>> Here is an issue that I'm seeing and I can't figure out why I'm seeing
>>> this. My .bp file has the following two sections, one for regular android
>>> build and one for android go:
>>>
>>> prebuilt_etc {
>>> name: "*sysconfig_google*",
>>> product_specific: true,
>>> sub_dir: "sysconfig",
>>> *src: "google.xml",*
>>> *filename_from_src: true,*
>>> }
>>>
>>> prebuilt_etc {
>>> name: "*sysconfig_google_go*",
>>> product_specific: true,
>>> sub_dir: "sysconfig",
>>> *src: "google_go.xml",*
>>> *filename: "google.xml",*
>>> }
>>>
>>> The intention is that if I'm making a regular build, a gms.mk file is
>>> used and it calls sysconfig_google. If I'm making a Go build, the
>>> gms_go.mk file is used, and that calls  sysconfig_google_go. In the
>>> source directory there is "google.xml" and "google_go.xml" and depending on
>>> which is called, it should go to the destination directory as "google.xml".
>>> However, currently when I build a regular build (non-Go), I see in the
>>> destination directory that the google.xml file has the content of the
>>> google_go.xml file. Any idea why it's doing that?
>>>
>>> Thanks,
>>>
>>> Kyle
>>>
>>> --
>>> --
>>> 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/a37db4cd-f4b0-43bf-a507-964f552873f1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/a37db4cd-f4b0-43bf-a507-964f552873f1%40googlegroups.com?utm_medium=email_source=footer>
>>

Re: [android-building] Android.bp file copy issue

['Dan Willemsen' via Android Building]

Modules must have unique output names, as the installation rules are always
defined. You should be seeing warnings during the build startup about
duplicate rules for target:

build/make/core/base_rules.mk:481: warning: overriding commands for target
`out/target/product//product/etc/sysconfig/google.xml'
build/make/core/base_rules.mk:481: warning: ignoring old commands for
target `out/target/product//product/etc/sysconfig/google.xml'

That's saying that there are two ways to build a specific installation
file, and we may pick one or the other (fairly arbitrarily, and sometimes
using a mix of the two rules).

- Dan

On Wed, Oct 9, 2019 at 1:09 PM 'Kyle Cai' via Android Building <
android-building@googlegroups.com> wrote:

> Hi,
>
> I'm not sure if this is the right place to ask about android.bp files.
> Here is an issue that I'm seeing and I can't figure out why I'm seeing
> this. My .bp file has the following two sections, one for regular android
> build and one for android go:
>
> prebuilt_etc {
> name: "*sysconfig_google*",
> product_specific: true,
> sub_dir: "sysconfig",
> *src: "google.xml",*
> *filename_from_src: true,*
> }
>
> prebuilt_etc {
> name: "*sysconfig_google_go*",
> product_specific: true,
> sub_dir: "sysconfig",
> *src: "google_go.xml",*
> *filename: "google.xml",*
> }
>
> The intention is that if I'm making a regular build, a gms.mk file is
> used and it calls sysconfig_google. If I'm making a Go build, the
> gms_go.mk file is used, and that calls  sysconfig_google_go. In the
> source directory there is "google.xml" and "google_go.xml" and depending on
> which is called, it should go to the destination directory as "google.xml".
> However, currently when I build a regular build (non-Go), I see in the
> destination directory that the google.xml file has the content of the
> google_go.xml file. Any idea why it's doing that?
>
> Thanks,
>
> Kyle
>
> --
> --
> 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/a37db4cd-f4b0-43bf-a507-964f552873f1%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/a37db4cd-f4b0-43bf-a507-964f552873f1%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdk_kXp3TJZ_NnJELDUK0jwHm_1w4KQ2zQmAvdAc%2BpRyfg%40mail.gmail.com.

Re: [android-building] Unable to compile wpa_supplicant in AOSP-10 (Android Q) by running make command in root foleder of AOSP.

['Dan Willemsen' via Android Building]

Does whichever product you're building set WPA_SUPPLICANT_VERSION so that
external/wpa_supplicant_8 is used?

https://android.googlesource.com/platform/external/wpa_supplicant_8/+/refs/heads/master/Android.mk

Is wpa_supplicant in your PRODUCT_PACKAGES? If not, you should be able to
build it with `m wpa_supplicant`

- Dan

On Thu, Oct 3, 2019 at 12:53 PM sachin verma 
wrote:

> Hi All,
>
> I have done some changes in
> external/wpa_supplicant_8/wpa_supplicant/hs20_supplicant.c file and then
> compiling it by running make command in AOSP root directory, after
> completion I can't see my changes. I checked its not compiling the
> wpa_supplicant module. It will be very helpful if someone can tell the
> reason or can tell the configuration where I can enable the compilation of
> wpa_supplicant.
>
> Thanks,
> Sachin
>
> --
> --
> 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/2c8e6527-b724-4aed-937d-907ca0821884%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/2c8e6527-b724-4aed-937d-907ca0821884%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnYvRZ6j1Tc%3DbLgCgWzpOXb5odoAtuJoENHtEEJQLWADQ%40mail.gmail.com.

Re: [android-building] how to distribute android 10/11 ?

['Dan Willemsen' via Android Building]

The build team does not recommend using Goma -- it does not work
particularly well with the Android build, and we expect to be removing
support for it in master in the coming months (support will most likely
still be in this years release, but not next years).

RBE is the replacement, but it's still evolving at the moment. Many of our
CI builds have switched to it (they never used Goma), but only a handful of
developers have used it so far. If you're interested in this, I'd highly
recommend asking your TAM about it (or if you don't have one, contact me
and I can try to route your request to the right team).

For what we're doing (other than Goma/RBE), the majority of our CI builds
are done on n1-standard-64
<https://cloud.google.com/compute/docs/machine-types#n1_machine_type>
machines with SSD persistent disks. Depending on your
limitations/requirements, the newer C2/N2 machine families may be more
efficient. For local developers, we're generally buying fast desktops -- 2x
Intel Xeon GOLD 6154 processor (18-core Skylake, up to 3.70 GHz) with 192
GB RAM and a few TB of SSDs.

- Dan

On Sun, Mar 1, 2020 at 11:52 PM 'Orion Hodson' via Android Building <
android-building@googlegroups.com> wrote:

> Hi Alexander
>
> Internally Android developers use goma. The thread below has pointers to
> the client and server. It is built on GCP.
>
>
> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/eOtBzosZtd8
>
> Kind regards
> Orion
>
> On Sun, 1 Mar 2020 at 22:39, alexander zhu  wrote:
>
>> Hi,
>>
>> I faced one problem, i have tried to solve it many days.
>>
>>
>> AOSP compile on one powerful physical server(36U128G) is fast . Because
>> my company has so many people need to compile AOSP on the server,so it is
>> busy all the time , and I do not have money to buy more.But the VM I can
>> request more.So I want to use VM on the cloud to compile AOSP.
>>
>> I have some distribute compile experiences in other c/c++ projects. So
>> I'm thinking is there any way to compile AOSP in distribute way?exp: use
>> many VMs for one AOSP build.
>>
>> I noticed there had topic long time ago :
>> https://groups.google.com/forum/#!searchin/android-building/distcc%7Csort:date/android-building/_YJNwvq6FtY/EENyTx4Elk4J
>>
>> I tried distcc , but failed . AOSP switching to clang, but distcc support
>> clang not ok.https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926884
>>
>>
>> So, I want to know ,AOSP in google , how to solve the long build time
>> ?use more powerful physical server? or you have your own distribute
>> compile solution?
>>
>> --
>> --
>> 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/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com
>> <https://groups.google.com/d/msgid/android-building/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
> --
> --
> 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/CAAttue0u%2BuqgwNO4ggmnWsYS%2B8FmL8xURN-Xqt9sw9d1aLENQQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAAttue0u%2BuqgwNO4ggmnWsYS%2B8FmL8xURN-Xqt9sw9d1aLENQQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mai

Re: [android-building] how to distribute android 10/11 ?

['Dan Willemsen' via Android Building]

Oh, and for developer builds (and many frequent CI builds), we're almost
always using incremental builds, so the clean build times are somewhat less
limiting. If you're often doing clean builds or very large builds, that's
probably one of the first things to look at.

- Dan

On Tue, Mar 3, 2020 at 1:57 PM Dan Willemsen  wrote:

> The build team does not recommend using Goma -- it does not work
> particularly well with the Android build, and we expect to be removing
> support for it in master in the coming months (support will most likely
> still be in this years release, but not next years).
>
> RBE is the replacement, but it's still evolving at the moment. Many of our
> CI builds have switched to it (they never used Goma), but only a handful of
> developers have used it so far. If you're interested in this, I'd highly
> recommend asking your TAM about it (or if you don't have one, contact me
> and I can try to route your request to the right team).
>
> For what we're doing (other than Goma/RBE), the majority of our CI builds
> are done on n1-standard-64
> <https://cloud.google.com/compute/docs/machine-types#n1_machine_type>
> machines with SSD persistent disks. Depending on your
> limitations/requirements, the newer C2/N2 machine families may be more
> efficient. For local developers, we're generally buying fast desktops -- 2x
> Intel Xeon GOLD 6154 processor (18-core Skylake, up to 3.70 GHz) with 192
> GB RAM and a few TB of SSDs.
>
> - Dan
>
> On Sun, Mar 1, 2020 at 11:52 PM 'Orion Hodson' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> Hi Alexander
>>
>> Internally Android developers use goma. The thread below has pointers to
>> the client and server. It is built on GCP.
>>
>>
>> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/eOtBzosZtd8
>>
>> Kind regards
>> Orion
>>
>> On Sun, 1 Mar 2020 at 22:39, alexander zhu  wrote:
>>
>>> Hi,
>>>
>>> I faced one problem, i have tried to solve it many days.
>>>
>>>
>>> AOSP compile on one powerful physical server(36U128G) is fast . Because
>>> my company has so many people need to compile AOSP on the server,so it is
>>> busy all the time , and I do not have money to buy more.But the VM I can
>>> request more.So I want to use VM on the cloud to compile AOSP.
>>>
>>> I have some distribute compile experiences in other c/c++ projects. So
>>> I'm thinking is there any way to compile AOSP in distribute way?exp: use
>>> many VMs for one AOSP build.
>>>
>>> I noticed there had topic long time ago :
>>> https://groups.google.com/forum/#!searchin/android-building/distcc%7Csort:date/android-building/_YJNwvq6FtY/EENyTx4Elk4J
>>>
>>> I tried distcc , but failed . AOSP switching to clang, but distcc
>>> support clang not ok.
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926884
>>>
>>>
>>> So, I want to know ,AOSP in google , how to solve the long build time
>>> ?use more powerful physical server? or you have your own distribute
>>> compile solution?
>>>
>>> --
>>> --
>>> 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/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> --
>> 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
&

Re: [android-building] Build failure in local environment

['Dan Willemsen' via Android Building]

Launcher3 is generally built as part of the Android platform, so following
the instructions here should work: https://source.android.com/setup/start

If you want to build it without building the rest of the platform (which
can be quite large), you could use tapas, like here:
https://source.android.com/devices/tv/reference-tv-app

I believe the launcher team sometimes does development with gradle, but I
have no idea what the state is on that, especially on AOSP.

- Dan

On Mon, Mar 2, 2020 at 9:21 PM GUNASEELAN N  wrote:

> Hi,
>   I tried to build the Aosp Launcher3 application in my local environment
> i am getting the error in IconLoader package. I am new to this process
> first time i am doing the AOSP android build. Is there any procedure to
> build the code or any guidelines to follow please help me to solve this
> error.
> I am using master branch to build but i dont know how to solve this issue
> please anyone help me.
> I need to know,
> Which os i need to use?
> Whether i can able to build the code directly using Android studio?
> Whether i need to use any other configuration to build the launcher code
> separately?
> Is it possible to build the Launcher3 code separately?
> Is there any rules or guidelines to follow for build ?
>
> Error:
>
> could not resolve androidx.core.core:1.0.0.beta01
>
> --
> --
> 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/dd4a4fae-c8d7-433f-aba4-0c866224c7e3%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/CALQgHdkGnu74iN1ktQ92wJLKv2deDa3BKCBMGpRiEFSn-ocJ6w%40mail.gmail.com.

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

['Dan Willemsen' via Android Building]

+Matthew Maurer  Do we have any documentation on this
target? I think the last time we talked about this target it was only
minimally functional.

- Dan

On Mon, Mar 2, 2020 at 12:51 PM Julien Robin 
wrote:

> I succeeded to find a workaround for the issue I signaled here, editing
> device/generic/trusty/BoardConfig.mk and putting BUILD_QEMU_IMAGES to
> false, which still gives vendor.img, system.img and userdata.img
>
> I then found this kernel
> https://android.googlesource.com/kernel/common/+/refs/heads/android-trusty-4.19,
> and using arch/arm64/configs/trusty_qemu_defconfig, I successfully built it.
>
> Also, I'm able to start most of this Android build on Debian 10 provided
> qemu-system-aarch64 the following way :
>
> qemu-system-aarch64
> -M virt
> -cpu cortex-a57
> -smp 1
> -m 2048
> -monitor none
> -parallel none
> -serial mon:stdio
> -kernel Image -append "root=/dev/vda rootfstype=ext4 ro init=/init
> loglevel=8 selinux=1 checkreqprot=1 androidboot.selinux=permissive
> androidboot.hardware=qemu_trusty console=ttyAMA0"
> -device virtio-gpu-pci
> -drive format=raw,file=system-custom.img
> -drive format=raw,file=userdata-custom.img
>
> userdata-custom.img is just a bigger userdata.img (1024MB instead of 4) in
> which I used resize2fs, system-custom.img is just a system.img in which the
> placeholder folder "vendor" now embeds the content of vendor.img, copied by
> "cp -a". Finally, still into system-custom.img, fstab.qemu_trusty only
> contains
> LABEL=data  /data   ext4  noatime,nosuid,nodev
> ,errors=panicwait
> So that /data (available at /dev/vdb) is mounted by its label, while
> system-custom.img embeding root system and vendor is already mounted by
> kernel cmdline (by /dev/vda). ramdisk.img is not used as system.img already
> contains everything needed to start init.
>
> However, I guess I should use a slightly modified version of qemu,
> available here
> https://android.googlesource.com/trusty/external/qemu/+/refs/heads/master
> Because using Debian 10 qemu version, I get the following output, and no
> display :
>
> init: init first stage started!
> [...]
> init: Loading SELinux policy
> [...]
> selinux: SELinux: Loaded policy from /vendor/etc/selinux/
> precompiled_sepolicy
>
> selinux: SELinux: Loaded file_contexts
>
> random: init: uninitialized urandom read (40 bytes read)
> random: init: uninitialized urandom read (40 bytes read)
> init: init second stage started!
> [...]
> ueventd: Coldboot took 1.344 seconds
> [...]
> init: starting service 'storageproxyd'...
> libprocessgroup: CgroupMap::FindController called for [1] failed, RC file
> was not initialized properly
> libprocessgroup: Failed to make and chown /uid_0: Read-only file system
> libprocessgroup: CgroupMap::FindController called for [829] failed, RC
> file was not initialized properly
> init: createProcessGroup(0, 829) failed for service 'storageproxyd': Read-only
> file system
> init: cpuset cgroup controller is not mounted!
> init: Service 'storageproxyd' (pid 829) exited with status 1
> init: Sending signal 9 to service 'storageproxyd' (pid 829) process group
> ...
> libprocessgroup: CgroupMap::FindController called for [1] failed, RC file
> was not initialized properly
> libprocessgroup: CgroupMap::FindController called for [1] failed, RC file
> was not initialized properly
>
>
> init: starting service 'storageproxyd'...
> libprocessgroup: CgroupMap::FindController called for [1] failed, RC file
> was not initialized properly
> libprocessgroup: Failed to make and chown /uid_0: Read-only file system
> init: createProcessGroup(0, 830) failed for service 'storageproxyd': Read-only
> file system
> libprocessgroup: CgroupMap::FindController called for [830] failed, RC
> file was not initialized properly
> init: cpuset cgroup controller is not mounted!
> init: Service 'storageproxyd' (pid 830) exited with status 1
> init: Sending signal 9 to service 'storageproxyd' (pid 830) process group
> ...
>
> ...and so on in loop
>
> However I'm still not sure to proceed correctly, as I'm doing everything
> alone with no documentation (I may have missed it?)
>
> Is here some documentation available? If there isn't, is someone able to
> provide an example of working qemu command line (even old or unoptimized),
> or just few explanations so that I can be placed on the right track?
>
> Thank you very much in advance
>
>
> On 3/1/20 2:14 PM, Julien Robin wrote:
>>
>> Hi there,
>>
>> I see that starting from branch android-10.0.0_r1, lunch offers a choice
>> called qemu_trusty_arm64-userdebug, in whi

Re: [android-building] Using device/generic/qemu/qemu_x86_64.mk files for QEMU

['Dan Willemsen' via Android Building]

These are the instructions on how to use the android emulator (with qemu):
https://source.android.com/setup/create/avd

- Dan

On Mon, Feb 24, 2020 at 1:58 PM Julien Robin 
wrote:

> Hi folks,
>
> I need a little bit of help on building something working on QEMU (on any
> architecture but let's start with x86_64). And yes as strange at it may
> seems, I have a professional need of being able to run untouched (or almost
> untouched) AOSP on QEMU platform ;)
>
> I noticed those files : AOSP_SOURCE_DIRECTORY/device/generic/qemu/
> qemu_x86_64.mk (and others architectures). Looked like the Holy Grail
>
> I successfully added a vendorsetup.sh file to show both qemu_x86_64-eng
> and qemu_x86-eng configurations into lunch menu, and built successfully.
>
> But I have troubles running this build on QEMU, be it with the given
> kernel, or using a self built 4.14-goldfish kernel (working both with the
> AVD emulator, Android-x86 and Debian, embedding all the drivers : the
> perfect kernel! It took me some time to have the good kernel build config)
> or even using the Android-x86 boot structure to boot the resulting built
> (after having replaced and placed everything in the right place, system
> files vendor files and ramdisk content with fstab about /cache needed by
> android-x86 structure...
>
> Android is sure booting but does nothing more after the following init
> output :
>
> init: init first stage started!
>
> [..]
>
> ueventd: Coldboot took 0.03 secondslogd.auditd: start
> logd.klogd: 42157422826
> healthd: No battery devices found
> healthd: battery none chg=
>
> Is this normal from the qemu_x86_64-eng build?
> How to use the AOSP_SOURCE_DIRECTORY/device/generic/qemu/qemu_x86_64.mk
> files available into AOSP to get some Android build working with QEMU?
>
> Thank you very much in advance
> Best regards,
>
> Julien ROBIN
>
> --
> --
> 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/c31b97c5-7642-4a5e-a770-897d3e6a4f07%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/c31b97c5-7642-4a5e-a770-897d3e6a4f07%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnJ218o-A0rR-_smmQqJQRR32S%2BkR6tQULWD5%2Bi1rdM_A%40mail.gmail.com.

Re: [android-building] error build referenced by a_bitstr.c:69 (external/boringssl/src/crypto/asn1/a_bitstr.c:

['Dan Willemsen' via Android Building]

Which version of AOSP are you building? What's your build target? Do you
have any local changes?

- Dan

On Wed, Jan 22, 2020 at 10:49 PM Kiên neiK Lê Trung 
wrote:

> i got stuck build here https://del.dog/gipposirep.txt. anyone encounter
> this error.
>
> --
> --
> 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/ebb8a509-0410-4df6-a1ca-463b180f5277%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ebb8a509-0410-4df6-a1ca-463b180f5277%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmjf23Y2XA%3Dhk03Ed5jTE3bEm%2Ba6fcAttvLXFqsH3WXgQ%40mail.gmail.com.

Re: [android-building] I m building for the first time

['Dan Willemsen' via Android Building]

This is off-topic for this group, as the build error appears to be in
non-AOSP code. If I'm reading it right, your kernel is having problems
compiling (it can't find an openssl host header).

- Dan

On Thu, Jan 30, 2020 at 2:02 PM Dnyanesh Mohite  wrote:

> CHK include/generated/utsrelease.h WRAP
> arch/arm64/include/generated/asm/set_memory.h WRAP
> arch/arm64/include/generated/asm/sizes.h WRAP
> arch/arm64/include/generated/asm/switch_to.h UPD
> include/generated/utsrelease.h WRAP
> arch/arm64/include/generated/asm/trace_clock.h WRAP
> arch/arm64/include/generated/asm/unaligned.h WRAP
> arch/arm64/include/generated/asm/user.h WRAP
> arch/arm64/include/generated/asm/vga.h WRAP
> arch/arm64/include/generated/asm/xor.h HOSTCC scripts/genksyms/genksyms.o
> HOSTCC scripts/dtc/dtc.o CC scripts/mod/empty.o HOSTCC
> scripts/selinux/genheaders/genheaders SHIPPED scripts/genksyms/parse.tab.c
> HOSTCC scripts/dtc/flattree.o SHIPPED scripts/genksyms/lex.lex.c SHIPPED
> scripts/genksyms/parse.tab.h HOSTCC scripts/genksyms/parse.tab.o HOSTCC
> scripts/mod/mk_elfconfig HOSTCC scripts/genksyms/lex.lex.o HOSTCC
> scripts/selinux/mdp/mdp HOSTCC scripts/dtc/fstree.o CC
> scripts/mod/devicetable-offsets.s HOSTCC scripts/dtc/data.o HOSTCC
> scripts/kallsyms HOSTCC scripts/dtc/livetree.o MKELF
> scripts/mod/elfconfig.h CHK scripts/mod/devicetable-offsets.h HOSTLD
> scripts/genksyms/genksyms HOSTCC scripts/conmakehash UPD
> scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/sumversion.o HOSTCC
> scripts/sortextable HOSTCC scripts/dtc/treesource.o HOSTCC
> scripts/asn1_compiler HOSTCC scripts/dtc/srcpos.o HOSTCC
> scripts/mod/modpost.o HOSTCC 
> scripts/sign-file/home/dmohite/havoc/kernel/xiaomi/sm6150/scripts/sign-file.c:25:30:
> fatal error: openssl/opensslv.h: No such file or directory #include
>  ^compilation terminated.make[2]: ***
> [scripts/Makefile.host:102: scripts/sign-file] Error 1make[2]: ***
> Waiting for unfinished jobs HOSTCC scripts/mod/file2alias.o HOSTCC
> scripts/dtc/checks.o HOSTCC scripts/dtc/util.o SHIPPED
> scripts/dtc/dtc-lexer.lex.c SHIPPED scripts/dtc/dtc-parser.tab.h SHIPPED
> scripts/dtc/dtc-parser.tab.c HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC
> scripts/dtc/dtc-parser.tab.oIn file included from
> /home/dmohite/havoc/kernel/xiaomi/sm6150/scripts/dtc/dtc.h:27:0, from
> dtc-lexer.l:37:/usr/include/stdint.h:137:0: warning: "UINT8_MAX"
> redefined [enabled by default] # define UINT8_MAX (255) ^dtc-lexer.lex.c:78:0:
> note: this is the location of the previous definitionIn file included
> from /home/dmohite/havoc/kernel/xiaomi/sm6150/scripts/dtc/dtc.h:27:0,
> from dtc-lexer.l:37:/usr/include/stdint.h:138:0: warning: "UINT16_MAX"
> redefined [enabled by default] # define UINT16_MAX (65535) 
> ^dtc-lexer.lex.c:81:0:
> note: this is the location of the previous definition HOSTLD
> scripts/mod/modpost HOSTLD scripts/dtc/dtcmake[1]: ***
> [/home/dmohite/havoc/kernel/xiaomi/sm6150/Makefile:582: scripts] Error 
> 2make[1]:
> Leaving directory
> '/home/dmohite/havoc/out/target/product/violet/obj/KERNEL_OBJ'make: ***
> [Makefile:146: sub-make] Error 2make: Leaving directory
> '/home/dmohite/havoc/kernel/xiaomi/sm6150'[ 11% 12126/105250]
> //bionic/libc:libc.llndk versioner preprocess includewarning: attempted
> to generate guard with empty availability: obsoleted = 23warning:
> attempted to generate guard with empty availability: obsoleted = 21[ 11%
> 12127/105250] //bionic/libc:libc.llndk versioner preprocess include 
> [arm]warning:
> attempted to generate guard with empty availability: obsoleted = 23warning:
> attempted to generate guard with empty availability: obsoleted = 2120:32:38
> ninja failed with: exit status 1 failed to build some targets (22:30
> (mm:ss)) 
>
> --
> --
> 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/92051b85-2eb1-4bf0-bdb4-5beed4fc556a%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/92051b85-2eb1-4bf0-bdb4-5beed4fc556a%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
You received this message because yo

Re: [android-building] Including a prebuilt shared librray in Android.bp

['Dan Willemsen' via Android Building]

It sounds like your cc_library is setting sdk_version: "XX" (so it's built
against the NDK), but your cc_prebuilt_library_shared is not (so it's
claiming it was built against the platform APIs, which contains APIs that
may change from release to release). If your prebuilt was actually built
against the NDK, you should specify which version it was built against. If
not, remove the sdk_version from your cc_library.

Also, instead of using `include_dirs` in your cc_library, you can use
`export_include_dirs` in your prebuilt library to expose a set of headers
to everything that links to that library. We'd eventually like to get rid
of include_dirs (not local_include_dirs). See
https://android.googlesource.com/platform/build/soong/+/master/docs/best_practices.md#headers
for
more discussion around this.

- Dan

On Fri, Feb 7, 2020 at 11:13 AM Shalini Salomi Bodapati 
wrote:

> Hi All,
>
> I facing the below error when trying to add a prebuilt shared library in
> Android.bp file.
>
> My approach:
>
> cc_prebuilt_library_shared {
> name: "my-lib",
> srcs: ["path-to-my-lib/my-lib.so"],
> }
> cc_librray {
>
>shared_libs : ["my-lib"],
>include_dirs : ["path to .h files"]
> }
>
> *module "X" variant "": depends on non-NDK-built library "my-lib"*
>
> Any help is appreciated.
>
> 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/bf51066b-6143-451f-ba11-840af2695d7a%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/bf51066b-6143-451f-ba11-840af2695d7a%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DQ%2BV1HbLBx4G-%3DU3EiLyW0SRCwupto3SiWn%3DdM-4S1oA%40mail.gmail.com.

Re: [android-building] Re: Problem when compiling - how to fix?

['Dan Willemsen' via Android Building]

jopt-simple-4.9 should be defined in prebuilts/tools/common/m2/...

https://cs.android.com/android/platform/superproject/+/master:prebuilts/tools/common/m2/repository/net/sf/jopt-simple/jopt-simple/4.9/Android.bp;l=17?q=jopt-simple-4.9=android%2Fplatform%2Fsuperproject

- Dan

On Tue, Jan 28, 2020 at 6:57 AM Aditya Upadhyay 
wrote:

> What command you are using for build?
>
> Attache the build log file which you have got after error.
>
>
> On Monday, January 6, 2020 at 9:40:22 AM UTC+5:30, Eliane Fonseca wrote:
>>
>> I don't know if this is caused by an incomplete download or  corrupt git
>> repo. The tag I used to download is: android-10.0.0_r1.
>>
>> Here is the error:
>> [100% 135/135] 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/icu/tools/srcgen/currysrc/Android.bp:42:1: "currysrc"
>> depends on undefined module "jopt-simple-4.9"
>> 00:16:17 soong bootstrap failed with: exit status 1
>>
>> --
> --
> 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/be1a780c-4114-449e-8589-5691248a7749%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/be1a780c-4114-449e-8589-5691248a7749%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdm1nAsdiYVbzynSc%3DeNcOJ2iD4JX70NciSudwDFFCH5gQ%40mail.gmail.com.

Re: [android-building] running emulator error

['Dan Willemsen' via Android Building]

For the emulator, you'll need to use aosp_x86, or a similar emulator
product, not a physical device product like aosp_bullhead.

- Dan

On Sat, Feb 15, 2020 at 11:57 AM 张亚琦 <1987zhangy...@gmail.com> wrote:

>
> *I compiled Android N,  but there was an error running the emulator*
>
> *VMware: Ubuntu 14.04*
> *The environment*
>
> root@ubuntu:~/Documents/work_dir# lunch
>
> You're building on Linux
>
> Lunch menu... pick a combo:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_mips-eng
>  4. aosp_mips64-eng
>  5. aosp_x86-eng
>  6. aosp_x86_64-eng
>  7. full_fugu-userdebug
>  8. aosp_fugu-userdebug
>  9. car_emu_arm64-userdebug
>  10. car_emu_arm-userdebug
>  11. car_emu_x86_64-userdebug
>  12. car_emu_x86-userdebug
>  13. mini_emulator_arm64-userdebug
>  14. m_e_arm-userdebug
>  15. m_e_mips64-eng
>  16. m_e_mips-userdebug
>  17. mini_emulator_x86_64-userdebug
>  18. mini_emulator_x86-userdebug
>  19. aosp_dragon-userdebug
>  20. aosp_dragon-eng
>  21. aosp_marlin-userdebug
>  22. aosp_marlin_svelte-userdebug
>  23. aosp_sailfish-userdebug
>  24. aosp_angler-userdebug
>  25. aosp_bullhead-userdebug
>  26. aosp_bullhead_svelte-userdebug
>  27. hikey-userdebug
>
> Which would you like? [aosp_arm-eng] 25
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=8.0.0
> TARGET_PRODUCT=aosp_bullhead
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_PLATFORM_VERSION=OPR1
> TARGET_BUILD_APPS=
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=cortex-a53
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv7-a-neon
> TARGET_2ND_CPU_VARIANT=cortex-a53.a57
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trusty
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=OPR6.170623.010
> OUT_DIR=out
> AUX_OS_VARIANT_LIST=
> 
>
> *and then i run the **emulator*
>
> root@ubuntu:~/Documents/work_dir# emulator -partition-size 1024
> emulator: WARNING: userdata partition is resized from 142 M to 1024 M
>
> ERROR: resizing partition e2fsck failed with exit code 8
> emulator: WARNING: encryption is off
> qemu-system-aarch64: Trying to execute code outside RAM or ROM at
> 0x0400
> This usually means one of the following happened:
>
> (1) You told QEMU to execute a kernel for the wrong machine type, and it
> crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb
> QEMU machine)
> (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU
> executed a ROM full of no-op instructions until it fell off the end
> (3) Your guest kernel has a bug and crashed by jumping off into nowhere
>
> This is almost always one of the first two, so check your command line and
> that you are using the right type of kernel for this machine.
> If you think option (3) is likely then you can try debugging your guest
> with the -d debug options; in particular -d guest_errors will cause the log
> to include a dump of the guest register state at this point.
>
> Execution cannot continue; stopping here.
>
> QObject::~QObject: Timers cannot be stopped from another thread
> root@ubuntu:~/Documents/work_dir#
>
>
>
>
> *I can't find the solution, please help me, thank you very much*
>
> --
> --
> 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/b9341e65-64b5-4804-996e-c2153f31f755%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/b9341e65-64b5-4804-996e-c2153f31f755%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegro

Re: [android-building] lunch aosp_coral-userdebug

['Dan Willemsen' via Android Building]

For the emulator, you'll need to use aosp_x86, or a similar emulator
product, not a physical device product like coral.

- Dan

On Tue, Feb 18, 2020 at 12:27 PM Damir Usmanov  wrote:

> Hi All.
>
> I just lunch aosp_coral-userdebug and started emulator.
> but it shows black screen all time.
>
> When I click black screen, it shows "##KBD: Full queue, dropping event,
> current drop count: 1"
> I attached screenshots.
>
> Please help me how to fix.
>
> Thanks.
> Damir.
>
> --
> --
> 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/9fe72d0a-9469-4b45-aeeb-c8c1607d8fae%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/9fe72d0a-9469-4b45-aeeb-c8c1607d8fae%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmPSdX0%2BQ4uiZyRxF-TwrTxJ%2B2riTgKga0s3M96vRBb2Q%40mail.gmail.com.

Re: [android-building] dext2oatd missing on macOS Catalina

['Dan Willemsen' via Android Building]

dex2oat[d] (the host version) is not supported on Mac, so you cannot use
WITH_DEXPREOPT=true on a Mac. (Not setting it should be the default)

- Dan

On Tue, Feb 18, 2020 at 7:15 AM Eric Park  wrote:

> Hello everyone,
>
> Trying to build Android Q on macOS Catalina and I keep getting this error:
>
> FAILED: ninja: '/Volumes/aosp/q/out/soong/host/darwin-x86/bin/dex2oatd',
> needed by
> '/Volumes/aosp/q/out/soong/bullhead/dex_bootjars/system/framework/arm64/boot.art',
> missing and no known rule to make it
> 17:09:04 ninja failed with: exit status 1
>
>  failed to build some targets (05:57 (mm:ss)) 
>
>
> It seems like it is missing dext2oatd, but since it's in the out/
> directory it must be getting copied over by something. How do I include
> this dext2oatd file?
>
> --
> --
> 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/9686a12b-89ac-4a4d-a49b-b74510148bb0%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/9686a12b-89ac-4a4d-a49b-b74510148bb0%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdki%2BmnDQJpjhhc%2B16HK%3D_7Fqa38dy%3Dmu3ANm3mhiJ977Q%40mail.gmail.com.

Re: [android-building] Can I run cuttlefish Arm64 on x86 PC?

['Dan Willemsen' via Android Building]

My understanding is that cuttlefish's arm[64] variant is meant to run on an
arm64 machine, not an x86 machine.

- Dan

On Thu, Feb 13, 2020 at 7:30 AM Lawrence Lin  wrote:

> Dear all,
>
> I follow the steps on the cuttlefish intro. page, "
> https://android.googlesource.com/device/google/cuttlefish/;
> I can run the aosp_cf_x86_phone sku on PC (x86)
> And I try to build the image "aosp_cf_arm64_phone-userdebug" sku from the
> AOSP codebase
> But I can not boot up the VM by same way.
> Please give me some help, I want to run the ARM vm on x86 PC.
> many thanks
>
> The logs are:
> launch_cvd I 02-11 15:56:57 23124 23132 process_monitor.cc:136] Detected
> exit of monitored subprocess
> launch_cvd I 02-11 15:56:57 23124 23132 process_monitor.cc:144] Subprocess
> /media/cslin/data/vmi/aosp-cuttlefish/bin/crosvm (23213) has exited with
> exit code 1
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:117] Started (pid:
> 23223): /media/cslin/data/vmi/aosp-cuttlefish/bin/crosvm
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] run
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --null-audio
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --mem=2048
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --cpus=2
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --params=androidboot.boot_devices=pci:00/:00:01.0
> androidboot.console=ttyS1 androidboot.cuttlefish_config_server_port=4680
> androidboot.fstab_name=fstab androidboot.hardware.egl=swiftshader
> androidboot.hardware.gralloc=cutf_ashmem
> androidboot.hardware.hwcomposer=cutf_cvm_ashmem
> androidboot.hardware=cutf_cvm androidboot.lcd_density=160
> androidboot.logcat_serial_port=/dev/ttyS2
> androidboot.serialno=CUTTLEFISHCVD01 androidboot.setupwizard_mode=DISABLED
> androidboot.tombstone_transmit=1 androidboot.vsock_frames_port=5580
> androidboot.vsock_tombstone_port=5630 audit=1 buildvariant=userdebug
> enforcing=1 init=/init loop.max_part=7 mac80211_hwsim.radios=0
> printk.devkmsg=on root=/dev/vda security=selinux
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//system.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//userdata.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//cache.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//metadata.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//vendor.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --rwdisk=/media/cslin/data/vmi/aosp-cuttlefish//product.img
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --socket=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/crosvm_control.sock
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --android-fstab=/media/cslin/data/vmi/aosp-cuttlefish/config/gsi.fstab
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --single-touch=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/touch.sock:720:1280
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --keyboard=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/keyboard.sock
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --tap-fd=29
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --tap-fd=31
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --disable-sandbox
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120] --cid=3
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --serial=num=1,type=file,path=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/kernel-log,console=true
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --serial=num=3,type=file,path=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/logcat
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> --serial=num=2,type=file,path=/media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/console-pipe,stdin=true
> launch_cvd I 02-11 15:56:57 23124 23132 subprocess.cpp:120]
> /media/cslin/data/vmi/aosp-cuttlefish/cuttlefish_runtime/kernel
> [WARNING:src/linux.rs:988] falling back to current user id for 9p:
> Success (os error 0)
> [WARNING:src/linux.rs:996] falling back to current group id for 9p:
> Success (os error 0)
> [ERROR:src/main.rs:969] The architecture failed to build the vm: error
> loading kernel bzImage: bzImage loader: bad kernel header signature
>
> --
> --
> You received this message because you are subscribed to th

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

['Dan Willemsen' via Android Building]

The correct links this time:

https://cs.android.com/android/platform/superproject/+/master:build/make/core/base_rules.mk;l=733?q=create-suite-dependencies=android%2Fplatform%2Fsuperproject
https://cs.android.com/android/platform/superproject/+/master:build/make/core/definitions.mk;l=2899?q=create-suite-dependencies=android%2Fplatform%2Fsuperproject

- Dan

On Thu, Jan 16, 2020 at 9:28 AM Dan Willemsen  wrote:

> The test_suite_name needs to match the individual module definitions that
> set `test_suites: ["vts"]` or `LOCAL_COMPATIBILITY_SUITE := vts`.
>
> The make code controlling that is roughly:
>
>
> https://source.corp.google.com/android/build/make/core/base_rules.mk;cl=master;l=733?q=create-suite-dependencies=package:%5Eandroid$
>
> https://source.corp.google.com/android/build/make/core/definitions.mk;cl=master;l=2899?q=COMPATIBILITY.*FILES%20lang:makefile%20case:yes=package:%5Eandroid$
>
> - Dan
>
> 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
>> <https://groups.google.com/d/msgid/android-building/769ed951-666c-44f6-baff-cc2da905518b%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
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/CALQgHdmD1TfuXvdT7Gz1WBt9Y_03b17Kx9vTFhMwMj-4HrbTzQ%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

The test_suite_name needs to match the individual module definitions that
set `test_suites: ["vts"]` or `LOCAL_COMPATIBILITY_SUITE := vts`.

The make code controlling that is roughly:

https://source.corp.google.com/android/build/make/core/base_rules.mk;cl=master;l=733?q=create-suite-dependencies=package:%5Eandroid$
https://source.corp.google.com/android/build/make/core/definitions.mk;cl=master;l=2899?q=COMPATIBILITY.*FILES%20lang:makefile%20case:yes=package:%5Eandroid$

- Dan

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
> <https://groups.google.com/d/msgid/android-building/769ed951-666c-44f6-baff-cc2da905518b%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DSqiqE8b1KRNo%2BO2wbG6NM4HkaG2TQ%2BGrtVHy8Niha7g%40mail.gmail.com.

Re: [android-building] Does ccache still works with newer AOSP?

['Dan Willemsen' via Android Building]

You have to provide your own ccache binary, then it should work (but I
haven't tested it).

That being said, using ccache will actually slow down your builds, as it
needs to do extra IO maintaining the cache. It really only helps if you're
repeatedly doing clean rebuilds, in which case why aren't you using
incremental builds? (It also only affects 1/3-1/2 of the build, as the rest
of the actions are Java/etc)

- Dan

On Sun, Jan 19, 2020 at 2:41 PM Eliane Fonseca 
wrote:

> I trying to use ccache with newer AOSP (9, 10) to attempt to speed up
> compiling time,but it looks like ccache is not being used even with the
> environment variables set. It is still possible to use ccache with AOSP 9
> or 10? If not there are any alternatives and how I can use them ? Since
> my hardware is very underpowered (1 GHz CPU with auto-overclocking) I need
> to speed up the build time with the newer AOSP.
>
> --
> --
> 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/f7b5d95e-6e73-4efd-9266-360db2b2fcbe%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/f7b5d95e-6e73-4efd-9266-360db2b2fcbe%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmTj2k9%2BGbekZfMAH424YiAa-LprbnXO1cGuM-4tk5RuQ%40mail.gmail.com.

Re: [android-building] How to add android header files in 'out/soong/ndk/sysroot/usr/include' directory

['Dan Willemsen' via Android Building]

out/soong/ndk/sysroot/usr/include is an internal implementation detail of
the build system, and only contains headers from the NDK. The headers
you've listed are not part of the NDK, and require you to be built within
the Android build system with Android.bp (or .mk). Then you can use the
libhardware_headers header library to access them.

- Dan

On Mon, Jan 20, 2020 at 11:13 PM Jay Jeon  wrote:

> Hi,
>
> I was trying to use the header files in
> './out/soong/ndk/sysroot/usr/include' directory by building some libraries,
> but I didn't find some android header files.
>
> I want to add the android header files in
> './out/soong/ndk/sysroot/usr/include' directory.
>
> : fatal error: 'hardware/thermal.h' file not found
> : fatal error: 'hardware/sensors.h' file not found
> : fatal error: 'system/graphics.h' file not found
>
> Please let me know how can I add the android header files in that
> directory at build time.
>
> --
> --
> 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/21facca5-a92e-4b26-b1f8-afa9102c0bf4%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/21facca5-a92e-4b26-b1f8-afa9102c0bf4%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmX%3DpuntfEP8kjSv0cfNTy2BuEfCWyUPKCs3N5NG2tFWA%40mail.gmail.com.

Re: [android-building] Migrate to python3

['Dan Willemsen' via Android Building]

>
>  If the host does not have python2(20.04), we can use AOSP prebuilt
> python2.


No, even if the host does have python2, we'll be using our prebuilt
instead. (Unless someone is explicitly calling /usr/bin/python[2], which
would be a bug)

As far as I know, AOSP uses host python to build  and uses the prebuilt
> version to do some testing


The Soong python support (for host tools/tests and device tests) uses the
python source in external/python/..., not the prebuilt. (The prebuilt is
generated from the same sources)

Will you change soong_ui to set AOSP build with prebuilt python2?
>

That already happened with Android 10 (Q).

- Dan

On Tue, Jan 21, 2020 at 8:23 AM XING WANG 
wrote:

> Thanks Dan,
>
> Please let me clarify further.
>
> So AOSP will not modify all python2 in the build script to be python3
> compatible(like dict.iteritems), and we should build AOSP with python2,  If
> the host does not have python2(20.04), we can use AOSP prebuilt python2.
>
> As far as I know, AOSP uses host python to build  and uses the prebuilt
> version to do some testing
> Will you change soong_ui to set AOSP build with prebuilt python2?
>
>
> On Tuesday, January 21, 2020 at 3:24:12 PM UTC+8, Dan Willemsen wrote:
>>
>> There are no current plans to switch everything over to python3. We
>> provide our own prebuilt of python2 (in
>> prebuilts/build-tools/path/linux-x86/python2 ->
>> prebuilts/build-tools/linux-x86/bin/py2-cmd), so that script you linked
>> should continue working even if you remove python2 from your host.
>>
>> (I'm still working on getting a fully functional python3 prebuilt, so
>> we'll still use the host for that, I should have that done for the next
>> release).
>>
>> Let me know if you see failures on 20.04 without python2, it's possible
>> there are some scripts hardcoding /usr/bin/python[2] still.
>>
>> - Dan
>>
>> On Sun, Jan 19, 2020 at 8:24 AM XING WANG  wrote:
>>
>>> We found AOSP cant not build successfully without python2
>>>
>>> There is a example for python2 only scripts
>>>
>>> https://cs.android.com/android/platform/superproject/+/master:build/make/tools/post_process_props.py?q=iteritems=android%2Fplatform%2Fsuperproject:build%2F
>>>
>>> Is there a plan to switch to a pure python3 environment ？
>>>
>>> We are evaluating whether we can switch the build server to ubuntu 20.04
>>> which without python2 support  in the near future.
>>>
>>>
>>> --
>>> --
>>> 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/afa2ada5-0bea-41dd-a7ab-eb3a7c8b7e7d%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/afa2ada5-0bea-41dd-a7ab-eb3a7c8b7e7d%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> --
> 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/0cb5a861-f45e-4cea-8cc4-d59c792964f7%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/0cb5a861-f45e-4cea-8cc4-d59c792964f7%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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.c

Re: [android-building] How to build kernel incrementally

['Dan Willemsen' via Android Building]

I'm not overly familiar with the kernel build scripts, but it looks like
you can set SKIP_MRPROPER=1 to skip the initial `make mrproper` (clean)
step.

- Dan

On Fri, Jan 3, 2020 at 9:14 PM Vova Ivanov  wrote:

> Having followed the instructions on the Android Open Source Project
> <https://source.android.com/setup/build/building-kernels#top_of_page>
> website, I was able to successfully modify and build a variety of kernels
> for testing. When using their build command: *./build/build.sh*, I
> noticed that it would always build everything from scratch. I was
> wondering, is it possible to incrementally build it so that files that
> haven't been changed aren't recompiled? Thanks!
>
> Sincerely,
> Vova
>
> --
> --
> 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/4b1cde76-6999-47cf-92d6-2a64d126fde9%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/4b1cde76-6999-47cf-92d6-2a64d126fde9%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D2Yzbkb%3DA665hUAg6999BKU6R9SEKtiq7iRekYh-%3DFPw%40mail.gmail.com.

Re: [android-building] when call COMMON_LUNCH_CHOICES in build?

['Dan Willemsen' via Android Building]

I'm not entirely sure what you're asking, but I wouldn't expect most people
to be using COMMON_LUNCH_CHOICES very often. That is only used for the
lunch menu, which only shows up when you don't pass an argument to lunch,
or pass a number (don't do that!). The expected flow would be to do
something like:

 $ source build/envsetup.sh
 $ lunch aosp_crosshatch-eng
 $ m

None of those steps will use COMMON_LUNCH_CHOICES.

- Dan

On Thu, Mar 12, 2020 at 8:58 AM Bo YU  wrote:

> Hi,
> please correct me if i understood wrong.
> In AOSP/build call chains,we know, `source
> aosp-src/build/envsetup.sh`, it will execute three shell functions firstly:
>
> validate_current_shell
> source_vendorsetup
> addcompletions
> In my view, it does not affect the config list.especially
> source_vendorsetup:
> But, if it does not source global var,eg,COMMON_LUNCH_CHOICES,
> lunch->print_lunch_menu->get_build_var
> (COMMON_LUNCH_CHOICES)->soong/soong_ui.bash.
> Although COMMON_LUNCH_CHOICES is defined in
> make/target/product/AndroidProducts.mk,
> Can we call it directly without preparing read COMMON_LUNCH_CHOICES?
> Thank you very much
>
>
>
> --
> --
> 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/dc791e87-4a9c-4501-bc1c-429843dbbb57%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/dc791e87-4a9c-4501-bc1c-429843dbbb57%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnGwD8CeDq8jrz4y7fPDMYGhEE0gjB4Bu0p9zUvR5ngyw%40mail.gmail.com.

Re: [android-building] Android 11` Preview building failed initially

['Dan Willemsen' via Android Building]

Sorry, apparently that link didn't 
work. https://groups.google.com/d/msg/android-building/t-70r0IdkZY/sY_NhNd6AgAJ 
should work better.

- Dan

On Tuesday, April 7, 2020 at 9:45:15 AM UTC-7 Dan Willemsen wrote:

> Yep, that's not intended to be a buildable tag. See my previous messages: 
> https://groups.google.com/g/android-building/c/t-70r0IdkZY/m/sY_NhNd6AgAJ
>
> - Dan
>
> On Tue, Apr 7, 2020 at 9:41 AM Varun Kumar  wrote:
>
>> Hi Dan Willemsen,
>>
>> I have used below branch/tag 
>>
>> *repo init -u https://android.googlesource.com/platform/manifest 
>> <https://android.googlesource.com/platform/manifest> -b android-r-preview-2*
>>
>> I googled few things related with this error. It's because of a 
>> duplicate entry in somewhere  which both are trying to copy some file to 
>> the same destination.
>>
>>
>> On Friday, April 3, 2020 at 9:30:34 AM UTC+5:30, Dan Willemsen wrote:
>>>
>>> What branch/tag did you use to initialize this source tree? (`repo init 
>>> ...`)
>>>
>>> - Dan
>>>
>>> On Thu, Apr 2, 2020 at 8:57 PM Varun Kumar  wrote:
>>>
>>>> 
>>>> PLATFORM_VERSION_CODENAME=R
>>>> PLATFORM_VERSION=R
>>>> TARGET_PRODUCT=aosp_arm64
>>>> TARGET_BUILD_VARIANT=eng
>>>> TARGET_BUILD_TYPE=release
>>>> TARGET_ARCH=arm64
>>>> TARGET_ARCH_VARIANT=armv8-a
>>>> TARGET_CPU_VARIANT=generic
>>>> TARGET_2ND_ARCH=arm
>>>> TARGET_2ND_ARCH_VARIANT=armv8-a
>>>> TARGET_2ND_CPU_VARIANT=generic
>>>> HOST_ARCH=x86_64
>>>> HOST_2ND_ARCH=x86
>>>> HOST_OS=linux
>>>> HOST_OS_EXTRA=Linux-4.15.0-91-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=AOSP.MASTER
>>>> OUT_DIR=out
>>>> 
>>>> [100% 430/430] writing build rules ...
>>>> FAILED: 
>>>> build/make/core/base_rules.mk:491: error: overriding commands for 
>>>> target `out/target/product/generic_arm64/system/bin/chattr', previously 
>>>> defined at build/make/core/base_rules.mk:467
>>>> 07:04:16 ckati failed with: exit status 1
>>>>
>>>>  failed to build some targets (03:53 (mm:ss)) 
>>>>
>>>> -- 
>>>> -- 
>>>> 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/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/android-building/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> -- 
>> 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-buildi...@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-buildi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/android-building/16d2c2e3-6dba-410d-a730-3b239ad5c436%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/android-building/16d2c2e3-6dba-410d-a730-3b239ad5c436%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
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/89249ef3-6117-448d-a3c2-11a945d35766%40googlegroups.com.

Re: [android-building] Classes.jar and classes-header.jar with same module name

['Dan Willemsen' via Android Building]

That generally should be an error, as we normally require modules to be
unique based on the combination of LOCAL_MODULE / LOCAL_IS_HOST_MODULE /
LOCAL_MODULE_CLASS (this is in build/make/core/base_rules.mk
<https://cs.android.com/android/platform/superproject/+/master:build/make/core/base_rules.mk;drc=fca369e4e3694b0f549613362f0568c88f67;l=322>
)


If that isn't triggering, you may be making two rules to create the same
/system/frameworks/X.jar, and you should be getting a warning like this:

build/make/core/mk:LLL: warning: overriding commands for target
`out/target/product/mydevice/system/frameworks/X.jar'
build/make/core/...mk:LLL: warning: ignoring old commands for target
`out/target/product/mydevice/system/frameworks/X.jar'

That should be an error by default unless you've got BUILD_BROKEN_DUP_RULES
set (at least as of Android-Q iirc). That means you're getting one of the
two, or sometimes a mix, but we don't really even guarantee which one
you'll get (it's fairly stable, but can change based on ordering/etc).


What did you intend for the snippet to do? How would we install both
classes.jar and classes-header.jar onto the device? Same filenames?
Different filenames? Why do they share the same module name?

- Dan

On Tue, Apr 14, 2020 at 8:10 AM Pranitha Reddy <
pranitha.alugube...@gmail.com> wrote:

> Hello
> Say there is module 'X' writtern twice in Android.mk
>
> include $(CLEAR_VARS)
> LOCAL_MODULE   := X
> LOCAL_MODULE_CLASS := JAVA_LIBRARIES
> LOCAL_SRC_FILES:= same_path/classes-header.jar
>
>
>
> include $(CLEAR_VARS)
> LOCAL_MODULE   := X
> LOCAL_MODULE_CLASS := JAVA_LIBRARIES
> LOCAL_SRC_FILES:= same_path/classes.jar
>
> Is there any way to install X such that both classes.jar and
> classes-header.jar will be in out folder?
> At present with above Android.mk, the rule that is writtern first is being
> compiled and the rest is being ingnored and so Im seeing only
> classes-header.jar in out folder
>
> 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/CAH4VoYmaY%3DokDbzrBCa%2BGt9ysJNLasKMeK2NKVTH2Lq95QjE3w%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAH4VoYmaY%3DokDbzrBCa%2BGt9ysJNLasKMeK2NKVTH2Lq95QjE3w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnpF2%2BgT_C9wymuA3VtCDEjP3g4uy4SAXyZ04%3DVEEEOcw%40mail.gmail.com.

Re: [android-building] Android 11` Preview building failed initially

['Dan Willemsen' via Android Building]

Yep, that's not intended to be a buildable tag. See my previous messages:
https://groups.google.com/g/android-building/c/t-70r0IdkZY/m/sY_NhNd6AgAJ

- Dan

On Tue, Apr 7, 2020 at 9:41 AM Varun Kumar  wrote:

> Hi Dan Willemsen,
>
> I have used below branch/tag
>
> *repo init -u https://android.googlesource.com/platform/manifest
> <https://android.googlesource.com/platform/manifest> -b android-r-preview-2*
>
> I googled few things related with this error. It's because of a duplicate
> entry in somewhere  which both are trying to copy some file to the same
> destination.
>
>
> On Friday, April 3, 2020 at 9:30:34 AM UTC+5:30, Dan Willemsen wrote:
>>
>> What branch/tag did you use to initialize this source tree? (`repo init
>> ...`)
>>
>> - Dan
>>
>> On Thu, Apr 2, 2020 at 8:57 PM Varun Kumar  wrote:
>>
>>> 
>>> PLATFORM_VERSION_CODENAME=R
>>> PLATFORM_VERSION=R
>>> TARGET_PRODUCT=aosp_arm64
>>> TARGET_BUILD_VARIANT=eng
>>> TARGET_BUILD_TYPE=release
>>> TARGET_ARCH=arm64
>>> TARGET_ARCH_VARIANT=armv8-a
>>> TARGET_CPU_VARIANT=generic
>>> TARGET_2ND_ARCH=arm
>>> TARGET_2ND_ARCH_VARIANT=armv8-a
>>> TARGET_2ND_CPU_VARIANT=generic
>>> HOST_ARCH=x86_64
>>> HOST_2ND_ARCH=x86
>>> HOST_OS=linux
>>> HOST_OS_EXTRA=Linux-4.15.0-91-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=AOSP.MASTER
>>> OUT_DIR=out
>>> 
>>> [100% 430/430] writing build rules ...
>>> FAILED:
>>> build/make/core/base_rules.mk:491: error: overriding commands for
>>> target `out/target/product/generic_arm64/system/bin/chattr', previously
>>> defined at build/make/core/base_rules.mk:467
>>> 07:04:16 ckati failed with: exit status 1
>>>
>>>  failed to build some targets (03:53 (mm:ss)) 
>>>
>>> --
>>> --
>>> 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/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> --
> 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/16d2c2e3-6dba-410d-a730-3b239ad5c436%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/16d2c2e3-6dba-410d-a730-3b239ad5c436%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkcOOkc6ciNDGj6kZ0mX%3DTNMqYB9Mk4CRb_nPJyJ9U55w%40mail.gmail.com.

Re: [android-building] Kotlin illegal reflection when building AOSP

['Dan Willemsen' via Android Building]

The problem isn't the kolin warning, but java.lang.OutOfMemoryError -- your
machine ran out of ram. How much ram is available/free before the build
starts?

Are you using AOSP master, or some other branch/tag? We've made some
attempts to help with this on master (running fewer "highmem" actions
concurrently), but that may still need tweaking.

- Dan

On Sun, Apr 5, 2020 at 8:27 AM Steve  wrote:

> Trying to build a standard AOSP on Ubuntu 14.04, target aosp_arm-eng.
> The build works fine until the metalava and the use of kotlin, when it
> fails with:
>
> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreApplicationEnvironment
>> (file:/aosp/soong/host/linux-x86/framework/metalava.jar) to field
>> java.lang.reflect.Field.modifiers
>> WARNING: Please consider reporting this to the maintainers of
>> org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreApplicationEnvironment
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>> at
>> java.base/java.util.LinkedHashMap$LinkedKeySet.iterator(LinkedHashMap.java:543)
>> at java.base/java.util.HashSet.iterator(HashSet.java:173)
>> at
>> kotlin.collections.CollectionsKt___CollectionsKt.toList(_Collections.kt:1220)
>> at kotlin.collections.ArraysKt___ArraysKt.distinct(_Arrays.kt:9836)
>> at
>> com.android.tools.metalava.model.psi.PsiModifierItem$Companion.create(PsiModifierItem.kt:188)
>> at
>> com.android.tools.metalava.model.psi.PsiModifierItem$Companion.create(PsiModifierItem.kt:58)
>> at
>> com.android.tools.metalava.model.psi.PsiItem$Companion.modifiers(PsiItem.kt:264)
>> at
>> com.android.tools.metalava.model.psi.PsiMethodItem$Companion.create(PsiMethodItem.kt:355)
>> at
>> com.android.tools.metalava.model.psi.PsiClassItem$Companion.create(PsiClassItem.kt:466)
>> at
>> com.android.tools.metalava.model.psi.PsiBasedCodebase.createClass(PsiBasedCodebase.kt:441)
>> at
>> com.android.tools.metalava.model.psi.PsiBasedCodebase.findOrCreateClass(PsiBasedCodebase.kt:559)
>> at
>> com.android.tools.metalava.model.psi.PsiClassItem$Companion$create$result$1.invoke(PsiClassItem.kt:534)
>> at
>> com.android.tools.metalava.model.psi.PsiClassItem$Companion$create$result$1.invoke(PsiClassItem.kt:391)
>> at
>> kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:172)
>> at
>> kotlin.sequences.SequencesKt___SequencesKt.toCollection(_Sequences.kt:716)
>> at
>> kotlin.sequences.SequencesKt___SequencesKt.toMutableList(_Sequences.kt:746)
>> at
>> com.android.tools.metalava.model.psi.PsiClassItem$Companion.create(PsiClassItem.kt:538)
>> at
>> com.android.tools.metalava.model.psi.PsiBasedCodebase.createClass(PsiBasedCodebase.kt:441)
>> at
>> com.android.tools.metalava.model.psi.PsiBasedCodebase.initialize(PsiBasedCodebase.kt:180)
>> at com.android.tools.metalava.Driver.parseSources(Driver.kt:876)
>> at
>> com.android.tools.metalava.Driver.parseSources$default(Driver.kt:847)
>> at com.android.tools.metalava.Driver.loadFromSources(Driver.kt:773)
>> at com.android.tools.metalava.Driver.processFlags(Driver.kt:182)
>> at com.android.tools.metalava.Driver.run(Driver.kt:115)
>> at com.android.tools.metalava.Driver.run$default(Driver.kt:98)
>> at com.android.tools.metalava.Driver.main(Driver.kt:86)
>> 12:35:03 ninja failed with: exit status 1
>>
>>>
>>>
> Following the AOSP environment instructions and build instructions, and
> have re-installed everything several times.  Same problem with the latest
> version of Ubuntu and the LTS 14.04 version.   Also with the aosp_arm64-eng
> target as well.
>
> Any suggestions?
>
>   Steve
>
> --
> --
> 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-build

Re: [android-building] Re: Kotlin illegal reflection when building AOSP

['Dan Willemsen' via Android Building]

Yeah, our minimum requirement
<https://source.android.com/setup/build/requirements> is 16GB (ignore the
comment about virtual machines there -- the point is that we expect 16GB
available for the OS+Build). Even on 16GB we've been seeing some number of
issues (hence the workarounds I mentioned earlier).

You can try setting NINJA_HIGHMEM_NUM_JOBS=1 in your environment, you may
also need to start lowering your `m -j#` value -- this defaults to a number
related to your cpu cores, but that always doesn't work well on machines
with low ram. (Anything we'd be doing to help the low ram cases would be
adjusting these defaults based on what we detect we're running on)

- Dan

On Mon, Apr 6, 2020 at 1:11 PM Steve  wrote:

> The machine has only 8Gb and 5580Mb are available when the build starts
> for 'm api-stubs-docs'.  Running a single job does not help.
> This happens on the master branch.
>
> It is not a virtual machine, the available swap is 7300Mb which is the
> default for Ubuntu installation.
>
> Too small?
>
>  -Steve
>
>
>
> On Sunday, April 5, 2020 at 5:27:36 PM UTC+2, Steve wrote:
>>
>> Trying to build a standard AOSP on Ubuntu 14.04, target aosp_arm-eng.
>> The build works fine until the metalava and the use of kotlin, when it
>> fails with:
>>
>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreApplicationEnvironment
>>> (file:/aosp/soong/host/linux-x86/framework/metalava.jar) to field
>>> java.lang.reflect.Field.modifiers
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreApplicationEnvironment
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release
>>> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>>> at
>>> java.base/java.util.LinkedHashMap$LinkedKeySet.iterator(LinkedHashMap.java:543)
>>> at java.base/java.util.HashSet.iterator(HashSet.java:173)
>>> at
>>> kotlin.collections.CollectionsKt___CollectionsKt.toList(_Collections.kt:1220)
>>> at kotlin.collections.ArraysKt___ArraysKt.distinct(_Arrays.kt:9836)
>>> at
>>> com.android.tools.metalava.model.psi.PsiModifierItem$Companion.create(PsiModifierItem.kt:188)
>>> at
>>> com.android.tools.metalava.model.psi.PsiModifierItem$Companion.create(PsiModifierItem.kt:58)
>>> at
>>> com.android.tools.metalava.model.psi.PsiItem$Companion.modifiers(PsiItem.kt:264)
>>> at
>>> com.android.tools.metalava.model.psi.PsiMethodItem$Companion.create(PsiMethodItem.kt:355)
>>> at
>>> com.android.tools.metalava.model.psi.PsiClassItem$Companion.create(PsiClassItem.kt:466)
>>> at
>>> com.android.tools.metalava.model.psi.PsiBasedCodebase.createClass(PsiBasedCodebase.kt:441)
>>> at
>>> com.android.tools.metalava.model.psi.PsiBasedCodebase.findOrCreateClass(PsiBasedCodebase.kt:559)
>>> at
>>> com.android.tools.metalava.model.psi.PsiClassItem$Companion$create$result$1.invoke(PsiClassItem.kt:534)
>>> at
>>> com.android.tools.metalava.model.psi.PsiClassItem$Companion$create$result$1.invoke(PsiClassItem.kt:391)
>>> at
>>> kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:172)
>>> at
>>> kotlin.sequences.SequencesKt___SequencesKt.toCollection(_Sequences.kt:716)
>>> at
>>> kotlin.sequences.SequencesKt___SequencesKt.toMutableList(_Sequences.kt:746)
>>> at
>>> com.android.tools.metalava.model.psi.PsiClassItem$Companion.create(PsiClassItem.kt:538)
>>> at
>>> com.android.tools.metalava.model.psi.PsiBasedCodebase.createClass(PsiBasedCodebase.kt:441)
>>> at
>>> com.android.tools.metalava.model.psi.PsiBasedCodebase.initialize(PsiBasedCodebase.kt:180)
>>> at com.android.tools.metalava.Driver.parseSources(Driver.kt:876)
>>> at
>>> com.android.tools.metalava.Driver.parseSources$default(Driver.kt:847)
>>> at com.android.tools.metalava.Driver.loadFromSources(Driver.kt:773)
>>> at com.android.tools.metalava.Driver.processFlags(Driver.kt:182)
>>> at com.android.tools.metalava.Driver.run(Driver.kt:115)
>>> at com.android.tools.metalava.Driver.run$default(Driver.kt:98)
>>> at com.android.tools.metalava.Driver.main(Driver.kt:86)
>>> 12:35:03 ninja failed with: exit status 1
&g

Re: [android-building] [Android 10] AOSP LibFuzzer example (soong) build problems.

['Dan Willemsen' via Android Building]

That page expects that you're using AOSP master, not 10.0.0_r30, which did
not yet have support for cc_fuzz (it had some support in Make instead, but
I know the fuzzing tooling as been changing over time, so I don't know if
there are other things on that page that may work differently as well.

The [2] module reference you're using is also coming from master, which is
why cc_fuzz is showing up as valid. You can get the equivalent docs locally
that are specific to your checkout by running `m soong_docs` and browsing
to out/soong/docs/soong_build.html (which shouldn't include cc_fuzz).

- Dan

On Thu, Mar 26, 2020 at 4:47 PM jrw  wrote:

> Hello,
>
> (i also postet this in the libfuzzer google group but maybe you guys might
> be able to help)
>
> i'm trying to implement a fuzzer described in [1].
> When i follow the directions and try to compile the fuzzer,
> i get the Error that soong does not know the module reference "cc_fuzz"
> which is listed in [2] as valid module.
> i tried to add the missing file "fuzz.go" [3] file to the folder
> "android/platform/build/soong/cc/"
> and added fuzz.go to the soong's folders "Android.bp" but did also result
> in errors.
> Did i miss a crucial step or is there a reason this file is gone?
> Is it recommended using the old build system or am i copying a deprecated
> file?
>
> i'm using branch "android-10.0.0_r30" (Pixel 2XL)
>
> [1] https://source.android.com/devices/tech/debug/libfuzzer
> [2]
> https://ci.android.com/builds/submitted/6334833/linux/latest/view/soong_build.html
> [3]
> https://android.googlesource.com/platform/build/soong/+/master/cc/fuzz.go
>
> Thanks for any help!
>
> Hannes
>
>
> --
> --
> 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/cd25a98c-b5e4-4e0d-a68a-d33b394085e9%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/cd25a98c-b5e4-4e0d-a68a-d33b394085e9%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkTJ4gRs2k7b-99vaiWGLSsUJYgoAZRC90MF1DNVPuvjw%40mail.gmail.com.

Re: [android-building] Android 11` Preview building failed initially

['Dan Willemsen' via Android Building]

What branch/tag did you use to initialize this source tree? (`repo init
...`)

- Dan

On Thu, Apr 2, 2020 at 8:57 PM Varun Kumar  wrote:

> 
> PLATFORM_VERSION_CODENAME=R
> PLATFORM_VERSION=R
> TARGET_PRODUCT=aosp_arm64
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.15.0-91-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=AOSP.MASTER
> OUT_DIR=out
> 
> [100% 430/430] writing build rules ...
> FAILED:
> build/make/core/base_rules.mk:491: error: overriding commands for target
> `out/target/product/generic_arm64/system/bin/chattr', previously defined at
> build/make/core/base_rules.mk:467
> 07:04:16 ckati failed with: exit status 1
>
>  failed to build some targets (03:53 (mm:ss)) 
>
> --
> --
> 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/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/c97e5216-cfd2-47c6-a7cb-7a67929f62a9%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmKQDzdzMkjBJmTKRqqZ_Rb61fW%2Bf8Tda%2BdGqiahkw05Q%40mail.gmail.com.

Re: [android-building] verbose: *kati*: slow included makefiles (1037.829698): art/Android.mk

['Dan Willemsen' via Android Building]

So that time was mostly spent initializing the find emulator:

verbose: *kati*: init find emulator time: 1311.781312

What that's doing is walking through your source tree and building up a
data structure to more efficiently (normally!) run `find` commands. This
can become very slow if you've added a symlink into your source tree
pointing to elsewhere on your filesystem (or a network filesystem). We've
also had reports that this can get very slow when you have a lot of output
trees under your source tree (being discussed in
https://github.com/google/kati/issues/184), but 20 minutes seems excessive
for that -- it claims that there are ~3M nodes in the cache:

verbose: *kati*: 3071468 find nodes

One of my AOSP trees (after removing out/) is closer to 1M nodes (~2s), and
after a hikey960 build it has ~1.5M nodes (3.4s).

- Dan

On Sat, Mar 28, 2020 at 8:36 AM Yongqin Liu  wrote:

> Hi, All
>
> Anyone knows what's the problem with the step of "including
> out/soong/Android-hikey960.mk ..."
> and how to work around this problem?
>
> it took about 20 minutes to include during the build, which is almost half
> of the entire build time.
>
> The build was an incremental build after did repo sync.
>
> here is some information from the out/verbose.log.gz
>
> out/soong/make_vars-hikey960.mk was modified, regenerating...
> verbose: *kati*: regen check time: 0.079827
> verbose: *kati*: Stack size: 8376320 bytes
> [287/287] initializing build system ...
> verbose: *kati*: slow included makefiles (4.618866): build/make/core/
> base_rules.mk
> verbose: *kati*: slow included makefiles (4.618982): build/make/core/
> soong_cc_prebuilt.mk
> verbose: *kati*: slow included makefiles (4.604702): build/make/core/
> base_rules.mk
> verbose: *kati*: slow included makefiles (4.605250): build/make/core/
> soong_cc_prebuilt.mk
> verbose: *kati*: slow included makefiles (43.432355):
> out/soong/Android-hikey960.mk
> [288/491] including out/soong/Android-hikey960.mk ...
> verbose: *kati*: 3071468 find nodes
> verbose: *kati*: init find emulator time: 1311.781312
> verbose: *kati*: slow included makefiles (1311.898633): art/build/
> Android.cpplint.mk
> verbose: *kati*: slow included makefiles (1312.676836): art/Android.mk
> [289/491] including art/Android.mk ...
>
>
> For details, please check the attached build log.
>
>
> Thanks in advance!
>
>
> Best Regards,
> Yongqin Liu
>
> --
> --
> 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/eebd86b2-83c0-460e-a26d-6cd5af31fb20%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/eebd86b2-83c0-460e-a26d-6cd5af31fb20%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmUPw9Gg-fTmv8q4kwy0-5Mk7nMx3rW2jOvJ0rP%2BURvxA%40mail.gmail.com.

Re: [android-building] Re: Dex2oat failed to compile a boot image

['Dan Willemsen' via Android Building]

As posted with the announcement:

This preview is not a full platform update and only for reference.


I would not expect this to build or necessarily get any further (eg
boot/etc). Only some components have been updated, and that's done on a
git-project boundary, so the entire build graph gets skewed significantly
between old and new projects.

- Dan

On Mon, Mar 30, 2020 at 10:10 PM Guoyin Chen  wrote:

> There are quite a lot of build error with android-preview-2 build. I think
> google have several wrong tag on different gits.
>
> On Tuesday, March 31, 2020 at 8:41:18 AM UTC+8, Michael Goffioul wrote:
>>
>> I found out I was missing this change:
>> https://android.googlesource.com/platform/libcore/+/271b4054b825efca3176c4ac11565e33cff5d09a
>> I cherry-picked it, but now I'm getting a different error:
>>
>> dex2oatd F 03-30 19:11:33  6962  6962 unstarted_runtime.cc:2085] Calling
>> native method void android.system.OsConstants.initConstants() in an
>> unstarted non-transactional runtime
>>
>>
>> On Mon, Mar 30, 2020 at 6:59 PM Michael Goffioul 
>> wrote:
>>
>>> On Mon, Mar 30, 2020 at 6:52 PM Michael Goffioul 
>>> wrote:
>>>
>>>> I'm still experimenting with android-r-preview-2, and very close to the
>>>> end of the build process, I'm getting the following error:
>>>>
>>>> FAILED:
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.vdex
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.vdex
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.vdex
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.vdex
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.vdex
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.art
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.invocation
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.oat
>>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.vdex
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot.oat
>>>> dex2oatd F 03-30 18:38:12  5762  5762 class_linker.cc:8451] Check
>>>> failed: previous_size == size (previous_size=108, size=104)
>>>> Ljava/lang/DexCache;
>>>> Runtime aborting...
>>>>
>>>> Any hint would be appreciated. I've never had that error in previous
>>>> Android versions, I'm not sure what to look for.
>>>>
>>>> Note that the above error is accompanied with a message to add
>>>> "--runtime-arg -verbose:verifier" to the
>>>>
>>>
>>> My apologies, I hit send too early. I just meant to say the additional
>>> flag didn't provide more information.
>>>
>>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this g

Re: [android-building] Android Build Teststub -- Linker failed "undefined symbol" Android.bp // maybe missing an include path?

['Dan Willemsen' via Android Building]

The `libsonic` in Android only includes `sonic.c`:
https://cs.android.com/android/platform/superproject/+/master:external/sonic/Android.bp

openInputWaveFile and readFromWaveFile are in `wave.c`

- Dan

On Tue, Mar 31, 2020 at 2:56 PM jrw  wrote:

> Hello,
>
> i'm facing an issue with the linker, most likely because of lack of
> knowledge :/
>
> i think i lack an include path or something like that, but i could not
> find something in the documentation or got confused by the Android.bp files.
>
> i try to simple example fuzzer:
>
> #include 
> #include 
> #include 
> #include "sonic.h"
> #include "wave.h"
>
> #define BUFFER_SIZE 2048
>
> extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
>
> short inBuffer[BUFFER_SIZE];
> int foo = 10;
> int bar = 1;
>
> waveFile batz = openInputWaveFile((char*)data, ,);
>
> readFromWaveFile(batz,inBuffer,size);
>
> return 0;
> }
>
>
> for that, i setup an Android.bp file in the subfolder "fuzz" i created.
>
> cc_fuzz {
> name: "sonic_fuzz",
> host_supported: false,
> srcs: [
> "sonic_fuzz.cc",
> ],
> shared_libs: [
> "libsonic",
> ],
> cflags: [
> "-g",
> ],
> cpp_std: "c++98",
> }
>
> and after i tried to build it, i get:
>
> ld.lld: error: undefined symbol: openInputWaveFile(char*, int*, int*)
> >>> referenced by sonic_fuzz.cc:16 (external/sonic/fuzz/sonic_fuzz.cc:16)
> >>>   out/soong/.intermediates/external/sonic/fuzz/sonic_fuzz/
> android_arm64_armv8-a_cortex-a73_hwasan_fuzzer/obj/external/sonic/fuzz/
> sonic_fuzz.o:(LLVMFuzzerTestOneInput)
>
> ld.lld: error: undefined symbol: readFromWaveFile(waveFileStruct*, short*,
> int)
> >>> referenced by sonic_fuzz.cc:18 (external/sonic/fuzz/sonic_fuzz.cc:18)
> >>>   out/soong/.intermediates/external/sonic/fuzz/sonic_fuzz/
> android_arm64_armv8-a_cortex-a73_hwasan_fuzzer/obj/external/sonic/fuzz/
> sonic_fuzz.o:(LLVMFuzzerTestOneInput)
> clang-10: error: linker command failed with exit code 1 (use -v to see
> invocation)
> 23:28:40 ninja failed with: exit status 1
>
>  failed to build some targets (13:07 (mm:ss)) 
>
> do i need to include some path for the sonic library in the Android.bp
> file or something?
>
> Thanks for your help
> Hannes
>
> --
> --
> 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/68c9f746-afc2-4870-b724-1b18c7cda9cf%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/68c9f746-afc2-4870-b724-1b18c7cda9cf%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmJDYp_U5De676SeAUBN_3tZJSxYYCXXnfEFMjYFdQ1FQ%40mail.gmail.com.

Re: [android-building] verbose: *kati*: slow included makefiles (1037.829698): art/Android.mk

['Dan Willemsen' via Android Building]

Interesting, 20 minutes still seems super excessive for that 

You'll probably save some amount of time sharing a single out directory
between devices, but not necessarily if you switch between them frequently,
as some of the device-specific files will clobber each other (this was
Soong trying to be smarter about sharing device-side code, until we came to
the point that we had too many configurations options to make that
reasonable ). And soong itself will re-run every time you switch devices
(kati may not, since we cache multiples of all of its outputs)

The one thing that would help you (at least until that github issue is
resolved) is to move the output directory outside of your source directory:
OUT_DIR=../out, etc. Then the find emulator wouldn't discover it.

Using a single output directory vs multiple output directories shouldn't
change the findemulator slowdown you're seeing as long as they're still in
the source directory. But the one thing a single output directory can slow
down is the initial ninja startup speed -- usually we expect to see that at
<=1s (depending on the machine), but that can grow if it needs to load
particularly large .ninja_log and .ninja_deps files, which will be shared
across all devices in a single output tree. It looks like yours is taking
~4s based on the trace. So your minimum incremental build times are
probably ~2x as long as they could be.

- Dan

On Mon, Mar 30, 2020 at 7:58 AM Yongqin Liu  wrote:

> Hi, Dan
>
> Thanks for the explanation!
>
> 在 2020年3月29日星期日 UTC+8上午3:15:52，Dan Willemsen写道：
>>
>> So that time was mostly spent initializing the find emulator:
>>
>> verbose: *kati*: init find emulator time: 1311.781312
>>
>> What that's doing is walking through your source tree and building up a
>> data structure to more efficiently (normally!) run `find` commands. This
>> can become very slow if you've added a symlink into your source tree
>> pointing to elsewhere on your filesystem (or a network filesystem). We've
>> also had reports that this can get very slow when you have a lot of output
>> trees under your source tree (being discussed in
>> https://github.com/google/kati/issues/184), but 20 minutes seems
>> excessive for that -- it claims that there are ~3M nodes in the cache:
>>
>
> Having a lot of output trees is my case.
> I build for following products under the same AOSP tree.
> beagle_x15/
> db845c/
> generic/
> generic_arm64/
> hikey/
> hikey960/
> vsoc_arm64
>
> I thought that would help to save time on the host tools/java files
> building...
>
>  verbose: *kati*: 3071468 find nodes
>
>>
>> One of my AOSP trees (after removing out/) is closer to 1M nodes (~2s),
>> and after a hikey960 build it has ~1.5M nodes (3.4s).
>>
> I checked log for another build which was done after out directory
> removed, the time is OK,
>
> Then what's your suggestion here:
> 1. use separate aosp tree for less product, like 2 or 3, my has 7 and cts,
> vts in the host out directory
> 2. I have not checked the details, and not verified it yet, do you think
> specifying the OUT out of the AOSP tree helps? still build multiply
> projects in the same out put directory.
> 3. I do not have data yet, just want to ask you here first, do you think
> build multiple products with the same output directory helps to save some
> time?
>  maybe my thought that it saves time on building the host binaries and
> java objects was wrong:(
>
>
> Thanks,
> Yongqin Liu
>
>
>
>
>> On Sat, Mar 28, 2020 at 8:36 AM Yongqin Liu  wrote:
>>
>>> Hi, All
>>>
>>> Anyone knows what's the problem with the step of "including
>>> out/soong/Android-hikey960.mk ..."
>>> and how to work around this problem?
>>>
>>> it took about 20 minutes to include during the build, which is almost
>>> half of the entire build time.
>>>
>>> The build was an incremental build after did repo sync.
>>>
>>> here is some information from the out/verbose.log.gz
>>>
>>> out/soong/make_vars-hikey960.mk was modified, regenerating...
>>> verbose: *kati*: regen check time: 0.079827
>>> verbose: *kati*: Stack size: 8376320 bytes
>>> [287/287] initializing build system ...
>>> verbose: *kati*: slow included makefiles (4.618866): build/make/core/
>>> base_rules.mk
>>> verbose: *kati*: slow included makefiles (4.618982): build/make/core/
>>> soong_cc_prebuilt.mk
>>> verbose: *kati*: slow included makefiles (4.604702): build/make/core/
>>> base_rules.mk
>>> verbose: *kati*: slow included makefiles (4.605250): build/make/core/
&g

Re: [android-building] Disallowed PATH tool "m4", but used by flex

['Dan Willemsen' via Android Building]

As a reminder:

This preview is not a full platform update and only for reference.


It is not expected that everything will build, as it only contains updates
to some projects.

For this breakage in particular, you'll need a change like this one, which
fixes up a bunch of things around how mesa was using flex/bison:
https://android-review.googlesource.com/c/platform/external/mesa3d/+/1203548

- Dan

On Mon, Mar 30, 2020 at 7:58 AM Michael Goffioul 
wrote:

> I'm experimenting with android-r-preview-2 and found a problem compiling
> mesa, which didn't occur with android-10. The error occurs when running
> flex:
>
> 23:56:24 Disallowed PATH tool "m4" used: []string{"m4", "-P"}
> 23:56:24 See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
> [  0% 1/74788] Mesa Lex: libmesa_glsl <=
> external/mesa/src/compiler/glsl/glcpp/glcpp-lex.l
> FAILED:
> out/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
> /bin/bash -c "prebuilts/build-tools/linux-x86/bin/flex --nounistd
> -oout/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
> external
> /mesa/src/compiler/glsl/glcpp/glcpp-lex.l"
> "m4" is not allowed to be used. See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
>
> From what I understand, flex internally calls "m4" (according to this
> reference:
> https://www.cs.virginia.edu/~cr4bd/flex-manual/M4-Dependency.html).
>
> Any pointer in the right direction would be appreciated, 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/CAB-99LtxMUAWGZG2SbnjKB0iOiNAQV5R5oZP%2BHaUaeeW%3D1LZMA%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAB-99LtxMUAWGZG2SbnjKB0iOiNAQV5R5oZP%2BHaUaeeW%3D1LZMA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DKLk8dSES94QAgJqgre99PrGJKBiBLwHSOOAcwudSeZg%40mail.gmail.com.

Re: [android-building] equivalent flag "optimize" from Android.bp in Android.mk

['Dan Willemsen' via Android Building]

`LOCAL_PROGUARD_ENABLED := disabled` would be the equivalent of `optimize:
{ enabled: false }`

- Dan

On Tue, Apr 28, 2020 at 11:51 AM Kbc K  wrote:

> Hi Everyone,
>
> Soong build system "Android.bp" has a useful flag called "optimize" which
> allow to disable compiler optimization.
>
> I'm looking for something equivalent in Android.mk system.
>
> BR, K
>
> --
> --
> 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/8d5ed84a-8753-44c9-999f-c55e7874b665%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/8d5ed84a-8753-44c9-999f-c55e7874b665%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnFyXbGOic1UNYqeFCtfFzaUTuMCUKsWTrG8cL_1MWNZA%40mail.gmail.com.

Re: [android-building] Replacing acloud prebuilt binary

['Dan Willemsen' via Android Building]

I believe the prebuilt comes from the python support in the platform build
system, not setup.py:

  source build/envsetup.sh
  m acloud
  cp out/host/linux-x86/bin/acloud-dev .../acloud

- Dan

On Tue, Apr 21, 2020 at 11:16 AM Andre D  wrote:

> Hello,
>
> Is it possible to replace the prebuilt acloud binary
> (prebuilts/asuite/acloud)? When I run "python setup.py bdist_wheel" within
> the tools/acloud directory I don't find any binary in the output. I'm new
> to Python, so perhaps I'm missing something.
>
> Thank you,
> Andre
>
> --
> --
> 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/83408403-ec0a-4b15-a87a-5d11bc230094%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/83408403-ec0a-4b15-a87a-5d11bc230094%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DCrR9jghSXM24t%3D3HdoHvga5fknU9%2Bmij7OiPQhhdSeA%40mail.gmail.com.

Re: [android-building] Memory leak?

['Dan Willemsen' via Android Building]

The minimum requirements for the build is 16GB of RAM available (and even
with that it can be difficult later in the build). The virtualization
mention was meant to say that a machine with 16GB of RAM wasn't enough when
virtualizing -- the virtual machine would need 16GB allocated to it.

`m -j1` means that we'll only launch a single process at a time, but many
of those spin up a number of threads on their own. Parallelism can have
some effect on peak RAM use, but I wouldn't expect that to significantly
affect things, at least for soong_build.

Which target you're building can have a reasonably big impact on RAM usage
(as 64-bit targets need both 64 and 32 bit configurations). On my machine
with aosp-master:

 aosp_cf_x86_phone - soong_build peaks at ~6GB  (and allocated ~20GB over
its lifetime). next, kati takes ~4GB
 aosp_crosshatch - soong_build peaks at ~8.5GB  (and allocated ~26GB over
its lifetime). next, kati takes ~6GB

For some of our larger branches/targets, I've seen peaks at >14GB (~50GB
lifetime allocs), with kati using >10GB.

- Dan

On Thu, Apr 30, 2020 at 12:05 PM Eliane Fonseca 
wrote:

> same problem with 2 processes and I have only 8 GB of physical RAM and it
> is not virtualized system . any timing for fix ?
>
> Em 30 de abr de 2020 13:43, "Silver Rampart" 
> escreveu:
>
> When running a normal build, process soong_build quickly fills up all
> available memory (6GB in under 5 minutes) and starts to swap. Quad-core i5.
> I understand this might have something to do with parallelism, but I run
> make with -j1 and soong_build is still running multiple threads.
>
> --
> --
> 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/ca25a692-cd1f-4096-be61-552017644208%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ca25a692-cd1f-4096-be61-552017644208%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
> --
> --
> 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/CAJ%2BSQK6ow5BwiNHUpt9bxTcjnJsyVBptX6mkL%2B4Pn9KaA3mNRA%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAJ%2BSQK6ow5BwiNHUpt9bxTcjnJsyVBptX6mkL%2B4Pn9KaA3mNRA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnkEefTzYxU%2BYnGH5RN27vROLmBitc6VkfgVCwjLMuN3g%40mail.gmail.com.

Re: [android-building] "Build sandboxing disabled due to nsjail error. This may become fatal in the future."

['Dan Willemsen' via Android Building]

Yes, we're familiar with the docker problems, and we'll likely have to live
with it for the time being: https://issuetracker.google.com/123210688 .
I've removed the above message from master and Android 11 (the other common
case was distributions that turned off user namespaces).

> I suppose this is not very helpful in my case for me as Docker is already
doing process isolation?

I'm actually less interested in it as a security isolation boundary, and
more interested in it providing more assurances about the behaviors we
expect from the build, and provide more safety by default:

* Guarantees that processes don't continue running past the end of the
build (or the part of the build). In practice, this should just be a safety
precaution, and if you're starting the build via the docker command line
every time, it should provide similar guarantees (if you're attaching to a
long-running docker instance, not so much).
* Allows us to turn off the network for part of the build. In most cases
right now this can be emulated by just turning off the network for that
docker container, but with the remote execution work that's ongoing, we
allow a daemon access to the network, but turn it off for the rest of the
build (which tunnels build requests to the daemon as necessary).
* Recently on master, turns off write access to the rest of the system
(except $srcdir, $outdir, $distdir, $home? something like that). Depending
on your docker setup, this safety may not be too important (just mounting
the necessary directories, and throwing away any changes made after the
build exists, for example).

So while we can't require the use of nsjail at this point, it may mean that
your build succeeds while the same build on another system using nsjail
fails. You may be able to configure docker similarly, but changing the
configuration during different parts of the build likely wouldn't be
possible.

I'd like to do things like turn the source directory read only, but I've
been hesitant to do so because it'll cause a larger behavior difference
between the nsjail users and the rest. Also on the list is hiding things
like /usr/include from the build, as we never want to use it. Potentially
changing what parts of the output tree are read/write vs read-only vs
invisible during different parts of the build is another idea I've had.

- Dan



On Thu, Apr 30, 2020 at 9:43 AM Ricky Ng-Adam  wrote:

> Hello!
>
> I'm building Android 10 in a Docker with overlay and getting the following
> error:
>
> Building Android
>
>
> 06:58:14 Build sandboxing disabled due to nsjail error. This may become
> fatal in the future.
>
> 06:58:14 Please let us know why nsjail doesn't work in your environment
> at:
>
> 06:58:14   https://groups.google.com/forum/#!forum/android-building
>
>
> 06:58:14   https://issuetracker.google.com/issues/new?component=381517
>
> https://github.com/google/nsjail
>
> A light-weight process isolation tool, making use of Linux namespaces and
> seccomp-bpf syscall filters (with help of the kafel bpf language)
>
> I suppose this is not very helpful in my case for me as Docker is already
> doing process isolation? I see it's possible to run nsjail but it requires
> --disable_proc and --privileged.
>
> I'm supposing nsjail exists to provide better performance?
>
> Does it work well with Overlay FS? I'm trying to build for every branch
> without copying over all source tree and output build objects.
>
> Thanks,
>
> Ricky
>
> --
> --
> 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/8cd8ef17-d322-404e-986e-feb0f5c7c3c8%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/8cd8ef17-d322-404e-986e-feb0f5c7c3c8%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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 sub

Re: [android-building] shared library can't be copied into OTATOOLS

['Dan Willemsen' via Android Building]

What version of AOSP are you using? The current aosp/master builds of
otatools.zip definitely have lib64/libbase.so:
https://ci.android.com/builds/submitted/6459548/aosp_cf_x86_phone-userdebug/latest

And printing out INTERNAL_OTATOOLS_MODULES_WITH_DEPS, it's getting libbase
added from get-all-shared-libs-deps.

- Dan

On Mon, May 4, 2020 at 8:48 AM 임정민  wrote:

> Hi I found there are no shared library in ota packages.
>
> I expect there are some modules and shared libraries.
> but only existing were modules like lpunpack.
> I hope there are shared libraries such as libbase.so.
> but It's not working.
>
> I think get-all-shared-libs-deps is related with copying shared libraries
> into ota_package. but It's not working
> please check it for me
>
> thanks
>
> !!
> /build/make/core/Makefile
> !
>
> ---
> INTERNAL_OTATOOLS_MODULES := \
>   aapt2 \
>   add_img_to_target_files \
>   append2simg \
>   avbtool \
>   blk_alloc_to_base_fs \
>   boot_signer \
>   brillo_update_payload \
>   brotli \
>   bsdiff \
>   build_image \
>   build_super_image \
>   build_verity_metadata \
>   build_verity_tree \
>   care_map_generator \
>   check_ota_package_signature \
>   check_target_files_signatures \
>   check_target_files_vintf \
>   checkvintf \
>   delta_generator \
>   e2fsck \
>   e2fsdroid \
>   fc_sort \
>   fec \
>   fs_config \
>   generate_verity_key \
>   img2simg \
>   img_from_target_files \
>   imgdiff \
>   libconscrypt_openjdk_jni \
>   lpmake \
>   lpunpack \
>   make_f2fs \
>   merge_target_files \
>   minigzip \
>   mk_combined_img \
>   mkbootfs \
>   mkbootimg \
>   mke2fs \
>   mke2fs.conf \
>   mkf2fsuserimg.sh \
>   mksquashfs \
>   mksquashfsimage.sh \
>   mkuserimg_mke2fs \
>   ota_from_target_files \
>   sefcontext_compile \
>   sgdisk \
>   shflags \
>   sign_apex \
>   sign_target_files_apks \
>   signapk \
>   simg2img \
>   sload_f2fs \
>   tune2fs \
>   unpack_bootimg \
>   update_host_simulator \
>   validate_target_files \
>   verity_signer \
>   verity_verifier \
>   zipalign \
>
> # Additional tools to unpack and repack the apex file.
> INTERNAL_OTATOOLS_MODULES += \
>   apexer \
>   deapexer \
>   debugfs_static \
>   merge_zips \
>   resize2fs \
>   soong_zip \
>
> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
> INTERNAL_OTATOOLS_MODULES += \
>   futility \
>   vboot_signer
> endif
>
> INTERNAL_OTATOOLS_FILES := \
>   $(filter $(HOST_OUT)/%,$(call
> module-installed-files,$(INTERNAL_OTATOOLS_MODULES)))
>
> .PHONY: otatools
> otatools: $(INTERNAL_OTATOOLS_FILES)
>
> # For each module, recursively resolve its host shared library
> dependencies. Then we have a full
> # list of modules whose installed files need to be packed.
>
> INTERNAL_OTATOOLS_MODULES_WITH_DEPS := \
>   $(sort $(INTERNAL_OTATOOLS_MODULES) \
>   $(foreach m,$(INTERNAL_OTATOOLS_MODULES),$(call
> get-all-shared-libs-deps,$(m
>
> INTERNAL_OTATOOLS_PACKAGE_FILES := \
>   $(filter $(HOST_OUT)/%,$(call
> module-installed-files,$(INTERNAL_OTATOOLS_MODULES_WITH_DEPS)))
>
> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>   $(sort $(shell find build/make/target/product/security -type f -name
> "*.x509.pem" -o \
>   -name "*.pk8" -o -name verity_key))
>
> ifneq (,$(wildcard device))
> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>   $(sort $(shell find device $(wildcard vendor) -type f -name "*.pk8" -o
> -name "verifiedboot*" -o \
>   -name "*.pem" -o -name "oem*.prop" -o -name "*.avbpubkey"))
> endif
> ifneq (,$(wildcard external/avb))
> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>   $(sort $(shell find external/avb/test/data -type f -name "testkey_*.pem"
> -o \
>   -name "atx_metadata.bin"))
> endif
> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>   $(sort $(shell find external/vboot_reference/tests/devkeys -type f))
> endif
>
> INTERNAL_OTATOOLS_RELEASETOOLS := \
>   $(sort $(shell find build/make/tools/releasetools -name "*.pyc" -prune
> -o \
>   \( -type f -o -type l \) -print))
>
> BUILT_OTATOOLS_PACKAGE := $(PRODUCT_OUT)/otatools.zip
> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_ZIP_ROOT := $(call
> intermediates-dir-for,PACKAGING,otatools)/otatools
> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_OTATOOLS_PACKAGE_FILES :=
> $(INTERNAL_OTATOOLS_PACKAGE_FILES)
> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_OTATOOLS_RELEASETOOLS :=
> $(INTERNAL_OTATOOLS_RELEASETOOLS)
> $(BUILT_OTATOOLS_PACKAGE): $(INTERNAL_OTATOOLS_PACKAGE_FILES)
>

Re: [android-building] Re: android build take eons

['Dan Willemsen' via Android Building]

Yep, this greatly depends on your machine and which target you're building
-- there are builds and configurations that can do a full clean build in
~30 minutes, but that's a simpler config and a high-end machine.

For the workflow:

if i want to include a new library, or write a new driver, or change
> something minimal, and recompile, isn't there a way to do it quicker?
>

You should only need to do the full clean build once, after that
incremental builds should be much much shorter (our goals are generally
<<1min, but that significantly depends on what you change, and your
machine). You should always try to use incremental builds.

And if you know that you only want to rebuild a single partition / don't
need images / etc, you can ask for `m vendorimage`/`m sync`/etc, but what
works there greatly depends on the types of changes you're making, and what
you need out of the build.


>  And be sure to use make -k to take advantage of all your CPUs.


'-k' is keep going, you're thinking of '-j', but that's been the default
for a while now.

- Dan

On Mon, May 4, 2020 at 12:29 PM 'Glenn Kasten' via Android Building <
android-building@googlegroups.com> wrote:

> The listed build hardware requirements
> <https://source.android.com/setup/build/requirements#hardware-requirements>
> are the bare minimum.
> The more RAM and CPUs you have, the better.
> And be sure to use make -k to take advantage of all your CPUs.
>
> On Monday, May 4, 2020 at 12:19:43 PM UTC-7, Imx6dev Kit wrote:
>>
>> I got my AOSP build to work but it took maybe 8 hours ... i cannot
>> imagine how anyone can develop anything this way .. if i want to include a
>> new library, or write a new driver, or change something minimal, and
>> recompile, isn't there a way to do it quicker?  What is the recommended way
>> to build after making a minor change?
>>
> --
> --
> 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/5192f89b-c40e-4bba-969c-ec6f012d8324%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/5192f89b-c40e-4bba-969c-ec6f012d8324%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DMqEL1LQ74%2Bn7aVjwEuKb3jbpFYGRujQLXmQyML_FdLw%40mail.gmail.com.

Re: [android-building] repo init python2.7 or python3.6 which one to use?

['Dan Willemsen' via Android Building]

When using `--repo-url=git://codeaurora.org/tools/repo.git
 --repo-branch=caf-stable`, you likely need to use a repo launcher
downloaded from codeaurora as well, as it seems the upstream repo launcher
is not compatible with it. I'm not familiar with codeaurora though --
there's a chance you could remove those arguments and be successful, this
may be something to bring up in their forums / support channels.

- Dan

On Wed, Apr 22, 2020 at 9:23 AM Yuvaraj Velumani  wrote:

> 1. I have my Ubuntu server 16.04.10 installed which has python 2.7.12 and
> 3.6.9(I installed it - following procedure referring
> https://realpython.com/installing-python/)
> 2. Installed repo launcher (version 2.5) as per
> https://source.android.com/setup/build/downloading (by default I used curl
> https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo)
>
> My intention was to install the qualcomm processor public code from using 
> "repo
> init -u https://source.codeaurora.org/quic/la/platform/manifest.git -b
> release -m LA.AU.0.0.1-03620-sa8155_gvmq.0.xml --repo-url=git://
> codeaurora.org/tools/repo.git --repo-branch=caf-stable"
>
> *My initial repo download messages showed (when using python 3.6.9)*
>  warning: Python 3 support is currently experimental. YMMV.
>  Please use Python 2.6 - 2.7 instead
>  Get https://source.codeaurora.org/quic/le/le/manifest
> *Error Message*
>  File "/usr/local/lib/python3.6/codecs.py", line 321, in decode
>  (result, consumed) = self._buffer_decode(data, self.errors, final)
>  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9d in position
> 151: invalid start byte
>
> *After this I change to python 2.7.12 *(rm -rf ~/bin/repo and used curl
> https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repo)
> and launched "repo init -u
> https://source.codeaurora.org/quic/la/platform/manifest.git -b release -m
> LA.AU.0.0.1-03620-sa8155_gvmq.0.xml --repo-url=git://
> codeaurora.org/tools/repo.git --repo-branch=caf-stable"
>
> *My initial repo download messages showed (when using python 2.7.12)*
> Get https://source.codeaurora.org/quic/la/tools/repo.git/clone.bundle
> Get https://source.codeaurora.org/quic/la/tools/repo.git
> *Error Message*
> File "/usr/lib/python2.7/pickle.py", line 1384, in load
> return Unpickler(file).load()
> File "/usr/lib/python2.7/pickle.py", line 864, in load
>  dispatch[key](self)
>  File "/usr/lib/python2.7/pickle.py", line 892, in load_proto
>  raise ValueError, "unsupported pickle protocol: %d" % proto
>  ValueError: unsupported pickle protocol: 4
>
> I really don't know what is the real issue.
>
> Thanks in advance and I appreciate your help.
>
> --
> --
> 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/054a0cab-d651-467d-942b-3aa54e3664a8%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/054a0cab-d651-467d-942b-3aa54e3664a8%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnGB4_WTUx_R8ZYEEeWo449%3DMxM7B3AGqArx%3Da6qE2S2Q%40mail.gmail.com.

Re: [android-building] Android.mk deprecation status and plan

['Dan Willemsen' via Android Building]

The AOSP master branch is already reflecting the 2021 work in progress.

For the Android 11 (2020) release,
https://cs.android.com/android/_/android/platform/build/+/be01cf841e95b8ae396625486b8fb746e5e71492:Deprecation.md;drc=97ec8127081ce0e4b372349caa513ccde9f0fcf7;bpv=0;bpt=0
will
be the state:

Host C/C++ builds in Make have been deprecated, and are errors by default
(but are still available behind BUILD_BROKEN_USES_BUILD_* flags). Lesser
used module types (AUX, NATIVE_BENCHMARK, STATIC_TEST_LIBRARY) are also in
that state. [HOST_]SHARED_TEST_LIBRARY was removed because it was
previously marked obsolete.

The rest of the module types are still available, but as before, there may
be other reasons you need to switch code to Android.bp -- if something else
that was converted to Android.bp needs to link to your library, your
library needs to be in an Android.bp; if you are defining a jar to put in
the bootclasspath; etc.

- Dan

On Thu, Apr 23, 2020 at 8:58 AM XING WANG 
wrote:

> I checked the doc in build repo
> https://cs.android.com/android/platform/superproject/+/master:build/make/Deprecation.md,
> Google is coverting the make to soong.
>
> Will google convert all BUILD_* to soong in 2020 release?  If not，could
> you give us a deprecation plan list in 2020 release ?
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/a9baa74b-96c7-4548-87cb-ba3295cb471f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/a9baa74b-96c7-4548-87cb-ba3295cb471f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkgXUOkb8F5WnorLMEZF0H-xP3-TrBecF6ffmJCnqoKxw%40mail.gmail.com.

Re: [android-building] Re: shared library can't be copied into OTATOOLS

['Dan Willemsen' via Android Building]

Just adding "libc++" (etc) to that list would trigger the shared library to
be installed, but in general (just like PRODUCT_PACKAGES), you shouldn't
need to refer to shared libraries because they should be included as a
byproduct of being used by one of the binaries in that list (unless they're
used via `dlopen`).

- Dan

On Wed, May 6, 2020 at 4:27 PM 임정민  wrote:

> I'm checking R OS
> And I made something wrong the question.
> I need OTATOOLS have shared library
> until Q OS there is lines like
> --
> 2504# Shared libraries.
> 2505OTATOOLS += \
> 2506 $(HOST_LIBRARY_PATH)/libc++$(HOST_SHLIB_SUFFIX) \
> 2507 $(HOST_LIBRARY_PATH)/liblog$(HOST_SHLIB_SUFFIX) \
> --
>
> but It's removed at R OS how could I insert shared library into OTA/tools
>
> 2020년 5월 5일 화요일 오전 12시 49분 15초 UTC+9, 임정민 님의 말:
>>
>> Hi I found there are no shared library in ota packages.
>>
>> I expect there are some modules and shared libraries.
>> but only existing were modules like lpunpack.
>> I hope there are shared libraries such as libbase.so.
>> but It's not working.
>>
>> I think get-all-shared-libs-deps is related with copying shared libraries
>> into ota_package. but It's not working
>> please check it for me
>>
>> thanks
>>
>> !!
>> /build/make/core/Makefile
>> !
>>
>> ---
>> INTERNAL_OTATOOLS_MODULES := \
>>   aapt2 \
>>   add_img_to_target_files \
>>   append2simg \
>>   avbtool \
>>   blk_alloc_to_base_fs \
>>   boot_signer \
>>   brillo_update_payload \
>>   brotli \
>>   bsdiff \
>>   build_image \
>>   build_super_image \
>>   build_verity_metadata \
>>   build_verity_tree \
>>   care_map_generator \
>>   check_ota_package_signature \
>>   check_target_files_signatures \
>>   check_target_files_vintf \
>>   checkvintf \
>>   delta_generator \
>>   e2fsck \
>>   e2fsdroid \
>>   fc_sort \
>>   fec \
>>   fs_config \
>>   generate_verity_key \
>>   img2simg \
>>   img_from_target_files \
>>   imgdiff \
>>   libconscrypt_openjdk_jni \
>>   lpmake \
>>   lpunpack \
>>   make_f2fs \
>>   merge_target_files \
>>   minigzip \
>>   mk_combined_img \
>>   mkbootfs \
>>   mkbootimg \
>>   mke2fs \
>>   mke2fs.conf \
>>   mkf2fsuserimg.sh \
>>   mksquashfs \
>>   mksquashfsimage.sh \
>>   mkuserimg_mke2fs \
>>   ota_from_target_files \
>>   sefcontext_compile \
>>   sgdisk \
>>   shflags \
>>   sign_apex \
>>   sign_target_files_apks \
>>   signapk \
>>   simg2img \
>>   sload_f2fs \
>>   tune2fs \
>>   unpack_bootimg \
>>   update_host_simulator \
>>   validate_target_files \
>>   verity_signer \
>>   verity_verifier \
>>   zipalign \
>>
>> # Additional tools to unpack and repack the apex file.
>> INTERNAL_OTATOOLS_MODULES += \
>>   apexer \
>>   deapexer \
>>   debugfs_static \
>>   merge_zips \
>>   resize2fs \
>>   soong_zip \
>>
>> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
>> INTERNAL_OTATOOLS_MODULES += \
>>   futility \
>>   vboot_signer
>> endif
>>
>> INTERNAL_OTATOOLS_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES)))
>>
>> .PHONY: otatools
>> otatools: $(INTERNAL_OTATOOLS_FILES)
>>
>> # For each module, recursively resolve its host shared library
>> dependencies. Then we have a full
>> # list of modules whose installed files need to be packed.
>>
>> INTERNAL_OTATOOLS_MODULES_WITH_DEPS := \
>>   $(sort $(INTERNAL_OTATOOLS_MODULES) \
>>   $(foreach m,$(INTERNAL_OTATOOLS_MODULES),$(call
>> get-all-shared-libs-deps,$(m
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES_WITH_DEPS)))
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find build/make/target/product/security -type f -name
>> "*.x509.pem" -o \
>>   -name "*.pk8" -o -name verity_key))
>>
>> ifneq (,$(wildcard device))
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find device $(wildcard vendor) -type f -name "*.pk8" -o
>> -name "verifiedboot*" -o \
>>   -name "*.pem" -o -name "oem*.prop" -o -name &quo

Re: [android-building] Re: shared library can't be copied into OTATOOLS

['Dan Willemsen' via Android Building]

No, libc++.so is already included in the otatools zip file that I linked
earlier (missing that file would cause issues in our infrastructure using
otatools as well). I've confirmed it's there in our internal R trees as
well. If it's not showing up in your builds, are you sure you don't have a
local change to the build system causing this problem?

$ zipinfo otatools.zip | less
Archive:  otatools.zip
Zip file size: 361711518 bytes, number of entries: 257
-rwx--  2.0 unx 68541840 bl defN 08-Jan-01 00:00 bin/aapt2
-rwx--  2.0 unx 31833568 bl defN 08-Jan-01 00:00
bin/add_img_to_target_files
...
-rwx--  2.0 unx   558272 bl defN 08-Jan-01 00:00 bin/lpmake
-rwx--  2.0 unx   519040 bl defN 08-Jan-01 00:00 bin/lpunpack
...
-rw 2.0 fat  1720976 bl defN 08-Jan-01 00:00
framework/boot_signer.jar
-rw 2.0 fat  2715758 bl defN 08-Jan-01 00:00 framework/signapk.jar
-rw 2.0 fat  1716209 bl defN 08-Jan-01 00:00
framework/verity_signer.jar
-rwx--  2.0 unx  4114648 bl defN 08-Jan-01 00:00 lib64/libbase.so
-rwx--  2.0 unx  1501888 bl defN 08-Jan-01 00:00
lib64/libbrillo-stream.so
-rwx--  2.0 unx  2690344 bl defN 08-Jan-01 00:00 lib64/libbrillo.so
-rwx--  2.0 unx  6454680 bl defN 08-Jan-01 00:00 lib64/libc++.so
-rwx--  2.0 unx 20883064 bl defN 08-Jan-01 00:00 lib64/libchrome.so
-rwx--  2.0 unx 13054768 bl defN 08-Jan-01 00:00
lib64/libconscrypt_openjdk_jni.so
-rwx--  2.0 unx  6968648 bl defN 08-Jan-01 00:00 lib64/libcrypto-host.so
-rwx--  2.0 unx16736 bl defN 08-Jan-01 00:00
lib64/libcrypto_utils.so
-rwx--  2.0 unx   199776 bl defN 08-Jan-01 00:00 lib64/libcutils.so
...

- Dan

On Wed, May 6, 2020 at 4:58 PM 임정민  wrote:

> Thanks for quick response.
> Why I'm doing this. We use lpunpack including OTA/tools.
> but when I'm running lpunpack there is error cause there are no shared
> library like libc++
>
> You mean I should check all of this and added it into OTA/tools one by one?
>
> 2020년 5월 5일 화요일 오전 12시 49분 15초 UTC+9, 임정민 님의 말:
>>
>> Hi I found there are no shared library in ota packages.
>>
>> I expect there are some modules and shared libraries.
>> but only existing were modules like lpunpack.
>> I hope there are shared libraries such as libbase.so.
>> but It's not working.
>>
>> I think get-all-shared-libs-deps is related with copying shared libraries
>> into ota_package. but It's not working
>> please check it for me
>>
>> thanks
>>
>> !!
>> /build/make/core/Makefile
>> !
>>
>> ---
>> INTERNAL_OTATOOLS_MODULES := \
>>   aapt2 \
>>   add_img_to_target_files \
>>   append2simg \
>>   avbtool \
>>   blk_alloc_to_base_fs \
>>   boot_signer \
>>   brillo_update_payload \
>>   brotli \
>>   bsdiff \
>>   build_image \
>>   build_super_image \
>>   build_verity_metadata \
>>   build_verity_tree \
>>   care_map_generator \
>>   check_ota_package_signature \
>>   check_target_files_signatures \
>>   check_target_files_vintf \
>>   checkvintf \
>>   delta_generator \
>>   e2fsck \
>>   e2fsdroid \
>>   fc_sort \
>>   fec \
>>   fs_config \
>>   generate_verity_key \
>>   img2simg \
>>   img_from_target_files \
>>   imgdiff \
>>   libconscrypt_openjdk_jni \
>>   lpmake \
>>   lpunpack \
>>   make_f2fs \
>>   merge_target_files \
>>   minigzip \
>>   mk_combined_img \
>>   mkbootfs \
>>   mkbootimg \
>>   mke2fs \
>>   mke2fs.conf \
>>   mkf2fsuserimg.sh \
>>   mksquashfs \
>>   mksquashfsimage.sh \
>>   mkuserimg_mke2fs \
>>   ota_from_target_files \
>>   sefcontext_compile \
>>   sgdisk \
>>   shflags \
>>   sign_apex \
>>   sign_target_files_apks \
>>   signapk \
>>   simg2img \
>>   sload_f2fs \
>>   tune2fs \
>>   unpack_bootimg \
>>   update_host_simulator \
>>   validate_target_files \
>>   verity_signer \
>>   verity_verifier \
>>   zipalign \
>>
>> # Additional tools to unpack and repack the apex file.
>> INTERNAL_OTATOOLS_MODULES += \
>>   apexer \
>>   deapexer \
>>   debugfs_static \
>>   merge_zips \
>>   resize2fs \
>>   soong_zip \
>>
>> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
>> INTERNAL_OTATOOLS_MODULES += \
>>   futility \
>>   vboot_signer
>> endif
>>
>> INTERNAL_OTATOOLS_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES)))
>>
>> .PHONY: otatools
>> otatools: $(INTERNAL_OTATOOLS_FILES)
>>
>> # For each module

Re: [android-building] Re: shared library can't be copied into OTATOOLS

['Dan Willemsen' via Android Building]

Ah, yes, the (internal, unstable) INTERNAL_OTATOOLS_FILES variable has
changed meaning. Your local change to copy the files into OTA/tools
wouldn't be able to use that variable anymore.

I think you'd need the contents of INTERNAL_OTATOOLS_PACKAGE_FILES before
the rest of the keys/etc get added to it, so maybe save it away in your own
variable directly after this line:

INTERNAL_OTATOOLS_PACKAGE_FILES := \
$(filter $(HOST_OUT)/%,$(call
module-installed-files,$(INTERNAL_OTATOOLS_MODULES_WITH_DEPS)))

- Dan

On Thu, May 7, 2020 at 12:41 AM 임정민  wrote:

> I haven't been checking otatools.zip yet
> but I'm pretty sure otatools.zip has lib already
> What I want is shared library should be located in OTA/tools
> When I checked the code, copy files only $(INTERNAL_OTATOOLS_FILES)
> with this script "$(hide) cp $(INTERNAL_OTATOOLS_FILES) $(zip_root)
> /OTA/tools/"
> before R, shared library located in OTA/tools/ cause
> INTERNAL_OTATOOLS_FILES has shared library also.
> but in R, INTERNAL_OTATOOLS_FILES doesn't have shared library
> 4872 $(hide) cp $(INTERNAL_OTATOOLS_FILES) $(zip_root)/OTA/tools/
>
>
> 2020년 5월 5일 화요일 오전 12시 49분 15초 UTC+9, 임정민 님의 말:
>>
>> Hi I found there are no shared library in ota packages.
>>
>> I expect there are some modules and shared libraries.
>> but only existing were modules like lpunpack.
>> I hope there are shared libraries such as libbase.so.
>> but It's not working.
>>
>> I think get-all-shared-libs-deps is related with copying shared libraries
>> into ota_package. but It's not working
>> please check it for me
>>
>> thanks
>>
>> !!
>> /build/make/core/Makefile
>> !
>>
>> ---
>> INTERNAL_OTATOOLS_MODULES := \
>>   aapt2 \
>>   add_img_to_target_files \
>>   append2simg \
>>   avbtool \
>>   blk_alloc_to_base_fs \
>>   boot_signer \
>>   brillo_update_payload \
>>   brotli \
>>   bsdiff \
>>   build_image \
>>   build_super_image \
>>   build_verity_metadata \
>>   build_verity_tree \
>>   care_map_generator \
>>   check_ota_package_signature \
>>   check_target_files_signatures \
>>   check_target_files_vintf \
>>   checkvintf \
>>   delta_generator \
>>   e2fsck \
>>   e2fsdroid \
>>   fc_sort \
>>   fec \
>>   fs_config \
>>   generate_verity_key \
>>   img2simg \
>>   img_from_target_files \
>>   imgdiff \
>>   libconscrypt_openjdk_jni \
>>   lpmake \
>>   lpunpack \
>>   make_f2fs \
>>   merge_target_files \
>>   minigzip \
>>   mk_combined_img \
>>   mkbootfs \
>>   mkbootimg \
>>   mke2fs \
>>   mke2fs.conf \
>>   mkf2fsuserimg.sh \
>>   mksquashfs \
>>   mksquashfsimage.sh \
>>   mkuserimg_mke2fs \
>>   ota_from_target_files \
>>   sefcontext_compile \
>>   sgdisk \
>>   shflags \
>>   sign_apex \
>>   sign_target_files_apks \
>>   signapk \
>>   simg2img \
>>   sload_f2fs \
>>   tune2fs \
>>   unpack_bootimg \
>>   update_host_simulator \
>>   validate_target_files \
>>   verity_signer \
>>   verity_verifier \
>>   zipalign \
>>
>> # Additional tools to unpack and repack the apex file.
>> INTERNAL_OTATOOLS_MODULES += \
>>   apexer \
>>   deapexer \
>>   debugfs_static \
>>   merge_zips \
>>   resize2fs \
>>   soong_zip \
>>
>> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
>> INTERNAL_OTATOOLS_MODULES += \
>>   futility \
>>   vboot_signer
>> endif
>>
>> INTERNAL_OTATOOLS_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES)))
>>
>> .PHONY: otatools
>> otatools: $(INTERNAL_OTATOOLS_FILES)
>>
>> # For each module, recursively resolve its host shared library
>> dependencies. Then we have a full
>> # list of modules whose installed files need to be packed.
>>
>> INTERNAL_OTATOOLS_MODULES_WITH_DEPS := \
>>   $(sort $(INTERNAL_OTATOOLS_MODULES) \
>>   $(foreach m,$(INTERNAL_OTATOOLS_MODULES),$(call
>> get-all-shared-libs-deps,$(m
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES_WITH_DEPS)))
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find build/make/target/product/security -type f -name
>> "*.x509.pem" -o \
>>   -name "*.pk8" -o -name verity_key))
>>
>> ifneq (,$(wildcard device))
>> INTERN

Re: [android-building] android.bp privileged prop not work

['Dan Willemsen' via Android Building]

I believe the problem is that you need to use `Privileged` instead of
`privileged`. (In Go, uppercase leading characters in field names are
exported and can be used by others, while lowercase ones are considered
private)

if ctx.AConfig().IsEnvTrue("PAX_PRI"){
>

Unless this is for temporary debugging, you probably want to use the
VendorConfig functions instead, so that it can be configured by the product
that you're building.

- Dan

On Mon, May 18, 2020 at 10:35 AM fanx lin  wrote:

> hi, I am buildding android Q , I want to build a app . and I want to use
> build env to control which the app installed in , I wrote a android.bp to
> build it. the key code as below:
>
> //omit
> //... ...
>
> func getPrivileged(ctx android.LoadHookContext)(bool){
> if ctx.AConfig().IsEnvTrue("PAX_PRI"){
> fmt.Println("PAX_PRI = true")
> return true
> }else{
> fmt.Println("PAX_PRI = false")
> return false
> }
> }
>
> func testDefault(ctx android.LoadHookContext){
> type props struct {
> privileged bool
> }
> p := {}
> p.privileged = getPrivileged(ctx)
> ctx.AppendProperties(p)
> }
>
>
> //omit
> //... ...
>
> the code above is not work，the println is ok, I can see the print, but the 
> privileged
> prop is not work, then I try to change the code as below, but is still not
> work:
>
> func testDefault(ctx android.LoadHookContext){
> type props struct {
> privileged *bool
> }
> var privileged bool
> p := {}
> privileged = getPrivileged(ctx)
> p.privileged = 
> ctx.AppendProperties(p)
> }
>
> maybe there is some error , can someone give me a hand ?  thanks a lot!!
>
> --
> --
> 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/cc666c99-50dd-4afd-a6ba-b3d3c10ec36a%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/cc666c99-50dd-4afd-a6ba-b3d3c10ec36a%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DJuRwPPsaZut71ivSGQHZABSbD5ycAH6%3DnELD0Qcae8w%40mail.gmail.com.

Re: [android-building] Re: android.bp privileged prop not work

['Dan Willemsen' via Android Building]

The Android.bp next to that go file is going to have a dep entry of
"soong-cc" (which gives you access to the "android/soong/cc" package).
"soong-java" will allow you to reference the "android/soong/java" package.

- Dan

On Tue, May 19, 2020 at 12:00 AM fanx lin  wrote:

> Hi Dan, I have one more question about：
>
> if we compile binary bin file，in go file，we write：
> func testDefaultFactory()(android.Module){
>  module := cc.DefaultsFactory()
>  android.AddLoadHook(module, testDefault)
>  return module
> }
> and if we compile shared lib，in go file ,we write:
> func testDefaultFactory()(android.Module){
>  module := cc.LibrarySharedFactory()
>  android.AddLoadHook(module, testDefault)
>  return module
> }
>
> but if we compile an app, I want to change the prop that only belong to
> app module, the binary module does not have. how do we write？ I tried to
> write like this：
> import (
> //omit
> "android/soong/java")
>
> func testDefaultFactory()(android.Module){
>  module := app.AndroidAppFactory()
>  android.AddLoadHook(module, testDefault)
>  return module
> }
>
> there is a compile error：can't find import: "android/soong/java". would
> you give me some help? thanks!
>
>
> 在 2020年5月19日星期二 UTC+8上午1:35:53，fanx lin写道：
>>
>> hi, I am buildding android Q , I want to build a app . and I want to use
>> build env to control which the app installed in , I wrote a android.bp to
>> build it. the key code as below:
>>
>> //omit
>> //... ...
>>
>> func getPrivileged(ctx android.LoadHookContext)(bool){
>> if ctx.AConfig().IsEnvTrue("PAX_PRI"){
>> fmt.Println("PAX_PRI = true")
>> return true
>> }else{
>> fmt.Println("PAX_PRI = false")
>> return false
>> }
>> }
>>
>> func testDefault(ctx android.LoadHookContext){
>> type props struct {
>> privileged bool
>> }
>> p := {}
>> p.privileged = getPrivileged(ctx)
>> ctx.AppendProperties(p)
>> }
>>
>>
>> //omit
>> //... ...
>>
>> the code above is not work，the println is ok, I can see the print, but
>> the privileged prop is not work, then I try to change the code as below,
>> but is still not work:
>>
>> func testDefault(ctx android.LoadHookContext){
>> type props struct {
>> privileged *bool
>> }
>> var privileged bool
>> p := {}
>> privileged = getPrivileged(ctx)
>> p.privileged = 
>> ctx.AppendProperties(p)
>> }
>>
>> maybe there is some error , can someone give me a hand ?  thanks a lot!!
>>
> --
> --
> 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/ec7139e6-7d2b-4b95-9257-e96c687b2b4d%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ec7139e6-7d2b-4b95-9257-e96c687b2b4d%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkw%2Bezp24vtb_ty5BwZaUi0LfHTa3UW1Oxoy8%3DJNG1ZGA%40mail.gmail.com.

Re: [android-building] Issue building AOSP with docker running on Mojave

['Dan Willemsen' via Android Building]

How much RAM have you given docker? `free -h` shows how much is available.
IIRC, unlike on linux, because docker on Mac is a VM, it can't grow to use
as much as necessary. Our docs list 16GB as the minimum available to the
build.

- Dan

On Thu, May 14, 2020 at 9:30 AM 6020peaks /\/\/\ <6020pe...@gmail.com>
wrote:

> Hi,
>
> I wonder if anyone tried to build the master branch of AOSP using a Docker
> container with Ubuntu 18.04 running on Mojave. If I compare the process
> with a Docker container running on Linux, on Mac it is way slower. And also
> the following issue appears when building. Any clue of what might be
> happening?
>
> Thanks!
>
> 07:58:34 Build sandboxing disabled due to nsjail error.
>
> 
>
> PLATFORM_VERSION_CODENAME=S
>
> PLATFORM_VERSION=S
>
> TARGET_PRODUCT=aosp_x86_64
>
> TARGET_BUILD_VARIANT=eng
>
> TARGET_BUILD_TYPE=release
>
> TARGET_ARCH=x86_64
>
> TARGET_ARCH_VARIANT=x86_64
>
> TARGET_2ND_ARCH=x86
>
> TARGET_2ND_ARCH_VARIANT=x86_64
>
> HOST_ARCH=x86_64
>
> HOST_2ND_ARCH=x86
>
> HOST_OS=linux
>
> HOST_OS_EXTRA=Linux-4.19.76-linuxkit-x86_64-Ubuntu-18.04.4-LTS
>
> HOST_CROSS_OS=windows
>
> HOST_CROSS_ARCH=x86
>
> HOST_CROSS_2ND_ARCH=x86_64
>
> HOST_BUILD_TYPE=release
>
> BUILD_ID=AOSP.MASTER
>
> OUT_DIR=out
>
> 
>
> [100% 39/39] 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
>
> Killed
>
> 08:00:37 soong bootstrap failed with: exit status 1
>
> ninja: build stopped: subcommand failed.
>
>
>  failed to build some targets (03:48 (mm:ss)) 
>
> --
> --
> 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/dc5e8f99-b0b8-46e2-9701-4f39f0f3dc13%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/dc5e8f99-b0b8-46e2-9701-4f39f0f3dc13%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmZyD2ej4puKrAJ3xGO%2B1cf5Od3z-4NoXrDXuS1srfEeA%40mail.gmail.com.

Re: [android-building] Android 10 build wmtest with extra jar error

['Dan Willemsen' via Android Building]

Does my-services.jar contain .class files, or .dex files?
java_import_libs is expecting .class files.

- Dan

On Thu, Mar 19, 2020 at 9:07 AM bersaty wu  wrote:

> I want to add my own jar to the wmtest apk, so I modify the .bp file like
> this:
>
> static_libs: [
> "frameworks-base-testutils",
> "services.core",
> "androidx.test.runner",
> "androidx.test.rules",
> "mockito-target-extended-minus-junit4",
> "platform-test-annotations",
> "servicestests-utils",
> "truth-prebuilt",
> "testables",
> "ub-uiautomator",
> "hamcrest-library",
> "my-services", //add for debug
> ],
>
>
> //add for debug
> java_import {
>  name: "my-services",
> jars: ["libs/my-services.jar"],
>   }
>
>
>
>
> I got this error when I build:
>
>
> Error: Cannot create android app from an archive
> 'out/soong/.intermediates/frameworks/base/services/tests/wmtests/WmTests/android_common/combined/WmTests.jar'
> containing both DEX and Java-bytecode content
> Compilation failed
> 15:55:32 ninja failed with: exit status 1
>
>
> Is there any solution?
>
>
> --
> --
> 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/ba80d301-a617-41e6-b0c3-ec7c67fecbf7%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ba80d301-a617-41e6-b0c3-ec7c67fecbf7%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdk4a4x%2BW9jcL3A2ds7dPupWps1Hr0RUZAjBe8EkJ-3EsA%40mail.gmail.com.

Re: [android-building] fatal error happens when I'm trying to include header files

['Dan Willemsen' via Android Building]

libupdater_core (which builds blockimg.cpp) does not depend on libinstall.
It gets edify/include and otautil/include through the libedify and
libotautil static libraries listed in libupdater_static_libs:

https://cs.android.com/android/platform/superproject/+/master:bootable/recovery/updater/Android.bp;drc=2bb374a86d0161700f01b68433063b0b13adc86a;l=16

Adding libinstall to that list would get you access to the header files,
but I don't think the code would be compiled into the updater binary.
That's still in make, so you'd have to add it to this list:

https://cs.android.com/android/platform/superproject/+/master:bootable/recovery/updater/Android.mk;drc=2bb374a86d0161700f01b68433063b0b13adc86a;l=25

That being said, I don't know anything about this code, so I don't know if
it's valid to use libinstall within the updater executable, since it's
normally in the recovery executable.

- Dan


On Thu, Mar 19, 2020 at 11:46 PM 임정민  wrote:

> I want to include install/install.h at blockimg.cpp
> but It returns always
>
> bootable/recovery/updater/blockimg.cpp: fatal error: 'install/install.h'
> file not found
> #include "install/install.h"
> ^~~
>
> I think this is related with Android.bp
>
> [ 35% 45930/130598] //bootable/recovery/updater:libupdater_core clang++
> install.cpp
> FAILED:
> out/soong/.intermediates/bootable/recovery/updater/libupdater_core/linux_glibc_x86_64_static/obj/bootable/recovery/updater/blockimg.o
> -Ibootable/recovery/edify/include
> -Ibootable/recovery/otautil/include
>
> there is no -Ibootable/recovery/install/include
>
> could you guide for me how to include install.h properly
>
> --
> --
> 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/09e2f0aa-d4b6-47af-aa86-2ed6057485eb%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/09e2f0aa-d4b6-47af-aa86-2ed6057485eb%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnQMwgZqAPL6hCMdsiF-pEkn%3DHMhFHWPwoE1b6iY_ZVqw%40mail.gmail.com.

Re: [android-building] How to integrate individual packages in cuttlefish

['Dan Willemsen' via Android Building]

Cuttlefish has opted into the mainline restrictions about using a common
system image. If this is meant to be generic, then maybe modify the
mainline_system.mk file (or there are variables to provide temporary
exemptions). Otherwise, configure your MyService / MyFramework modules to
be on the product image (product_specific: true), and use /product instead
of /system.

- Dan

On Fri, Mar 20, 2020 at 8:47 AM శంకర్ కుమార్ యల్లపు <
sankarkumar...@gmail.com> wrote:

> Hi,
>
> I was just trying to integrate our changes into cuttlefish. I am getting
> an error called *Offending entries when I add my make files in
> device/google/cuttlefish/vsoc_x86_64/device.mk <http://device.mk>*.
>
> Following is the error:
>
> FAILED:
> build/make/core/main.mk:1202: warning:
> device/google/cuttlefish/vsoc_x86_64/phone/aosp_cf.mk produces files
> inside build/make/target/product/mainline_system.mks artifact path
> requirement.
> Offending entries:
>
> system/app/MyService/MyService.apk
> system/etc/myfiles/config
> system/priv-app/MyFramework/MyFramework.apk
>
> Could anyone help me on why this error happens and how to resolve it?
>
> Thanks,
> Shankar
>
> --
> --
> 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/3525dc54-9ee0-47da-8536-70bba4e9f64f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/3525dc54-9ee0-47da-8536-70bba4e9f64f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D7ZHt285U%2BVjZtNr7eitYxVN%3DRKCAVejUUBg_TKyiY%3Dw%40mail.gmail.com.

[android-building] Re: how to integrate ninja and RBE to support remote build AOSP so fast?

['Dan Willemsen' via Android Building]

Someone should be reaching out to you directly about RBE, but I'd like to 
clarify that the remote execution API 
<https://github.com/bazelbuild/remote-apis> has more clients than just 
Bazel (even though it is in the bazelbuild github organization). The 
rewrapper support in AOSP is unrelated to Bazel, and currently integrates 
with the build similarly to ccache -- as a compiler wrapper.

- Dan

On Monday, March 23, 2020 at 7:39:55 AM UTC-7 mooo...@gmail.com wrote:

> hi,
>
> Android Building group,
>
> I noticed that One PPT called "Remote Execution and Caching for Android 
> Platform" . 
> Inside it has one page , it shows that ninja can call re.warper to execute 
> clang/java on remote server.
>
> In that PPT it shows the result is quite good from my point of view. So, I 
> want to know how it works? how can i build one system like this? I have 
> read pages https://cloud.google.com/remote-build-execution/docs/overview . 
> I learned that RBE is for Bazel .
>
> So I learned Bazel, I found that ,Bazel has its own BUILD file to be the 
> input to compile code. So I confused ,could any one can tell me ? How does 
> ninja call re-wrapper and send "compile" command to remote execution? How 
> does this progress know the out file is exist in Remote Cache? 
>
>
> I need to build one system like this to make the android and chips driver 
> compile as fast as I can. thanks
>
> [image: google.png]
>
>
>

-- 
-- 
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/43f97c87-1404-4bd8-9d72-0fe4f7ac712d%40googlegroups.com.

Re: [android-building] Establishing a build environment

['Dan Willemsen' via Android Building]

In general, at least with modern versions of Android, you shouldn't run
into any issues with any fairly modern linux distribution. And with each
release, we've been using fewer and fewer tools from your host distribution
to help with this. Please report any problems you run into.

Our build farm is still standardized on Ubuntu 14.04 because it still needs
to build some older versions of Android, which is why that text around
"tested internally" is still there. Our developers are on a version of
Debian Testing <https://en.wikipedia.org/wiki/GLinux> that is much more up
to date.

- Dan

On Wed, Sep 30, 2020 at 10:37 AM Gianmaria Iaculo 
wrote:

> Hello,
> We use 18.04 without any problem. Aosp 9.
>
> Regards
> Gianmaria
>
> Il giorno mer 30 set 2020 alle 17:51 malik...@gmail.com <
> malikma...@gmail.com> ha scritto:
>
>> Dear all,
>>
>> I have to establish a build environment for android. I was going through
>> the documentation provided on android website in order to find out that
>> which ubuntu version is best for installation. On one page it says
>>
>> If you're developing against the AOSP master branch, use either Ubuntu
>> 18.04 (Bionic Beaver) or the latest versions of macOS and Xcode with
>> command line tools installed.
>>
>> and on the other, it says
>>
>> The Android build is routinely tested in house on Ubuntu LTS (14.04) and
>> Debian testing. Most other distributions should have the required build
>> tools available.
>> You need a 64-bit version of Ubuntu (14.04 is recommended).
>>
>> Kindly let me know which version should I install 18.04 or 14.04
>>
>>
>> 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/ad7f1097-d6f2-49bc-8639-9dadb991n%40googlegroups.com
>> <https://groups.google.com/d/msgid/android-building/ad7f1097-d6f2-49bc-8639-9dadb991n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>> --
> --
> 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/CAN4d76rj4spXDhuizyEiS4KadBMUpak7N14kHhq_TkeNTPwXCg%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAN4d76rj4spXDhuizyEiS4KadBMUpak7N14kHhq_TkeNTPwXCg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D0KSxF6dW5czvVs0qBnkZQyfGV1rASK8meaGLoPK_ZnA%40mail.gmail.com.

Re: [android-building] Um........Please help me!!!

['Dan Willemsen' via Android Building]

Does prebuilts/go/linux-x86/bin/go exist in your source tree? It should
exist:

https://android.googlesource.com/platform/manifest/+/refs/heads/android-8.1.0_r64/default.xml#552
https://android.googlesource.com/platform/prebuilts/go/linux-x86/+/refs/tags/android-8.1.0_r64/bin/

If it does exist, are you able to execute it?

- Dan

On Tue, May 26, 2020 at 7:57 AM 박종현TV  wrote:

> I build android-8.1.0_r64 but an error occurred while build
>
>
> pjh@pjh-System-Product-Name:/media/pjh/android/AOSP$ make
> /media/pjh/android/AOSP/build/soong/cmd/microfactory/microfactory.bash: 줄
> 85: /media/pjh/android/AOSP/prebuilts/go/linux-x86//bin/go: 그런 파일이나 디렉터리가
> 없습니다
>
>  failed to build some targets  
>
> What should I do?
>
> --
> --
> 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/43a3acbc-60b8-4d5d-9dd4-1b3f756a94e9%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/43a3acbc-60b8-4d5d-9dd4-1b3f756a94e9%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DRVzz%3DQcDd40Cy-uz4Je4%2BpaFWvtDr9astGqV-b7ugdQ%40mail.gmail.com.

Re: [android-building] aosp master code build fail with "FAILED: out/soong/.primary/soong-ui-build/test/test.passed"

['Dan Willemsen' via Android Building]

I believe this was fixed with
https://android-review.googlesource.com/c/platform/build/soong/+/1384901,
so sync your tree and that should go away.

- Dan

On Fri, Jul 31, 2020 at 11:11 AM Suhang Wang  wrote:

> I sync the latest code, but get fallowing build fail.
>
> Mac OS Catalina 10.15.4 (19E287)
>
> FAILED: out/soong/.primary/soong-ui-build/test/test.passed
> out/soong/.bootstrap/bin/gotestrunner -p ./build/soong/ui/build -f
> out/soong/.primary/soong-ui-build/test/test.passed --
> out/soong/.primary/soong-ui-build/test/test -test.short --- FAIL:
> TestDumpRBEMetricsErrors (0.33s) --- FAIL:
> TestDumpRBEMetricsErrors/failed_to_copy_metrics_file (0.01s)
> rbe_test.go:111: got "rbe bootstrap with shutdown failed with: fork/exec
> /Volumes/android/android/out/soong/.temp/TestDumpRBEMetricsErrors_failed_to_copy_metrics_file418957930/001/bootstrap:
> exec format error\n\n", want "failed to copy" to be contained in error FAIL
>
> --
> --
> 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/9fcfa49f-42d4-4196-8ee8-a48699127662n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/9fcfa49f-42d4-4196-8ee8-a48699127662n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdm6_eLqX9gTem2DDBe%3DO-6ZSeKfdh2kpcLrOPpD1vpOTQ%40mail.gmail.com.

Re: [android-building] Replacement for BUILD_BROKEN_PHONY and phony-rebuild in android R

['Dan Willemsen' via Android Building]

So the problem here is likely because it's mixing absolute and relative
paths. All makefile rules (inputs and outputs) should be using $(OUT_DIR)
as is (which is usually "out", but can be an absolute path if the user has
changed it). So this would be appropriate:

KERNEL_OUT ?= $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ


But then the rule itself is likely expecting to use that path as an
absolute path, since the kernel build system likely uses `cd` to change
into a different path, where the relative path is no longer correct. The
best solution is to expand it inside those rules, as it keeps absolute
paths out of the ninja file (which can preserve the ability to diff between
checkouts, and allows moving the source directory without requiring
rebuilding everything). This doc section
<https://android.googlesource.com/platform/build/+/master/Changes.md#envsetup_sh-variables-with-make-equivalents>
has
an example, but it's essentially something like:

$(KERNEL_OUT)/arch/.../zImage: PRIVATE_SRCDIR := $(KERNEL_SRCDIR)
$(KERNEL_OUT)/arch/.../zImage: PRIVATE_OUT := $(KERNEL_OUT)
$(KERNEL_OUT)/arch/.../zImage: $(KERNEL_CONFIG) $(sort $(shell find -L
$(KERNEL_SRCDIR) -type f))
$(MAKE) -C $(PRIVATE_SRCDIR) O=$$(cd $(PRIVATE_OUT); pwd) ...

(If you can guarantee that nothing later in the build will change
KERNEL_SRCDIR/KERNEL_OUT, then you wouldn't need to use the PRIVATE_*
indirection, but it's generally a good idea to do so to prevent issues in
the future)

- Dan

On Tue, Aug 11, 2020 at 12:06 PM Sumit Kumar 
wrote:

> HI Dan,
> Thank for the insight , i was able to get through the phony-rebuild
> with an alternate mechanism "KERNEL_CONFIG: $(shell find -L
> $(KERNEL_SRCDIR)" and the build is passing successfully the only issue now
> i am getting is because of the previous change
>
> *#KERNEL_OUT ?= $(if $(filter /%
> ~%,$(TARGET_OUT_INTERMEDIATES)),,$(realpath
> $(OUT_DIR))/../)$(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ*
> *KERNEL_OUT ?= $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ*
>
> all the kernel intermidiates are generated in* kernel source * folder as
> we have removed the *realpath $(OUT_DIR) *from the equation , generating
> kernel intermidiates in *kernel_source *dir is not acceptable, i have
> tried all diffrent methods of pointing to the real
> *"out/target/product/**" * but with out success,  ,
> further please help me with the following querry
>
> ->  from the link
> https://android.googlesource.com/platform/build/+/master/Changes.md#phony_targets
>
>   *The target is a real file, but it's outside the output
> directories. All outputs from the build system should be within the output
> directory, otherwise m clean is unable to clean the build, and future
> builds may not work properly*.
> :- Does this mean the path to the target file should start with "*out*"  
> because
> i am not getting readonly error only when the path is specified as 
> *out/target/product/**
> *as mentoined by *KERNE_OUT *above , but any other real path "
> */data/home/sumkumar/work/workspace/R/out/target/product/**/obj/KERNEL_OBJ/arch/arm64/boot/Image"
>  * is
> leading to error thrown ?
>
> Please sugget any alternative for this so that the kernel intermidiates
> are actually generated in the real *out/target/product/**/obj/KERNEL_OBJ* 
> directory
> .
>
> Regards,
> Sumit Kumar
>
> On Tuesday, August 11, 2020 at 8:43:40 PM UTC+5:30 rr44r...@gmail.com
> wrote:
>
>> II
>>
>> تم الإرسال من هاتف Huawei الخاص بي
>>
>>
>>  الرسالة الأصلية 
>> من:‏ 'Dan Willemsen' via Android Building 
>> التاريخ:‏ الثلاثاء، ١١ آب، ٢٠٢٠ ١٢:٠٢ ص
>> إلى:‏ Android Building 
>> الموضوع:‏ Re: [android-building] Replacement for BUILD_BROKEN_PHONY and
>> phony-rebuild in android R
>>
>> but in my case this rebuilding is required .
>>
>>
>> I think this is where we're disconnected. Forcing rebuilds means that
>> incremental builds will nearly never be as fast as they should be, as the
>> entire tree starting from that phony would need to be rebuilt even if you
>> weren't touching anything related to the kernel. Instead, we'd much prefer
>> that the rule depended on what it uses, so it'll only be re-executed when
>> necessary. That list of dependencies may end up being a significant portion
>> of the kernel tree, but that's still better than every build.
>>
>> This also gets more important as we improve per-action sandboxing to get
>> better incremental builds and remote execution / cross-machine caching of
>> build actions. We're not there yet, but that's the direction we'd like to
>> be heading.
>>
>> - Dan
>>
>> On Wed, Jul 29, 2020 at 9:08 AM S

Re: [android-building] Replacement for BUILD_BROKEN_PHONY and phony-rebuild in android R

['Dan Willemsen' via Android Building]

>
> but in my case this rebuilding is required .
>

I think this is where we're disconnected. Forcing rebuilds means that
incremental builds will nearly never be as fast as they should be, as the
entire tree starting from that phony would need to be rebuilt even if you
weren't touching anything related to the kernel. Instead, we'd much prefer
that the rule depended on what it uses, so it'll only be re-executed when
necessary. That list of dependencies may end up being a significant portion
of the kernel tree, but that's still better than every build.

This also gets more important as we improve per-action sandboxing to get
better incremental builds and remote execution / cross-machine caching of
build actions. We're not there yet, but that's the direction we'd like to
be heading.

- Dan

On Wed, Jul 29, 2020 at 9:08 AM Sumit Kumar  wrote:

> hi all,
> i am trying to build android R but getting the following error in the
> kernel makefile
> *   kernel/exynos/AndroidKernel.mk:155: error: writing to readonly
> directory:
> "/data/home/sumkumar/work/workspace/R/out/../out/target/product/**/obj/KERNEL_OBJ/arch/arm64/boot/Image"*
> this was handled in Android Q by using the flag
> "BUILD_BROKEN_PHONY_TARGETS=true" but in R this is depreciated hence cannot
> use the same.
>
>after looking at following link given for phony rules changes from
> google for android R
>
> https://android.googlesource.com/platform/build/+/master/Changes.md#phony_targets
>
>   i have updated my Makefile as follows by removing the "../" in the
> erronous path and past the previous error ,
> *  #KERNEL_OUT ?= $(if $(filter /%
> ~%,$(TARGET_OUT_INTERMEDIATES)),,$(realpath
> $(OUT_DIR))/../)$(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ*
> *KERNEL_OUT ?= $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ*
>
>  but now i am getting errors with phony-rebuild as mentioned below
>   *kernel/exynos/AndroidKernel.mk:139: error: real file
> "out/target/product/**/obj/KERNEL_OBJ/.config" depends on PHONY target
> "phony-rebuild"*
> *14:21:04 ckati failed with: exit status 1*
>
>
>
>i understood as phony targets are always dirty hence every file will be
> rebuild which depends on that phony, but in my case this rebuilding is
> required .
>   Attaching a snap of the file depicting the same
>
> KERNEL_CONFIG := $(KERNEL_OUT)/.config
>
> KERNEL_CONFIG := $(KERNEL_OUT)/.config
>
>
>
> .PHONY: phony-rebuild
>
>
>
>
>
> $(KERNEL_CONFIG): phony-rebuild
>
>   $(show) echo "make $(KERNEL_DEFCONFIG)"
>
>   $(MAKE_CONFIG_CMD)
>   $(info  MAKE_CONFIG_CMD is $(MAKE_CONFIG_CMD))
>
>   Please let me know if there is any way to avoid using phony-rebuild and
> replace it with an alternate mechanism.
>
> Regards,
>
> --
> --
> 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/786689cd-9816-454d-ba1f-bead4944ce3fo%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/786689cd-9816-454d-ba1f-bead4944ce3fo%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdnNEArhZ-NoDSwrmmncaacN8WVFDeekUPYj%3DmUmk4rYiQ%40mail.gmail.com.

Re: [android-building] Add build tag from a blueprint

['Dan Willemsen' via Android Building]

Huh, I hadn't even realized that was customizable. In any case, we'd expect
global configuration like this to happen in the global/device configuration
part of the build (build/make/core/config.mk / product makefiles /
BoardConfig.mk, and things they include), not happen in Android.mk /
Android.bp files (which define things that may not even be used by the
current build). What's your use case for setting this in an Android.mk /
Android.bp file?

- Dan

On Mon, Aug 10, 2020 at 1:11 PM Simon Williams <
simondavidwilliam...@gmail.com> wrote:

> Using Android.mk, I'm able to add a new Build.TAG value by using
> BUILD_VERSION_TAGS += my-tag
>
> Is it possible to do this from an Android.bp soong BluePrint file?
>
> --
> --
> 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/eb6940ac-2a71-4b77-9a4d-eea3ac02d587n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/eb6940ac-2a71-4b77-9a4d-eea3ac02d587n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D6WK6XnuVq_u11m1axXjrbm6bf8Uk0%2Bi3L15r8rZGAbQ%40mail.gmail.com.

Re: [android-building] repo sync fails on the latest Ubuntu

['Dan Willemsen' via Android Building]

Can you file an issue at
https://bugs.chromium.org/p/gerrit/issues/entry?template=GoogleSource+Issue
?

Thanks

On Wed, Jul 1, 2020 at 2:38 PM Sasha Sirotkin 
wrote:

> Tried 10 times already
>
> On Wed, Jul 1, 2020, 22:25 Ljube Babunski  wrote:
>
>> Try again to sync.
>>>
>>> --
>> --
>> 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/CAKEATv_Ui6M4FLR17374NFG%2B2T3_tHPwCc9PHCj8C5dGbEc_Dw%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/CAJV9mPW-SFzG%3DqiOpepO1A4G3tcbtAz94YB5YR6%3DN9vZAU7wYA%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/CALQgHd%3DqZQ-fmgw15DF60_EOZyMb9SsrHBaF22WKn1Wf_HbThg%40mail.gmail.com.

Re: [android-building] Controlling clang-tidy during the builds

['Dan Willemsen' via Android Building]

`tidy: true` always runs clang-tidy. If you only want to run it on specific
builds, you can omit that property and instead set WITH_TIDY=true in your
environment. Unfortunately, that doesn't let you select which code to run
tidy on, it'll be run on anything that is built whenever that environment
variable is set.

- Dan

On Fri, Jun 19, 2020 at 8:29 AM 'Wesolowski, Krzysztof' via Android
Building  wrote:

> Hello,
>
> I have pretty big codebase, with most of BP modules specifying tidy: true.
>
> This codebase is then included in multiple product variants, and tidy
> checks are repeated numerous times for no good reason.
>
> Is there a ways to separate running tidy checks from actual build?
> Sth like:
> NO_TIDY=1 make flashfiles (called for 10 product variants)
> ONLY_TIDY=1 cd vendor/... && mma (validates common codebase clang tidy,
> would run on 11th machine)
>
> BR,
>
> Krzysztof Wesolowski
>
> --
> --
> 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/VI1P174MB00150A3D4ADDC5ABC91DE86B91980%40VI1P174MB0015.EURP174.PROD.OUTLOOK.COM
> <https://groups.google.com/d/msgid/android-building/VI1P174MB00150A3D4ADDC5ABC91DE86B91980%40VI1P174MB0015.EURP174.PROD.OUTLOOK.COM?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkBi0G76__wOcU2QfGyOpzfW2p5rdLhc8zgwpBPY2S83A%40mail.gmail.com.

Re: [android-building] android-9.0.0_r8 build error

['Dan Willemsen' via Android Building]

Did you sync to that from some other revision? The `repo` tool doesn't go
back and clean up "removed" / files when changing
manifests, so there's some number of dangling symlinks in your worktree. If
you remove the five files that it complains about, that's probably enough
to get it working.

- Dan

On Mon, Nov 9, 2020 at 8:13 AM Arthur Clark  wrote:

> this is output message:
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=9
> TARGET_PRODUCT=aosp_x86
> TARGET_BUILD_VARIANT=eng
> 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.4.0-42-generic-x86_64-Ubuntu-18.04.5-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PPR2.180905.006.A1
> OUT_DIR=out
> 
> [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
> FAILED: out/soong/.bootstrap/build.ninja
> out/soong/.minibootstrap/minibp -t -l out/.module_paths/Android.bp.list -b
> out/soong -n out -d out/soong/.bootstrap/build.ninja.d -o
> out/soong/.bootstrap/build.ninja Android.bp
> internal error: could not open symlink hardware/qcom/sdm845/Android.bp;
> its target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm8150p/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm7250/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm8150/Android.bp;
> its target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm7150/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> ninja: build stopped: subcommand failed.
> 16:32:42 soong minibootstrap failed with: exit status 1
>
>  failed to build some targets (4 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/d1c3b2ed-8460-4704-b98c-c6b3085cead4n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/d1c3b2ed-8460-4704-b98c-c6b3085cead4n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdk9Hkn6uDm4cQfZ9LHWLwO-Z3q5ERfLYSb4k6YE68VhLA%40mail.gmail.com.

Re: [android-building] Not able to build with OUT_DIR?

['Dan Willemsen' via Android Building]

This is definitely a bug, I uploaded a fix here:
https://android-review.googlesource.com/c/platform/build/soong/+/1489596

- Dan

On Thu, Nov 5, 2020 at 8:30 AM Yongqin Liu  wrote:

> Hi, All
>
> I want to build hikey960 with the default aosp tree with OUT_DIR specified,
> but I got following error reported:
>
> Starting ninja...
> FAILED: ninja: 'out/host/linux-x86/bin/bindgen', needed by
> '/data/android/aosp/pure-master/pure-master-out/soong/.intermediates/frameworks/native/libs/binder/rust/libbinder_ndk_bindgen/android_arm64_armv8-a_cortex-a73_source/
> bindings.rs', missing and no known rule to make it
> 13:08:47 ninja failed with: exit status 1
>
> If I do not have the OUT_DIR specified explicitly, then there is no
> problem reported.
>
> Anyone could please help to check if OUT_DIR is not supported or there is
> any issues with the bindgen module?
>
> --
> --
> 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/b15087b7-fb63-4e96-a3c8-c72092c1c3e2n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/b15087b7-fb63-4e96-a3c8-c72092c1c3e2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D%2B9CWPS_%2BsTV_HnEe4_UX0bmi7_Rgcs8gErY6bEAx-zw%40mail.gmail.com.

Re: [android-building] Re: Build problem

['Dan Willemsen' via Android Building]

If that doesn't work, try rebuilding the blob files, my understanding is
that they've been fixed.

Thanks,
Dan

On Tue, Jun 15, 2021 at 3:34 PM cptl...@gmail.com 
wrote:

> In vendor/qcom/redfin/proprietary/Android.mk:
>
> There are several lines that say:
> *LOCAL_NOTICE_FILE := $(LOCAL_PATH)/../COPYRIGHT $(LOCAL_PATH)/../LICENSE*
>
> Remove the  *$(LOCAL_PATH)/../COPYRIGHT* part.  Only the LICENSE file
> exists.
>
> On Tuesday, June 8, 2021 at 10:27:06 PM UTC-4 s41...@gmail.com wrote:
>
>> Where to get the COPYRIGHT document?
>> I want to build image for my Pixel 5 but always get error as below.
>>
>> error: ninja: 'vendor/qcom/redfin/COPYRIGHT', needed by
>> 'out/target/product/redfin/obj/NOTICE_FILES/src/system_ext/app/QtiTelephonyService/QtiTelephonyService.apk.txt',
>> missing and no known rule to make it
>>
>> Does anyone face this issue?
>>
> --
> --
> 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/95115842-5e59-4b81-9845-86cab2bb3b38n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/95115842-5e59-4b81-9845-86cab2bb3b38n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DszwBF4CgzEzNGFCs%2BuyuARaQrsJVSA7WNvhHV_2YAzw%40mail.gmail.com.

Re: [android-building] AOSP on aws a1 instance (arm)

['Dan Willemsen' via Android Building]

Building Android requires a x86-64 machine, it is not supported on arm. As
you've found, all of our prebuilt tools are x86-64, and I suspect there are
further issues even if you manage to replace them with arm equivalents, as
that hasn't been tested. There's limited support in Soong for Linux/arm64,
but that's for cross-compiling binaries for that configuration on an x86-64
system.

- Dan

On Tue, Jun 8, 2021 at 7:27 PM kkh  wrote:

> Hi,
>
> Anyone manage to build AOSP on arm host? After repo sync on
> android-11.0.0_r35, did the source envsetup.sh and lunch command, but it
> seem that the build tools is in x86.
>
> Error encountered
> */home/ubuntu/android/build/blueprint/microfactory/microfactory.bash: line
> 62: /home/ubuntu/android/prebuilts/go/linux-x86//bin/go: cannot execute
> binary file: Exec format error*
>
> *You're building on Linux*
>
> *Lunch menu... pick a combo:*
>
> *Which would you like? [aosp_arm-eng] *
> */home/ubuntu/android/build/blueprint/microfactory/microfactory.bash: line
> 62: /home/ubuntu/android/prebuilts/go/linux-x86//bin/go: cannot execute
> binary file: Exec format error*
>
> --
> --
> 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/19e0f12e-d416-4ac5-83ec-0a89afae7fb6n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/19e0f12e-d416-4ac5-83ec-0a89afae7fb6n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdn6uwJM9QZcjndOb3W_YJCjxxrW_CR9Ug1Mn_SVXitnNQ%40mail.gmail.com.

Re: [android-building] ABI update Failed

['Dan Willemsen' via Android Building]

I'd recommend contacting your source code provider about that build issue,
as that doesn't appear to be AOSP, and the AOSP-based targets don't seem to
work in that source tree.

In general, the idea behind API/ABI stability is that it's stable across
Android releases, so it's not something that can just be changed in a
version that has already been released. If you intended to make changes to
the radio ABI, you'd need to work with one or more of AOSP/Google/your
source provider to add any newly required APIs into a new version of that
API (in which case someone would be running those commands in an AOSP tree,
where they would work).

If you didn't make changes to the ABI, you'd want to debug that issue
further rather than attempting to update the ABI to fix your build issue.

- Dan

On Tue, Jun 22, 2021 at 10:09 PM figs개발자  wrote:

> Hi All
>
> i have a problem with the ABI update.
>
> i changed the android.hardware.radio@1.0
> So, i'm getting an error when building aosp.
>
> FAILED:
> out/soong/.intermediates/hardware/interfaces/radio/1.0/android.hardware.radio@1.0
> /android_arm64_armv8-a_vendor_shared/android.hardware.ra...@1.0.so.abidiff
> (prebuilts/clang-tools/linux-x86/bin/header-abi-diff
> -allow-unreferenced-changes -allow-unreferenced-elf-symbol-changes -lib
> android.hardware.radio@1.0 -arch arm64 -o
> 'out/soong/.intermediates/hardware/interfaces/radio/1.0/android.hardware.radio@1.0
> /android_arm64_armv8-a_vendor_shared/android.hardware.ra...@1.0.so.abidiff'
> -new
> 'out/soong/.intermediates/hardware/interfaces/radio/1.0/android.hardware.radio@1.0
> /android_arm64_armv8-a_vendor_shared/android.hardware.ra...@1.0.so.lsdump'
> -old
> prebuilts/abi-dumps/vndk/29/64/arm64_armv8-a/source-based/android.hardware.ra...@1.0.so.lsdump)||
> (echo 'error: Please update ABI references with:
> $ANDROID_BUILD_TOP/development/vndk/tools/header-checker/utils/create_reference_dumps.py
> -l android.hardware.radio@1.0' && (mkdir -p $DIST_DIR/abidiffs && cp
> 'out/soong/.intermediates/hardware/interfaces/radio/1.0/android.hardware.radio@1.0
> /android_arm64_armv8-a_vendor_shared/android.hardware.ra...@1.0.so.abidiff'
> $DIST_DIR/abidiffs/) && exit 1)
> **
> error: VNDK library: android.hardware.radio@1.0's ABI has INCOMPATIBLE
> CHANGES Please check compatibility report at:
> out/soong/.intermediates/hardware/interfaces/radio/1.0/android.hardware.radio@1.0
> /android_arm64_armv8-a_vendor_shared/android.hardware.ra...@1.0.so.abidiff
> **
> error: Please update ABI references with:
> $ANDROID_BUILD_TOP/development/vndk/tools/header-checker/utils/create_reference_dumps.py
> -l android.hardware.radio@1.0
>
> i watched the document (
> https://source.android.com/devices/architecture/vndk/abi-stability?hl=en )
> i attempted to update ABI.
> /development/vndk/tools/header-checker/utils/create_reference_dumps.py  -l
> android.hardware.radio@1.0
>
> FAILED]
> making libs for aosp_arm_ab-userdebug
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=aosp_arm_ab
> TARGET_BUILD_VARIANT=userdebug
> 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-142-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=QKQ1.201109.002
> OUT_DIR=out
> 
> [100% 773/773] 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
> Clang SA is not enabled
> error: external/nos/host/generic/citadel/updater/Android.bp:17:1:
> "citadel_updater" depends on undefined module "libnos_citadeld_proxy"
> 15:34:56 soong bootstrap failed with: exit status 1
> Traceback (most recent call last):
>   File
> "./development/vndk/tools/header-checker/utils/create_reference_dumps.py",
> line 254, in 
> main()
>   File
> "./development/vndk/tools/header-checker/utils/create_reference_dumps.py",
> line 245, in main
> num_processed =
> create_source_abi_reference_dumps_for_all_products(args)
>   File
> "./development/vndk/tools/header-checker/utils/create_reference_dumps.py",
> line 199, in create_source_abi_reference_dumps_for_all_products
>

Re: [android-building] Re: Including Library in AOSP/frameworks/base/core

['Dan Willemsen' via Android Building]

>
> *AOSP/build/make/core/tasks/check_boot_jars/package_allowed_list.txt*


Be careful if you're planning on being compatible with the CDD
<https://source.android.com/compatibility/cdd.html>, particularly section
3.6
<https://source.android.com/compatibility/android-cdd#3_6_api_namespaces>.
Adding new classes to the bootclasspath can cause compatibility issues with
apps, which is why that check exists (and is your subsequent problem).

One method mentioned in the CDD to work around this is to add your new
packages to a separate library that apps can opt into. That doesn't really
work if you're using it in modified framework classes that get loaded into
every app though. There's one example with bouncycastle that gets repackaged
<https://cs.android.com/android/platform/superproject/+/master:external/bouncycastle/Android.bp;drc=f8a7462f1d6d713c4fa611e5f3be8d90ad287df0;l=116>
to be inside a different namespace in order to not conflict with apps. That
may be possible with jarjar <https://github.com/google/jarjar> too (which
the build system has support for), I'm not sure what the scripts
<https://cs.android.com/android/platform/superproject/+/master:external/bouncycastle/srcgen_platform/generate_android_src.sh>
used
for bouncycastle are doing differently.

- Dan

On Tue, Jun 22, 2021 at 10:10 PM Yolo Pucky  wrote:

> So I actually got a solution to my problem mentioned on 09.06.2021.
> However, I have another problem now, that is closely related to the
> aforementioned.
>
>
> ---
> BEGINNING OF SOLUTION
>
> ---
> First here is my solution to my problem from 09.06.2021:
> The blueprint in *AOSP/prebuilts/misc/common/gson/Android.bp *remains.
>
> *AOSP/frameworks/base/Android.bp*
> *...*
> java_library {
> name: "framework-minus-apex",
> ...
> libs: [
> "framework-updatable-stubs-module_libs_api",
> "gson",
> ],
> static_libs: [
> // If MimeMap ever becomes its own APEX, then this dependency would need
> to be removed
> // in favor of an API stubs dependency in java_library "framework" below.
> "mimemap",
> "gson",
> ],
> ...
> }
> ...
>
> *AOSP/build/make/core/tasks/check_boot_jars/package_allowed_list.txt*
> # Boot jar package name allowed list.
> # Each line is interpreted as a regular expression.
> ...
> com\.google\.gson\..*
> com\.google\.gson.*
> ...
>
> ---
> END OF SOLUTION
>
> ---
>
>
> ---
> BEGINNING OF SUBSEQUENT PROBLEM
>
> ---
> First, note that I exchanged the Gson library with the Jackson library by
> now.
> Building custom Android and using the Jackson library is no problem
> anymore. Though I only want to use the library within the AOSP i.e. I do
> not want third-party apps installed on my custom Android to see those
> libraries.
> The way I include the library leads to the problem that third-party apps
> that import classes or methods from these libraries will always try to
> import them from the Android library instead of the library the apps bring
> themselves.
> Since the library I include within my custom Android might differ from the
> library brought by the third-party apps, it does not necessarily contain
> all required classes or methods for those apps. Subsequently, these apps
> break:
> *// Caused by: java.lang.NoSuchMethodError: No interface method
> getterVisibility()LX/15g; in class
> Lcom/fasterxml/jackson/annotation/JsonAutoDetect; or its super classes
> (declaration of 'com.fasterxml.jackson.annotation.JsonAutoDetect' appears
> in /system/framework/framework.jar!classes4.dex)*
>
> How can I make my included library within the framework.jar only visible
> to AOSP internals?
>
>
>
>
> *---END
> OF SUBSEQUENT
> PROBLEM-

Re: [android-building] Build error for target db845c-userdebug

['Dan Willemsen' via Android Building]

That doesn't actually look like the error -- there should be a line
starting with `FAILED:` earlier in your console. You can always look at the
dedicated error log after the build too, in out/error.log, which should
only contain errors (not other build output that finished after the error).

- Dan

On Tue, Jun 22, 2021 at 10:11 PM Prabhakar Lad 
wrote:

> Hi All,
>
> I am trying to build the master branch for target db845c-userdebug, at
> around 90% I see the below build errors:
>
> [ 90% 97817/107707] //bionic/libm:libm.ndk abidw
> out/soong/.intermediates/bionic/libm/libm/android_arm_armv8-2a_kryo385_shared/unstripped/libm.
> no declaration found for ELF symbol acoshl
> no declaration found for ELF symbol acosl
> no declaration found for ELF symbol asinhl
> no declaration found for ELF symbol asinl
> no declaration found for ELF symbol atan2l
> no declaration found for ELF symbol atanhl
> no declaration found for ELF symbol atanl
> no declaration found for ELF symbol cacoshl
> no declaration found for ELF symbol cacosl
> no declaration found for ELF symbol casinhl
> no declaration found for ELF symbol casinl
> no declaration found for ELF symbol catanhl
> no declaration found for ELF symbol catanl
> no declaration found for ELF symbol cbrtl
> no declaration found for ELF symbol ceill
> no declaration found for ELF symbol clogl
> no declaration found for ELF symbol coshl
> no declaration found for ELF symbol cosl
> no declaration found for ELF symbol csqrtl
> no declaration found for ELF symbol erfcl
> no declaration found for ELF symbol erfl
> no declaration found for ELF symbol expm1l
> no declaration found for ELF symbol floor
> no declaration found for ELF symbol floorl
> no declaration found for ELF symbol fmal
> no declaration found for ELF symbol frexpl
> no declaration found for ELF symbol hypotl
> no declaration found for ELF symbol ldexpf
> no declaration found for ELF symbol ldexpl
> no declaration found for ELF symbol lgammal
> no declaration found for ELF symbol lgammal_r
> no declaration found for ELF symbol log10l
> no declaration found for ELF symbol log1pl
> no declaration found for ELF symbol logbl
> no declaration found for ELF symbol nanl
> no declaration found for ELF symbol nextafterl
> no declaration found for ELF symbol nexttoward
> no declaration found for ELF symbol nexttowardl
> no declaration found for ELF symbol remainderl
> no declaration found for ELF symbol remquol
> no declaration found for ELF symbol rintl
> no declaration found for ELF symbol scalbnl
> no declaration found for ELF symbol sinhl
> no declaration found for ELF symbol sinl
> no declaration found for ELF symbol sqrt
> no declaration found for ELF symbol sqrtf
> no declaration found for ELF symbol sqrtl
> no declaration found for ELF symbol tanhl
> no declaration found for ELF symbol tanl
> no declaration found for ELF symbol truncl
> 18:07:10 ninja failed with: exit status 137
>
>  failed to build some targets (04:58:40 (hh:mm:ss)) 
>
> My host platform is ubntu20.04.
>
> Has anyone faced similar  issue or any pointers on this would be helpful.
>
> Cheers,
> Prabhakar
>
> --
> --
> 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/e303dccd-e520-480b-adfc-c7acad4475bbn%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/e303dccd-e520-480b-adfc-c7acad4475bbn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmUs-Q8c0SmR83DCutJVZgnke5qNQm8NpGr4Jszn5vJwQ%40mail.gmail.com.

Re: [android-building] clang++.real stack dump llvm when building nougat-86 android-x86

['Dan Willemsen' via Android Building]

The common reason that clang crashes come up on this mailing list is that
your system has run out of memory during the build -- you might want to
watch `top` during a build, or look at the kernel logs afterwards and see
if it was OOM-killed or crashed due to some other reason. Sometimes it's a
bug in clang too, but that's rarer (and with clang & code that old, not all
that useful to track down).

- Dan

On Tue, Jun 22, 2021 at 10:12 PM sazer kpla 
wrote:

> Android Building
>
> [  0% 13/29446] //external/llvm/lib/LTO:libLLVMLTO clang++ LTOModule.cpp
> FAILED:
> out/soong/.intermediates/external/llvm/lib/LTO/libLLVMLTO/android_x86_64_static_core/obj/external/llvm/lib/LTO/LTOModule.o
> PWD=/proc/self/cwd
> prebuilts/clang/host/linux-x86/clang-4053586/bin/clang++ -c
> -Iexternal/llvm/lib/LTO  -fno-exceptions -Wno-multichar -O2
> -Wa,--noexecstack -Werror=format-security -D_FORTIFY_SOURCE=2
> -Wstrict-aliasing=2 -ffunction-sections -fno-short-enums -fstrict-aliasing
> -funwind-tables -fstack-protector-strong -no-canonical-prefixes
> -Werror=pointer-to-int-cast -Werror=int-to-pointer-cast
> -Werror=implicit-function-declaration -O2 -g -fno-strict-aliasing -DANDROID
> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
> -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd=
> -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion
> -Wno-reserved-id-macro -Wno-format-pedantic
> -Wno-unused-command-line-argument -fcolor-diagnostics
> -Wno-expansion-to-defined -fdebug-prefix-map=$PWD/= -Werror=return-type
> -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point
> -Werror=date-time -nostdlibinc -m64 -march=x86-64 -DUSE_SSSE3 -mssse3
> -msse4 -msse4.1 -msse4.2 -mpopcnt -Iexternal/llvm/include
> -Iexternal/llvm/device/include
> -Iout/soong/.intermediates/external/llvm/llvm-gen-attributes/gen
> -Iout/soong/.intermediates/external/llvm/llvm-gen-intrinsics/gen
> -Iexternal/libcxx/include -Iexternal/libcxxabi/include
> -Isystem/core/include -Isystem/media/audio/include
> -Ihardware/libhardware/include -Ihardware/libhardware_legacy/include
> -Ihardware/ril/include -Ilibnativehelper/include
> -Iframeworks/native/include -Iframeworks/native/opengl/include
> -Iframeworks/av/include -isystem bionic/libc/arch-x86_64/include -isystem
> bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem
> bionic/libc/kernel/uapi/asm-x86 -isystem bionic/libc/kernel/android/scsi
> -isystem bionic/libc/kernel/android/uapi
> -Ilibnativehelper/include_deprecated -D_GNU_SOURCE -D__STDC_LIMIT_MACROS
> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -fomit-frame-pointer -Wall
> -W -Wno-sign-compare -Wno-unused-parameter -Wno-missing-field-initializers
> -Wwrite-strings -Werror -Dsprintf=sprintf -Wno-error=unused-lambda-capture
> -Wno-error=user-defined-warnings -target x86_64-linux-android
> -Bprebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/x86_64-linux-android/bin
> -fPIC -D_USING_LIBCXX -std=gnu++14 -Wsign-promo
> -Wno-inconsistent-missing-override -Wno-null-dereference
> -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS -Wno-thread-safety-negative
> -Wno-sign-promo -std=c++11 -Woverloaded-virtual -fno-rtti
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast
> -Werror=address-of-temporary -Werror=return-type -MD -MF
> out/soong/.intermediates/external/llvm/lib/LTO/libLLVMLTO/android_x86_64_static_core/obj/external/llvm/lib/LTO/LTOModule.o.d
> -o
> out/soong/.intermediates/external/llvm/lib/LTO/libLLVMLTO/android_x86_64_static_core/obj/external/llvm/lib/LTO/LTOModule.o
> external/llvm/lib/LTO/LTOModule.cpp
> clang++.real: error: unable to execute command: Bus error
> clang++.real: error: clang frontend command failed due to signal (use -v
> to see invocation)
> Android clang version 5.0.300080  (based on LLVM 5.0.300080)
> Target: x86_64--linux-android
> Thread model: posix
> InstalledDir: prebuilts/clang/host/linux-x86/clang-4053586/bin
> clang++.real: note: diagnostic msg: PLEASE submit a bug report to
> http://llvm.org/bugs/ and include the crash backtrace, preprocessed
> source, and associated run script.
> clang++.real: error: unable to execute command: Bus error
> clang++.real: note: diagnostic msg: Error generating preprocessed
> source(s).
> [  0% 20/29446] //external/llvm/lib/Transforms/IPO:libLLVMipo clang++
> SampleProfile.cpp
> ninja: build stopped: subcommand failed.
> 21:30:12 ninja failed with: exit status 1
> any idea ?
>
> --
> --
> 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
> h

Re: [android-building] How to fix or avoid “Android.mk: error: ”libxyz (native:vendor) can not link against libgui.vendor (native:vndk_private)"?

['Dan Willemsen' via Android Building]

vndk_private libraries are not part of the stable ABI provided to /vendor
code, so they're not safe to link against, as it's possible for a VNDK
update to be installed without recompiling your vendor code. They still
have ".vendor" versions because they're used in the implementations of
other VNDK libraries that are exposed to /vendor code.

- Dan

On Tue, Jun 22, 2021 at 10:10 PM Vitaly Bortz  wrote:

> Hi all,
> Is there a modifiable condition[s]/rule[s] which I could change to allow
> linking between two given libraries types and prevent the "can not link
> against" error to appear?
>
> Thanks in advance,
> Vitaly
>
> P.S. posted initially a question about this error on stackoverflow
> <https://stackoverflow.com/questions/67983413/how-to-fix-or-avoid-android-mk-error-libxyz-nativevendor-can-not-link-aga>,
> but in 3 days got 0 answers :- (
>
> --
> --
> 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/d220b717-30e6-43de-8fe4-c16999f5fad0n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/d220b717-30e6-43de-8fe4-c16999f5fad0n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkrXeQPyWnL%2BRF-Za6u-amxUrxCm0LLaaW9Hviysc2UwA%40mail.gmail.com.

Re: [android-building] how to distribute android 10/11 ?

['Dan Willemsen' via Android Building]

>
> While I understand goma support is being deprecated/removed on AOSP
> master, is there a way to still be able to use Goma on Android 12 since I
> already have a goma client and server setup to work with Android 10.
>

No, it was removed before Android 12 was branched, so it's not in Android
12 either. You could always attempt to revert those removals in your own
tree, but I don't know how complex that could be. RBE works with
significantly more of the build actions than GOMA ever did.

- Dan

On Fri, May 14, 2021 at 3:37 PM Ruben Wu  wrote:

> Hi Dan,
> While I understand goma support is being deprecated/removed on AOSP
> master, is there a way to still be able to use Goma on Android 12 since I
> already have a goma client and server setup to work with Android 10.
>
> Best,
> Ruben
>
> On Tuesday, February 16, 2021 at 4:14:19 PM UTC-6 Dan Willemsen wrote:
>
>> GOMA support has been removed on the AOSP master branch, and has been
>> replaced with RBE.
>>
>> - Dan
>>
>> On Wed, Feb 3, 2021 at 9:30 AM 唐木村  wrote:
>>
>>> @Dan Willemsen
>>>
>>> >>> The build team does not recommend using Goma -- it does not work
>>> particularly well with the Android build, and we expect to be removing
>>> support for it in master in the coming months (support will most likely
>>> still be in this years release, but not next years).
>>>
>>> whether goma not work well for android build ??? and now 2021 year
>>> support better ???
>>> https://chromium.googlesource.com/infra/goma/client/
>>> https://chromium.googlesource.com/infra/goma/server/
>>>
>>> 在2020年3月4日星期三 UTC+8 上午5:57:32 写道：
>>>
>>>> The build team does not recommend using Goma -- it does not work
>>>> particularly well with the Android build, and we expect to be removing
>>>> support for it in master in the coming months (support will most likely
>>>> still be in this years release, but not next years).
>>>>
>>>> RBE is the replacement, but it's still evolving at the moment. Many of
>>>> our CI builds have switched to it (they never used Goma), but only a
>>>> handful of developers have used it so far. If you're interested in this,
>>>> I'd highly recommend asking your TAM about it (or if you don't have one,
>>>> contact me and I can try to route your request to the right team).
>>>>
>>>> For what we're doing (other than Goma/RBE), the majority of our CI
>>>> builds are done on n1-standard-64
>>>> <https://cloud.google.com/compute/docs/machine-types#n1_machine_type>
>>>> machines with SSD persistent disks. Depending on your
>>>> limitations/requirements, the newer C2/N2 machine families may be more
>>>> efficient. For local developers, we're generally buying fast desktops -- 2x
>>>> Intel Xeon GOLD 6154 processor (18-core Skylake, up to 3.70 GHz) with 192
>>>> GB RAM and a few TB of SSDs.
>>>>
>>>> - Dan
>>>>
>>>> On Sun, Mar 1, 2020 at 11:52 PM 'Orion Hodson' via Android Building <
>>>> android-...@googlegroups.com> wrote:
>>>>
>>>>> Hi Alexander
>>>>>
>>>>> Internally Android developers use goma. The thread below has pointers
>>>>> to the client and server. It is built on GCP.
>>>>>
>>>>>
>>>>> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/eOtBzosZtd8
>>>>>
>>>>> Kind regards
>>>>> Orion
>>>>>
>>>>> On Sun, 1 Mar 2020 at 22:39, alexander zhu  wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I faced one problem, i have tried to solve it many days.
>>>>>>
>>>>>>
>>>>>> AOSP compile on one powerful physical server(36U128G) is fast .
>>>>>> Because my company has so many people need to compile AOSP on the 
>>>>>> server,so
>>>>>> it is busy all the time , and I do not have money to buy more.But the VM 
>>>>>> I
>>>>>> can request more.So I want to use VM on the cloud to compile AOSP.
>>>>>>
>>>>>> I have some distribute compile experiences in other c/c++ projects.
>>>>>> So I'm thinking is there any way to compile AOSP in distribute way?exp: 
>>>>>> use
>>>>>> many VMs for one AOSP build.
>>>>>>
>>>>>> I noticed there had

[android-building] Re: Platform development on MacOS isn't supported as of June 22, 2021.

['Dan Willemsen' via Android Building]

> -g default,tools

The "tools" group in the manifest is unrelated to building these SDK tools, 
so that shouldn't be necessary (though all of the "tools" grouped projects 
are also in "default" currently, so it really shouldn't change anything 
either).

> LOCAL_MULTILIB=64 USE_NINJA=false

LOCAL_MULTILIB doesn't do anything on the command line, and ninja has been 
the only way to build for several releases now, so you can drop these. Just 
`m aapt` should work fine.

> Running into error after error attempting a build leads me to believe I'm 
not doing this right.

I think I just fixed this particular error with 
https://android-review.googlesource.com/c/platform/build/+/1760965 this 
afternoon, so if you sync or cherry-pick that change, your command should 
work. Building the actual SDK zip files on AOSP is still broken, and I'm 
working on refactoring those so that you don't need to build a system image 
in order to build the platform/build-tools zips.

- Dan

On Thursday, July 8, 2021 at 2:47:43 PM UTC-7 connor.t...@gmail.com wrote:

> I saw this message - "*Important: Platform development on MacOS isn't 
> supported as of June 22, 2021.*" when attempting to pull down AOSP on 
> MacOS to build the platform/build tools.
>
> I set it up via:
>
> repo init -u https://android.googlesource.com/platform/manifest -b master 
> -g default,tools
> repo sync -c -j8
> source build/envsetup.sh
> lunch sdk-eng
> make LOCAL_MULTILIB=64 USE_NINJA=false aapt
>
> Is there an expected path of building just the tools (platform & build) 
> with that announcement? It is getting tougher and tougher to build these 
> platform/build tools on each release and not sure if I'm making something 
> more difficult than it should be.
>
> Running into error after error attempting a build leads me to believe I'm 
> not doing this right.
>
> FAILED: out/soong/build.ninja
> cd "$(dirname "out/soong/.bootstrap/bin/soong_build")" && 
> BUILDER="$PWD/$(basename "out/soong/.bootstrap/bin/soong_build")" && cd / 
> && env -i "$BUILDER" --top "$TOP" --out "out/soong" -n 
> "out" -d "out/soong/build.ninja.d" -t -l 
> out/.module_paths/Android.bp.list -globFile 
> out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja 
> --available_env out/soong/soong.environment.available --used_env 
> out/soong/soong.environment.used Android.bp
> error: system/bt/vendor_libs/test_vendor_lib/Android.bp:100:1: module 
> "test-vendor_test_host" variant "darwin_x86_64": depends on disabled module 
> "libbluetooth_headers"
> error: system/bt/vendor_libs/test_vendor_lib/Android.bp:100:1: module 
> "test-vendor_test_host" variant "darwin_x86_64": depends on disabled module 
> "libbt-rootcanal-types"
> error: system/bt/vendor_libs/test_vendor_lib/Android.bp:100:1: module 
> "test-vendor_test_host" variant "darwin_x86_64": depends on disabled module 
> "libbt-rootcanal"
> 05:49:56 soong bootstrap failed with: exit status 1
> ninja: build stopped: subcommand failed.
>

-- 
-- 
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/63bbf36e-6746-430d-8a8e-39983269a56cn%40googlegroups.com.

Re: [android-building] Missing "deployagent.inc" in standalone ADB build

['Dan Willemsen' via Android Building]

We've got a public code search site that can help find these:
https://cs.android.com/search?q=deployagent.inc==android%2Fplatform%2Fsuperproject
--
in this case, it's defined in packages/modules/adb/Android.bp.

- Dan

On Mon, Apr 26, 2021 at 9:07 AM Daniel Caruso  wrote:

> Hi all,
>
>  This is my first experience working with the AOSP. My goal is to
> build a standalone ADB1.0.41 binary that is cross-compiled for aarch32. To
> do this, I am first trying to build ADB for 64-bit ubuntu (and move on to
> the CC step after). Because of my tasks requirements, I need to get this
> source to build with automake and gcc/g++ instead of soong, so I am slowly
> creating my own makefile based on the contents of Android.bp in the
> system/core/adb directory.
>
>  I am at a point where my build fails for "deployagent.inc: No such
> file or directory" when trying to compile adb/client/fastdeploy.cpp. The
> comment in the code says "// Generated include via build rule." Running the
> linux "locate" command, I can find a DeployAgent.java file but nothing that
> looks like it can generate a .inc file.
>
>  Here is the relevant compiler output:
>
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> Compiler executable checksum: 435c9a72f92ce04eba08a47828fa63c4
> In file included from ./adb_trace.h:20,
>  from ./adb.h:28,
>  from ./client/commandline.h:22,
>  from ./client/fastdeploy.cpp:29:
> ../base/include/android-base/logging.h:454: warning: ignoring ‘#pragma
> clang diagnostic’ [-Wunknown-pragmas]
>   454 | #pragma clang diagnostic push
>   |
> ../base/include/android-base/logging.h:455: warning: ignoring ‘#pragma
> clang diagnostic’ [-Wunknown-pragmas]
>   455 | #pragma clang diagnostic ignored "-Wgcc-compat"
>   |
> ../base/include/android-base/logging.h:462: warning: ignoring ‘#pragma
> clang diagnostic’ [-Wunknown-pragmas]
>   462 | #pragma clang diagnostic pop
>   |
> ./client/fastdeploy.cpp:30:10: fatal error: deployagent.inc: No such file
> or directory
>30 | #include "deployagent.inc"// Generated include via build
> rule.
>   |  ^
> compilation terminated.
> Makefile:100: recipe for target '.build/fastdeploy.o' failed
> make: *** [.build/fastdeploy.o] Error 1
>
>
>  Where can I find this required file? Or alternatively, how can I
> generate this file? The code comment gives a hint that it is part of a
> build rule, but I am lost as to what rule, where, and what relevant files I
> need to generate it in my own makefile rules. If any other system
> output/context is needed let me know. Any help will be greatly appreciated!
>
> Thank you,
> Dan
>
> --
> --
> 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/0b5f06ec-1a58-493c-b47c-49595bee49bfn%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/0b5f06ec-1a58-493c-b47c-49595bee49bfn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkf3OYcTU7s%3DpWrEjOOOXVtqROtMLGZhpWx2ueZ86zQWA%40mail.gmail.com.

Re: [android-building] How to run AOSP module in a verbose mode?

['Dan Willemsen' via Android Building]

You can see a list of all the commands run in the out/verbose.log.gz file
after a build completes (at least on modern builds -- for older builds
specify `showcommands` on the command line)

- Dan

On Wed, Mar 3, 2021 at 3:06 PM anands...@gmail.com 
wrote:

> Hi All,
>
>   I am debugging one AOSP module and would like to enable verbose mode
> when I fire 'mmm' . Is there a way to do it? I am interested in knowing
> which step/command copy over a specific .apk to a folder.
>
> Thanks,
> Anand
>
> --
> --
> 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/e1eb1f5b-2925-429c-83f6-fb0a8ed966e6n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/e1eb1f5b-2925-429c-83f6-fb0a8ed966e6n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmE5R6Zz54Saa4xYygetrYkQxm3ybB_eb7V3O2KMn1W%2Bg%40mail.gmail.com.

Re: [android-building] How to avoid soong_build run in every build

['Dan Willemsen' via Android Building]

>
> Clang SA is not enabled
>

This isn't an AOSP tree.

My guess is that either an Android.bp, environment variable, or other
file/directory soong_build reads is changing every build, but since you
have some custom changes to the build system, I can't say for certain. You
can check out/soong.log and compare timestamps of the files in
out/soong/build.ninja.d to see what's triggering soong_build to run.

- Dan

On Mon, Apr 12, 2021 at 8:52 AM Mikael Björklund <
mikael.bjorkl...@vidhance.com> wrote:

> I have an AOSP tree were out/soong/.bootstrap/bin/soong_build
> out/soong/build.ninja always reruns, I have another AOSP tree were it only
> ran for the first build.
>
> I am on the limit when it comes to RAM so I need to close down all
> processes in order to have a chance for the build to pass:
> [100% 1770/1770] 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
> Clang SA is not enabled
> Killed
> 06:03:27 soong bootstrap failed with: exit status 1
> ninja: build stopped: subcommand failed.
>
>  failed to build some targets (01:08 (mm:ss)) 
>
> Is there a way to avoid this memory consuming step to run for every build?
>
> 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/62e9b15a-cb3d-45f3-b748-42493950016en%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/62e9b15a-cb3d-45f3-b748-42493950016en%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdn1aU6rzNC6RWQ%2BUMuNzomCu5mc0n9hFVn9aYCXEyDo3g%40mail.gmail.com.

Re: [android-building] [Help] clang error while building on Mac OS X El Capitan

['Dan Willemsen' via Android Building]

Oh, I forgot El Capitan is MacOSX 10.11, which is probably old enough to be
supported on that branch. But the MacOS 11.1 SDK shouldn't work on that,
and the screenshot claims that you're running 10.15.7 (Darwin 19.6.0). So
something doesn't line up here.

Regardless, the Linux VM is probably your best bet -- platform builds on
Mac aren't entirely full-featured anyways (close enough for most
development, but a handful of things can be missing).

- Dan

On Tue, Feb 16, 2021 at 2:07 PM Dan Willemsen  wrote:

> Older versions of Android don't build with newer versions of MacOS (the
> inverse works, you can build newer android versions with older MacOS
> versions, though that's not usually interesting except for CI servers)
>
> If you really need to build a 4+ year old android version on your Mac,
> then your best bet is probably to use a Linux virtual machine. That may be
> faster anyways.
>
> - Dan
>
> On Wed, Feb 3, 2021 at 9:30 AM Abhijeet Salunke 
> wrote:
>
>> I have setup my Mac OS X for building Android. I am able to execute
>> following commands
>> - source build/envsetup.sh
>> - lunch
>> But when I run "make" it gives me following error:
>>
>> *clang: error: invalid version number in '--mmacosx-version-min=11.1'*
>>
>> My configuration is as follows:
>> - Mac OS X El Capitan
>> - Xcode 12.4
>> - Mac OS X 11.1 SDK
>> - JDK 1.8
>>
>> I have been stuck on this issue for while can anyone help me with these.
>> I have also attached screenshot.
>>
>> This is my first time building a Android.
>>
>> --
>> --
>> 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/4fdeb00d-070b-41a3-bcc6-90b8c61b2151n%40googlegroups.com
>> <https://groups.google.com/d/msgid/android-building/4fdeb00d-070b-41a3-bcc6-90b8c61b2151n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
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/CALQgHdmvbh0uoXcBuoC3jwFbG%3Dt3goaipSpnqpsayfsW0jMrbQ%40mail.gmail.com.

Re: [android-building] how to distribute android 10/11 ?

['Dan Willemsen' via Android Building]

GOMA support has been removed on the AOSP master branch, and has been
replaced with RBE.

- Dan

On Wed, Feb 3, 2021 at 9:30 AM 唐木村  wrote:

> @Dan Willemsen
>
> >>> The build team does not recommend using Goma -- it does not work
> particularly well with the Android build, and we expect to be removing
> support for it in master in the coming months (support will most likely
> still be in this years release, but not next years).
>
> whether goma not work well for android build ??? and now 2021 year support
> better ???
> https://chromium.googlesource.com/infra/goma/client/
> https://chromium.googlesource.com/infra/goma/server/
>
> 在2020年3月4日星期三 UTC+8 上午5:57:32 写道：
>
>> The build team does not recommend using Goma -- it does not work
>> particularly well with the Android build, and we expect to be removing
>> support for it in master in the coming months (support will most likely
>> still be in this years release, but not next years).
>>
>> RBE is the replacement, but it's still evolving at the moment. Many of
>> our CI builds have switched to it (they never used Goma), but only a
>> handful of developers have used it so far. If you're interested in this,
>> I'd highly recommend asking your TAM about it (or if you don't have one,
>> contact me and I can try to route your request to the right team).
>>
>> For what we're doing (other than Goma/RBE), the majority of our CI builds
>> are done on n1-standard-64
>> <https://cloud.google.com/compute/docs/machine-types#n1_machine_type>
>> machines with SSD persistent disks. Depending on your
>> limitations/requirements, the newer C2/N2 machine families may be more
>> efficient. For local developers, we're generally buying fast desktops -- 2x
>> Intel Xeon GOLD 6154 processor (18-core Skylake, up to 3.70 GHz) with 192
>> GB RAM and a few TB of SSDs.
>>
>> - Dan
>>
>> On Sun, Mar 1, 2020 at 11:52 PM 'Orion Hodson' via Android Building <
>> android-...@googlegroups.com> wrote:
>>
>>> Hi Alexander
>>>
>>> Internally Android developers use goma. The thread below has pointers to
>>> the client and server. It is built on GCP.
>>>
>>>
>>> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/eOtBzosZtd8
>>>
>>> Kind regards
>>> Orion
>>>
>>> On Sun, 1 Mar 2020 at 22:39, alexander zhu  wrote:
>>>
>>>> Hi,
>>>>
>>>> I faced one problem, i have tried to solve it many days.
>>>>
>>>>
>>>> AOSP compile on one powerful physical server(36U128G) is fast .
>>>> Because my company has so many people need to compile AOSP on the server,so
>>>> it is busy all the time , and I do not have money to buy more.But the VM I
>>>> can request more.So I want to use VM on the cloud to compile AOSP.
>>>>
>>>> I have some distribute compile experiences in other c/c++ projects. So
>>>> I'm thinking is there any way to compile AOSP in distribute way?exp: use
>>>> many VMs for one AOSP build.
>>>>
>>>> I noticed there had topic long time ago :
>>>> https://groups.google.com/forum/#!searchin/android-building/distcc%7Csort:date/android-building/_YJNwvq6FtY/EENyTx4Elk4J
>>>>
>>>> I tried distcc , but failed . AOSP switching to clang, but distcc
>>>> support clang not ok.
>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926884
>>>>
>>>>
>>>> So, I want to know ,AOSP in google , how to solve the long build time
>>>> ?use more powerful physical server? or you have your own distribute
>>>> compile solution?
>>>>
>>>> --
>>>> --
>>>> 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-buildi...@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-buildi...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/android-buildin

Re: [android-building] [Help] clang error while building on Mac OS X El Capitan

['Dan Willemsen' via Android Building]

Older versions of Android don't build with newer versions of MacOS (the
inverse works, you can build newer android versions with older MacOS
versions, though that's not usually interesting except for CI servers)

If you really need to build a 4+ year old android version on your Mac, then
your best bet is probably to use a Linux virtual machine. That may be
faster anyways.

- Dan

On Wed, Feb 3, 2021 at 9:30 AM Abhijeet Salunke 
wrote:

> I have setup my Mac OS X for building Android. I am able to execute
> following commands
> - source build/envsetup.sh
> - lunch
> But when I run "make" it gives me following error:
>
> *clang: error: invalid version number in '--mmacosx-version-min=11.1'*
>
> My configuration is as follows:
> - Mac OS X El Capitan
> - Xcode 12.4
> - Mac OS X 11.1 SDK
> - JDK 1.8
>
> I have been stuck on this issue for while can anyone help me with these. I
> have also attached screenshot.
>
> This is my first time building a Android.
>
> --
> --
> 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/4fdeb00d-070b-41a3-bcc6-90b8c61b2151n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/4fdeb00d-070b-41a3-bcc6-90b8c61b2151n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmmnDFLbFVB-eokPm6-12tXzsk1nFmpAuVqB4atN%2BGCGw%40mail.gmail.com.

Re: [android-building] Is there tool like androidmk to convert Android.bp to Android.mk?

['Dan Willemsen' via Android Building]

It would be simple enough to write one that handles a few use cases, but
no, I don't know of one. The Android.mk that ndk-build uses was never the
same format as the Android.mk used by the platform builds -- they just
happened to share some names (and both used make).

- Dan

On Wed, Feb 3, 2021 at 9:29 AM min chang 
wrote:

> I need to add Android.mk to AndroidStudio and use for ndk-build.
> It seems that ndk-build cannot read Android.bp.
>
> --
> --
> 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/e0f3482b-aa11-4598-b49d-3741141d9f10n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/e0f3482b-aa11-4598-b49d-3741141d9f10n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkXua5SmgaCWWjLWXcvTZBvk5Sd8Prr6FDUMiTRKymjTA%40mail.gmail.com.

Re: [android-building] Re: Soong build system install & use

['Dan Willemsen' via Android Building]

Soong is intended to build the Android Platform, so while it can build
"unbundled" apps in some contexts, that's only by downloading a large
portion of the android platform in order to do so. If you're just building
an Android application, it's more than likely not the right tool to use. If
you are trying a platform build, have you successfully downloaded the code
and built something without any changes?

- Dan

On Fri, Feb 19, 2021 at 9:16 AM Akshay Sakare  wrote:

> Hello,
> May be this document will help you
> https://android.googlesource.com/platform/build/soong/
>
>
> On Friday, February 19, 2021 at 9:08:37 PM UTC+5:30 Ankita Kulkarni wrote:
>
>>
>> Hello,
>> I am a newbie in Android & Soong build system. I want to build basic
>> HelloWorld example using Soong build system, referred following links
>>
>> https://android.googlesource.com/platform/build/soong/+/refs/heads/master/README.md
>>
>> https://source.android.com/setup/build .
>>
>> I am not able to understand how to install Soong & use it to build any
>> application.
>>
>> Could anyone please guide me on it?
>>
>> Thanks & Regards,
>> Ankita
>>
> --
> --
> 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/0db43b2f-d379-4a1f-ad8d-347c26654941n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/0db43b2f-d379-4a1f-ad8d-347c26654941n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DmzcncgFetVid_SVYjGsKKb1%3DpRLjXObfPi4%3DhwnW2ZA%40mail.gmail.com.

Re: [android-building] build android q version on ubuntu 18.04 all cpu at low priority

['Dan Willemsen' via Android Building]

Is there a specific use case where you need the nice value increased?
Realize that we're also running in SCHED_BATCH mode, which also affects how
the processes are scheduled. We didn't really see any build time changes
when we switched this, only an increase in interactivity when using the
desktop while building a build.

If you did want to change this, it looks like we'd need to upgrade our
nsjail prebuilt (with this change
<https://github.com/google/nsjail/commit/494a5f63cdbb91565e8233133c345280687bd451>),
then you could add "--nice_value", "0", to the argument list here
<https://cs.android.com/android/platform/superproject/+/master:build/soong/ui/build/sandbox_linux.go;drc=0506361a60215defc5098a6253fdc8f51371ce88;l=158>
.

- Dan

On Wed, Aug 18, 2021 at 10:40 AM Longping Tang 
wrote:

> Hi  Dan
> I want to increase priority when building aosp.  How can I increase ni
> value to 0？
> On Monday, October 12, 2020 at 11:27:27 PM UTC+8 mmh19...@gmail.com wrote:
>
>> Thank you very much.
>>
>> 在2020年4月8日星期三 UTC+8 上午12:52:26 写道：
>>
>>> Yes, one byproduct of the nsjail sandboxing that we use is to switch up
>>> the scheduling groups. In our testing, this did not change the performance
>>> of the build.
>>>
>>> It did help the interactiveness (ssh, desktop w/mouse+keyboard, etc) of
>>> the machine while the build was running. It's still not perfect, but it's
>>> an improvement (cgroups help the most, but are difficult for the build to
>>> set up).
>>>
>>> - Dan
>>>
>>> On Tue, Apr 7, 2020 at 9:42 AM Minghui Ma  wrote:
>>>
>>>>
>>>> hi all
>>>>
>>>>  when i build android q version on ubuntu 18.04 i found all cpu at low
>>>> priority, and the ni value is 19, PRI value is 39. like below picture. is
>>>> this normal???
>>>>
>>>>
>>>>
>>>>
>>>> [image: QQ拼音截图20200407142802.png]
>>>>
>>>> --
>>>> --
>>>> 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-buildi...@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-buildi...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/android-building/91a40872-46d8-4755-9419-06a039fbaccc%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/android-building/91a40872-46d8-4755-9419-06a039fbaccc%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> --
> --
> 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/d770a1b0-c026-4689-8d13-d818d327c56an%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/d770a1b0-c026-4689-8d13-d818d327c56an%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkMDh%3DTZiZLMxbyBnR1i201sozE-KM28%2B7H5b5tZAxDcg%40mail.gmail.com.

Re: [android-building] Creating Symbolic Links in the /vendor partition

['Dan Willemsen' via Android Building]

Ah, now I understand why I'm confused -- Android 12 (and main for the last
year+) doesn't allow you to use PRODUCT_COPY_FILES to install binaries and
libraries: docs
<https://android.googlesource.com/platform/build/+/master/Changes.md#build_broken_elf_prebuilt_product_copy_files>.
This lets us verify that all of the needed libraries will be installed,
among other checks. Instead, you should define a prebuilt in an Android.bp
and add the name to PRODUCT_PACKAGES. Example:

in your Android.bp:
cc_prebuilt_binary {
name: "my_binary",
vendor: true,
arch: {
arm64: {
 srcs: ["arm64/my_binary"]
},
},
shared_libs: ["libmylibrary"],
}

cc_prebuilt_library {
name: "libmylibrary",
vendor: true,
arch: {
arm64: {
srcs: ["arm64/libmylibrary.so"],
},
},
}

If they were built with the NDK, or use other libraries, you may need to
set `sdk_version: "30"` or `shared_libs: [...]` as appropriate.

Then to install symlinks like your original question, there is a `symlinks:
["foo"]` property, which if added to my_binary above, would install a
"/vendor/bin/foo -> /vendor/bin/my_binary" symlink whenever my_binary is
installed.

Then in your product makefile (no need to add libmylibrary, as it will get
installed as a dependency):
PRODUCT_PACKAGES += my_binary

- Dan

On Thu, Aug 26, 2021 at 10:49 AM Curt Schwaderer 
wrote:

> Hello - I'm building an Android 11 product and placed the application
> binaries and libraries in /vendor/bin and /vendor/lib. I also need to
> create a symbolic link in /vendor/lib  to one of the library files also in
> /vendor/lib. If I try to do this in an init..rc file, it will not
> create the symbolic link because the /vendor partition is read only.
>
> I move the modules into /vendor/bin and /vendor/lib at build time using
> the COPY_FILES += macro in an aosp_.mk file, but I have not found
> a way to create a symbolic link in the makefile.
>
> How and when do I create symbolic links in the /vendor partition? Please
> provide an example if possible.
>
> Thanks!
> Curt
>
> --
> --
> 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/4a4400a8-2653-48c3-ad52-ba9470879304n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/4a4400a8-2653-48c3-ad52-ba9470879304n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DuN4UGA1DtSw2FfJqJW7a2TBOBpYZ6ZyxQyCnpBumaAQ%40mail.gmail.com.

Re: [android-building] ninja error while upgrading external/v8 in Nougat due to Android.bp

['Dan Willemsen' via Android Building]

Android.bp (and the Soong build system in general) wasn't really supported
until Android-O, so an Android.bp will be ignored in Nougat. (There was
some prototype support in Nougat under a USE_SOONG flag, but I really doubt
that'll work for you)

- Dan

On Tue, Sep 14, 2021 at 4:19 PM Saurabh Banore 
wrote:

> Hello All,
>
> I am upgrading one of the Nougat libraries - external/v8 and I am facing
> the following error when I try to build the changes in external/v8 with the
> comand *mma*
>
> *ninja: error: unknown target 'MODULES-IN-external-v8', did you mean
> 'MODULES-IN-external-iw'?*
>
> The changes required for upgrading are replacing the Android.mk with
> Android.bp. When checked about error, I understood that the Android.bp from
> the external/v8 is not getting loaded. I have verified that the Android.bp
> in the top level directory contains:
>
> *optional_subdirs = [*
> *"external/*",*
> *]*
>
> Instead of *external/**, I also tried using *external/v8, external/v8/*  *but
> still the Android.bp won't get loaded.
>
> Is there anything else I am missing? Could anyone please provide any
> pointers on how to debug this further?
>
>
> --
> --
> 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/37d6d753-7a12-4457-b23f-ef97e2338276n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/37d6d753-7a12-4457-b23f-ef97e2338276n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D%2B66DK35ApBEtKKOvPg8%3DWx9GR%3DTquZrr%3DWS%3DQ7kqOFw%40mail.gmail.com.

Re: [android-building] Re: How to build AOSP with 8GB RAM

['Dan Willemsen' via Android Building]

>
> I hope AOSP will provide a way to disable the documentation build part of
> it. Can someone from Google help me out here..?
>

Unfortunately, the documentation part of the build also generates code
stubs and other information extracted from the code/docs (@hidden is a
javadoc tag, not an annotation / etc), so it cannot be disabled.

- Dan

On Tue, Jul 13, 2021 at 9:56 PM Ravishankar S 
wrote:

> This process given below (for the Droid documentation build) does not work
> for AOSP11 build! We have to use the method given below:
>
>
> https://forum.xda-developers.com/t/guide-how-to-build-android-11-with-low-ram.4298483/
>
> Thanks and Regards
> Ravishankar
>
> On Wednesday, June 9, 2021 at 7:55:13 AM UTC+5:30 Ravishankar S wrote:
>
>> I have completed by AOSP build on a 4 core 8GB machine with the following
>> specs:
>>
>> Ryzen 3 3300u, 1TB HDD, 8GB Dual channel RAM.
>> Usable is 5.81G when fully booted into Kubuntu 20.04 (no apps running)
>>
>> 1) FIrst enable the zram on you system and reboot: sudo apt install
>> zram-config.
>>
>> 2) Default swapfile size is 2G. Its barely sufficient for the initial
>> soong_ui phase.  Just scraped through. It should be increased to least 4GB.
>> If you have the swapfile on SSD or  can move it to an SSD then its even
>> better.
>>
>> (For sure this phase takes a lot of RAM (~12G) and lots of disk IO. It
>> will take more time than normal as there is lots of swapping)
>>
>> 3)  Still in case the soong_ui phase does not get through then you can
>> try to reduce  reduce the number of jobs say m -j3 or m -j2.
>>
>> 4) The next phase is just compilation and other stuff that is not RAM
>> intensive but mainly CPU and some Disk I/O. You can speed up this phase
>> slightly by using tmfs for the /tmp folder.
>>
>> 5) The last phase is the documentation where Java is used and for this no
>> amount of swap space will help and the system will crash for sure. We have
>> the use the solution provided here and restart the make with just 1 job (m
>> -j1)
>>
>>
>> https://stackoverflow.com/questions/60468693/java-outofmemoryerror-when-building-aosp-10/60474592#60474592
>>
>> export _JAVA_OPTIONS="-Xmx4g"
>>
>> You can try to use m-j2 but it seemed fast enough with m -j1 and less
>> pressure on RAM.
>>
>> Other resources are: 110GB disk space after checkout and 170GB after
>> build.
>>
>>
>>
>>
> --
> --
> 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/47a3f319-9572-4522-8b54-df45e0e8ac4cn%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/47a3f319-9572-4522-8b54-df45e0e8ac4cn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkmpJm54j87Xxg3sUaMsyfjNMYCtfSD5xnf%2BRQjz22Eog%40mail.gmail.com.

Re: [android-building] Error while building Android 12 for a signed image

['Dan Willemsen' via Android Building]

The *-sign-targetfile-* rule doesn't appear to be in AOSP, so this looks
like an issue in your custom make code. Switching to the
built sign_target_files_apks is definitely a good start.

out/.path should not have a working soong_zip, though it may be present --
the intention is to limit the available $PATH tools used in the build
exactly to prevent this sort of issue. For commands that aren't allowed, we
return an error and log its usage. Check the config
<https://cs.android.com/android/platform/superproject/+/master:build/soong/ui/build/paths/config.go;drc=bdbbfd53ecee2fd51a69cdd42b8c57b8b8732dab;l=76>
to see if someone has improperly added soong_zip to the allowlist in your
fork.

Rules within the build should be depending and calling the actual paths
instead (but that's not what releasetools is set up to do), or adjusting
PATH for their command, like when we call add_img_to_target_files here
<https://cs.android.com/android/platform/superproject/+/master:build/make/core/Makefile;drc=ab1d0dc36e2eb3b1945bdd402f1d3a22212652b8;l=5252>.
Make sure that there are dependencies to every tool used by the script if
you use that mechanism though, or you can get flaky builds.

I'd also question why you're [re]signing output in the build itself. Based
on the names in the command, it's to sign the targetfiles with a test key
that isn't caught by the CTS test that verifies that you're not shipping
with well-known keys. But signing automatically with insecure keys means
you're no longer getting that protection. It would be a better idea to mark
that as a known failure until you do the real testing on the release image
(especially since in this case it'll also complain about you running an
'eng' build).

- Dan

On Wed, Oct 13, 2021 at 12:20 AM Salini Venate 
wrote:

> Hi,
>
> I'm getting a build error while trying to generate the* Android-12 signed
> image* using sign_target_files_apks:
> Build details: building Android S for x86_64 on Intel celadon platform
>
>
> 1) The make file calls sign_target_files_apks from
> *build/tools/releasetools/sign_target_files_apks* but the build fails
> with below import error:
>
> *[ 99% 131551/131570] Package release:
> out/target/product/caas/caas-sign-targetfile-eng.svenate.zip*
> *FAILED: out/target/product/caas/caas-sign-targetfile-eng.svenate.zip*
> */bin/bash -c "build/tools/releasetools/sign_target_files_apks -o
> -d device/intel/build/testkeys/cts-release-test --key_mapping
> build/target/product/security/networkstack=device/intel/build/testkeys/cts-release-test/networkstack
>
>  
> out/target/product/caas/obj/PACKAGING/target_files_intermediates/caas-target_files-eng.svenate.zip
> out/target/product/caas/caas-sign-targetfile-eng.svenate.zip"*
> *Warning: releasetools script should be invoked as hermetic Python
> executable -- build and run `sign_target_files_apks` directly.*
> *Traceback (most recent call last):*
> *  File "build/tools/releasetools/sign_target_files_apks", line 160, in
> *
> *import add_img_to_target_files*
> *  File
> "/svenate/celadon_S/build/make/tools/releasetools/add_img_to_target_files.py",
> line 63, in *
> *import ota_metadata_pb2*
> *  File
> "/svenate/celadon_S/build/make/tools/releasetools/ota_metadata_pb2.py",
> line 7, in *
> *from google.protobuf import descriptor as _descriptor*
> *ImportError: No module named google.protobuf*
> *[ 99% 131552/131570] Package:
> out/target/product/caas/caas-img-eng.svenate.zip*
>
> command used:
> /bin/bash -c "build/tools/releasetools/sign_target_files_apks -o  -d
> device/intel/build/testkeys/cts-release-test --key_mapping
> build/target/product/security/networkstack=device/intel/build/testkeys/cts-release-test/networkstack
>
>  
> out/target/product/caas/obj/PACKAGING/target_files_intermediates/caas-target_files-eng.svenate.zip
> out/target/product/caas/caas-sign-targetfile-eng.svenate.zip"
>
> 2)  If I point sign_target_files_apks to
> *out/host/linux-x86/bin/sign_target_files_apks*, the above step succeeds
> in bash terminal, but fails when executed as part of build  with the error
> that it is not able to get soong_zip binary.
>
> * File
> "/svenate/S_staging/out/host/linux-x86/bin/sign_target_files_apks/apex_utils.py",
> line 519, in SignApex*
> *apex_utils.ApexInfoError: Failed to get type for
> /svenate/S_staging/out/soong/.temp/apex-container-hTH_qc.apex:*
> *Failed to run command '['apex_compression_tool', 'compress',
> '--apex_compression_tool_path',
> '/svenate/S_staging/out/host/linux-x86/bin:/svenate/S_staging/prebuilts/build-tools/path/linux-x86:/svenate/S_staging/out/.path',
> '--input', '/svenate/S_staging/out/soong/.temp/apex-container-Hr12d3.apex',
> '--output',
> '/svenate/S_staging/out/soong/.temp/apex-container

Re: [android-building] Android bootstrap fails with Golang panic

['Dan Willemsen' via Android Building]

It looks like this was an issue in "VSDK"-based trees that are using a
vendor snapshot, and was fixed in master (but not in Android 12):
https://android-review.googlesource.com/q/topic:vendor_snapshot-192647618

You can either try to cherry-pick that topic, or disable the VSDK.

- Dan

On Wed, Oct 6, 2021 at 2:03 PM 나수환  wrote:

> Hi all,
> I was eager to try android 12. So I synced android-12.0.0_r2 and tried
> building with my device tree. But it fails to bootstrap with long lines of
> Golang panic.
> Error Msg:  FAILED: out/soong/.bootstrap/bin/soong_build
> out/soong/build.ninja - Pastebin.com <https://pastebin.com/PEpzz9vK>
> The Blueprint (Android.bp) of the  libshim_sensorndkbridge:
>
> cc_library_shared {
> name: "libshim_sensorndkbridge",
> srcs: ["ASensorManager.cpp"],
> shared_libs: [
> "libsensorndkbridge",
> "libutils",
> "liblog",
> ],
> whole_static_libs: ["libbase"],
> header_libs: ["libbase_headers"],
> vendor: true,
> include_dirs: [
> "system/core/libutils/include",
> "frameworks/hardware/interfaces/sensorservice/libsensorndkbridge",
> ],
> }
> It will be great if someone can guide me what is the problem
>
> --
> --
> 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/a1a7f78a-9a63-4d52-8939-0207cfa3255bn%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/a1a7f78a-9a63-4d52-8939-0207cfa3255bn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdmM27ASMr8t%2BrjTGofa2TGYro67QNX4OoDFVy8PAitOpQ%40mail.gmail.com.

Re: [android-building] post install step for cc_binary

['Dan Willemsen' via Android Building]

No, the source tree should be considered read-only from within the build.
I'd suggest doing this as a wrapper around the build, rather than inside
the build. You can set up `dist` options so that `m ... dist` builds will
copy artifacts (and logs -- it's meant to be used on build servers) to
$DIST_DIR (defaults to out/dist/) after a build, but you'd still need
something wrapping the build to put them where you wanted, so that may or
may not simplify things.

- Dan

On Mon, Oct 4, 2021 at 12:13 PM Abhayadev S  wrote:

>
> Hi,
>
> I have a cc_binary module (name myBin) defined in in a/b/Android.bp which
> is building fine and installs the binary in to out//system/bin/myBin
>
> Now, every time the binary is built, i need to copy this binary in to
> another git repo project cloned in a/b/bins/ to keep the prebuilts
>
> so, is there post build/install options i can use inside the Android.bp ?
>
> regards,
> abhay
>
> --
> --
> 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/2edbc3a5-816e-4e12-8528-1cc0f0a7e841n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/2edbc3a5-816e-4e12-8528-1cc0f0a7e841n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdkEXCceMwd0iWNMieObQtrNXnyU8Sfs1jvPGYVmQp6ZHA%40mail.gmail.com.

Re: [android-building] cc_binary module name and binary name

['Dan Willemsen' via Android Building]

No, that's not possible, as the installation system still sets up the
install rules for every module, so that the user can request a module to be
installed even if it isn't in PRODUCT_PACKAGES.

Either have them named differently on the device, or use soong namespaces
<https://android.googlesource.com/platform/build/soong/+/master/README.md#namespaces>
and
the same module name(myBin) so that only one will ever be exported to Make
at a time, that can be chosen through PRODUCT_SOONG_NAMESPACES
(PRODUCT_PACKAGES would just have myBin in either case).

- Dan

On Mon, Oct 4, 2021 at 12:14 PM Abhayadev S  wrote:

> Hi,
>
> usually the name of the installed binary will be same as the module "name"
> but can we have 2 cc_binary modules defined to install a binary of same
> name but on a conditional PRODUCT_PACKAGES definition?
>
> like a/Android.bp will define cc_binary with name : mymodule and it shall
> install myBin
> and b/Android.bp will define cc_binary with name mymodule2 and it shall
> install myBin
> and this will be controlled by a conditional PRODUCT_PACKAGES definition
> PRODUCT_PACKAGES += mymodule  OR PRODUCT_PACKAGES += mymodule2
>
> this is the install a binary (with same name) from 2 partners but based on
> a build condition/rule.
>
> regards,
> abhay
>
>
>
> --
> --
> 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/697400b2-6362-430e-99f2-9e5bce018996n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/697400b2-6362-430e-99f2-9e5bce018996n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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/CALQgHdm%3D55ZQtZuOrrJKBm_0EbPSYUAfJEpN%2BLuHeg2SYEb1Ug%40mail.gmail.com.

Re: [android-building] Android envsetup.sh overrides pre-set TARGET_BUILD_TYPE env variable!

['Dan Willemsen' via Android Building]

We never really use anything other than TARGET_BUILD_TYPE=release -- in
AOSP changing that flag is effectively a no-op. TARGET_BUILD_VARIANT=eng or
runtime flags tend to control more debug-like features, but in general it's
problematic to turn on any sort of "debug" for everything in a build
(doesn't fit in the partitions, too slow on device, yet another
cross-cutting feature that isn't regularly tested, etc).

We also tend to avoid using `lunch` (or even envsetup.sh) at all for
automation -- it's only setting ~3 variables that the build actually uses (
TARGET_PRODUCT / TARGET_BUILD_VARIANT / TARGET_BUILD_APPS, plus
TARGET_BUILD_TYPE=release). So much of our automation just does:

build/soong/soong_ui.bash --make-mode TARGET_PRODUCT=my_product
TARGET_BUILD_VARIANT=userdebug droid dist 

Which is roughly equivalent to:

source build/envsetup.sh && lunch my_product-userdebug && m dist

- Dan

On Tue, Jan 4, 2022 at 2:41 PM Abhayadev S  wrote:

> Hi,
>
> I am using a master build script to trigger the android build and the
> master script does the following steps,
>
> *source build/envsetup.sh && lunch *
>
> Now in my master script i was planning to export the TARGET_BUILD_TYPE as
> debug or release according to my other options.
>
> Now I see that the  *build/envsetup.sh* is over-writing it by exporting
> TARGET_BUILD_TYPE always as *release *in the *lunch* function ! (ref:
> https://cs.android.com/android/platform/superproject/+/master:build/make/envsetup.sh;drc=6a012266a18cdf89d4e94a3ce7aa15a9c462a448;l=718
> )
>
> is this expected? its really blocking any possibilities for automation
> right?
>
> regards,
> abhay
>
> --
> --
> 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/1ef6ee61-9e47-4116-96c3-b64041461b03n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/1ef6ee61-9e47-4116-96c3-b64041461b03n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3D%3Dz_gubTvAOOq4b1mvXr%3D006EXuLZ_qsyaQvn0PH%2Bs_Q%40mail.gmail.com.

Re: [android-building] error.GitError: Cannot checkout platform/build/blueprint: Cannot initialize work tree for platform/build/blueprint

['Dan Willemsen' via Android Building]

It sounds like you're having some issues with git, or your
network/filesystem. There's not really enough information here to
understand what issue you're hitting. Some things that may help:

   - Which repo command you're running
   - What git version you're using (git --version)
   - More complete output from repo -- it may be useful to limit it down to
   just blueprint to start: `repo sync build/blueprint`

when I later try to set the mobile with "lunch aosp_walleye-eng" I do get
> the error message that the concerned blueprint could not be found.
>

Yeah, trying a build when the source is incomplete is unlikely to work very
well. build/blueprint is one of the earliest projects used during a build
(along with build/make and build/soong), so it's not surprising to see a
blueprint error if that didn't sync.

 I am almost certain that I found a Google page where it is was mentioned,
> that Google will no longer maintain the blueprint Git repository.
>

The standalone github project <https://github.com/google/blueprint> is no
longer maintained, but it is still actively used within Android
<https://android.googlesource.com/platform/build/blueprint/+log/master>.

- Dan

On Tue, Jan 4, 2022 at 2:40 PM Michael Herren 
wrote:

>
> Hello
>
> I hope I am correct here. Since some days I am trying to build an Android
> kernel for a Pixel 2 and Nexus 5X. But so far I constantly failed.
>
> I tried several times to download AOSP. I tried to download the master and
> I also tried to create a local mirror and to then download the master from
> the local mirror. I also tried to download the corresponding branch. But
> what ever I try I do get the message  error.GitError: Cannot checkout
> platform/build/blueprint: Cannot initialize work tree for
> platform/build/blueprint
>
> when I later try to set the mobile with "lunch aosp_walleye-eng" I do get
> the error message that the concerned blueprint could not be found.
>
> I am almost certain that I found a Google page where it is was mentioned,
> that Google will no longer maintain the blueprint Git repository.
>
> Can  anyone help
>
> Kind Regards
> 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/0184edc2-f91e-4e1f-a46e-6a111d0f7133n%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/0184edc2-f91e-4e1f-a46e-6a111d0f7133n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
-- 
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%3DOvtM99iZo%2BHFVAvJCaVBW20a27Y%3DF1c_Nzye0_fHXmA%40mail.gmail.com.