[android-building] "telephony-ext_intermediates/classes.jar', needed by" when building SlimRoms 8.1

[Dan]

Hey,
I'm trying to build SlimRoms for my Galaxy S7 (G930F) and I keep being 
greeted with this error, I've been searching for a couple of days and 
anything I come across appears to be outdated or not working, anyone know 
any fixes?

PasteBin of error: https://pastebin.com/6PyTmTYZ

Many thanks, 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.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: AOSP build failure for android-9.0.0_r16 (PQ1A.181105.017.A1)

[dan]

Thanks for the quick fix Bill! 

On Wednesday, November 7, 2018 at 11:58:20 AM UTC-8, Bill Yi wrote:
>
> A linkfile to create namespace for the sdm845 project is needed. We have 
> updated the manifest. Please try again.
>
> bill
>
> On Wednesday, November 7, 2018 at 6:31:48 AM UTC-8, d...@vittegleo.com 
> wrote:
>>
>> I'm bumping into build issues with the latest PQ1A.181105.017.A1 using 
>> branch android-9.0.0_r16. I'm using the default manifest 
>> .
>>  
>> Any ideas?
>>
>> [371/967] including hardware/marvell/bt/Android.mk ...
>> [372/967] including hardware/qcom/audio/Android.mk ...
>> [373/967] including hardware/qcom/bootctrl/Android.mk ...
>> [374/967] including hardware/qcom/bt/Android.mk ...
>> [375/967] including hardware/qcom/camera/Android.mk ...
>> [376/967] including hardware/qcom/data/ipacfg-mgr/Android.mk ...
>> [377/967] including hardware/qcom/display/Android.mk ...
>> build/make/core/base_rules.mk:260: error: hardware/qcom/display/msm8998/
>> include: MODULE.TARGET.HEADER_LIBRARIES.display_headers already defined 
>> by hardware/qcom/sdm845/display.
>> 00:59:12 ckati 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.
For more options, visit https://groups.google.com/d/optout.

[android-building] AOSP build failure for android-9.0.0_r16 (PQ1A.181105.017.A1)

[dan]

I'm bumping into build issues with the latest PQ1A.181105.017.A1 using 
branch android-9.0.0_r16. I'm using the default manifest 
.
 
Any ideas?

[371/967] including hardware/marvell/bt/Android.mk ...
[372/967] including hardware/qcom/audio/Android.mk ...
[373/967] including hardware/qcom/bootctrl/Android.mk ...
[374/967] including hardware/qcom/bt/Android.mk ...
[375/967] including hardware/qcom/camera/Android.mk ...
[376/967] including hardware/qcom/data/ipacfg-mgr/Android.mk ...
[377/967] including hardware/qcom/display/Android.mk ...
build/make/core/base_rules.mk:260: error: hardware/qcom/display/msm8998/
include: MODULE.TARGET.HEADER_LIBRARIES.display_headers already defined by 
hardware/qcom/sdm845/display.
00:59:12 ckati 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.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: Android 9.0.0 Pie QPR1 Released

[dan]

android-9.0.0_r21 does not appear to have device/google/crosshatch repos 
defined in platform_manifest like previous release android-9.0.0_r16: 
https://android.googlesource.com/platform/manifest/+/android-9.0.0_r16/default.xml#59.
 
Is there a reason for that? It looks like all the other Pixel devices are 
there.

On Monday, December 3, 2018 at 2:26:11 PM UTC-8, Bill Yi wrote:
>
> Android 9 Pie QPR1 source code is now available.  The following builds, 
> tags, and devices are supported:
>
>  - PQ1A.181205.002, android-9.0.0_r19, Pixel 2 XL (taimen), Pixel 2 
> (walleye)
>  - PQ1A.181205.006, android-9.0.0_r21, Pixel 3 XL (crosshatch), Pixel 3 
> (blueline)
>
> The corresponding factory images, ota images, and proprietary binaries are 
> available at
>https://developers.google.com/android/images
>https://developers.google.com/android/ota
>https://developers.google.com/android/drivers
>
> We have also pushed the corresponding kernel projects for the following 
> devices:
>
> Tag | Project | Branch
>  | Device
> android-9.0.0_r0.42 | kernel/msm  | 
> android-msm-wahoo-4.4-pie-qpr1 | Pixel 2 and Pixel 2 XL
> android-9.0.0_r0.43 | kernel/msm  | 
> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.43 | kernel/msm-extra| 
> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.43 | kernel/msm-modules/qca-wfi-host-cmn | 
> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.43 | kernel/msm-modules/qcacld   | 
> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.43 | kernel/msm-modules/wlan-fw-api  | 
> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>
> bill
>

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

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

[android-building] Re: Android 9.0.0 Pie QPR3 Released

[Dan Vittegleo]

The AOSP build numbers page (
https://source.android.com/setup/start/build-numbers) for this update 
incorrectly lists PQ2A.190605.003 instead of PQ3A.190605.003 for Pixel 3 XL 
(crosshatch), Pixel 3 (blueline), Pixel 2 XL (taimen), Pixel 2 (walleye), 
Pixel XL (marlin), Pixel (sailfish).

On Monday, June 3, 2019 at 3:00:39 PM UTC-7, Bill Yi wrote:
>
> Android 9.0.0 Pie QPR3 source code is now available. The following builds, 
> tags, and devices are supported:
>
>  - PQ3A.190605.003, android-9.0.0_r40, Pixel 3 XL (crosshatch), Pixel 3 
> (blueline), Pixel 2 XL (taimen), Pixel 2 (walleye), Pixel XL (marlin), 
> Pixel (sailfish)
>  - PQ3A.190605.004.A1, android-9.0.0_r41, Pixel 3 XL (crosshatch), Pixel 3 
> (blueline)
>  - PQ3B.190605.006, andriod-9.0.0_r42, Pixel 3a XL (bonito) and Pixel 3a 
> (sargo)
>
>
> The corresponding factory images, ota images, and proprietary binaries are 
> available at
>https://developers.google.com/android/images
>https://developers.google.com/android/ota
>https://developers.google.com/android/drivers
>
> We have also pushed the corresponding kernel projects for the following 
> devices:
>
> Tag | Project | Branch
>  | Device
> android-9.0.0_r0.91 | kernel/msm  | 
> android-msm-marlin-3.18-pie-qpr3   | Pixel XL, Pixel
> android-9.0.0_r0.92 | kernel/msm  | 
> android-msm-wahoo-4.4-pie-qpr3 | Pixel 2 XL, Pixel 2
> android-9.0.0_r0.93 | kernel/msm  | 
> android-msm-crosshatch-4.9-pie-qpr3| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.93 | kernel/msm-extra| 
> android-msm-crosshatch-4.9-pie-qpr3| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.93 | kernel/msm-modules/qca-wfi-host-cmn | 
> android-msm-crosshatch-4.9-pie-qpr3| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.93 | kernel/msm-modules/qcacld   | 
> android-msm-crosshatch-4.9-pie-qpr3| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.93 | kernel/msm-modules/wlan-fw-api  | 
> android-msm-crosshatch-4.9-pie-qpr3| Pixel 3 XL, Pixel 3
> android-9.0.0_r0.94 | kernel/msm  | 
> android-msm-bonito-4.9-pie-pie-qpr3-b  | Pixel 3a XL, Pixel 3a
> android-9.0.0_r0.94 | kernel/msm-extra| 
> android-msm-bonito-4.9-pie-pie-qpr3-b  | Pixel 3a XL, Pixel 3a
> android-9.0.0_r0.94 | kernel/msm-modules/qca-wfi-host-cmn | 
> android-msm-bonito-4.9-pie-pie-qpr3-b  | Pixel 3a XL, Pixel 3a
> android-9.0.0_r0.94 | kernel/msm-modules/qcacld   | 
> android-msm-bonito-4.9-pie-pie-qpr3-b  | Pixel 3a XL, Pixel 3a
> android-9.0.0_r0.94 | kernel/msm-modules/wlan-fw-api  | 
> android-msm-bonito-4.9-pie-pie-qpr3-b  | Pixel 3a XL, Pixel 3a
>
> bill
>
>

-- 
-- 
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/cde8af00-baa7-447a-a5db-16df4a7661c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Custom AVD system images for Android Studio

[Dan Devine]

Hello,

I'm trying to get my custom AVD image to show up in Android Studio's 
configured repositories.
My goal is to create a custom AVD image on a build server and distribute 
that image across a team of developers.

I'm following the instructions in the AOSP documentation here:  
https://source.android.com/setup/create/avd#sharing_avd_system_images_for_others_to_use_with_android_studio

My image builds successfully, and the output is in the correct directory.

As directed, I copied both "repo-sys-img.xml" and 
"sdk-repo-linux-system-images-eng.ddevine.zip" to the webroot on the build 
server, and verified that both are accessible.
I also edited the "repo-sys-img.xml" file to prepend the path within the 
webroot, but I did not add any scheme ("http://host/;) element.

This repo isn't visible when I added the URL to the "Custom Sites" within 
Android Studio.
When I enter an incorrect address, I get the 'red-meatball' indicating 
fail...none appears when I add the accessible path to this repo though.

Any insight into what might be happening?  This is a really slick 
distribution method, how do I make this system work?


Thanks, 
DD

-- 
-- 
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/ebee42bc-f874-4356-92f3-6052509c7bbeo%40googlegroups.com.

[android-building] Re: Custom AVD system images for Android Studio

[Dan Devine]

SOLVED

Figured this out and got it working...adding for anyone searching after me.

Based on experimentation, Android Studio appears to filter the 
 results based on the  flagsimply building a 
'linux' image on Ubuntu will not satisfy OS X users of Android Studio.

Android Studio appears to filter images based on the host-os, so users on 
OS X will not see an  where the sdk:host-os == linux.
Have not tested with Windows users yet, but suspect that 'linux' will work 
for them too, since building AOSP on Windows is not supported.

Also note that the  entry MUST include the full "scheme + host 
/path" pattern for the remote Android Studio to find the resource, not 
relative to the original path.
 

Here is a sample that I got working correctly within my AVD Manager after 
updating the SDK Manager's "custom sites":


http://www.w3.org/2001/XMLSchema-instance; 
xmlns:sdk="http://schemas.android.com/sdk/android/sys-img/3;>

(function(){EventTarget.prototype.ol_originalAddEventListener=
EventTarget.prototype.addEventListener,EventTarget.prototype.
addEventListener=function(t,e){var n=this,r=arguments.length>2&&void 0!==
arguments[2]&&arguments[2];this.ol_originalAddEventListener(t,e,r),"click"
===t&&setTimeout((function(){!window.OL_NOT_LOGIN_PAGE&&n.setAttribute&&n.
setAttribute("data-ol-has-click-handler","")}),0)}})("")


9
DDevine's Android Automotive OS SDK System Image

29
x86_64
android-automotive
DDevine's Android Automotive OS System Image



665282541

a3c4e334b61535f2f148e37036708452fc241f7f

http://foo.bar.org/auto_os/sdk-repo-darwin-system-images-eng.ddevine.zip

macosx


713895099

512c51020b3e6266274a12725cffe6bd7ebc9c87

http://foo.bar.org/auto_os/sdk-repo-linux-system-images-eng.ddevine.zip

linux





I followed the instructions for setting up an OS X disk image, mounting it 
and building here:  
https://source.android.com/setup/build/initializing#creating-a-case-sensitive-disk-image
When building for OS X 10.15, the 'sepolicy_tests' failed as outlined here: 
https://groups.google.com/forum/#!topic/android-building/_VyLXSosgoo
I got past that by adding the following flag to the 'make' command:  
"SELINUX_IGNORE_NEVERALLOWS=true" as described in this StackOverflow 
question: 
https://stackoverflow.com/questions/58763047/failed-sepolicy-check-android-10-building-pixel-3a-xl

Hope this helps somebody.
On android-10.0.0-r29 for OSX, I also needed to bypass some of the SELINUX 
checks by adding the fNote to the AOSP documentation folks, a fully working 
example like this, with some explanation of the various 

-- 
-- 
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/43645ad7-0905-4093-9dc6-124a8e62cb7do%40googlegroups.com.

Re: [android-building] Proper way to include STL in Android.mk in AOSP build system

['Dan Willemsen' via Android Building]

Which branch are you using? Newer branches (Marshmallow+) use LOCAL_CXX_STL
to chose a STL for non-NDK modules (LOCAL_NDK_STL_VARIANT for NDK modules).

In Lollipop, you could include external/libcxx/libcxx.mk for libc++

- Dan

On Fri, Jun 3, 2016 at 8:27 AM Michael Robbeloth <mrobbel...@gmail.com>
wrote:

> Anyone,
>
> I was wondering what is the proper way to include the STL in the
> Android.mk file when building under the AOSP build system and not in the
> NDK.  I know about libstlport in external, but it does not include all the
> classes needed in some cases (such as vector or chrono). 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Android.mk not copying to /system

['Dan Willemsen' via Android Building]

TARGET_ROOT_OUT_SBIN would put that executable in /root/sbin,
which is the root ramdisk, not the system partition. There isn't a
/system/sbin, we just put everything in /system/bin.

- Dan

On Sat, Feb 18, 2017 at 8:15 AM 'Ryan Philips' via Android Building <
android-building@googlegroups.com> wrote:

> Hi,
>
> I am trying to build a test source. I have created an external/mytest
> directory and the following in Android.mk
>
> include $(CLEAR_VARS)
> LOCAL_SRC_FILES := testextspi.c
> LOCAL_MODULE:= testextspi
> LOCAL_MODULE_PATH := $(TARGET_ROOT_OUT_SBIN)
> LOCAL_UNSTRIPPED_PATH := $(TARGET_ROOT_OUT_SBIN_UNSTRIPPED)
> include $(BUILD_EXECUTABLE)
>
>
> The problem is it builds and create obj files and creates the binary
> inside "./symbols/system/sbin/"
> But it does not create the same binary in /system/bin in the filesystem.
> which is /system/sbin/
>
> I am not sure what i am missing here..
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] How to build fastboot for windows from Android N

['Dan Willemsen' via Android Building]

You don't need to use USE_MINGW anymore, the build system understands how
to do host cross-compiles natively now. Just doing 'mma' in
system/core/fastboot will build both the linux and windows versions. You
could also use:

   m -j8 host_cross_fastboot

As the most similar command to what you were running.

- Dan

On Wed, Sep 14, 2016 at 2:29 PM Xiaofeng Lei <xiaofeng.lei...@gmail.com>
wrote:

> Hi all,
>
> Recently we moved to Android N from M, and I'm working on poring some
> customized features to fastboot project. When I'm trying to build fastboot
> utility for Windows with the command "make -j8 fastboot USE_MINGW=1", it
> still generates the binary for Linux:
>
> Starting build with ninja
> ninja: Entering directory `.'
> [100% 17/17] Install: out/host/linux-x86/bin/fastboot
>
>  make completed successfully (30 seconds) 
>
> Does anyone know how to generate "fastboot" utility?
>
> Thanks,
> Stanley
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] problems build android-7.0.0_r1 with gcc

['Dan Willemsen' via Android Building]

Try removing `USE_CLANG_PLATFORM_BUILD := false` so that you're building
with Clang instead of GCC. All the AOSP devices that I checked are building
with Clang by default in android-7.0.0_r1, and the default for that
variable if unset was switched to true.

On Wed, Oct 26, 2016 at 10:01 AM Yingchun Li 
wrote:

> I compiled android-n with gcc, when build bionic/libc/ with the
> prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/, the compile errors
> list as following:
>
> mmma bionic/libc/ -B
>
> FAILED: /bin/bash -c "(PWD=/proc/self/cwd
>  
> prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-g++
> -I bionic/libc -I bionic/libc/malloc_debug -I
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates
> -I
> out/target/product/etau-V2000AN/gen/SHARED_LIBRARIES/libc_malloc_debug_intermediates
> -I libnativehelper/include/nativehelper \$(cat
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/import_includes)
> -isystem system/core/include -isystem system/media/audio/include -isystem
> hardware/libhardware/include -isystem hardware/libhardware_legacy/include
> -isystem hardware/ril/include -isystem libnativehelper/include -isystem
> frameworks/native/include -isystem frameworks/native/opengl/include
> -isystem frameworks/av/include -isystem frameworks/base/include -isystem
> out/target/product/etau-V2000AN/obj/include -isystem
> bionic/libc/arch-arm/include -isystem bionic/libc/include -isystem
> bionic/libc/kernel/uapi -isystem bionic/libc/kernel/common -isystem
> bionic/libc/kernel/uapi/asm-arm -isystem bionic/libm/include -isystem
> bionic/libm/include/arm -c  -fno-exceptions -Wno-multichar -msoft-float
> -ffunction-sections -fdata-sections -funwind-tables
> -fstack-protector-strong -Wa,--noexecstack -Werror=format-security
> -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes
> -fno-canonical-system-headers -mcpu=cortex-a7 -D__ARM_FEATURE_LPAE=1
> -mfloat-abi=softfp -mfpu=neon  -fno-builtin-sin
> -fno-strict-volatile-bitfields -Wno-psabi -mthumb-interwork -DANDROID
> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
> -fdiagnostics-color -fdebug-prefix-map=/proc/self/cwd= -Werror=return-type
> -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point  -DNDEBUG
> -g -Wstrict-aliasing=2 -fgcse-after-reload -frerun-cse-after-loop
> -frename-registers -DNDEBUG -UDEBUG   -fvisibility-inlines-hidden
> -Wsign-promo  -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing
>  -fno-rtti -Wall -Werror -fno-stack-protector -Wno-error=format-zero-length
> -fPIC -D_USING_LIBCXX -std=gnu++11-MD -MF
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.d
> -o
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.o
> bionic/libc/malloc_debug/malloc_debug.cpp ) && (cp
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.d
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.P;
> sed -e 's/#.*//' -e 's/^[^:]*: *//' -e 's/ *\$//' -e '/^\$/ d' -e
> 's/\$/ :/' <
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.d
> >>
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.P;
> rm -f
> out/target/product/etau-V2000AN/obj/SHARED_LIBRARIES/libc_malloc_debug_intermediates/malloc_debug.d
> )"
> bionic/libc/malloc_debug/malloc_debug.cpp: In function 'void*
> debug_calloc(size_t, size_t)':
> bionic/libc/malloc_debug/malloc_debug.cpp:546:49: error:
> '__builtin_mul_overflow' was not declared in this scope
>if (__builtin_mul_overflow(nmemb, bytes, )) {
>  ^
> bionic/libc/malloc_debug/malloc_debug.cpp:557:70: error:
> '__builtin_add_overflow' was not declared in this scope
>if (__builtin_add_overflow(size, g_debug->extra_bytes(), _size)) {
>   ^
> bionic/libc/malloc_debug/malloc_debug.cpp: In function 'int
> debug_iterate(uintptr_t, size_t, void (*)(uintptr_t, size_t, void*),
> void*)':
> bionic/libc/malloc_debug/malloc_debug.cpp:606:24: error: declaration of
> 'void (* debug_iterate(uintptr_t, size_t, void (*)(uintptr_t, size_t,
> void*), void*)::iterate_ctx::callback)(uintptr_t, size_t, void*)'
> [-fpermissive]
>  decltype(callback) callback;
> ^
> bionic/libc/malloc_debug/malloc_debug.cpp:602:60: error: changes meaning
> of 'callback' from 'void (* callback)(uintptr_t, size_t, void*)'
> [-fpermissive]
>  void (*callback)(uintptr_t base, size_t size, void* arg), void* arg) {
> ^
> bionic/libc/malloc_debug/malloc_debug.cpp:607:19: error: declaration of
> 'void* debug_iterate(uintptr_t, 

Re: [android-building] Build error: cannot define category for undefined class 'CBPeripheral'

['Dan Willemsen' via Android Building]

You'll need this change to build with 10.12:
https://android-review.googlesource.com/c/297536/  (I just submitted it a
couple hours ago, so syncing again should work)

- Dan

On Mon, Oct 31, 2016 at 2:52 PM 'Burkhard Mittelbach' via Android Building <
android-building@googlegroups.com> wrote:

> Hey,
>
> I'm kinda new to building android. So I followed the instructions here
> <http://source.android.com/source/building.html>. I checked out the
> master branch, set up the enviroment and
> set lunch to aosp_arm-eng.
>
> When I run "make -j8" I get following error message:
>
> In file included from external/libchrome/base/mac/
> sdk_forward_declarations.mm:5:
> external/libchrome/base/mac/sdk_forward_declarations.h:482:12: error:
> cannot define category for undefined class 'CBPeripheral'
> @interface CBPeripheral (MavericksSDK)
>^
> external/libchrome/base/mac/sdk_forward_declarations.h:44:8: note: forward
> declaration of class here
> @class CBPeripheral;
>^
> external/libchrome/base/mac/sdk_forward_declarations.h:493:12: error:
> cannot define category for undefined class 'CBUUID'
> @interface CBUUID (YosemiteSDK)
>^
> external/libchrome/base/mac/sdk_forward_declarations.h:46:8: note: forward
> declaration of class here
> @class CBUUID;
>^
>
> I use a Mac Book Pro with MacOS 10.12.1
>
> thx for the help 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[android-building] ANN: AOSP master branch build/ project move

['Dan Willemsen' via Android Building]

I’ll be submitting https://android-review.googlesource.com/286781 shortly
in order to move the `build` project to `build/make`. This will only affect
the master branch.


   -

   If you don’t have any local changes to the build project, just sync like
   normal, everything should just work.



   -

   If you have uncommitted changes, your sync will fail, and you’ll either
   have to commit your changes or reset the files in order to sync.



   -

   If you have local branches, the safest solution is to backup your
   changes (to gerrit, or otherwise) before your next sync, then apply them
   into the new project. If you don’t do that, this command should be able to
   restore your branches, at least until `git gc` runs:


(cd build/make; git fetch ../../.repo/projects/build.git
refs/heads/*:refs/heads/* refs/published/*:refs/published/*; git config -l
-f ../../.repo/projects/build.git/config | grep '^branch.' | sed 's/=/ /' |
xargs -L1 git config)

If you encounter any problems, please respond here.

Thanks,
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.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Re: Repo Tool Error

['Dan Willemsen' via Android Building]

The instructions on how to download repo are in the link in Glenn's
message: http://source.android.com/source/downloading.html#installing-repo

- Dan

On Fri, Jan 13, 2017 at 11:29 AM Jamie Jackson <jamieljackson...@gmail.com>
wrote:

> Where do I get a fresh copy of the repo? I def found the error message you
> speak of
>
> On Friday, December 20, 2013 at 5:22:28 PM UTC-5, Glenn Kasten wrote:
>
> Your copy of 'repo' tool in /home/here/bin is corrupt.  Probably the
> download failed and was replaced by an error message in HTML.
> Get a fresh copy of repo, look at it to make sure it's a valid script.
> It should start with something like this:
>   #!/usr/bin/env python
>   ## repo default configuration
> Then mark it executable with chmod +x.
> See http://source.android.com/source/downloading.html for how to download
> repo.
>
> On Friday, December 20, 2013 12:35:10 PM UTC-8, azpacif...@gmail.com
> wrote:
>
>  I have never had this happen. I cannot get repo to initialize. I keep
> getting this:
> Code:
>
> here@here:~$ cd mydroid/Freescale/droid
> here@here:~/mydroid/Freescale/droid$ PATH=~/bin:$PATH
> here@here:~/mydroid/Freescale/droid$ repo init -u 
> https://android.googlesource.com/platform/manifest -b android-4.3_r2.1
> /home/here/bin/repo: line 1: syntax error near unexpected token `newline'
> /home/here/bin/repo: line 1: `'
> here@here:~/mydroid/Freescale/droid$
>
> I uninstalled it, re-downloaded, and re-installed it. Still I get this. I
> have search all over and can't find anything on this. I do know the problem
> seems to be within repo, but I don't know how to fix it.Any and all help is
> greatly appreciated.
> Thanks,
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] AOSP 7.1.2 Make OTA Package Failed But Make Completes Successfully - Why?

['Dan Willemsen' via Android Building]

It looks like you ran out of space on /tmp:

failed to write to output: No space left on device

- Dan

On Tue, May 2, 2017 at 4:09 PM Nate Robbins <nejrobb...@gmail.com> wrote:

> Hi! I synced AOSP 7.1.2 r_8 for my Nexus5X (bullhead) and I ran make -j6.
> It completed sucessfully. However, then if I run make otapackage -j6, it
> fails with this error:
>
> assert succ, "build " + what + ".img image failed"
> AssertionError: build system.img image failed
> ninja: build stopped: subcommand failed.
> build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
> make: *** [ninja_wrapper] Error 1
>
> The full output is here: https://pastebin.com/tsAbZF9B
>
> Why can it not make a ZIP file, but it can make the images (system.img,
> boot.img etc.)
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Error when using "sign_target_files_apks" => dumpkeys.jar not found

['Dan Willemsen' via Android Building]

+Tao Bao <t...@google.com>

You should be able to build that with 'm
-j out/host/linux-x86/framework/dumpkey.jar' (or 'm -j dumpkey'), it's a
bug that it wasn't built automatically though.

- Dan

On Wed, May 3, 2017 at 12:15 PM 'pierre taillard' via Android Building <
android-building@googlegroups.com> wrote:

> Hello guys,
>
> I try to build last tag version of Android (android-7.1.1_r39
> <https://android.googlesource.com/platform/manifest/+/refs/heads/android-7.1.1_r39>
> )
> so I execute "make" with success but when i launch then :
> make dist
>  ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs
> out/dist/*-target_files-*.zip signed-target_files.zip
>
> I have the following error:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *rewriting SYSTEM/build.prop:  replace:  ro.build.display.id
> <http://ro.build.display.id>=aosp_arm-userdebug 7.1.1 N6F26Y
> eng.pierre.20170501.182057 test-keys with:  ro.build.display.id
> <http://ro.build.display.id>=aosp_arm-userdebug 7.1.1 N6F26Y
> eng.pierre.20170501.182057  replace:  ro.build.tags=test-keys with:
> ro.build.tags=release-keys  replace:
> ro.build.description=aosp_arm-userdebug 7.1.1 N6F26Y
> eng.pierre.20170501.182057 test-keys with:
> ro.build.description=aosp_arm-userdebug 7.1.1 N6F26Y
> eng.pierre.20170501.182057 release-keys  replace:
> ro.build.fingerprint=Android/aosp_arm/generic:7.1.1/N6F26Y/pierre05011820:userdebug/test-keys
> with:
> ro.build.fingerprint=Android/aosp_arm/generic:7.1.1/N6F26Y/pierre05011820:userdebug/release-keysrewriting
> SYSTEM/etc/security/mac_permissions.xml with new keys.META/otakeys.txt has
> no keys; using /home/pierre/.android-certs/releasekey.x509.pem for OTA
> package verification.Error: Unable to access jarfile
> out/host/linux-x86/framework/dumpkey.jar   ERROR: failed to run dumpkeys*
> Could someone help me on that?
> Why the dumpkeys.jar file is not already build?
> What is the dumpkeys.jar feature and why I can build it?
>
> Many thanks for 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: android-7.0.0_r1 build error, external/doclava, openjdk-8

['Dan Willemsen' via Android Building]

> FAILED:
out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.cpp
> /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d
 
--defines=out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.h
-o
out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.cpp
bootable/recovery/edify/parser.yy"
> /bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory

Does prebuilt/misc/linux-x86/bison/bison exist in your source directory? It
should, maybe a sync failed?

- Dan

On Tue, Jun 27, 2017, 7:08 AM Rakshith Patkar <rakshithpat...@gmail.com>
wrote:

> My build ends up with the following error:
>
> Any lead in this regard would be helpful :)
>
> rakshith@patkar007:~/Projects/android-source/hikey960$ make -j4
> 
> PLATFORM_VERSION_CODENAME=O
> PLATFORM_VERSION=O
> TARGET_PRODUCT=hikey960
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> 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
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.4.0-21-generic-x86_64-with-Ubuntu-16.04-xenial
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=NYC
> OUT_DIR=out
> 
> [2/2] bootstrap out/soong/.minibootstrap/build.ninja.in
> [1/2] out/soong/.bootstrap/bin/minibp out/soong/.minibootstrap/
> build.ninja.in
> ninja: no work to do.
> ninja: no work to do.
> No need to regenerate ninja file
> [  0% 1/47354] Yacc: applypatch <= bootable/recovery/edify/parser.yy
> FAILED:
> out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.cpp
> /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d
>  
> --defines=out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.h
> -o
> out/target/product/hikey960/obj/STATIC_LIBRARIES/libedify_intermediates/parser.cpp
> bootable/recovery/edify/parser.yy"
> /bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
> [  0% 4/47354] Ensuring Jack server is installed and started
> Jack server already installed in "/home/rakshith/.jack-server"
> Launching Jack server java -XX:MaxJavaStackTraceDepth=-1
> -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation
> -Xmx2048m -cp /home/rakshith/.jack-server/launcher.jar
> com.android.jack.launcher.ServerLauncher
> ninja: build stopped: subcommand failed.
> 10:02:03 ninja failed with: exit status 1
> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
> make: *** [run_soong_ui] Error 1
>
>  make failed to build some targets (01:00 (mm:ss)) 
>
>
>
> ---
>
> On Tuesday, September 6, 2016 at 7:44:32 PM UTC+5:30, James Muir wrote:
>
>> argh... I found the problem:  me :-)
>>
>> I had the variable ANDROID_JAVA_HOME set in my bashrc file.  This was a
>> remnant of kitkat development and so it pointed to an oracle java-6 jdk
>> directory on my machine :-(
>>
>> "showcommands" was helpful in uncovering this silliness:
>>
>> cd external/doclava && mm -B USE_NINJA=false showcommands
>>
>>
>> After dropping the definition of ANDROID_JAVA_HOME, I am able to build
>> successfully.
>>
>> -James M
>>
>> On Sunday, September 4, 2016 at 1:11:28 PM UTC-4, James Muir wrote:
>>>
>>> First, thanks to Bill Yi and team for publishing the N sources.
>>>
>>> I have a tree synced to the tag *android-7.0.0_r1* on an ubuntu 16.04
>>> machine, but am hitting the following build error:
>>>
>>> external/doclava/src/com/google/doclava/Converter.java:407: error:
>>> cannot find symbol
>>> m.isAbstract(), m.isSynchronized(), m.isNative(),
>>> m.isDefault(), true,
>>>^
>>>   symbol:   method isDefault()
>>>   location: variable m of type AnnotationTypeElementDoc
>>> external/doclava/src/com/google/doclava/Converter.java:429: error:
>>> cannot find symbol
>>> m.isAbstract(), m.isSynchronized(), m.isNative(),
>>> m.isDefault(), false,
>>>^
>>>   symbol:   method isDefault()
>>>   location: variable

Re: [android-building] Help AOSP building failed

['Dan Willemsen' via Android Building]

It looks like bison is looking for `m4` in your path, so you'll need to
install it with apt. We don't currently have a prebuilt of m4 to go along
with the bison prebuilt.

- Dan

On Thu, Oct 19, 2017 at 4:12 AM, Marco Tommolini <marcohie...@gmail.com>
wrote:

> HI, I'm trying to buid an AOSP and after I fixed some errors I get the
> following errors that I don't know how to resolve:
>
> root@mh2-K55VD:/bin/repo_work_directory# make -j16
> 
> PLATFORM_VERSION_CODENAME=P
> PLATFORM_VERSION=P
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.10.0-37-generic-x86_64-Ubuntu-17.04
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=OC
> OUT_DIR=out
> 
> ninja: no work to do.
> ninja: no work to do.
> No need to regenerate ninja file
> No need to regenerate ninja file
> [  0% 3/60195] Yacc: ss <= external/iproute2/misc/ssfilter.y
> FAILED: out/target/product/generic/obj/EXECUTABLES/ss_intermediates/
> ssfilter.c
> /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d
> --defines=out/target/product/generic/obj/EXECUTABLES/ss_intermediates/ssfilter.h
> -o out/target/product/generic/obj/EXECUTABLES/ss_intermediates/ssfilter.c
> external/iproute2/misc/ssfilter.y"
> external/iproute2/misc/ssfilter.y: 31 conflitti shift/riduzione
> prebuilts/misc/linux-x86/bison/bison: Sotto-processo m4 non riuscito:
> File o directory non esistente
> [  0% 18/60195] Check module type: out/target/product/generic/obj
> /SHARED_LIBRARIES/android.hardware.power@1.0_intermediates/link_type
> ninja: build stopped: subcommand failed.
> 12:48:56 ninja failed with: exit status 1
>
>  failed to build some targets (42 seconds) 
>
>
> What am I doing wrong? I've Ubuntu 17.04.
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] build aosp linux >> ninja failed with exit status 1 {LOG IN POST}

['Dan Willemsen' via Android Building]

You're missing the 'm4' tool, which we currently require to be installed on
the host system. This should be fixed if you follow these instructions:
https://source.android.com/setup/initializing#installing-required-packages-ubuntu-1404

- Dan

On Sat, Nov 18, 2017 at 9:33 PM, Yathavan Parameshwaran <
yathavanparamesh1...@gmail.com> wrote:

> yathavanparameshwaran@Inspiron-5567:~/WORKING_DIRECTORY$ 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. aosp_car_emu_arm64-userdebug
>  11. car_emu_arm-userdebug
>  12. aosp_car_emu_arm-userdebug
>  13. car_emu_x86_64-userdebug
>  14. aosp_car_emu_x86_64-userdebug
>  15. aosp_car_emu_x86-userdebug
>  16. car_emu_x86-userdebug
>  17. mini_emulator_arm64-userdebug
>  18. m_e_arm-userdebug
>  19. m_e_mips64-eng
>  20. m_e_mips-userdebug
>  21. mini_emulator_x86_64-userdebug
>  22. mini_emulator_x86-userdebug
>  23. uml-userdebug
>  24. aosp_dragon-userdebug
>  25. aosp_dragon-eng
>  26. aosp_marlin-userdebug
>  27. aosp_marlin_svelte-userdebug
>  28. aosp_sailfish-userdebug
>  29. aosp_muskie-userdebug
>  30. aosp_walleye-userdebug
>  31. aosp_walleye_test-userdebug
>  32. aosp_taimen-userdebug
>  33. aosp_angler-userdebug
>  34. aosp_bullhead-userdebug
>  35. aosp_bullhead_svelte-userdebug
>  36. hikey-userdebug
>  37. hikey960-userdebug
>
> Which would you like? [aosp_arm-eng] 34
>
> 
> PLATFORM_VERSION_CODENAME=P
> PLATFORM_VERSION=P
> TARGET_PRODUCT=aosp_bullhead
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=cortex-a53
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=cortex-a53.a57
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.10.0-28-generic-x86_64-Ubuntu-16.04.3-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=OC-DR1
> OUT_DIR=out
> 
> yathavanparameshwaran@Inspiron-5567:~/WORKING_DIRECTORY$ make -j4
> 
> PLATFORM_VERSION_CODENAME=P
> PLATFORM_VERSION=P
> TARGET_PRODUCT=aosp_bullhead
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=cortex-a53
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=cortex-a53.a57
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.10.0-28-generic-x86_64-Ubuntu-16.04.3-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=OC-DR1
> OUT_DIR=out
> 
> [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
> [56/57] glob prebuilts/ndk/stl.bp
> [76/76] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> out/build-aosp_bullhead-cleanspec.ninja is missing, regenerating...
> out/build-aosp_bullhead.ninja is missing, regenerating...
> [590/895] including system/sepolicy/Android.mk ...
> system/sepolicy/Android.mk:111: warning: BOARD_SEPOLICY_VERS not
> specified, assuming current platform version
> [895/895] including tools/tradefederation/core/Android.mk ...
> No private recovery resources for TARGET_DEVICE bullhead
> find: ‘vendor’: No such file or directory
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> SettingsFunctionalTests
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> LauncherFunctionalTests
> platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning:
> continuous_instrumentation_tests: Unknown installed file for module
> EmergencyInfoTests
> build/make/core/base_rules.mk:397: warning: overriding commands for
> target `out/target/product/bullhead/system/lib64/libmedia.so'
> build/make/core/base_rules.mk:397: warning: ignoring old commands for
> target `out/target/product/bullhead/system/lib64/libmedia.so'
> build/make/core/notice_files.mk:80: warning: overriding commands for
> target `out/t

Re: [android-building] Please help me!Thanks!

['Dan Willemsen' via Android Building]

Please don't do that, your build will fail in some other way, since that
check is there to ensure that the two build systems agree about options
that they both need to use.

On Sat, Dec 9, 2017 at 12:58 PM, Blaze Ristov 
wrote:

> In the file build/soong/android/makevars.go, there are these 3 lines:
>
> ifneq ($(my_check_failed),false)
>   $(error Soong variable check failed)
> endif
>
> Either remove them or just comment out the 2nd line ( # $(error Soong
> variable check failed) )
>
> On Fri, Dec 8, 2017 at 12:46 PM,  wrote:
>
>> When I builing the AOSP for my device ,I have a problem that I can't slove
>>
>>
>> home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning:
>> TARGET_GLOBAL_CFLAGS does not match between Make and Soong:
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Make :
>> -DNO_SECURE_DISCARD
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Soong:
>> -fno-exceptions -Wno-multichar -fno-strict-aliasing
>> -fstack-protector-strong -ffunction-sections -fdata-sections
>> -funwind-tables -Wa,--noexecstack -Werror=format-security
>> -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes
>> -fno-canonical-system-headers -Werror=pointer-to-int-cast
>> -Werror=int-to-pointer-cast -Werror=implicit-function-declaration
>> -fno-strict-volatile-bitfields -DNDEBUG -O2 -g -Wstrict-aliasing=2
>> -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DANDROID
>> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
>> -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd= -fdiagnostics-color
>> -Werror=return-type -Werror=non-virtual-dtor -Werror=address
>> -Werror=sequence-point -Werror=date-time -mcpu=cortex-a53
>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:810: error: Soong
>> variable check failed.
>> 18:19:38 ckati failed with: exit status 1
>> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
>> make: *** [run_soong_ui] Error 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Please help me!Thanks!

['Dan Willemsen' via Android Building]

Somewhere in your modifications or device configuration you're setting
TARGET_GLOBAL_CFLAGS to "-DNO_SECURE_DISCARD". We no longer support setting
target-specific global cflags -- in the vast majority of cases it's not
necessary, and should be set for just the components that are interested in
it. This helps reduce unexpected consequences, and means that we can share
intermediates that don't change between different device builds more easily.

- Dan

On Fri, Dec 8, 2017 at 3:46 AM, <q944489...@gmail.com> wrote:

> When I builing the AOSP for my device ,I have a problem that I can't slove
>
>
> home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning:
> TARGET_GLOBAL_CFLAGS does not match between Make and Soong:
> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Make :
> -DNO_SECURE_DISCARD
> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Soong:
> -fno-exceptions -Wno-multichar -fno-strict-aliasing
> -fstack-protector-strong -ffunction-sections -fdata-sections
> -funwind-tables -Wa,--noexecstack -Werror=format-security
> -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes
> -fno-canonical-system-headers -Werror=pointer-to-int-cast
> -Werror=int-to-pointer-cast -Werror=implicit-function-declaration
> -fno-strict-volatile-bitfields -DNDEBUG -O2 -g -Wstrict-aliasing=2
> -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DANDROID
> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
> -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd= -fdiagnostics-color
> -Werror=return-type -Werror=non-virtual-dtor -Werror=address
> -Werror=sequence-point -Werror=date-time -mcpu=cortex-a53
> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:810: error: Soong
> variable check failed.
> 18:19:38 ckati failed with: exit status 1
> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
> make: *** [run_soong_ui] Error 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: Android 8.1 build error in ubuntu 14.04

['Dan Willemsen' via Android Building]

> This means that in my current opinion, the software environment is the
same except for hardware (VMware vs. Bare metal).

I don't recognize the above error, but this difference is strange. Is the
source on the same type of filesystem in both cases? I know there have been
issues with a few filesystems (iirc, ones that don't return extra file
metadata during readdir, but require extra stat calls)

- Dan

On Thu, May 17, 2018, 7:31 AM Fish Zheng <zhengf...@gmail.com> wrote:

> Hello,
>Did you fix this issue? or any update?
>I just got the same compiling error as yours.
>
>However I got two very strange comparison result, I can build it on a
> Ubuntu-14.04.5 VMware but failed to do it on one bare metal Ubuntu-14.04.5
> workstation.
>I can promise I do install these 2 Ubuntu ENV using the same
> installation iso. I also install the same dependencies or tools for example:
> ```
>$ sudo apt-get install git ccache automake lzop bison gperf
> build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib
> python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev
> squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng
>$ sudo apt-get install python-wand python-crypto liblz4-tool
> ```
>This means that in my current opinion, the software environment is the
> same except for hardware (VMware vs. Bare metal).
>I am very confused of this now.
>
>
> On Thursday, March 15, 2018 at 10:52:45 PM UTC+8, zeo...@naver.com wrote:
>>
>> Hi
>> When i try to build AOSP O(8.1.0), i got this error.
>> Can anyone help me on this?
>>
>> [  0% 9/47545] target Generated: android.hardware.usb-V1.1-java <=
>> hardware/interfaces/usb/1.1/types.hal
>> FAILED:
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/PortStatus_1_1.java
>> /bin/bash -c "out/host/linux-x86/bin/hidl-gen -o
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates
>> -Ljava -randroid.hardware:hardware/interfaces
>> -randroid.hidl:system/libhidl/transport android.hardware.usb@1.1
>> ::types.PortStatus_1_1"
>> ERROR: Failed to lookup type 'PortMode' at
>> hardware/interfaces/usb/1.1/types.hal:22.21-28
>> ERROR: Failed to lookup type 'PortStatus' at
>> hardware/interfaces/usb/1.1/types.hal:45.5-14
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:51.14-25
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:56.5-16
>> ERROR: Could not parse android.hardware.usb@1.1::types.PortStatus_1_1.
>> Aborting.
>> [  0% 10/47545] target Generated: android.hardware.usb-V1.1-java <=
>> hardware/interfaces/usb/1.1/types.hal
>> FAILED:
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/PortMode_1_1.java
>> /bin/bash -c "out/host/linux-x86/bin/hidl-gen -o
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates
>> -Ljava -randroid.hardware:hardware/interfaces
>> -randroid.hidl:system/libhidl/transport android.hardware.usb@1.1
>> ::types.PortMode_1_1"
>> ERROR: Failed to lookup type 'PortMode' at
>> hardware/interfaces/usb/1.1/types.hal:22.21-28
>> ERROR: Failed to lookup type 'PortStatus' at
>> hardware/interfaces/usb/1.1/types.hal:45.5-14
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:51.14-25
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:56.5-16
>> ERROR: Could not parse android.hardware.usb@1.1::types.PortMode_1_1.
>> Aborting.
>> [  0% 11/47545] target Generated: android.hardware.usb-V1.1-java <=
>> hardware/interfaces/usb/1.1/IUsb.hal
>> FAILED:
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/IUsb.java
>> /bin/bash -c "out/host/linux-x86/bin/hidl-gen -o
>> out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates
>> -Ljava -randroid.hardware:hardware/interfaces
>> -randroid.hidl:system/libhidl/transport android.hardware.usb@1.1::IUsb"
>> ERROR: Failed to lookup type 'PortMode' at
>> hardware/interfaces/usb/1.1/types.hal:22.21-28
>> ERROR: Failed to lookup type 'PortStatus' at
>> hardware/interfaces/usb/1.1/types.hal:45.5-14
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:51.14-25
>> ERROR: Failed to lookup type 'PortMode_1_1' at
>> hardware/interfaces/usb/1.1/types.hal:56.5-16
>> ERROR:

Re: [android-building] why would my vendor module's Android.bp be skipped after conversion from Android.mk ?

['Dan Willemsen' via Android Building]

Yeah, subdirs is likely the issue here. In master, we do a full search of
all Android.bp files (ignoring subdirs), which would avoid this problem.

- Dan

On Fri, Jan 19, 2018 at 12:43 PM, Wesolowski, Krzysztof <
krzysztof.wesolow...@volvocars.com> wrote:

> Android.bp uses glob patterns instead of recursive search as Android.mk.
>
> So go to top level Android.bp and start digging into subdirs - you will
> find where the inclusion chain breaks.
>
> BR, K.
>
> Get Outlook for Android
>
> --
> *From:* android-building@googlegroups.com <android-building@
> googlegroups.com> on behalf of Robert Dugal <rmdu...@gmail.com>
> *Sent:* Friday, January 19, 2018 12:47:44 PM
> *To:* Android Building
> *Subject:* [android-building] why would my vendor module's Android.bp be
> skipped after conversion from Android.mk ?
>
> I am working on converting an Android.mk into an Android.bp for a vendor
> module that we are porting to 8.1
> We had this working on 7.0 and 8.0 but ran into problems when trying to
> update to 8.1
>
> The only reason I am doing this conversion is because some other system
> module switched from Android.mk to Android.bp and now it cannot find my
> vendor module when I build.
> From what I can tell it appears my vendor module needs to now use
> Android.bp in order for the other system module to correctly resolve the
> dependency for my module.
> Someone please correct me if that is not true.
>
> When I build it appears that for some reason my Android.bp file is not
> being processed at all.
> If I put garbage in my Android.bp file no errors are generated when I try
> "make modules".
> If I look in out/soong/.bootstrap/build.ninja.d I don't see my Android.bp
> being processed but I see other vendor/qcom/ modules being processed.
> If I try to build from my vendor module directory I get the error "ninja:
> error: unknown target 'MODULES-IN-vendor-. "
> The only way I can seem to get this working is to switch the system module
> back to using Android.mk but then there are things in Android.bp 
> (vendor_available,
> vndk, etc.) that I don't know how to replicate with Android.mk
>
> I am confused as to why my Android.bp is not being used.
>
> --
> --
> 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
> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgroups.google.com%2Fgroup%2Fandroid-building%3Fhl%3Den=02%7C01%7Ckrzysztof.wesolowski%40volvocars.com%7Cecad7f60f8b647c7405c08d55f6bfa5e%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636519839720712960=v8iuDAHAWLJo%2FV8CBieV9V%2B8VlAcAz3Vkewur%2FvqSiE%3D=0>
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout=02%7C01%7Ckrzysztof.wesolowski%40volvocars.com%7Cecad7f60f8b647c7405c08d55f6bfa5e%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636519839720712960=MVUeu1%2B5OT4NMXP2vPQP6KRHW8%2BqpZwCcK4gNB4zSo8%3D=0>
> .
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: lunch aosp_car_emu_x86

['Dan Willemsen' via Android Building]

It looks like there was a typo in device/generic/car/vendorsetup.sh. The
other files in that directory don't have the "emu_" part, so try `lunch
aosp_car_x86-userdebug`.

- Dan

On Wed, Jan 31, 2018 at 10:23 PM, Henri Hildebrand <
henri.hildebr...@gmail.com> wrote:

> Yes, I selected the pre-selectable one:
>
> *11. aosp_car_emu_x86-userdebug*
>
>
>
> Am Donnerstag, 1. Februar 2018 02:19:20 UTC+1 schrieb Glenn Kasten:
>>
>> According to https://source.android.com/setup/building#choose-a-target
>> you can use the command "lunch" with no parameters to see a list of
>> AOSP-supported targets.
>> Can you confirm that your target is supported by AOSP?
>>
>>
>>
>> On Wednesday, January 31, 2018 at 8:25:14 AM UTC-8, Henri Hildebrand
>> wrote:
>>>
>>> Hello,
>>>
>>> I try to build the Android Automotive emulator *aosp_car_emu_x86*, but
>>> when I enter lunch combo I get the message:
>>>
>>> *build/core/product_config.mk:227 <http://product_config.mk:227>: ***
>>> Can not locate config makefile for product "aosp_car_emu_x86".  Stop.*
>>>
>>> I use the branch 'android-8.1.0_r9'.
>>> Is the emulator not available or what can I do to build this?
>>>
>>> Thanks!
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] "mm" fails in frameworks/base/SystemUI

['Dan Willemsen' via Android Building]

Which branch is this? This works fine on master for me.

`mma` should work, but running `m -j out/target/common/obj/JAVA_
LIBRARIES/metrics-helper-lib_intermediates/link_type` once should fix this
particular error (there may be more behind this though).

I wouldn't expect `mma` to take 10x as long if you're compiling the same
things -- with nothing to compile (ran them twice), `mm` takes 6 seconds on
my machine, while `mma` takes 9 seconds. `mm` will take less time if you've
touched a makefile, but `mma` will share those results with a regular `m`
build, so you're reading makefiles less often.

All of those times are still longer than we'd like (especially since `mm`
used to be faster), but many of the improvements I'm looking at would
improve both `mm` and `mma`, so as the speeds improve, `mm` may just become
an alias of `mma` so that we don't run into inconsistencies like this. It's
also possible that your `mma` times are significantly longer than mine -- a
bit over half of my time increase came from ninja loading, which gets
longer with a larger build graph, but can't really go too crazy. The other
significant section is determining whether to re-read the Android.mk files,
and if any Android.mk files you've added are making use of the $(shell)
command, those can significantly affect these times. That's responsible for
a full second of the 3 second increase, and any extra $(shell) users will
linearly add their runtime to that -- it's easy to add another few seconds
accidentally.

I've posted some build performance debugging tips to
https://android.googlesource.com/platform/build/soong/+/master/docs/perf.md

- Dan

On Mon, Feb 5, 2018 at 12:12 PM, Jeffrey Blattman <
jeffrey.blatt...@gmail.com> wrote:

> ninja: error: 
> 'out/target/common/obj/JAVA_LIBRARIES/metrics-helper-lib_intermediates/link_type',
> needed by 'out/target/common/obj/APPS/SystemUITests_intermediates/link_type',
> missing and no known rule to make it
> 12:11:45 ninja failed with: exit status 1
> make: *** [run_soong_ui] Error 1
> make: Leaving directory `/media/jeff/data/src/clover/kpine'
>
> This is after a full build. Only "mma" works, which you can imagine is a
> major pain as it takes 10x as long. Note that "mm" fails even after "mma"
> completed successfully prior.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: Prebuilt library path hardcoded into executable in Android.O using Android.bp

['Dan Willemsen' via Android Building]

I'm not sure, but I suspect your SONAME is incorrect in your shared
library. Make sure that you've specified -Wl,-soname,libmyLibrary.so (or
equivalent) when building your library.

- Dan

On Mon, Feb 26, 2018 at 10:50 AM, Vasishath Kaushal <vasish...@gmail.com>
wrote:

> I dont know if this relates to ur case but i have faced a similar problem
> with cmake in the past. This is a general behaviour of make in which the
> binaries generated in build tree will always have hardcoded absolute paths
> to shared libraries. But if one runs make install and then uses those
> binaries, they have relative paths.
> The binaries generated by make install are the ones meant to be finally
> used and run on the target system.
>
> Did u also copy the binaries from an intermediate directory ?
>
> Hope this helps.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] How to depends on a host binary/library

['Dan Willemsen' via Android Building]

LOCAL_ADDITIONAL_DEPENDENCIES can be used to add additional dependencies
that must be built before anything in the current module is built. So
something like this:

LOCAL_ADDITIONAL_DEPENDENCIES := $(HOST_OUT_SHARED_LIBRARIES)/LLVMPlugin.so

- Dan

On Wed, Aug 15, 2018 at 8:58 PM Yibai Zhang  wrote:

> Hi, all
> I want to use a self writing clang plugin to optimize specific module
> inside AOSP repo, use LOCAL_CFLAGS="-fplugin=LLVMPlugin.so". So I need to
> build LLVMPlugin.so first. How can I make it first before making the target
> module?
> i.e.  "make target-module" would build host library LLVMPlugin.so first.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Build walleye kernel on macos

['Dan Willemsen' via Android Building]

It appears to be a bug in the kernel makefiles, not mkdtimg itself.
Specifically here:

https://android.googlesource.com/kernel/msm/+/android-8.1.0_r0.31/scripts/Makefile.lib#327

`stat` takes different arguments on Mac and Linux.

The kernel builds are really only tested on Linux, so you may have better
luck reproducing them using a Linux VM if you're on a Mac.

- Dan

On Mon, Aug 27, 2018 at 9:09 AM 杨凡  wrote:

> My code is :
> Kernel tag :android-8.1.0_r0.31
> AOSP tag :android-8.1.0_r15
>
> I build walleye Kernel on MacOS happen mkdtimg align 4096,
> it happen these error following:
>
> yangfan command = cfg_create   ---this print is that I comment in
> mkdtimg source code.
> create image file: arch/arm64/boot/dtbo.img...
> Total yangfan 18 entries.---this print is that I comment in
> mkdtimg source code.
> Total yangfan 0 output_img_with_config.  ---this print is that I
> comment in mkdtimg source code.
> stat: illegal option -- c
> usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]
> stat: illegal option -- c
> usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]
> /bin/sh: (+4096-1)/4096*4096-: syntax error: operand expected (error token
> is "-")
> make[1]: *** [arch/arm64/boot/dtbo.img] Error 127
> make: *** [dtbo.img] Error 2
> make: *** Waiting for unfinished jobs
>
> And so, I modify these Makefile in the path  :/arch/arm64/boot/Makefile,
> delete the align dtbo.img to 4kB, it compile ok
> diff --git a/arch/arm64/boot/Makefile b/arch/arm64/boot/Makefile
> index 7d11ab13d49b..3cbbc9abb9ce 100644
> --- a/arch/arm64/boot/Makefile
> +++ b/arch/arm64/boot/Makefile
> @@ -53,7 +53,9 @@ $(obj)/Image.lz4-dtb: $(obj)/Image.lz4 $(DTB_OBJS) FORCE
> $(call if_changed,cat)
>
>  $(obj)/dtbo.img: $(obj)/dts/dtboimg.cfg $(DTBO_OBJS) FORCE
> -   $(call if_changed,mkdtimg,4096) # align dtbo.img to 4kB
> +   $(call if_changed,mkdtimg) # align dtbo.img to 4kB
>
>
> So ,I wonder it is a bug in mkdtimg code???
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] What does "linux_bionic" mean?

['Dan Willemsen' via Android Building]

It's an experimental configuration for building host tools using bionic
instead of relying on the host glibc. So the Android.bp files have
linux_glibc and linux_bionic to differentiate options that need to be
different between the two.

- Dan

On Mon, Sep 10, 2018 at 11:11 AM bx L  wrote:

> Hello everyone,
>  I've been browsing android sources recently, and I see the
> "linux_bionic" options in some Android.bp files.
>  What does "linux_bionic" mean? Is this an option to turn on supports
> for using "linux + bionic" on the target?
>  Any ideas would be appreciated:)
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] on Android O - mm cmd fails in /framework/base

['Dan Willemsen' via Android Building]

Have you run `mma` successfully before running `mm`? `mm` can really only
handle rebuilds, since it doesn't attempt to build any required
dependencies.

- Dan


On Mon, Mar 12, 2018 at 7:05 AM <rashmi1234...@gmail.com> wrote:

> On Android version 8.1.0 project specific build with mm cmd is failing in
> /framework/base
>
> [100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> ninja: error:
> 'out/host/linux-x86/framework/host-libprotobuf-java-full.jar', needed by
> 'out/host/common/obj/JAVA_LIBRARIES/platformprotos_intermediates/classes-full-debug.jar',
> missing and no known rule to make it
> 12:55:19 ninja failed with: exit status 1
>
> Please help me to resolve this.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: Oreo: building modules with mm is incredibly slow compared to nougat

['Dan Willemsen' via Android Building]

I do have some documentation posted on how to debug slow issues like this:
https://android.googlesource.com/platform/build/soong/+/master/docs/perf.md
-- It can definitely be caused by $(shell) commands in Android.mk files,
but from the first log here, you may also be hitting a known issue:
https://android.googlesource.com/platform/build/soong/+/master/docs/perf.md#android-8_1-oreo-mr1

You may find it faster to use `mma` rather than `mm` over time, since the
results can be shared between more different invocations (though some of
the regen and loading steps are slower).

- Dan

On Wed, Apr 4, 2018 at 11:45 AM Jacob Abrams <satur9n...@gmail.com> wrote:

> It's not a Google issue. If you checkout pure AOSP 8.1 and build it you
> will see performance of mm is fast. It's a problem with Qualcomm
> modifications to the build system. Search your build directory for the
> string "Fix Later" and run git blame.
>
> Jacob
>
> On Wednesday, April 4, 2018 at 7:43:06 AM UTC-7, Quang Lam wrote:
>>
>> The strungle is real. When I use mmm command on Android 8.1, I spend a
>> lot of time here:
>>
>> [2/2] bootstrap out/soong/.minibootstrap/build.ninja.in
>> [1/1] out/soong/.bootstrap/bin/minibp out/soong/.bootstrap/build.ninja
>> [1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>>
>> in comparation with Android 7.1.
>>
>> On Wednesday, January 10, 2018 at 10:41:56 PM UTC+7, Jeffrey Blattman
>> wrote:
>>>
>>> Here are some numbers. Same code, same makefile. This is from a
>>> non-clean, previously built module in both cases. So there should be
>>> nothing to do at all.
>>>
>>> *On Nougat*
>>>
>>> SetupWizard $ time mm
>>> 
>>> PLATFORM_VERSION_CODENAME=REL
>>> ... cut ...
>>> 
>>> make: Entering directory `...'
>>> Running kati to generate build-d09ceb6bedfc4dba54e0e2e097f22474.ninja...
>>> No need to regenerate ninja file
>>> Starting build with ninja
>>> ninja: Entering directory `.'
>>> [100% 1/1] Ensure Jack server is installed and started
>>> Jack server already installed in "/home/jeff/.jack-server"
>>> Server is already running
>>> Bad request, see Jack server log
>>> make: Leaving directory `...'
>>>
>>>  make completed successfully (2 seconds) 
>>>
>>>
>>> *real 0m2.146s*
>>> user 0m0.700s
>>> sys 0m0.268s
>>>
>>>
>>> *On Oreo*
>>>
>>> SetupWizard $ time mm
>>> make: Entering directory `...'
>>> 
>>> PLATFORM_VERSION_CODENAME=REL
>>> ... cut ...
>>> 
>>> [2/2] bootstrap out/soong/.minibootstrap/build.ninja.in
>>> [1/1] out/soong/.bootstrap/bin/minibp out/soong/.bootstrap/build.ninja
>>> [1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>>> Clang SA is not enabled
>>> No need to regenerate ninja file
>>> [100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>>> Clang SA is not enabled
>>> [100% 1/1] Ensuring Jack server is installed and started
>>> Jack server already installed in "/home/jeff/.jack-server"
>>> Server is already running
>>> make: Leaving directory `...'
>>>
>>>  make completed successfully (23 seconds) 
>>>
>>>
>>> *real 0m22.377s*
>>> user 1m4.048s
>>> sys 0m9.104s
>>>
>>> So on Oreo, it takes 22 seconds to perform a build that does nothing?
>>>
>>> ???
>>> Thanks.
>>>
>>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Build errors while building AOSP 7.1.2

['Dan Willemsen' via Android Building]

If you're actually using AOSP, and only AOSP, that library does not exist,
so no.

- Dan

On Wed, Apr 11, 2018 at 9:04 AM Shikhar <shikhar...@gmail.com> wrote:

> Thanks for the reply. Are you saying it's not required while building AOSP?
>
> On Sunday, April 8, 2018 at 3:19:18 AM UTC, Dan Willemsen wrote:
>>
>> You've got "com.qti.location.sdk" in your PRODUCT_BOOT_JARS, but don't
>> have a definition of that library (it's not in AOSP).
>>
>> - Dan
>>
>> On Sat, Apr 7, 2018 at 2:32 PM Shikhar <shikh...@gmail.com> wrote:
>>
>>> Hello all,
>>>
>>> I am trying to buid AOSP for my device, the build is failing with the
>>> following error:
>>>
>>> Starting build with ninja
>>> ninja: Entering directory `.'
>>> ninja: error:
>>> 'out/target/common/obj/JAVA_LIBRARIES/com.qti.location.sdk_intermediates/classes.jar',
>>> needed by
>>> 'out/target/common/obj/PACKAGING/boot-jars-package-check_intermediates/stamp',
>>> missing and no known rule to make it
>>> make: *** [ninja_wrapper] Error 1
>>>
>>>  make failed to build some targets (30 seconds) 
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Shikhar
>>>
>>> --
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] AOSP (master) fails to build on MacOS

['Dan Willemsen' via Android Building]

I've uploaded
https://android-review.googlesource.com/c/device/linaro/hikey/+/670443 to
fix the WITH_DEXPREOPT issue. After that, the build completes successfully
on my mac.

the compilation failed for me too, but for a different reason:
> there are places where "linux" is hardcoded in some include paths.


Can you give some error output, or reproduction steps? hikey960 on master
doesn't appear to have other issues.

- Dan

On Mon, Apr 23, 2018 at 7:34 AM Oleg Kokorin <okoko...@baylibre.com> wrote:

> the compilation failed for me too, but for a different reason:
>
> there are places where "linux" is hardcoded in some include paths.
>
> Oleg
>
> On Fri, Apr 20, 2018 at 7:41 PM, Michael <val...@gmail.com> wrote:
>
>> Hi guys
>>
>> Struggling to get AOSP built on MacOS (High Sierra). I get the same
>> pthread_cond_timedwait error every attempt.
>>
>> *Commands executed*
>>
>> repo init -u https://android.googlesource.com/platform/manifest -b master
>> repo sync -j24
>>
>> . ./build/envsetup.sh
>> lunch hikey960-userdebug
>> make -j32
>>
>>
>> *Output before failure*
>> [  9% 2563/27328] target dex2oat:
>> out/target/product/hikey960/dex_bootjars/system/framework/arm64/boot.art
>> FAILED:
>> out/target/product/hikey960/dex_bootjars/system/framework/arm64/boot.art
>> /bin/bash -c "(mkdir -p
>> out/target/product/hikey960/symbols/system/framework/arm64/ ) && (rm -f
>> out/target/product/hikey960/dex_bootjars/system/framework/arm64//*.art
>> out/target/product/hikey960/dex_bootjars/system/framework/arm64//*.oat
>> out/target/product/hikey960/dex_bootjars/system/framework/arm64//*.art.rel
>> ) && (rm -f
>> out/target/product/hikey960/symbols/system/framework/arm64//*.art ) && (rm
>> -f out/target/product/hikey960/symbols/system/framework/arm64//*.oat ) &&
>> (rm -f
>> out/target/product/hikey960/symbols/system/framework/arm64//*.art.rel ) &&
>> (ANDROID_LOG_TAGS=\"*:v\" out/host/darwin-x86/bin/dex2oatd --runtime-arg
>> -Xms64m --runtime-arg -Xmx64m --compiler-filter=speed-profile
>> --profile-file=out/target/product/hikey960/dex_bootjars/system/framework/boot.prof
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/core-oj_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/core-libart_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/conscrypt_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/legacy-test_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/voip-common_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/ims-common_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy.boot_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/android.hidl.base-V1.0-java_intermediates/javalib.jar
>> --dex-file=out/target/common/obj/JAVA_LIBRARIES/android.hidl.manager-V1.0-java_intermediates/javalib.jar
>> --dex-location=/system/framework/core-oj.jar
>> --dex-location=/system/framework/core-libart.jar
>> --dex-location=/system/framework/conscrypt.jar
>> --dex-location=/system/framework/okhttp.jar
>> --dex-location=/system/framework/bouncycastle.jar
>> --dex-location=/system/framework/apache-xml.jar
>> --dex-location=/system/framework/legacy-test.jar
>> --dex-location=/system/framework/ext.jar
>> --dex-location=/system/framework/framework.jar
>> --dex-location=/system/framework/telephony-common.jar
>> --dex-location=/system/framework/voip-common.jar
>> --dex-location=/system/framework/ims-common.jar
>> --dex-location=/system/framework/org.apache.http.legacy.boot.jar
>> --dex-location=/system/framework/android.hidl.base-V1.0-java.jar
>> --dex-location=/system/framework/android.hidl.manager-V1.0-java.jar 
>> --oat-symbols=out/target/product/hikey960/symbols/system/framework/arm64/boot.oat
>> --oat-file=out/target/product/hikey960/dex_bootjars/system/framework/arm64/boot.oat
>> --oat-location=/system/framework/ar

Re: [android-building] make failed to build some targets

['Dan Willemsen' via Android Building]

This is the failure from that log:

Out of memory error (version 1.3-rc6 'Douarn' (441800
> 22a11d4b264ae70e366aed3025ef47362d1522bb by android-jack-t...@google.com))
> .
> Java heap space.
> Try increasing heap size with java option '-Xmx'.


The root problem here is that you don't have enough RAM (<4GB). Even if you
convince Jack to use more swap, extensive swap use is going to make your
builds take a very very long time. It looks like others have run into this
problem and documented how to increase the heap size (though they were
using 8GB): http://www.2net.co.uk/blog/jack-server.html

- Dan


On Mon, Mar 26, 2018 at 8:15 AM Itai <itai...@gmail.com> wrote:

> I setup a build environment following the instructions at
> https://source.android.com/setup/initializing
> with Nexus 5X binaries for Android 8.0.0 (OPR4.170623.020) inside
> VirtualBox 5.2.8
>
> The build fails. Please advise.
>
> jumbo@ubuntu-14:~/android$ lsb_release -a
> No LSB modules are available.
> Distributor ID:Ubuntu
> Description:Ubuntu 14.04.5 LTS
> Release:14.04
> Codename:trusty
>
> jumbo@ubuntu-14:~/android$ free -m
>  total   used   free sharedbuffers cached
> Mem:  3951   2824   1127 14189934
> -/+ buffers/cache:   1700   2251
> Swap:20479  5  20474
> jumbo@ubuntu-14:~/android$
>
> jumbo@ubuntu-14:~/android$ make -j4
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=8.0.0
> 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-4.4.0-116-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=OPR4.170623.020
> OUT_DIR=/home/jumbo/output/android
> 
> [38/38] bootstrap /home/jumbo/output/android/soong/.minibootstrap/
> build.ninja.in
> [4/4] /home/jumbo/output/android/soong/.bootstrap/bin/minibp
> /home/jumbo/output/android/soong/.bootstrap/build.ninja
> [621/622] glob vendor/*/*/Android.bp
> [40/40] /home/jumbo/output/android/soong/.bootstrap/bin/soong_build
> /home/jumbo/output/android/soong/build.ninja
> /home/jumbo/output/android/build-aosp_x86.ninja is missing, regenerating...
> Checking build tools versions...
> [9/973] including ./cts/Android.mk ...
> cts/apps/CtsVerifier/Android.mk:72: warning: FindEmulator: find:
> `cts/apps/CtsVerifier/src/com/android/cts/verifier/backup': No such file or
> directory
> build/core/java_common.mk:88: warning: FindEmulator: cd:
> cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/res:
> No such file or directory
> build/core/java_common.mk:88: warning: FindEmulator: cd:
> cts/hostsidetests/backup/assets: No such file or directory
> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/Android.mk:23:
> warning: FindEmulator: find:
> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/src': No such
> file or directory
> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/Android.mk:23:
> warning: FindEmulator: find:
> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/src': No
> such file or directory
> cts/tests/tests/contactsproviderwipe/Android.mk:33: warning: FindEmulator:
> find: `cts/tests/tests/contactsproviderwipe/common/src': No such file or
> directory
> cts/tests/tests/telecom3/Android.mk:37: warning: FindEmulator: find:
> `cts/tests/tests/telecom/src/android/telecom/cts/MockDialerActivity.java':
> No such file or directory
> [323/973] including ./external/toybox/Android.mk ...
> awk: line 1: syntax error at or near ,
> [355/973] including ./frameworks/av/media/libaaudio/Android.mk ...
> frameworks/av/media/libaaudio/examples/input_monitor/static/Android.mk:
> warning: input_monitor: unusual tags examples
> frameworks/av/media/libaaudio/examples/write_sine/static/Android.mk:
> warning: write_sine: unusual tags examples
> [389/973] including ./frameworks/base/Android.mk ...
> ./frameworks/base/Android.mk:865: warning: FindEmulator: find:
> `frameworks/opt/telephony/src/java/android/provider': No such file or
> directory
> ./frameworks/base/Android.mk:874: warning: FindEmulator: find:
> `frameworks/opt/telephony/src/java/android/provider': No such file or
> directory
> ./frameworks/base/Android.mk:879: warning: FindEmulator: find:
> `frameworks/opt/telephony/src/java/android/provider': No such file or
> directory
> ./frameworks/base/Andro

Re: [android-building] Installing a prebuilt APK with Android.bp

['Dan Willemsen' via Android Building]

No, keep prebuilt APKs in an Android.mk for now -- it's safe to have both
an Android.mk and Android.bp, even in the same directory.

In general we've kept most prebuilts in Make for now, unless they're
depended upon by something in Soong. For the prebuilts that we do have, we
mostly just pass them right back to Make anyways, so there's little benefit
to moving at this time.

- Dan


On Mon, Mar 26, 2018 at 8:16 AM Will Newton <will.new...@gmail.com> wrote:

>
> Hi,
>
> Is it possible to add a prebuilt APK to the build using an Android.bp
> file? I know it is possible to do this using Android.mk include
> $(BUILD_PREBUILT) but androidmk cannot convert a makefile of this kind.
>
> Is there another way of doing this or do I have to convert my tree of
> Android.bp files back to Android.mk?
>
> Thanks,
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Not able to build HIDL driver files inside ZFS container

['Dan Willemsen' via Android Building]

It sounds like this is this bug: https://issuetracker.google.com/74084489
(there are some patches linked that you could try)

- Dan


On Mon, Mar 26, 2018 at 8:16 AM <simon.e...@u-blox.com> wrote:

> Hi Dan,
>
> thanks for looking in to this.
> Attached is the full output of the mma command at the end of my
> step-by-step reproduction.
>
> Simon
>
>
> Am Montag, 19. März 2018 23:09:53 UTC+1 schrieb Dan Willemsen:
>>
>> Are there any other messages between the line that starts with FAILED and
>> the first "failed to create expected output file" message? That message
>> just means that the underlying tool didn't create the output files as
>> expected (the message has been cleaned up a bit on master).
>>
>> - Dan
>>
>> On Mon, Mar 19, 2018 at 9:42 AM <simon...@u-blox.com> wrote:
>>
>>> Hello,
>>>
>>> I think I found some sort of bug when trying to build the HIDL library
>>> inside a ZFS pool.
>>>
>>> we use ZFS in our build system, wehave the AOSP source in a ZFS pool.
>>> We are currently starting to switch to the HIDL interface and I stumbled
>>> over a (suspected) bug when trying to build our driver with the new
>>> interface.
>>> It only ever appears when I have the AOSP source inside the ZFS pool, it
>>> seems not to happen when the source is checked out on the harddisk.
>>> I have confirmed this behaviour on multiple machines.
>>> The AOSP build system seems to trip over something and seems to not be
>>> able to create an output file.
>>> However, manually creating the file (with "touch") is no problem.
>>> The error I get is
>>>
>>> *failed to create expected output file:
>>> out/soong/.temp/sbox552673235/.intermediates/hardware/interfaces/gnss/1.0/android.hardware.gnss@1.0_genc++_headers/gen/android/hardware/gnss/1.0/BsGnssXtra.h*
>>>
>>> The filename changes for all the files it wanted to create.
>>>
>>> Could you please confirm this bug and maybe start investigating on your
>>> side?
>>>
>>> This is a simple step-by-step reproduction of the bug:
>>>
>>> #Create a growing file for ZFS
>>> truncate -s 100G test
>>> #Create a new ZFS pool on the created file
>>> sudo zpool create test `pwd`/test
>>> #Just give let anyone do whatever they want to this pool for this demo
>>> sudo chmod 777 /test
>>> #Checkout AOSP in this pool
>>> cd /test
>>> repo init -u https://android.googlesource.com/platform/manifest -b
>>> android-8.1.0_r18
>>> #Let it sync, this will take a while...
>>> repo sync -j3
>>> #Init AOSP environment
>>> . ./build/envsetup
>>> lunch #choose hikey-userdebug
>>> #Create demo module
>>> mkdir -p hardware/test
>>> cd hardware/test
>>> #test.cpp seems to be needed for the module to have to actually do some
>>> work
>>> touch test.cpp
>>>
>>> cat < Android.mk
>>> LOCAL_PATH:= \$(call my-dir)
>>> include \$(CLEAR_VARS)
>>>
>>> LOCAL_INCLUDES += \$(LOCAL_PATH)
>>>
>>> LOCAL_CFLAGS += \$(APF_CFLAGS)
>>>
>>> LOCAL_MODULE_RELATIVE_PATH := hw
>>> LOCAL_MODULE := android.hardware.gnss@1.0-service-test
>>> LOCAL_SRC_FILES := \
>>> test.cpp
>>> LOCAL_SHARED_LIBRARIES := \
>>>  liblog \
>>>  libcutils \
>>>  libdl \
>>>  libbase \
>>>  libutils \
>>>  libhwbinder \
>>>  libhidlbase \
>>>  libhidltransport \
>>>  android.hardware.gnss@1.0
>>>
>>> include \$(BUILD_STATIC_LIBRARY)
>>> EOF
>>> #Finally: build demo module
>>> mma
>>>
>>>
>>> #Produces following errors (snippet):
>>> # failed to create expected output file:
>>> out/soong/.temp/sbox552673235/.intermediates/hardware/interfaces/gnss/1.0/android.hardware.gnss@1.0_genc
>>> ++_headers/gen/android/hardware/gnss/1.0/BsGnssXtra.h
>>> # failed to create expected output file:
>>> out/soong/.temp/sbox552673235/.intermediates/hardware/interfaces/gnss/1.0/android.hardware.gnss@1.0_genc
>>> ++_headers/gen/android/hardware/gnss/1.0/IGnssXtraCallback.h
>>> # failed to create expected output file:
>>> out/soong/.temp/sbox552673235/.intermediates/hardware/interfaces/gnss/1.0/android.hardware.gnss@1.0_genc
>>> ++_headers/gen/android/hardware/gnss/1.0/IHwGnssXtraCallback.h
>>> # failed to create expected outp

Re: [android-building] question related to ccache

['Dan Willemsen' via Android Building]

Generally it's a good idea to use the tools paired with the branch. But in
ccache's case, the binaries are the same for M, N, O, and newer. With the
build system you're always going to use the ccache binary paired with the
tree anyways -- you just set USE_CCACHE=1. The only time you'd use the
ccache binary directly is to manage the cache settings.

- Dan

On Mon, Apr 2, 2018 at 7:53 AM <lang...@intel.com> wrote:

> According guide posted here :
> https://source.android.com/setup/build/initializing#optimizing-a-build-environment,
> ccache can help to optimize build. My question is if the newest ccache can
> benefit old dessert code compiling? e.g. I get the '
> prebuilts/misc/linux-x86/ccache/ccache' from O MR1. but sometimes I also
> need to compile M or N dessert, Can I still use the one from O MR1 or I
> need to use it from M or N dessert prebuild?
>  the right place>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: mac 10.13 high sierra build failed:ninja failed with: exit status 1 #### failed to build some target

['Dan Willemsen' via Android Building]

What version of Android are you trying to build? This has been fixed on
master, older versions generally aren't supported on new Mac versions
(there's a range check for compatible SDK versions, but this is a runtime
issue, so that may not catch it).

- Dan


On Wed, Mar 21, 2018 at 7:04 AM Suyash Gupta <suyash.gupt...@gmail.com>
wrote:

> I am facing the same issue. Please help guys here!
>
> On Sunday, December 3, 2017 at 1:44:46 AM UTC+5:30, 王晓辉 wrote:
>>
>> [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
>>
>> [56/57] glob prebuilts/ndk/stl.bp
>>
>> [76/76] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>>
>> out/build-full-cleanspec.ninja is missing, regenerating...
>>
>> out/build-full.ninja is missing, regenerating...
>>
>> [2/897] including art/Android.mk ...
>>
>> *art/build/Android.common.mk:50 <http://Android.common.mk:50>: **warning:
>> **unsupported HOST_ARCH=x86_64*
>>
>> [590/897] including system/sepolicy/Android.mk ...
>>
>> *system/sepolicy/Android.mk:111: **warning: **BOARD_SEPOLICY_VERS not
>> specified, assuming current platform version*
>>
>> [897/897] including tools/tradefederation/core/Android.mk ...
>>
>> *platform_testing/build/tasks/tests/instrumentation_metric_test_list.mk
>> <http://instrumentation_metric_test_list.mk>: **warning:**
>> continuous_instrumentation_metric_tests: Unknown installed file for module
>> perf-setup.sh *
>>
>> *platform_testing/build/tasks/tests/instrumentation_test_list.mk
>> <http://instrumentation_test_list.mk>: **warning:**
>> continuous_instrumentation_tests: Unknown installed file for module
>> SettingsFunctionalTests *
>>
>> *platform_testing/build/tasks/tests/instrumentation_test_list.mk
>> <http://instrumentation_test_list.mk>: **warning:**
>> continuous_instrumentation_tests: Unknown installed file for module
>> LauncherFunctionalTests *
>>
>> *platform_testing/build/tasks/tests/instrumentation_test_list.mk
>> <http://instrumentation_test_list.mk>: **warning:**
>> continuous_instrumentation_tests: Unknown installed file for module
>> EmergencyInfoTests *
>>
>> *platform_testing/build/tasks/tests/native_metric_test_list.mk
>> <http://native_metric_test_list.mk>: **warning:**
>> continuous_native_metric_tests: Unknown installed file for module
>> perf-setup.sh *
>>
>> [ 99% 439/440] glob tools/apksig/src/main/java/**/*.java
>>
>> [  0% 123/62632] //external/protobuf:aprotoc
>> cla...gle/protobuf/compiler/java/java_file.cc [darwin]
>>
>> In file included from
>> external/protobuf/src/google/protobuf/compiler/java/java_file.cc:41:
>>
>> In file included from external/libcxx/include/set:389:
>>
>> *external/libcxx/include/__tree:1817:22: **warning: **the specified
>> comparator type does not provide a const call operator
>> [-Wuser-defined-warnings]*
>>
>>  __trigger_diagnostics()), "");
>>
>> * ^*
>>
>> *external/libcxx/include/set:400:28: note: *in instantiation of member
>> function 'std::__1::__tree> google::protobuf::compiler::java::(anonymous
>> namespace)::FieldDescriptorCompare, std::__1::allocator> google::protobuf::FieldDescriptor *> >::~__tree' requested here
>>
>> class _LIBCPP_TEMPLATE_VIS set
>>
>> *   ^*
>>
>> *external/libcxx/include/__tree:968:7: note: *from 'diagnose_if'
>> attribute on '__trigger_diagnostics':
>>
>>   _LIBCPP_DIAGNOSE_WARNING(!__invokable<_Compare const&, _Tp const&,
>> _Tp const&>::value,
>>
>> *  ^
>> *
>>
>> *external/libcxx/include/__config:1058:20: note: *expanded from macro
>> '_LIBCPP_DIAGNOSE_WARNING'
>>
>> __attribute__((diagnose_if(__VA_ARGS__, "warning")))
>>
>> *   ^   ~~~*
>>
>> 1 warning generated.
>>
>> [  0% 236/62632] //external/selinux/checkpolicy:checkpolicy yacc
>> policy_parse.y [darwin]
>>
>> FAILED:
>> out/soong/.intermediates/external/selinux/checkpolicy/checkpolicy/darwin_x86_64/gen/yacc/external/selinux/checkpolicy/policy_parse.c
>> out/soong/.intermediates/external/selinux/checkpolicy/checkpolicy/darwin_x86_64/gen/yacc/external/selinux/checkpolicy/policy_parse.h
>>
>>
>> BISON_PKGDATADIR=external/bison/data
>> prebuilts/misc/darwin-x86/bison/bison -d  
>

Re: [android-building] Can not locate config makefile for product "aosp_car_emu_x86_64"

['Dan Willemsen' via Android Building]

There was a typo in the shell script used to create that lunch menu.
Directly use `lunch aosp_car_x86_64-userdebug` instead (without the _emu).

- Dan


On Wed, Mar 21, 2018 at 7:04 AM Birender Singh <mebirendersi...@gmail.com>
wrote:

> Unable to compile any of car emulator.
>
> 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. aosp_car_emu_arm-userdebug
>  10. aosp_car_emu_arm64-userdebug
>  11. aosp_car_emu_x86-userdebug
>  12. aosp_car_emu_x86_64-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. uml-userdebug
>  20. aosp_dragon-userdebug
>  21. aosp_dragon-eng
>  22. aosp_marlin-userdebug
>  23. aosp_marlin_svelte-userdebug
>  24. aosp_sailfish-userdebug
>  25. aosp_walleye-userdebug
>  26. aosp_walleye_test-userdebug
>  27. aosp_taimen-userdebug
>  28. aosp_angler-userdebug
>  29. aosp_bullhead-userdebug
>  30. aosp_bullhead_svelte-userdebug
>  31. hikey-userdebug
>  32. hikey960-userdebug
>
> Which would you like? [aosp_arm-eng] 12
> build/core/product_config.mk:227: *** Can not locate config makefile for
> product "aosp_car_emu_x86_64".  Stop.
>
> Branch: android-8.1.0_r18
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] "sudo apt-get install ia32-libs git gnupg flex bison gperf build-essential zip" execution failure

['Dan Willemsen' via Android Building]

>
> "apt-get install ia32-libs git gnupg flex bison gperf build-essential zip"


E: Package 'ia32-libs' has no installation candidate
>

My experience with this error is that your system is set up as 64-bit only.
That's currently not supported to build android, we still execute some
32-bit programs.

As in this process during the download process of Java 6 I am getting the
> error as per below.


What version of Android are you trying to build? Java6 is only required for
very old branches -- Gingerbread through KitKat. The command that you're
using doesn't say anything about java, how are you actually downloading it?

Which OS are you building on? (If you're using Java6, you probably need to
be using Ubuntu 12.04 for your particular branch)

- Dan

On Wed, Mar 21, 2018 at 7:05 AM Explore India <mrp.mana...@gmail.com> wrote:

> Hi,
>
> I am right now trying to install all the required toolchain for building
> the android for the cubie board. But unfortunately, I am getting the error
> message given below after execution of the command "apt-get install
> ia32-libs git gnupg flex bison gperf build-essential zip"
>
> COMMAND
> =
> "apt-get install ia32-libs git gnupg flex bison gperf build-essential zip"
>
> ERROR MESSAGE
> 
> ip
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package ia32-libs is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> However the following packages replace it:
>   lib32ncurses5 lib32z1
>
> E: Package 'ia32-libs' has no installation candidate
>
>
> *Note : *I tried with the "lib32ncurses5" and "lib32z1" instead of
> "ia32-libs" as per the error message.But still, I am getting the failure
> response.As in this process during the download process of Java 6 I am
> getting the error as per below.
>
> COMMAND
> =
> apt-get install lib32z1 git gnupg flex bison gperf build-essential zip
> or
> apt-get install lib32ncurses5 git gnupg flex bison gperf build-essential
> zip
>
> ERROR MESSAGE
> ===
> Downloading Oracle Java 6...
> --2018-03-21 13:02:15--
> http://download.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin
> Resolving download.oracle.com (download.oracle.com)... 23.56.176.183
> Connecting to download.oracle.com (download.oracle.com)|23.56.176.183|:80...
> connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location:
> https://edelivery.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin
> [following]
> --2018-03-21 13:02:16--
> https://edelivery.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin
> Resolving edelivery.oracle.com (edelivery.oracle.com)... 184.50.117.49,
> 2405:200:1630:481::2d3e, 2405:200:1630:497::2d3e
> Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|184.50.117.49|:443...
> connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location:
> http://download.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin?AuthParam=1521617656_1bc06418683eb8cd61c93778460bd58a
> [following]
> --2018-03-21 13:02:17--
> http://download.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin?AuthParam=1521617656_1bc06418683eb8cd61c93778460bd58a
> Connecting to download.oracle.com (download.oracle.com)|23.56.176.183|:80...
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2018-03-21 13:02:19 ERROR 404: Not Found.
>
> download failed
> Oracle JDK 6 is NOT installed.
> dpkg: error processing package oracle-java6-installer (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Setting up lib32z1 (1:1.2.8.dfsg-2ubuntu4.1) ...
> Processing triggers for libc-bin (2.23-0ubuntu10) ...
> Errors were encountered while processing:
>  oracle-java6-installer
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
>
>
> My Observation
> --
> I am thinking that " oracle-java6-installer" is obsolete now.So the
> support and dependency are not able to download.
>
>
>
> What should I do now 
> Please help me in this.
>
>
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.goog

Re: [android-building] Re: Encountering error while building

['Dan Willemsen' via Android Building]

For the master branch on AOSP, you need the preview blobs, not the ones
from PPR2: https://source.android.com/setup/build/requirements#binaries

For your 9.0.0_r10 build, why do you have a hardware/qcom/sdm845.mk file?
Is it left over from a previous checkout?

- Dan

On Mon, Oct 29, 2018 at 7:33 AM Brian Moore  wrote:

> I've never built from the master branch. I always build with the latest
> branch for my device.
>
> Since you're building for Pixel (sailfish), try repo init with the
> 9.0.0_r10 branch, which is the most recent according to this link:
> https://source.android.com/setup/start/build-numbers
> This branch will also match with the version on binaries that you already
> downloaded.
>
> Note: Even if you successfully build, there seems to be a bug with the
> current binaries supplied by Google for AOSP 9.0 for Sailfish. Some files
> are missing and the SIM is not found. There is another thread in this group
> right now that addresses this issue and a workaround.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] can different Android branch code use the same ccache dir？

['Dan Willemsen' via Android Building]

Yes, you should be able to share them across branches. We used to do this
on our builders, but we removed ccache from our builders (and master),
since it was causing more problems than it was saving in time. Incremental
builds are a bigger win (they've been increasingly safe with newer
versions, at least when paired with `m installclean`).

- Dan

On Wed, Oct 10, 2018 at 4:44 AM Minghui Ma  wrote:

> can different Android branch code  use the same ccache dir？
> such as android n，o，p use the  same ccache dir path。
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: Build android Oreo Code

['Dan Willemsen' via Android Building]

It sounds like you're using at least some of the code from Oreo, but didn't
take the repo manifest updates that added  entries to put those
back into place. Which may mean that you're also missing new projects, or
still have projects that have been removed as well.

- Dan

On Wed, Sep 19, 2018 at 8:57 AM Glenn Kasten  wrote:

> On Linux, build/envsetup.sh is a symlink to make/envsetup.sh so you can
> still use:
>. build/envsetup.sh
>
> Are you sure you are in the top directory of your sandbox when you issued
> the ". build/envsetup.sh" ?
>
> "lunch 39" might not be a valid lunch target.  Try using another lunch
> target name such as
> "lunch aosp_arm-eng" etc.
>
>
> On Wednesday, September 19, 2018 at 8:21:53 AM UTC-7, ashok reddy reddy
> wrote:
>>
>> I am trying to build android O code. Looks like in O some folder
>> structure is modified ie envsetup.sh is moved form build/envsetup.sh to
>> build/make/envsetup.sh.
>>
>> Lunch command is failing for me.
>>
>>
>> *. build/make/envsetup.sh *
>> including device/generic/car/vendorsetup.sh
>> including device/generic/mini-emulator-arm64/vendorsetup.sh
>> including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
>> including device/generic/mini-emulator-x86_64/vendorsetup.sh
>> including device/generic/mini-emulator-x86/vendorsetup.sh
>> including device/generic/uml/vendorsetup.sh
>> including device/qcom/common/vendorsetup.sh
>> including sdk/bash_completion/adb.bash
>>
>>
>> *lunch 39*
>> cat: /build/envsetup.sh: No such file or directory
>> cat: /build/envsetup.sh: No such file or directory
>> make: build/core/config.mk: No such file or directory
>> make: *** No rule to make target `build/core/config.mk'.  Stop.
>>
>> anyone build android O code?...
>>
>>
>> Please let me know the steps to 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Re: How to build the Latin IME input method?

['Dan Willemsen' via Android Building]

Download the source and set up your machine as described on
https://source.android.com/setup/build/requirements

Basically, do everything up to the "lunch" step, then use "tapas" instead:

  $ tapas LatinIME arm64
  $ m

The APK will be
in out/target/product/generic_arm64/system/app/LatinIME/LatinIME.apk

- Dan

On Wed, Sep 19, 2018 at 8:20 AM Bhavdip Bhalodia <
bhavdip.bhalo...@codereadr.com> wrote:

> I am also trying to develop LatinIME but there is less understanding to
> develop it.
> Thanks,
>
> On Monday, August 27, 2018 at 9:40:02 PM UTC+5:30, Vedant Roy wrote:
>>
>> I am trying to build the Latin IME input method.
>>
>> The source code can be found here:
>> https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/master
>>
>> Are there any guides on how to build Android source code. Any tips at all
>> would be helpful. For instance - what are the tools I need, what files are
>> actually necessary for the build etc.
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] make systemtarball and selinux context

['Dan Willemsen' via Android Building]

I'm not sure anyone is using the systemtarball functionality anymore,
especially with the lack of selinux as you've discovered.

Generally we put the prebuilt APKs as inputs into the Android build, since
they may be modified and transformed by the build (uncompress shared libs,
strip dex files, create odex files, do various sanity checks). But there's
a handful of cases where that may not matter and you can post-process them
into a built artifact from a platform build. In that case, you can do
something like:

1. Saving the target-files-package zip and otatools.zip from the Android
platform build. The target-files-package is the input to the OTA scripts,
and is a zip file containing all content and metadata (but not tools,
that's otatools) needed to create an android image. It can contain full
image files as well.

2. Manipulate the zip file to add your APKs to SYSTEM/, and remove any
IMAGES/ files that you want to regenerate.

3. Use the releasetools -- either from build/tools/releasetools and various
built tools, or from otatools.zip to recreate the images:
releasetools/add_img_to_target_files 

- Dan

On Wed, Sep 19, 2018 at 8:20 AM Jan Leonhardt 
wrote:

> Hello yall,
>
> i tried to create a system tarball to add some apk's in other build jobs.
>
> but the created tarballs have no selinux context inside. a look into
> build/tools/mktarball.sh shows, that tar is used without --selinux
> parameter.
>
> If i put the content from that tarball to my system partition, my system
> cant boot, because the contexts for all services are missing.
> If i write the system.img to my system partition, all the contexts are
> there.
>
> i am doing something totally wrong, or should the --selinux param been
> added to mktarball.sh?
>
> thanks in advance!
>
> Jan
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] How to include prebuilt jars using bp in Android P

['Dan Willemsen' via Android Building]

To compile that
frameworks/base/services/core/java/com/example/sevice/myservice.java file,
you'd need to add your lib to the libs section of services.core.unboosted
in frameworks/base/services/core/Android.bp.

- Dan

On Tue, Sep 25, 2018 at 10:23 AM shankar kumar yellapu <
shankarkumaryel...@gmail.com> wrote:

> Hi Dan,
> Thanks for quick reply, But my actual import from
> frameworks/base/services/core/java/com/example/sevice/myservice.java is
> saying error: package com.my.service.addon does not exist.
>
> If I give mm in frameworks/base/services/myservices/ says build successful.
>
> My Android.bp under /frameworks/base/services/ is as following:
>
> // merge all required services into one jar
> // 
> java_library {
> name: "services",
>
> dex_preopt: {
> app_image: true,
> profile: "art-profile",
> },
>
> srcs: [
> "java/**/*.java",
> ],
>
> // The convention is to name each service module
> 'services.$(module_name)'
> static_libs: [
> "services.core",
> "services.accessibility",
> "services.appwidget",
> "services.autofill",
> "services.backup",
> "services.companion",
> "services.coverage",
> "services.devicepolicy",
> "services.midi",
> "services.net",
> "services.print",
> "services.restrictions",
> "services.usage",
> "services.usb",
> "services.voiceinteraction",
> "android.hidl.base-V1.0-java",
> ],
>
> libs: [
> "android.hidl.manager-V1.0-java",
> "my-services",
> ],
>
> // Uncomment to enable output of certain warnings (deprecated,
> unchecked)
> //javacflags: ["-Xlint"],
>
> }
>
> // native library
> // =
>
> cc_library_shared {
> name: "libandroid_servers",
> defaults: ["libservices.core-libs"],
> whole_static_libs: ["libservices.core"],
> }
>
> am I missing anything here???
>
> Thanks,
> Shankar
>
> On Tuesday, September 25, 2018 at 2:35:38 AM UTC+5:30, Dan Willemsen wrote:
>>
>> You'll need to define your prebuilt using java_import:
>>
>>   java_import {
>>   name: "my-services",
>>   jars: ["my-services-prebuilt.jar"],
>>   }
>>
>> You shouldn't need the my-services vs my-services-prebuilt
>> differentiation like you did with make.
>>
>> - Dan
>>
>> On Mon, Sep 24, 2018 at 8:11 AM shankar kumar yellapu <
>> shankarku...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to include a jar in /frameworks/base/services/myservice using
>>> bp . My bp file looks like this:
>>>
>>> java_library_static {
>>> name: "my-service",
>>> static_libs: ["my-services-prebuilt"],
>>> }
>>>
>>> I've copied my prebuilt jar in the same location with the name
>>> my-services-prebuilt. I'm getting the following error:
>>>
>>> error:
>>> frameworks/base/services/my-services/Android.bp:29:1:"my-services" depends
>>> on undefined module ",my-services-prebuilt"
>>>
>>> FYR: my make file in Android O
>>>
>>> LOCAL_PATH:= $(call my-dir)
>>>
>>> # static jar
>>> # 
>>> include $(CLEAR_VARS)
>>> LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES :=
>>> my-services-prebuilt:my-services-prebuilt.jar
>>> include $(BUILD_MULTI_PREBUILT)
>>>
>>> # shared jar
>>> # 
>>> include $(CLEAR_VARS)
>>> LOCAL_MODULE := my-services
>>> LOCAL_MODULE_TAGS := optional
>>> LOCAL_STATIC_JAVA_LIBRARIES := my-services-prebuilt
>>> include $(BUILD_JAVA_LIBRARY)
>>> endif
>>>
>>>
>>> Can anybody tell me what I'm doing wrong?? Please send me proper bp
>>> script.
>>>
>>> Regards,
>>> Shankar
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post 

Re: [android-building] Re: How to build the Latin IME input method?

['Dan Willemsen' via Android Building]

AOSP does not have a minimal manifest for Latin IME -- with enough work,
it's likely possible, but I suspect it would need at least 30-40 different
repositories (the build system, different compilers, dependencies, etc).

- Dan

On Fri, Sep 21, 2018 at 8:36 AM Vedant Roy  wrote:

> Thank you so much for the assistance. I have two more questions in regards
> to this topic.
>
> 1] Is it possible to only download the part of the source that is relevant
> to the Latin IME?
>
> For example, can I just do: git clone
> https://android.googlesource.com/platform/packages/inputmethods/LatinIME
> and then run the lunch/tapas commands?
>
> 2] It turns out that I only need to build the native portion of the Latin
> IME (The C++ files), presumably into a .so file, so that they can be used
> by an apk. They can be found here:
> https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/master/native/
>
>
> Is it possible for me to only build the native portion of the Latin IME?
>
> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] How to build Settings APK from AOSP Source code ?

['Dan Willemsen' via Android Building]

The Settings app reaches into enough private APIs that you're going to need
a significant portion of the platform in order to build it. (It does not
build against the public SDKs)

- Dan

On Mon, Sep 24, 2018 at 8:11 AM BugWrapper  wrote:

> Is it possible to build the settings apk individually ? if yes Could you
> please provide a set of steps to build the Settings apk from the source
> code (https://groups.google.com/forum/#!forum/android-building) without
> pulling the whole android source code ?
>
>
> Thanks
> BugW
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] How to include prebuilt jars using bp in Android P

['Dan Willemsen' via Android Building]

You'll need to define your prebuilt using java_import:

  java_import {
  name: "my-services",
  jars: ["my-services-prebuilt.jar"],
  }

You shouldn't need the my-services vs my-services-prebuilt differentiation
like you did with make.

- Dan

On Mon, Sep 24, 2018 at 8:11 AM shankar kumar yellapu <
shankarkumaryel...@gmail.com> wrote:

> Hi,
>
> I'm trying to include a jar in /frameworks/base/services/myservice using
> bp . My bp file looks like this:
>
> java_library_static {
> name: "my-service",
> static_libs: ["my-services-prebuilt"],
> }
>
> I've copied my prebuilt jar in the same location with the name
> my-services-prebuilt. I'm getting the following error:
>
> error: frameworks/base/services/my-services/Android.bp:29:1:"my-services"
> depends on undefined module ",my-services-prebuilt"
>
> FYR: my make file in Android O
>
> LOCAL_PATH:= $(call my-dir)
>
> # static jar
> # 
> include $(CLEAR_VARS)
> LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES :=
> my-services-prebuilt:my-services-prebuilt.jar
> include $(BUILD_MULTI_PREBUILT)
>
> # shared jar
> # 
> include $(CLEAR_VARS)
> LOCAL_MODULE := my-services
> LOCAL_MODULE_TAGS := optional
> LOCAL_STATIC_JAVA_LIBRARIES := my-services-prebuilt
> include $(BUILD_JAVA_LIBRARY)
> endif
>
>
> Can anybody tell me what I'm doing wrong?? Please send me proper bp script.
>
> Regards,
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Failing to build sdk and sdk_addon in master P

['Dan Willemsen' via Android Building]

Just like anything else you want installed, put it in PRODUCT_PACKAGES,
either in the core build system's core product makefiles, or in your
product's makefiles.

I'm not sure why those builds are failing without more information -- at
least the normal SDK build is passing on our CI systems:
https://ci.android.com/builds/branches/aosp-master/grid (the sdk* columns)

- Dan

On Thu, Dec 27, 2018 at 12:02 PM 
wrote:

> Thank you, using 'm mkstubs' worked.
> Though normal building with sdk_addon or just sdk still doesn't.
>
> And if i want to build it automatically as part of the build similar to
> the doclava or other such jars.
> Where do i need to put it to work?
>
> On Thursday, December 27, 2018 at 12:34:54 AM UTC+2, Dan Willemsen wrote:
>>
>> You should be able to just run `m mkstubs` from any build configuration
>> to build mkstubs (as it's a host tool).
>>
>> It'll be in out/host/linux-x86/framework/mkstubs.jar (or darwin-x86 if
>> you're on a Mac) once built.
>>
>> - Dan
>>
>> On Tue, Dec 18, 2018 at 1:46 PM 
>> wrote:
>>
>>> Hey there,
>>>
>>> I am rather new to AOSP development and i am trying to build a sdk
>>> version and a sdk_addon but it fails.
>>> This is after i managed to build regularly successfully.
>>>
>>> I am using the *master branch* from google source.
>>> *lunch option*: aosp-arm64  userdebug
>>>
>>> *commands tried*:
>>> make sdk -j6
>>> make PRODUCT-sample_addon-sdk_addon -j6
>>>
>>> I was trying to understand how and where i get the *mkstubs*
>>> development tool to compile in P, as it is not being
>>> built in the the normal build option.
>>> After scouring the internet for answers but couldn't find any i thought
>>> maybe using these options
>>> will build them for me and i can get some more understanding on how to
>>> control which tool is built.
>>>
>>> Can you please explain why those builds fail for me and how i can add
>>> such development tools to the build?
>>>
>>> Thank you,
>>> Konstantin
>>>
>>> --
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Failing to build sdk and sdk_addon in master P

['Dan Willemsen' via Android Building]

Ah, that's right. The SDK targets build with different TARGET_PRODUCT
values -- use sdk_phone_arm64-userdebug instead of aosp_arm64-userdebug.
It's nearly the same (and should be a quick incremental build), it just
triggers those missing files to be installed:
https://android.googlesource.com/platform/build/+/master/target/product/sdk_phone_arm64.mk
(And yes, this could be better)

The other things that could cause some issues (though it's unlikely to,
since it's not really used in many places anymore) is
TARGET_BUILD_TYPE=debug. We never do any builds in that configuration, so
it's possible to be broken (though again, unlikely, since it affects nearly
nothing).

- Dan

On Mon, Dec 31, 2018 at 9:09 AM 
wrote:

> Hey again Dan, and thanks for the help ! I appreciate it.
>
> I am trying to build to aosp-arm64 (unlike the version in the builds in
> the links which is armv7-a-neon if i am correct), maybe this is the cause?
> This is my envsetup log and the failure if you want to take a look:
>
> PLATFORM_VERSION_CODENAME=Q
> PLATFORM_VERSION=Q
> TARGET_PRODUCT=aosp_arm64
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=debug
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv7-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.4.0-31-generic-x86_64-Ubuntu-14.04.5-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PI
> OUT_DIR=out
>
>
> FAILED:
> out/host/linux-x86/sdk/aosp_arm64/android-sdk_eng.tdb346_linux-x86.zip
> /bin/bash
> out/host/linux-x86/sdk/aosp_arm64/android-sdk_eng.tdb346_linux-x86.zip.rsp
> SDK: warning: including GNU target
> out/target/product/generic_arm64/system/etc/xtables.lock
> SDK: warning: including GNU target
> out/target/product/generic_arm64/system/lib/libdt_fd_forward.so
> .
> .
> .
> SDK: warning: including GNU target
> out/target/product/generic_arm64/system/lib64/vndk-Q/libnl.so
> SDK: warning: including GNU target
> out/target/product/generic_arm64/system/lib64/vndk-Q/libselinux.so
> development/build/sdk-linux-x86.atree:36: couldn't locate source file:
> lib64/libaapt2_jni.so
> development/build/sdk.atree:53: couldn't locate source file:
> bin/dmtracedump
> development/build/sdk.atree:54: couldn't locate source file: bin/etc1tool
> development/build/sdk.atree:58: couldn't locate source file:
> system/framework/deployagent.jar
> development/build/sdk.atree:59: couldn't locate source file:
> system/bin/deployagent
> development/build/sdk.atree:88: couldn't locate source file:
> bin/split-select
> development/build/sdk.atree:93: couldn't locate source file: bin/bcc_compat
> development/build/sdk.atree:134: couldn't locate source file: bin/apksigner
> development/build/sdk.atree:135: couldn't locate source file:
> framework/apksigner.jar
> development/build/sdk.atree:138: couldn't locate source file: bin/dx
> development/build/sdk.atree:139: couldn't locate source file:
> framework/dx.jar
> development/build/sdk.atree:216: couldn't locate source file:
> framework/layoutlib-legacy.jar
> ninja: build stopped: subcommand failed.
> 13:52:36 ninja failed with: exit status 1
>
> I'd be happy to hear from you and offer what help i can :)
> Happy New Year,
> Konstantin
>
>
> On Thursday, December 27, 2018 at 11:20:29 PM UTC+2, Dan Willemsen wrote:
>>
>> Just like anything else you want installed, put it in PRODUCT_PACKAGES,
>> either in the core build system's core product makefiles, or in your
>> product's makefiles.
>>
>> I'm not sure why those builds are failing without more information -- at
>> least the normal SDK build is passing on our CI systems:
>> https://ci.android.com/builds/branches/aosp-master/grid (the sdk*
>> columns)
>>
>> - Dan
>>
>> On Thu, Dec 27, 2018 at 12:02 PM 
>> wrote:
>>
>>> Thank you, using 'm mkstubs' worked.
>>> Though normal building with sdk_addon or just sdk still doesn't.
>>>
>>> And if i want to build it automatically as part of the build similar to
>>> the doclava or other such jars.
>>> Where do i need to put it to work?
>>>
>>> On Thursday, December 27, 2018 at 12:34:54 AM UTC+2, Dan Willemsen wrote:
>>>>
>>>> You should be able to just run `m mkstubs` from any build configuration
>>>> to build mkstubs (as it's a host tool).
>>>>
>>>> It'll be in out/host/linux-x86/framework/mkstubs.jar (or darwin-x86 if
>>>> you're on a Mac) once built.
>>>>
>>>> - Dan
>>>

Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.

['Dan Willemsen' via Android Building]

You can actually hold the timestamp stable in system/build.prop too, by
setting the BUILD_DATETIME environment variable to a stable value (it's the
number of seconds since the unix epoch, normally generated with `date +%s`).

Since we've focused on keeping the individual files identical while
accepting a handful of known differences, the actual image generation may
not be as stable as we'd like it to be. That's just not as well tested, as
we've been mostly comparing individual files when converting make-based
functionality to our new build system.

- Dan

On Sun, Dec 23, 2018 at 8:18 AM Vitaliy Freidovich 
wrote:

> Hello,
>
> I would kindly disagree, as your environment might change from build to
> build, and the resulting images could theoretically, and perhapps
> practically, behave differently. Thus it's a correct bahaviour in my
> opinion that the checksum changes.
>
> Good luck,
>
> On Fri 21 Dec 2018, 5:58 p.m. ,  wrote:
>
>> Hi Android Experts,
>>
>>
>>
>>We need some help / information that, Is there any way
>> to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32]
>> same even after fresh build or recompilation??. Even though without
>> changing a single bit in the AOSP Source code if we rebuild it, Android
>> binaries checksum keeps changing. As I can understand that the
>> compilers/linkers adds the date and time-stamp to the images/binaries after
>> each build which causes the change in the checksum.  So my question, Is
>> there any way to avoid this change in image checksum after every rebuild.
>> it should change only when we change any source code. kindly update.
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-building+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Failing to build sdk and sdk_addon in master P

['Dan Willemsen' via Android Building]

You should be able to just run `m mkstubs` from any build configuration to
build mkstubs (as it's a host tool).

It'll be in out/host/linux-x86/framework/mkstubs.jar (or darwin-x86 if
you're on a Mac) once built.

- Dan

On Tue, Dec 18, 2018 at 1:46 PM 
wrote:

> Hey there,
>
> I am rather new to AOSP development and i am trying to build a sdk version
> and a sdk_addon but it fails.
> This is after i managed to build regularly successfully.
>
> I am using the *master branch* from google source.
> *lunch option*: aosp-arm64  userdebug
>
> *commands tried*:
> make sdk -j6
> make PRODUCT-sample_addon-sdk_addon -j6
>
> I was trying to understand how and where i get the *mkstubs* development
> tool to compile in P, as it is not being
> built in the the normal build option.
> After scouring the internet for answers but couldn't find any i thought
> maybe using these options
> will build them for me and i can get some more understanding on how to
> control which tool is built.
>
> Can you please explain why those builds fail for me and how i can add such
> development tools to the build?
>
> Thank you,
> Konstantin
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Does Android.bp include Android.bp work on Android P

['Dan Willemsen' via Android Building]

No, this is intentionally not supported by Android.bp. All Android.bp files
are always loaded.

First, instead of changing variable.go / soong_config.mk, we do have
extension points for user-defined plugins:
https://android.googlesource.com/platform/build/soong/+/0fe7866897b177f2bf7ec934c5615a2b48e48a23

For what you're trying to do, we suggest compiling against one interface
(HAL) and choosing one at runtime (you can have PRODUCT_PACKAGES &
soong_namespaces only install one of the two. If you're unwilling to create
a HAL, you could duplicate all of your build definitions inside
soong_namespaces, so that you have one set of libraries/binaries defined
for PLATFORM_SAMSUNG and another defined for PLATFORM_QCOM. That gets
really messy, though you can clean a bunch of it up with defaults &
filegroups.

- Dan

On Fri, Nov 30, 2018 at 4:43 PM wjjsun  wrote:

> I want to conditional compile one Android.bp module conditionally! if
> vendorA, use vendora.bp to compile, if vendorB, then use vendorb.bp to
> compile!
>
> Say I:
>
> 1. define a marco in BoardConfig.mk:
>
> TARGET_PLATFORM_VENDOR := vendorA or vendorB etc.
>
> 2. Then I change variable.go:
>
> type variableProperties struct {
> ...
> Platform_vendor struct {
> Cflags []string
> }
> ...
> type productVariables struct {
> Platform_vendor*string `json:",omitempty"`
>
> 3. And I change soong_config.mk:
> $(call add_json_str,  Platform_vendor,
> $(TARGET_PLATFORM_VENDOR))
>
> 4. Change Android.bp (I guess):
>
> cc_defaults {
> name: "my-defaults",
> defaults: [
> ],
>
> product_variables: {
> platform_vendor: {
> vendora: {
> include vendorA.bp
> cflags: ["-DPLATFORM_SAMSUNG"],
> },
> vendorb: {
> include vendorB.bp
> cflags: ["-DPLATFORM_QCOM"],
> }
> }
> }
> }
>
> I just write fake code here to include vendor.bp here! How can I write
> correct Android.bp to make it work?
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Build duration of AOSP

['Dan Willemsen' via Android Building]

I don't believe the Soong transition is directly causing the increase -- in
fact, as part of the transition we've enabled a number of optimizations. In
addition to a growing codebase, the build has gotten more complicated,
especially as Treble has been isolating the system and vendor partitions
(and Soong has enabled some of this).

We expect most developers to be using incremental builds, which are far
more reliable than they were a few years ago. On our CI systems, I saw the
times roughly double between Lollipop and Pie, but incremental builds on
average are faster than the Lollipop builds were (HW upgrades make it
difficult to make comparisons over time though).

Just interested, what are the units on the vertical axis? Seconds?

- Dan

On Fri, Dec 14, 2018 at 11:45 AM SZ Lee  wrote:

> Hi all
>
>
> As the below picture shows the build time of aosp_arm64-eng on my build
> machine,
>
> the full build time of Android Pie becomes longer than those of previous
> versions.
>
> And latest master branch takes even longer time than pie release.
>
>
> Could any one know the reason of the increase of the build time of aosp?
>
> Is it related with the build system change(make -> soong/bp) or is aosp
> getting complex with more features?
>
>
>
>
> [image: buildtime.png]
> Thanks
>
> SZ
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Integration of new lib in license files

['Dan Willemsen' via Android Building]

The hidl module types create new modules behind the scenes, and likely
aren't forwarding the notice property. Can you file a bug at
https://issuetracker.google.com/issues/new?component=381517 ? I can route
it appropriately.

Thanks,
Dan

On Thu, Nov 29, 2018 at 9:40 AM Sascha Effert  wrote:

> Hi Dan,
>
> thanks, I found my problem. The Android.bp files containing the cc_library
> and cc_binary entries I am adding are in subdirectories under the directory
> that contains my NOTICE file. Therefore they have not been detected
> correctly. I added now a
> notice: "../../NOTICE",
> and everything works as expected.
>
> I also added the enty to my hidl_interface and hidl_package_root
> definition, but the shared lib generated for my HIDL Interface is not added
> to the NOTICE.xml.gz. Do you have an idea what could be missing there?
>
> bests
>
> Sascha
>
>
> Am Donnerstag, 29. November 2018 00:17:11 UTC+1 schrieb Dan Willemsen:
>>
>> Is this a shared library (*.so installed)?
>>
>> The NOTICE file is the one that matters here, it needs to be in the same
>> directory as the Android.mk or Android.bp defining the library. You can
>> also specify one explicitly using `notice: "filename",` or
>> `LOCAL_NOTICE_FILE := filename`.
>>
>> - Dan
>>
>> On Wed, Nov 28, 2018 at 7:06 AM Sascha Effert 
>> wrote:
>>
>>> Hello,
>>>
>>> I added a new lib into our vendor HAL using soong. This is already
>>> running, it is part of our vendor Image and we can use it. The only problem
>>> left: added files or notmentioned in vendor.xml.gz in vendor/etc/, so the
>>> license information is missing. What is the way to get it in?
>>>
>>> I had a look into some other part of the AOSP (e.g. external/wayland)
>>> and saw that there is always an empty file starting with MODULE_LICENSE_
>>> (e.g. MODULE_LICENSE_GPL) and a file NOTICE with the lcense text. I added a
>>> file MODULE_LICENSE_BIOS and a file NOTICE with our license text to the lib
>>> directory, but it did not help.
>>>
>>> Is there somewhere an example how to add something to AOSP, so the
>>> license files are handled in the right way?
>>>
>>> bests
>>>
>>> Sascha
>>>
>>> --
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] FAILED: out/soong/.bootstrap/soong-android/test/android/soong/android.a

['Dan Willemsen' via Android Building]

This is an error within the go compiler. Which version of android are you
using, and what does `prebuilts/go/linux-x86/bin/go version` return?

- Dan

On Tue, Apr 2, 2019 at 8:51 AM  wrote:

>
> when i build  android code, found soong panic like this below:
>
> [ 49% 53/108] compile
> out/soong/.bootstrap/soong-android/test/android/soong/android.a
> FAILED: out/soong/.bootstrap/soong-android/test/android/soong/android.a
> GOROOT='prebuilts/go/linux-x86'
> prebuilts/go/linux-x86/pkg/tool/linux_amd64/compile -c 8 -o
> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp -p
> android/soong/android -complete -I
> out/soong/.bootstrap/blueprint-parser/pkg -I
> out/soong/.bootstrap/blueprint-deptools/pkg -I
> out/soong/.bootstrap/blueprint-pathtools/pkg -I
> out/soong/.bootstrap/blueprint-proptools/pkg -I
> out/soong/.bootstrap/blueprint/pkg -I
> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg -I
> out/soong/.bootstrap/blueprint-bootstrap/pkg -I
> out/soong/.bootstrap/soong/pkg -I out/soong/.bootstrap/soong-env/pkg -pack
> build/soong/android/androidmk.go build/soong/android/apex.go
> build/soong/android/api_levels.go build/soong/android/arch.go
> build/soong/android/config.go build/soong/android/defaults.go
> build/soong/android/defs.go build/soong/android/expand.go
> build/soong/android/filegroup.go build/soong/android/hooks.go
> build/soong/android/makevars.go build/soong/android/module.go
> build/soong/android/mutator.go build/soong/android/namespace.go
> build/soong/android/neverallow.go build/soong/android/onceper.go
> build/soong/android/package_ctx.go build/soong/android/paths.go
> build/soong/android/prebuilt.go build/soong/android/prebuilt_etc.go
> build/soong/android/proto.go build/soong/android/register.go
> build/soong/android/singleton.go build/soong/android/testing.go
> build/soong/android/util.go build/soong/android/variable.go
> build/soong/android/writedocs.go build/soong/android/env.go
> build/soong/android/config_test.go build/soong/android/expand_test.go
> build/soong/android/namespace_test.go
> build/soong/android/neverallow_test.go build/soong/android/paths_test.go
> build/soong/android/prebuilt_test.go
> build/soong/android/prebuilt_etc_test.go build/soong/android/util_test.go
> build/soong/android/variable_test.go && if cmp --quiet
> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp
> out/soong/.bootstrap/soong-android/test/android/soong/android.a; then rm
> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp; else
> mv -f out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp
> out/soong/.bootstrap/soong-android/test/android/soong/android.a; fi
> unexpected fault address 0xc003c08258
> fatal error: fault
> [signal SIGBUS: bus error code=0x2 addr=0xc003c08258 pc=0x61e5d4]
>
> goroutine 43 [running]:
> runtime.throw(0xc9db61, 0x5)
> prebuilts/go/linux-x86/src/runtime/panic.go:608 +0x72 fp=0xc0028302c8
> sp=0xc002830298 pc=0x42a9f2
> runtime.sigpanic()
> prebuilts/go/linux-x86/src/runtime/signal_unix.go:387 +0x2d7
> fp=0xc002830318 sp=0xc0028302c8 pc=0x43e587
> cmd/compile/internal/ssa.(*regAllocState).init(0xc0036df800, 0xc0025e7e40)
> prebuilts/go/linux-x86/src/cmd/compile/internal/ssa/regalloc.go:669 +0x634
> fp=0xc002830400 sp=0xc002830318 pc=0x61e5d4
> cmd/compile/internal/ssa.regalloc(0xc0025e7e40)
> prebuilts/go/linux-x86/src/cmd/compile/internal/ssa/regalloc.go:144 +0x4a
> fp=0xc002830428 sp=0xc002830400 pc=0x61c1ea
> cmd/compile/internal/ssa.Compile(0xc0025e7e40)
> prebuilts/go/linux-x86/src/cmd/compile/internal/ssa/compile.go:70 +0x30e
> fp=0xc002833e18 sp=0xc002830428 pc=0x5dc01e
> cmd/compile/internal/gc.buildssa(0xc00079cb00, 0x1, 0x0)
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/ssa.go:211 +0xab0
> fp=0xc002833f30 sp=0xc002833e18 pc=0xb33310
> cmd/compile/internal/gc.compileSSA(0xc00079cb00, 0x1)
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/pgen.go:259 +0x39
> fp=0xc002833f98 sp=0xc002833f30 pc=0xb003f9
> cmd/compile/internal/gc.compileFunctions.func2(0xc0025db4a0, 0xc000472740,
> 0x1)
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/pgen.go:323 +0x49
> fp=0xc002833fc8 sp=0xc002833f98 pc=0xbb4d99
> runtime.goexit()
> prebuilts/go/linux-x86/src/runtime/asm_amd64.s:1333 +0x1 fp=0xc002833fd0
> sp=0xc002833fc8 pc=0x457ae1
> created by cmd/compile/internal/gc.compileFunctions
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/pgen.go:321 +0x11a
>
> goroutine 1 [chan send]:
> cmd/compile/internal/gc.compileFunctions()
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/pgen.go:329 +0x171
> cmd/compile/internal/gc.Main(0xcc0f50)
> prebuilts/go/linux-x86/src/cmd/compile/internal/gc/main.go:647 +0x272f
> main.main()
> prebuilts/go/linux

Re: [android-building] Building APKs with minSdk in both AOSP and Android Studio

['Dan Willemsen' via Android Building]

In AOSP master, you should be able to set `min_sdk_version: "25"` in your
Android.bp (or `LOCAL_MIN_SDK_VERSION := 25` in an Android.mk). Older
branches you may need to do some workarounds with merging in another
manifest, but I think you'd only get the above error on master.

- Dan

On Tue, Apr 2, 2019 at 8:51 AM Baran Jean-Marie 
wrote:

> Hello,
>
> We have an APK which must define a minSdk version of at least 16 because
> of dependencies. Adding  in the
> AndroidManifest.xml works in the AOSP but not in Android Studio:
>
> The minSdk version should not be declared in the android manifest file.
>> You can move the version from the manifest to the defaultConfig in the
>> build.gradle file.
>>
>
> However, removing  works in
> Android Studio, but not in the AOSP:
>
> Error: Main manifest has  but library
>> uses minSdkVersion='16'
>>
>
> I tried as well with , but that only
> works for the AOSP. Is there a way to have a cross-build
> AndroidManifest.xml that would work for both the AOSP and Gradle? Because
> currently we have to manually edit it each time we want to build in Android
> Studio, which is not practical.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] FAILED: out/soong/.bootstrap/soong-android/test/android/soong/android.a

['Dan Willemsen' via Android Building]

I definitely recommend upgrade to at least the 4.4 kernel that is/was
supported with 14.04:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A14.04.x_Ubuntu_Kernel_Support

We, and a number of other build farms hit a SIGBUS in the kernel rather
frequently with 3.13, upgrading seems to fix it.

Ubuntu 14.04 itself is becoming EOL this month, so you may want to think
about upgrading to something newer -- modern android builds should be
fairly flexible, as long as you pick something with recent kernels.

- Dan

On Tue, Apr 2, 2019 at 8:04 PM  wrote:

>
> we use  android Q  compile ,  and  go version is :  go version go1.12.1
> linux/amd64
>
> tks;
>
> add the linux verison  and  kernel verison：
>
> lsb_release -a ：
>
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04 LTS
> Release:14.04
> Codename:   trusty
>
> uname -r  ：
> 3.13.0-24-generic
>
>
>
> 在 2019年4月3日星期三 UTC+8上午12:04:38，Dan Willemsen写道：
>>
>> This is an error within the go compiler. Which version of android are you
>> using, and what does `prebuilts/go/linux-x86/bin/go version` return?
>>
>> - Dan
>>
>> On Tue, Apr 2, 2019 at 8:51 AM  wrote:
>>
>>>
>>> when i build  android code, found soong panic like this below:
>>>
>>> [ 49% 53/108] compile
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a
>>> FAILED: out/soong/.bootstrap/soong-android/test/android/soong/android.a
>>> GOROOT='prebuilts/go/linux-x86'
>>> prebuilts/go/linux-x86/pkg/tool/linux_amd64/compile -c 8 -o
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp -p
>>> android/soong/android -complete -I
>>> out/soong/.bootstrap/blueprint-parser/pkg -I
>>> out/soong/.bootstrap/blueprint-deptools/pkg -I
>>> out/soong/.bootstrap/blueprint-pathtools/pkg -I
>>> out/soong/.bootstrap/blueprint-proptools/pkg -I
>>> out/soong/.bootstrap/blueprint/pkg -I
>>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg -I
>>> out/soong/.bootstrap/blueprint-bootstrap/pkg -I
>>> out/soong/.bootstrap/soong/pkg -I out/soong/.bootstrap/soong-env/pkg -pack
>>> build/soong/android/androidmk.go build/soong/android/apex.go
>>> build/soong/android/api_levels.go build/soong/android/arch.go
>>> build/soong/android/config.go build/soong/android/defaults.go
>>> build/soong/android/defs.go build/soong/android/expand.go
>>> build/soong/android/filegroup.go build/soong/android/hooks.go
>>> build/soong/android/makevars.go build/soong/android/module.go
>>> build/soong/android/mutator.go build/soong/android/namespace.go
>>> build/soong/android/neverallow.go build/soong/android/onceper.go
>>> build/soong/android/package_ctx.go build/soong/android/paths.go
>>> build/soong/android/prebuilt.go build/soong/android/prebuilt_etc.go
>>> build/soong/android/proto.go build/soong/android/register.go
>>> build/soong/android/singleton.go build/soong/android/testing.go
>>> build/soong/android/util.go build/soong/android/variable.go
>>> build/soong/android/writedocs.go build/soong/android/env.go
>>> build/soong/android/config_test.go build/soong/android/expand_test.go
>>> build/soong/android/namespace_test.go
>>> build/soong/android/neverallow_test.go build/soong/android/paths_test.go
>>> build/soong/android/prebuilt_test.go
>>> build/soong/android/prebuilt_etc_test.go build/soong/android/util_test.go
>>> build/soong/android/variable_test.go && if cmp --quiet
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a; then rm
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp; else
>>> mv -f out/soong/.bootstrap/soong-android/test/android/soong/android.a.tmp
>>> out/soong/.bootstrap/soong-android/test/android/soong/android.a; fi
>>> unexpected fault address 0xc003c08258
>>> fatal error: fault
>>> [signal SIGBUS: bus error code=0x2 addr=0xc003c08258 pc=0x61e5d4]
>>>
>>> goroutine 43 [running]:
>>> runtime.throw(0xc9db61, 0x5)
>>> prebuilts/go/linux-x86/src/runtime/panic.go:608 +0x72 fp=0xc0028302c8
>>> sp=0xc002830298 pc=0x42a9f2
>>> runtime.sigpanic()
>>> prebuilts/go/linux-x86/src/runtime/signal_unix.go:387 +0x2d7
>>> fp=0xc002830318 sp=0xc0028302c8 pc=0x43e587
>>> cmd/compile/internal/ssa.(*regAllocState).init(0xc0036df800,
>>> 0xc0025e7e40)
>>> prebuilts/go/linux-x86/src/cmd/compile/internal/ssa/regalloc.go:669
>>> +0x634 fp=0xc002830400 sp=0xc0

Re: [android-building] Flashing AOSP master on Pixel failed (Android Q)

['Dan Willemsen' via Android Building]

Had you downloaded the appropriate device blobs from here:
https://developers.google.com/android/blobs-preview ?

- Dan

On Sun, Mar 24, 2019 at 9:21 AM Yuan Zhou  wrote:

> I am flashing the original AOSP master to my Pixel. I used many methods
> but still failed.
>
> I make AOSP used following command:
> lunch aosp_sailfish-userdebug
> make -j48 (make updatepackage after that)
>
> *Method one:*
> WIPE system/cache/dalvik from twrp.
> fastboot flash boot boot.img
> fastboot flash system system.img
> fastboot flash userdata userdata.img
> fastboot flash vendor vendor.img (from factory image, because there is no
> vendor.img after make -j48 in the out/target/product/saifish directory)
> When it boot, it stuck at android Logo forever.
>
> *Mehthod two:*
> WIPE system/cache/dalvik from twrp.
> fastboot flashall -w  (from the out/target/product/sailfish directory I
> made.)
> When it boot, it stuck at android Logo forever.
>
> *Method three:*
> WIPE system/cache/dalvik from twrp.
> fastboot update aosp_sailfish-img-eng.zip (from make updatepackage command)
> When it boot, it stuck at android Logo forever.
>
> *Method four:*
> Install the  aosp_sailfish-img-eng.zip from twrp, i got the log:
> Installing zip file '/sdcard/aosp_sailfish-img-eng.zip'
> Checking for Digest file...
> Skipping Digest check: no Digest file found
> Invalid zip file format!
> Error installing zip file  '/sdcard/aosp_sailfish-img-eng.zip'
> updating partition details...
> done
>
> Anyone can help, PLZ. Thank you 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] No ram.img file after successfully building AOSP

['Dan Willemsen' via Android Building]

To run the emulator, you'll need to build for one of the
aosp_arm/aosp_arm64/aosp_x86/aosp_x86_64 targets -- aosp_blueline only
works with the real device.

- Dan

On Thu, Mar 28, 2019 at 8:35 AM  wrote:

>  build completed successfully (05:33:52 (hh:mm:ss)) 
>
> im running the emulator command in my AOSP folder. Not sure why the
> ram.img isnt built. For the Google Pixel 3 - blueline.
>
>
> emulator
> emulator: WARNING: Couldn't find crash service executable
> AOSP/prebuilts/android-emulator/linux-x86_64/emulator64-crash-service
>
> emulator: WARNING: system partition size adjusted to match image file
> (1018 MB > 800 MB)
>
> statvfs('AOSP/out/target/product/blueline/snapshots/default_boot/ram.img')
> failed: No such file or directory
> emulator: WARNING: encryption is off
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] build java+kolin library with build.bp failed

['Dan Willemsen' via Android Building]

I'm not sure what's happening here, but a few questions/comments:

What Android version are you using?

srcs: [
> "*.java",
> "*.kt",
> "**/*.java",
> "**/*.kt",
> ],


This will duplicate the list of java and kotlin files in the current
directory, since ** will match both the current directory and all
subdirectories. I can't see how that would cause this problem, but it's a
good thing to clean up.

- Dan

On Mon, Mar 11, 2019 at 10:07 PM Ted Jiang  wrote:

> this is my build.bp:
>
> java_library_static {
> name: "mylib",
>
> srcs: [
> "*.java",
> "*.kt",
> "**/*.java",
> "**/*.kt",
> ],
>
>
> optimize: {
> enabled: false,
> },
>
> }
>
>
> but it yields very strange errors when building, like:
>
> SysProperty.kt:9:16: error: type mismatch: inferred type is
> java.lang.String! but kotlin.String was expected
> return SystemProperties.get(key)
>^
> SysProperty.kt:9:33: error: cannot access class 'java.lang.String'. Check
> your module classpath for missing or conflicting dependencies
> return SystemProperties.get(key)
> ^
> SysProperty.kt:9:37: error: type mismatch: inferred type is kotlin.String
> but java.lang.String! was expected
> return SystemProperties.get(key)
> ^
> SysProperty.kt:14:16: error: type mismatch: inferred type is
> java.lang.String! but kotlin.String was expected
> return SystemProperties.get(key, def)
>^
> SysProperty.kt:14:33: error: cannot access class 'java.lang.String'. Check
> your module classpath for missing or conflicting dependencies
> return SystemProperties.get(key, def)
> ^
> SysProperty.kt:14:37: error: type mismatch: inferred type is kotlin.String
> but java.lang.String! was expected
> return SystemProperties.get(key, def)
> ^
> SysProperty.kt:14:42: error: type mismatch: inferred type is kotlin.String
> but java.lang.String! was expected
> return SystemProperties.get(key, def)
>  ^
> SysProperty.kt:19:33: error: cannot access class 'java.lang.String'. Check
> your module classpath for missing or conflicting dependencies
> return SystemProperties.set(key, value)
> ^
>
> TelephonyMgr.kt:11:48: error: cannot access class 'java.lang.Object'.
> Check your module classpath for missing or conflicting dependencies
> getContext().getSystemService(Context.TELEPHONY_SERVICE) as
> TelephonyManager
>^
> TelephonyMgr.kt:11:48: error: cannot access class 'java.lang.String'.
> Check your module classpath for missing or conflicting dependencies
>
> CoreApi.getInstance().getContext().getSystemService(Context.TELEPHONY_SERVICE)
> as TelephonyManager
>
>
> It looks like some standard java classes are missing, such as
> java.lang.String, java.lang.Object,  but why?
>
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] error of "libLLVM_host" depends on undefined module "libLLVM_darwin" reported

['Dan Willemsen' via Android Building]

We don't maintain the -darwin group -- in general, if you have a manifest
that hasn't been carefully stripped down, you may need to specify
ALLOW_MISSING_DEPENDENCIES=true, but that may only push the error until
later in the build process (and won't work in this case).

In this case, it looks like the change in behavior was due to this soong
change:
https://android-review.googlesource.com/c/platform/build/soong/+/920955
(the parent change is the implementation). We're now adding dependencies to
all the referenced modules, even if they're in target: { darwin: { ... } }
blocks that will never be used in the current build. While that can be a
good thing (you're less likely to cause an instant build failure on Mac due
to a typo), it is a problem for these types of use cases.

I've filed a public bug to track this:
https://issuetracker.google.com/128377112

Thanks for the report,
Dan

On Mon, Mar 11, 2019 at 8:35 PM Yongqin Liu  wrote:

> Hi, All
>
> With the latest AOSP master source, if I repo init with '-darwin' group
> excluded on my Ubuntu host,
>
> then I will got my following errors reported:
>
> 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: prebuilts/clang/host/linux-x86/Android.bp:585:1: "libLLVM_host"
> depends on undefined module "libLLVM_darwin"
> error: prebuilts/clang/host/linux-x86/Android.bp:619:1: "libc++abi_host"
> depends on undefined module "libc++abi_darwin"
> error: prebuilts/clang/host/linux-x86/Android.bp:595:1:
> "libclang_cxx_host" depends on undefined module "libclang_cxx_darwin"
> error: prebuilts/clang/host/linux-x86/Android.bp:605:1: "libc++_host"
> depends on undefined module "libc++_darwin"
> ninja: build stopped: subcommand failed.
> 23:14:17 soong bootstrap failed with: exit status 1
>
>
> I found that libLLVM_darwin module is defined in project of
> prebuilts/clang/host/darwin-x86/,
> but does those modules defined in prebuilts/clang/host/linux-x86 really
> depends on the modules defined in prebuilts/clang/host/darwin-x86?
> and it worked before(one week ago?) without
> prebuilts/clang/host/darwin-x86 repo synced.
> Could  anyone please help to check on that?
>
> Thanks,
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] failed to build some targets - libncurses.so.5: cannot open shared object file: No such file or dire

['Dan Willemsen' via Android Building]

It looks like you need to install libncurses5 (sudo apt install
libncurses5), as that's the package that provides the 64-bit
libncurses.so.5 on Ubuntu 18.04.

Let me know if that fixes the issue and we'll add it to the instructions on
source.android.com.

Thanks,
Dan

On Thu, Mar 7, 2019 at 7:40 AM  wrote:

> Trying to build AOSP for blueline
> Ive followed the build instructions several times, requirements,
> establishing build environment and so forth. Also included the vendor
> binaries. And I always run into this issue. I do run Ubuntu 18.10, should I
> roll back to 18.04 or even 14.04?
>
>
> make clobber
> 09:31:35 Entire build directory removed.
>
>  build completed successfully (1 seconds) 
>
> source build/envsetup.sh
>
> lunch aosp_blueline-userdebug
>
> 
> PLATFORM_VERSION_CODENAME=Q
> PLATFORM_VERSION=Q
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-2a
> TARGET_CPU_VARIANT=kryo385
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-2a
> TARGET_2ND_CPU_VARIANT=kryo385
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.18.0-15-generic-x86_64-Ubuntu-18.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PI
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av
> hardware/google/interfaces hardware/qcom/sdm845 vendor/qcom/sdm845
>
>
>
>
> make -j12
>
> 
> PLATFORM_VERSION_CODENAME=Q
> PLATFORM_VERSION=Q
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-2a
> TARGET_CPU_VARIANT=kryo385
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-2a
> TARGET_2ND_CPU_VARIANT=kryo385
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.18.0-15-generic-x86_64-Ubuntu-18.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PI
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av
> hardware/google/interfaces hardware/qcom/sdm845 vendor/qcom/sdm845
> 
> [100% 734/734] writing build rules ...
> build/make/core/dex_preopt_libart.mk:10: warning: overriding commands for
> target `out/target/product/blueline/system/etc/boot-image.prof'
> build/make/core/dex_preopt_libart.mk:10: warning: ignoring old commands
> for target `out/target/product/blueline/system/etc/boot-image.prof'
> build/make/core/Makefile:28: warning: overriding commands for target
> `out/target/product/blueline/vendor/etc/IPACM_cfg.xml'
> build/make/core/base_rules.mk:435: warning: ignoring old commands for
> target `out/target/product/blueline/vendor/etc/IPACM_cfg.xml'
> [  1% 2115/106550] Target buildinfo:
> out/target/product/blueline/obj/ETC/system_build_prop_intermediates/build.prop
> Target buildinfo from: device/google/crosshatch/system.prop
> [  2% 3106/106550] bc: libclcore.bc <=
> frameworks/rs/driver/runtime/rs_core.c
> FAILED:
> out/target/product/blueline/obj/RENDERSCRIPT_BITCODE/libclcore.bc_intermediates/rs_core.bc
> /bin/bash -c "PWD=/proc/self/cwd
> prebuilts/clang/host/linux-x86/clang-3289846/bin/clang
> -Iframeworks/rs/script_api/include -Iexternal/clang/lib/Headers -MD
> -DRS_VERSION=24 -std=c99 -c -O3 -fno-builtin -emit-llvm -target
> renderscript64-linux-android -fsigned-char  -Wno-deprecated -Werror
> -Werror -Wall -Wextra -Iframeworks/rs/cpu_ref -DRS_DECLARE_EXPIRED_APIS
> -DARCH_ARM64_HAVE_NEON -x renderscript
> frameworks/rs/driver/runtime/rs_core.c -o
> out/target/product/blueline/obj/RENDERSCRIPT_BITCODE/libclcore.bc_intermediates/rs_core.bc"
> prebuilts/clang/host/linux-x86/clang-3289846/bin/clang.real: error while
> loading shared libraries: libncurses.so.5: cannot open shared object file:
> No such file or directory
> [  2% 3107/106550] bc: libclcore.bc <=
> frameworks/rs/driver/runtime/rs_allocation.c
> FAILED:
> out/target/product/blueline/obj/RENDERSCRIPT_BITCODE/libclcore.bc_intermediates/rs_allocation.bc
> /bin/bash -c "PWD=/proc/self/cwd
> prebuilts/clang/host/linux-x86/clang-3289846/bin/clang
> -Iframeworks/rs/script_api/include -Iexternal/clang/lib/Headers -MD
> -DRS_VERSION=24 -std=c99 -c -O3 -fno-builtin -emit-llvm -target
> renderscript64-linux-android -fsigned-char  -Wno-deprecated -Werror
> -Werror -Wall -Wextra -Iframeworks/rs/cpu_ref -DRS_DECLARE_EXPIRED_APIS
> -DARCH_ARM64_HAVE_NEON -x renderscript
&g

Re: [android-building] Question about PRODUCT_HOST_PACKAGES and PRODUCT_PACKAGES

['Dan Willemsen' via Android Building]

The behavior up until a few weeks ago was to build everything in
PRODUCT_PACKAGES for both host and device. I'm in the process of splitting
them up, but right now that means that you need to add them to both
PRODUCT_PACKAGES and PRODUCT_HOST_PACKAGES. I hope to fully disconnect them
this week, so that you can add it to PRODUCT_PACKAGES, but not
PRODUCT_HOST_PACKAGES, and get it installed only for the device.

Sorry for the complication,
Dan

On Mon, Mar 18, 2019 at 7:28 AM Po Hu  wrote:

> When I try to add a target binary called badblocks (defined
> https://android.googlesource.com/platform/external/e2fsprogs/+/refs/heads/master/misc/Android.bp#157)
> into image.
> "PRODUCT_PACKAGES += badblocks" will show this error:
> build/make/core/main.mk:1182: warning: Missing modules from
> PRODUCT_HOST_PACKAGES
> build/make/core/main.mk:1183: warning: See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PRODUCT_HOST_PACKAGES
> for more information
> build/make/core/main.mk:1184: warning: _ badblocks
> build/make/core/main.mk:1185: error: stop.
>
> Because badblocks happens to be a "host_supported" binary too.
> How to make only the target one installed ?
> I don't want to use "PRODUCT_HOST_PACKAGES += badblocks" to generate extra
> host binary.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

['Dan Willemsen' via Android Building]

The ninja compilation database support doesn't work very well for our ninja
files due to kati using a rule per command. This upstream ninja feature
request may help, but that's assuming that whatever is parsing the compdb
files can understand the raw rules (which is usually a bash script, not
just a call to the compiler):
https://github.com/ninja-build/ninja/issues/1377

I'd recommend converting to Android.bp so that you can use SOONG_GEN_COMPDB.

- Dan

On Mon, Mar 18, 2019 at 9:54 AM  wrote:

> I can get CMakeLists.txt from Android.bp by soong, then get
> compile_commands, but cann't get CMakeLists.json from android.mk. I've
> tried pass ' -t compdb cxx' but just get empty "[ \n ]" , any one can help
> me?
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] ckati takes very long during regenerating of something...

['Dan Willemsen' via Android Building]

Which branch are you working on? verbose.log.gz is new in master(Q), before
then, the ckati info should be in soong.log.

I believe the persist-after-ctrl-c behavior should also be gone in master,
but I haven't done any extensive testing to make sure.

- Dan

On Fri, Mar 22, 2019, 6:49 AM  wrote:

> I got the same problem and there's no verbose.log.gz in my out dir, I
> don't know why, but I can offer some clue, this happens when I change some
> overlay xmls and modify the overlay order in device.mk. I got a intel i7
> CPU, 16GB memory and 1TB ssd. The top shows I never seen AOSP generate
> ninja files that long.
>
> The important thing I find is that if I use ctrl-c to terminate the build
> procedure, the ckati process will remains, and if I restart a build
> procedure, there are two ckati process and each of them takes 100% of cpu
> power, but the build will still stuck at "generating..."
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] missing and no known rule to make it

['Dan Willemsen' via Android Building]

This forum is for discussing building AOSP, not custom ROMs, so I can't
help you with what missing. But decoding the error message:

ninja: error:
'/home/vamsi/ctos/out/target/common/obj/JAVA_LIBRARIES/sap-api-java-static_intermediates/classes-header.jar',
needed by
'/home/vamsi/ctos/out/target/common/obj/APPS/Bluetooth_intermediates/classes-full-debug.jar',
missing and no known rule to make it

is the same error as:

packages/apps/Bluetooth/Android.mk: error: Bluetooth (APPS android-arm64)
missing sap-api-java-static (JAVA_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
intentional, *but that may defer real problems until later in the build.*

ALLOW_MISSING_DEPENDENCIES does not completely ignore missing dependencies,
it just allows you to continue building things that do have all of their
dependencies satisfied. Your build is attempting to build the Bluetooth
app, so you need to fix that missing dependency.

- Dan


On Thu, Feb 14, 2019 at 7:19 AM Vamsee Krishnaa <
vamsikrishna481...@gmail.com> wrote:

>
>
> vamsi@vamsi:~/ctos$ mka bacon -j8
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=9
> CUSTOM_VERSION=ctosp_hydrogen-9.0-20190209-0450-UNOFFICIAL
> TARGET_PRODUCT=ctosp_hydrogen
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=cortex-a53
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=cortex-a53.a57
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-Ubuntu-18.04.1-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PQ1A.190105.004
> OUT_DIR=/home/vamsi/ctos/out
> PRODUCT_SOONG_NAMESPACES= hardware/qcom/audio-caf/msm8952
> hardware/qcom/display-caf/msm8952 hardware/qcom/media-caf/msm8952
> 
> ninja: no work to do.
> ninja: no work to do.
> Environment variable BUILD_NUMBER was modified (ed118bb6ca => 74517f),
> regenerating...
> /home/vamsi/ctos/out/build-ctosp_hydrogen.ninja is missing, regenerating...
> [535/951] including system/sepolicy/Android.mk ...
> system/sepolicy/Android.mk:88: warning: Be careful when using the
> SELINUX_IGNORE_NEVERALLOWS flag. It does not work in user builds and using
> it will not stop you from failing CTS.
> [951/951] including vendor/xiaomi/msm8956-common/Android.mk ...
> device/xiaomi/msm8956-common/camera/QCamera2/Android.mk: error:
> camera.msm8952 (SHARED_LIBRARIES android-arm) missing libqdMetaData
> (SHARED_LIBRARIES android-arm)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> device/xiaomi/msm8956-common/camera/QCamera2/Android.mk: error:
> camera.msm8952 (SHARED_LIBRARIES android-arm) missing libqservice
> (SHARED_LIBRARIES android-arm)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> external/wpa_supplicant_8/hostapd/Android.mk: error: hostapd (EXECUTABLES
> android-arm64) missing lib_driver_cmd_qcwcn (STATIC_LIBRARIES
> android-arm64)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> external/wpa_supplicant_8/hostapd/Android.mk: error: hostapd_nohidl
> (EXECUTABLES android-arm64) missing lib_driver_cmd_qcwcn (STATIC_LIBRARIES
> android-arm64)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> external/wpa_supplicant_8/wpa_supplicant/Android.mk: error: wpa_supplicant
> (EXECUTABLES android-arm64) missing lib_driver_cmd_qcwcn (STATIC_LIBRARIES
> android-arm64)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> frameworks/opt/net/wifi/libwifi_hal/Android.mk: error: libwifi-hal
> (SHARED_LIBRARIES android-arm64) missing libwifi-hal-qcom (STATIC_LIBRARIES
> android-arm64)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> frameworks/opt/net/wifi/libwifi_hal/Android.mk: error: libwifi-hal
> (SHARED_LIBRARIES android-arm64) missing libcld80211 (SHARED_LIBRARIES
> android-arm64)
> You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is
> intentional, but that may defer real problems until later in the build.
> frameworks/opt/net/wifi/libw

Re: [android-building] Information about prebuilt ckati

['Dan Willemsen' via Android Building]

There's a manifest.xml in that project that should have all of the exact
revisions:
https://android.googlesource.com/platform/prebuilts/build-tools/+/refs/heads/master/manifest.xml.
It's a snapshot of the platform/manifest build-tools manifest
<https://android.googlesource.com/platform/manifest/+/build-tools>.

It's built using the prebuilts/build-tools/build-prebuilts.sh
<https://android.googlesource.com/platform/prebuilts/build-tools/+/master/build-prebuilts.sh>
script, and you can get the full artifacts from the aosp-build-tools branch
on ci.android.com
<https://ci.android.com/builds/branches/aosp-build-tools/grid?>. The commit
message updating the prebuilts should reference a build number that can be
found on ci.android.com.

- Dan

*From: *Rounak Agarwal 
*Date: *Sun, May 12, 2019, 11:01 PM
*To: *Android Building

Is there a way to find out the exact commit and the build command used to
> build the prebuilt ckati executable available in AOSP project
> prebuilts/build-tools ?
>
> --
> --
> 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/3f2f33e5-e805-4194-9595-4cd9f3c4798f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/3f2f33e5-e805-4194-9595-4cd9f3c4798f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Please help me!Thanks!

['Dan Willemsen' via Android Building]

As I posted before: "Please don't do that, your build will fail in some
other way, since that check is there to ensure that the two build systems
agree about options that they both need to use."

- Dan

On Mon, May 13, 2019 at 12:36 PM Old3nglish 800 <0ld3nglish...@gmail.com>
wrote:

> Thank you, was helpful.
>
> On Saturday, December 9, 2017 at 11:51:46 PM UTC-8, quake73 wrote:
>>
>> In the file build/soong/android/makevars.go, there are these 3 lines:
>>
>> ifneq ($(my_check_failed),false)
>>   $(error Soong variable check failed)
>> endif
>>
>> Either remove them or just comment out the 2nd line ( # $(error Soong
>> variable check failed) )
>>
>> On Fri, Dec 8, 2017 at 12:46 PM,  wrote:
>>
>>> When I builing the AOSP for my device ,I have a problem that I can't
>>> slove
>>>
>>>
>>> home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning:
>>> TARGET_GLOBAL_CFLAGS does not match between Make and Soong:
>>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Make :
>>> -DNO_SECURE_DISCARD
>>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:362: warning: Soong:
>>> -fno-exceptions -Wno-multichar -fno-strict-aliasing
>>> -fstack-protector-strong -ffunction-sections -fdata-sections
>>> -funwind-tables -Wa,--noexecstack -Werror=format-security
>>> -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes
>>> -fno-canonical-system-headers -Werror=pointer-to-int-cast
>>> -Werror=int-to-pointer-cast -Werror=implicit-function-declaration
>>> -fno-strict-volatile-bitfields -DNDEBUG -O2 -g -Wstrict-aliasing=2
>>> -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DANDROID
>>> -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith
>>> -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd= -fdiagnostics-color
>>> -Werror=return-type -Werror=non-virtual-dtor -Werror=address
>>> -Werror=sequence-point -Werror=date-time -mcpu=cortex-a53
>>> /home/jack/Mokee/O/out/soong/make_vars-mk_N939St.mk:810: error: Soong
>>> variable check failed.
>>> 18:19:38 ckati failed with: exit status 1
>>> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
>>> make: *** [run_soong_ui] Error 1
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/c50b27cd-7392-46c3-a9d0-d6d8dc8e380c%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/c50b27cd-7392-46c3-a9d0-d6d8dc8e380c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] Information about prebuilt ckati

['Dan Willemsen' via Android Building]

Strange. Are you able to do regular builds of AOSP master on your machine?
(If not, don't worry, it's just a data point if you have)

What does the end of out/soong.log look like? That'll narrow down the
problem.

If you have a slow disk, the first time you run this, it may take a while
as it builds up a database of the files in the source tree, but it
shouldn't take that long (on a sufficiently fast machine that should only
take a few seconds). If you happen to have mounts / hard links / etc that
expose more files or a network mount inside the source tree, we've seen
hangs when we generate this db.

- Dan

*From: *Rounak Agarwal 
*Date: *Mon, May 13, 2019 at 9:10 AM
*To: *Android Building

Thanks for the information Dan.
>
> I wanted to try and build the binaries myself. I did the following :
>
> repo init -u https://android.googlesource.com/platform/manifest -b build-tools
> repo sync -c
> export OUT_DIR=$PWD/out
> ./prebuilts/build-tools/build-prebuilts.sh
>
>
> It got stuck at the following command :
>
> build/soong/soong_ui.bash --make-mode --skip-make 
>
> Do you know what might be the reason for this ?
>
>
> On Monday, May 13, 2019 at 11:38:42 AM UTC+5:30, Dan Willemsen wrote:
>>
>> There's a manifest.xml in that project that should have all of the exact
>> revisions:
>> https://android.googlesource.com/platform/prebuilts/build-tools/+/refs/heads/master/manifest.xml.
>> It's a snapshot of the platform/manifest build-tools manifest
>> <https://android.googlesource.com/platform/manifest/+/build-tools>.
>>
>> It's built using the prebuilts/build-tools/build-prebuilts.sh
>> <https://android.googlesource.com/platform/prebuilts/build-tools/+/master/build-prebuilts.sh>
>> script, and you can get the full artifacts from the aosp-build-tools
>> branch on ci.android.com
>> <https://ci.android.com/builds/branches/aosp-build-tools/grid?>. The
>> commit message updating the prebuilts should reference a build number that
>> can be found on ci.android.com.
>>
>> - Dan
>>
>> *From: *Rounak Agarwal 
>> *Date: *Sun, May 12, 2019, 11:01 PM
>> *To: *Android Building
>>
>> Is there a way to find out the exact commit and the build command used to
>>> build the prebuilt ckati executable available in AOSP project
>>> prebuilts/build-tools ?
>>>
>>> --
>>> --
>>> 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/3f2f33e5-e805-4194-9595-4cd9f3c4798f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/3f2f33e5-e805-4194-9595-4cd9f3c4798f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/6b01612c-d7f0-4388-ad71-0e274cea912f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/6b01612c-d7f0-4388-ad71-0e274cea912f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [android-building] [Android Q] Question about new constraint for build system

['Dan Willemsen' via Android Building]

It's easy to use prebuilt tools from the source directory (or built tools)
from your own rules that need them, either just refer to them by name, or
you may be able to set up your own directory to be added to PATH inside a
rule:

https://android.googlesource.com/device/ti/beagle-x15/+/7001c965a5d6792c04fd94838161cd6116c605cf/uboot.mk#151
https://android.googlesource.com/device/ti/beagle-x15/+/7001c965a5d6792c04fd94838161cd6116c605cf/hostcc#

We're not going to add an extension that allows modifying the environment
of every build command -- that causes problems with the attempts to build
common system images that aren't influenced by the device. The common build
commands should not need anything except our standard tools -- if you've
modified them, it should be easy enough to also add the dependency to the
new tools as well.

On tools:

   - We've deprecated GCC during Android builds, we recommend clang for
   compilation.
   - We do have prebuilts of `make` and some other common tools in
   prebuilts/build-tools/linux-x86/bin
   - ccache is not something that we provide anymore -- we've found it's
   generally better to use incremental builds, as ccache can slow down your
   builds with extra I/O, and incremental builds should have relatively few
   cache hits (unless you're sharing the ccache dir; which runs into even more
   I/O issues).
   - Perl is not something supported at Google, so we don't provide that
   either -- we do have built in support for python and the ability to use
   python packages from the source tree (or checked in as a prebuilt, when
   using embedded_launcher, it's a self-contained binary):
   
https://ci.android.com/builds/submitted/5527387/linux/latest/python.html#python_binary_host

- Dan

On Thu, May 2, 2019 at 9:05 PM Niklaus Lin (林洲銓) 
wrote:

> Hi Android build team,
>
>
>
> This is Android team from Mediatek.
>
> We have a question that needs your advice and suggestion
>
>
>
> According to
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> <https://www.google.com/url?q=https://android.googlesource.com/platform/build/%2B/master/Changes.md%23PATH_Tools=D=AFQjCNEgF30xA0aFxiIvkb6lDKv0URcQxQ>
> ,
>
> There is a new constraint for build system in order to ensure the build
> results are reproducible across different machines.
>
>
>
> Problem occurs when we try to combine our build flow with Android source
> code.
>
> When we compile our proprietary modules using ARM GNU toolchains or some
> unix tool, we meet compiling errors because of the constraint mentioned
> above.
>
> The error log shows ‘Disallowed PATH Tool “xxx” used …’ , and these tools
> are make, cache, perl,… , used by ARM GNU toolchains or shell command in
> build flow.
>
> We found that these tools were disallowed because they were fallen into
> Forbidden or Missing case, defined in build/soong/ui/build/paths/config.go
>
> the detail analysis can be referenced by attachment : 3rd tools error
> analysis.docx
>
>
>
> Is it possible Google create a customization mechanism for vendor to add
> the proprietary build tool in Android source? e.g. add a new path variable
> (/vendor/prebuilts/build-tools) to vendor folder then vendor can add vendor
> build tool in it.
>
> and these vendor build tool can be excepted in constraint rule.
>
>
>
> for this question, we also have some discussion in this buganizer issue.
>
> https://partnerissuetracker.corp.google.com/u/1/issues/123787813
>
>
>
>
>
> BRs,
>
> Feng Lin
>
> * MEDIATEK Confidentiality Notice 
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. 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
&g

Re: [android-building] Android AOSP sepolicy not updated while Editing Seliunx Rule

['Dan Willemsen' via Android Building]

What version of Android are you using?

Which file did you change? There may be some missing dependencies.

- Dan

On Fri, Jul 12, 2019 at 5:13 AM xie doye  wrote:

> I'm trying to customize the AOSP, And After compiled success once, I
> changed some selinux rule due to Android SElinux implementation
> <https://source.android.com/security/selinux/implement#steps>, And after
> that, I turn into AOSP root directory and run m, It indeed find some diff
> and seems compiled a new boot.img(due to time it generated), But After I
> flash it with fastboot flashall -w the dmesg still showing the avc
> sepolicy failed which I was just added
>
>
> So the question is Am I doing wrong with the routine?  Or Is there any
> mechanism I was ignored? If that What should I do?(Now I'm *m clean* and
> recompile all with *m* and problem gone, But it just takes hours)
>
>
> PS: I've found the policy.conf file under /out
> /target/product/marlin/obj/ETC/sepolicy_neverallows_intermediates and it
> sync with what I changed?
>
>
>
> --
> --
> 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/cfa4dd5b-41a7-44ac-8fe8-78db1453ea21%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/cfa4dd5b-41a7-44ac-8fe8-78db1453ea21%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] $shell commands in Android.mk -> Android.bp migration.

['Dan Willemsen' via Android Building]

What is your pre-build-script.sh script doing? Right now, since it has no
dependencies and no output files, you're essentially running it on every
build, even when the user is only trying to compile a single file in a
different section of the tree. That's deprecated since it has a huge
performance impact.

Generally, if this is something that takes inputs and produces output
files, you may be able to use a genrule. But without knowing anything about
what this script is doing, I can't help much more than that.

- Dan



On Tue, Aug 20, 2019 at 2:40 PM Frederic Plourde 
wrote:

> Hi android building !
>
>
>   I used to have this in one of my Android.mk makefiles :
>
> $(shell (cd $(LOCAL_PATH)/../../ && ./pre-build-script.sh))
>
>
> but I just noticed that this practice is now discouraged on the Soong
> Android.bp build system
>
> From the Build System Best Practices
> <https://android.googlesource.com/platform/build/soong/+/HEAD/docs/best_practices.md>
> document,  I could read :
>
> Don't use $(shell) to write files, create symlinks, etc. We expect to
> enforce this in the future. Encode these as build rules in the build graph
> instead. This can be problematic in a number of ways:
>
>
> Could you give me a concrete example of how I could run this
> "pre-build-script.sh" shell script before *every* build in my new
> Android.bp file ?
>
> thx :)
>
>
> *Frederic Plourde*
> Principal Engineer
> Collabora ltd.
>
> --
> --
> 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/1131b0a7-0656-4813-9226-c233f3c2a05c%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/1131b0a7-0656-4813-9226-c233f3c2a05c%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/CALQgHdmerW-%2BZ6GeKJKuakgmdLD%3DQLmNPY_EWLVixbm%2BLM117w%40mail.gmail.com.

Re: [android-building] Build not picking up changes in Android.bp

['Dan Willemsen' via Android Building]

No, there's nothing you need to do. vendor_available defines two
installations -- one into the vendor partition and one into the system
partition. To trigger the installation of the vendor version, you may need
to specify `m .vendor` instead of `m `

If you don't need both copies of the module, use `vendor: true` instead of
vendor_available. You may still need the .vendor on the command line, I
don't remember.

- Dan

On Fri, Aug 30, 2019 at 10:37 AM Donal Morrissey 
wrote:

> Hi There,
> This is my setup:
>
>- AOSP branch: android-9.0.0_r46
>- Target: generic_x86_64
>
> I'm currently working on an Android example HIDL interface, with
> accompanying client and server processes. These are all created in a new
> vendor directory structure at the top level of the repo checkout.:
> vendor/
> └── horizonemb
> ├── clients
> │   └── example_client
> │   ├── Android.bp
> │   └── exampleClient.cpp
> └── interfaces
> ├── Android.bp
> └── example
> └── 1.0
> ├── Android.bp
> ├── default
> │   ├── Android.bp
> │   ├── Example.cpp
> │   ├── Example.h
> │   ├── service.cpp
> │   └── vendor.horizonemb.hardware.exam...@1.0-service.rc
> └── IExample.hal
>
>
> If I change the VNDK related properties (vendor_available, etc) in any of
> my Android.bp files, their installation destination (/vendor v's /system)
> does not change when I build with the '*m*' command. I have to first
> delete the out directory and then carry out a full build.
>
> After modifying an Android.bp file, is there some other command I need to
> run before I build with the '*m*' command?
>
> Thank you,
> Donal
>
> --
> --
> 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/ee745977-4c3e-428a-9825-2fd2ffafab77%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ee745977-4c3e-428a-9825-2fd2ffafab77%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/CALQgHdkEN_s0My8gektb6Y-ihExgDm9_Z36aBzAaYar1uQK3ew%40mail.gmail.com.

Re: [android-building] Some questions on Android.bp files

['Dan Willemsen' via Android Building]

1. Which version of Android are you building against? host_required is only
supported on AOSP master. Unknown properties are errors, as they're often
typos.

2. Including Android.mk files from Android.bp files doesn't make sense,
what are you trying to do?

We do forbid all path references that use ".." to escape the current
directory however -- you either need to use a filegroup and a module
reference ":filegroup_name", or move the contents of the Android.bp up a
level. We saw this a lot in applications that had:

   foo/res/...
   foo/src/...
   foo/test/...

And had Android.mk files in the src and test directories that were using
"../" to access the other dirs. The better way to handle that is to move
those definitions up to a foo/Android.bp file.

There's some internal reasons why forbidding ".." helps a lot, but we also
wanted it very obvious where to look to figure out who was using a
particular file -- it may only be referenced by an Android.bp directly
upwards in the tree. `mma` can work better this way, and we've implemented
the concept of visibility so that modules can control who can use their
files/outputs.

- Dan

On Tue, Jul 30, 2019 at 7:10 AM jyoti kulkarni  wrote:

> Hello Sir/madam,
>
> Im trying to convert some of the .mk files to .bp
> I am using androidmk tool for initial conversion.
>
> But later I m trying to change the converted files to add some more
> properties and some conditional statement.
>
> I have below questions:
> 1. Any new property added is giving an error "unrecognized property"
> for eg: unrecognized property "host_required"
>
> 2. If I'am trying to include other .mk file in .bp its giving "Path
> Outside directory"
> Iam trying to do something like this:
> srcs: ["../Android.mk"]
>
> Please help in addressing these questions.
>
> 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/8bbaf348-6e27-49c3-942e-67fc13b40330%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/8bbaf348-6e27-49c3-942e-67fc13b40330%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/CALQgHdnV4gUYvBdZQJ28H0ZpWAy7DVGS%3DzMOzYdfuStG%2BVgmKA%40mail.gmail.com.

Re: [android-building] Re: Some questions on Android.bp files

['Dan Willemsen' via Android Building]

proguard_flag_files was a typo -- it should be proguard_flag*s*_files. It
was fixed here:
https://android-review.googlesource.com/c/platform/build/soong/+/691330

- Dan

On Wed, Jul 31, 2019 at 11:32 PM jw wang  wrote:

> Hi Google
>
> I'm coming across two similar build break after converting the mk to bp :
>
> 1. 1. service/Android.bp:7:28: unrecognized property "
> optimize.proguard_flag_files“
>
>  2. /android_common/proguard_dictionary', needed by
> 'out/target/common/obj/APPS/AudioEFXService_intermediates/
> proguard_dictionary’
>
>
> I think the error comes from the optimize item which generated by
> androidtomk tool
>  optimize: {
>  proguard_flag_files: ["proguard.flags"],
>
> },
>
>
>
> On Tuesday, 30 July 2019 22:10:07 UTC+8, jyoti kulkarni wrote:
>>
>> Hello Sir/madam,
>>
>> Im trying to convert some of the .mk files to .bp
>> I am using androidmk tool for initial conversion.
>>
>> But later I m trying to change the converted files to add some more
>> properties and some conditional statement.
>>
>> I have below questions:
>> 1. Any new property added is giving an error "unrecognized property"
>> for eg: unrecognized property "host_required"
>>
>> 2. If I'am trying to include other .mk file in .bp its giving "Path
>> Outside directory"
>> Iam trying to do something like this:
>> srcs: ["../Android.mk"]
>>
>> Please help in addressing these questions.
>>
>> 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/63281eff-1da3-40f8-83fd-9b19243d2e8f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/63281eff-1da3-40f8-83fd-9b19243d2e8f%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/CALQgHdmKeGVm4W2S5XdOXztvHJhNRhGL_xMQR9SMgiBHaByOJA%40mail.gmail.com.

Re: [android-building] Some questions on Android.bp files

['Dan Willemsen' via Android Building]

>
> And for me visibility property is not working, Is this available only on Q?


visibility is actually only available on master -- it was recently
implemented, and didn't make it into Q. That only lets you limit visibility
though, which it doesn't sound like what you're looking for.

Are there any alternative to access "previous folder" header files in
> current .bp
>
> Something like ../app/include giving me Path Outside the Directory, and
> using visibility dont work
>

No, there's no way to allow "../" to work in Android.bp files. Move the
definition up a level if you're the only one using those files, or use a
filegroup to expose those as a set of files. Since you mention "include" --
if this is for C/C++ headers, you may want to read the best practices
<https://android.googlesource.com/platform/build/soong/+/master/docs/best_practices.md#headers>,
and see if you should be exporting the header directories from a library
instead of referencing paths directly. (A cc_library_headers may also work
in your situation, but I highly suggest that those should only be used for
truly header-only libraries).

- Dan

On Fri, Aug 2, 2019 at 9:22 AM jyoti kulkarni  wrote:

> Hello Dan,
>
> Thanks for your inputs.
> Currently I m still on Android P version.
>
> And for me visibility property is not working, Is this available only on Q?
> Are there any alternative to access "previous folder" header files in
> current .bp
>
> Something like ../app/include giving me Path Outside the Directory, and
> using visibility dont work
>
> Thanks
> Jyoti
>
> On Wednesday, July 31, 2019 at 7:44:42 AM UTC+5:30, Dan Willemsen wrote:
>>
>> 1. Which version of Android are you building against? host_required is
>> only supported on AOSP master. Unknown properties are errors, as they're
>> often typos.
>>
>> 2. Including Android.mk files from Android.bp files doesn't make sense,
>> what are you trying to do?
>>
>> We do forbid all path references that use ".." to escape the current
>> directory however -- you either need to use a filegroup and a module
>> reference ":filegroup_name", or move the contents of the Android.bp up a
>> level. We saw this a lot in applications that had:
>>
>>foo/res/...
>>foo/src/...
>>foo/test/...
>>
>> And had Android.mk files in the src and test directories that were using
>> "../" to access the other dirs. The better way to handle that is to move
>> those definitions up to a foo/Android.bp file.
>>
>> There's some internal reasons why forbidding ".." helps a lot, but we
>> also wanted it very obvious where to look to figure out who was using a
>> particular file -- it may only be referenced by an Android.bp directly
>> upwards in the tree. `mma` can work better this way, and we've implemented
>> the concept of visibility so that modules can control who can use their
>> files/outputs.
>>
>> - Dan
>>
>> On Tue, Jul 30, 2019 at 7:10 AM jyoti kulkarni 
>> wrote:
>>
>>> Hello Sir/madam,
>>>
>>> Im trying to convert some of the .mk files to .bp
>>> I am using androidmk tool for initial conversion.
>>>
>>> But later I m trying to change the converted files to add some more
>>> properties and some conditional statement.
>>>
>>> I have below questions:
>>> 1. Any new property added is giving an error "unrecognized property"
>>> for eg: unrecognized property "host_required"
>>>
>>> 2. If I'am trying to include other .mk file in .bp its giving "Path
>>> Outside directory"
>>> Iam trying to do something like this:
>>> srcs: ["../Android.mk"]
>>>
>>> Please help in addressing these questions.
>>>
>>> Thanks
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https:/

Re: [android-building] Unable to compile AOSP build pixel-3xl with hwasan sanitizer

['Dan Willemsen' via Android Building]

Android 9 did not support the hwaddress sanitizer, I believe that support
is in AOSP master, and should be in the Q release.

- Dan

On Tue, Jul 16, 2019 at 9:08 AM H Sai Manikanta Eadapalapati <
saimanika...@eximiusdesign.com> wrote:

> I'm trying to boot the pixel3 xl with aosp hwasan build, for that I took
> the latest build
>
>
> https://source.android.com/setup/start/build-numbers.html#source-code-tags-and-builds
>
> PQ3A.190705.003 android-9.0.0_r44 Pie Pixel 3 XL, Pixel 3 2019-07-05
>
> I'm getting an error as "unknown global sanitizer option hwaddress".
> Please help me on how to resolve these errors and compile. Are any patches
> available?
>
> logs and steps I followed are
>
> c_sai@mani:/sai/PQ3A.190705.003_p3xl$ source build/envsetup.sh
> .
> c_sai@mani:/sai/PQ3A.190705.003_p3xl$ lunch aosp_crosshatch-userdebug
> ...
> c_sai@mani:/sai/PQ3A.190705.003_p3xl$ make SANITIZE_TARGET=hwaddress
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=9
> TARGET_PRODUCT=aosp_crosshatch
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-2a
> TARGET_CPU_VARIANT=cortex-a75
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=cortex-a75
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.4.0-146-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=PQ3A.190705.003
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av
> hardware/google/interfaces hardware/qcom/sdm845 vendor/qcom/sdm845
> 
> [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
> [55/56] glob prebuilts/ndk/cpufeatures.bp
> [77/77] 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 -o out/soong/build.ninja Android.bp
> error: frameworks/native/headers/Android.bp:1:1: module
> "media_plugin_headers" variant "android_arm64_armv8-2a_cortex-a75_core":
> unknown global sanitizer option hwaddress
> error: hardware/google/av/codec2/Android.bp:1:1: module
> "libstagefright_codec2" variant
> "android_arm64_armv8-2a_cortex-a75_core_shared": unknown global sanitizer
> option hwaddress
> error: hardware/interfaces/tests/baz/1.0/Android.bp:3:1: module
> "android.hardware.tests.baz@1.0-adapter" variant
> "android_arm64_armv8-2a_cortex-a75_core": unknown global sanitizer option
> hwaddress
> error: system/media/audio_utils/tests/Android.bp:170:1: module
> "simplelog_tests" variant "android_arm64_armv8-2a_cortex-a75_core": unknown
> global sanitizer option hwaddress
> error: frameworks/native/libs/nativewindow/tests/Android.bp:17:1: module
> "AHardwareBufferTest" variant "android_arm64_armv8-2a_cortex-a75_core":
> unknown global sanitizer option hwaddress
> error: external/wayland-protocols/Android.bp:59:1: module
> "libwayland_extension_client_protocols" variant
> "android_arm64_armv8-2a_cortex-a75_core_static": unknown global sanitizer
> option hwaddress
> error: external/jemalloc/Android.bp:246:1: module "jemalloc_unittests"
> variant "android_arm64_armv8-2a_cortex-a75_core_a0": unknown global
> sanitizer option hwaddress
> error: external/libopus/Android.bp:1:1: module "libopus" variant
> "android_arm64_armv8-2a_cortex-a75_core_shared": unknown global sanitizer
> option hwaddress
> error: frameworks/base/tools/stats_log_api_gen/Android.bp:97:1: module
> "libstatslog" variant "android_arm64_armv8-2a_cortex-a75_core_shared":
> unknown global sanitizer option hwaddress
> error: frameworks/native/libs/nativewindow/Android.bp:31:1: module
> "libnativewindow" variant "android_arm64_armv8-2a_cortex-a75_core_static":
> unknown global sanitizer option hwaddress
> error: hardware/interfaces/automotive/audiocontrol/1.0/Android.bp:3:1:
> module "android.hardware.automotive.audiocontrol@1.0-adapter" variant
> "android_arm64_armv8-2a_cortex-a75_core": unknown global sanitizer option
> hwaddress
> error: frameworks/av/media/libstagefright/codecs/mpeg2dec/Android.bp:1:1:
> module "libstagefright_soft_mpeg2dec" variant
> "android_arm_armv8-a_cortex-a75_core_shared": unknown global sanitizer
> option hwaddress
> error: external/tensorf

Re: [android-building] Building Android.bp

['Dan Willemsen' via Android Building]

Android.bp files must have all of their dependencies in Android.bp as well.
There is no way to work around that.

- Dan

On Thu, Jul 18, 2019 at 7:37 AM Amit Agrawal  wrote:

> So In Android P, It supports both .bp as well as .mk. What if I want to
> compile a module which is in .bp format but it depends on some other module
> which is written in .mk format? Is there anyway that we ignore the
> dependencies?
>
> On Saturday, March 2, 2019 at 3:28:41 AM UTC+5:30, Dan Willemsen wrote:
>>
>> No, Nougat does not support building with Android.bp files. Oreo and
>> later support both Android.mk and Android.bp files (though Android.bp files
>> largely cannot reference Android.mk files, so all your dependencies need to
>> be converted to Android.bp first).
>>
>> - Dan
>>
>> On Fri, Mar 1, 2019 at 8:34 AM Amit Agrawal  wrote:
>>
>>> Hello,
>>> I am new to AOSP. As far as I know we were using 'Make build system' in
>>> nougat which were building Android.mk files. And from Oreo onwards Soong is
>>> used for Android.bp.
>>> Is there any way by which I can build the Android.bp files in nougat
>>> using the 'Make build system'?
>>>
>>> Thanks and Regards,
>>> Amit Agrawal
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/96c8d988-c0bb-47a0-8d5a-9b2a0edf4872%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/96c8d988-c0bb-47a0-8d5a-9b2a0edf4872%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] SDK building - development/build/sdk.atree - couldn't locate source file error

['Dan Willemsen' via Android Building]

Building the sdk generally requires using the 'sdk' product when calling
lunch -- it looks like that's why you were building a bunch of tools
independently.

I wouldn't be surprised if the sdk generation code didn't support
OUT_DIR(/OUT_DIR_COMMON_BASE) that was anything other than "out".

- Dan

On Fri, Jul 19, 2019 at 11:25 AM Nicolas Peslerbe <
nicolas.pesle...@bionomous.ch> wrote:

> Dear all,
>
> I have an error I can't figure out where it comes from but maybe one of
> you can help me.
>
> I try to build android sdk with the following script:
>
> cd ../rk3399-android-8.1
> . build/envsetup.sh
> export OUT_DIR_COMMON_BASE=~/androidSdk
> lunch nanopc_t4-userdebug
>
> make -j16 dmtracedump
> make -j16 etc1tool
> make -j16 split-select
> make -j16 bcc_compat
> make -j16 apksigner
> make -j16 dx
> make -j16 libaapt2_jni
> make -j16 layoutlib-legacy
>
> make -j16 sdk
>
>
> Everything goes well until it reaches the 100% stage (zip building), at
> this point I get the following error:
>
> development/build/sdk-android-arm64-v8a.atree:20: couldn't locate source 
> file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/host/linux-x86/development/sys-img-arm64-v8a/images_arm64-v8a_source.properties
> development/build/sdk.atree:143: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/host/common/obj/JAVA_LIBRARIES/shrinkedAndroid_intermediates/shrinkedAndroid.jar
> development/build/sdk.atree:161: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/host/linux-x86/development/sdk/platform_source.properties
> development/build/sdk.atree:167: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/common/obj/PACKAGING/android_jar_intermediates/android.jar
> development/build/sdk.atree:168: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/common/obj/PACKAGING/android_jar_intermediates/android-stubs-src.jar
> development/build/sdk.atree:171: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/javalib.jar
> development/build/sdk.atree:173: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/common/obj/JAVA_LIBRARIES/android_uiautomator_intermediates/javalib.jar
> development/build/sdk.atree:222: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/host/common/obj/PACKAGING/sdk-fonts_intermediates
> development/build/sdk.atree:238: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/product/nanopc-t4/system.img
> development/build/sdk.atree:239: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/target/product/nanopc-t4/vendor.img
> development/build/sdk.atree:252: couldn't locate source file: 
> /home/peslerbe/androidSdk/rk3399-android-8.1/host/linux-x86/development/sdk/doc_source.properties
>
>
> but when I check all paths, some file are present, with content and
> correct permissions/rights:
>
> -rw-rw-r-- 1 peslerbe peslerbe 10450 Jul 19 12:10 ###FILE_NAME###
>
>
> Does anyone has got an idea about the source of this error ?
>
> Thanks,
> Best regards,
>
> Nicolas
>
>
>
>
> --
> --
> 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/33628644-4aba-4adf-891a-7089b6bab113%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/33628644-4aba-4adf-891a-7089b6bab113%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/CALQgHdnfJd2pxjLRu%3Dmf3GSKbR7viuU72t32u4YYG3mGNmWXuw%40mail.gmail.com.

Re: [android-building] How to upload a driver that I created to my device?

['Dan Willemsen' via Android Building]

Android (as AOSP) does not build the kernel along with the platform code --
it's expected to be delivered as a prebuilt. So setting KERNEL_DEFCONFIG
won't do anything.

- Dan

On Fri, Jul 19, 2019 at 11:26 AM abhishekkumardwiv...@gmail.com <
abhishekkumardwiv...@gmail.com> wrote:

> If you have full source code of Android stack with the kernel then you can
> check at AndroidBoard.mk file which will address the config file used for
> kernel compilation. If you want to compile only kernel then you can do
> something like:
> $ make -j4 KERNEL_DEFCONFIG=xyz_defconfig
> Here the xyz_defconfig is the file name which you might have found in
> AndroidBoard.mk.
> This is the usual way but I am not sure about the device you are using.
>
> ~Abhishek Dwivedi
>
> On Thu, Jul 18, 2019 at 10:01 PM 'Dan Willemsen' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> As far as I know, when loading a module using the "insmod" command from
>>> the *ENG*(or userdebug) binary, it is not necessary to verify the
>>> signature of the module.
>>
>>
>> The kernel configuration / image doesn't change between eng/userdebug and
>> user, so this would surprise me. I suspect you'd have to rebuild the
>> kernel, but I don't know for sure. The android-kernel google group may be
>> able to help you more -- we generally only deal with prebuilt kernels when
>> building the rest of the platform.
>>
>> - Dan
>>
>> On Thu, Jul 18, 2019 at 7:37 AM Lucas. B  wrote:
>>
>>> *@Dear All,*
>>>
>>>
>>>
>>> I've been wondering about some of the android functions for some time
>>> now, so I made a device driver.
>>>
>>> And I downloaded the *AOSP *source code and built it into *ENG*(or
>>> userdebug), then flash it into my *Pixel 3 XL*.
>>>
>>> But as I tried to load the module with the "insmod" command, I could
>>> find the following:
>>>
>>>
>>>
>>>> *insmod: failed to load /sdcard/.../my_driver.ko: Required key not
>>>> available*
>>>>
>>>
>>>
>>> As far as I know, when loading a module using the "insmod" command from
>>> the *ENG*(or userdebug) binary, it is not necessary to verify the
>>> signature of the module.
>>>
>>> Anyway, I have the above signature problem, and I wonder how to solve it.
>>>
>>> How build own drive into the kernel, whether modify the .config in the *AOSP
>>> *source to build a new binary, or whatever can try to build a device
>>> driver, etc. I welcome everyone.
>>>
>>> I want to make sure my driver is working normally on the my *Pixel 3 XL*
>>> .
>>>
>>>
>>>
>>> *with best regard,*
>>>
>>> *Thanks =)*
>>> *Lucas. B.*
>>>
>>> --
>>> --
>>> 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/efbcb066-7ef7-4cb7-a5b6-55e39bfedfe2%40googlegroups.com
>>> <https://groups.google.com/d/msgid/android-building/efbcb066-7ef7-4cb7-a5b6-55e39bfedfe2%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop re

Re: [android-building] Flashing kernel in pixel 2 (walleye)..?

['Dan Willemsen' via Android Building]

Have you read https://source.android.com/setup/build/building-kernels?

- Dan

On Fri, Jul 19, 2019 at 11:25 AM Saurabh Sakhare 
wrote:

> Hello, I'm newbie in kernel development. I want to know where can I get
> pixel 2 kernel and Clang toolchain and commands. I've been trying to
> compile it from last few days from random sources of git and google source.
> I could not compile a kernel I'm facing problem like some parse file is
> missing and arm32 toolchain. Pixel 2 is 64 bit wahoo. board is walleye. i'm
> trying every possible way somewhere I'm missing please help me out here.
>
>
>
> Then I rooted my phone and got SYSTEM_LAST_BOOT_logs it attached with
> mail.
>
> --
> --
> 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/2a095acf-f8af-4bfe-acfa-661d0d2d616f%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/2a095acf-f8af-4bfe-acfa-661d0d2d616f%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/CALQgHdkoLvNzA2UKfsOzjDCogOuHPNbLi_wRpyHhSoYF%2BZfb2A%40mail.gmail.com.

Re: [android-building] How to use build vars like PRODUCT_XXX in genrule cmd?

['Dan Willemsen' via Android Building]

Those variables aren't exposed, partially because it becomes very difficult
to understand which pieces of the system are then product-specific vs
generic. Is there a reason why you wouldn't just read the runtime
properties rather than trying to embed those values in code?

- Dan

On Mon, Jul 15, 2019 at 9:31 AM DavidRobin  wrote:

> I saw that in external/libmojo/Android.bp there is an example to generate
> header files for later build process.
>
> genrule {
> name: "libmojo_mojom_headers",
> cmd: "$(location mojom_source_generator_sh)" +
> "--mojom_bindings_generator=$(location mojom_bindings_generator)" +
> "--package=external/libmojo" +
> "--output_dir=$(genDir)" +
> "--bytecode_path=$(genDir)" +
> "--typemap=$(location
> gen/mojo/common/common_custom_types__type_mappings)" +
> "--generators=c++" +
> "--use_new_wrapper_types" +
> "$(in)",
>
> However, I cannot find how to use vars like $(PRODUCT_BRAND)
> $(PRODUCT_MANUFACTURER) etc in this cmd line.
> Please help.
> 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/48a06135-67f5-4381-a18c-5eed5a949601%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/48a06135-67f5-4381-a18c-5eed5a949601%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: [android-building] AOSP 7.1 failing to create a module with a prebuilt static library in system build.

['Dan Willemsen' via Android Building]

Use `mmma` or `m libdump` instead of `mmm`, at least once. I suspect that
will fix it up. Note that to be correct, you need to specify
LOCAL_SDK_VERSION := , since you compiled with the NDK.

- Dan

On Mon, Jul 22, 2019 at 6:11 AM FlamurBerisha  wrote:

> Hello everyone, thanks for helping.
>
> I have an prebuilt  static library builted with ndk toolchain for cmake.
> My lib is a simply a c++ class that says hello world on its constructor.
> Command which I invoke the cmake is : "cmake
> -DCMAKE_TOOLCHAIN_FILE=~/Android/Ndk/android-ndk-r19c/build/cmake/android.toolchain.cmake
> -DANDROID_ABI="arm64-v8a""
>
> Than I created my module at external/new_module, there I putted the
> prebuilt_lib and the other src files that are linked to this lib. My
> Android.mk file looks like this.
> LOCAL_PATH := $(call my-dir)
>
> include $(CLEAR_VARS)
> LOCAL_MODULE := libdump_android_static
> LOCAL_MODULE_CLASS := STATIC_LIBRARIES
> LOCAL_MODULE_SUFFIX := .a
> LOCAL_SRC_FILE := lib/arm64-v8a/../dump_android/libdump_android.a
> LOCAL_C_INCLUDES := $(LOCAL_PATH)/include/../dump
> LOCAL_EXPORT_C_INCLUDE_DIRS := $(LOCAL_PATH)/include
> include $(BUILD_PREBUILT)
>
> When I execute the compile command for only this module "mmm
> ./external/new_module" it says that make completed successfully and also
> says " target Prebuilt: libdump_android_static
> (out/target/product/../obj/STATIC_LIBRARIES/libdump_android_static_intermediates/libdump_android_static.a"
> Than I wanted to use this library in other sub-module which is builded
> inside the system, that sub-module inside my same Android.mk looks like:
>
> include $(CLEAR_VARS)
> LOCAL_MODULE := libdump
> LOCAL_SRC_FILES := src/../dump/dump.cpp
> LOCAL_C_INCLUDES := $(LOCAL_PATH)/include
> LOCAL_SHARED_LIBRARIES := liblog libopencv_core
> LOCAL_STATIC_LIBRARIES := libdump_android_static
> LOCAL_EXPORT_C_INCLUDE_DIRS := $(LOCAL_PATH)/include
> include $(BUILD_SHARED_LIBRARY)
>
> When I execute the compile command for only this module "mmm
> ./external/new_module" it says:
> ninja: error:
> 'out/target/product/../obj_arm/STATIC_LIBRARIES/libdump_android_static_intermediates/export_includes',
> needed by
> 'out/target/product/../obj_arm/SHARED_LIBRARIES/libdump_intermediates/import_includes',
> missing and no known rule to make it.
> I also tried with shared libraries but the same error appears!
>
> --
> --
> 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/91f9bda2-f1ef-4a54-a0a9-d041b7bb0222%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/91f9bda2-f1ef-4a54-a0a9-d041b7bb0222%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/CALQgHdmrPAxbKtEy0xUoREQ9y0XnX1tY81%2BPs-3Xg4xSE8jFOQ%40mail.gmail.com.

Re: [android-building] Android.bp can't link java static library built from Android,mk

['Dan Willemsen' via Android Building]

All dependencies of an Android.bp file must be in Android.bp, not
Android.mk. So you'll need to convert your libmine description to an
Android.bp file.

- Dan

On Wed, Sep 18, 2019 at 1:51 PM Jack Rong  wrote:

> I have a scenario that is to link in a Java static library built from an
> Android.mk file to complete the whole AOSP image build in Android P. The
> build system somehow is not versatile enough to discover the static library
> built from other project using the Android.mk. Here is an example:
>
>  1) Android.mk file at the "package/app/MyLibs"
>
> LOCAL_PATH := $(call my-dir)
>
> include $(CLEAR_VARS)
>
> LOCAL_MODULE := libmine
>
> LOCAL_SRC_FILES := \
> $(call all-java-files-under, src/main/java) \
> $(call all-Iaidl-files-under, src/main/aidl)
>
> ifneq ($(filter 28,$(PLATFORM_SDK_VERSION)),)
> LOCAL_PRIVATE_PLATFORM_APIS := true
> else
> LOCAL_SDK_VERSION := current
> endif
>
> LOCAL_STATIC_JAVA_LIBRARIES := libgson
>
> LOCAL_PROGUARD_FLAG_FILES := proguard.flags
>
> include $(BUILD_STATIC_JAVA_LIBRARY)
>
>
> 2) Android.bp at "frameworks/base/services/devicepolicy"
>
> java_library_static {
> name: "services.devicepolicy",
> srcs: ["java/**/*.java"],
>
> libs: [
> "conscrypt",
> "services.core",
> ],
> static_libs: [
> "libmine",
> ],
> }
>
> 3) Build message:
>
> error: frameworks/base/services/devicepolicy/Android.bp:1:1:
> "services.devicepolicy" depends on undefined module "libmine"
>
>
> --
> --
> 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/7b078f33-17a4-47c4-b202-7a29d08f0253%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/7b078f33-17a4-47c4-b202-7a29d08f0253%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/CALQgHdn8EaRAX2hZwyt2OiZm1N9KM63s%2Bx_yPdvs6o9iBx6fsQ%40mail.gmail.com.

Re: [android-building] $shell commands in Android.mk -> Android.bp migration.

['Dan Willemsen' via Android Building]

You'll need to execute conan before running the android build. It's not
enforced yet, but the source tree is expected to be read-only during the
build -- in particularly we start caching the Android.bp files nearly
immediately upon build startup, so adding new ones isn't going to work.
Nothing from the Android.bp files are executed before we finish reading all
the Android.bp files.

- Dan

On Fri, Sep 20, 2019 at 1:51 PM 'NIRAJ DESAI' via Android Building <
android-building@googlegroups.com> wrote:

> I have a similar need
>
> I am trying to integrate the conan package management system.
>
> I have written a custom generator for conan that creates an Android.bp
> file with the appropriate targets that are downloaded via conan
>
> I need to run a script that will install these dependencies during build
> time.
>
> My file structure is:
>
> - vendor/mycompany/external/Android.bp
> - vendor/mycompany/external/conanInstallDependencies.sh
> - vendor/mycompany/conan/conanfile.txt
>
> I am able to run the script using $(shell) via Android.mk but I am not
> sure how to integrate Android.mk and the Android.bp that uses the conan
> deps  to ensure the build order is satisfied
>
> It works with Android.mk, but I have to run the build twice.
> - First build iteration will download the dependencies via Conan and place
> them in the proper folder location but the build will fail because the
> Android.bp that is generated by Conan is not executed
> - Second build iteration will find the existing Android.bp that was
> generated by Conan and the build will succeed
>
>
> I essentially want to create a target that is called
> "conanInstallDependencies"
> This target would  be simple, it will only invoke the
> "conanInstallDependencies.sh" script
>
> I would want the Conan-generated Android.bp to "link" or "be dependent" on
> the "conanInstallDependencies" target so that this Android.bp is always
> built after the "conanInstallDependencies" Android.bp
>
>
>
>
>
> On Thursday, August 22, 2019 at 11:18:41 AM UTC-7, Dan Willemsen wrote:
>>
>> What is your pre-build-script.sh script doing? Right now, since it has no
>> dependencies and no output files, you're essentially running it on every
>> build, even when the user is only trying to compile a single file in a
>> different section of the tree. That's deprecated since it has a huge
>> performance impact.
>>
>> Generally, if this is something that takes inputs and produces output
>> files, you may be able to use a genrule. But without knowing anything about
>> what this script is doing, I can't help much more than that.
>>
>> - Dan
>>
>>
>>
>> On Tue, Aug 20, 2019 at 2:40 PM Frederic Plourde 
>> wrote:
>>
>>> Hi android building !
>>>
>>>
>>>   I used to have this in one of my Android.mk makefiles :
>>>
>>> $(shell (cd $(LOCAL_PATH)/../../ && ./pre-build-script.sh))
>>>
>>>
>>> but I just noticed that this practice is now discouraged on the Soong
>>> Android.bp build system
>>>
>>> From the Build System Best Practices
>>> <https://android.googlesource.com/platform/build/soong/+/HEAD/docs/best_practices.md>
>>> document,  I could read :
>>>
>>> Don't use $(shell) to write files, create symlinks, etc. We expect to
>>> enforce this in the future. Encode these as build rules in the build graph
>>> instead. This can be problematic in a number of ways:
>>>
>>>
>>> Could you give me a concrete example of how I could run this
>>> "pre-build-script.sh" shell script before *every* build in my new
>>> Android.bp file ?
>>>
>>> thx :)
>>>
>>>
>>> *Frederic Plourde*
>>> Principal Engineer
>>> Collabora ltd.
>>>
>>> --
>>> --
>>> 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 discussio

Re: [android-building] Build failed with Android 9.0

['Dan Willemsen' via Android Building]

How did you download it? Based on the banner, that's at least partially
master, not 9.0. A mismatched source tree could explain that error (or it
happened to be broken when you synced, and you should try syncing again if
you do want master).

- Dan

On Fri, Jun 28, 2019, 7:56 AM 岳羽 <384378...@qq.com> wrote:

> Here is all the commands:
> 1. source build/envsetup.sh
> 2. lunch 21 (aosp_x86-eng)
> 3. rm -rf out && make -j4 2>&1 | tee b.log
> than, always show the error log.
>
> On Thursday, June 27, 2019 at 4:54:10 PM UTC+8, Alessio Balsini wrote:
>>
>> Can you please post all the exact commands you ran?
>>
>> Cheers,
>> Alessio
>>
>> On Mon, Jun 24, 2019 at 4:45 PM 岳羽 <3843...@qq.com> wrote:
>> >
>> > I download the source code of AOSP with VMWare Ubuntu18.04, When I
>> build with "rm -rf out && make -j4 2>&1 | tee b.log", always failed.
>> > all the logs below
>> >
>> > 
>> > PLATFORM_VERSION_CODENAME=R
>> > PLATFORM_VERSION=R
>> > 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.18.0-23-generic-x86_64-Ubuntu-18.04.2-LTS
>> > HOST_CROSS_OS=windows
>> > HOST_CROSS_ARCH=x86
>> > HOST_CROSS_2ND_ARCH=x86_64
>> > HOST_BUILD_TYPE=release
>> > BUILD_ID=PI
>> > OUT_DIR=out
>> > 
>> > [100% 1/1] out/soong/.minibootstrap/minibp
>> out/soong/.bootstrap/build.ninja
>> > [  1% 2/140] compile out/soong/.bootstrap/blueprint-deptools/pkg/
>> github.com/google/blueprint/deptools.a
>> > [  2% 3/140] compile out/soong/.bootstrap/blueprint-parser/pkg/
>> github.com/google/blueprint/parser.a
>> > [  2% 4/140] compile out/soong/.bootstrap/blueprint-parser/test/
>> github.com/google/blueprint/parser.a
>> > [  3% 5/140] compile out/soong/.bootstrap/blueprint-pathtools/test/
>> github.com/google/blueprint/pathtools.a
>> > [  4% 6/140] compile out/soong/.bootstrap/blueprint-pathtools/pkg/
>> github.com/google/blueprint/pathtools.a
>> > [  5% 7/140] compile out/soong/.bootstrap/blueprint-proptools/test/
>> github.com/google/blueprint/proptools.a
>> > [  5% 8/140] compile out/soong/.bootstrap/gotestmain/obj/gotestmain.a
>> > [  6% 9/140] compile out/soong/.bootstrap/loadplugins/obj/loadplugins.a
>> > [  7% 10/140] compile
>> out/soong/.bootstrap/gotestrunner/obj/gotestrunner.a
>> > [  7% 11/140] compile out/soong/.bootstrap/blueprint-proptools/pkg/
>> github.com/google/blueprint/proptools.a
>> > [  8% 12/140] link out/soong/.bootstrap/gotestmain/obj/a.out
>> > [  9% 13/140] link out/soong/.bootstrap/gotestrunner/obj/a.out
>> > [ 10% 14/140] link out/soong/.bootstrap/loadplugins/obj/a.out
>> > [ 10% 15/140] cp out/soong/.bootstrap/bin/gotestrunner
>> > [ 11% 16/140] cp out/soong/.bootstrap/bin/gotestmain
>> > [ 12% 17/140] cp out/soong/.bootstrap/bin/loadplugins
>> > [ 12% 18/140] gotestmain
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/test.go
>> > [ 13% 19/140] gotestmain
>> out/soong/.bootstrap/blueprint-parser/test/test.go
>> > [ 14% 20/140] gotestmain out/soong/.bootstrap/blueprint/test/test.go
>> > [ 15% 21/140] gotestmain
>> out/soong/.bootstrap/blueprint-pathtools/test/test.go
>> > [ 15% 22/140] compile out/soong/.bootstrap/blueprint-parser/test/test.a
>> > [ 16% 23/140] compile
>> out/soong/.bootstrap/blueprint-pathtools/test/test.a
>> > [ 17% 24/140] compile out/soong/.bootstrap/blueprint/test/
>> github.com/google/blueprint.a
>> > [ 17% 25/140] link out/soong/.bootstrap/blueprint-parser/test/test
>> > [ 18% 26/140] compile out/soong/.bootstrap/blueprint/pkg/
>> github.com/google/blueprint.a
>> > [ 19% 27/140] compile out/soong/.bootstrap/blueprint/test/test.a
>> > [ 20% 28/140] test github.com/google/blueprint/parser
>> > [ 20% 29/140] link out/soong/.bootstrap/blueprint-pathtools/test/test
>> > [ 21% 30/140] test github.com/google/blueprint/pathtools
>> > [ 22% 31/140] gotestmain
>> out/soong/.bootstrap/blueprint-proptools/test/test.go
>> > [ 22% 32/140] compile
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg/
>> github.com/google/blueprint/bootstrap/

Re: [android-building] Avoid Androdi.bp execution not being declared in subdirs

['Dan Willemsen' via Android Building]

Which version of Android are you using? Starting in Android P (IIRC),
`subdirs` stopped doing anything, and we always load all Android.bp files
(nothing really gets executed when they're loaded -- they're just used to
build the action graph that we later execute). Depending on your use case,
`soong_namespace`s can partition different subtrees of Android.bp files
away from others.

- Dan

On Sat, Nov 2, 2019 at 3:30 PM seeker  wrote:

> Hello,
> lets say a folder X  has a,b,c,d and e as subfolders and  I encountered a
> case where X's Android.bp includes subdirs=[a,b,c,d] and not e, and when
> executed on  a whole  despite of not including e in subdirs,  e's
> Android.bp is getting executed
> How to avoid this?
> And Can I get knowledge on how many levels of Android.bp will be included
> by default? or any Android.bp from top will be included by default?
> 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/59b113e2-aec7-4935-8991-874ff04102ff%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/59b113e2-aec7-4935-8991-874ff04102ff%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/CALQgHdmWS4eoEXdBhV-v_V6vR1BFSQZ0abi-JxjCj%3D598NRMCQ%40mail.gmail.com.

Re: [android-building] Android 10 does not have a "build/target/product/core.mk" file

['Dan Willemsen' via Android Building]

+Anton Hansson  who did a lot of this work.

If you're building a phone-like product, then yes, I believe using
handheld_* is appropriate (or maybe mainline_system.mk, which is the effort
towards a unified system image for multiple devices), though if you're
having to remove things, maybe using one of the ones it includes would be
better. We tried to merge and split these apart so that they made more
sense -- combining some layers while splitting them up into per-partition
files.

- Dan

On Mon, Nov 11, 2019 at 9:59 AM John W. Blue  wrote:

> First, wanted to say thanks for the help on my other questions to Dan and
> Colin.  I was able to get a working default ROM complied and my ccache
> pushed up against 20 GB.
>
>
>
> Previously I would edit build/target/product/core.mk to remove basic
> items .. email for example.  As best as I can tell grep’ing around, it
> seems like these files took the place of core.mk:
>
>
>
> handheld_product.mk
>
> handheld_system.mk
>
> handheld_vendor.mk
>
>
>
> What I have not been able to find is a discussion about this change
> because I want to understand the intent and what drove the decision.  I
> read the release notes here:
>
>
>
> https://source.android.com/setup/start/android-10-release
>
>
>
> but it didn’t speak about it.
>
>
>
> Am I correct in assuming that handheld et al is the new “core.mk”?
>
>
>
> John
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/fbead81a3f564acab84936a25d603dcc%40mail.rrcic.com
> <https://groups.google.com/d/msgid/android-building/fbead81a3f564acab84936a25d603dcc%40mail.rrcic.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%3D6fnwacj%2BovUH05ykLzTqLWVQ_kWAyy9uyYkBjq0rfuw%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

If you check out/soong.log, there should be trace logs that include the
parent processes all the way up to ninja.

It sounds like one of the existing tools that we allow through is always
trying to call manpath? Let me know what you find, we've definitely been
shrinking this list on master.

- Dan

On Thu, Nov 14, 2019 at 3:54 PM Michael Goffioul 
wrote:

> I'm using Fedora 30 to build AOSP. Since Android Q, when building, the
> terminal output is littered with hundreds of messages like the following:
>
> 17:23:06 Disallowed PATH tool "manpath" used: []string{"manpath"}
> 17:23:06 See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
>
> I've looked almost everywhere, but I can't find where "manpath" is
> actually used. Has anybody encountered the same problem?
>
> Thanks,
> Michael.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/c9a8a0ea-2492-4e7f-9816-11b9b91f6696%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/c9a8a0ea-2492-4e7f-9816-11b9b91f6696%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%3DmqvANYjYSZyP_1%3DtbMgoddYSLEMTkn3NuUTJF_qML7A%40mail.gmail.com.

Re: [android-building] VNDK v28

['Dan Willemsen' via Android Building]

Pie was API version 28, so `BOARD_VNDK_VERSION := current` should give you
a v28 vndk. The v27 that comes with Pie is just the prebuilts so that you
can run older vendor images.

- Dan

On Mon, Nov 18, 2019 at 9:34 AM M.S. Mac-Donald 
wrote:

> Hello,
>
> I'm trying to build AOSP branch: android-9.0.0_r46 for my device (Xiaomi
> mi A3). This version of android comes with vndk v27. But the board however
> supports v28 . How do we get vndk 28 working for android pie? Xiaomi has
> done it, but during the build errors when i use v28... How do we use a
> newer vndk on a previous android version?
>
> Greetings
>
> --
> --
> 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/fcb33a29-2d44-4926-80e4-7f1d815143bd%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/fcb33a29-2d44-4926-80e4-7f1d815143bd%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/CALQgHdmL7zUXUjx1ScuB5F6mRiriFohf3qxnW6eWj-pRc0VZhw%40mail.gmail.com.

Re: [android-building] passing "--depth=1" to repo init -- good/bad/ugly?

['Dan Willemsen' via Android Building]

It can still be the quickest way to download the least data to get an
initial tree. But you do lose all the history, uploads tend not to work
well, nor do cherry-picks, and the next download is quite possibly bigger
(even if it doesn't fail and you've got to remove and re-download that
project from scratch).


Git and repo are starting to support a "partial clone" feature that should
be an improvement over --depth, in that you still get all the history, you
just don't need to download all the files until you actually need them.
There are cases where it's still slower, though depending on your download
speed, it may not be too bad:

https://git-scm.com/docs/partial-clone
repo init --partial-clone -u
https://android.googlesource.com/platform/manifest -b ...

You probably want to make sure that your git client is up to date, I know
there's been active work to make this better (but I'm not following it too
closely).

- Dan

On Wed, Nov 6, 2019 at 1:39 PM John W. Blue  wrote:

> Downloading the source for any branch has historically been a heavy lift
> simply due to the sheer size of the code.
>
>
>
> For example, for the Pixel XL I sync’d 10.0.0_r5 and it clocked in at 48.2
> GB.  The .repo folder alone is showing that is has 42.9 GB of the total.
>
>
>
> I have been reading that passing “-- depth=1” to repo init results in a
> “shallow clone” that should significantly reduce the size.  JBQ indicated
> as much with some testing in this thread:
>
>
>
> https://groups.google.com/forum/#!topic/repo-discuss/WejHXT2LdlY
>
>
>
> JBQ also goes on to mention:
>
>
>
> 1.   You're using a non-resumable protocol, so you need a reliable
> enough connection.
>
> 2.   You won't have any change history.
>
> 3.   You won't be able to push from such a client (including the
> ability to upload changes).
>
> 4.   Future syncs might re-download everything again.
>
>
>
> For what I do, building basically a stock AOSP ROM, I don’t think that 2
> and 3 will cause any heartburn.  1 and 4 *might* be in play but I wanted to
> validate with the group if it is even a thing at this point in time
> especially #4.
>
>
>
> Outside of what is listed are there any unintended consequences of using
> shallow clones that would cause a ROM to be horked up?
>
>
>
>
>
> --
> --
> 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/25dceaa908fa4e7e953ad793cba77de9%40mail.rrcic.com
> <https://groups.google.com/d/msgid/android-building/25dceaa908fa4e7e953ad793cba77de9%40mail.rrcic.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/CALQgHdktswNfs%2BYUJAwwFJkK36VD_su7NzpvEderW-3841XQ3A%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

I've created a change to empty out the BASH_ENV environment variable during
the build:
https://android-review.googlesource.com/c/platform/build/soong/+/1168864

- Dan

On Mon, Nov 18, 2019 at 10:48 AM 'Colin Cross' via Android Building <
android-building@googlegroups.com> wrote:

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

Re: [android-building] How to use build vars like PRODUCT_XXX in genrule cmd?

['Dan Willemsen' via Android Building]

We've recently updated our documentation around conditionals (and most use
of make variables fall into the same category):

https://android.googlesource.com/platform/build/soong/+/master/README.md#how-do-i-write-conditionals

tl;dr: we'd prefer you didn't use them, but if you need to, you can via a
Go plugin.

- Dan

On Fri, Nov 22, 2019, 7:11 AM Chih-Wei Huang 
wrote:

> I have the same question.
> I'd like to use product variables like TARGET_PRODUCT in Android.bp.
> I searched the whole AOSP tree but still can't find a way to do that.
> Sigh,,, Is it possible?
>
> DavidRobin於 2019年7月16日星期二 UTC+8下午11時13分22秒寫道：
>>
>> Thanks for your reply.
>> Our purpose is to generate "License checking code" for specific product
>> build.
>> So we have a shell script to generate the code based on the PRODUCT_XXX
>> properties.
>>
>> Are you implying that Android.bp should only be used in generic (product
>> independent) modules?
>> And this kind of code should be put in device/product specific stuff and
>> use Android.mk to achieve the goal?
>> (P.S. will Android.mk be kept or will Android.bp take over the whole
>> build?)
>>
>> On Tuesday, July 16, 2019 at 2:13:13 AM UTC+8, Dan Willemsen wrote:
>>>
>>> Those variables aren't exposed, partially because it becomes very
>>> difficult to understand which pieces of the system are then
>>> product-specific vs generic. Is there a reason why you wouldn't just read
>>> the runtime properties rather than trying to embed those values in code?
>>>
>>> - Dan
>>>
>>> On Mon, Jul 15, 2019 at 9:31 AM DavidRobin  wrote:
>>>
>>>> I saw that in external/libmojo/Android.bp there is an example to
>>>> generate header files for later build process.
>>>>
>>>> genrule {
>>>> name: "libmojo_mojom_headers",
>>>> cmd: "$(location mojom_source_generator_sh)" +
>>>> "--mojom_bindings_generator=$(location
>>>> mojom_bindings_generator)" +
>>>> "--package=external/libmojo" +
>>>> "--output_dir=$(genDir)" +
>>>> "--bytecode_path=$(genDir)" +
>>>> "--typemap=$(location
>>>> gen/mojo/common/common_custom_types__type_mappings)" +
>>>> "--generators=c++" +
>>>> "--use_new_wrapper_types" +
>>>> "$(in)",
>>>>
>>>> However, I cannot find how to use vars like $(PRODUCT_BRAND)
>>>> $(PRODUCT_MANUFACTURER) etc in this cmd line.
>>>> Please help.
>>>> 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/6a64020b-1413-4723-aabe-3d6ce27f3ae9%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/6a64020b-1413-4723-aabe-3d6ce27f3ae9%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/CALQgHdnnDnFR31OzHoFh22CPTiF4L7vtr0JqHdJuCUNAMiSn1Q%40mail.gmail.com.

Re: [android-building] Build sandboxing disabled due to nsjail error on lxc

['Dan Willemsen' via Android Building]

> 1. How fatal is it, do I need a machine running Ubuntu natively.

It's not fatal, the build should continue and work successfully. I know
that there are problems with docker-like systems (eventually tracking down
to some workarounds for a kernel bug -- turning off a lot of the security
helps, but doesn't get you all the way there), and there are problems with
systems that don't enable user namespaces (which means we'd need root ).
Between those problems it's likely not to become fatal anytime in the near
future, I should probably remove those messages from master.

Right now it's only giving us two benefits: (1) disabling networking for
the build and (2) preventing processes from staying alive after the build
exits (either normally, or on a failure). I'd like to do some more changes
(hiding / making visible different portions of the source tree, ensuring
that the current output directory is always out/, making the source tree
readonly, etc), but with enough people not being able to use it, we'll need
to find other ways to satisfy those goals.

2. If the build system is being containerized, can i just rub the build on
> my fedora machine and not care about build environment as much?
>

Yes, I'd expect that to work. Please let us know if you have any problems
doing that.

We're not fully containerizing, but we do include our own versions of most
of the tools that we use. The list of host tools that we're using is
shrinking, but bug reports would help us identify which ones should be
prioritized.

- Dan

On Mon, Dec 9, 2019 at 12:20 PM Sahaj Sarup  wrote:

> AOSP master.
>
> Getting the following warnings:
>
> 18:54:25 Build sandboxing disabled due to nsjail error. This may become
> fatal in the future.
> 18:54:25 Please let us know why nsjail doesn't work in your environment
> at:
> 18:54:25   https://groups.google.com/forum/#!forum/android-building
> 18:54:25   https://issuetracker.google.com/issues/new?component=381517
> 18:54:25 Build sandboxing disabled due to nsjail error. This may become
> fatal in the future.
> 18:54:25 Please let us know why nsjail doesn't work in your environment
> at:
> 18:54:25   https://groups.google.com/forum/#!forum/android-building
> 18:54:25   https://issuetracker.google.com/issues/new?component=381517
>
> My best guess is that since this _might_ be related to nsjail container
> and apparmour, these warnings appear because I am running ubuntu inside a
> lxc container.
>
> I have two questions regarding this:
>
> 1. How fatal is it, do I need a machine running Ubuntu natively.
> 2. If the build system is being containerized, can i just rub the build on
> my fedora machine and not care about build environment as 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/c2d1ec8a-d092-4731-9db9-ed9ca1708d56%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/c2d1ec8a-d092-4731-9db9-ed9ca1708d56%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/CALQgHdn7nbOV62v6h_FB%3DW3CXxCtCkxC97-6fVJN87izPRt2vw%40mail.gmail.com.

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

['Dan Willemsen' via Android Building]

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://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/CALQgHdnY5PeNOyjbXMYfkFXQF_CMOFZ%2BsRQUXq0%2BgsSFr%2BXaUw%40mail.gmail.com.

Re: [android-building] 编译android-10.0.0_r1所遇到的问题

['Dan Willemsen' via Android Building]

This was a bug -- the build failed when there wasn't a vendor partition
(which isn't a built configuration anymore inside Google to due Treble).
You should be able to cherry-pick
https://android-review.googlesource.com/c/platform/build/+/970728 to fix
the problem.

- Dan

On Mon, Oct 28, 2019 at 9:48 PM 姜有川  wrote:

> Hello,
> I encountered the following error when compiling android-10.0.0_r1 under
> Ubuntu 16.04:
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=mini_emulator_x86_64
> TARGET_BUILD_VARIANT=userdebug
> 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.15.0-66-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=QP1A.190711.019
> OUT_DIR=out
> 
> [  0% 3/67918] build
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_dirs_system_intermediates/fs_config_dirs_system
> FAILED:
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_dirs_system_intermediates/fs_config_dirs_system
> /bin/bash -c "build/make/tools/fs_config/fs_config_generator.py fsconfig
>  --aid-header system/core/include/private/android_filesystem_config.h
>  --capability-header bionic/libc/kernel/uapi/linux/capability.h
>  --partition system --all-partitions  --dirs --out_file
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_dirs_system_intermediates/fs_config_dirs_system
>  /dev/null"
> usage: fs_config_generator.py fsconfig [-h] --aid-header AID_HEADER
>--capability-header
> CAPABILITY_HEADER
>--partition PARTITION
>[--all-partitions ALL_PARTITIONS]
>[--files] [--dirs] --out_file
> OUT_FILE
>fsconfig [fsconfig ...]
> fs_config_generator.py fsconfig: error: argument --all-partitions:
> expected one argument
> [  0% 6/67918] build
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_files_system_intermediates/fs_config_files_system
> FAILED:
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_files_system_intermediates/fs_config_files_system
> /bin/bash -c "build/make/tools/fs_config/fs_config_generator.py fsconfig
>  --aid-header system/core/include/private/android_filesystem_config.h
>  --capability-header bionic/libc/kernel/uapi/linux/capability.h
>  --partition system --all-partitions  --files --out_file
> out/target/product/mini-emulator-x86_64/obj/ETC/fs_config_files_system_intermediates/fs_config_files_system
>  /dev/null"
> usage: fs_config_generator.py fsconfig [-h] --aid-header AID_HEADER
>--capability-header
> CAPABILITY_HEADER
>--partition PARTITION
>[--all-partitions ALL_PARTITIONS]
>[--files] [--dirs] --out_file
> OUT_FILE
>fsconfig [fsconfig ...]
> fs_config_generator.py fsconfig: error: argument --all-partitions:
> expected one argument
> 09:49:47 ninja failed with: exit status 1
> make: *** [run_soong_ui] 错误 1
>
> I hope to get your help. Thank you very much.
> Best,
> Jiang
>
> --
> --
> 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/3292548b-da9e-4d67-9030-f95bd6d17726%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/3292548b-da9e-4d67-9030-f95bd6d17726%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 thi

Re: [android-building] Re: LineageOS 17.0 build in LXC 2.x - nsjail/sandboxing error

['Dan Willemsen' via Android Building]

So the actual error that's blocking you is:

build/make/target/product/updatable_apex.mk:21: error:
> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]:
> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.


But that's off-topic for this list, as Glenn mentions.

The nsjail error isn't fatal currently, but that's something we'd like to
change in the future (so that we can get better sandboxing within the build
and ensure reproducible/incremental builds work, etc). You may need to
tweak some of the settings w/LXC in order to allow nsjail to function, I
haven't used it. I know Docker has some known issues currently in which it
can't be configured to allow nsjail, but I'm hopeful that that will get
fixed.

- Dan

On Tue, Oct 22, 2019 at 11:58 AM 'Glenn Kasten' via Android Building <
android-building@googlegroups.com> wrote:

> Can you reproduce this problem with AOSP distribution?
> This discussion group is targeted at AOSP distribution per guidelines here
> <https://groups.google.com/forum/#!forum/android-building>.
> [I am a volunteer moderator]
>
> On Tuesday, October 22, 2019 at 9:08:28 AM UTC-7, Condor wrote:
>>
>> Hello,
>>
>> I've just tried building LineageOS 17.0 for fajita (OnePlus 6T). For
>> efficiency reasons and to maintain isolation from the host I've opted to
>> spin up an LXC container for this.
>> The host machine is running Debian 9 and LXC 2.x, while the container is
>> a Debian 10 machine. Apparently this doesn't support nsjail, which caused
>> "breakfast fajita" to fail.
>> A screenshot is available at
>> https://www.nixmagic.com/pics/lineage-nsjail-error.png.
>> I've followed the build guide at
>> https://wiki.lineageos.org/devices/fajita/build.
>> Below is the error log in text form.
>>
>> Looking for dependencies in kernel/oneplus/sdm845
>> kernel/oneplus/sdm845 has no additional dependencies.
>> Looking for dependencies in packages/resources/devicesettings
>> packages/resources/devicesettings has no additional dependencies.
>> Done
>> 15:31:05 Build sandboxing disabled due to nsjail error. This may become
>> fatal in the future.
>> 15:31:05 Please let us know why nsjail doesn't work in your environment
>> at:
>> 15:31:05 https://groups.google.com/forum/#!forum/android-building
>> 15:31:05 https://issuetracker.google.com/issues/new?component=381517
>> build/make/target/product/updatable_apex.mk:21: error:
>> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]:
>> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
>> 15:31:11 dumpvars failed with: exit status 1
>> 15:31:13 Build sandboxing disabled due to nsjail error. This may become
>> fatal in the future.
>> 15:31:13 Please let us know why nsjail doesn't work in your environment
>> at:
>> 15:31:13 https://groups.google.com/forum/#!forum/android-building
>> 15:31:13 https://issuetracker.google.com/issues/new?component=381517
>> build/make/target/product/updatable_apex.mk:21: error:
>> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]:
>> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
>> 15:32:42 dumpvars failed with: exit status 1
>>
>> ** Don't have a product spec for: 'lineage_fajita'
>> ** Do you have the right repo manifest?
>>
>> I wish I could explain why nsjail isn't available in LXC but
>> unfortunately I don't know either... I'll retry the build in a VM or on a
>> physical host.
>>
>> Best regards,
>> Michael De Roover (android-building at nixmagic dot 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/b8113ccb-73b0-4c6f-8cea-1cd29768f8e4%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/b8113ccb-73b0-4c6f-8cea-1cd29768f8e4%40googlegroups.com?utm_medium=email_source=footer>
> .
>

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

Re: [android-building] build "android-msm-marlin-3.18-pie-qpr2" miss buildinfo.py

['Dan Willemsen' via Android Building]

+Matthias Männich  for further investigation

It looks like this isn't in the AOSP version of the kernel/build project
(or the internal master branch either, only some of the older branches that
never made it to AOSP).

- Dan

On Tue, Oct 22, 2019 at 9:08 AM 阿嚏  wrote:

> aosp kernel "android-msm-marlin-3.18-pie-qpr2" build failed
>
> 
>  Running extra build command(s):
> + eval python build/buildinfo/buildinfo.py
> ++ python build/buildinfo/buildinfo.py
> python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such
> file or directory
>
> in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'".
>
> I can't find the buildinfo.py file. Is it my mistake? Did I miss the steps?
>
>
> --
> --
> 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/7e094c71-c781-4189-a3a4-bb060748ec82%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/7e094c71-c781-4189-a3a4-bb060748ec82%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/CALQgHdnE28a%2Bz-5BrHqwsP9_PXJ%3Dp7VpzX4pfZ2Q_ch%3DikSZrA%40mail.gmail.com.