Hey Dan,
Yeah this worked indeed.
Thank you for all the help so far!
Good luck and have a Great Weekend,
Konstantin
On Wednesday, January 2, 2019 at 11:29:28 PM UTC+2, Dan Willemsen wrote:
>
> Ah, that's right. The SDK targets build with different TARGET_PRODUCT
> values -- use
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:
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:
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:
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,
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
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
