i fell into the dependency target 'chrome_public_apk/compile.stamp' and what i noticed on this Ninja target is the two lines from screenshot which are marked by Vim cursor../../build/android/gyp/util/build_utils.py../../build/android/gyp/javac.pyAFAIK, Ninja interprets those two lines as two explicit dependency targets
but i could not find definitions for those two targets. On the other hand, i did try with some sample .ninja script and could confirm that the missing of definitions for dependency targets results in build failure.Hence, my question is how Ninja processes the two links to Python scripts in this case?
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
@newt:
Ninja scripts are the most reliable source for me to understand what is compiled/packaged in Android Chromium. So i feel uncomfortable while hitting the scripts that seem to be out of logic.
@Nico:
The syntax of build statement in Ninja is as following:
build out_put_files_separated_by_spaces name_of_rule : input_files_separated_by_spaces
https://martine.github.io/ninja/manual.html#ref_dependencies
I read the reference guide of Ninja and tried some tests with some simple Ninja scripts and i experienced that the input_files_separated_by_spaces is also interpreted as list of dependency targets.
And following this logic, the two links to Python scripts refer to dependency targets, which is actually not the case.