1. 29 Nov, 2014 2 commits
    • Stephen Kelly's avatar
      Export: Disallow export of targets with INTERFACE_SOURCES · e1348056
      Stephen Kelly authored
      This can be allowed in the next release, but it needs to have some
      features present and tested such as
      
      * Ensuring that relative paths do not appear in the generated property.
      * Ensuring that paths to the source or build directories do not appear.
      * Generating a check in the file for CMake 3.1 or later so that the
          resulting property will be consumed.
      * Ensuring that any referenced targets are part of an export set and
          generating a check for them.
      * INSTALL_INTERFACE and BUILD_INTERFACE content.
      
      All of these checks are already done for INTERFACE_INCLUDE_DIRECTORIES,
      but it is too late to add them for INTERFACE_SOURCES for CMake 3.1.
      As the checks introduce some new error conditions, it is better to
      disallow exporting fully for this case and introduce proper error
      conditions later instead of policies.
      e1348056
    • Stephen Kelly's avatar
      cmTarget: Don't allow relative paths in INTERFACE_SOURCES · bb5905bb
      Stephen Kelly authored
      Follow the pattern of checks that are made for INTERFACE_INCLUDE_DIRECTORIES.
      Existence is already checked by cmSourceFile::GetFullPath.  Add a check
      to disallow relative paths in source directories. Otherwise code such as
      
       target_sources(lib1 INTERFACE foo.cpp)
      
      would fail if consumed by a target in a different directory.
      
      Unlike the INTERFACE_INCLUDE_DIRECTORIES behavior, we don't care whether
      the entry comes from an IMPORTED target or not.  In the include directories
      case, the directory for a non-imported target might not exist yet but
      might be created.  In the sources case, a file which does not yet
      exist in the filesystem must be explicitly marked with the GENERATED
      property.
      
      Adjust existing tests and add a new test for the error.
      bb5905bb
  2. 26 Nov, 2014 1 commit
  3. 25 Nov, 2014 4 commits
  4. 23 Nov, 2014 1 commit
  5. 20 Nov, 2014 5 commits
  6. 19 Nov, 2014 4 commits
  7. 18 Nov, 2014 2 commits
  8. 17 Nov, 2014 8 commits
  9. 14 Nov, 2014 3 commits
  10. 13 Nov, 2014 7 commits
  11. 12 Nov, 2014 3 commits
    • Stephen Kelly's avatar
      Features: Don't record for AppleClang · ded30405
      Stephen Kelly authored
      Features are currently recorded accidentally for all versions of
      AppleClang > 3.4 (I have no idea how that relates to upstream
      Clang). Presumably that version has the features which are
      accidentally recorded, but in the future features will be
      recorded initially for only AppleClang >= 5.1, which would
      appear as a feature regression.
      
      Commit v3.1.0-rc1~635^2~11 (Don't load Clang-CXX from
      AppleClang-CXX., 2013-11-11) ajusted the logic for the CXX
      language.  Make a similar change for the C language.
      ded30405
    • Brad King's avatar
      CMake 3.1.0-rc2 · 433c6d46
      Brad King authored
      433c6d46
    • Brad King's avatar
      5d1fe90e