[Android] Makefile regen rule doesn't work

[GoogleCodeExporter]

This means that the generated makefiles aren't portable. Is portability a goal 
of gyp-generated makefiles? Do other backends have the same problem?

Makefile regeneration is currently not used by Chromium on Android, so this is 
low priority.

See also http://code.google.com/p/gyp/issues/detail?id=281

Original issue reported on code.google.com by stevebl...@chromium.org on 5 Jul 2012 at 9:43

• Blocking: #275

[GoogleCodeExporter]

Original comment by torne@chromium.org on 18 Oct 2012 at 9:11

[GoogleCodeExporter]

Original comment by torne@chromium.org on 7 Dec 2012 at 12:19

• Now blocking: #275

[GoogleCodeExporter]

Having looked into this more, it seems like actually the makefile regeneration 
rules have a lot more problems than this (they don't always get generated to 
the right place, either) and since we aren't using this support and aren't 
likely to ever need it for WebView it's probably simplest to just delete this 
code from the backend. Retitling bug appropriately.

Original comment by torne@chromium.org on 7 Dec 2012 at 12:23

• Changed title: [Android] Makefile regen rule doesn't work

[GoogleCodeExporter]

Support for makefile regeneration has been disabled in gyp r1545.

Original comment by torne@chromium.org on 10 Dec 2012 at 2:44

• Changed state: Fixed