Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.
You can actually hold the timestamp stable in system/build.prop too, by setting the BUILD_DATETIME environment variable to a stable value (it's the number of seconds since the unix epoch, normally generated with `date +%s`). Since we've focused on keeping the individual files identical while accepting a handful of known differences, the actual image generation may not be as stable as we'd like it to be. That's just not as well tested, as we've been mostly comparing individual files when converting make-based functionality to our new build system. - Dan On Sun, Dec 23, 2018 at 8:18 AM Vitaliy Freidovich wrote: > Hello, > > I would kindly disagree, as your environment might change from build to > build, and the resulting images could theoretically, and perhapps > practically, behave differently. Thus it's a correct bahaviour in my > opinion that the checksum changes. > > Good luck, > > On Fri 21 Dec 2018, 5:58 p.m. , wrote: > >> Hi Android Experts, >> >> >> >>We need some help / information that, Is there any way >> to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] >> same even after fresh build or recompilation??. Even though without >> changing a single bit in the AOSP Source code if we rebuild it, Android >> binaries checksum keeps changing. As I can understand that the >> compilers/linkers adds the date and time-stamp to the images/binaries after >> each build which causes the change in the checksum. So my question, Is >> there any way to avoid this change in image checksum after every rebuild. >> it should change only when we change any source code. kindly update. >> >> -- >> -- >> 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. > -- -- 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 maintain android binaries checksum intact. after rebuild of AOSP.
Hello, I would kindly disagree, as your environment might change from build to build, and the resulting images could theoretically, and perhapps practically, behave differently. Thus it's a correct bahaviour in my opinion that the checksum changes. Good luck, On Fri 21 Dec 2018, 5:58 p.m. , wrote: > Hi Android Experts, > > > >We need some help / information that, Is there any way > to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] > same even after fresh build or recompilation??. Even though without > changing a single bit in the AOSP Source code if we rebuild it, Android > binaries checksum keeps changing. As I can understand that the > compilers/linkers adds the date and time-stamp to the images/binaries after > each build which causes the change in the checksum. So my question, Is > there any way to avoid this change in image checksum after every rebuild. > it should change only when we change any source code. kindly update. > > -- > -- > 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 maintain android binaries checksum intact. after rebuild of AOSP.
We work pretty hard to make sure that the contents of the system image don't change unless the source tree is changed, and AOSP master should be in pretty good shape, although bugs do creep in sometimes. The build time and build number are stored in system/build.prop and change on every build though. The build number can be fixed on the command line with m BUILD_NUMBER=12345, but there is currently no way to fix the build date. You would need to edit build/make/tools/buildinfo_common.sh to not use $DATE to get the current timestamp. We would accept patches that made the build date settable from the command line. On Fri, Dec 21, 2018 at 7:58 AM wrote: > Hi Android Experts, > > > >We need some help / information that, Is there any way > to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] > same even after fresh build or recompilation??. Even though without > changing a single bit in the AOSP Source code if we rebuild it, Android > binaries checksum keeps changing. As I can understand that the > compilers/linkers adds the date and time-stamp to the images/binaries after > each build which causes the change in the checksum. So my question, Is > there any way to avoid this change in image checksum after every rebuild. > it should change only when we change any source code. kindly update. > > -- > -- > 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.
[android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.
Hi Android Experts, We need some help / information that, Is there any way to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] same even after fresh build or recompilation??. Even though without changing a single bit in the AOSP Source code if we rebuild it, Android binaries checksum keeps changing. As I can understand that the compilers/linkers adds the date and time-stamp to the images/binaries after each build which causes the change in the checksum. So my question, Is there any way to avoid this change in image checksum after every rebuild. it should change only when we change any source code. kindly update. -- -- 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.
