Skip to content
Snippets Groups Projects
  1. Jul 02, 2013
  2. Jun 28, 2013
    • Brad King's avatar
      FindBoost: Add -vc120 mangling for VS 12 · 78fdbbcb
      Brad King authored
      78fdbbcb
    • Brad King's avatar
      VS12: Generate flag tables from MSBuild v120 tool files · e99d7b1c
      Brad King authored
      Run cmparseMSBuildXML.py on cl.xml, lib.xml, and link.xml to generate
      our flag tables:
      
       python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/v120/1033/cl.xml" > cmVS12CLFlagTable.h
       python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/v120/1033/lib.xml" > cmVS12LibFlagTable.h
       python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/v120/1033/link.xml" > cmVS12LinkFlagTable.h
      
      Fix up the declaration names at the top of each file.  Finally, teach
      cmVisualStudio10TargetGenerator to select the version of the table
      matching the version of VS.
      e99d7b1c
    • Brad King's avatar
      VS12: Add Visual Studio 12 generator (#14251) · 77ac9b8b
      Brad King authored
      
      Copy cmGlobalVisualStudio11Generator to cmGlobalVisualStudio12Generator
      and update version numbers accordingly.  Add the VS12 enumeration value.
      Add module CMakeVS12FindMake to find MSBuild.  Look for MSBuild in its
      now-dedicated Windows Registry entry.  Teach the platform module
      Windows-MSVC to set MSVC12 and document the variable.  Teach module
      InstallRequiredSystemLibraries to look for the VS 12 runtime libraries.
      
      Teach tests CheckCompilerRelatedVariables, Preprocess, VSExternalInclude,
      and RunCMake.GeneratorToolset to treat VS 12 as they do VS 10 and 11.
      
      Inspired-by: default avatarMinmin Gong <minmin.gong@gmail.com>
      77ac9b8b
  3. Jun 27, 2013
  4. Jun 14, 2013
  5. Jun 13, 2013
    • Brad King's avatar
      cmCryptoHash: Increase alignment of HashFile buffer · 75994d95
      Brad King authored
      The SHA512_Update implementation accesses input data via 64-bit
      integers.  This requires alignment of the input buffer on some
      architectures.  Align our stack-allocated buffer for file content to
      satisfy this requirement.
      75994d95
  6. Jun 05, 2013
  7. Jun 04, 2013
    • Brad King's avatar
      Xcode: Fix framework search paths in STATIC library targets (#14191) · 21a0beac
      Brad King authored
      In commit 2bc22bda (Xcode: Add frameworks search paths from link
      dependeny closure, 2012-12-07) we made framework search paths from the
      link closure conditional on target type, skipping it on STATIC and
      OBJECT library targets that do not actually link.  However, the
      framework search paths also influence the compile lines (-F options) so
      we need them for all target types.  The Makefile generator already does
      this, as did the Xcode generator prior to the above-mentioned commit.
      21a0beac
  8. Jun 03, 2013
  9. May 31, 2013
  10. May 30, 2013
    • Brad King's avatar
      FindBoost: Fix handling of \ in input paths (#14179) · 363825cd
      Brad King authored
      In commit 5b9149e0 (FindBoost: Overhaul caching and search repeat
      behavior, 2012-09-24) we refactored the internal library search to use a
      _Boost_FIND_LIBRARY macro to wrap around find_library calls.  However,
      CMake macros re-process escape sequences when evaluating calls inside
      the macro after substituting placeholders (a historical bug).  In order
      to avoid escape sequences, convert backslashes to forward slashes before
      passing arguments to the _Boost_FIND_LIBRARY macro.
      363825cd
    • Stephen Kelly's avatar
    • Stephen Kelly's avatar
      GenexEval: Fix evaluation of INCLUDE_DIRECTORIES target property. · 3aa9ce44
      Stephen Kelly authored
      This property should come from the content of the property itself,
      plus the INTERFACE_INCLUDE_DIRECTORIES of the link *implementation*.
      
      In contrast, when the INTERFACE_INCLUDE_DIRECTORIES is evaluated for
      a target, the INTERFACE_INCLUDE_DIRECTORIES of the link *interface*
      is used.
      
      Similar logic applies for the COMPILE_DEFINITIONS target properties.
      
      If the propertyName is already an INTERFACE_ variant of the property,
      ie, the expression is similar to
      
       $<TARGET_PROPERTY:foo,INTERFACE_INCLUDE_DIRECTORIES>
      
      then the INTERFACE_INCLUDE_DIRECTORIES of the link *interface* of foo
      is used.
      
      However, if the propertyName is not an INTERFACE_ variant, and the
      interfacePropertyName is, ie, the expression is similar to:
      
       $<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>
      
      then the INTERFACE_INCLUDE_DIRECTORIES of the link *implementation*
      of foo is used.
      3aa9ce44
    • Stephen Kelly's avatar
      GenexEval: Extract a getLinkedTargetsContent from TargetPropertyNode. · 0b39fefe
      Stephen Kelly authored
      This will be used to process transitive components of properties
      which depend on linked targets. Currently only the link interface
      of the target can be used as the source of the linked targets, but
      in the next commit it will be possible to use the link implementation
      as the source of link targets.
      
      This commit does not change the semantics of the code.
      0b39fefe
    • Stephen Kelly's avatar
    • Stephen Kelly's avatar
      try_compile: Trim whitespace from LINK_LIBRARIES entries · e5375442
      Stephen Kelly authored
      Commit e65ef08b (try_compile: Fix quoting of libraries in generated
      CMakeLists.txt, 2013-05-24) added quoting to entries specified in
      the LINK_LIBRARIES. However, if the input entries contain whitespace
      padding, that quoted whitespace causes an error in the generated
      CMakeLists.txt at target_link_libraries.
      
      Strictly, it is an error to have space separated entries in the
      CMAKE_REQUIRED_LIBRARIES, as it was never properly handled by
      CMakeExpandImportedTargets even prior to commit 236133e7 (Handle
      targets in the LINK_LIBRARIES of try_compile., 2013-02-09). However,
      it is causing a regression in KDE code which tests the next branch.
      e5375442
  11. May 28, 2013
Loading