1. 03 May, 2018 1 commit
  2. 02 May, 2018 2 commits
  3. 01 May, 2018 6 commits
  4. 30 Apr, 2018 11 commits
  5. 29 Apr, 2018 1 commit
  6. 28 Apr, 2018 1 commit
  7. 27 Apr, 2018 7 commits
  8. 26 Apr, 2018 11 commits
    • Jeremiah van Oosten's avatar
    • Vitaly Stakhovsky's avatar
      4465a278
    • Calum Robinson's avatar
      VS: Don't turn on /DEBUG:FASTLINK for managed C++ targets · 27b28c00
      Calum Robinson authored
      FastLink is only supported for native C++ targets. Turning it off avoids
      a warning when building managed C++.
      27b28c00
    • Brad King's avatar
      Merge topic 'csharp_reference_imported_targets' · e52cf103
      Brad King authored and Kitware Robot's avatar Kitware Robot committed
      de549083 cmVisualStudio10TargetGenerator: warn if /clr flag is set manually
      59ec7d50 cmVisualStudio10TargetGenerator: fix for backward compatibility
      663f5120 cmGlobalVisualStudioGenerator: remove TargetCanBeReferenced()
      359544a9 add tests for using target_link_libraries() with imported managed targets
      43571073 cmVisualStudio10TargetGenerator: store managed reference information in maps
      16fec7e2 cmVisualStudio10TargetGenerator: make some methods config aware
      f3c68288 cmVisualStudio10TargetGenerator: /clr compatible flags for managed tgt
      f9042d80
      
       remove TargetIsCSharpOnly() and use methods from cmGeneratorTarget
      ...
      
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Merge-request: !1805
      e52cf103
    • Brad King's avatar
      Merge branch 'release-3.11' · 6fd60c6e
      Brad King authored
      6fd60c6e
    • Brad King's avatar
      Merge topic 'ninja-issue-17942' · cca8bc88
      Brad King authored and Kitware Robot's avatar Kitware Robot committed
      ee44f390 Ninja: Make assumed source dependencies order-only
      625b8f90 Ninja: Avoid empty phony edges for target ordering
      ae672248 Merge branch 'backport-ninja-issue-17942' into ninja-issue-17942
      0826c201
      
       Ninja: Do not add empty custom command for file(GENERATE) outputs
      
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Merge-request: !2010
      cca8bc88
    • Brad King's avatar
      Merge branch 'backport-ninja-issue-17942' into release-3.11 · a92ee4e3
      Brad King authored
      Merge-request: !2010
      a92ee4e3
    • Brad King's avatar
      Ninja: Make assumed source dependencies order-only · ee44f390
      Brad King authored
      Since its beginning the Ninja generator has handled `GENERATED` source
      files that have no custom command producing them by writing a dummy
      custom command for them that depends on the target ordering phony edge.
      Make the custom command's dependency order-only since the phony edge
      also has only order-only dependencies.  The dummy custom command
      should never be considered "dirty" by `ninja`.
      
      Fixes: #17942
      ee44f390
    • Brad King's avatar
      Ninja: Avoid empty phony edges for target ordering · 625b8f90
      Brad King authored
      Since commit v3.9.0-rc1~230^2~2 (ninja: break unnecessary target
      dependencies, 2017-04-17) we unconditionally generate a phony edge for
      target ordering.  It is needed in case a later target depends on it.
      However, if the phony edge has no inputs then `ninja -d explain` prints:
      
          ninja explain: output ... of phony edge with no inputs doesn't exist
      
      Furthermore the phony edge's output is considered dirty and can cause
      dependents to be incorrectly considered dirty.  Avoid this by always
      generating at least one input to the target ordering phony edges.
      If we have no real dependencies just use a path that always exists.
      
      Fixes: #17942
      625b8f90
    • Brad King's avatar
    • Brad King's avatar
      Ninja: Do not add empty custom command for file(GENERATE) outputs · 0826c201
      Brad King authored
      Internally we mark `file(GENERATE)` outputs as `GENERATED` in order
      to tell custom command dependency tracing logic not to expect the
      files to exist on disk yet.  This is because we do not generate the
      files until after that tracing is done.
      
      The Ninja generator also interprets the `GENERATED` property to mean
      that it is expected that some build rule will generate the file if
      another build rule depends on it.  If the generator does not know of a
      custom command that generates the file then it adds an empty one so that
      the `ninja` build tool does not complain about a dependency on a file
      that does not exist and has no rule to generate it.  However, this step
      is not necessary for `file(GENERATE)` outputs because there is no build
      rule to generate them and they will exist before `ninja` runs.
      
      Add an additional `__CMAKE_GENERATED_BY_CMAKE` property internally to
      tell the Ninja generator that a `GENERATED` file will exist before the
      build starts and is not expected to have a build rule producing it.
      
      Fixes: #17942
      0826c201