Граф коммитов

2 Коммитов

Автор SHA1 Сообщение Дата
cjhopman 70e3a8bbaa Fix generation of java enums
java_cpp_enum.gypi was creating all enums in the same root folder and
then adding that folder to its dependents generated_src_dirs. This has
two issues: first, incremental builds will include stale files when
things are moved/renamed/etc. second, all libraries that depend on such
an enum target will actually compile and include all the enum targets
(and in fact may even include different versions of one enum in
 different libraries).

This change just makes each such target use its own unique directory
(this will still have the stale enum issue when renaming an enum if the
 target name doesn't change, but that is very rare).

The GN version already used unique directories.

TBR=mkosiba

Review URL: https://codereview.chromium.org/578363002

Cr-Original-Commit-Position: refs/heads/master@{#295595}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: e98bcec0ee81f43526ad06a2e27a1cdc3ef7f190
2014-09-18 23:20:47 +00:00
mkosiba bcf73b21f3 New C++ -> Java enum build rule + parser/generator.
This adds a new build rule for generating Java constants for C++ enums.

BUG=405532
TBR=brettw@chromium.org

Review URL: https://codereview.chromium.org/484603004

Cr-Original-Commit-Position: refs/heads/master@{#294153}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 9610607d5adf4afd2ad821c94434cd749041268a
2014-09-10 10:54:40 +00:00