And this time to the list (like I meant to.) On 19/11/2012, at 11:29 , Ramon Andiñach wrote:
> On 19/11/2012, at 2:11, Jürgen E. Fischer <j...@norbit.de> wrote: > > Hi Jürgen, > Thanks for your answers. > >> Hi Ramon, >> >> On Fri, 16. Nov 2012 at 18:52:38 +0800, Ramon Andiñach wrote: >>> b) Because the linux and mac gdal installs use the 3.3 SDK source .ecw >>> support will continue in the current manner on those platforms? >> >> That won't change. From source nothing changes. It's just that you need to >> build the gdal ecw plugin to get ECW support and you need the SDK for that - >> and that's the same as on Windows and Linux. >> >> For debian for instance there's also no ecw binary - the available package >> that >> has a script that builds the plugin for you, if you tell where you SDK is. > > Ok. So if a windows user gets adventurous and decided to build the SDK and > ecw plugin (from the source) themselves will the OSGeo4w gdal be able to use > it? > > Or will this necessitate a gdal recompile? > >>> c) Does anyone have an set of 3.3 dlls lying around somewhere? >> >> Those won't help as they are probably not build with VC10 and are therefore >> incompatible with the GDAL build (interface ECW<=>GDAL is C++; so unlike C >> the >> ABI is an issue). > > Ok. I misunderstood. > >>> d) If ECW support is disappearing from the osgeo4w packages (and so also the >>> 2.0 standalone when that happens) can it be made abundantly clear (in a >>> visible to average user sort of way)? >> >> In OSGeo4W the ecw package was already tagged obsolete. For the standalone >> we >> could add a big fat notice... > > A *really* big fat notice. > > Are the gdal-ecw for older gdal versions going to remain visible in the > installer? > (I can see someone trying one of those in an attempt to restore ecw > functionality.) > > Apologies if I'm sounding thick. > -ramon. _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
