<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Jason,<br>
<br>
I understand all that (though not necessarily agree). Possibly part
of my reluctance stands also from the no-understanding of the degree
of potential evilness attributed to PATH changes. Remember that path
changes can be done on local profiles only or system wide but most
of all, path changes are APPENDED to previous value of PATH not
PREPEND (at least that's my experience with the Inno Setup) so it
will not disrupt any other previously program that uses dll with
same names. In the worst case what may happen is that that GDAL
install would not work due to incompatibilities with previously
installed libs. But that is essence of the dll-hell for which an
universal solution is yet to come. <br>
<br>
Joaquim<br>
<br>
<blockquote
cite="mid:03d101cbae80$ce7cbf80$6b763e80$@roberts@duke.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">Joaquim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">I hear your pain about having the space in the
name. It would probably not be too much trouble for the
installer to allow the user to change the installation
directory. That is a basic option of most installers so it
would probably not be hard to implement with a WIX-built
installer.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">But I should reiterate that a requirement of this
package is that the GDAL bindings (installed as separate
packages) must be able to locate the GDAL libraries. The one
approach mentioned so far is to put the binaries in a
well-known location. If the bindings were designed to look
for the libraries in a well-known location, they would be
broken if the user installed them to a different location.
Therefore it is important to pick a default location and
recommend that only very knowledgeable users select a
different place. My view is that adhering to Microsoft’s
best practice of using \Program Files outweighs the
convenience of using a directory off a root partition that
does not have a space in the name. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">An alternative idea is to store the location of
the GDAL libraries in the registry and then permitting them
to be installed anywhere with no consequences. The bindings
would read the registry to determine their location. This is
also a fairly standard way to do things on Windows, but it
would be slightly more complicated for the bindings.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">Jason<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;"> Joaquim Luis [<a class="moz-txt-link-freetext" href="mailto:jluis@ualg.pt">mailto:jluis@ualg.pt</a>] <br>
<b>Sent:</b> Friday, January 07, 2011 10:27 AM<br>
<b>To:</b> Jason Roberts<br>
<b>Cc:</b> 'Tamas Szekeres'; <a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<b>Subject:</b> Re: Fwd: Re: [gdal-dev] FWTools and GDAL
1.7.0<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On 07-01-2011 15:07, Jason Roberts wrote: <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif";">Tamas,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif";"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif";">WIX looks like
a great technology for building the installation package.
I’ve never used it but I took a quick look and it seems to
provide what is needed.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif";"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif";">As I understand
it, you are pondering whether it would be better to have
GDAL in Program Files\OSGeo\GDAL or in Program Files\GDAL.
Is it simply a question aesthetics or principle, in which it
seems proper to put all OSgeo projects under Program
Files\OSGeo, but there could be problems coordinating the
efforts of multiple projects to adhere to that carefully and
not mash each other’s files? If that summarizes the issue,
then I’d recommend going with the more practical, less
principled approach: put GDAL in Program Files\GDAL, and
OSGeo4W in Program Files\OSGeo4W. It could get messy if both
installers have to be able to create the Program Files\OSGeo
directory but not necessarily delete it when they are
uninstalled, because there could be another OSGeo project in
there.</span><o:p></o:p></p>
<p class="MsoNormal"><br>
Let me just recall that OSGeo4W proposes the default install
directory as C:\OSGeo4W<br>
This is just my opinion and I feel quite at rest because I'm
able to build GDAL and install it wherever I wont, but I would
really hate that an installer would force me to install in a
location contrary to my will. In particular when that location
has blanks in the name (Program Files).<br>
But, as I said it's just my private view.<br>
<br>
<br>
Joaquim<o:p></o:p></p>
</div>
</blockquote>
<br>
</body>
</html>