summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* find_package: Search a "system package registry"Brad King2011-04-132-14/+39
| | | | | | | | Generalize the "user package registry" created by commit ed0650f6 (Teach find_package to search a "package registry", 2009-09-01). Define a corresponding "system" registry key under HKEY_LOCAL_MACHINE. This gives package installers a place to create a registry value that points at the right location for find_package() to locate the package.
* find_package: Document user package registry locationsBrad King2011-04-131-3/+10
| | | | | Specify the Windows registry key under HKEY_CURRENT_USER and directory on UNIX platforms in which the package registry is stored.
* find_package: Cleanup user package registry less aggressivelyBrad King2011-04-131-4/+3
| | | | | | Delete only REG_SZ entries that are specifically detected to point to invalid paths. This will allow future versions to add other value types for different purposes.
* find_package: Rename implementation of user package registryBrad King2011-04-132-7/+7
| | | | | Rename {Registry => UserRegistry} in names associated specifically with the user package registry and not registry access in general.
* KWSys Nightly Date StampKWSys Robot2011-04-131-1/+1
|
* Merge topic 'vs10-custom-working-directory-issue-11938'Brad King2011-04-124-15/+58
|\ | | | | | | | | | | | | 234bae7 VS10: Fix exit code of custom commands with setlocal/endlocal (#11938) b98fdd5 VS: Use setlocal/endlocal only in VS 10 custom commands 06fcbc4 VS10: Fix working directory of consecutive custom commands (#11938)
| * VS10: Fix exit code of custom commands with setlocal/endlocal (#11938)Brad King2011-04-111-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the pattern setlocal ... endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone :cmErrorLevel exit /b %1 :cmDone if %errorlevel% neq 0 goto :VCEnd in custom commands to preserve the %errorlevel% from inside the setlocal/endlocal block.
| * VS: Use setlocal/endlocal only in VS 10 custom commandsBrad King2011-04-113-13/+39
| | | | | | | | | | | | | | The setlocal/endlocal and errorlevel pattern added by commit 06fcbc47 (VS10: Fix working directory of consecutive custom commands, 2011-04-08) does not work well in VS 7.1. Restore the original behavior for VS versions that do not need the new behavior.
| * VS10: Fix working directory of consecutive custom commands (#11938)Brad King2011-04-084-22/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The VS 10 msbuild tool uses a single command shell to invoke all the custom command scripts in a project. Isolate the environment and working directory of custom commands using setlocal/endlocal. The form of each command is set errlev= setlocal cd c:\work\dir if %errorlevel% neq 0 goto :cmEnd c: if %errorlevel% neq 0 goto :cmEnd command1 ... if %errorlevel% neq 0 goto :cmEnd ... commandN ... if %errorlevel% neq 0 goto :cmEnd :cmEnd endlocal & set errlev=%errorlevel% if %errlev% neq 0 goto :VCEnd so that all changes to the environment and working directory are isolated within the script and the return code is preserved.
* | Merge topic 'CPackDeb-fix12061'Brad King2011-04-121-1/+1
|\ \ | | | | | | | | | | | | b22fcfb CPackDeb: Handle dirs for CONTROL_EXTRA correctly when packaging components
| * | CPackDeb: Handle dirs for CONTROL_EXTRA correctly when packaging componentsMartin Konrad2011-04-091-1/+1
| | | | | | | | | | | | | | | | | | Copy the files specified in CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA to the right directory when packaging components. This fixes #12061. Signed-off-by: Eric NOULARD <eric.noulard@gmail.com>
* | | Merge topic 'windows-make-working-drive'Brad King2011-04-121-3/+9
|\ \ \ | | | | | | | | | | | | | | | | | | | | 42a732b Change working drive only in MinGW Makefiles b567613 Fix working drive of make rules on Windows
| * | | Change working drive only in MinGW MakefilesBrad King2011-04-081-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parent commit assumed that "cd /d" would work in all Windows shells. While all modern versions of windows have shells that support it, the shells used by NMake and Borland make do not. Borland make does not seem to even support changing drive letters with "d:". Just revert the feature for all make tools except MinGW where the shell is known to support this feature.
| * | | Fix working drive of make rules on WindowsBrad King2011-04-081-3/+6
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | Teach cmLocalUnixMakefileGenerator3::CreateCDCommand to change working directories for make tools using a Windows shell using "cd /d" instead of just "cd". This tells the shell to change the current drive letter as well as the working directory on that drive. Commit abaa0267 (When the working directory for a custom command is on another drive..., 2007-12-17) fixed the same problem for VS IDE generators as reported by issue #6150.
* | | Merge topic 'xcode-attribute-conditions'Brad King2011-04-122-10/+21
|\ \ \ | | | | | | | | | | | | | | | | c519bb2 XCode: Also qoute [] as needed to set build-configurations.
| * | | XCode: Also qoute [] as needed to set build-configurations.Johan Björk2011-04-072-10/+21
| | | |
* | | | Merge topic 'find_package-forward-components'Brad King2011-04-121-14/+23
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 9fc7ea4 find_package: Forward component list for recursive calls in modules
| * | | | find_package: Forward component list for recursive calls in modulesBrad King2011-04-071-14/+23
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some find modules call find_package recursively to locate a package configuration file for the package instead of searching for individual pieces. Commit 79e9b755 (Help recursive find_package calls in modules, 2008-10-03) taught find_package to forward the version number and EXACT arguments through the recursive call automatically. Do the same for the component list.
* | | | Merge topic 'libarchive-strip-xattr-issue-11958'Brad King2011-04-121-0/+3
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | e8558ef cmArchiveWrite: Clear xattr and acl from entries (#11958)
| * | | | cmArchiveWrite: Clear xattr and acl from entries (#11958)Brad King2011-04-071-0/+3
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When reading archive entries from disk strip any xattr and acl entry headers that may have been loaded from the filesystem (e.g. selinux). These fields are only useful for backup tools and not for packaging and distribution of software. Furthermore, the GNU tar 1.15.1 on at least one Linux distribution treats unknown entry headers as an error rather than a warning. Therefore avoiding such fields is necessary for archive portability. Suggested-by: Tim Kientzle <tim@kientzle.com>
* | | | KWSys Nightly Date StampKWSys Robot2011-04-121-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-111-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-101-1/+1
| |_|/ |/| |
* | | KWSys Nightly Date StampKWSys Robot2011-04-091-1/+1
| |/ |/|
* | KWSys Nightly Date StampKWSys Robot2011-04-081-1/+1
|/
* KWSys Nightly Date StampKWSys Robot2011-04-071-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-061-1/+1
|
* Merge topic 'drag-n-drop-components'Brad King2011-04-054-7/+114
|\ | | | | | | | | | | dd04608 Fix KWStyle warnings 2973c1f Add component support to DragNDrop generator.
| * Fix KWStyle warningsEric NOULARD2011-04-012-9/+19
| |
| * Add component support to DragNDrop generator.Clinton Stimpson2011-03-314-6/+103
| |
* | Merge topic 'cpack-grouping-enum'Brad King2011-04-055-48/+97
|\ \ | | | | | | | | | | | | | | | 9c43824 Fix KWStyle warnings 64a5e20 Combine component packaging methods into an enum.
| * | Fix KWStyle warningsEric NOULARD2011-04-045-14/+20
| |/
| * Combine component packaging methods into an enum.Clinton Stimpson2011-03-315-43/+86
| | | | | | | | | | Also allow generators to override the default packaging method. Add a ONE_PER_GROUP option so that method can be specified by the user without relying on defaults.
* | Merge topic 'fix_vs10_object_files'Brad King2011-04-051-5/+21
|\ \ | | | | | | | | | | | | 9a6ff95 Fix for bug where VS2010 did not use .obj files as part of the build.
| * | Fix for bug where VS2010 did not use .obj files as part of the build.Bill Hoffman2011-04-011-5/+21
| | | | | | | | | | | | | | | | | | | | | For VS2010 if a precompiled .obj file was the output of a custom commad, it was used as part of the build. If it was not, then VS did not use it as part of the build. This commit updates the test to check for this issue, and fixes the problem. This fixes bugs #0011891 and
* | | Merge topic 'upload-built-files'Brad King2011-04-0511-48/+345
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3e32db7 cmCTestUploadCommand::CheckArgumentKeyword should return false if not FILES 6b6f309 Add the FILES keyword to ctest_upload command 28cdd0a Don't tar/gz ctest_upload() files fbe4356 Change 'Files' tag to 'Upload' in Upload.xml 350546d Implement ctest_upload command
| * | | cmCTestUploadCommand::CheckArgumentKeyword should return false if not FILESZach Mullen2011-03-311-1/+1
| | | |
| * | | Add the FILES keyword to ctest_upload commandZach Mullen2011-03-152-13/+31
| | | |
| * | | Don't tar/gz ctest_upload() filesZach Mullen2011-03-153-5/+15
| | | |
| * | | Change 'Files' tag to 'Upload' in Upload.xmlZach Mullen2011-03-151-2/+2
| | | |
| * | | Implement ctest_upload commandZach Mullen2011-03-1511-48/+317
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-051-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-041-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-021-1/+1
| |/ / |/| |
* | | KWSys Nightly Date StampKWSys Robot2011-04-011-2/+2
| |/ |/|
* | Merge topic 'custom-command-slashes'Brad King2011-03-313-5/+14
|\ \ | | | | | | | | | | | | 1286050 Normalize slashes of add_custom_(command|target) DEPENDS (#11973)
| * | Normalize slashes of add_custom_(command|target) DEPENDS (#11973)Brad King2011-03-303-5/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All commands accepting file paths should normalize the slashes so that the string-represented names can be compared reliably. The commands add_library and add_executable have done this for years. We taught add_custom_command to normalize its OUTPUT names in commit a75a0a14 (Normalize add_custom_command OUTPUT names, 2010-12-15). We handled a special case of the DEPENDS option in commit 7befc007 (Handle trailing slashes on add_custom_command DEPENDS, 2011-01-26). Teach both add_custom_command and add_custom_target to normalize slashes of DEPENDS files up front. This approach subsumes the above-mentioned special case so remove the one line added for it but keep its test. Extend the CustomCommand test to check that slash count mismatches between custom command OUTPUT and DEPENDS can still be linked correctly.
* | | Merge topic 'fix_long_filenames_vs2010'Brad King2011-03-311-10/+1
|\ \ \ | | | | | | | | | | | | | | | | 945f2c2 With very long file names, VS 2010 was unable to compile files.
| * | | With very long file names, VS 2010 was unable to compile files.Bill Hoffman2011-03-231-10/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At some point in the past VS 2010 failed some tests with custom commands when relative paths were not used. It seems that those problems have been fixed. However, the relative paths apparently are appended to the current working directoy before vs accesses the file. So, with a long path, relative paths cause it to create a combined path that is too long.
* | | | Merge topic 'cleanup-unused-variable-check'Brad King2011-03-313-26/+27
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | a4335a6 Fix unused cache warning after multiple configure iterations a75ebe3 Refine unused cache variable warning
generated by cgit v0.12 at 2025-02-09 13:32:58 (GMT)