Changes between Version 4 and Version 5 of PackagingInstructions


Ignore:
Timestamp:
Jan 20, 2009, 2:59:31 PM (15 years ago)
Author:
maphew
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PackagingInstructions

    v4 v5  
    7272One 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::
    7373
    74 == !TextReplace Example #1 ==
     74== !TextReplace Example !#1 ==
    7575
    7676 * hardcoded paths exist in the /httpd.d/httpd_gmap.conf file of the gmap package:
     
    9999}}}
    100100
    101 == !TextReplace Example #2 ==
     101== !TextReplace Example !#2 ==
    102102
    103103{{{
     
    143143
    144144= 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`
     145Sample 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.
    146146{{{
    147147@echo off
     
    149149PATH %OSGEO4W_ROOT%\bin;%PATH%
    150150for %%f in ("%OSGEO4W_ROOT%"\etc\ini\*.bat) do call "%%f"
    151 start /B %OSGEO4W_ROOT%\bin\myapp.exe %*
     151start /B %OSGEO4W_ROOT%\bin\foo.exe %*
    152152@echo on
    153153}}}