On 22 Mai, 23:58, Yuval Levy <[email protected]> wrote: > > Before I continue, let me point out the minor changes > > ... > > would you help me rephrase the above with the purpose of explaining to those > who get the tarball what has been done and what is still left to do, and how > to do it?
This probably does the trick: hsi/hpi for hugin is optional. It has to be compiled into hugin. This is done by defining BUILD_HSI=ON in the cmake command that sets up the code generation. Inside hugin's C++ code, there are some #defines that are relevant only for hsi/hpi: HUGIN_HSI - this is defined globally if hsi/hpi capability has been switched on. It is used to introduce code which is hsi/hpi-specific into files which are also part of 'plain' hugin SWIG - this is only defined when code is processed by SWIG. It's used to hide code from SWIG which it can't handle. _HSI_IGNORE_SECTION - this is only defined during the separate C- preprocessing of certain hugin header files which use a technique dubbed 'lazy metaprogramming' which SWIG can't handle. Preprocessing 'flattens' the files - it pulls in all code that is #included by them. Most of the code pulled in this way mustn't be wrapped by SWIG, so it is switched off via #ifndef _HSI_IGNORE_SECTION. 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
