- Aug 24, 2012
-
-
Brad King authored
At the top of a build tree we configure inside the CMakeFiles directory files such as "CMakeSystem.cmake" and "CMake<lang>Compiler.cmake" to save information detected about the system and compilers in use. The method of detection and the exact results store varies across CMake versions as things improve. This leads to problems when loading files configured by a different version of CMake. Previously we ignored such existing files only if the major.minor part of the CMake version component changed, and depended on the CMakeCache.txt to tell us the last version of CMake that wrote the files. This led to problems if the user deletes the CMakeCache.txt or we add required information to the files in a patch-level release of CMake (still a "feature point" release by modern CMake versioning convention). Ensure that we always have version-consistent platform information files by storing them in a subdirectory named with the CMake version. Every version of CMake will do its own system and compiler identification checks even when a build tree has already been configured by another version of CMake. Stored results will not clobber those from other versions of CMake which may be run again on the same tree in the future. Loaded results will match what the system and language modules expect. Rename the undocumented variable CMAKE_PLATFORM_ROOT_BIN to CMAKE_PLATFORM_INFO_DIR to clarify its purpose. The new variable points at the version-specific directory while the old variable did not.
-
- Aug 22, 2012
-
-
Brad King authored
When a language is not enabled at the top level of a project but is enabled in multiple disjoint subdirectories we should re-use the CMake<lang>Compiler.cmake file from the first directory. Load the file whenever it exists and is not left from a different version of CMake.
-
Brad King authored
Configure a hand-generated Visual Studio project to build the compiler id source file since we cannot run the compiler command-line tool directly. Add a post-build command to print out the full path to the compiler tool. Parse the full path to the compiler tool from the build output.
-
Brad King authored
When the VS 10 generator selects a non-default PlatformToolset to specify for MSBuild, report the selected name in this variable.
-
Brad King authored
Configure a hand-generated Xcode project to build the compiler id source file since we cannot run the compiler command-line tool directly. Add a post-build shell script phase to print out the compiler toolset build setting. Run xcodebuild to compile the identification binary. Parse the full path to the compiler tool from the xcodebuild output.
-
Brad King authored
Teach CMAKE_DETERMINE_COMPILER_ID to check for variable CMAKE_${lang}_COMPILER_ID_TOOL after CMAKE_DETERMINE_COMPILER_ID_BUILD to use as CMAKE_${lang}_COMPILER since it will not be known until after the IDE runs. In CMAKE_DETERMINE_COMPILER_ID_BUILD prepare a cascading "if" so we can use a generator-specific method to compile the identification source file. Leave "if(0)" as a placeholder for now and put the direct compiler invocation in "else()". After running the compiler to build the compiler identification source we file(GLOB) the list of output files as candidates for extracting the compiler information. An IDE may create directories, so exclude exclude directories from this list. -
Brad King authored
Re-organize CMakeDetermine(C|CXX|Fortran)Compiler.cmake to search for the compiler command-line tool only under generators for which it makes sense. For the Visual Studio generators we do not expect to find the compiler tool from the environment, nor would we use the result anyway. Furthermore, set CMAKE_${lang}_COMPILER_ID_TEST_FLAGS only when it has a chance to be used. Extract _CMAKE_TOOLCHAIN_LOCATION from the compiler path after running the compiler id step so in the future that step can help find the path to the compiler. -
Move adding of definitions into cmGlobalVisualStudioGenerator to share code and avoid duplicate architecture string literals.
-
- Aug 15, 2012
-
-
Kitware Robot authored
-
- Aug 14, 2012
-
-
68bc863d Merge branch 'master' into cleanup-style a05eba57 CMakeVersion.bash: Update sed expression for lower-case 'set' 3c0488d7 Fix WarnUnusedUnusedViaUnset test pass/fail regex 6c2c483e Remove trailing TAB from NSIS.template.in 9db31162 Remove CMake-language block-end command arguments 77543bde Convert CMake-language commands to lower case 7bbaa428 Remove trailing whitespace from most CMake and C/C++ code be9db989 Merge topic 'watcom-compiler-version' af42ae4f Watcom: Simplify compiler version detection (#11866)
-
Brad King authored
Conflicts: Source/CMakeVersion.cmake
-
-
Brad King authored
After conversion of Modules .cmake files to lower case the FAIL_REGULAR_EXPRESSION for this test matched warnings in modules other than the test line itself. Make the pass and fail regular expressions specific to the file containing the lines they are testing.
-
-
Kitware Robot authored
-
- Aug 13, 2012
-
-
Ancient versions of CMake required else(), endif(), and similar block termination commands to have arguments matching the command starting the block. This is no longer the preferred style. Run the following shell code: for c in else endif endforeach endfunction endmacro endwhile; do echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | egrep -z -v 'Tests/CMakeTests/While-Endwhile-' | xargs -0 sed -i -f convert.sed && rm convert.sed -
Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed -
Our Git commit hooks disallow modification or addition of lines with trailing whitespace. Wipe out all remnants of trailing whitespace everywhere except third-party code. Run the following shell code: git ls-files -z -- \ bootstrap doxygen.config '*.readme' \ '*.c' '*.cmake' '*.cpp' '*.cxx' \ '*.el' '*.f' '*.f90' '*.h' '*.in' '*.in.l' '*.java' \ '*.mm' '*.pike' '*.py' '*.txt' '*.vim' | egrep -z -v '^(Utilities/cm|Source/(kwsys|CursesDialog/form)/)' | egrep -z -v '^(Modules/CPack\..*\.in)' | xargs -0 sed -i 's/ \+$//'
-
-
e88bae77 Xcode: Run xcode-select to find Xcode version file (#13463)
-
822c1eaf Do not include directories which are part of the package install prefix.
-
67f11cf1 FindSelfPackers: fix typo (#13456)
-
76d6c593 Clean up documentation formatting so that it is rendered properly in HTML.
-
b237dbd8 Xcode: Fix object library references in multi-project trees (#13452)
-
-
6c8722fa Fix typo direcotry -> directory (and similar) [#13444]
-
5797512c SelectLibraryConfiguration: generate correct output when input vars are lists
-
-
4ea5dc5b Eclipse: fix #13358: don't create bad linked resources
-
-
af80da34 remove lib64 Unix paths if the respective lib path is also given 733726ed find_library: Fix mixed lib->lib64 (non-)conversion cases (#13419) 54add62f find_library: Simplify lib->lib<arch> expansion 6ca2f82d find_library: Refactor lib->lib64 conversion 1fe4b82a find_library: Add test covering lib->lib64 cases
-
4ddd3b9f Use OUTPUT_NORMAL instead of OUTPUT_MERGE for cmake -E chdir.
-
214589b1 Add ability to run as a ctest -S script also
-
3a17311b Release: Temporarily exclude ExternalProject test on cygwin
-
Brad King authored
Since commit c198730b (Detect Watcom compiler version with its id, 2011-12-07) the CMAKE_(C|CXX)_COMPILER_VERSION variables are set for the Watcom compiler. Use these in Windows-wcl386.cmake to set the old WATCOM1* version variables. This avoids using the old EXECUTE_PROCESS command which failed due to extra quotes anyway.
-
Kitware Robot authored
-
- Aug 12, 2012
-
-
Kitware Robot authored
-
- Aug 11, 2012
-
-
Kitware Robot authored
-
- Aug 10, 2012
-
-
Brad King authored
Multiple versions of Xcode may be installed in different locations. Run "xcode-select --print-path" to detect the active Xcode location and parse its Contents/version.plist file. Note that the Xcode.app directory name may vary in developer versions.
-
Kitware Robot authored
-
