Re: [CMake] Changing the the current generator in CMake GUI
On 7/12/2014 8:17 AM, Bill Hoffman wrote: You can use clear cache. Just to be clear. If you want to change the current generator, you can use File -> Delete Cache. Then you will be able to select a new generator for that directory. I guess the GUI could be change to have a change generator button that gave a big huge warning that it Cache was getting deleted could be done. Or we could address it with documentation. We do welcome contributions if you are interested. See: https://github.com/Kitware/CMake/blob/master/CONTRIBUTING.rst Thanks. -Bill -- 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] CMAKE_FIND_ROOT_PATH and find_library()
I've tried this again, but on OSX. The first example,
cmake_minimum_required( VERSION 3.0 )
project( "cmakefindlibtest" )
list( APPEND CMAKE_FIND_ROOT_PATH "/Users/tmiddleton/lib" )
find_library( punycode_library_test punycode )
message( "punycode_library_test is now ${punycode_library_test}" )
doesn't work - perhaps because find_library() doesn't have any paths to
prepend with CMAKE_FIND_ROOT_PATH? But this,
cmake_minimum_required( VERSION 3.0 )
project( "cmakefindlibtest" )
list( APPEND CMAKE_FIND_ROOT_PATH "/Users/tmiddleton" )
list( APPEND CMAKE_LIBRARY_PATH "lib" )
find_library( punycode_library_test punycode )
message( "punycode_library_test is now ${punycode_library_test}" )
and this,
cmake_minimum_required( VERSION 3.0 )
project( "cmakefindlibtest" )
list( APPEND CMAKE_FIND_ROOT_PATH "/Users/tmiddleton" )
find_library( punycode_library_test punycode PATHS "lib" )
message( "punycode_library_test is now ${punycode_library_test}" )
DO work, as expected. Should I raise a bug for the Windows version? Is the
first example supposed to work too?
On Thu, Jul 10, 2014 at 10:55 AM, Ted Middleton
wrote:
> I'm using cmake 3.0.0 on win7 64-bit and I'm having a difficult time with
> CMAKE_FIND_ROOT_PATH. The cross-compiling cmake page as well as the
> find_library() docs seem to suggest that if CMAKE_FIND_ROOT_PATH is
> non-empty, find_library() will use it to prepend any paths it searches,
> sort of like an alternate sysroot? But that doesn't seem to be happening in
> my set-up and I can't figure out why? When I run this:
>
>cmake_minimum_required( VERSION 3.0 )
>project( "cmakefindlibtest" )
>list( APPEND CMAKE_FIND_ROOT_PATH "C:/DEV/lib" )
>find_library( punycode_library_test punycode )
>message( "punycode_library_test is now ${punycode_library_test}" )
>
> In this case, ${punycode_library_test} ends up being
> punycode_library_test-NOTFOUND. I thought that maybe this was because my
> CMAKE_LIBRARY_PATH was empty - perhaps the problem here is that
> find_library() doesn't have any paths to prepend with CMAKE_FIND_ROOT_PATH
> in the first place, so I tried this:
>
>cmake_minimum_required( VERSION 3.0 )
>project( "cmakefindlibtest" )
>list( APPEND CMAKE_FIND_ROOT_PATH "C:/DEV/" )
>list( APPEND CMAKE_LIBRARY_PATH "lib" )
>find_library( punycode_library_test punycode )
>message( "punycode_library_test is now ${punycode_library_test}" )
>
> This doesn't work either, and neither does
>
> cmake_minimum_required( VERSION 3.0 )
> project( "cmakefindlibtest" )
> list( APPEND CMAKE_FIND_ROOT_PATH "C:/DEV/" )
> find_library( punycode_library_test punycode PATHS "lib" )
> message( "punycode_library_test is now ${punycode_library_test}" )
>
> When I specify PATHS "C:/DEV/lib" to find_library(), or I add "C:/DEV/lib"
> to CMAKE_LIBRARY_PATH, I can find the punycode.lib sitting in my C:/DEV/lib
> directory, but I'd like to know what's going wrong with
> CMAKE_FIND_ROOT_PATH because I'm trying to use it for cross-compiling and
> it doesn't seem to be doing anything the way that I'm using it.
>
>
>
>
>
>
>
--
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] opencl and visual studio
There are two ways to solve your problem I think. Either create a build rule that copies the .cl files over to your build directory on every build. Use a config file that creates a #define with the absolute/relative path to the .cl files. As for the OpenCL integration, I did not know that the Intel SDK checks the validity of the kernel files. That indeed makes life easier. In case you would need something a little more lightweight, AMD’s CodeXL also provides some nice features, and as far as syntax highlighting goes, it does not depend on any feature being turned on inside the project. It just uses the extension of the source file to turn on highlighting. Feladó: Boxer, Aaron Elküldve: hétfő, 2014. július 14. 15:56 Címzett: cmake@cmake.org Hello List, I have a cmake project that I am adding opencl support to. I am using the Intel OpenCL sdk, which integrates with Visual Studio. So far, I do the following: 1) I have a cmake script that finds the opencl libraries and include files 2) I manually enable opencl support in visual studio in the Tools menu With these steps, all opencl files are statically checked by the compiler. So far, so good. However, to actually compile The files with opencl, I need to pass the absolute file path of the *.cl file into opencl. This is because, as is typical With cmake, the build files reside in a folder separate from the source files. Has anyone encountered a similar problem? Is there a way of setting the *.cl folder path in cmake? Currently I have to Hard code this into my code, which is hacky. Also, it would be nice if cmake could automatically switch on opencl support in the visual studio project, but I have no idea how this could be done. Thanks, Aaron This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization.-- 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
[CMake] Show results from the bullseye coverage in CDash
Hello, I use bullseye coverage to perform coverage analysis on windows. We have 2 dashboard (CDash) machines (productive, testing) On the testing machine I could click on a file in CDash to display the coverage analyze for the selected file. On the productive machine I doesn't have those links. Does anybody know why the file links aren't shown, or where the problem could be that they aren't shown? I also tried to update to CDash 2.2.2 with no luck. Thanks in advance Best Regards -- 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] Setting Policy CMP0028
Just to update. I managed to solve the issue by adding this line: cmake_policy(SET CMP0028 OLD) directly to the macro that ends up calling the add_library/add_executable commands. Thank you for the help. Regards, Pierre Andersson From: Nils Gladitz To: pierre.anders...@se.atlascopco.com Cc: cmake@cmake.org Date: 2014-07-11 15:47 Subject:Re: [CMake] Setting Policy CMP0028 On 07/11/2014 03:33 PM, pierre.anders...@se.atlascopco.com wrote: > Then it is odd that it does not work, the warning is given during > generation time and I have tested to print the status of the 0028 policy > at all points where the projects that get the warning has their > add_library/add_executable command called, as well as at the end of > their respective CMakeLists.txt files and it remains in the state OLD > throughout. > At which point is the state of the policy stored when it comes to > generation time? I can see that it works when I construct a minimal > example, so knowing when it's state is 'used' would greaty help in > solving the issue or creating a minimal example that showcases the problem. Given that the warning is at generation time I think it should be the state of the policy at the end of the CMakeLists.txt that defines the target (add_library/add_executable). Nils -- 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
[CMake] opencl and visual studio
Hello List, I have a cmake project that I am adding opencl support to. I am using the Intel OpenCL sdk, which integrates with Visual Studio. So far, I do the following: 1) I have a cmake script that finds the opencl libraries and include files 2) I manually enable opencl support in visual studio in the Tools menu With these steps, all opencl files are statically checked by the compiler. So far, so good. However, to actually compile The files with opencl, I need to pass the absolute file path of the *.cl file into opencl. This is because, as is typical With cmake, the build files reside in a folder separate from the source files. Has anyone encountered a similar problem? Is there a way of setting the *.cl folder path in cmake? Currently I have to Hard code this into my code, which is hacky. Also, it would be nice if cmake could automatically switch on opencl support in the visual studio project, but I have no idea how this could be done. Thanks, Aaron This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization. -- 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
