<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20498">
<style><!--
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
}
a:link, span.MsoHyperlink {
color:blue;
text-decoration:underline;
}
span.MsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
}
span.EmailStyle17 {
font-family:"Calibri","sans-serif";
color:windowtext;
}
.MsoChpDefault {
font-family:"Calibri","sans-serif";
}
div.WordSection1 {
}
ol {
margin-bottom:0in;
}
ul {
margin-bottom:0in;
}
--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>There are two ways to solve your problem I think.</div><div><br></div><ol style="padding-top: 0px; padding-bottom: 0px; margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;"><li style='color: rgb(0, 0, 0); font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 16px;'><div>Either create a build rule that copies the .cl files over to your build directory on every build.</div></li><li style='color: rgb(0, 0, 0); font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 16px;'><div>Use a config file that creates a #define with the absolute/relative path to the .cl files.</div></li></ol><div style='color: rgb(0, 0, 0); font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 16px;'><br></div><div style='color: rgb(0, 0, 0); font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 16px;'>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.</div><div data-signatureblock="true"><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>Feladó:</b> <a href="mailto:Aaron.Boxer@uhn.ca" target="_parent">Boxer, Aaron</a><br><b>Elküldve:</b> hétfő, 2014. július 14. 15:56<br><b>Címzett:</b> <a href="mailto:CMake@cmake.org" target="_parent">cmake@cmake.org</a></font></div></div><div><br></div><div dir="">
<div class="WordSection1">
<p class="MsoNormal">Hello List,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have a cmake project that I am adding opencl support to.</p>
<p class="MsoNormal">I am using the Intel OpenCL sdk, which integrates with Visual Studio.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">So far, I do the following:</p>
<p class="MsoNormal"> </p>
<p class="MsoListParagraph" style="text-indent: -0.25in;"><span>1)<span style='font: 7pt/normal "Times New Roman"; font-size-adjust: none; font-stretch: normal;'>
</span></span>I have a cmake script that finds the opencl libraries and include files</p>
<p class="MsoListParagraph" style="text-indent: -0.25in;"><span>2)<span style='font: 7pt/normal "Times New Roman"; font-size-adjust: none; font-stretch: normal;'>
</span></span>I manually enable opencl support in visual studio in the Tools menu</p>
<p class="MsoListParagraph"> </p>
<p class="MsoNormal">With these steps, all opencl files are statically checked by the compiler. So far, so good.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Has anyone encountered a similar problem? Is there a way of setting the *.cl folder path in cmake? Currently I have to</p>
<p class="MsoNormal">Hard code this into my code, which is hacky.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal">Aaron</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoListParagraph"> </p>
</div>
<p><br>
This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. <br>
Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. <br>
If you have received this e-mail in error, please contact the sender and delete all copies. <br>
Opinions, conclusions or other information contained in this e-mail may not be that of the organization.</p>
</div></div>
</body>
</html>