[GRASS-dev] Re: [GRASS GIS] #1178: WinGrass: g.extension - problem with path to $GISBASE

GRASS GIS trac at osgeo.org
Fri Oct 1 14:49:55 EDT 2010


#1178: WinGrass: g.extension - problem with path to $GISBASE
---------------------------------------------------------------+------------
 Reporter:  hellik                                             |       Owner:  grass-dev@…              
     Type:  defect                                             |      Status:  new                      
 Priority:  major                                              |   Milestone:  6.4.1                    
Component:  Installation                                       |     Version:  svn-releasebranch64      
 Keywords:  wingrass, g.extension, path, installation, addons  |    Platform:  MSWindows Vista          
      Cpu:  x86-32                                             |  
---------------------------------------------------------------+------------

Comment(by hellik):

 Replying to [comment:13 hamish]:
 > > The answer will be in our own archives from 6 months ago or so..
 >
 >
 > two batch file leads to get 8.3 shortened path names:
 >
 >  dir /x
 > and
 >  %~sX
 >
 > see #629 comment 3, and
 >
 > http://old.nabble.com/make-target---dependency-names-with-spaces-
 td22997327.html
 >
 http://sourceforge.net/tracker/index.php?func=detail&aid=1087569&group_id=2435&atid=202435
 >
 >
 > Hamish

 I've searched a little bit through the wingrass-nsis-code.

 getting the short name of the installation path is already there:
 (https://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows
 /GRASS-Installer.nsi#L804)

 {{{
 ;Get the short form of the install path (to allow for paths with spaces)
 VAR /GLOBAL INST_DIR_SHORT
 GetFullPathName /SHORT $INST_DIR_SHORT $INSTALL_DIR
 }}}

 so maybe this can be used? where could this be included and as which
 variable?

 Helmut

 p.s. noted that this is a statical approach, but at the moment it's a
 chance to test g.extension in wingrass. later on - after testing
 g.extension - it could be changed into a dynamically approach as described
 in comment:7

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



More information about the grass-dev mailing list