1. 06 Aug, 2009 1 commit
  2. 05 Aug, 2009 10 commits
    • Brad King's avatar
      Cleanup FortranCInterface for PGI and GCC 4.2 · edcddb52
      Brad King authored
      This documents the purpose of the extra my_module_.c and mymodule.c
      source files, and sorts the symbols.
    • Bill Hoffman's avatar
    • David Cole's avatar
    • David Cole's avatar
      Overhaul GetPrerequisites and BundleUtilities: make fixup_bundle do something... · fe0b121d
      David Cole authored
      Overhaul GetPrerequisites and BundleUtilities: make fixup_bundle do something useful on Windows and Linux.
      Formerly, fixup_bundle was useful only on the Mac for making standalone bundle applications that could be drag-n-drop moved to anyplace in the file system. fixup_bundle is not just for the Mac any more. It will now analyze executable files on Windows and Linux, too, and copy necessary non-system dlls to the same folder that the executable is in. This should work with dlls that you build as part of your build and also with 3rd-party dlls as long as you give fixup_bundle the right list of directories to search for those dlls. Many thanks to Clinton Stimpson for his help in ironing out the details involved in making this work.
    • Brad King's avatar
      Rewrite FortranCInterface module · 80f0201b
      Brad King authored
      This is a new FortranCInterface.cmake module to replace the previous
      prototype.  All module support files lie in a FortranCInterface
      directory next to it.
      This module uses a new approach to detect Fortran symbol mangling.  We
      build a single test project which defines symbols in a Fortran library
      (one per object-file) and calls them from a Fortran executable.  The
      executable links to a C library which defines symbols encoding all known
      manglings (one per object-file).  The C library falls back to the
      Fortran library for symbols it cannot provide.  Therefore the executable
      will always link, but prefers the C-implemented symbols when they match.
      These symbols store string literals of the form INFO:symbol[<name>] so
      we can parse them out of the executable.
      This module also provides a simpler interface.  It always detects the
      mangling as soon as it is included.  A single macro is provided to
      generate mangling macros and optionally pre-mangled symbols.
    • Bill Hoffman's avatar
      Allow for static libraries to depend on other targets so that the MSBuild runs... · 7b36fd63
      Bill Hoffman authored
      Allow for static libraries to depend on other targets so that the MSBuild runs build things in the correct order
    • Brad King's avatar
      Remove WXDialog source code · 87442aef
      Brad King authored
      The QtDialog is our supported cross-platform GUI, so the WXDialog source
      is no longer needed.
    • Brad King's avatar
      Remove FLTKDialog source code · 32869ea3
      Brad King authored
      The QtDialog is our supported cross-platform GUI, so the FLTKDialog
      source is no longer needed.
    • Brad King's avatar
      Fix find_package for cmake-gui registry entry · be24db77
      Brad King authored
      The find_package commands looks at the "WhereBuild" registry entries
      created by CMakeSetup and cmake-gui hoping that the project was recently
      built.  CMakeSetup created WhereBuild1..WhereBuild10 but cmake-gui
      creates WhereBuild0-WhereBuild9.
      This fixes find_package to look at WhereBuild0 so that the most recently
      configured project can be found.  It is important in the case that the
      package to be found was the last one configured in cmake-gui but the
      current project that is finding it is configured from the command line.
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · b592154b
      Kitware Robot authored
  3. 04 Aug, 2009 5 commits
    • Ken Martin's avatar
      ENH: minor cleanup of test · 410b8eba
      Ken Martin authored
    • Brad King's avatar
      No /fast targets in try_compile project mode · 80c947b3
      Brad King authored
      The try_compile command builds the cmTryCompileExec executable using the
      cmTryCompileExec/fast target with Makefile generators in order to save
      time since dependencies are not needed.  However, in project mode the
      command builds an entire source tree that may have dependencies.
      Therefore we can use the /fast target approach only in one-source mode.
    • Brad King's avatar
      Test C, C++, Fortran interface combinations · f3cd1e06
      Brad King authored
      Previously the Fortran test created a single executable containing C,
      C++, and Fortran sources.  This commit divides the executable into three
      libraries corresponding to each language, and two executables testing
      Fortran/C only and Fortran/C/C++ together.  The result tests more
      combinations of using the languages together, and that language
      requirements propagate through linking.
    • Ken Martin's avatar
      ENH: change to CDASH · 39e0e044
      Ken Martin authored
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · 346a5b2d
      Kitware Robot authored
  4. 03 Aug, 2009 3 commits
    • Brad King's avatar
      Fix recursive try_compile calls · 73de2362
      Brad King authored
      When building an entire source tree with try_compile instead of just a
      single source file, it is possible that the CMakeLists.txt file in the
      try-compiled project invokes try_compile.  This commit fixes propagation
      of language-initialization results from the outer-most project into any
      number of try-compile levels.
    • Brad King's avatar
      Test try_compile project mode · 1a159bbf
      Brad King authored
      The try_compile command project mode builds an entire source tree
      instead of one source file.  It uses an existing CMakeLists.txt file in
      the given source tree instead of generating one.  This commit creates a
      test for the mode in the TryCompile test.
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · 8049b503
      Kitware Robot authored
  5. 02 Aug, 2009 1 commit
  6. 01 Aug, 2009 1 commit
  7. 31 Jul, 2009 5 commits
    • Alexander Neundorf's avatar
      DOCS: fix typo (#9231) · e5dd49c5
      Alexander Neundorf authored
    • Brad King's avatar
      Set current directory variables in CTest scripts · a48f29c9
      Brad King authored
      The commit "Fix get_filename_component ABSOLUTE mode" broke the code
        get_filename_component(cwd . ABSOLUTE)
      because CTest scripts did not make cmMakefile::GetCurrentDirectory()
      available.  This commit fixes the problem by setting the proper
      information on CTest script instances of cmMakefile.
      available to CTest scripts.  They are set to the working directory at
      script startup.
    • Brad King's avatar
      Fix installation when built by CMake 2.4 · 36bb6249
      Brad King authored
      CMake 2.4 generates old-style cmake_install.cmake code including calls
      to the file(INSTALL) command with the COMPONENTS argument.  We need to
      set CMAKE_INSTALL_SELF_2_4 for the whole install tree to prevent the
      command from complaining in this special case.  Previously this was
      needed only in the QtDialog directory, but now it is needed in the
      entire tree.
    • Alexander Neundorf's avatar
      DOCS: fix typo (see #9308) · 121df27f
      Alexander Neundorf authored
    • Kitware Robot's avatar
      KWSys Nightly Date Stamp · 8783f8d0
      Kitware Robot authored
  8. 30 Jul, 2009 4 commits
    • Brad King's avatar
      Pass Fortran90 test result to try-compile · 68434483
      Brad King authored
      This stores CMAKE_Fortran_COMPILER_SUPPORTS_F90 in the Fortran compiler
      information file CMakeFiles/CMakeFortranCompiler.cmake instead of in
      CMakeCache.txt.  This file makes the result available to try-compile
    • Brad King's avatar
      Do not always propagate linker language preference · fcab87c9
      Brad King authored
      The commit "Consider link dependencies for link language" taught CMake
      to propagate linker language preference from languages compiled into
      libraries linked by a target.  It turns out this should only be done for
      some languages, such as C++, because normally the language of the
      program entry point (main) should be used.
      We introduce variable CMAKE_<LANG>_LINKER_PREFERENCE_PROPAGATES to tell
      CMake whether a language should propagate its linker preference across
      targets.  Currently it is true only for C++.
    • Brad King's avatar
      Refactor target linker language selection · fd633b33
      Brad King authored
      This factors the decision logic out of cmTarget::ComputeLinkClosure into
      dedicated class cmTargetSelectLinker.  We replace several local
      variables with a single object instance, and organize code into methods.
    • Kitware Robot's avatar
      STYLE: Nightly Date Stamp · ace4d5d3
      Kitware Robot authored
  9. 29 Jul, 2009 10 commits