summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* make compile command output optionalManuel Klimek2011-04-252-2/+3
|
* implement cxx command outputManuel Klimek2011-04-253-2/+66
|
* cache flags and definesManuel Klimek2011-04-252-45/+54
|
* refactor flags and definesManuel Klimek2011-04-252-55/+68
|
* KWSys Nightly Date StampKWSys Robot2011-04-251-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-241-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-231-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-221-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-211-1/+1
|
* KWSys Nightly Date StampKWSys Robot2011-04-201-1/+1
|
* Merge topic 'find_package-system-registry'Brad King2011-04-192-30/+95
|\ | | | | | | | | | | | | | | | | | | | | 08b9397 find_package: Fix system package registry test path conversion 93021ad find_package: Test system package registry when possible b95f3ca find_package: Check both 32-bit and 64-bit registry views a0d76c1 find_package: Search a "system package registry" 549458f find_package: Document user package registry locations c9563db find_package: Cleanup user package registry less aggressively 4df1197 find_package: Rename implementation of user package registry
| * find_package: Check both 32-bit and 64-bit registry viewsBrad King2011-04-132-6/+40
| | | | | | | | | | | | The system package registry is under HKEY_LOCAL_MACHINE\SOFTWARE which has separate views for 32-bit and 64-bit applications. Look in both views, but prefer the architecture matching the build target platform.
| * 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.
* | Merge topic 'CPackRPM-fix12096'Brad King2011-04-191-0/+22
|\ \ | | | | | | | | | | | | d3fd945 CPackRPM Fix #12096: handle absolute install path with component install
| * | CPackRPM Fix #12096: handle absolute install path with component installEric NOULARD2011-04-171-0/+22
| | |
* | | Merge topic 'improve-debug-trycompile-help-text'Brad King2011-04-192-6/+13
|\ \ \ | | | | | | | | | | | | | | | | 7f6f606 CMake: Clarify the --debug-trycompile help text
| * | | CMake: Clarify the --debug-trycompile help textDavid Cole2011-04-122-6/+13
| | | |
* | | | Merge topic 'MoreGraphVizFeatures'Brad King2011-04-193-25/+177
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 08fa5dd Also generate dependers-graphviz files. 4f96a76 GRAPHVIZ_IGNORE_TARGETS is now a list of regular expressions 5698ad2 Make it possible to exlude external libs from dot files
| * | | | Also generate dependers-graphviz files.Alex Neundorf2011-02-063-0/+140
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With this commit, the --graphviz option now also generates dot files which show which other targets depend on some target. So, now there is * a global dot-file which shows all targets and dependencies * a dot file which shows on what a target Foo depends * a dot file which shows which other targets depend on Foo Alex
| * | | | GRAPHVIZ_IGNORE_TARGETS is now a list of regular expressionsAlex Neundorf2011-02-052-25/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is similar e.g. to CTEST_CUSTOM_WARNING_EXCEPTION from ctest. GRAPHVIZ_TARGET_IGNORE_REGEX is not supported anymore. I hope this is ok, since this was 100% undocumented and can't break a build. Alex
| * | | | Make it possible to exlude external libs from dot filesAlex Neundorf2011-02-052-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Patch from Christian Ehrlicher. By setting GRAPHVIZ_EXTERNAL_LIBS to TRUE in CMakeGraphVizOptions.cmake you can now exclude external libraries from the produced dot file. I.e. then you see only the dependencies within your project. Alex
* | | | | KWSys Nightly Date StampKWSys Robot2011-04-191-1/+1
| | | | |
* | | | | KWSys Nightly Date StampKWSys Robot2011-04-181-1/+1
| |_|/ / |/| | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-171-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-161-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-151-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-04-141-1/+1
| | | |
* | | | KWSys: Remove unused CheckCXXSourceRuns cmake moduleBrad King2011-04-131-62/+0
| |_|/ |/| | | | | | | | | | | | | | | | | | | | This file has not been used in KWSys since commit "Moved test for large file support into kwsysPlatformCxxTests.cxx", 2006-08-25. CMake 2.6.0 and above come with a copy of this module anyway, and KWSys has required CMake 2.6.3 since commit "KWSys: Require at least CMake 2.6.3", 2011-03-01.
* | | 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
| |_|/ / |/| | |
generated by cgit v0.12 at 2025-01-25 18:52:32 (GMT)