Databases
StackOverflow2013
Postsdbo
POHow to set up Xcode to run OpenCL code, and how to verify the kernels before building
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to set up Xcode to run OpenCL code, and how to verify the kernels before building
    text
    copied!<p>I am looking at the official documentation on the Apple site, and I see that there is a quickstart about how to use OpenCL on Xcode.</p> <p>Maybe it is just me, but I had no luck building the code that is mentioned on the "hello world OCL" section.</p> <p>I've started Xcode and created an empty project; created a main.c and a .cl kernel file, pasting what is on the Apple developer site, and I am not able to get anything to build, even after adding a target.</p> <p>The AD site does not have a project to download, so I have no clue about the cause of the failure (it may be me most likely, or the site assume steps and does not mention them).</p> <p>I've also tried the sample project from macresearch.org, but they are quite ancient, and the test project in the 3rd lesson is not running at all.</p> <p>Now, I am pretty sure that others are using Xcode to run OCL code, but I cannot find any single page (except the aforementioned macresearch.org) that gives a clear setup about how to run an Xcode project with OCL. Is there anyone aware of a tutorial that shows how to work with OCL and Xcode?</p> <p>I have purchased 3 books on OCL (Gaster's Heterogeneous computing with OpenCL, Scarpino's OpenCL in action and Munshi's OpenCL programming guide), and neither mention how to set up Xcode, while they go in detail for the visual studio setup and even for the eclipse setup.</p> <p>On the side; is there any application that is able to validate kernel code before running it in the OCL application?</p> <p>Thanks in advance for any suggestion that you may have.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload