[GRASS-dev] GRASS GIS compilation on windows: SET OSGEO4W_ROOT=@osgeo4w@ not replaced by SET OSGEO4W_ROOT=C:\OSGeo4W64

GRASS GRASS developer
1

hi,

just tested compiling GRASS on windows; compilation works fine with the
instruction in:

https://trac.osgeo.org/grass/wiki/CompileOnWindows

but I've found in one of the last steps of installing following issue:

grass75svn.bat is copied to

C:\OSGeo4W64\bin\grass75svn.bat

the content is:

--------------------------
@echo off
rem
#########################################################################
rem #
rem # GRASS initialization bat script (OSGeo4W)
rem #
rem
#########################################################################

SET OSGEO4W_ROOT=@osgeo4w@ <=

[...]
-------------------------

comparing it with a OSGeo4W-installation:

--------------------------
@echo off
rem
#########################################################################
rem #
rem # GRASS initialization bat script (OSGeo4W)
rem #
rem
#########################################################################

SET OSGEO4W_ROOT=C:\OSGeo4W64
[...]
--------------------------

it seems @osgeo4w@ isn't replaced by C:\OSGeo4W64

any idea how to fix this?

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

2

Hi,

2018-01-06 21:27 GMT+01:00 Helmut Kudrnovsky <hellik@web.de>:

SET OSGEO4W_ROOT=@osgeo4w@ <=

[...]

SET OSGEO4W_ROOT=C:\OSGeo4W64
[...]
--------------------------

it seems @osgeo4w@ isn't replaced by C:\OSGeo4W64

any idea how to fix this?

not needed, it's done by installation process on client machine [1]
(path can differ)

Ma

[1] https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/postinstall.bat#L3

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

3

Martin Landa wrote

Hi,

2018-01-06 21:27 GMT+01:00 Helmut Kudrnovsky &lt;

hellik@

&gt;:

SET OSGEO4W_ROOT=@osgeo4w@ <=

[...]

SET OSGEO4W_ROOT=C:\OSGeo4W64
[...]
--------------------------

it seems @osgeo4w@ isn't replaced by C:\OSGeo4W64

any idea how to fix this?

not needed, it's done by installation process on client machine [1]
(path can differ)

[1]
https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/postinstall.bat#L3

don't understand it right.

when I do in msys2:

PACKAGE_POSTFIX=-daily OSGEO4W_POSTFIX=64 ./mswindows/osgeo4w/package.sh

grass75svn.bat is copied to C:\OSGeo4W64\bin\, but with this line:

SET OSGEO4W_ROOT=@osgeo4w@

when is this replaced? when is postinstall.bat launched? only when the
compiled package is uploaded to OSGeo4W and then downloaded by the
OSGeo4W-installer?

in the wiki (https://trac.osgeo.org/grass/wiki/CompileOnWindows#Usage)

---------------------
Usage

To start GRASS use the icon on the desktop or if you want to be able to use
the command line from within GRASS.

Type in the OSGeo4W cmd console (assuming that we compiled GRASS 7.1):

c:\osgeo4w\bin\grass71svn.bat
---------------------

when I do this with the self compiled C:\OSGeo4W64\bin\grass75svn.bat, then
GRASS can't be started because of the missing correct SET OSGEO4W_ROOT=....

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

4

Hi,

2018-01-06 21:59 GMT+01:00 Helmut Kudrnovsky <hellik@web.de>:

grass75svn.bat is copied to C:\OSGeo4W64\bin\, but with this line:

SET OSGEO4W_ROOT=@osgeo4w@

the process is dedicated for creating osgeo4w package.

when is this replaced? when is postinstall.bat launched? only when the
compiled package is uploaded to OSGeo4W and then downloaded by the
OSGeo4W-installer?

yes. Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

5

Hi,

2018-01-06 22:07 GMT+01:00 Martin Landa <landa.martin@gmail.com>:

the process is dedicated for creating osgeo4w package.

we could fix the local installation process (after the osgeo package
is created). Anyway, created package must contain original bat file.
Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

6

SET OSGEO4W_ROOT=@osgeo4w@

the process is dedicated for creating osgeo4w package.

ok

Anyway, created package must contain original bat file.

ok

we could fix the local installation process (after the osgeo package
is created).

if it's possible, yes.

otherwise we have to extend the wiki section.

https://trac.osgeo.org/grass/wiki/CompileOnWindows#Usage

-------------------------
Usage

To start GRASS use the icon on the desktop or if you want to be able to use
the command line from within GRASS.

Type in the OSGeo4W cmd console (assuming that we compiled GRASS 7.1):

c:\osgeo4w\bin\grass71svn.bat
------------------------

that for a local use, SET OSGEO4W_ROOT= has to be set manually.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html