1. 13 May, 2012 1 commit
  2. 03 May, 2012 2 commits
  3. 30 Apr, 2012 2 commits
    • Modestas Vainius's avatar
      Support building shared libraries or modules without soname (#13155) · e1409ac5
      Modestas Vainius authored
      Add a boolean target property NO_SONAME which may be used to disable
      soname for the specified shared library or module even if the platform
      supports it.  This property should be useful for private shared
      libraries or various plugins which live in private directories and have
      not been designed to be found or loaded globally.
      
      Replace references to <CMAKE_SHARED_LIBRARY_SONAME_${LANG}_FLAG> and
      hard-coded -install_name flags with a conditional <SONAME_FLAG> which is
      expanded to the value of the CMAKE_SHARED_LIBRARY_SONAME_${LANG}_FLAG
      definition as long as soname supports is enabled for the target in
      question.  Keep expanding CMAKE_SHARED_LIBRARY_SONAME_${LANG}_FLAG in
      rules in case third party projects still use it.  Such projects would
      not yet use NO_SONAME so the adjacent <TARGET_SONAME> will always be
      expanded.  Make <TARGET_INSTALLNAME_DIR> NO_SONAME aware as well.  Since
      -install_name is soname on OS X, this should not be a problem if this
      variable is expanded only if soname is enabled.
      
      The Ninja generator performs rule variable substitution only once
      globally per rule to put its own placeholders.  Final substitution is
      performed by ninja at build time.  Therefore we cannot conditionally
      replace the soname placeholders on a per-target basis.  Rather than
      omitting $SONAME from rules.ninja, simply do not write its contents for
      targets which have NO_SONAME.  Since 3 variables are affected by
      NO_SONAME ($SONAME, $SONAME_FLAG, $INSTALLNAME_DIR), set them only if
      soname is enabled.
      e1409ac5
    • Brad King's avatar
  4. 28 Apr, 2012 2 commits
  5. 26 Apr, 2012 1 commit
  6. 25 Apr, 2012 1 commit
    • David Cole's avatar
      ExternalProject: Avoid unnecessary git clones (#12564) · 987c017f
      David Cole authored
      In the case of git, only track the repository in the
      repository info dependency tracking file. Not the tag.
      
      The download step should only re-run if the repository changes.
      The download step should NOT re-run if the tag changes.
      
      The update step is an 'always' re-running step, and so should
      already re-run, unless it's been eliminated by use of
      
        UPDATE_COMMAND ""
      987c017f
  7. 24 Apr, 2012 1 commit
    • Brad King's avatar
      Intel: On Windows use /EHsc instead of deprecated /GX (#13163) · 4f80896e
      Brad King authored
      Use of the deprecated option with Intel 2011 produces
      
       icl: command line remark #10010: option '/GX' is deprecated and will
       be removed in a future release. See '/help deprecated'
      
      so use its replacement option which has been supported for several
      older versions anyway.
      4f80896e
  8. 22 Apr, 2012 2 commits
    • Patrick Gansterer's avatar
      Added CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL · fe58b67e
      Patrick Gansterer authored
      If CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL is set to ON the NSIS installer will look for a previous installed version and ask the user about uninstall.
      fe58b67e
    • David Cole's avatar
      ExternalProject: Add missing COMMAND keyword · 64818c10
      David Cole authored
      Commit f67139ae added running a verify script in between running
      the download and extract scripts. Since then, it has always been
      missing the COMMAND keyword added in this commit.
      
      It worked anyway (semi-accidentally) by running a command line like:
      
        cmake -P script1.cmake cmake -P script2.cmake
      
      CMake, when running -P scripts on the command line, runs them in order,
      and apparently ignores spurious arguments in between (the middle "cmake"
      in the above example) and so, all appeared to work as intended.
      
      This commit adds the missing keyword and the commands that run are
      now two separate sequential cmake invocations like:
      
        cmake -P script1.cmake
        cmake -P script2.cmake
      
      ...which was the original intent of commit f67139ae
      64818c10
  9. 21 Apr, 2012 1 commit
    • David Cole's avatar
      CPack/NSIS: Add CPACK_NSIS_EXTRA_PREINSTALL_COMMANDS (#13085) · aa8acea3
      David Cole authored
      Allows custom NSIS commands to run prior to any installation
      actions. Projects that need to run an uninstaller first,
      especially one from a non-NSIS previous revision of a project
      that is NOW using CPack and NSIS, may do so by putting custom
      NSIS commands into this variable.
      
      Inspired-by: David Golub
      aa8acea3
  10. 20 Apr, 2012 1 commit
  11. 16 Apr, 2012 1 commit
    • Rolf Eike Beer's avatar
      UseJava: fix typo in variable name (#13135) · 8bdd4495
      Rolf Eike Beer authored
      As Dave Abrahams pointed out CMAKE_CURRENT_SOURCE_PATH is wrong, it's of
      course CMAKE_CURRENT_SOURCE_DIR.
      
      Also wrap the path in quotes so the example would even work if the source path
      has spaces.
      8bdd4495
  12. 15 Apr, 2012 1 commit
  13. 09 Apr, 2012 1 commit
    • Brad King's avatar
      CheckIncludeFiles: Shorten check description message · 5adb6b7a
      Brad King authored
      Since commit 44d007b6 (CheckIncludeFiles: fix status output, 2012-02-01)
      check_include_files reports the list of files tested instead of the name
      of the variable storing the result.  Some projects incrementally test
      and concatenate very long lists leading to long messages that do not
      provide much information.  Users report confusion especially when the
      lines wrap.
      
      For lists of more than two files produce messages of the format
      
       Looing for N include files first.h, ..., last.h
      
      where N is the list length and "..." is literal.  Leave the log file
      entries and cache entry description unchanged as they should have the
      full detail of the check performed.
      5adb6b7a
  14. 07 Apr, 2012 1 commit
  15. 06 Apr, 2012 2 commits
  16. 05 Apr, 2012 1 commit
  17. 29 Mar, 2012 1 commit
  18. 27 Mar, 2012 4 commits
    • Ben Boeckel's avatar
      Search for other ABIFLAGS builds of Python · 4bdec581
      Ben Boeckel authored
      Starting with Python3, standard Python installs may have additional ABI
      flags attached to include directories and library names. As of 3.2, the
      following flags are in the configure file:
      
          d -> --with-debug
          m -> --with-pymalloc
          u -> --with-wide-unicode
      
      Python 3.3 seems to no longer have --with-wide-unicode. Hopefully Python
      will ensure that the possible flags always show up in a stable order.
      The 'd' flag is ignored since the debug library is considered separate.
      
      There is still the problem where ABI flags cannot be specified in
      find_package since the letters confuse the version comparator.
      4bdec581
    • Ben Boeckel's avatar
      Don't put legacy variables back into the cache · 6a46f5ce
      Ben Boeckel authored
      If PYTHON_INCLUDE_PATH is put into the cache, then it will always
      override whatever might be found and PYTHON_INCLUDE_DIR is never given a
      chance to find something different. It being marked as INTERNAL also
      means that it cannot be changed without editing CMakeCache.txt directly.
      
      Basically, the scenario is that if the Python version is changed, then
      deleting PYTHON_INCLUDE_DIR doesn't work because any cached
      PYTHON_INCLUDE_PATH variable is set before find_path is even called. Any
      build tree using a previous version will still need either manual
      removal of PYTHON_INCLUDE_PATH or a complete reconfigure, but in the
      future changing the Python version can be accomplished by deleting
      PYTHON_INCLUDE_DIR and reconfiguring with the new version.
      6a46f5ce
    • Tom Hughes's avatar
      Override topdir from rpm command line seems necessary on Amazon linux. · 3a0c60d3
      Tom Hughes authored
      
      
      This modification should be harmless on other distro.
      Signed-off-by: Eric Noulard's avatarEric NOULARD <eric.noulard@gmail.com>
      3a0c60d3
    • Eric Noulard's avatar
      8fe0da59
  19. 26 Mar, 2012 2 commits
  20. 25 Mar, 2012 1 commit
  21. 20 Mar, 2012 3 commits
  22. 19 Mar, 2012 4 commits
  23. 10 Mar, 2012 2 commits
  24. 08 Mar, 2012 1 commit
    • David Cole's avatar
      Xcode: Detect new default locations of Xcode 4.3 bits and pieces (#12621) · 4693cf84
      David Cole authored
      Xcode 4.3 installs into "/Applications" by default, from the Mac App Store.
      
      Also, the paths to the available SDKs changed: they are now within the
      Xcode.app bundle.
      
      PackageMaker is installed as a separate program, and may be installed
      anywhere. It is not installed with Xcode 4.3 by default anymore.
      Download the "Auxiliary Tools for Xcode" to get PackageMaker.
      Put PackageMaker inside the Xcode.app bundle, in its nested Applications
      folder, or put it alongside Xcode in "/Applications" and CMake will find
      it.
      
      Update references to "find" paths: add new possible locations for finding
      Xcode.app and PackageMaker.app. Prefer the most recent version's locations
      first, but keep the old locations as fallback search paths, too.
      
      Thanks to all the contributors who provided and tested out various patches
      for fixing this issue. Especially, but by no means limited to:
      Francisco Requena Espí, Jamie Kirkpatrick and drfrogsplat.
      4693cf84
  25. 07 Mar, 2012 1 commit