#570: startup problem with standalone GRASS install
-------------------------+--------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: default | Version: unspecified
Keywords: | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
please see attachments of error when the program is started with GRASS
Icon
#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: MSWindows XP | Cpu: Unspecified
---------------------------+------------------------------------------------
Changes (by hamish):
* component: default => Installation
Comment:
I expect an incompatibility with the PythonXY installation.
(ie pyXY is built without some needed library function)
can you install a secondary python install (generic 2.5) to run with
grass?
what version of pythonXY? is it supposed to be a full python install +
scientific tools, or has it dumped normal python things it thinks a
scientist won't use?
from the dos box screenshot it looks like you try with grass 6.4.0rc4.
can you translate the error messages into english for those of us too
ignorant to understand?
#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Changes (by timmie):
* cpu: Unspecified => x86-32
Comment:
> I expect an incompatibility with the PythonXY installation. (ie pyXY is
built without some needed library function)
You may have a look at the standard plugins of PythonXY here: http://www.pythonxy.com/standard.php
It's really neat for straight off installation for science.
> can you install a secondary python install (generic 2.5) to run with
grass?
Just bare Python 2.5?
I can try as long as it does not spoil my sys.path
More an more FOSS programs have python. On windows, everyone installs its
own version of python into the programs directory...
> what version of pythonXY?
latest. 2.1.12
> is it supposed to be a full python install + scientific tools,
Yes.
> or has it dumped normal python things it thinks a scientist won't use?
I don't think so.
> from the dos box screenshot it looks like you try with grass 6.4.0rc4.
Yes. from the standalone installer.
> can you translate the error messages into english for those of us too
ignorant to understand?
I will try: https://trac.osgeo.org/grass/attachment/ticket/570/bug_grass.jpg
=> prozedureinsprungspunkt: starting point of procedure
=> wurde in der DLL [...] nicht gefunden : was not found in the DLL [...]
#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by timmie):
I've just seen that GRASS also conatins a menu item for "Old Gui" very
good. I would like to see these choices (GUI, OLd GUI, command line) as
well in the OSGEO4W install...
#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by timmie):
As we suppose that this is a python import error:
I would suggest that there are axceptions with error messages added to the
points where python needs some distinct modules.
Disclaimer: I never looked at the code of the Python GUI
#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by cnielsen):
Related errors have been posted elsewhere. The path given in the error
"C:\Programs\GIS..." is from my system where I built the installer.
Somewhere this path is getting saved even when the installer is supposed
to be generic. As I mentioned in other posts, if anyone can tell me how to
fix this I will gladly do so, I'm just a packager :).
I got it fixed on my computer.
It was a problem with the win32 packages for python.
After copying them over from
c:\Programme\pythonxy\python\Lib\site-packages\win32\
c:\Programme\pythonxy\python\Lib\site-packages\win32com\
c:\Programme\pythonxy\python\Lib\site-packages\win32comext\
everything works.
The GUI is really nice and fast. congratulations to thos who made it.
Where can upload a ZIP for verification?
I would like to know whether this is specific for my setup or others may
have the same problem.
I can suppose that peaple working a lot with Python may even have 3 python
installs:
python25, python26, python3000
One small issue:
When GRASS is started from the menu shortcut, there is still an empty dos
CLI in the background.
AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably running the temp file cleaning operations at the end. So, until we have reengineered the Windows startup logic, I don't think we can get rid of it.
> When GRASS is started from the menu shortcut, there is still an empty dos
> CLI in the background.
AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably
running the temp file cleaning operations at the end. So, until we have
reengineered the Windows startup logic, I don't think we can get rid of it.
If enough users are likely to want to use the wxPython GUI as the main
interface, I'd consider adding a Python-based startup as an
alternative to grassXX[.bat] and Init.{sh,bat}.
This should be invoked via pythonw on Windows, and should redirect
std{out,err} to files. Also, if GISBASE isn't already defined, set it
from a registry key.
A command-line-only interface is of relatively little use on Windows,
due to the absence of monitors.
On Wed, May 6, 2009 at 11:58 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Moritz Lennert wrote:
> When GRASS is started from the menu shortcut, there is still an empty dos
> CLI in the background.
AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably
running the temp file cleaning operations at the end. So, until we have
reengineered the Windows startup logic, I don't think we can get rid of it.
If enough users are likely to want to use the wxPython GUI as the main
interface, I'd consider adding a Python-based startup as an
alternative to grassXX[.bat] and Init.{sh,bat}.
Yes, this would help to sort out a series of problems.
timmie wrote:
> Where can upload a ZIP for verification?
verification of what? what's in the ZIP file?
> One small issue: When GRASS is started from the menu shortcut,
> there is still an empty dos CLI in the background.
as discussed on grass-dev,
- in the OSGeo4W installer you get a grass terminal session in a dos box
using the wx gui
- in the OSGeo4W installer you get a blank dos box when using the tcltk
gui until you exit the gui when it becomes a grass terminal session (patch
in osgeo4w bug # 83 http://trac.osgeo.org/osgeo4w/ticket/83)
- in Colin's stand-alone installer the empty dos box is now minimized by
default. maybe some valuable error messages could end up there; maybe
Glynn will rewrite grass.bat into a general launch_grass.py.
Replying to [comment:17 hamish]:
> > Where can upload a ZIP for verification?
> verification of what? what's in the ZIP file?
Yes. I mean, now it works on my computer.
But I guess we need to verify if others with different python
installations are also affected.
Take the contents of the ZIP to compare what has changed.
> > One small issue: When GRASS is started from the menu shortcut,
> > there is still an empty dos CLI in the background.
Sorry, I should have written:
An empty DOS window with no command promp. Just a black window.
> - in Colin's stand-alone installer the empty dos box is now minimized
by default. maybe some valuable error messages could end up there; maybe
Glynn will rewrite grass.bat into a general launch_grass.py.
I think after my replacement of the win32* packages in the GRASS python
install, Colins minimisation doesn't work.
> - in Colin's stand-alone installer the empty dos box is now minimized
by default. maybe some valuable error messages could end up there; maybe
Glynn will rewrite grass.bat into a general launch_grass.py.
Can anyone tell me where to find a Windows version of wxPython which
works for compiling GRASS?
