1. 13 Aug, 2012 20 commits
  2. 12 Aug, 2012 1 commit
  3. 11 Aug, 2012 1 commit
  4. 10 Aug, 2012 2 commits
  5. 09 Aug, 2012 4 commits
  6. 08 Aug, 2012 1 commit
  7. 07 Aug, 2012 2 commits
  8. 06 Aug, 2012 1 commit
  9. 05 Aug, 2012 1 commit
  10. 04 Aug, 2012 2 commits
  11. 03 Aug, 2012 3 commits
    • Zack Galbreath's avatar
    • Brad King's avatar
      Xcode: Fix object library references in multi-project trees (#13452) · b237dbd8
      Brad King authored
      In cmGlobalXCodeGenerator::Generate we generate a .xcodeproj for each
      directory in the tree containing a project() command.  First we
      iteratively use SetGenerationRoot to add "ALL_BUILD" and other targets
      to each project.  This leaves "CurrentProject" set to the last project
      when we invoke cmGlobalGenerator::Generate, which is not the same as the
      top-level project if any subdirectories invoke the project() command.
      When cmGlobalGenerator::Generate reaches CreateGeneratorTargets it
      constructs cmGeneratorTarget and calls ComputeTargetObjects exactly once
      per target.  In this context the value of CurrentProject is undefined so
      we cannot pass it to GetObjectsNormalDirectory.  Use "$(PROJECT_NAME)"
      instead so it will adapt automatically to each project.
      Also teach Tests/ObjectLibrary to cover this case.
    • Kitware Robot's avatar
      CMake Nightly Date Stamp · 896524e1
      Kitware Robot authored
  12. 02 Aug, 2012 2 commits
    • Brad King's avatar
      Prefer generic system compilers by default for C, C++, and Fortran · 7e58e5bb
      Brad King authored
      Teach CMake to prefer the system default compiler automatically when no
      compiler is specified.  By default use "cc" for C, "CC" for C++, and
      "f95" for Fortran.  Load a new Platform/<os>-<lang>.cmake module to
      allow each platform to specify for each language its system compiler
      name(s) and/or exclude certain names.
      Create Platform/(CYGWIN|Darwin|Linux|Windows)-CXX.cmake modules to
      specify "c++" as the system C++ compiler name for these platforms.  On
      systems that use case-insensitive filesystems exclude C++ compiler names
      that are distinguished from C compiler names only by case.
      This will change the default compiler selection for existing build
      scripts that do not specify a compiler when run on machines with
      separate system and GNU compilers both installed in the PATH.  We do not
      make this change in default behavior lightly.  However:
      (1) If a given build really needs specific compilers one should specify
          them explicitly e.g. by setting CC, CXX, and FC in the environment.
      (2) The motivating case is to prefer the system Clang on newer OS X
          systems over the older GNU compilers typically also installed.  On
          such systems the names "cc" and "c++" link to Clang.  This is the
          first platform known to CMake on which "c++" is not a GNU compiler.
          The old behavior selected "gcc" for C and "c++" C++ and therefore
          chooses GNU for C and Clang for C++ by default.  The new behavior
          selects GNU or Clang consistently for both languages on older or
          newer OS X systems, respectively.
      (3) Other than the motivating OS X case the conditions under which the
          behavior changes do not tend to exist in default OS installations.
          They typically occur only on non-GNU systems with manually-installed
          GNU compilers.
      (4) The consequences of the new behavior are not dire.  At worst the
          project fails to compile with the system compiler when it previously
          worked with the non-system GNU compiler.  Such failure is easy to
          work around (see #1).
      In short this change creates a more sensible default behavior everywhere
      and fixes poor default behavior on a widely-used platform at the cost of
      a modest change in behavior in less-common conditions.
    • Brad King's avatar
      Factor common code out of CMakeDetermine(ASM|C|CXX|Fortran)Compiler · 796e3373
      Brad King authored
      The compiler candidate list selection and search code for C, C++, ASM,
      and Fortran languages was duplicated across four modules.  To look for
      compilers adjacent to already-enabled languages the C and CXX modules
      each used _CMAKE_USER_(C|CXX)_COMPILER_PATH and the ASM module used
      _CMAKE_TOOLCHAIN_LOCATION.  Since commit 4debb7ac (Bias Fortran compiler
      search with C/C++ compilers, 2009-09-09) CMake prefers Fortran compilers
      matching the vendor and directory of an enabled C or C++ compiler.
      Factor out the common functionality among the four languages into a new
      CMakeDetermineCompiler module.  Generalize the Fortran implementation so
      that all languages may each use the vendor and directory of the other
      languages that have already been enabled.  For now do not list any
      vendor-specific names for C, C++, or ASM so that only the directory
      preference is used for these languages (existing behavior).