| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
| |
file is not found during a core try compile.
|
|
|
|
| |
resolves the strange and difficult to diagnose (or reproduce) test failures on the dashmacmini2 Continuous dashboard.
|
| |
|
|
|
|
|
|
| |
The link_directories command treats relative paths differently from most
CMake commands. This notes the difference in the documentation.
See issue #8377.
|
|
|
|
|
|
|
| |
Some OS X linkers want a 'dylib_' prefix on the -compatiblity_version
and -current_version flags while others do not. This passes the flags
through gcc instead since it never wants the prefix and translates the
flags for the linker correctly.
|
|
|
|
| |
Fixes #8433.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
am deducing that the value of CMAKE_OSX_ARCHITECTURES_DEFAULT is responsible for the failure, although I cannot reproduce it on other builds or even by running the test via ctest interactively *on* the continuous dashboard's build...
|
|
|
|
| |
that runs on 10.3 and earlier does not understand the compiler flag it maps to...
|
|
|
|
| |
from the Continuous dashboard test that is failing.
|
|
|
|
|
|
|
|
|
|
| |
When running in script mode it is possible to run multiple separate
dashboard submissions in one cmCTest instance. The recent refactoring
of file submission lists into parts failed to clear the submission lists
when starting a new dashboard (ctest_start or ctest_update). Only the
unused old submission set was cleared. This fixes the refactored
version to remove the old submission set completely and also clear the
part-wise lists.
|
|
|
|
|
|
|
|
| |
We need to initialize cmCTestSubmitHandler on construction to make sure
all parts get enabled by default. The recent fix to re-enable all parts
on initialization broke submit-only operations because the handler did
not initialize on construction. This also removes duplicate
initialization code.
|
|
|
|
| |
is auto-defined now
|
|
|
|
| |
is auto-defined now
|
|
|
|
| |
specify the target deployment runtime OS version of the built executables on Mac OSX. Thanks to Mike Jackson for the patch.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
with Qt 4.5 on Mac.
|
| |
|
|
|
|
| |
speaking, this changes behavior from cpack 2.6, but now that cpack returns a non-zero exit code when it encounters an error, and it is an error to try to use a generator that is not available... It makes sense to turn these off by default since not everybody has these generators installed. It is easy for a project to turn these options back on if they need to: simply set(CPACK_BINARY_TBZ2 ON) or set(CPACK_BINARY_ZIP ON) before include(CPack) in your CMakeLists.txt...
|
| |
|
|
|
|
| |
doesn't have to have everything in order for FLTK_FOUND to be true. #7809
|
| |
|
|
|
|
| |
cmCPackDragNDropGenerator. Fix it now that it really matters. (The BundleGenerator test started failing after the last commit. This fixes it.)
|
|
|
|
| |
and CPACK_BUNDLE_NAME is not set. Instead, fail gracefully giving an informative error message and non-zero exit code.
|
|
|
|
|
|
|
|
| |
Isolation of policy changes inside scripts is important for protecting
the including context. This teaches include() and find_package() to
imply a cmake_policy(PUSH) and cmake_policy(POP) around the scripts they
load, with a NO_POLICY_SCOPE option to disable the behavior. This also
creates CMake Policy CMP0011 to provide compatibility. See issue #8192.
|
|
|
|
|
|
|
| |
This teaches functions and macros to use policies recorded at creation
time when they are invoked. It restores the policies as a weak policy
stack entry so that any policies set by a function escape to its caller
as before.
|
|
|
|
|
|
| |
This re-organizes the discussion of the policy stack in documentation of
the cmake_policy() command. The new organization clearer and easier to
extend with new information.
|
|
|
|
|
|
|
| |
A 'weak' poilcy stack entry responds normally to queries. However,
setting a policy in a weak entry will recursively set the policy in the
next entry too. This also gives the internal interface to create a weak
entry the option to provide an initial PolicyMap for it.
|
|
|
|
| |
of CPack. Add a test of it in the CPackComponents test. Thanks to Clinton Stimpson for the patch.
|
|
|
|
|
| |
This creates a barrier mechanism to prevent user code from using
cmake_policy(POP) to pop a scope it didn't push with cmake_policy(PUSH).
|
|
|
|
|
|
|
|
| |
This makes cmMakefile::PushPolicy and cmMakefile::PopPolicy private so
that any outside place that uses them needs to use the PolicyPushPop
helper in an automatic variable. We grant an exception to
cmCMakePolicyCommand so it can implement cmake_policy(PUSH) and
cmake_policy(POP).
|