1. 10 Sep, 2009 2 commits
  2. 09 Sep, 2009 3 commits
    • Brad King's avatar
      Enable C and C++ first in Fortran test · 14b12d03
      Brad King authored
      CMake now looks for a Fortran compiler matching any C or C++ compiler
      already enabled.  We test this by enabling C and C++ first in the
      Fortran test, which is what user projects will likely do.
    • Brad King's avatar
      Bias Fortran compiler search with C/C++ compilers · 4debb7ac
      Brad King authored
      When CMAKE_Fortran_COMPILER and ENV{FC} are not defined CMake searches
      for an available Fortran compiler.  This commit teaches the search code
      to look for compiler executables next to the C and C++ compilers if they
      are already found.  Furthermore, we bias the compiler executable name
      preference order based on the vendor of the C and C++ compilers, which
      increases the chance of finding a compatible compiler by default.
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · 4678c619
      Kitware Robot authored
  3. 08 Sep, 2009 10 commits
  4. 07 Sep, 2009 5 commits
    • Zach's avatar
      ENH: Added ctest test options PROCESSORS and RUN_SERIAL. These allow... · 5fb958fd
      Zach authored
      ENH: Added ctest test options PROCESSORS and RUN_SERIAL.  These allow specification of resource allocation for given tests running with the ctest -j N option.  RUN_SERIAL ensures that a given test does not run in parallel with any other test.  Also forced appending of "..." to the longest test name in ctest.
    • Brad King's avatar
      Put custom commands in topological order for VS 10 · 4e16813f
      Brad King authored
      Visual Studio 10 uses MSBuild to drive the build.  Custom commands
      appear in MSBuild files inside CustomBuild elements, which appear inside
      ItemGroup elements.  The Outputs and AdditionalInputs elements of each
      CustomBuild element are evaluated according to timestamps on disk.
      MSBuild does not use inputs/outputs to order CustomBuild steps within a
      single ItemGroup or across multiple ItemGroup elements.  Instead we must
      put only unrelated CustomBuild elements in a single ItemGroup and order
      the item groups from top to bottom using a topological order of the
      custom command dependency graph.
      This fixes CustomCommand and ExternalProject test failures, so we remove
      the expectation of these failures.
    • Brad King's avatar
      Save source dependencies from custom command trace · 4224513c
      Brad King authored
      In each target we trace dependencies among custom commands to pull in
      all source files and build rules necessary to complete the target.  This
      commit teaches cmTarget to save the inter-source dependencies found
      during its analysis.  Later this can be used by generators that need to
      topologically order custom command rules.
    • Brad King's avatar
      Do Windows command line escapes for VS 10 too · 355511ad
      Brad King authored
      Until now the VS 10 generator did no Windows command-line escaping and
      just did XML escapes.  This commit teaches the generator to use the same
      command-line escape addition code used by other generators.  The script
      construction method cmLocalVisualStudioGenerator::ConstructScript need
      not do XML escapes.  Each VS generator version adds the XML escapes
      necessary for that version.
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · f143dc2a
      Kitware Robot authored
  5. 06 Sep, 2009 5 commits
  6. 05 Sep, 2009 1 commit
  7. 04 Sep, 2009 14 commits