A number of people have reported that they have had problems building the bindings. I have two ideas to bounce around:
1. Would it make sense to distribute SWIG-generated pyfprint_swig.c together with the sources? This way, we get rid of a build-time dependency on SWIG. The configure process can still check for SWIG and, if found, force regeneration of pyfprint_swig.c... 2. Would it make sense to use setup_tools to build the extension with 'python setup.py build_ext --inplace' like the SWIG documentation strongly recommends? -Artem _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
