Have you added the framework to your project? To do this, click on the project in the left file-pane (on top), make sure your target is selected, select ‘Build Phases’, open up ‘Link Binary With Libraries’ and click the ‘+’ at the bottom, type in ‘opencl’ and double-click on OpenCL.framework.
That error pops up when xcode tries to compile the .cl files. These files are usually compiled at run-time using the clCreateProgramWithSource function. You can get rid of that error by removing the .cl files from the “Compile Sources” sections of the “Build Phases” of the target. Here is what you do:
Select the Project in the Project Navigator.
Select the target.
Click on the Build Phases tab on the top.
Expand the Compile Sources section.
Select the .cl files and click the “-” button
Run your program.
That should get rid of the error.
If this fixes your problem, take a second to upvote the answer on stackoverflow
Ok the onnoyng opencl error disappear (this make me feel more optimist!!!) but there comes a lot different!
*: No such file or directory
/Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/../../../addons/MSAOpenCL/src/MSAOpenCLImagePingPong.h:17:25: error: MSAPingPong.h: No such file or directory
/Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/../../../addons/MSAOpenCL/src/MSAOpenCLImagePingPong.h:17:25: error: MSAPingPong.h: No such file or directory
/Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/../../../addons/MSAOpenCL/src/MSAOpenCLImagePingPong.h:17:25: error: MSAPingPong.h: No such file or directory
/Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/../../../addons/MSAOpenCL/examples/openFrameworks/MSAOpenCL example - hello world/src/testApp.cpp:4:22: error: MSATimer.h: No such file or directory
It seems that it can’t find the lib, but I linked all of them in my left panel.
ok I fixed all references (always read the debugger…)
now the last (hoping) error is
ld: duplicate symbol _main in /Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/build/myFirstProject.build/Debug/myFirstProject.build/Objects-normal/i386/main-9D8930C78D0D6C37.o and /Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/build/myFirstProject.build/Debug/myFirstProject.build/Objects-normal/i386/main-82227D70F1DD098B.o for architecture i386
collect2: ld returned 1 exit status
Command /Developer/usr/bin/llvm-g++-4.2 failed with exit code 1
Apple Mach-O Linker (ld) Error
Command /Developer/usr/bin/llvm-g+±4.2 failed with exit code 1
That’s a linker error, it’s telling you that there is a duplicate symbol main. There can only be 1 main function, because this is the starting point of your application. This is the error you get when you forget to remove the example projects from the addons.
Assertion failed: (err != CL_INVALID_GL_OBJECT), function initFromGLObject, file /Users/bruzzmac/Documents/LAVORI/of_preRelease_v007_osx/apps/bruzzWorkspace/MSAOpenCL Example - particles/../../../addons/MSAOpenCL/src/MSAOpenCLBuffer.cpp, line 82
xcode open the page related to the threads and it says that the program received the signal SIGABRT
ps: thank daanvanhasselt it was true, I forgot to cancel the examples from the libs!
Returns a valid non-zero OpenCL buffer object and errcode_ret is set to CL_SUCCESS if the buffer object is created successfully. Otherwise, it returns a NULL value with one of the following error values returned in errcode_ret:
…
CL_INVALID_GL_OBJECT if bufobj is not a GL buffer object or is a GL buffer object but does not have an existing data store.
…
I don’t know if this would help but memo updated his github 2 month ago: https://github.com/memo/ofxMSAOpenCL
And as it is said in the description, it is compatible with oF0072. So if you do not have this version, I would advise to try with it.
