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: [email protected]
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
