[GRASS-dev] [GRASS GIS] #1428: WinGRASS + how to deliver Microsoft Visual C++ Redistributable Package (vcredist)?
GRASS GIS
trac at osgeo.org
Wed Apr 17 23:42:18 PDT 2013
#1428: WinGRASS + how to deliver Microsoft Visual C++ Redistributable Package
(vcredist)?
--------------------------+-------------------------------------------------
Reporter: dhastings | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.4.3
Component: Installation | Version: 6.4.3 RCs
Keywords: wingrass | Platform: MSWindows 7
Cpu: x86-64 |
--------------------------+-------------------------------------------------
Comment(by hellik):
Replying to [comment:61 neteler]:
>
> Question: Is there a potential race condition during installation of
> DLL package while the winGRASS package already offers the "Next" button?
> Could winGRASS wait for the DLL redistribuition package installation
> to complete?
yes
from the nsis-manual
http://nsis.sourceforge.net/Docs/Chapter4.html
{{{
4.9.1.4 ExecWait
command [user_var(exit code)]
Execute the specified program and wait for the executed process to quit.
See Exec for more information. If no output variable is specified ExecWait
sets the error flag if the program executed returns a nonzero error code,
or if there is an error. If an output variable is specified, ExecWait sets
the variable with the exit code (and only sets the error flag if an error
occurs; if an error occurs the contents of the user variable are
undefined). Note, if the command could have spaces, you should put it in
quotes to delimit it from parameters. e.g.: ExecWait
'"$INSTDIR\command.exe" parameters'. If you don't put it in quotes it will
not work on Windows 9x with or without parameters.
ExecWait '"$INSTDIR\someprogram.exe"'
ExecWait '"$INSTDIR\someprogram.exe"' $0
DetailPrint "some program returned $0"
}}}
should we switch to ExecWait?
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1428#comment:62>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list