| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
| |
today.
|
|
|
|
| |
that their executables could be found.
|
|
|
|
|
|
| |
as a framework
Patch from rpavlik attached to issue #9714
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Alex
|
|
|
|
|
|
| |
variable)
Alex
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Windows, but passes on Linux. Put back later after addressing inconsistency.
|
|
|
|
| |
new test cases to increase the coverage of the FILE command even further.
|
| |
|
| |
|
|
|
|
| |
should be...
|
|
|
|
| |
That GetLineFromStream method while loop sure is fussy.
|
|
|
|
| |
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...
|
|
|
|
| |
from it. Return false and an empty line instead...
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(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
|
|
|
|
| |
and warnings to the SmallAndFast project. Turn them on for the FailedSubmit tests to cover analyzing LABELS-related errors and warnings.
|
|
|
|
| |
cmCTestCoverageHandler.cxx.
|
|
|
|
| |
width as max test index.
|
|
|
|
| |
code that is only invoked when labels are present.
|
|
|
|
| |
should correct all failures of the new FailedSubmit tests.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
location.
|
|
|
|
| |
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.
|
|
|
|
| |
without any drop location so that the submits fail. Call for each possible type of submit. Also use the launchers from these scripts.
|
| |
|
| |
|
|
|
|
| |
Alex
|
| |
|
| |
|
|
|
|
| |
within source or binary tree. Allows gcc/gcov coverage analysis using MinGW on Windows.
|
|
|
|
| |
Alex
|
|
|
|
|
|
|
| |
The CodeBlocks generator did not put all cmake files into the cmake tree of
the generated project. Patch from Daniel Teske.
Alex
|
| |
|
|
|
|
| |
Requires CDash update to show on CDash.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Add STATUS output "Could NOT find Boost" if boost is not found
which brings FindBoost closer in behavior to most CMake find modules.
2. Add an option: Boost_DETAILED_FAILURE_MSG to output
Boost_ERROR_REASON on a non-REQUIRED find if this
is desired by the developer. This is done because the error messages
are rather long and software with optional Boost dependencies might
not like them showing up by default, especially since this wasn't done
before.
3. Add mention of Boost_ADDITIONAL_VERSIONS close to top
of file since this seems to be the most common problem brought
up on the mailing list (maybe people will notice it there)
4. Added additional check for intel compiler which probably isn't
necessary but ultimately should be cleaner if CMAKE_CXX_COMPILER_ID
sticks around.
5. Added my name to the Copyright list
|
| |
|
|
|
|
| |
Also refrain from setting _LIBRARIES & _INCLUDE_DIRS if lib not found (seems to be mostly standard practice).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We revert commit "Create CMake Policy CMP0015 to fix set(CACHE)" because
the NEW behavior of the policy breaks a valid use case:
# CMakeLists.txt
option(BUILD_SHARED_LIBS "..." ON)
add_library(mylib ...)
set(BUILD_SHARED_LIBS OFF) # we want only mylib to be shared
add_subdirectory(ThirdParty)
# ThirdParty/CMakeLists.txt
option(BUILD_SHARED_LIBS "..." ON)
# uh, oh, with NEW behavior this dir uses shared libs!!!
We'll re-introduce the policy later with a different change in behavior
to resolve the motivating case, which was more subtle but less common.
See issue #9008.
|