[GRASS-dev] Re: [GRASS GIS] #580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run

[GRASS GIS]

#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
---------------------------+------------------------------------------------
  Reporter:  hamish        |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect        |      Status:  new                      
  Priority:  blocker       |   Milestone:  6.4.0                    
 Component:  wxGUI         |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:  wingrass                 
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Comment (by cmbarton):

 Replying to [comment:20 glynn]:
 > Replying to [comment:16 cnielsen]:
 >
 > > However, if the gui or other modules needs a build specific version
 then this could get complicated... Is there a clear idea of which parts
 require build specific and which do not?
 >
 > The vdigit and nviz modules are compiled for a specific version of
 Python, and vdigit for a specific version of wxPython. But at present,
 neither of those modules compile on Windows.
 >
 > > Where do pywin32 and numpy fit in?
 >
 > The GUI needs numpy and pywin32, but those packages only need to be
 compatible with the system Python, not with any specific version, nor with
 wxPython.
 >
 > > Can build specific parts only be included in the installer and still
 use an external Python?
 >
 > If Python code imports a binary module, it must be running under the
 version of Python/wxPython for which the binary module was compiled. If we
 were to supply the vdigit and nviz modules in the Windows installer, the
 wxGUI would need to be run using the version of Python/wxPython for which
 those modules were built.
 >

 Suggestion for building binaries: Build with a a Python version (say
 2.5.x), supply the specific wxPython binaries, have the installer check
 for the Python version and install it if needed, have the grass startup
 script in Windows set a python path so that the needed version comes first
 for a grass session.

 Michael

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/580#comment:23>
GRASS GIS <http://grass.osgeo.org>