CyanogenMod/android_vendor_cm — comment on commit bc1f988afaea186c5ad508fff550189d98698bbb
File: config/common.mk line 108
By kmobs:

As long as a device's vendor has stabilized and you're only building for
one target, incremental builds should be fine (besides the obvious
build.prop issue)
On Feb 18, 2012 4:57 PM, "Justin White" <
reply@reply.github.com>
wrote:

> Good to know. I do incremental builds for myself because my little VM takes
> quite a while to do a fresh build.
> On Feb 18, 2012 5:55 PM, "Keyan Mobli" <
> reply@reply.github.com>
> wrote:
>
> > All nightlies are clobber builds meaning there is no build.prop there to
> > begin with.
> > On Feb 18, 2012 4:52 PM, "Justin White" <
> > reply@reply.github.com>
> > wrote:
> >
> > > This is very much what I had in mind with my Build Date addition to the
> > > Device Info screen. Will be good to keep the time info out of
> cm.version,
> > > though.
> > > Will this change cause the datestamp to be updated on every build, or
> > only
> > > when build.prop is first created? One issue with my mod is that if
> you're
> > > not doing a fresh build, you must remove
> > > out/target/product/*/system/build.prop by hand so it will be recreated
> > and
> > > have a current datestamp.
> > >
> > > ---
> > > Reply to this email directly or view it on GitHub:
> > >
> > >
> >
> https://github.com/CyanogenMod/android_vendor_cm/commit/bc1f988afaea186c5ad508fff550189d98698bbb#commitcomment-981759
> > >
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> >
> https://github.com/CyanogenMod/android_vendor_cm/commit/bc1f988afaea186c5ad508fff550189d98698bbb#commitcomment-981762
> >
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/CyanogenMod/android_vendor_cm/commit/bc1f988afaea186c5ad508fff550189d98698bbb#commitcomment-981764
>