<br><br><div class="gmail_quote">2012/3/27 Vincent Picavet <span dir="ltr"><<a href="mailto:vincent.ml@oslandia.com">vincent.ml@oslandia.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div class="im"><br>
> In osgeo4w the gdal-ecw DLLs are released binary compiled. I never needed<br>
> to compile them by myself. Are you saying that osgeo4w is doing something<br>
> incorrect?<br>
<br>
</div>The gdal/ecw case is particularly complex, as the ECW licence changes<br>
regularly and is some kind of opensource but not really.<br>
<br>
As for YOUR specific case, I think you should have understood by now that it's<br>
not possible to use Arcgis inside a python plugin, whatever the energy you<br>
deploy to try to convince the world to the opposite.<br></blockquote><div><br></div><div>I don't want to convince anyone vincent :)</div><div>I'm just exploring the various corner cases to understand precisely what can be done and what not.</div>
<div>It simply sounds strange to me that, somehow, ECW closed source code can arrive into the QGis process space. It means there's a hole somewhere. Ok, ECW releases the headers as open source, but the underlying SDK algorithms and data structures aren't. </div>
<div>It follows that SOMEHOW some proprietary code can "infect" the purity of the QGis process.</div><div>You can give me all the reasons, but I suppose that if it happens for ECW it can be reproduced, SOMEHOW, for anything else.</div>
<div><br></div><div>For my plugin I already have decided what to do. This is a general question now. If a Qgis user can leavarage a proprietary algorithm (ECW), anyway it happens, it can happen again :)</div><div><br></div>
<div>giovanni</div></div><br>