summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'add_preprocessor_def_vs2010_resources'Brad King2011-01-045-1/+26
|\ | | | | | | | | | | | | 8c7b19d Only run resource test for MSVC compilers. 753e208 Disable incremental testing for this test, it crashes vs9 linker. 16e7d4b Add flags to resource builds on vs 2010 with a test.
| * Only run resource test for MSVC compilers.Bill Hoffman2010-12-221-11/+3
| |
| * Disable incremental testing for this test, it crashes vs9 linker.Bill Hoffman2010-12-221-0/+3
| | | | | | | | | | On windows 7 64 bit, the vs9 linker will crash when linking an application with a resource in it.
| * Add flags to resource builds on vs 2010 with a test.Bill Hoffman2010-12-215-1/+31
| |
* | Merge topic 'dev/add_test-working-directory'Brad King2010-12-283-0/+131
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 667a90a Fix sentence break in add_test documentation 96309fc Make TestsWorkingDirectory test a C file a4a5e37 Use iostream to make Borland happy cfe53cd Fully specify the path to old-signature add_test 017d4e9 Group adding tests with its properties 561cc33 Only test the default cwd with Makefiles d87bae7 Simplify the _default_cwd derivation 992c74f Use --><-- markers to denote the path 5249551 Flip slashes around on Windows 0a014da Add ctype.h include for toupper() af12f83 Fix header includes for C++ and Visual Studio 5597aa2 Rename the project to match the test 9bf4165 Add tests for WORKING_DIRECTORY arg to add_test 42de5d0 Add WORKING_DIRECTORY argument to add_test 7679f9f Rename WorkingDirectory test d95f817 Add the WORKING_DIRECTORY property to tests
| * | Make TestsWorkingDirectory test a C fileBen Boeckel2010-12-172-11/+11
| | |
| * | Use iostream to make Borland happyBen Boeckel2010-12-171-4/+5
| | | | | | | | | | | | | | | It seems as though cstdio doesn't bring in stdio.h with the Borland compilers.
| * | Fully specify the path to old-signature add_testBen Boeckel2010-12-171-2/+2
| | |
| * | Group adding tests with its propertiesBen Boeckel2010-12-171-6/+4
| | |
| * | Only test the default cwd with MakefilesBen Boeckel2010-12-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | XCode and Visual Studio generators can run from ${EXECUTABLE_OUTPUT_PATH}/${CMAKE_BUILD_TYPE} and determining this at testing time is not feasible without adding in more PASS_REGULAR_EXPRESSION's which may create false positives. Since the parsing code is in cross-platform, generator-agnostic code, if it passes with Makefiles, it should work with other generators on other platforms.
| * | Simplify the _default_cwd derivationBen Boeckel2010-12-171-5/+3
| | |
| * | Use --><-- markers to denote the pathBen Boeckel2010-12-172-7/+7
| | |
| * | Flip slashes around on WindowsBen Boeckel2010-12-171-0/+7
| | |
| * | Add ctype.h include for toupper()Ben Boeckel2010-12-171-0/+1
| | |
| * | Fix header includes for C++ and Visual StudioBen Boeckel2010-12-171-2/+3
| | |
| * | Rename the project to match the testBen Boeckel2010-12-161-1/+1
| | |
| * | Add tests for WORKING_DIRECTORY arg to add_testBen Boeckel2010-12-161-0/+21
| | |
| * | Rename WorkingDirectory testBen Boeckel2010-12-163-6/+6
| | |
| * | Add the WORKING_DIRECTORY property to testsRolf Eike Beer2010-12-163-0/+98
| |/
* | Merge topic 'resolve/tests-if-CYGWIN'Brad King2010-12-212-3/+3
|\ \ | | | | | | | | | | | | | | | 853de2e Merge branch 'custom-command-generator-expressions' into resolve/tests-if-CYGWIN d89e238 Cygwin: Fix tests to check CYGWIN instead of WIN32
| * \ Merge branch 'custom-command-generator-expressions' into resolve/tests-if-CYGWINBrad King2010-12-179-40/+82
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tests-if-CYGWIN topic made a change to Tests/Testing/CMakeLists.txt in code that the custom-command-generator-expressions topic moved to the Tests/PerConfig/CMakeLists.txt file. Make the same change to the same content in the new file. (Only a small part of the file moved so rename detection did not do this automatically.)
| * | | Cygwin: Fix tests to check CYGWIN instead of WIN32Brad King2010-12-172-3/+3
| | | | | | | | | | | | | | | | | | | | Use "UNIX AND NOT CYGWIN" to detect a "soname" platform. Use "WIN32 OR CYGWIN" to detect a "DLL" platform.
* | | | Merge topic 'custom-command-generator-expressions'Brad King2010-12-218-32/+51
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4499d50 Mark CustomCommand test perconfig.out as SYMBOLIC f0cdb60 Introduce "generator expression" syntax to custom commands (#11209) 4749e4c Record set of targets used in cmGeneratorExpression ef9e9de Optionally suppress errors in cmGeneratorExpression 45e1953 Factor per-config sample targets out of 'Testing' test 4091bca Factor generator expression docs out of add_test bfb7288 Record backtrace in cmCustomCommand
| * | | | Mark CustomCommand test perconfig.out as SYMBOLICBrad King2010-12-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The custom command with this output does not actually create the file, so mark it as SYMBOLIC.
| * | | | Introduce "generator expression" syntax to custom commands (#11209)Brad King2010-12-153-1/+14
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Evaluate in the COMMAND arguments of custom commands the generator expression syntax introduced in commit d2e1f2b4 (Introduce "generator expressions" to add_test, 2009-08-11). These expressions have a syntax like $<TARGET_FILE:mytarget> and are evaluated during build system generation. This syntax allows per-configuration target output files to be referenced in custom command lines.
| * | | Factor per-config sample targets out of 'Testing' testBrad King2010-12-157-31/+36
| | | | | | | | | | | | | | | | | | | | | | | | Put the source files, build rules, and test scripts for these targets under Tests/PerConfig and refer to it from Tests/Testing as a subdirectory. The targets and scripts will be useful in other tests.
| * | | Merge branch 'imported-target-dependencies' into custom-command-refactorBrad King2010-12-081-5/+45
| |\ \ \
* | \ \ \ Merge topic 'vs2010_header_only_fix'Brad King2010-12-212-1/+9
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | f578381 Fix vs2010 project generation error when HEADER_FILE_ONLY is set.
| * | | | | Fix vs2010 project generation error when HEADER_FILE_ONLY is set.Bill Hoffman2010-12-202-1/+9
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | In vs2010 a bad project file could be generated if a .c or .cxx file was marked with HEADER_FILE_ONLY, if it was in a library that contained both c and c++ code. This fixes the error in the code, and adds a test for this case.
* | | | | Merge topic 'CheckCCompilerFlag-strict-prototypes'Brad King2010-12-211-0/+6
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | b3efdb5 CheckCCompilerFlag: Strict signature of 'main' (#11615)
| * | | | | CheckCCompilerFlag: Strict signature of 'main' (#11615)Brad King2010-12-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use "int main(void)" instead of just "int main()" so that compiling with "gcc -Werror=strict-prototypes" works. Test this check using the flags "-Werror -Wstrict-prototypes" to work with old GCC versions.
* | | | | | Merge topic 'ctest-depend-cycle'Brad King2010-12-212-0/+13
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1f7133c CTest: Fix line-too-long style in DEPEND cycle error f48d3bc CTest: Fix test DEPEND cycle detection
| * | | | | | CTest: Fix test DEPEND cycle detectionBrad King2010-12-152-0/+13
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A cycle exists when the DFS returns to the root node, not just when multiple paths lead to the same node. Inspired-By: Alexander Esilevich <aesilevich@pathscale.com>
* | | | | | Merge topic 'CPack-AddMoreTests'Brad King2010-12-217-0/+243
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 86979e4 Change cpack run and verify script to work with multi-config generators. cdf92c9 Precise the project config type when invoking cpack 08f829b Arrange output in a better way 58bd4f2 CPackTest spit out more output in case of failure dd2a5aa CPack Default component test for ZIP should be OK 88b7f42 CPack new tests for component install
| * | | | | Change cpack run and verify script to work with multi-config generators.Bill Hoffman2010-12-141-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the location of the running cmake to find cpack, and use the CMAKE_CONFIG_TYPE environtment variable as a type for cpack.
| * | | | | Precise the project config type when invoking cpackEric NOULARD2010-12-141-1/+1
| | | | | |
| * | | | | Arrange output in a better wayEric NOULARD2010-12-141-9/+5
| | | | | |
| * | | | | CPackTest spit out more output in case of failureEric NOULARD2010-12-141-3/+16
| | | | | |
| * | | | | CPack Default component test for ZIP should be OKEric NOULARD2010-12-143-6/+19
| | | | | |
| * | | | | CPack new tests for component installEric NOULARD2010-12-147-0/+214
| | |_|_|/ | |/| | |
* | | | | Merge topic 'custom-command-slashes'Brad King2010-12-161-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | a75a0a1 Normalize add_custom_command OUTPUT names (#10485)
| * | | | | Normalize add_custom_command OUTPUT names (#10485)Brad King2010-12-151-1/+1
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the OUTPUT arguments of add_custom_command were not slash-normalized but those of add_library and add_executable were. This caused the example add_custom_command(OUTPUT a//b.c ...) add_library(... a//b.c ...) to fail at build time with "no rule to make a/b.c". Fix this and modify the CustomCommand test to try it.
* | | | | Merge topic 'NAG-Fortran'Brad King2010-12-161-1/+8
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 09d1c10 FortranCInterface: Recognize NAG Fortran module symbols af2ad90 Add NAG Fortran compiler information files 24cc3d4 Recognize the NAG Fortran compiler 83892c4 Allow Fortran platform files to set empty values fe3f878 Detect object files in implicit link information
| * | | | Detect object files in implicit link informationBrad King2010-12-091-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The NAG Fortran compiler implicitly passes object files by full path to the linker. Teach CMakeParseImplicitLinkInfo to parse object files that match some tool-specific regular expression.
* | | | | Merge topic 'dev/support-substring-negative-indices'Brad King2010-12-141-0/+24
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 36cb701 allow STRING(SUBSTRING) work with length -1 as "rest of the string"
| * | | | | allow STRING(SUBSTRING) work with length -1 as "rest of the string"Rolf Eike Beer2010-12-081-0/+24
| | |/ / / | |/| | | | | | | | | | | | | This fixes the first half of bug 10740.
* | | | | Merge topic 'custom-command-depend'Brad King2010-12-141-4/+1
|\ \ \ \ \ | | |_|/ / | |/| | / | |_|_|/ |/| | | | | | | ced1d5e Skip file-level dependencies on custom targets (#11332) e30a775 Improve signature of cmLocalGenerator::GetRealDependency
| * | | Skip file-level dependencies on custom targets (#11332)Brad King2010-12-081-4/+1
| |/ / | | | | | | | | | | | | | | | | | | A custom command may name a target created by add_custom_target in its DEPENDS field. Treat this case as a target-level dependency only since a custom target provides no standard file on which to add a file-level dependency.
* | | Honor custom command dependencies on imported targets (#10395)Brad King2010-12-081-5/+45
|/ / | | | | | | | | | | | | Imported targets do not themselves build, but we can follow dependencies through them to find real targets. This allows imported targets to depend on custom targets that provide the underlying files at build time.
* | Allow add_dependencies() on imported targets (#10395)Brad King2010-11-192-1/+17
| | | | | | | | | | | | | | Imported targets do not themselves build, but we can follow dependencies through them to find real targets. This allows imported targets to depend on custom targets that provide the underlying files at build time.
generated by cgit v0.12 at 2025-01-29 04:58:04 (GMT)