[GRASS-windows] Re: [GRASS-user] Re: [GRASS-dev] call for
volunteers - urgent need for Windows Vista binaries
Helena Mitasova
hmitaso at unity.ncsu.edu
Tue Mar 31 00:28:15 EDT 2009
Colin,
Marco's installer has been a great success here (both on Vista and XP)
and students greatly appreciate
also the msys console that gives them lot of convenient linux tools.
So if you could rebuild the installer with GRASS64 it would be
greatly appreciated.
thanks a lot for your work,
Helena
P.S. the only issue (minor) that I had was that he re-named the
nc_spm data set to
NORTH-CAROLINA causing some confusion because the name is
different from the one used in the GRASSbook and we also have North
Carolina in other coordinate systems (nc_ll and nc_spf). But that is
just cosmetics.
On Mar 30, 2009, at 7:41 PM, Colin Nielsen wrote:
> I should have looked harder before I hit "Send", I just found Marco's
> instructions on creating the standalone installer.
> <http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/
> mswindows>
>
> 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.)
>
> -Colin
>
> On Mon, Mar 30, 2009 at 7:29 PM, Colin Nielsen
> <colin.nielsen at gmail.com> wrote:
>> Michael,
>> 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
>> solved.
>>
>> 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.
>>
>> -Colin
>>
>> 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.
>>>
>>> Michale
>>>
>>> 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>
>>>> wrote:
>>>>>
>>>>> 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
>>>>> be
>>>>> 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:
>>>> http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
>>>> -> 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.
>>>>
>>>> Markus
>>>
>>> _______________________________________________
>>> grass-user mailing list
>>> grass-user at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
More information about the grass-windows
mailing list