Re: [android-building] Re: Android 8.1.0 Oreo MR1 Released
On Fri, May 25, 2018 at 7:49 AM Chih-Wei Huang wrote: > Thank you for the update. > > However, I always feel uneasy why the updated tag is not a fast-forward > commit of previous release. > Worse, usually there are explicitly conflicts between them. > > For example, in frameworks/av, merging > > android-8.1.0_r22 to > > android-8.1.0_r25 (or r29) > results in the conflicts: > These tags were from different branches, see https://source.android.com/setup/start/build-numbers for additional information. You should use tag for the build of the same branch that corresponds to the desired security level; if it's not possible (e.g. branch was switched for the device, etc.), it's usually easier to cherry-pick your local modifications over the latest tag. Cheers, -- -- 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 P Preview 2 AOSP build issue (Pixel/sailfish)
*Thanks for the answer. +1* El jueves, 24 de mayo de 2018, 17:20:47 (UTC+2), Satish Patel escribió: > > Hi Jean, > > need to apply 3 fix for build, reference at# > https://groups.google.com/forum/#!topic/android-building/MYF2ZmXbmQo > > prebuilts/tools: > git fetch https://android.googlesource.com/platform/prebuilts/tools > refs/changes/02/682002/1 && git cherry-pick FETCH_HEAD > > external/e2fsprogs/ > git fetch https://android.googlesource.com/platform/external/e2fsprogs > refs/changes/05/683305/1 && git cherry-pick FETCH_HEAD > > external/f2fs-tools > git fetch https://android.googlesource.com/platform/external/f2fs-tools > refs/changes/06/683306/1 && git cherry-pick FETCH_HEAD > > -- > satish > > On Thursday, May 17, 2018 at 8:01:50 PM UTC+5:30, Jean-Marc GRIMAUD wrote: >> >> Ok thank you, that's very clear. >> >> -- -- 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] Has anyone built AOSP with Ubuntu 18.04?
Curious if anyone out there tried to build android on Ubuntu 18.04? If so any notes you can provide on the experience? 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.
[android-building] Re: Android 8.1.0 Oreo MR1 Released
Thank you for the update. However, I always feel uneasy why the updated tag is not a fast-forward commit of previous release. Worse, usually there are explicitly conflicts between them. For example, in frameworks/av, merging android-8.1.0_r22 to android-8.1.0_r25 (or r29) results in the conflicts: git merge android-8.1.0_r25 Auto-merging media/libmediaplayerservice/include/MediaPlayerInterface.h CONFLICT (content): Merge conflict in media/libmediaplayerservice/include/MediaPlayerInterface.h Auto-merging media/libmediaplayerservice/MediaPlayerService.h CONFLICT (content): Merge conflict in media/libmediaplayerservice/MediaPlayerService.h Auto-merging media/libmediaplayerservice/MediaPlayerService.cpp CONFLICT (content): Merge conflict in media/libmediaplayerservice/MediaPlayerService.cpp Auto-merging media/libmediaplayerservice/MediaPlayerFactory.h CONFLICT (content): Merge conflict in media/libmediaplayerservice/MediaPlayerFactory.h Auto-merging media/libmediaplayerservice/MediaPlayerFactory.cpp CONFLICT (content): Merge conflict in media/libmediaplayerservice/MediaPlayerFactory.cpp Recorded preimage for 'media/libmediaplayerservice/MediaPlayerFactory.cpp' Recorded preimage for 'media/libmediaplayerservice/MediaPlayerFactory.h' Recorded preimage for 'media/libmediaplayerservice/MediaPlayerService.cpp' Recorded preimage for 'media/libmediaplayerservice/MediaPlayerService.h' Recorded preimage for 'media/libmediaplayerservice/include/MediaPlayerInterface.h' Automatic merge failed; fix conflicts and then commit the result. After checking the git history, I was surprised to find the conflicts result from the two commits: commit 8a54af87b632c03ff2ae15a4a08880 1bb39fdae7 Author: Pawin Vongmasa Date: Sun Dec 17 02:31:18 2017 -0800 Refactor MediaPlayerBase's notify and commit 5ffa7ea0dfa9ba3eba8ded0878c5293dc35e74a9 Author: Pawin Vongmasa Date: Tue Dec 12 01:56:40 2017 -0800 Prevent MediaPlayerService::Client's use-after-free More precisely, android-8.1.0_r22 contains the patch "Refactor MediaPlayerBase's notify" but android-8.1.0_r29 doesn't. Digging deeper, I found git log of android-8.1.0_r29 still contains "Refactor MediaPlayerBase's notify" (commit d12c3600c8), but it was silently removed by commit dd6cda64 (Snap for 4657601 from 18cd9b58775e53b2ec1ffe571d165ad8fddfeff4 to oc-m4-release). This doesn't look right to me. If "Refactor MediaPlayerBase's notify" is unnecessary, shouldn't it be reverted explicitly? Could anyone explain what happened? Xin Li於 2018年5月15日星期二 UTC+8上午4時58分39秒寫道： > > Hi all, > > Android 8.1.0 Oreo MR1 source code is now available. The following build, > tag, and device is supported: > > - OPM2.171019.029.A1, android-8.1.0_r25, Nexus 6P (angler) > > 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 > device: > > Tag | Project| Branch | Device > android-8.1.0_r0.50 | kernel/msm | android-msm-angler-3.10-oreo-m2 | Nexus > 6P (OPM2.171019.029.A1) > -- -- 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] Heap size increase without jack help
I'm running VM with 3GB and 20GB exchange zone,looks like pretty small,hah? -- -- 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: Building vendor variants of a module on Android P
Hi, Actually I investigated a bit more and it looks like though the soong detects that the modules are on different namespace , but since the Ninja build system builds for all targets, and it fails identify that those they are same binaries/modules ,they are on different namespaces ninja: error: out/soong/build.ninja:455718: multiple rules generate out/soong/host/linux-x86/nativetest64/art_dex2oat_tests/dex2oat_image_test [-w dupbuild=err] . I am not sure then how can we build both core and vendor modules with same names ..Even I tried enabling vndk in the core lib, but it finally ends with the above errors of ninja. Any help is appreciated thanks ! Regards Priyanka On Tuesday, May 22, 2018 at 7:44:45 PM UTC+5:30, Priyanka Bose wrote: > > Hi, > > We are using the Android P preview release where we see that soong build > system has been changed to no longer depend on subdirs , > and as I understand it will include all the Android.bp files from the root > directory in the Android.bp list. > Actually we are working on a vendor variant of libart.so and till lately > we could use the conditional environment variable setting to check which > source code to be built. > Thus excluding the Android.bp files for the core variant . > For eg: we have a Module A in both the Android.bp files located in > different folders for Core and our vendor variant. > We used to read which variant to be built/enabled with an environment > variable setting and include those Android.bp for the variant folder . > > But with the latest master of Android P , this seems to be not possible > and we end up in multiple definitions since we have the similar module > names in the Android.bp files for > both core and vendor variants. > I see there is a new feature called VNDK , i tried to use it with "vendor: > true" in Android.bp file but that seems to also not help me. > > Can you let me know if an VNDK is an option we can use for this or any > suggestions ? > > Regards, > Priyanka > > -- -- 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.
