On 13 Feb., 20:32, Harry van der Wolf <[email protected]> wrote:
> The other scripts don't work either. I also tried the xx3 scripts (python 3 > I suppose?) > Can I find more info about what goes wrong? It's not in the system.log It's not the scripts which aren't working, but the interface module not being loaded, because hugin doesn't know where to find it. Merely clicking on 'execute Python script' and hoping the relevant files will be found won't get you anywhere. Four days ago I posted a message explaining what I'd like you to do and why, so here it is again: On 10 Feb., 09:23, Harry van der Wolf <[email protected]> wrote: > There is a target _hsi and a shared module _hsi.so is created. I assume this > a dynamic library for a linux system. If it is a shared library, the name > should be _hsi.dylib as that's the dynamic name/extension on macosx. If I'm > wrong, nice. If I'm right the name needs to be changed. I'm not sure what extension a shared library has to have on Mac OS. I'll explain what these files are to you, and if you want a slightly more in-depth explanation about the files and how they come to be, there is a README.hsi file in the source directory. hsi.i (the interface definition file), is converted by SWIG into the files hsi.py (the high-level-interface) and hsiPYTHON_wrap.cxx (the low-level-interface). The latter is compiled into _hsi.so. When you import hsi.py into a python session, it will try and load _hsi.so. So I'd ask you to do the following: - Open a shell prompt - set your PYTHONPATH environment variable to the target directory where cmake has placed hsi.py and _hsi.so (like, type export PYTHONPATH=<whatever that path is>) - start a python interpreter session by typing 'python' - at the python prompt, type 'import hsi' after that, if all goes well, the module is loaded, and you can try stuff with it, like help(hsi) If that works, we have hsi runing, and I'd like you to report back. If it doesn't work, chances are that all that's needed is a name change of _hsi.so to whatever is appropriate for python modules on Mac OS, but I'd ask you to try with the unchanged name first. So, again, once you've established you can import hsi into a python session, we can proceed to the next step and call it from hugin. But first things first. Kay -- 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
