[GRASS-user] Re: [GRASS-dev] call for volunteers - urgent need
for Windows Vista binaries
colin.nielsen at gmail.com
Mon Mar 30 19:41:26 EDT 2009
I should have looked harder before I hit "Send", I just found Marco's
instructions on creating the standalone installer.
If modified to the osgeo4w tree, new native installers should be
relatively easy to create. The wingrass team seems to be a little
divided right now (native, mingw/msys, osgeo4w, cygwin, not to mention
lots of different user & developer wiki pages saying different
things), is there a consensus on where to take wingrass? (I should
note that I'm relatively new to the scene and therefore may be missing
longer-term trends and discussions.)
On Mon, Mar 30, 2009 at 7:29 PM, Colin Nielsen <colin.nielsen at gmail.com> wrote:
> I have just tried r.patch, v.patch and v.what.rast on the new
> grass-6.4.svn release in osgeo4w (built on XP I assume), and haven't
> had any problems with any of them. So perhaps these issues have been
> Maybe I'm missing it somewhere in the many wiki pages, but is there a
> complete list of vista related issues for me/others to test?
> http://grass.osgeo.org/wiki/WinGRASS_Current_Status#Vista seems not to
> have been updated recently.
> My two cents: I agree that an standalone installer is vastly
> preferable to the osgeo4w format for the majority of windows users. I
> have heard that Marco is not able to continue to supply these
> installers, but did he document the steps required to create
> installers somewhere? With the osgeo4w installer allowing for quick
> compiles of new grass versions, there should be no reason why these
> can't be continued.
> On Fri, Mar 27, 2009 at 12:24 PM, Michael Barton <Michael.Barton at asu.edu> wrote:
>> Thanks Markus,
>> This will make the information more accessible.
>> On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:
>>> On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton at asu.edu>
>>>> Thanks Moritz,
>>>> I'm glad to see that this is possible at least, though it is by no means
>>>> obvious. I will try to find a place to archive this information as I will
>>>> again doing a lab course later this spring. The fact that critical
>>>> information for creating a stand-alone package is buried in a blog is
>>>> problematic--though I know that all are very pressed for time.
>>> easy to solve: I have added it here:
>>> -> Lab Installation as offline set of packages
>>> It would not harm of course to move the relevant into to that trac
>>> page rather thank linking around.
>> grass-user mailing list
>> grass-user at lists.osgeo.org
More information about the grass-dev