Martin Landa wrote:
> 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
> (?)
Glynn:
Okay, I'm going to hold off doing anything regarding
Windows until that gets sorted out.
(if you guys haven't already read jef's input from that osgeo4w
bug report it may be useful..)
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.
my hope was to patch up few remaining issues so we can ship a
fully featued 6.4.0 out the door now, and make it pretty later.
as the core 6.4 is quite well tested now most wingrass user
issues tend to stem from build issues, so hopefully working
from both ends complement each other.
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.
no arguement there.
Hamish
Hi,
2009/5/9 Hamish <hamish_b@yahoo.com>:
Okay, I'm going to hold off doing anything regarding
Windows until that gets sorted out.
(if you guys haven't already read jef's input from that osgeo4w
bug report it may be useful..)
personally I spent a lot of my time trying to compile and run wxGUI
vdigit on MS Windows - without success till now. And to be honest I am
going to be frustrated from that. 
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin Landa wrote:
>> Okay, I'm going to hold off doing anything regarding
>> Windows until that gets sorted out.
>
> (if you guys haven't already read jef's input from that osgeo4w
> bug report it may be useful..)
personally I spent a lot of my time trying to compile and run wxGUI
vdigit on MS Windows - without success till now. And to be honest I am
going to be frustrated from that.
FWIW, I eventually managed to get most of 7.0 to compile on Windows,
although a few bugs needed fixing. I had to upgrade make to 3.81.
r.li, r.tileset and Tcl/Tk NVIZ failed to compile.
r.li and r.tileset are known issues; r.li is Unix-specific, while
r.tileset is a bash script. I don't know what's up with NVIZ; it's
throwing up "undefined reference" errors for Tcl/Tk and OpenGL which
imply that the linker finds the import libraries but not the DLLs.
This is --without-python (I don't have SWIG installed) and
--without-wxwidgets (AFAICT, the wxWidgets and wxPython binary
packages don't work with wx-config.exe). The wxGUI works.
--
Glynn Clements <glynn@gclements.plus.com>