Thanks for the answer,<br>you replied :<br><br>I'd say yes, you have to include the VTK copyright/statement in your<br>
documentation. "Redistributions in binary form" would include<br>
statically linking to VTK libraries as you are distributing VTK object<br>
files as part of your binary.<br><br>So just to be 100% sure : the BSD license only applies to the VTK libs which <br>are no longer visible because they are statically linked in and we can write something like:<br><br>Our application links with VTK which uses the following license:<br>
<br>... license text ....<br><br><div class="gmail_quote">2009/3/18 Berk Geveci <span dir="ltr"><<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> 1. If we release an application that links with the VTK Dlls<br>
> statically , is it necessary to attach the license at all ? I am asking<br>
> this because the clauses<br>
> only refer to REDISTRIBUTION. However, we only use a statically<br>
> linked VTK and do not redistribute the dlls.<br>
> This came to my mind because the license seems to make a difference between<br>
> redistribution and usage:<br>
><br>
> Redistribution and use in source and binary forms, .....<br>
><br>
> the following list of license requirements however only refers to<br>
> REDISTRIBUTION and not to USE.<br>
<br>
</div>I'd say yes, you have to include the VTK copyright/statement in your<br>
documentation. "Redistributions in binary form" would include<br>
statically linking to VTK libraries as you are distributing VTK object<br>
files as part of your binary.<br>
<div class="im"><br>
> 2. Another question: the BSD-license will have no effect concerning the<br>
> distribution of our application.<br>
> E.g. others wont be able to use our binaries for free -- correct ?<br>
<br>
</div>It is your choice. You can distribute you application free or sell it.<br>
VTK license does not impose any conditions other than the inclusion of<br>
the copyright/license statement in your documentation.<br>
<font color="#888888"><br>
-berk<br>
</font></blockquote></div><br>