Hi Kay the versions should match. Python 2.7 (includes, libs, dll installed with same package, no other version installed) Python 2.7 is compiled with MSVC9, as I compile my hugin version
Sorry, I was not successful to provide a backtrace. When running Hugin with debug the import of the module fails (paths were modified, so it should find the module). So the script is never executed. > A common problem when using SWIG on Windows are the Microsoft > function calling conventions which are not in the C++ standard. SWIG > parses ISO C/C++ so cannot deal with proprietary conventions such as > __declspec(dllimport), __stdcall etc. There is a Windows interface > file, windows.i, to deal with these calling conventions though. The > file also contains typemaps for handling commonly used Windows > specific types such as __int64, BOOL , DWORD etc. Include it like you > would any other interface file, for example: > > %include <windows.i> > > __declspec(dllexport) ULONG __stdcall foo(DWORD, __int32);" > I will try it. Thomas -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
