summaryrefslogtreecommitdiffstats
path: root/Tests/CustomCommandWorkingDirectory
Commit message (Collapse)AuthorAgeFilesLines
* add_custom_{command,target}: Fix WORKING_DIRECTORY leading genexBrad King2018-11-031-2/+2
| | | | | | | | | | | Since commit v3.13.0-rc1~39^2 (add_custom_{command,target}: WORKING_DIRECTORY generator expressions, 2018-09-22) the `WORKING_DIRECTORY` option accepts generator expressions. Fix support for the case of a leading generator expression by deferring conversion to an absolute path until after evaluation of the generator expression. Fixes: #18543
* Tests: Update CustomCommandWorkingDirectory to handle in-source byproductsPedro Navarro2018-09-281-4/+4
| | | | | | | When running an in-source build the CustomCommandWorkingDirectory test created a copy of a source file in the same directory it was running on. This breaks when byproducts are cleaned (e.g. via Ninja) because it deletes one of the source files.
* add_custom_{command,target}: WORKING_DIRECTORY generator expressionsJon Chronopoulos2018-09-281-0/+20
| | | | | | | This teaches add_custom_command and add_custom_target WORKING_DIRECTORY about generator expressions Fixes: #14089
* Tests: use BYPRODUCTS in the CustomCommandWorkingDirectory testBen Boeckel2017-04-211-0/+2
| | | | | | | This was inadvertently testing the assumed sources behavior in Ninja (no other test seems to exercise it). There is now a test explicitly testing it in `RunCMake.Ninja`, so fix this test to work properly regardless of the assumed sources behavior.
* Convert CMake-language commands to lower caseKitware Robot2012-08-131-6/+6
| | | | | | | | | | | | | | | | | 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
* Remove trailing whitespace from most CMake and C/C++ codeKitware Robot2012-08-131-1/+1
| | | | | | | | | | | | | | | | | 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/ \+$//'
* Handle relative WORKING_DIRECTORY in add_custom_(command|target)Brad King2011-01-261-2/+9
| | | | This also fixes handling of trailing slashes in the directory name.
* Handle trailing slashes on add_custom_command DEPENDSBrad King2011-01-261-2/+12
|
* ENH: preclean some warningsKen Martin2008-03-251-0/+1
|
* ENH: fix test to work with in source buildBill Hoffman2006-02-102-1/+1
|
* ENH: add test for working directory of custom command and targetBill Hoffman2006-02-083-0/+35