| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
non-bootstrap builds
|
|
|
|
|
| |
- The GET_TEST_PROPERTY command does not exist during bootstrap.
- Instead of lots of conditionals, replace it with a macro.
|
|
|
|
|
|
| |
- Commands SET_TESTS_PROPERTIES and GET_TEST_PROPERTY exist
in CMake 2.4, which is now required.
- Therefore we need not check before using them.
|
|
|
|
|
| |
- Test SubProject-Stage2 is conditionally created.
- Set properties on it only if it exists.
|
| |
|
| |
|
|
|
|
| |
installer is available.
|
|
|
|
| |
don't get mylibapp.exe in our GLOB results in make based build trees where the built exes end up in the same directory as the CPack installers...)
|
|
|
|
| |
PackageMaker installers. Thanks to Doug Gregor for all the hard work involved with implementing this patch! Also added new test CPackComponents that is conditionally executed only when NSIS or PackageMaker installer builders are available.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Alex
|
| |
|
|
|
|
|
|
| |
- Previously the find_* commands did not normalize the search paths
- The recent refactoring enabled such normalization
- The FindBase test must also normalize before comparing paths
|
|
|
|
| |
IDE adds some extra characters to the variable value during expansion.
|
|
|
|
| |
VERBATIM option.
|
|
|
|
|
|
|
|
| |
- Option was recently added but never released.
- Custom commands no longer depend on build.make so we do
not need the option.
- Rule hashes now take care of rebuilding when rules change
so the dependency is not needed.
|
|
|
|
|
|
|
| |
- Tests IMPLICIT_DEPENDS_INCLUDE_TRANSFORM properties.
- See issue #6648.
- Works without help in VS IDEs due to native dependency handling.
- Xcode needs help to rebuild correctly.
|
|
|
|
|
|
| |
- Allows make rules to be created with no dependencies.
- Such rules will not re-run even if the commands themselves change.
- Useful to create rules that run only if the output is missing.
|
| |
|
|
|
|
|
| |
- See bug#6868.
- Update CustomCommand test to check.
|
| |
|
|
|
|
| |
minutes on really slow/busy machines. bootstrap has been timing out on tiamat, a very old machine, this should help it...
|
|
|
|
| |
Alex
|
|
|
|
| |
framework names.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Place the built library in foo.framework/Versions/A/foo
- Do not create unused content symlinks (like PrivateHeaders)
- Do not use VERSION/SOVERSION properties for frameworks
- Make cmTarget::GetDirectory return by value
- Remove the foo.framework part from cmTarget::GetDirectory
- Correct install_name construction and conversion on install
- Fix MACOSX_PACKAGE_LOCATION under Xcode to use the
Versions/<version> directory for frameworks
- Update the Framework test to try these things
|
| |
|
|
|
|
| |
source.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- This will help projects support multiple CMake versions.
- In order to set a policy when using a newer CMake but still
working with an older CMake one may write
if(POLICY CMP1234)
cmake_policy(SET CMP1234 NEW)
endif(POLICY CMP1234)
- Note that since CMake 2.4 does not have if(POLICY) supporting
it will also require using "if(COMMAND cmake_policy)"
|
|
|
|
| |
Tests/MakeClean/ToClean/CMakeLists.txt and Tests/Preprocess/CMakeLists.txt. CMP0000 now requires the cmake_minimum_required command.
|
|
|
|
| |
duplicates from a list (keep the ordering)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove CMP_0001 (no slash in target name) and restore
old CMAKE_BACKWARDS_COMPATIBILITY check for it
- Replace all checks of CMAKE_BACKWARDS_COMPATIBILITY
with cmLocalGenerator::NeedBackwardsCompatibility calls
- Create new CMP_0001 to determine whether or not
CMAKE_BACKWARDS_COMPATIBILITY is used.
(old = use, new = ignore)
- Show CMAKE_BACKWARDS_COMPATIBILITY in cache only when
CMP_0001 is set to OLD or WARN
- Update documentation of cmake_policy and cmake_minimum_required
to indicate their relationship and the 2.4 version boundary
- When no cmake policy version is set in top level makefile
implicitly call cmake_policy(VERSION 2.4) which restores
CMAKE_BACKWARDS_COMPATIBILITY and other 2.4 compatibility
- Fix tests MakeClean and Preprocess to call
cmake_policy(VERSION 2.6) because they depend on new policies
|
|
|
|
| |
executable files depend on. Primary uses are to determine what shared libraries should be copied into Mac OSX bundle applications to create standalone bundles apps and to determine what shared library files need to be installed for an executable to run on any platform. Requires native platform tools dumpbin, otool and ldd to generate results.
|
| |
|
|
|
|
| |
tool that is at fault for not supporting a particular character in definitions. Make it skip the % character when the compiler is MSVC and it is a non-nmake tool.
|
|
|
|
| |
consistent with new SET_PROPERTY and GET_PROPERTY signatures.
|
| |
|
| |
|
| |
|
|
|
|
| |
difficult test cases.
|
|
|
|
|
| |
- Use real name instead of link for location of versioned targets
- Error when a target is exported multiple times
|
| |
|
|
|
|
| |
sub-project
|