mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
947f8f4ee9
This commit adds an empty recipe to dependencies of .aapt.deps, which forces the appropriate gecko-R.jar rebuild. This is because Make treats targets with no recipe at all differently than targets with an empty recipe, in a way that defeats our dependencies. What appeared to be happening is the following: Touch a resource. On the next build, .aapt.deps is stale, so aapt is invoked, which generates R.java, and we touch .aapt.deps. Now R.java depends on .aapt.deps, but this does not appear to force Make to consider targets that depend on R.java to be stale. A target that depends on R.java (such as gecko-R.jar) itself compares timestamps and finds that gecko-R.jar is newer than R.java (from the previous build), and this comparison appears to happen before aapt is invoked. So even though .aapt.deps is seen to be stale, and by transitivity R.java is stale, this does not mark gecko-R.jar as stale. The timestamp check between R.java and gecko-R.jar appears to happen *before* aapt is invoked. On the second build following the update, the R.java generated in the previous build is newer than gecko-R.jar, triggering the observed rebuild of gecko-R.jar. |
||
---|---|---|
.. | ||
android | ||
locales |