Re: [GRASS-user] Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

[Michael Barton]

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 > 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-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-user] Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

[Markus Neteler]

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton  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-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #537: g.proj.exe crashes on Windows Vista (osgeo4w)

[GRASS GIS]

#537: g.proj.exe crashes on Windows Vista (osgeo4w)
--+-
  Reporter:  giohappy |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  closed   
  Priority:  major|   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:  fixed|Keywords:  osgeo4w g.proj gdal  
  Platform:  MSWindows Vista  | Cpu:  x86-32   
--+-
Changes (by giohappy):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 Perfect! Just tested.

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

[Michael Barton]

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.  
What happens is you want to do 2 separate stand alone packages? Do the  
libraries conflict? I'm just not well enough versed (i.e., ignorant)  
in Windows, and especially Vista, to know about this.


Michael


On Mar 27, 2009, at 2:27 AM, Moritz Lennert wrote:


On 27/03/09 07:18, Michael Barton wrote:
Also, while the osteo4w installer is nice for individual installs,  
it is problematic for institutional lab installs, where IT managers  
want to have stand alone apps that they can test, install, and  
remove rather than a suite of apps in a package installer format.  
It's the same problem I've face with the Cygwin version when trying  
to use GRASS in university classroom labs. It would help to have  
the option to install a package as stand alone.


Creating such standalone packages should not be too hard using  
osgeo4w as a starting point. See


http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall
("How do I perform an offline or computer lab install?")

and the blog referenced there:
http://blog.qgis.org/node/124

Moritz


___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #537: g.proj.exe crashes on Windows Vista (osgeo4w)

[GRASS GIS]

#537: g.proj.exe crashes on Windows Vista (osgeo4w)
--+-
  Reporter:  giohappy |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  reopened 
  Priority:  major|   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  osgeo4w g.proj gdal  
  Platform:  MSWindows Vista  | Cpu:  x86-32   
--+-
Comment (by neteler):

 For the record: r36484 (trunk), r36483 (6.5) and r36482 (6.4)

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[Markus Neteler]

On Fri, Mar 27, 2009 at 3:05 PM, G. Allegri  wrote:
> Thanks Jef. So, fixing the memory issues in grass code isn't
> avoidable.

I think that several developer are willing to help here once understood
the problems which means...

> I'll go on with this (after g.proj, db binaries, v.in.ogr, etc.),

... cycle through all these problems and fix one after the other.
g.proj is already done thanks to Paul.

Please send a concrete list, ideally with debug output.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[G. Allegri]

Thanks Jef. So, fixing the memory issues in grass code isn't
avoidable. I'll go on with this (after g.proj, db binaries, v.in.ogr,
etc.), because probably this will solve the problems that users are
facing from within QGis (various crashes when using the grass plugin).
So the real limitation for the end-user, is the possibility to use the
complete wxgui (digitizer, nviz), but as Martin is working on this I
think this isn't an issue.

The build system is not strict for the end-users collegues: "I want it
to work, I don't care how they made it!". This is my boss phrase :)

2009/3/27 Jürgen E. :
> Hi Giovanni,
>
> On Fri, 27. Mar 2009 at 12:36:43 +0100, G. Allegri wrote:
>>  the problem on mixing MSVC and MinGW built things (at C level) is
>> just a problem of a clean memory management (malloc/free). So, my
>> question is: would changing the build system (GNU make -> cmake) solve
>> this? Or they're unrelated things?
>
> Unrelated.
>
> If everything is compile with the same compiler (ie. using the same
> runtime library), that will make the problems disappear again.
>
> But that's not even true for all the VC built binaries in OSGeo4W (e.g.
> QGIS and Qt are build with Visual C++ 2008 Express Edition, while GDAL
> and python are built with VC 7.1 - I think).
>
> AFAICS there's no way around fixing that in GRASS for OSGeo4W.
>
> The build system currently doesn't support VC at all.  I didn't
> investigate how intensive it would be to add that to the existing
> Makefile, but that might be an option, too.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer         norBIT GmbH               Tel. +49-4931-918175-20
> Dipl.-Inf. (FH)           Rheinstraße 13            Fax. +49-4931-918175-50
> Software Engineer         D-26506 Norden               http://www.norbit.de
>
> --
> norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
> Rheinstrasse 13, 26506 Norden
> GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[Jürgen E . Fischer]

Hi Giovanni,

On Fri, 27. Mar 2009 at 12:36:43 +0100, G. Allegri wrote:
>  the problem on mixing MSVC and MinGW built things (at C level) is
> just a problem of a clean memory management (malloc/free). So, my
> question is: would changing the build system (GNU make -> cmake) solve
> this? Or they're unrelated things?

Unrelated.

If everything is compile with the same compiler (ie. using the same
runtime library), that will make the problems disappear again.

But that's not even true for all the VC built binaries in OSGeo4W (e.g.
QGIS and Qt are build with Visual C++ 2008 Express Edition, while GDAL
and python are built with VC 7.1 - I think).

AFAICS there's no way around fixing that in GRASS for OSGeo4W.

The build system currently doesn't support VC at all.  I didn't
investigate how intensive it would be to add that to the existing
Makefile, but that might be an option, too.


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-20
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de

-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[G. Allegri]

Anyway, IIUC Glynn and Jurgen:

 the problem on mixing MSVC and MinGW built things (at C level) is
just a problem of a clean memory management (malloc/free). So, my
question is: would changing the build system (GNU make -> cmake) solve
this? Or they're unrelated things?

2009/3/27 G. Allegri :
> Ok Markus. I'm sorry for pressing... My hope is to do not have a
> broken community around this issues. I would like to come to a common
> thought, and work for a coherent and clear roadmap. Probably it's me
> (and the users) that don't have it clear, while it is for all of the
> developers: who is doing what and in which direction?
>
> From an old Qgis log, Frank has explained that his dream is to have
> everything coherently packaged under osgeo4w, and hopefully to be able
> to extract standalone builds from it  (ie, qgis, grass, qgis+grass).
> This viewsight probably would be the best from the users point of
> view. The best would be to have osgeo4w setup, and standalone NSI
> installers... but I'm talking with no experience on what this would
> require, or if it's possible.
>
> I hope the discussion will go on.
>
>
> 2009/3/27 Moritz Lennert :
>> On 27/03/09 10:30, G. Allegri wrote:
>>  >  In any case the questions remain:
>>>
>>>  1 -  continue to build grass with MingW?
>>>      1a: build it against MinGW built libs (not osgeo4w)?
>>>      1b: build it against vc built libs (osgeo4w)?
>>>
>>> 2 - build Qgis with vc (osgeo4w) and solve the bindings problems with
>>> Grass: 1a or 1b?
>>
>> IIUC what Markus and Glynn are trying to get at: these questions seem to be
>> a bit quick without having clarified where the problem actually lies. Is it
>> with the GRASS source code, is it with the choice of build system or is it
>> with the osgeo4w tool chain. Jürgen says it's mainly the choice of
>> configure/make which is at stake, Glynn seems to contest that. So before we
>> haven't clearly identified where the problems actually lie, we cannot answer
>> the above questions.
>>
>> Moritz
>>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

[Doug_Newcomb]

Jachym,

I have to echo what Michael is saying about the Windows installer.  In a
government enterprise environment, I doubt the present osgeo installation
format would be accepted.  A stand-alone msi package would be better.

Another question with the osgeo installer, would the installation of the
support libraries/utilites ( python, gdal, etc.) conflict with an existing
installation of ArcGIS and it's libraries?   I'm trying to get folks who
already use ArcGIS to try doing some things in GRASS.

The combination of an unfamiliar installation package and conflicts with
their existing software would increase the resistance to initial use.

Doug


Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newc...@fws.gov
-

The opinions I express are my own and are not representative of the
official policy of the U.S.Fish and Wildlife Service or Dept. of Interior.
Life is too short for undocumented, proprietary data formats.


   
 Michael Barton
 To
 Sent by:  Jachym Cepicky  
 grass-dev-bounces   
 @lists.osgeo.org   cc
   grass-user grass-user   
   , GRASS
 03/27/2009 02:18  developers list 
 AM 
   Subject
   Re: [GRASS-dev] call for volunteers
   - urgent need for Windows Vista 
   binaries
   
   
   
   
   
   






On Mar 26, 2009, at 10:21 PM, Jachym Cepicky wrote:

> hi, just small note:
>
> On Thu, Mar 26, 2009 at 12:21:55PM -0700, Michael Barton wrote:
>> Marco Pasetti made a very nice Windows installer for 6.3 last year,
>> but
>> is unable to continue this work.
>>
>> Other folks in OSGEO have created OSGEO4W with a number of packages.
>> However, GRASS is in the 'advanced' section--and it is not clear what
>> libraries need to be downloaded with it--and it cannot be installed
>> stand-alone.
>>
>
> the osgeo4w installer is just fine, only thing is missing is, that
> GRASS
> should appear in the 'basic' section as well (should not be that
> complicated) and all depandances are fixed. than the installation is
> IMHO enough straight forward and easy.
>
> jachym

Jachym,

The osgeo4w installer does not work well with Vista. The binary seems
to have been compiled for XP and so various modules fail when GRASS
installed is installed in this way on Vista. There needs to be a Vista
version of the installer

Also, while the osteo4w installer is nice for individual installs, it
is problematic for institutional lab installs, where IT managers want
to have stand alone apps that they can test, install, and remove
rather than a suite of apps in a package installer format. It's the
same problem I've face with the Cygwin version when trying to use
GRASS in university classroom labs. It would help to have the option
to install a package as stand alone.

Michael

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
<><><>___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[G. Allegri]

Ok Markus. I'm sorry for pressing... My hope is to do not have a
broken community around this issues. I would like to come to a common
thought, and work for a coherent and clear roadmap. Probably it's me
(and the users) that don't have it clear, while it is for all of the
developers: who is doing what and in which direction?

>From an old Qgis log, Frank has explained that his dream is to have
everything coherently packaged under osgeo4w, and hopefully to be able
to extract standalone builds from it  (ie, qgis, grass, qgis+grass).
This viewsight probably would be the best from the users point of
view. The best would be to have osgeo4w setup, and standalone NSI
installers... but I'm talking with no experience on what this would
require, or if it's possible.

I hope the discussion will go on.


2009/3/27 Moritz Lennert :
> On 27/03/09 10:30, G. Allegri wrote:
>  >  In any case the questions remain:
>>
>>  1 -  continue to build grass with MingW?
>>      1a: build it against MinGW built libs (not osgeo4w)?
>>      1b: build it against vc built libs (osgeo4w)?
>>
>> 2 - build Qgis with vc (osgeo4w) and solve the bindings problems with
>> Grass: 1a or 1b?
>
> IIUC what Markus and Glynn are trying to get at: these questions seem to be
> a bit quick without having clarified where the problem actually lies. Is it
> with the GRASS source code, is it with the choice of build system or is it
> with the osgeo4w tool chain. Jürgen says it's mainly the choice of
> configure/make which is at stake, Glynn seems to contest that. So before we
> haven't clearly identified where the problems actually lie, we cannot answer
> the above questions.
>
> Moritz
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[Moritz Lennert]

On 27/03/09 10:30, G. Allegri wrote:
 >  In any case the questions remain:


 1 -  continue to build grass with MingW?
  1a: build it against MinGW built libs (not osgeo4w)?
  1b: build it against vc built libs (osgeo4w)?

2 - build Qgis with vc (osgeo4w) and solve the bindings problems with
Grass: 1a or 1b?


IIUC what Markus and Glynn are trying to get at: these questions seem to 
be a bit quick without having clarified where the problem actually lies. 
Is it with the GRASS source code, is it with the choice of build system 
or is it with the osgeo4w tool chain. Jürgen says it's mainly the choice 
of configure/make which is at stake, Glynn seems to contest that. So 
before we haven't clearly identified where the problems actually lie, we 
cannot answer the above questions.


Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-windows] windows qgis-grass: make grass build with vc or keep a separate qgis-grass mingw build?

[G. Allegri]

> I am not aware of any postings in this regard from Marco.
> Please point us to that to better understand the issues he found.

I've just asked him if he can partecipate to the discussion to explain this...

> Question: Did you try to update the installer from Marco? Maybe
> it works out of the box with a few minor tweaks? It is in the
> mswindows/ directory in the source code.

No problems with mingw build. I've already built grass6_devel from
scratch, and it almost works (better then the one I've built against
osgeo4w libs):

 1 - wxdigit and wxnviz don't work, but I know that Martin is working
on this right now
 2 - Marco told me that there soudl be made some changes to update the
build system. I still have to dig in this, but there are reasons to
hope that Marco, maybe, will find some time to work on this...
 3 -qgis bindings. With osgeo4w, on windows Vista, qgis crashes
whatever you try to do with the plugin: db.exe returns and makes Qgis
crash. I don't know yet if it's the same problem with memory
management or what else.

 In any case the questions remain:

 1 -  continue to build grass with MingW?
  1a: build it against MinGW built libs (not osgeo4w)?
  1b: build it against vc built libs (osgeo4w)?

2 - build Qgis with vc (osgeo4w) and solve the bindings problems with
Grass: 1a or 1b?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

[Moritz Lennert]

On 27/03/09 07:18, Michael Barton wrote:
Also, while the osteo4w installer is nice for individual installs, it is 
problematic for institutional lab installs, where IT managers want to 
have stand alone apps that they can test, install, and remove rather 
than a suite of apps in a package installer format. It's the same 
problem I've face with the Cygwin version when trying to use GRASS in 
university classroom labs. It would help to have the option to install a 
package as stand alone.


Creating such standalone packages should not be too hard using osgeo4w 
as a starting point. See


http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall
("How do I perform an offline or computer lab install?")

and the blog referenced there:
http://blog.qgis.org/node/124

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev