Changes between Version 4 and Version 5 of PackagingInstructions
- Timestamp:
- 01/20/09 14:59:31 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PackagingInstructions
v4 v5 72 72 One very common thing to do in postinstall actions is to insert/update configuration files to include the installed path to the OSGeo4W tree. This is normally done with a postinstall file, and here are 2 examples:: 73 73 74 == !TextReplace Example #1 ==74 == !TextReplace Example !#1 == 75 75 76 76 * hardcoded paths exist in the /httpd.d/httpd_gmap.conf file of the gmap package: … … 99 99 }}} 100 100 101 == !TextReplace Example #2 ==101 == !TextReplace Example !#2 == 102 102 103 103 {{{ … … 143 143 144 144 = Application batch file template = 145 Sample of how to start an application with standard environment set. Replace myapp.exe with your application executable and save as `mypackage.bz2:bin/myapp.bat.tmpl`145 Sample of how to start an application with standard environment set. Replace `foo.exe` with your application executable and save as `foobar.bz2:bin/foo.bat.tmpl`. [#Post-InstallActions Post-Install] will set the proper OSGEO4W_ROOT. 146 146 {{{ 147 147 @echo off … … 149 149 PATH %OSGEO4W_ROOT%\bin;%PATH% 150 150 for %%f in ("%OSGEO4W_ROOT%"\etc\ini\*.bat) do call "%%f" 151 start /B %OSGEO4W_ROOT%\bin\ myapp.exe %*151 start /B %OSGEO4W_ROOT%\bin\foo.exe %* 152 152 @echo on 153 153 }}}