Re: [CMake] opencl and visual studio

[Boxer, Aaron]

Thanks for your suggestions.  I like the first options. So, how may I create a 
cmake build rule to do this?

Thanks,
Aaron

From: outlook_f942cba43dcb6...@outlook.com 
[mailto:outlook_f942cba43dcb6...@outlook.com] On Behalf Of Nagy-Egri Máté Ferenc
Sent: Monday, July 14, 2014 4:11 PM
To: Boxer, Aaron; cmake@cmake.org
Subject: Re: [CMake] opencl and visual studio

There are two ways to solve your problem I think.


  1.  Either create a build rule that copies the .cl files over to your build 
directory on every build.

  1.  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.

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

[CMake] Fails for Solaris

[Amos]

No matter if I use GNU or workshop compilers, the initial config fails:

CC supports member templates
CC has standard template specialization syntax
CC has argument dependent lookup
CC has struct stat with st_mtim member
CC has ios::binary openmode
CC has ANSI for scoping
-
gmake: 'cmake' is up to date.
loading initial cache file
/usr/soft/that/cmake-3.0.0/src/default/sparcv9_sun_solaris2.10/Bootstrap.cmk/InitialCacheFlags.cmake
-- Using system-installed BZIP2
-- Using system-installed ZLIB
CMake Error: File
/usr/soft/that/cmake-3.0.0/src/default/sparcv9_sun_solaris2.10/Tests/.NoDartCoverage
does not exist.
CMake Error at CMakeLists.txt:161 (configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:527 (CMAKE_SETUP_TESTING)
-- 

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] Install CMake3.0 as alternate

[Nils Gladitz]

On 07/15/2014 02:31 PM, Bradley Lowekamp wrote:

Hello,

Is there a way I can configure CMake when I build it so it's executable with have a "3" or 
"3.0" suffix, so that I can easily have multiple version of cmake installed into 
"/usr/local"?

I am looking for something similar to python's altinstall or gcc's 
"program-suffix" option.



I'd install CMake with a custom prefix e.g. 
"-DCMAKE_INSTALL_PREFIX=/opt/cmake-3.0".


And create appropriate symlinks or aliases.
e.g. ln -s /opt/cmake-3.0/bin/cmake /usr/local/bin/cmake-3.0

Or run it with full path.

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] Install CMake3.0 as alternate

[Bradley Lowekamp]

Hello,

Is there a way I can configure CMake when I build it so it's executable with 
have a "3" or "3.0" suffix, so that I can easily have multiple version of cmake 
installed into "/usr/local"?

I am looking for something similar to python's altinstall or gcc's 
"program-suffix" option.

Thanks,
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

Re: [CMake] [Cdash] Show results from the bullseye coverage in CDash

[David Cole via CMake]

>> There is an option (which should be on by default) in the
>> "Miscellaneous" section of the project settings, which is
>> called: "Show coverage code".

> Thanks, this solves the problem. The option wasn't checked.

The option should be *OFF* by default.

If the intent is not to show your code (because it's private, for
example), then having it OFF is the safe default. Having it OFF by
default and making a mistake results in emails like this... along with
a quick and easy solution to the problem. Having it ON by default and
making a mistake would result in the loss of privacy, which is by far a
worse consequence, with no solution whatsoever. Please keep the default
value *OFF*.


Thanks,
David C.


-- 

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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

Thanks, this solves the problem. The option wasn't checked.

Best Regards

> Am 15.07.2014 um 08:32 schrieb Julien Jomier :
> 
> There is an option (which should be on by default) in the "Miscellaneous" 
> section of the project settings, which is called: "Show coverage code". Can 
> you make sure it's checked?
> 
> Julien
> 
>> On 15/07/2014 00:01, noru...@me.com wrote:
>> 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
>> ___
>> Cdash mailing list
>> cd...@public.kitware.com
>> http://public.kitware.com/mailman/listinfo/cdash
>> 
-- 

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