Victor,
When I look at the code, I don't understand how you are handling the Mac
OS, when you don't typically see so libraries, by dylibs. Can you elaborate?
Also, when I try to add --enable-config to configure, I get
configure: WARNING: unrecognized options: --enable-config
Thanks,
Partha
Hello Partha.
I'm sorry, I mean --enable-debug instead of --enable-config.
That's a good observation. In Windows I look for OpenCL.dll and in
Linux I look for libOpenCL.so, but I'm not sure how I should handle
it in MacOS. I was assuming it was the same as the Linux way. Do you
know how I should
Hi Victor,
I think on Windows for 32-bit you are OK with call OpenCL.dll, but I think
you need to call OpenCL64.dll for 64-bit?
For Mac, according to
http://developer.apple.com/library/mac/documentation/Performance/Conceptual/OpenCL_MacProgGuide/OpenCL_MacProgGuide.pdf
the sample code on page
On Fri, Feb 1, 2013 at 11:10 PM, Partha Bagchi parth...@gmail.com wrote:
Hi Victor,
I think on Windows for 32-bit you are OK with call OpenCL.dll, but I think
you need to call OpenCL64.dll for 64-bit?
I have a 64-bit Windows system and it comes with OpenCL.dll.
For Mac, according to
On Fri, Feb 1, 2013 at 8:46 PM, Victor Oliveira victormath...@gmail.comwrote:
On Fri, Feb 1, 2013 at 11:10 PM, Partha Bagchi parth...@gmail.com wrote:
Hi Victor,
I think on Windows for 32-bit you are OK with call OpenCL.dll, but I
think
you need to call OpenCL64.dll for 64-bit?
I