[Cmake-commits] CMake branch, master, updated. v3.9.1-671-gb4efc19

2017-08-30 Thread Kitware Robot 
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, master has been updated
   via  b4efc1936ac4d4154c7d9215165a805b2a6056d5 (commit)
  from  a0ef210da8f8037340049ae99530f2bee6723bc3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b4efc1936ac4d4154c7d9215165a805b2a6056d5
commit b4efc1936ac4d4154c7d9215165a805b2a6056d5
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Thu Aug 31 00:01:11 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Thu Aug 31 00:01:11 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0e0c748..fda6caa 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170830)
+set(CMake_VERSION_PATCH 20170831)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] Future direction for FindCUDA

2017-08-30 Thread Robert Maynard 
> Can I link to CUDA libraries with GCC while not using FindCUDA

Yes you can if you have enabled the CUDA language. You will need to
use find_package and can use the CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES
as the location(s) to search.

> Instead of modifying what FindCUDA does, which would break backwards 
> compatibility, FindCUDA could be split into FindCUDA and FindCUDALibraries or 
> something like that.

That is something I have wanted to do, but haven't had the time to
formalize and finish. You can find my initial implementation at
https://gitlab.kitware.com/robertmaynard/find_cuda_wrappers

On Wed, Aug 30, 2017 at 5:06 AM, Mueller-Roemer, Johannes Sebastian
 wrote:
> Hi,
>
> we have encountered this issue as well, in our case when using thrust on the 
> host side. We currently solve this by still using FindCUDA, even when using 
> CMake 3.8/3.9, but only using the CUDA_*_LIBRARY and CUDA_TOOLKIT_INCLUDE 
> variables and nothing else.
>
> Instead of modifying what FindCUDA does, which would break backwards 
> compatibility, FindCUDA could be split into FindCUDA and FindCUDALibraries or 
> something like that.
>
> Regards
> Johannes
>
> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
> Tel +49 6151 155-606  |  Fax +49 6151 155-139
> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>
>
> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Siyuan Liu
> Sent: Wednesday, August 30, 2017 07:05
> To: cmake@cmake.org
> Subject: [CMake] Future direction for FindCUDA
>
> Dear all,
>
> I've noticed the change to CUDA as a language in CMake 3.8. I've migrated to 
> this new syntax, but this change leads to some difficulties for me with 
> CMake. I think we should treat CUDA as not just a language but rather a 
> language with some libraries.
>
> Now that the FindCUDA module is deprecated, I cannot compile a file with GCC 
> while linking to a CUDA library (since the CUDA_xxx_LIBRARY variables are 
> gone). The reason for not using NVCC is to save compilation time. Personally, 
> I think FindCUDA should become a module for purely finding CUDA libraries for 
> linking without anything related to the NVCC compiler (e.g. the 
> cuda_add_executable macro).
>
> My questions in short:
> 1. Can I link to CUDA libraries with GCC while not using FindCUDA?
> 2. What's your opinion on my suggestion about FindCUDA?
>
> Regards,
> Siyuan
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [cmake-developers] [CMake] Debugging find_package() search behavior?

2017-08-30 Thread Brad King 
On 08/29/2017 05:28 PM, Robert Dailey wrote:
> One other thing: Is there a way to make find_package() default to
> CONFIG mode? Right now it seems to search MODULE first, then CONFIG.
> But right now the only way to enable config is to explicitly use the
> CONFIG option or make sure CMake can't find a find module by
> manipulating CMAKE_MODULE_PATH.

It only searches in one mode.  The presence or non-presence of a
find module in CMAKE_MODULE_PATH is the way the mode is selected
if an explicit CONFIG option is not given.  There is an issue
about this here:

 https://gitlab.kitware.com/cmake/cmake/issues/16805

with an unfinished/expired MR:

 https://gitlab.kitware.com/cmake/cmake/merge_requests/768

Some find modules call `find_package(MyPackage CONFIG ...)` as
their first step if the external package may be found by either
method.

-Brad
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [CMake] Future direction for FindCUDA

2017-08-30 Thread Mueller-Roemer, Johannes Sebastian 
Hi,

we have encountered this issue as well, in our case when using thrust on the 
host side. We currently solve this by still using FindCUDA, even when using 
CMake 3.8/3.9, but only using the CUDA_*_LIBRARY and CUDA_TOOLKIT_INCLUDE 
variables and nothing else.

Instead of modifying what FindCUDA does, which would break backwards 
compatibility, FindCUDA could be split into FindCUDA and FindCUDALibraries or 
something like that.

Regards
Johannes

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
Tel +49 6151 155-606  |  Fax +49 6151 155-139
johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de


-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Siyuan Liu
Sent: Wednesday, August 30, 2017 07:05
To: cmake@cmake.org
Subject: [CMake] Future direction for FindCUDA

Dear all,

I've noticed the change to CUDA as a language in CMake 3.8. I've migrated to 
this new syntax, but this change leads to some difficulties for me with CMake. 
I think we should treat CUDA as not just a language but rather a language with 
some libraries. 

Now that the FindCUDA module is deprecated, I cannot compile a file with GCC 
while linking to a CUDA library (since the CUDA_xxx_LIBRARY variables are 
gone). The reason for not using NVCC is to save compilation time. Personally, I 
think FindCUDA should become a module for purely finding CUDA libraries for 
linking without anything related to the NVCC compiler (e.g. the 
cuda_add_executable macro).

My questions in short:
1. Can I link to CUDA libraries with GCC while not using FindCUDA?
2. What's your opinion on my suggestion about FindCUDA?

Regards,
Siyuan
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake