As soon as I find a minute for it, I will publish my experience on a wiki
page (where? I will see...). The pages from SAGA to build it under Windows
are a bit outdated, respect to the src contents. I will ask Conrad if it's
possible to update them. In this case I can remove mine.
giovanni
On Wed, Apr 13, 2011 at 5:21 AM, G. Allegri gioha...@gmail.com wrote:
As soon as I find a minute for it, I will publish my experience on a wiki
page (where? I will see...).
Add it to the same wiki at github if you want.
On an unrelated note: Do you know if a particular python version is
On an unrelated note: Do you know if a particular python version is
defined as target for QGIS plugins? I believe I read 2.3 somewhere,
but can't find the source.
I don't remember about a reference version. The Python libs shipped with
Osgeo4w come from Python 2.5.2
Camilo
2011/4/13 G. Allegri gioha...@gmail.com
On an unrelated note: Do you know if a particular python version is
defined as target for QGIS plugins? I believe I read 2.3 somewhere,
but can't find the source.
I don't remember about a reference version. The Python libs shipped with
Osgeo4w come
Hi Camilo.
Could you please start a wiki page, accumulating the info so far?
Thanks.
Sure.
I had stated to keep links (to APIs, forum threads, etc.) and some notes here:
http://github.com/polymeris/qgis/wiki
I can move some of that to the QGIS wiki and add the info I find in
the threads. Is
Il giorno mar, 12/04/2011 alle 04.05 -0300, Camilo Polymeris ha scritto:
http://github.com/polymeris/qgis/wiki
I can move some of that to the QGIS wiki and add the info I find in
the threads. Is that what you mean?
If so, an admin would have to create an account for me.
Else, I can
I've just realized that QGis uses Python 2.5, and it isn't possible (at
least, straightforward/recomended) to build Python 2.5 extensions with VS
2008 (because Py 2.5 for Windows is being built with VS 2003).
A solution is the use of MinGW... or recompile Qgis's Python support for
version 2.6.
Just for the record, under linux I had to pass the following options
to the configure script:
--enable-python
--enable-unicode
The first is to build the python modules (could be done by hand, too).
The second forces saga to use unicode, so it matches debian's wx
packages.
No problems otherwise,
Il giorno lun, 11/04/2011 alle 18.48 -0300, Camilo Polymeris ha
scritto:
Just for the record, under linux I had to pass the following options
to the configure script:
--enable-python
--enable-unicode
The first is to build the python modules (could be done by hand, too).
The second
