JehanneOS
/
newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Remove Mingw.org from FAQ, or replace with Mingw-w64. 

* faq-api.xml: Change MingW to Mingw-w64.
	* faq-programming.xml: Ditto.

Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
This commit is contained in:
Corinna Vinschen 2016-03-21 21:09:23 +01:00
parent 3ba2c39fb2
commit 445036bb98
2 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/faq-api.xml
View File

@ -264,8 +264,9 @@ direct calls to Winsock functions. If you use Cygwin, use the POSIX API.
<question><para>I don't want Unix sockets, how do I use normal Win32 winsock?</para></question> <question><para>I don't want Unix sockets, how do I use normal Win32 winsock?</para></question>
<answer> <answer>
<para>You don't. Look for the MingW project to port applications using <para>You don't. Look for the Mingw-w64 project to port applications using
native Win32/Winsock functions. native Win32/Winsock functions. Cross compilers packages to build Mingw-w64
targets are available in the Cygwin distro.
</para> </para>
</answer></qandaentry> </answer></qandaentry>

18
winsup/doc/faq-programming.xml
View File

@ -90,8 +90,8 @@ Windows, while `long' on 64 bit Cygwin is 8 bytes.</para>
ReadFile (HANDLE, LPVOID, DWORD, LPDWORD, LPOVERLAPPED); ReadFile (HANDLE, LPVOID, DWORD, LPDWORD, LPOVERLAPPED);
</screen> </screen>
<para>In the 32 bit Cygwin and Mingw environments, as well as in the 64 bit <para>In the 32 bit Cygwin and Mingw-w64 environments, as well as in the 64 bit
Mingw environment, it is no problem to substitute DWORD with unsigned Mingw-w64 environment, it is no problem to substitute DWORD with unsigned
long:</para> long:</para>
<screen> <screen>
@ -478,14 +478,10 @@ as well as the User's Guide section
<question><para>How do I compile a Win32 executable that doesn't use Cygwin?</para></question> <question><para>How do I compile a Win32 executable that doesn't use Cygwin?</para></question>
<answer> <answer>
<para>The compilers provided by the <literal>mingw-gcc</literal>, <para>The compilers provided by the <literal>mingw64-i686-gcc</literal> and
<literal>mingw64-i686-gcc</literal>, and <literal>mingw64-x86_64-gcc</literal> <literal>mingw64-x86_64-gcc</literal> packages link against standard Microsoft
packages link against standard Microsoft DLLs instead of Cygwin. This is DLLs instead of Cygwin. This is desirable for native Windows programs that
desirable for native Windows programs that don't need a UNIX emulation layer. don't need a UNIX emulation layer.
</para>
<para>This is not to be confused with 'MinGW' (Minimalist GNU for Windows),
which is a completely separate effort. That project's home page is
<ulink url="http://www.mingw.org/index.shtml"/>.
</para> </para>
</answer></qandaentry> </answer></qandaentry>
@ -549,7 +545,7 @@ have our own Win32 headers which are pretty complete.
</answer></qandaentry> </answer></qandaentry>
<qandaentry id="faq.programming.msvs-mingw"> <qandaentry id="faq.programming.msvs-mingw">
<question><para>How do I use <literal>cygwin1.dll</literal> with Visual Studio or MinGW?</para></question> <question><para>How do I use <literal>cygwin1.dll</literal> with Visual Studio or Mingw-w64?</para></question>
<answer> <answer>
<para>Before you begin, note that Cygwin is licensed under the GNU GPL (as <para>Before you begin, note that Cygwin is licensed under the GNU GPL (as