Re: [android-building] How to include prebuilt jars using bp in Android P
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 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
Re: [android-building] Building Marlin For Nexus 5X -- Cannot Flash Build Product To Device.
I understand this now. Thanks. I misunderstood the codename as referring to an Android build, not the device itself. This topic can be closed. Thanks. On Tuesday, September 25, 2018 at 1:33:10 PM UTC-4, Colin Cross wrote: > > marlin images are for the Pixel XL, they are not compatible with the Nexus > 5x (bullhead). > > On Tue, Sep 25, 2018 at 12:31 AM American Justice Corp < > americanj...@gmail.com > wrote: > >> Target Device: Nexus 5X >> Development Host: Linux, Slackware 14.2, 64-Bit, x86_64 Desktop Hardware. >> >> This posting is regarding installing, (flashing) a "userdebug" build of >> marlin, (repo sync'd on 21 Sept. 2018), to a Nexus 5X Device, >> that is built unmodified via the "repo" commands, "lunch" and "make >> droid". >> >> Android Studio, and Platform Tools are installed and up to date. Android >> Studio has been used successfully to build sample Apps, push them to device, >> and run them on device. >> >> The repo folder on the Development Host is sync'd, (as of 21 September >> 2018). >> >> After a "repo init" and "repo sync", the lunch menu has 37 items. Item >> #19 is "aosp_marlin-userdebug" >> >> After selecting "aosp_marlin-userdebug", (#19), from the Lunch Menu, >> "make "adb" and "make fastboot" work. >> >> adb and fastboot command line programs, (whether from Platform Tools, >> or after "make adb" or "make fast boot"), work fine for shell access to >> the device, push, pull, bootloader unlock, and flashing with files obtained >> from here: >> >> https://developers.google.com/android/images >> >> The commands in flash-all.sh all work fine to successfully flash device >> with its latest "Factory" image, (Bullhead), ID: 8.1.0 >> (OPM6.171019.030.K1, Sep 2018) >> >> >> Then, running "make droid", (for aosp-marlin-userdebug"), successfully >> builds the various Target Device Image Files, for Marlin, and puts them in >> $OUT. (After a Glacial Epoch of Time). >> >> >> Prior to flashing the device with the Image Files created from "make >> droid", I tried to flash the device with a Marlin System Image, ID: >> image-marlin-njh34c.zip from *marlin-njh34c-factory-be914eaa.zip* >> ) >> The error message I get is: >> >> *fastboot -w update image-marlin-njh34c.zip* >> >> * * >> >> *Bootloader Version...: BHZ31b* >> >> *Baseband Version.: M8994F-2.6.41.5.01* >> >> *Serial Number: 0255046c4c403d85* >> >> * * >> >> *extracting android-info.txt (0 MB) to RAM...* >> >> *Checking 'product' FAILED* >> >> >> *Device product is 'bullhead'.* >> >> *Update requires 'marlin' or 'sailfish'.* >> >> >> So, as far as I can tell, the "build" process works fine, but if the >> "stock" Marlin image cannot be installed on the device, how can one built >> from source be flashed onto the device? >> >> >> I picked an earlier release, Major Version "7" Because I thought it >> should work. I will update this post after I try the latest "marlin" and >> "sailfish" Updates in version "8" and "9" >> >> -- >> -- >> 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.
Re: [android-building] Building Marlin For Nexus 5X -- Cannot Flash Build Product To Device.
marlin images are for the Pixel XL, they are not compatible with the Nexus 5x (bullhead). On Tue, Sep 25, 2018 at 12:31 AM American Justice Corp < americanjusticec...@gmail.com> wrote: > Target Device: Nexus 5X > Development Host: Linux, Slackware 14.2, 64-Bit, x86_64 Desktop Hardware. > > This posting is regarding installing, (flashing) a "userdebug" build of > marlin, (repo sync'd on 21 Sept. 2018), to a Nexus 5X Device, > that is built unmodified via the "repo" commands, "lunch" and "make droid". > > Android Studio, and Platform Tools are installed and up to date. Android > Studio has been used successfully to build sample Apps, push them to device, > and run them on device. > > The repo folder on the Development Host is sync'd, (as of 21 September > 2018). > > After a "repo init" and "repo sync", the lunch menu has 37 items. Item #19 > is "aosp_marlin-userdebug" > > After selecting "aosp_marlin-userdebug", (#19), from the Lunch Menu, "make > "adb" and "make fastboot" work. > > adb and fastboot command line programs, (whether from Platform Tools, or > after "make adb" or "make fast boot"), work fine for shell access to the > device, push, pull, bootloader unlock, and flashing with files obtained > from here: > > https://developers.google.com/android/images > > The commands in flash-all.sh all work fine to successfully flash device > with its latest "Factory" image, (Bullhead), ID: 8.1.0 > (OPM6.171019.030.K1, Sep 2018) > > > Then, running "make droid", (for aosp-marlin-userdebug"), successfully > builds the various Target Device Image Files, for Marlin, and puts them in > $OUT. (After a Glacial Epoch of Time). > > > Prior to flashing the device with the Image Files created from "make > droid", I tried to flash the device with a Marlin System Image, ID: > image-marlin-njh34c.zip from *marlin-njh34c-factory-be914eaa.zip* > ) > The error message I get is: > > *fastboot -w update image-marlin-njh34c.zip* > > * * > > *Bootloader Version...: BHZ31b* > > *Baseband Version.: M8994F-2.6.41.5.01* > > *Serial Number: 0255046c4c403d85* > > * * > > *extracting android-info.txt (0 MB) to RAM...* > > *Checking 'product' FAILED* > > > *Device product is 'bullhead'.* > > *Update requires 'marlin' or 'sailfish'.* > > > So, as far as I can tell, the "build" process works fine, but if the > "stock" Marlin image cannot be installed on the device, how can one built > from source be flashed onto the device? > > > I picked an earlier release, Major Version "7" Because I thought it should > work. I will update this post after I try the latest "marlin" and > "sailfish" Updates in version "8" and "9" > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google 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
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 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.
[android-building] Building minikin into shared library for NDK use
I have synced the entire AOSP just to build the framework/minikin into a shared library and use it with NDK. Any instruction on this? Thanks for any 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.
[android-building] Building Marlin For Nexus 5X -- Cannot Flash Build Product To Device.
Target Device: Nexus 5X Development Host: Linux, Slackware 14.2, 64-Bit, x86_64 Desktop Hardware. This posting is regarding installing, (flashing) a "userdebug" build of marlin, (repo sync'd on 21 Sept. 2018), to a Nexus 5X Device, that is built unmodified via the "repo" commands, "lunch" and "make droid". Android Studio, and Platform Tools are installed and up to date. Android Studio has been used successfully to build sample Apps, push them to device, and run them on device. The repo folder on the Development Host is sync'd, (as of 21 September 2018). After a "repo init" and "repo sync", the lunch menu has 37 items. Item #19 is "aosp_marlin-userdebug" After selecting "aosp_marlin-userdebug", (#19), from the Lunch Menu, "make "adb" and "make fastboot" work. adb and fastboot command line programs, (whether from Platform Tools, or after "make adb" or "make fast boot"), work fine for shell access to the device, push, pull, bootloader unlock, and flashing with files obtained from here: https://developers.google.com/android/images The commands in flash-all.sh all work fine to successfully flash device with its latest "Factory" image, (Bullhead), ID: 8.1.0 (OPM6.171019.030.K1, Sep 2018) Then, running "make droid", (for aosp-marlin-userdebug"), successfully builds the various Target Device Image Files, for Marlin, and puts them in $OUT. (After a Glacial Epoch of Time). Prior to flashing the device with the Image Files created from "make droid", I tried to flash the device with a Marlin System Image, ID: image-marlin-njh34c.zip from *marlin-njh34c-factory-be914eaa.zip* ) The error message I get is: *fastboot -w update image-marlin-njh34c.zip* * * *Bootloader Version...: BHZ31b* *Baseband Version.: M8994F-2.6.41.5.01* *Serial Number: 0255046c4c403d85* * * *extracting android-info.txt (0 MB) to RAM...* *Checking 'product' FAILED* *Device product is 'bullhead'.* *Update requires 'marlin' or 'sailfish'.* So, as far as I can tell, the "build" process works fine, but if the "stock" Marlin image cannot be installed on the device, how can one built from source be flashed onto the device? I picked an earlier release, Major Version "7" Because I thought it should work. I will update this post after I try the latest "marlin" and "sailfish" Updates in version "8" and "9" -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google 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: Soong confusion
I'm also a long-time pre-8.0 developer who has added many packages and heavily customized the framework. How does one unconditionally make (-B) all targets within a given package using the new build system? Thanks, -John On Tuesday, December 12, 2017 at 2:08:35 PM UTC-8, Colin Cross wrote: > > > > On Mon, Dec 11, 2017 at 1:50 PM, Jacob Abrams > wrote: > >> Hello, >> >> I would like to voice protest over the AOSP build system switch from Make >> to Soong. Make is not a perfect tool but it is well documented and >> extremely stable. The introduction of ninja into AOSP was seamless and >> acceptable. However, migrating away from Make to a totally new tool with >> zero history is a serious set back. Why not instead choose Bazel, Tup, >> Gradle, Buck or simply stick with what works? >> >> I read the following statements from one of the developers of Soong build: >> >> > One of our goals for build health is to reduce the number of different >> > ways we build modules. Adding too many build flags makes it harder to >> > tell if a change will break the build, and hard to run tests. We >> > would much rather compiling everything the same on all devices, and >> > then determine which parts to use at runtime. >> >> It is unclear what is meant by "reduce the number of different ways we >> build modules.", nor is it clear what is meant by "We would much rather >> compiling everything the same on all devices". This seems to conflict with >> the example of LLVM where the build basically consists of completely custom >> go code: >> https://android.googlesource.com/platform/external/llvm/+/master/soong/llvm.go >> >> Clearly this custom go code does not reduce the number of different ways >> modules are built. >> > > Some teams have existing flows where they want to locally modify the way > they build, and we've supported those through the custom go code for those > modules. In general we still try to avoid them. > > >> I assume this is an attempt to improve build performance yet again, but >> it ends up wasting thousands of engineering hours across the globe. >> Engineers must figure out a new system that likely contains numerous bugs >> and could possibly be destined for the dustbin if it is not maintained >> properly or turns out to be inferior. If the goal is to improve build >> performance perhaps Google engineers could explore an under-the-hood >> contribution to Make itself? >> > > As Glenn pointed out, the purpose for Soong is not primarily performance, > it is correctness and reliability. Before Soong (and the conversion to > Ninja was part of Soong), incremental builds were completely unreliable, > requiring significant knowledge of the internals of the Android build for > platform developers to get anything done. Wiping the entire output > directory and rebuilding was common. Incremental builds are now reliable > enough to be used in our continuous build infrastructure. > > Debugging typos in Android.mk files was also very painful. LOCAL_CFALGS > instead of LOCAL_CFLAGS gets silently ignored, deleting a module that still > has users doesn't break incremental builds but breaks clean builds, > overwriting variables that are being used by other modules, subtle > differences between := and =, or ifdef blah and ifneq(,$(blah)). All of > these problems are fundamental to the way that Make works and can't be > fixed. > > We've explored various options with Make (for a while we had a modified > version of Make that would cache its build rules). The conversion to Ninja > (and all of the speed and reliability improvements that came with it) was > done by using Kati instead of Make, and we've continued to invest in new > features there. But most of the improvements have come from moving the > very complex build code out of the terrible Make language and into a high > level, maintainable, testable language. > > Android is mature; it deserves a mature build system. >> >> Jacob Abrams >> >> -- >> -- >> 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. >> > > > On Mon, Dec 11, 2017 at 1:50 PM, Jacob Abrams > wrote: > >> Hello, >> >> I would like to voice protest over the AOSP build system switch from Make >> to Soong. Make is not a perfect tool but it is well documented and >> extremely stable. The introduction of ninja into AOSP was seamless and >> acceptable.
