On Fri, Feb 1, 2013 at 8:46 PM, Victor Oliveira <victormath...@gmail.com>wrote:
> 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. > OK, I could be wrong, but I have an nvidia card on my windows machine and seem to remember seeing opencl64.dll. I don't have it handy this weekend, but I will check when I am back on that machine. > > > For Mac, according to > > > http://developer.apple.com/library/mac/documentation/Performance/Conceptual/OpenCL_MacProgGuide/OpenCL_MacProgGuide.pdf > > > > the sample code on page 17, says: > > > > // This include pulls in everything you need to develop with OpenCL on > OS X > > v10.7. > > #include <OpenCL/opencl.h> > > > > To compile from the command line, I think you need to do have -framework > > OpenCL during compilation. > > > > For instance, > > > > gcc -framework OpenCL filein.c -o filein > > > > Can we test this out? > > > > The problem is, I don't have a machine with MacOS :/ > > I do. :) Happy to test out any code you want me to. > > Thanks, > > Partha > > > > > > On Fri, Feb 1, 2013 at 7:30 PM, Victor Oliveira <victormath...@gmail.com > > > > wrote: > >> > >> 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 do this? > >> > >> Victor > >> > >> On Fri, Feb 1, 2013 at 8:10 PM, Partha Bagchi <parth...@gmail.com> > wrote: > >> > 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 > >> > > >> > > >> > > >> > > >> > On Tue, Jan 29, 2013 at 12:32 PM, Victor Oliveira > >> > <victormath...@gmail.com> > >> > wrote: > >> >> > >> >> yes, > >> >> > >> >> export GEGL_ENABLE_OPENCL=yes > >> >> > >> >> also, when you build GEGL, put the option --enable-config. > >> >> with that you can set: > >> >> > >> >> export GEGL_DEBUG=opencl > >> >> > >> >> so you can see if OpenCL is really being used or if there is some > bug. > >> >> > >> >> Victor > >> >> > >> >> On Tue, Jan 29, 2013 at 11:31 AM, Paka <ptilopt...@gmail.com> wrote: > >> >> > * Victor Oliveira <victormath...@gmail.com> [01-29-13 07:39]: > >> >> >> You can use OpenCL in the CPU, just install the AMD OpenCL SDK. > GEGL > >> >> >> looks for libOpenCL.so in /usr/lib. > >> >> >> > >> >> >> You should use GEGL_ENABLE_OPENCL=yes > >> >> > > >> >> > export as environment varible or ?? > >> >> > > >> >> > tks, > >> >> > -- > >> >> > (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # > >> >> > US1244711 > >> >> > http://wahoo.no-ip.org Photo Album: > >> >> > http://wahoo.no-ip.org/gallery2 > >> >> > http://en.opensuse.org openSUSE > Community > >> >> > Member > >> >> > Registered Linux User #207535 @ > >> >> > http://linuxcounter.net > >> >> > _______________________________________________ > >> >> > gimp-developer-list mailing list > >> >> > gimp-developer-list@gnome.org > >> >> > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > >> >> _______________________________________________ > >> >> gimp-developer-list mailing list > >> >> gimp-developer-list@gnome.org > >> >> https://mail.gnome.org/mailman/listinfo/gimp-developer-list > >> > > >> > > > > > >
_______________________________________________ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
