Updated MFC legal issues section according to the new license, some
other changes.
This commit is contained in:
parent
a47eb31d2a
commit
609c93df49
|
@ -64,21 +64,22 @@
|
|||
from several sources: your code, Winelib code, Microsoft MFC code,
|
||||
and possibly code from other vendor sources. As a result, you must
|
||||
ensure that the licenses of all code sources are obeyed. What you are
|
||||
allowed and not allowed to do can vary depending on how you compile
|
||||
your program and if you will be distributing it. For example, if you
|
||||
are releasing your code under the GPL, you cannot link your code to
|
||||
MFC code because the GPL requires that you provide ALL sources to your
|
||||
users. The MFC license forbids you from distributing the MFC source so
|
||||
you cannot both distribute your program and comply with the GPL
|
||||
license. On the other hand, if your code is released under the LGPL,
|
||||
you cannot statically link your program to the MFC and distribute it,
|
||||
but you can dynamically link your LGPL code and the MFC library and
|
||||
distribute it.
|
||||
allowed and not allowed to do can vary depending on how you combine
|
||||
the code and if you will be distributing it. For example, if you
|
||||
are releasing your code under the GPL or LGPL, you cannot use MFC
|
||||
because these licenses do not allow covered code to depend on
|
||||
libraries with non-compatible licenses.
|
||||
There is a workaround - in the license for your
|
||||
code you can make an exception for the MFC library.
|
||||
For details see
|
||||
<ulink url="http://www.gnu.org/licenses/gpl-faq.html">The GNU GPL FAQ</ulink>.
|
||||
</para>
|
||||
<para>
|
||||
Wine/Winelib is distributed under an X11-like license. It places few
|
||||
restrictions on the use and distribution of Wine/Winelib code. I doubt
|
||||
the Wine license will cause you any problems. On the other hand, MFC
|
||||
Wine/Winelib is distributed under the GNU Lesser General Public
|
||||
License. See the license for restrictions on the modification and
|
||||
distribution of Wine/Winelib code. In general it is possible to
|
||||
satisfy these restrictions in any type of application.
|
||||
On the other hand, MFC
|
||||
is distributed under a very restrictive license and the restrictions
|
||||
vary from version to version and between service packs. There are
|
||||
basically three aspects you must be aware of when using the MFC.
|
||||
|
|
Loading…
Reference in New Issue