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 <konstantin.kara...@motorolasolutions.com> 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 <konstanti...@motorolasolutions.com> >> 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.
