search

wutingcindy / gyp

Automatically exported from code.google.com/p/gyp
0 stars 0 forks source link

Android backend: make gyp target name aliases optional #341

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently given a target "foo" with mangled name "bar_foo_gyp" we generate both 
a target "bar_foo_gyp" and an alias for it "foo". This causes name collisions 
in the Android tree since some of the unmangled names are fairly generic. 
However, we depend on these aliases to run gyp tests since the test framework 
is not aware of the name mangling scheme.

There should be a generator option to control whether these aliases are 
generated or not.

Original issue reported on code.google.com by torne@chromium.org on 17 May 2013 at 2:33

GoogleCodeExporter commented 9 years ago

Original comment by torne@chromium.org on 17 May 2013 at 2:38

GoogleCodeExporter commented 9 years ago

Original comment by torne@chromium.org on 2 Apr 2014 at 5:35

GoogleCodeExporter commented 9 years ago 
Implemented in r1886; pass -G write_alias_targets=0 to skip writing the aliases.

Original comment by torne@chromium.org on 4 Apr 2014 at 10:25