Hi,
> As far as I understand, you aren't mixing in OSG code with another
> library with a different license, you are just linking to both so the
> licenses shouldn't conflict with each other - as long as you honour
> the individual licenses with how you use them in your applications.
Yes, my a
On Wed, 6 Mar 2019 at 10:42, Matthias Schütze wrote:
> Currently, I am checking the possibilities to update my company's proprietary
> application from using OSG 3.0.1 to use a newer version. On GitHub, I could
> see that with OSG 3.4 the license document changed from OSGPLv0.0 to
> OSGPLv1.0.
Hi,
Currently, I am checking the possibilities to update my company's proprietary
application from using OSG 3.0.1 to use a newer version. On GitHub, I could see
that with OSG 3.4 the license document changed from OSGPLv0.0 to OSGPLv1.0.
There are only minor differences and I understand that th
3 matches
Mail list logo
