Very timely! That is precisely the reason I joined the mailing list,
Basically, all compiled okay, make, make install, and the lib went where
it is supposed to be. However, when I copy-paste the example from the
online doc, it cries out that the import is unresolved. Could that be
Thank you all for your help!
On 06/22/2010 10:17 PM, Andreas Kloeckner wrote:
On Tue, 22 Jun 2010 12:20:28 -0400, Rick Gerkin<rickg(a)cmu.edu>
>>> For the latter, all dependencies are 64-bit
>>> libraries except for MSVCR90.dll, MSVCP90.dll, the boost_python dll
>>> mentioned above, python26.dll, and the _cl.pyd I am examining. For the
>>> step in getting this to work, I don't what of all this is relevant.
>>> I abandon trying to make it work in a 64-bit OS? Has anyone ever made it
>>> work in 64-bit Windows?
>> I'm not sure I understand what you're saying here--which ones are
>> 64-bit, and which ones are 32? Wouldn't they all need to be 64-bit?
> OK, you're probably right that they should all be 64-bit. I imagine I can
> find 64-bit version of each of them, except _CL.pyd. I don't know why the
> pyOpenCl build script didn't try to build me a 64-bit version. Maybe it was
> just matching the bit-depth of its immediate dependencies (e.g.
> Python26.dll, BoostPython-VC90-MT-1.43.dll). Perhaps I should work from the
> bottom and try to get/build 64-bit dll's all the way up. Is it known
> whether anyone has built a 64-bit _CL.pyd in Windows?
As far as I know, the PyOpenCL build will try to match the Python
interpreter with which it is being built.
PyOpenCL mailing list