today I published first winGRASS builds compiled with python 2.7 and
wxPython 2.8.12.1 which has been recently introduced in OSGeo4W
framework. I have also changed a little bit extended OSGeo4W framework
for compiling GRASS. MinGW/MSys addons [1] are now copied into
`apps/msys/` [2, 3].
I would like to ask you to test winGRASS (standalone/osgeo4w),
especially daily builds for `grass64` (due to upcoming 6.4.2 release).
today I published first winGRASS builds compiled with python 2.7 and
wxPython 2.8.12.1 which has been recently introduced in OSGeo4W
framework. I have also changed a little bit extended OSGeo4W framework
for compiling GRASS. MinGW/MSys addons [1] are now copied into
`apps/msys/` [2, 3].
I would like to ask you to test winGRASS (standalone/osgeo4w),
especially daily builds for `grass64` (due to upcoming 6.4.2 release).
does this mean that I have to reorganize my etablished and working
wingrass-build-environment?
unfortunately yes.
can you please elaborate the rationale behind this change a little bit?
All installed extension [1,2] are msys related not related to
`osgeo4w` framework itself, so they should go to `apps/msys` rather to
the the osgeo4w root directory. This make things more clear.