1. 19 Nov, 2018 1 commit
    • Frank Benkstein's avatar
      configure_file: canonicalize input and output path in dependencies · 57701227
      Frank Benkstein authored
      Represent the input file path internally in canonical form.  Otherwise
      multiple `configure_file` calls that share the same input file but specify
      it relative to different directories (e.g. via `../`) result in multiple
      copies of the dependency on the rule to re-run CMake.  This causes the
      Ninja generator to emit duplicate phony build statements for these
      dependencies, which generates an error with `-w dupbuild=err`, which
      will be default in Ninja 1.9.
      
      Also canonicalize the output path for consistency.
      
      Add a test case.
      
      Fixes: #18584
      57701227
  2. 13 Nov, 2018 1 commit
    • Frank Benkstein's avatar
      configure_file: canonicalize input and output path in dependencies · 6199637e
      Frank Benkstein authored
      Represent the input file path internally in canonical form.  Otherwise
      multiple `configure_file` calls that share the same input file but specify
      it relative to different directories (e.g. via `../`) result in multiple
      copies of the dependency on the rule to re-run CMake.  This causes the
      Ninja generator to emit duplicate phony build statements for these
      dependencies, which generates an error with `-w dupbuild=err`, which
      will be default in Ninja 1.9.
      
      Also canonicalize the output path for consistency.
      
      Add a test case.
      
      Fixes: #18584
      6199637e
  3. 09 Mar, 2015 1 commit
    • Brad King's avatar
      Tests: Add more signature tests to RunCMake.configure_file test · 024e25e4
      Brad King authored
      Move the test cases from Tests/CMakeTests/ConfigureFileTest.cmake.in
      over to use the RunCMake.configure_file infrastructure.  This does much
      more robust verification of CMake output for each test case, and would
      have caught the regression fixed in our parent commit.
      024e25e4
  4. 27 Jan, 2015 1 commit
    • Brad King's avatar
      configure_file: Test that CMake re-runs on input change or output missing · 7f2dc8dc
      Brad King authored
      With the Makefile generators we expect that touching or modifying the
      input file of a configure_file, or removing its output, will cause CMake
      to re-run on the next build.  Extend the RunCMake.configure_file test
      with a case covering this.  Also check that CMake does not re-run if
      nothing has changed.
      7f2dc8dc
  5. 31 Oct, 2014 1 commit
  6. 17 Mar, 2014 1 commit