[cmake-developers] Patch for FindOpenSSL.cmake

Hi, some applications only need the OpenSSL crypto library and want to avoid linking against the SSL library, this is currently not possible. This patch adds the variables OPENSSL_CRYPTO_LIBRARY and OPENSSL_SSL_LIBRARY which are set to the respective library; this allows to be more specific when

[cmake-developers] [CMake 0015268]: FindOpenGL.cmake incorrectly depends on X11 on Linux

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15268 == Reported By:GreatEmerald Assigned To:

[CMake] How about GNU Automatic Variables

Hi, I want to use cmake for a library which supports different floating point precision. In Makefile, I used $(*F) to generate the different function name. Could I use $(*F) in cmake? == test.c === #ifdef DOUBLE #define TYPE double #else #define TYPE

Re: [CMake] How about GNU Automatic Variables

On Fri, Nov 28, 2014 at 1:29 AM, Zhang Xianyi traits.zh...@gmail.com wrote: Hi, I want to use cmake for a library which supports different floating point precision. In Makefile, I used $(*F) to generate the different function name. Could I use $(*F) in cmake? ==

Re: [CMake] L

Hi Crni, I just added generating OpenBLASConfig.cmake on OpenBLAS develop branch. ( https://github.com/xianyi/OpenBLAS/commit/fe7dcf98f3666388b75839c6b3e6656580dcd222 ) I think the find_package(OpenBLAS) works fine now. Xianyi 2014-11-11 16:35 GMT+08:00 Crni Gorac cgo...@gmail.com: On Tue,

Re: [CMake] Creating a library from subdirectories

Thanks to all who have replied for your efforts in trying to help me. My apologies for any lack of clarity in describing my problem. With the various information and advice you provided, I have been able to get my CMake configuration working. Thanks again! ..chris On Wed, Nov 26, 2014 at

[CMake] Support OpenBLAS in FindBLAS module

Apologies for the new thread, I just subscribed in order to comment on this, and didnt know how to reply in the existing thread. I am grateful to Xianyi for his addition of OpenBlasConfig.cmake, and I do recognize that this is the direction that projects should go when wanting to build

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc2-915-gafd9747

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via afd97471ab39ab780ae72c8477852ce09df0a2e2 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc2-393-g584d625

20141128) +set(CMake_VERSION_PATCH 20141129) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake