- 02 Dec, 2014 10 commits
-
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
d051cbda FindOpenGL: Drop explicit dependency on X11 (#15268)
-
64f8c533 Help: Fix typo in cmake-compile-features(7) manual
-
20bf6971 CMakeParseImplicitLinkInfo: Fix implicit library logging
-
1c5be1f3 Makefile: Do not create an empty linker response file
-
be9bec5d FindOpenSSL: Report crypto and ssl libraries separately
-
Fix spelling 'execptions' => 'exceptions'.
-
Kitware Robot authored
-
- 01 Dec, 2014 27 commits
-
-
Brad King authored
-
Brad King authored
-
Brad King authored
Since commit v3.1.0-rc1~821^2 (Windows: Use response files to specify link libraries for GNU tools, 2014-03-04) we use a response file to pass possibly long linker flag lists to the GNU linker on Windows. On MinGW, this may cause gfortran to use a response file to pass some flags to its own internal invocation. This is okay except when we are parsing implicit link flags from the compiler ABI detection build. If gfortran uses a response file in that case then we may miss extracting some of the implicit link flags, such as -lgfortran. Fortunately, in the compiler ABI detection case we do not actually link to anything so the response file is empty. Work around this problem by simply not using a response file when the list of flags it is used to pass is empty (or just whitespace). Reported-by:
Bill Somerville <bill@classdesign.com>
-
Brad King authored
In commit v3.1.0-rc1~640^2~5 (Clean up usage of if(... MATCHES regex) followed string(REGEX REPLACE regex), 2014-04-06) we accidentally broke logging of the implicit library detection. Restore use of the intermediate 'lib' variable so that the log message is constructed properly. Reported-by:
Bill Somerville <bill@classdesign.com>
-
Brad King authored
In commit 079e8469 (... OpenGL always needs X11 on Unix, 2002-09-05) the FindOpenGL module was taught to search for X11 as a dependency of the OpenGL library. This was done without a detailed explanation, and the dependency should not be explicitly needed because OpenGL headers should not expose applications to X11 APIs directly. Unfortunately the only way to know if anything legitimately depends on this behavior (perhaps in static library cases) is to simply remove it and wait for issues to be reported. If so, then we can add some kind of compatibility setting for this later. Add a release note to draw attention to this change. Reported-by:
Dainius "GreatEmerald" Masiliūnas <pastas4@gmail.com>
-
Brad King authored
-
df53aafd Help: Add missing space to ctest -j option description
-
Some applications only need the OpenSSL crypto library and want to avoid linking against the SSL library. Set OPENSSL_CRYPTO_LIBRARY and OPENSSL_SSL_LIBRARY in the code paths that do not need to find them separately, and document them publicly. This allows applications to be more specific when linking against OpenSSL.
-
Brad King authored
-
-
191d2b20 Help: Remove duplicate '#' in CMP0053 valid character list
-
672f1001 Genex: Fix evaluation context propagation for TARGET_OBJECTS.
-
84d124e8 Fix lookup of source names after conversion to their actual case (#15259)
-
75dee2f2 FindwxWidgets: Add versions 3.0.1 and 3.0.2
-
d49f1c5e Build CMake with most-recent available language dialect.
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
Since commit v3.1.0-rc1~479^2~1 (Add an "installed file" property scope, 2014-05-15) the get_property and set_property commands support an 'INSTALL' scope. Add documentation for this scope.
-
Brad King authored
-
-
Kitware Robot authored
-
- 30 Nov, 2014 1 commit
-
-
Kitware Robot authored
-
- 29 Nov, 2014 2 commits
-
-
Stephen Kelly authored
-
Stephen Kelly authored
This can be allowed in the next release, but it needs to have some features present and tested such as * Ensuring that relative paths do not appear in the generated property. * Ensuring that paths to the source or build directories do not appear. * Generating a check in the file for CMake 3.1 or later so that the resulting property will be consumed. * Ensuring that any referenced targets are part of an export set and generating a check for them. * INSTALL_INTERFACE and BUILD_INTERFACE content. All of these checks are already done for INTERFACE_INCLUDE_DIRECTORIES, but it is too late to add them for INTERFACE_SOURCES for CMake 3.1. As the checks introduce some new error conditions, it is better to disallow exporting fully for this case and introduce proper error conditions later instead of policies.
-