<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><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";}
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-reply;
font-family:"Verdana","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Tamas,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Nice job getting something out so quickly. You remind me of <a href="http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/000000/10000/8000/400/18402/18402.strip.zoom.gif">this Dilbert cartoon</a> from back in the day.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Due to various deadlines I won’t be able to look at this until Wednesday but hope to get you some comments by that time. We should probably follow through on Frank’s request for an RFC, so the design can be reviewed and approved according to the normal procedure.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>I do have one request/requirement: unattended install. It would be really great if I could include eventually include or dynamically download a copy of the GDAL msi in my own software, and then invoke msiexec to install it automatically. Can you make sure this is possible with your msi package?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>BTW, when we get to the Python bindings installer, this is another reason to build the Python bindings installer as a .msi rather than a .exe. That is possible with Python 2.5 and later.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Jason <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> gdal-dev-bounces@lists.osgeo.org [mailto:gdal-dev-bounces@lists.osgeo.org] <b>On Behalf Of </b>Tamas Szekeres<br><b>Sent:</b> Sunday, January 09, 2011 7:52 AM<br><b>To:</b> gdal-dev<br><b>Subject:</b> [gdal-dev] GDAL windows installers available<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Folks,<br><br>Upon the inspiration on the recent conversation in this topic I've put some efforts to automate the creation of a generic GDAL installer derived from the distributions available at <a href="http://vbkto.dyndns.org/sdk/">http://vbkto.dyndns.org/sdk/</a>.<br><br>Currently the following options are available from this site to install and use GDAL:<br><br>1. Download the .zip package extract it in some location and run SDKShell.bat to run the commandline tools (this is the former approach)<br>2. Use the core msi installer to install GDAL and use the installed shortcut to run the command line tools. Python users should install the python bindings installer as well.<br><br>In order to have the bindings work the location of the core files should be added to the PATH manually (this requirement will probably be removed in the future when the automatic loader approach is implemented at the bindings)<br><br>The core installer places an entry in the registry (currently in HKCU) containing the install location which will allow the loader to find the required components.<br><br>This task is not yet complete, the following issues are to be handled or reviewed in some way.<br><br>1. Side by side installation of the multiple versions is not yet supported.<br>2. Must review the license agreement (currently taken from the GDAL site)<br>3. Must review the product name<br>4. Must review the installer design<br>5. Must review the selectable features<br>6. Loader approach to be implemented for the bindings<br>7. Versioning rules should be clarified (should synchronize the registry entries among the versions)<br>8. Further fixes <br><br><br>The core installer is provided as a single <a href="http://wix.sourceforge.net/">wix</a> project file the build process is executed by the command line apps (candle.exe and light.exe). I will make the whole approach public as part to the -dev packages at <a href="http://vbkto.dyndns.org/sdk/">http://vbkto.dyndns.org/sdk/</a>. By using this addition one can easily rebuild the installer after creating a customized GDAL build.<br><br>The wix project file could also be included in GDAL source tree and a new target could be added in the gdal makefile for creating the installer (the CRT redistributable merge modules and the dependent dlls must be available during the build). Having the locations of the OSGeo4w files in place, this approach could easily generate the same installer for the OSGeo4w bundle.<br><br><br>Any testing efforts / comments / wishes are graciously accepted.<br><br>Best regards,<br><br>Tamas<o:p></o:p></p></div></body></html>