On Sun 29-Jan-2012 at 08:45 -0800, Kay F. Jahnke wrote:
I'll make the code available soon as a mercurial patch, but I'm not sure if everyone is happy with me introducing new dependencies. Obviously, numpy.i would be one, but the file doesn't seem to be copyrighted at all, so there seems to be no problem just putting it into the hugin source tree. But numpy.i needs access to numpy header files to know the structure of the numpy data. So the relevant numpy source has to be installed as well. I'd like some echo on this, and in case you feel I am asking too much, maybe you can propose a way to make the new code an option - like a compile-time option.
Python is already a compile-time option, so presumably a non-python build wouldn't need numpy either.
If and when Hugin switches to a current vigra library, there will be new dependencies here anyway - vigra-1.8.0 has a boost-python and numpy extension, so a future Hugin that links to this is likely to indirectly require numpy anyway.
-- Bruno -- 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
