Closed makson96 closed 9 years ago
I am pretty sure this is a bug in swig: http://sourceforge.net/p/swig/bugs/1345/
I never encountered this issue on any of my machines (swig-2.0.12 and swig-2.0.10 or 2.0.8?)
Arch has 3.0.2. Could you try using 2.0.12, makson?
seems to be fixed for swig-3.0.0: https://github.com/swig/swig/commit/0e54a51c104ecf1c1a68892132d9506890a99036 swig-2.0.12: https://github.com/swig/swig/commit/5602a61bb6fa2b6de419c251fceb2e5cd499893d
the thing is, how should we handle this case? According to http://www.swig.org/Doc2.0/Python.html#Python_builtin_types it may be not good to support both ways
it also fails with python3.3
I think we will go with requiring swig-2.0.12
If worst comes to worst you could always just disable Python bindings given 3.3 or higher with a low SWIG version.
or just install a newer one
System: Xubuntu 14.04 64 bit. Command: cmake .. -DCMAKE_INSTALL_PREFIX=/home/tomek/Publiczny/Gamekeeper-Framework/install -DBUILD_PROTOTYPES=ON -DWITH_NCURSES=ON -DWITH_PYTHON_BINDINGS=ON Output:
Command: make install Error Output:
Removing "-builtin" from " Gamekeeper-Framework/src/bindings/model/python/CMakeLists.txt" solves the issue