💡 Fix jmake root_build_dir vs root_out_dir

build/config/android/internal_rules.gni

Index: build/config/android/internal_rules.gni
diff --git a/build/config/android/internal_rules.gni b/build/config/android/internal_rules.gni
index ffe5bf37ab578d2910c9f4f244bbdc464b2716ed..1c79ba54ac5fb054975453f92b6cb986a765b1d9 100644
--- a/build/config/android/internal_rules.gni
+++ b/build/config/android/internal_rules.gni
@@ -1580,8 +1580,8 @@ template("compile_java") {
     ]
     if (_enable_incremental_javac) {
       args += [ "--incremental" ]
-      deps += [ "//third_party/jmake" ]
-      inputs += [ "$root_out_dir/bin/jmake" ]
+      deps += [ "//third_party/jmake($default_toolchain)" ]

[Dirk Pranke, 2016/06/03 18:19:34]

Are you sure this shouldn't be ($host_toolchain) ? Why would we run jmake on the
target?

[agrieve, 2016/06/03 18:49:58]

Toolchains & targets are a funny thing. Arguably we'd want to have a toolchain
just for java targets. E.g. with monochrome, we'll be rebuilding all the java
for arm64 and arm32, even though it's identical.

For this change, I figured using the version of jmake in the outermost build
directory made the most sense. 

+      inputs += [ "$root_build_dir/bin/jmake" ]
       outputs += [ "${_javac_jar_path}.pdb" ]
     }
     if (_supports_android) {