This content has been marked as final. Show 5 replies
I believe you are "sorry out of luck" with this, because the shared libraries (DLLs) used by the OTFDK are specific to the version of Python headers/libraries they were compiled with (if compiled with 2.2, usable with 2.2, but not 2.3). It appears that the specific problem you have right now is that the OTFDK search paths (.pth files) were not installed properly, but even if they were, the DLL import would still fail because of the aforementioned problem.
OK, I've done "brute force" for now: I binary-patched the .pyd files from "python22.dll" to "python23.dll". Issies a warning but works :/ I hope FDK 1.7 will be 2.3-compatible!
Yes, we are in the process of upgrading to python 2.3. It is really frustrating for us as well that the executables are not backwards compatible for pyd's and slb's.
Has this situation changed in any way? I recently downloaded the FDK, Python 2.4... all sorts of things I never used before. When I try to run "python FDK.py" I get the same error message, no doubt for the same reason. I have no idea how to "brute force" anything.
No, it hasn't changed. Windows FDK libs were compiled with Python 2.2 headers. The only way to get the FDK to work is to use Python 2.2 under Windows. However, a new FDK release, updated to Python 2.4, will be out soon., 'soon' meaning early December 2005.