#827: standalone-installer: execution failed on g.proj.exe -p
---------------------------+------------------------------------------------
Reporter: timmie | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Installation | Version: svn-releasebranch64
Resolution: | Keywords: wingrass
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by timmie):
> The %PATH% environment variable is the last resort for locating
libraries, so if there is a libtiff.dll in e.g. Windows or
Windows/System32, it will take precedence. The only locations which are
ahead of the Windows directories are the executable's directory (i.e.
$GISBASE/bin) and any "Side-by-Side Assemblies" specified in the program's
manifest (if it has one).
I will conform to morrow but the computer I am experiencing this has
definately a separate version of GDAL installed:
* the binaries from the website
* python bindings: http://pypi.python.org/pypi/GDAL
* the OSGEO4W files.
> We're already faced with having to create manifests to keep UAC happy,
so it would be useful if someone could read up on this stuff and figure
out how to use manifests to control searching for DLLs.
I have a lot of opensource programs installed on Windows that rely on GTK
or Python (wxPython). But all can run independatly.
Thanks for your feedback.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/827#comment:22>
GRASS GIS <http://grass.osgeo.org>