1. 12 Apr, 2016 1 commit
  2. 11 Apr, 2016 4 commits
  3. 10 Apr, 2016 1 commit
  4. 09 Apr, 2016 1 commit
  5. 08 Apr, 2016 9 commits
  6. 07 Apr, 2016 11 commits
  7. 06 Apr, 2016 9 commits
  8. 05 Apr, 2016 4 commits
    • Brad King's avatar
    • Brad King's avatar
      Ninja: Restat custom command byproducts even with a SYMBOLIC output (#16049) · add7abc8
      Brad King authored
      The change in commit v3.5.0-rc1~198^2 (Ninja: Always re-run custom
      commands that have symbolic dependencies, 2015-11-19) broke the
      byproducts feature added by commit v3.2.0-rc1~340^2~2 (Add an option for
      explicit BYPRODUCTS of custom commands, 2014-11-13) when SYMBOLIC
      outputs also appear.  This case occurs with AUTORCC-generated custom
      targets because the output is SYMBOLIC (to always run) and the generated
      file is a byproduct (for restat so dependents do not run unnecessarily).
      
      The two use cases conflict because Ninja does not support per-output
      restat.  Favor restat whenever byproducts are present because it is
      required for byproducts to work correctly.  In use cases where we want
      an always-run chain we simply will not be able to also use byproducts.
      add7abc8
    • Brad King's avatar
      Ninja: Fix detection of custom command symbolic outputs · ff805113
      Brad King authored
      Fix logic introduced by commit v3.5.0-rc1~198^2 (Ninja: Always re-run
      custom commands that have symbolic dependencies, 2015-11-19) to not
      consider only the last output.  We need to know if any output is
      SYMBOLIC, so stop checking as soon as one is found.
      ff805113
    • Brad King's avatar
      4ffd85cf