summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Test OSX_ARCHITECTURES target propertyBrad King2009-10-214-2/+34
| | | | | | | We test the property with a project that fails to link due to an architecture mismatch between an executable and a static library. See issue #8725.
* Define per-target OSX_ARCHITECTURES propertyBrad King2009-10-218-25/+112
| | | | | | | | | | | The CMAKE_OSX_ARCHITECTURES variable works only as a global setting. This commit defines target properties OSX_ARCHITECTURES OSX_ARCHITECTURES_<CONFIG> to specify OS X architectures on a per-target and per-configuration basis. See issue #8725.
* Fix seg fault for empty ENV{} call bug #9747Bill Hoffman2009-10-211-1/+5
|
* KWSys Nightly Date StampKWSys Robot2009-10-211-1/+1
|
* Better fix for finding the MSBuild that matches the VS 10 install.Bill Hoffman2009-10-201-4/+2
|
* Add search path for VS 10 beta 2 MSBuild.Bill Hoffman2009-10-201-0/+2
|
* make testing the CodeBlocks and Eclipse generators easier by not requiring ↵Alexander Neundorf2009-10-202-4/+14
| | | | | | | | | | | | | the CMAKE_EDIT_COMMAND variable Both generators use the CMAKE_EDIT_COMMAND variable to determine whether they should add the edit_cache target, i.e. they don't add it if it's ccmake, since this does not work inside the output log view of Eclipse/Codeblocks. But instead of requiring the variable to be set they now check it for 0 and handle this appropriately. This should help Dave getting some testing for them :-) Alex
* Do not link library dependencies in VS solutionsBrad King2009-10-206-1/+50
| | | | | | | | | | | | | | | | | | | | | | | | In VS 8 and greater this commit implements add_dependencies(myexe mylib) # depend without linking by adding the LinkLibraryDependencies="false" option to project files. Previously the above code would cause myexe to link to mylib in VS 8 and greater. This option prevents dependencies specified only in the solution from being linked. We already specify the real link library dependencies in the project files, and any project depending on this to link would not have worked in Makefile generators. We were already avoiding this problem in VS 7.1 and below by inserting intermediate mylib_UTILITY targets. It was more important for those versions because if a static library depended on another library the librarian would copy the dependees into the depender! This is no longer the case with VS 8 and above so we do not need that workaround. See issue #9732.
* Fix failing test. Forgot to double quote last arg to STRING.David Cole2009-10-201-3/+3
|
* Add test of all available CPack generators. Add this test with the goal of ↵David Cole2009-10-204-1/+96
| | | | increasing coverage of the cpack source code, even/especially when the underlying packager tool is not installed. The test does not fail if there is a cpack problem with a certain generator. I expect some generators will fail on every machine running a CMake dashboard.
* Added a ctest add_subdirectory test which fails before my patch made earlier ↵Zach Mullen2009-10-206-0/+65
| | | | today.
* Ctest was broken for subdirs. Restored working directory state for tests so ↵Zach Mullen2009-10-201-0/+5
| | | | that their executables could be found.
* Fixes version detection using osg/Version on Mac OSX when OSG is installed ↵Philip Lowman2009-10-201-2/+8
| | | | | | as a framework Patch from rpavlik attached to issue #9714
* KWSys Nightly Date StampKWSys Robot2009-10-201-1/+1
|
* Avoid C++ linker language in VS Fortran projectBrad King2009-10-191-1/+2
| | | | | | | | | | | | | | | In Visual Studio project files we pass compiler flags to the whole target based on the linker language, which works for MS tools and combinations of C and C++. For the Intel Fortran plugin though the generated .vfproj files should never contain C or C++ options. We generate .vfproj files only for targets consisting only of Fortran code. Now that the linker language is computed transitively through linking it is possible that the linker language is C++ for an otherwise Fortran-only project. This commit forces Fortran as the linker language for the purpose of specifying target-wide flags in .vfproj files. See issue #9719.
* fix whitespace, so documentation is formatted properlyAlexander Neundorf2009-10-191-15/+15
| | | | Alex
* fix two more icpc warnings, ok by Brad (float compared for equality, unused ↵Alexander Neundorf2009-10-191-2/+2
| | | | | | variable) Alex
* Avoid duplicate ZERO_CHECK in VS solutionsBrad King2009-10-194-122/+107
| | | | | | | | | | | | The commit "Avoid non-root copies of root-only targets" moved the check for root-only targets into cmGlobalGenerator::GetTargetSets to avoid adding multiple ALL_BUILD targets to the "original" target set. This approach did not work for ZERO_CHECK targets though because those are pulled in by dependency analysis. Instead we eliminate duplicate ZERO_CHECK targets altogether and refer to a single one from all solution files. This cleans up VS 10 project file references to ZERO_CHECK targets anyway.
* Fixed bug 8319, search for the Python shared library in the standard locations.Marcus Hanwell2009-10-191-2/+0
|
* KWSys Nightly Date StampKWSys Robot2009-10-191-1/+1
|
* KWSys Nightly Date StampKWSys Robot2009-10-181-1/+1
|
* Remove the rpath_remove_file_is_not_executable test case. It fails on ↵David Cole2009-10-172-3/+3
| | | | Windows, but passes on Linux. Put back later after addressing inconsistency.
* Fixed issues with message text in FILE command error situations. Added many ↵David Cole2009-10-173-11/+122
| | | | new test cases to increase the coverage of the FILE command even further.
* KWSys Nightly Date StampKWSys Robot2009-10-171-1/+1
|
* Add more testing coverage of the FILE command.David Cole2009-10-162-0/+116
|
* Try to fix bug#9714, should not crash when version file is not where it ↵Bill Hoffman2009-10-161-4/+7
| | | | should be...
* Better fix for crash on Windows. This time it will even work on Linux, too. ↵David Cole2009-10-161-2/+14
| | | | That GetLineFromStream method while loop sure is fussy.
* Allow test to pass even if an expected-to-fail submit claims 'Submission ↵David Cole2009-10-161-1/+2
| | | | successful' - apparently when there is a valid HTTP_PROXY involved, our submitting to an empty drop location appears to succeed. Presumably, the proxy simply takes it like a man, and then discards it...
* Fix crash on Windows. If input stream is no good, do not try to read a line ↵David Cole2009-10-161-2/+3
| | | | from it. Return false and an empty line instead...
* KWSys Nightly Date StampKWSys Robot2009-10-161-1/+1
|
* add a test which checks that cmake can build the latest stable KDE4 ↵Alexander Neundorf2009-10-152-0/+104
| | | | | | | | | | | (kdelibs) release To enable this test, the option TEST_KDE4_STABLE_BRANCH must be switched on. It can only be switched on if CMAKE_RUN_LONG_TESTS is ON. Then the test will only be added if Qt >= 4.5 can be found, Perl can be found and ZLIB can be found. Alex
* Increase ctest coverage. Introduce optionally on intentional compile errors ↵David Cole2009-10-154-1/+24
| | | | and warnings to the SmallAndFast project. Turn them on for the FailedSubmit tests to cover analyzing LABELS-related errors and warnings.
* Use LABELS in some ctest_coverage calls to increase coverage in ↵David Cole2009-10-152-1/+12
| | | | cmCTestCoverageHandler.cxx.
* Fix ctest output alignment for cases where total tests run is not the same ↵Zach Mullen2009-10-151-1/+1
| | | | width as max test index.
* Add LABELS to the SmallAndFast test project to increase coverage of ctest ↵David Cole2009-10-151-0/+7
| | | | code that is only invoked when labels are present.
* Fix crash on Windows. Remove trailing white space from regex. These changes ↵David Cole2009-10-152-2/+2
| | | | should correct all failures of the new FailedSubmit tests.
* KWSys Nightly Date StampKWSys Robot2009-10-151-1/+1
|
* make it more robust wrt. #9621Alexander Neundorf2009-10-141-8/+8
| | | | | | | | | | although #9621 did not happen anymore with cmake 2.8.0, probably because GET_PROPERTY(... GLOBAL ...) now makes the result variable empty instead of simply not touching it, using FUNCTION() instead of MACRO() makes sure that the _EnabledFeatures variables is always empty before the GET_PROPERTY() call (and does not still have the old value from the previous call) Alex
* Add another possible error message that curl might emit with an empty drop ↵David Cole2009-10-141-0/+1
| | | | location.
* Use macro instead of function since DASH2 continuous dashboard still uses ↵David Cole2009-10-141-2/+11
| | | | CMake 2.4.8 to drive the dashboard. Add clarifying comments so that a future developer does not delete seemingly unused variables: they are used: inside the input to the configure_file call.
* Increase ctest coverage. Add tests that intentionally call ctest_submit ↵David Cole2009-10-142-1/+70
| | | | without any drop location so that the submits fail. Call for each possible type of submit. Also use the launchers from these scripts.
* KWSys Nightly Date StampKWSys Robot2009-10-141-1/+1
|
* Fix floating point comparison warnings. Thanks to Alex Neundorf for the patch.David Cole2009-10-133-7/+7
|
* fix line lengthAlexander Neundorf2009-10-131-1/+2
| | | | Alex
* Fix line length.Zach Mullen2009-10-131-1/+2
|
* KWSys Nightly Date StampKWSys Robot2009-10-131-1/+1
|
* Fix issue #5668 - use CollapseFullPath when determining if covered file is ↵David Cole2009-10-121-91/+133
| | | | within source or binary tree. Allows gcc/gcov coverage analysis using MinGW on Windows.
* fix indentationAlexander Neundorf2009-10-121-75/+74
| | | | Alex
* fix #9687Alexander Neundorf2009-10-121-4/+12
| | | | | | | The CodeBlocks generator did not put all cmake files into the cmake tree of the generated project. Patch from Daniel Teske. Alex
* Uncomment block in InitializeFromCommand (accidentally checked this change in)Zach Mullen2009-10-121-4/+4
|
generated by cgit v0.12 at 2025-02-11 04:27:16 (GMT)