ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated MFC legal issues section according to the new license, some 

other changes.
This commit is contained in:
Andriy Palamarchuk 2002-07-24 19:01:11 +00:00 committed by Alexandre Julliard
parent a47eb31d2a
commit 609c93df49
1 changed files with 50 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
documentation/winelib-mfc.sgml
View File

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