Adding hints to dual-style selective license between Apache License and GPL...

Adding hints to dual-style selective license between Apache License and GPL (depending on configuration)
parent 2d706e45
......@@ -208,12 +208,12 @@
<tr>
<td><b>ITABase</b> <br /> <i>(ITACoreLibs component)</i></td>
<td><i>none</i></td>
<td>libsamplerate <br /> libsndfile <br /> pcre and pcrecpp <br /> SPLINE <br /> IPP [optional] <br /> SimpleINI (in source) </br> pthreads (POSIX only)</td>
<td>libsamplerate <br /> libsndfile <br /> pcre and pcrecpp <br /> SPLINE <br /> IPP [optional, problematic license] <br /> SimpleINI (in source) </br> pthreads (POSIX only)</td>
</tr>
<tr>
<td><b>ITAFFT</b> <br /> <i>(ITACoreLibs component)</i></td>
<td>ITABase</td>
<td>FFTW3 [optional, but recommended] <br /> MKL [optional] <br /> FFTS [optional]</td>
<td>FFTW3 [optional, but recommended, though forces VA into GPL] <br /> MKL [optional] <br /> FFTS [optional]</td>
</tr>
<tr>
<td><b>ITADataSources</b> <br /> <i>(ITACoreLibs component)</i></td>
......
......@@ -94,19 +94,23 @@
</p>
<p>
<b>Build name: <a href="download/VA_full.v2018a_win32-x64.vc12.zip">VA_full.v2018a_win32-x64.vc12</b></a><br />
<i>Includes Redstart, VAServer, VC12 C++ programming libraries, all bindings (except Python) and Unity scripts.</i><br />
<i>Includes Redstart, VAServer, VC12 C++ programming libraries, all bindings (except Python) and Unity scripts. </i><br />
<br />
<b>Quick user guide</b>:<br />
Unpack to any location and run the batch scripts from the root folder to start a server application.<br />
<br />
<b>Binary package license</b>:<br />
GNU General Public License<br />
<br />
<b>Details</b>:<br />
+ VABase, VANet and VACore C++ developer packages for Visual C++ Compiler Version 12 (Visual Studio 2013)<br />
+ VABase, VANet and VACore * C++ developer packages for Visual C++ Compiler Version 12 (Visual Studio 2013)<br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAUnity and VAUnityExtensions <br />
+ VAServer command line interface application <br />
+ Redstart VA GUI application [BETA] <br />
- VAPython binding * <br />
<span style="font-size: 0.6em">* not available for this compiler version and Python 3.6</span> <br />
- VAPython binding ** <br />
<span style="font-size: 0.6em">* includes FFTW3 (GNU GPL)</span> <br />
<span style="font-size: 0.6em">** not available for this compiler version and Python 3.6</span> <br />
</p>
<hr />
......@@ -122,9 +126,12 @@
<b>Quick user guide</b>:<br />
Unpack to any location. Add paths to <code>include</code>, <code>lib</code> and <code>bin</code> folders for C++ programming. For bindings, make sure the environment (Matlab, Python, C# framework) finds the corresponding folders.<br />
<br />
<b>Binary package license</b>:<br />
Apache License, Version 2.0<br />
<br />
<b>Details</b>:
<br />
+ VABase and VANet C++ developer packages for Visual C++ Compiler Version 14 (Visual Studio 2015)<br />
+ VABase and VANet C++ developer packages for Visual C++ Compiler Version 14 (Visual Studio 2015)<br />
+ VAMatlab, VALua and VAC# bindings <br />
+ VAPython binding for Python 3.6 <br />
+ VAUnity and VAUnityExtensions <br />
......@@ -156,7 +163,9 @@
<br /><br />
We <b>can not guarantee compatibility among VA versions</b>! The reason is, that we still update the interface for new powerful features. This is unfortunate, but can not be achieved with the resources we can afford. If you are interested in new features, you will have to pay the price and update everything, including the bindings you use.
<br /><br />
We adopt naming conventions for platforms and compiler versions from <a href="developers.html#ViSTA">ViSTA VR Toolkit</a>. This way, one can easily extract the target platform, such as <code>win32-x64</code> for a Windows operating system using a mixed 32 bit and 64 bit environment, or <code>vc12</code> to indicate that the binary package was built using the Microsoft Visual C++ Compiler Version 12. If you are missing redistributable libraries you can identify the required Microsoft installer by this suffix.
We adopt naming conventions for platforms and compiler versions from <a href="developers.html#ViSTA">ViSTA VR Toolkit</a>. This way, one can easily extract the target platform, such as <code>win32-x64</code> for a Windows operating system using a mixed 32 bit and 64 bit environment, or <code>vc12</code> to indicate that the binary package was built using the Microsoft Visual C++ Compiler Version 12. If you are missing redistributable libraries you can identify the required Microsoft installer by this suffix.<br />
<br />
The build environment of VA provides configuration of the underlying components. This may or may not result in a binary package that links against GNU GPL licensed libraries. For this reason, VA is either licenses under the favored Apache License, Version 2.0 or under the GNU General Public License, as required by the copyleft nature.
</p>
</section>
......
......@@ -96,7 +96,7 @@
<h3>Licensing</h3>
<h4>Software</h4>
<p>Virtual Acoustics is licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License Version 2.0</a>.</p>
<p>Virtual Acoustics is licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache License Version 2.0</a> or <a href="http://www.gnu.org/licenses/" target="_blank">GNU General Public License</a>, depending on the build configuration, which can potentially linking against GPL libraries.</p>
<h4>Resources</h4>
<p>Virtual Acoustics provides some input data necessary for auralization - like an HRTF dataset. Resources are generally licensed under the original <a href="http://creativecommons.org" target="_blank">Creative Commons Version 4.0</a> license or a CC derivative. The individual license for each work is usually placed next to the resource file and is typically called LICENSE. Some files may also have the license embedded in the metadata, if possible.</p>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment