Glynn:
> > Can anyone tell me where to find a Windows version of wxPython
> > which works for compiling GRASS?
Martin wrote:
> do you mean for compiling extensions like vdigit or nviz? If so, I
> don't know ... It's possible to compile the extensions with wxPython
> from osgeo4w, but loading fails due to the swig-related errors.
Glynn:
I mean "configure --with-python --with-wxwidgets=...".
ie where to find the wx-config program? I've filed a ticket with osgeo4w,
hopefully it's not noise.
http://trac.osgeo.org/osgeo4w/ticket/85
Hamish
Hi,
2009/5/8 Hamish <hamish_b@yahoo.com>:
I mean "configure --with-python --with-wxwidgets=...".
ie where to find the wx-config program? I've filed a ticket with osgeo4w,
hopefully it's not noise.
http://trac.osgeo.org/osgeo4w/ticket/85
wx-config is not part of the OSGeo4w wxPython package. Probably you
need to compile your own wxPython using mingw. Also python-config is
missing. Question: do we need python-config? wxGUI extensions are
build using setup.py. So --with-python could check only if 'python'
binaries are available (?)
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin Landa wrote:
>> I mean "configure --with-python --with-wxwidgets=...".
>
> ie where to find the wx-config program? I've filed a ticket with osgeo4w,
> hopefully it's not noise.
>
> http://trac.osgeo.org/osgeo4w/ticket/85
wx-config is not part of the OSGeo4w wxPython package. Probably you
need to compile your own wxPython using mingw. Also python-config is
missing. Question: do we need python-config? wxGUI extensions are
build using setup.py. So --with-python could check only if 'python'
binaries are available (?)
Okay, I'm going to hold off doing anything regarding Windows until
that gets sorted out.
Ultimately, one of the biggest problems facing the Windows version is
that it's *still* a major hassle to compile GRASS on Windows.
Anyone interested in having GRASS work well on Windows would be well
advised to spend less time worrying about end users, and spend more
time making life easy for developers.
Otherwise, we're going to remain stuck in the situation where, at any
given time, at most one person has the ability to compile GRASS on
Windows, that one person spends their time focusing on end users, but
they eventually get fed up and quit because they're having to do it
all themselves.
--
Glynn Clements <glynn@gclements.plus.com>
Hi,
2009/5/8 Glynn Clements <glynn@gclements.plus.com>:
wx-config is not part of the OSGeo4w wxPython package. Probably you
need to compile your own wxPython using mingw. Also python-config is
Ultimately, one of the biggest problems facing the Windows version is
that it's *still* a major hassle to compile GRASS on Windows.
Anyone interested in having GRASS work well on Windows would be well
advised to spend less time worrying about end users, and spend more
time making life easy for developers.
Agreed.
missing. Question: do we need python-config? wxGUI extensions are
build using setup.py. So --with-python could check only if 'python'
binaries are available (?)
to the question: any objection to make python-config checking
optional? So --with-python will check if python binaries are available
and optionally also python-config.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin Landa wrote:
>> missing. Question: do we need python-config? wxGUI extensions are
>> build using setup.py. So --with-python could check only if 'python'
>> binaries are available (?)
to the question: any objection to make python-config checking
optional? So --with-python will check if python binaries are available
and optionally also python-config.
Whatever works, really.
Preferably, whatever works with the wxPython binary packages from
wxpython.org, rather than requiring a GRASS-specific version.
--
Glynn Clements <glynn@gclements.plus.com>
Hi,
2009/5/9 Glynn Clements <glynn@gclements.plus.com>:
to the question: any objection to make python-config checking
optional? So --with-python will check if python binaries are available
and optionally also python-config.
Whatever works, really.
Preferably, whatever works with the wxPython binary packages from
wxpython.org, rather than requiring a GRASS-specific version.
OK, done in r37060.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin Landa wrote:
>> to the question: any objection to make python-config checking
>> optional? So --with-python will check if python binaries are available
>> and optionally also python-config.
>
> Whatever works, really.
>
> Preferably, whatever works with the wxPython binary packages from
> wxpython.org, rather than requiring a GRASS-specific version.
OK, done in r37060.
Er, I think I misread "python-config" as "wx-config".
While this change is reasonable enough in itself, it doesn't help with
the issue of needing a working wx-config program in order to build the
extensions.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn Clements wrote:
> >> to the question: any objection to make python-config checking
> >> optional? So --with-python will check if python binaries are available
> >> and optionally also python-config.
> >
> > Whatever works, really.
> >
> > Preferably, whatever works with the wxPython binary packages from
> > wxpython.org, rather than requiring a GRASS-specific version.
>
> OK, done in r37060.
Er, I think I misread "python-config" as "wx-config".
While this change is reasonable enough in itself,
Actually, I take that back. The SWIG wrappers need PYTHON_CFLAGS etc,
so configure should generate a fatal error if --with-python is given
but python-config can't be found. Either that, or configure needs to
get this information from setup.py.
--
Glynn Clements <glynn@gclements.plus.com>
Hi,
2009/5/9 Glynn Clements <glynn@gclements.plus.com>:
[...]
> OK, done in r37060.
Er, I think I misread "python-config" as "wx-config".
While this change is reasonable enough in itself,
Actually, I take that back. The SWIG wrappers need PYTHON_CFLAGS etc,
so configure should generate a fatal error if --with-python is given
but python-config can't be found. Either that, or configure needs to
get this information from setup.py.
Probably SWIG wrappers should be also build with setup.py...
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa