- 05 Oct, 2015 13 commits
-
-
Brad King authored
-
Brad King authored
Release versions do not have the development topic section of the CMake Release Notes index page.
-
Brad King authored
Add section headers similar to the 3.3 release notes and move each individual bullet into an appropriate section. Revise a few bullets.
-
Brad King authored
Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.4.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
-
2402bb8c Help: Document Windows 10 Universal Applications in cmake-toolchains(7) 1be2f12c VS: Add support for Windows 10 Universal (Store) Applications 2798dbda VS: Refactor indentation of LinkLibraryDependencies 8c426183 MSVC: Add system libs for WindowsStore on VS 2015 d1b87d72 VS: Select Windows 10 Store SDK and toolset for VS 2015
-
45812111 VS: Select latest Windows 10 SDK if no specific version was requested
-
2775768f FindMatlab: Add support for Matlab R2015b
-
Brad King authored
-
Teach the VS 2015 generator to support WindowsStore 10.0 applications. Add target properties to customize them: * VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION: Specifies the minimum version of the OS that the project can target. * VS_DESKTOP_EXTENSIONS_VERSION, VS_MOBILE_EXTENSIONS_VERSIONS, VS_IOT_EXTENSIONS_VERSION: Add a reference to the version of the SDK specified to the target allowing to target the extended functionality in a universal project. * VS_IOT_STARTUP_TASK: Specifies that the target should be built as an IOT continuous background task.
-
Use our indentation specifier instead of hard-coding spaces.
-
-
Kitware Robot authored
-
- 04 Oct, 2015 1 commit
-
-
Kitware Robot authored
-
- 03 Oct, 2015 1 commit
-
-
Kitware Robot authored
-
- 02 Oct, 2015 16 commits
-
-
Use WindowsApp.lib for a Universal Application Platform project.
-
-
If CMAKE_SYSTEM_VERSION is just "10.0" then use the latest SDK available since no particular version was requested.
-
85d7a610 Tests: Use consistent C++ flags FindPackageModeMakefileTest
-
7bc202cc Tests: Simplify VSGNUFortran Oracle-specific link lines
-
ec725815 Utilities/Release: Update path to 'cmake.exe' on Windows build machine
-
Teach the VS 2015 generator to produce a WindowsTargetPlatformVersion value. Use the CMAKE_SYSTEM_VERSION to specify the version and if not set choose a default based on available SDKs. Activate this behavior when targeting Windows 10. Co-Author: Brad King <brad.king@kitware.com>
-
Teach CMakeDetermineSystem to check for a CMAKE_SYSTEM_VERSION setting even when CMAKE_SYSTEM_NAME is not set. This will allow builds on the host OS to target other versions of the OS without full cross-compiling.
-
Give VS 10+ generators a chance to choose Windows platform settings just as they already can for WindowsCE, WindowsStore, and WindowsPhone.
-
Wrap a call to VersionCompare with OP_GREATER in a signature suitable for use with std::sort.
-
Brad King authored
Specify their meaning for host builds and when cross compiling. Sepcify their relationship in each case.
-
Kitware Robot authored
-
- 01 Oct, 2015 9 commits
-
-
Brad King authored
-
Brad King authored
On an Oracle 12.4 build the c_using_fortran executable cannot find the "fsu" library at runtime. Since this is an implementation detail of the "hello" library, link that library to it privately so that "-lfsu" does not propagate to the executables consuming it.
-
Brad King authored
Rather than using the CXXFLAGS environment variable in the make-only build, copy the CMAKE_CXX_FLAGS used to build the files on the CMake side. This will account for any changes made by CompileFlags.cmake or cache-provided flags.
-
Use the run_cmake() function to generate the test build tree with the proper CMake generator and also to verify that it succeeds. Drop our PreTestError helper as it is no longer needed.
-
Brad King authored
The DEPENDENCIES test case uses install(TARGETS) and so generates a warning: CMake Warning in CMakeLists.txt: WARNING: Target "test_prog" has runtime paths which cannot be changed during install. To change runtime paths, OS X version 10.6 or newer is required. Therefore, runtime paths will not be changed when installing. CMAKE_BUILD_WITH_INSTALL_RPATH may be used to work around this limitation. Set CMAKE_BUILD_WITH_INSTALL_RPATH to avoid the warning since we do not need to run the binaries from the build tree anyway.
-
Brad King authored
This avoids compiler warnings on stderr while building them.
-
Kitware Robot authored
-