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 bu
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_lib
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
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.
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.
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 v
