Failing to build sdk and sdk_addon in master P

[konstanti...@motorolasolutions.com]

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

[Dan Willemsen]

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

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

[konstanti...@motorolasolutions.com]

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?

[Dan Willemsen]

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

[konstanti...@motorolasolutions.com]

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

[Dan Willemsen]

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

[konstanti...@motorolasolutions.com]

Hey Dan,

Yeah this worked indeed.

Thank you for all the help so far! 

Good luck and have a Great Weekend,

Konstantin