14
edits
Tmacchant0 (talk | contribs) |
|||
(One intermediate revision by one other user not shown) | |||
Line 128: | Line 128: | ||
At this moment building of boost-python with 64 bit tool chain fails at final link stage. Using 32 bit octave 4.1.0+ for windows build of boost_python was successful | At this moment building of boost-python with 64 bit tool chain fails at final link stage. So far octave-4.1.0+ 64 bit was used. From this point we shifted to using 32 bit octave. Using 32 bit octave 4.1.0+ for windows build of boost_python was successful. | ||
==== Build Pytave ==== | ==== Build Pytave ==== | ||
Line 201: | Line 198: | ||
=== Conclusion === | === Conclusion === | ||
With some efforts, build Pytave on windows has not been completed yet. | |||
Here list of unsolved issue including boost-python are listed | |||
# libboost_python cannot be build be build on 64 bit environments | |||
# path separator handling issue in libtool (windows standard path separator \ (back slash) is ignored. | |||
# make fails at building shared library | |||
For 3, to quote Tatsuro ''A lot of _imp__ symbols errors are detected because no _imp__(symbol)s exist in object files. While object files libboost_python for threading-multi have _imp__(symbol)s in their object files. Boost does not show full compiling states. Therefore I do not know what libboost is to do.'' | |||
I too have googled extensively but haven't gotten to any solution for this problem. | I too have googled extensively but haven't gotten to any solution for this problem. |
edits