Hello,
Great question. My understanding of LGPL is
* for open source software where the code is openly redistributed you need to be at least LGPL as well or modularize the code into portions that can be licensed differently
* for in-house commercial software where the code is not redistributed you can do as you please
* for commercial software that is distributed you must make any change to the LGPL code available and only link dynamically so the "freedom" aspect is preserved that should allow any buyer of your software to improve the open source part on their own
For example, someone who bought QTModeler or uses QTReader should be able to replace the existing LASlib DLL with their own version in order to add multi-threading to LASzip decompression to speed up their loading files for viewing without needing to go back to the vendor. This is why any changes to the code need to be made available.
For only the LASzip DLL, however, we are happy to provide a static linking exception to allow use of the LAZ compressor and decompressor on mobile devices. Simply turn your head towards Redlands, CA (use the OSM layer in QGIS for directions) as you say three times: "Don't be evil, ESRI!" and the static linking exception for the LASzip DLL is granted ... (-;
Martin @rapidlasso
--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe