Folks,<br><br>I'd be curious to know what would be the desired process to package specific parts of GDAL (like the various plugins or bindings) in OSGeo4w.<br>Currently the only reasonable approach I have in my mind is that all of the parts are generated from a single compilation (provided to use the same compiler and dependencies)<br>
In this regard would that be reasonable to include the actions in the corresponding <a href="http://makefile.vc">makefile.vc</a> in the GDAL source tree. For example I would be happy to maintain the csharp part in the csharp <a href="http://makefile.vc">makefile.vc</a>.<br>
We could also store the common settings (like the version information in the package names, location of the OSGeo4w installation etc.) in nmake.opt.<br><br><br>Best regards,<br><br>Tamas<br> <br><br><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>