- Oct 15, 2013
-
-
e4e5b28c cmTarget: Deprecate the LOCATION target property with a policy.
-
50762188 FindCUDA: Fix NPP library search for CUDA 5.5
-
3507d5af Deprecate COMPILE_FLAGS target property.
-
af1f6987 CMP0024: Store the fact of included export in global generator.
-
920ffbf5 Require CMake 2.8.4 or greater to build CMake
-
2e13c362 OS X: Encode -F framework search flag in per-language platform variable
-
617ee7c5 Add a test for SYSTEM headers in INTERFACE libraries.
-
This allows the use of the $<TARGET_FILE:...> generator expression as a replacement for the use of the LOCATION target property. The use of the LOCATION target property is now deprecated for in-build targets. Also drop other checks for older CMake versions: * Simplify cmake_set_target_folder macro. * Use find_package(LibArchive) unconditionally. * Simplify condition for running testVisualStudioSlnParser test. * Convert two macros to functions. * Unconditionally run the CTestTestRerunFailed test.
-
Kitware Robot authored
-
- Oct 14, 2013
-
-
Kitware Robot authored
-
- Oct 13, 2013
-
-
Kitware Robot authored
-
- Oct 12, 2013
-
-
Kitware Robot authored
-
- Oct 11, 2013
-
-
Stephen Kelly authored
The final location and name of a build-target is not determined until generate-time. However, reading the LOCATION property from a target is currently allowed at configure time. Apart from creating possibly-erroneous results, this has an impact on the implementation of cmake itself, and prevents some major cleanups from being made. Disallow reading LOCATION from build-targets with a policy. Port some existing uses of it in CMake itself to use the TARGET_FILE generator expression.
-
In CUDA 5.5 NPP was divided onto 3 separate libraries: nppc, npps, nppi.
-
Stephen Kelly authored
It is succeeded by COMPILE_OPTIONS, which supports generator expressions, is a list rather than a string, and is properly escaped.
-
Stephen Kelly authored
The export-sets topic, merged in commit 49c7b649 (Merge topic 'export-sets', 2012-10-01) changed install(EXPORT) to allow exporting targets whose dependents are exported separately to different locations. Doing the same for export() was not possible because the export() command was executed at configure-time. Now that export() is also executed at generate-time, make it possible to export to multiple dependent export sets.
-
Stephen Kelly authored
Make the API for adding targets string based so that it can easily use cmGeneratorTarget. Teach the cmIncludeCommand to generate the exported file at configure-time instead if it is to be include()d. The RunCMake.ExportWithoutLanguage test now needs a dummy header.h file as expected error from export() is now reported after the missing file error.
-
Kitware Robot authored
-
- Oct 10, 2013
-
-
Stephen Kelly authored
This is better than the cmCommand, because the lifetime of that is not as useful, and it is only used to report an error anyway. In the next commit, the cmExportBuildFileGenerator will outlive the cmCommand.
-
Brad King authored
Compilers for languages other than C and C++ on OS X may not understand the -F framework search flag. Create a new platform information variable CMAKE_<LANG>_FRAMEWORK_SEARCH_FLAG to hold the flag, and set it for C and CXX lanugages in the Platform/Darwin module. Reported-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Stephen Kelly authored
It was copied from cmExportBuildFileGenerator.
-
Stephen Kelly authored
Storing it in the makefile means that the policy does not trigger when include and export are in differing directories.
-
Kitware Robot authored
-
- Oct 09, 2013
-
-
Stephen Kelly authored
-
7f459a66 Xcode: Teach BuildDepends test that Xcode >= 5 needs no help
-
dcf1b645 OS X: Set CMake.app bundle Info.plist fields (#11694)
-
7efef02d FindGTK2: Add tests for components and targets in gtk and gtkmm modules 95fc47aa FindGTK2: Make pangocairo and cairo optional dependencies 26f790f0 FindGTK2: Change extra includes -> optional 24e0272b FindGTK2: do not skip target creation if optional dependencies are not found d5f130cd FindGTK2: Refactor _GTK2_ADJUST_LIB_VARS into _GTK2_ADD_TARGET fffbd725 FindGTK2: Do not add freetype includes if they are not found b69720d9 FindGTK2: Add libraries to the GTK2_LIBRARIES variable only when found 425ec408 FindGTK2: Do not link libfreetype e9f46dfe FindGTK2: Add config directories only if different from include ones 56a79e1f FindGTK2: Set INTERFACE_COMPILE_DEFINITIONS target property only if not empty 4b47586a FindGTK2: Add check to ensure that target exists 61242ccc FindGTK2: Fix gmodule, glibmm, pangoft2, and pangoxft targets 4b876de9 FindGTK2: Link freetype libs to targets including freetype includes 67e761fa FindGTK2: Small cleanup 682eea39 FindGTK2: Do not require the GTK_ prefix in all the internal functions 0bc3763c FindGTK2: Better handling of include directories ...
-
c5c217c6 FindSDL: Add path suffixes for <prefix>/include/(SDL|SDL12|SDL11)
-
261c2482 unset: Add PARENT_SCOPE option
-
Kitware Robot authored
-
- Oct 08, 2013
-
-
Brad King authored
Drop the HELP_XCODE workarounds needed on older Xcode versions when using Xcode >= 5. We now expect builds and rebuilds to work using proper dependencies with no special help.
-
Brad King authored
Use the Apple Info.plist reference documentation: Core Foundation Keys https://developer.apple.com/library/mac/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html Launch Services Keys https://developer.apple.com/library/mac/documentation/general/Reference/InfoPlistKeyReference/Articles/LaunchServicesKeys.html Cocoa Keys https://developer.apple.com/library/mac/documentation/general/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html modify the Info.plist we create for cmake-gui to add/set fields CFBundleShortVersionString = The release-version-number string LSApplicationCategoryType = UTI that categorizes the app for the App Store NSHumanReadableCopyright = Specifies the copyright notice and drop fields CFBundleGetInfoString CFBundleLongVersionString LSRequiresCarbon Also prepare to set CFBundleVersion = The build-version-number string but leave it commented out as TBD (To Be Determined) for now. The version fields must have form <major>.<minor>.<patch> with integer components. While at it, rename the bundle to end in ".<patch>" instead of "-<patch>" so that it is consistent with the version number and does not look like a packaging increment suffix.
-
Stephen Kelly authored
-
Stephen Kelly authored
-