Even hi,
As was noted Mikhail works under windows on QTCreator. There is no autoconf
on window and building python bindings is not trivial.
So I wrote cmake scripts which build fine on both (Linux/windows) os.
Yes, were is some limitations on windows: cannot build swig python bindings
on debug build. This is because linker required python and all it modules
compiled with debug support. But on release build everything is OK.
So the scenario is so: Mikhail develop gnm C methods for bindings and test
them on debug build. If them works fine, than write python bindings in
separate file (i.e. gnm.i) and try to compile on release build. Than
install the bindings and test them too.
Best regards,
Dmitry
11 июля 2014 г. 22:27 пользователь Even Rouault
even.roua...@mines-paris.org написал:
Le vendredi 11 juillet 2014 20:21:36, Mikhail Gusev a écrit :
Hello everyone.
According to my plan this week I worked on automatic graph building in
GNM.
See my blog post:
http://gsoc2014gnm.blogspot.ru/2014/07/week-8-automatic-graph-building.html
I'm also still a bit blocked on python tests and bindings. I haven't
succeeded in building GDAL with python support using CMake. But I hope to
finish this the next week.
Mikhail,
why do you mention CMake ? Your tree
https://github.com/MikhanGusev/gdal/commits/trunk is based on GDAL trunk,
which uses autoconf.
Anyway, you don't even need to ask for the python bindings at configure
time.
Building them should just be a matter of :
cd swig/python
python setup.py build
And if you want to install them
* system-wide: (sudo) python setup.py install
* otherwise export PYTHONPATH=$PWD/build/lib.use_autocompletion
Even
--
Geospatial professional services
http://even.rouault.free.fr/services.html
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
