Fix comment on how java rules handle unknown output files am: f7eac7a2ac
am: a14eee8e4a
Change-Id: Id664781384aaad7bdaf0855addb88025bdd60c4a
This commit is contained in:
commit
4bc286eca9
1 changed files with 3 additions and 3 deletions
|
@ -35,9 +35,9 @@ var (
|
||||||
// Compiling java is not conducive to proper dependency tracking. The path-matches-class-name
|
// Compiling java is not conducive to proper dependency tracking. The path-matches-class-name
|
||||||
// requirement leads to unpredictable generated source file names, and a single .java file
|
// requirement leads to unpredictable generated source file names, and a single .java file
|
||||||
// will get compiled into multiple .class files if it contains inner classes. To work around
|
// will get compiled into multiple .class files if it contains inner classes. To work around
|
||||||
// this, all java rules write into separate directories and then a post-processing step lists
|
// this, all java rules write into separate directories and then are combined into a .jar file
|
||||||
// the files in the the directory into a list file that later rules depend on (and sometimes
|
// (if the rule produces .class files) or a .srcjar file (if the rule produces .java files).
|
||||||
// read from directly using @<listfile>)
|
// .srcjar files are unzipped into a temporary directory when compiled with javac.
|
||||||
javac = pctx.AndroidGomaStaticRule("javac",
|
javac = pctx.AndroidGomaStaticRule("javac",
|
||||||
blueprint.RuleParams{
|
blueprint.RuleParams{
|
||||||
Command: `rm -rf "$outDir" "$annoDir" "$srcJarDir" && mkdir -p "$outDir" "$annoDir" "$srcJarDir" && ` +
|
Command: `rm -rf "$outDir" "$annoDir" "$srcJarDir" && mkdir -p "$outDir" "$annoDir" "$srcJarDir" && ` +
|
||||||
|
|
Loading…
Reference in a new issue