Hi Sebastian, OTB's license is a string copyleft one. That means that any software using OTB has to be distributed under OTB's license.
So there is no license trouble as far as I understand, since: 1. You are allowed to link together OTB with BSD licensed software 2. You can distribute the resulting software under OTB's licence However, if you want to distribute the resulting product with a non-copyleft license (i.e. BDS, Apache, MIT) you can't use OTB (or any other GPL-like licensed product for that matter). Jordi Sebastian Wirkert wrote: > Hi everyone, > > I recently started my PhD in multi-spectral imaging, albeit not in remote > sensing but in endoscopy (medicine). The OTB offers a lot of useful stuff > (FastICA, endmember estimation, PAN-sharpening, ...) out of the box which > could be incredibly helpful for my theses. > An additional plus is that MITK <http://www.mitk.org/>, the software > platform for which I develop, is also based on itk 4 so it fits well in our > framework. > My main question now is: if I integrate OTB into the MITK superbuild, will > this generate license troubles? MITK uses a free BSD style > <http://www.mitk.org/License> license. > > Best regards and thanks for your help! > Sebastian -- -- Check the OTB FAQ at http://www.orfeo-toolbox.org/FAQ.html You received this message because you are subscribed to the Google Groups "otb-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/otb-users?hl=en --- You received this message because you are subscribed to the Google Groups "otb-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
