From 4840966807557ce529c9c6ea8a71ad7eebe24392 Mon Sep 17 00:00:00 2001 From: Ben Liblit Date: Sat, 31 Mar 2018 18:04:00 -0500 Subject: [PATCH] Don't try to exhaustively anticipate all generated header names When JNI headers for a given class, each nested class will end up with its own additional header. But I don't want to try to parse nested class details out of the Java source files just so we can determine exactly which headers will be created. Instead, simply treat the entire header destination directory as the output of this task. --- com.ibm.wala.cast.test/build.gradle | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/com.ibm.wala.cast.test/build.gradle b/com.ibm.wala.cast.test/build.gradle index 01032002b..7a1021996 100644 --- a/com.ibm.wala.cast.test/build.gradle +++ b/com.ibm.wala.cast.test/build.gradle @@ -32,7 +32,7 @@ task generateJniHeaders(type: Exec, dependsOn: [testClasses, ':com.ibm.wala.cast headerDir = "$buildDir/include" } inputs.files files(qualifiedClasses.collect { "$buildDir/${it.replace('.', '/')}.class" }) - outputs.files files(qualifiedClasses.collect { "$headerDir/${it.replace('.', '_')}.h" }) + outputs.dir headerDir outputs.cacheIf { true } // javah command to generate headers