André Hentschel : winelib: Remove some outdated information about the C libraries.

[Alexandre Julliard]

Module: docs
Branch: master
Commit: cb5403292188f6cf2a2ed748c3370a1fa34fff95
URL:    http://source.winehq.org/git/docs.git/?a=commit;h=cb5403292188f6cf2a2ed748c3...

Author: André Hentschel 
Date:   Tue Dec 22 19:07:31 2015 +0100

winelib: Remove some outdated information about the C libraries.

Signed-off-by: André Hentschel 
Signed-off-by: Alexandre Julliard

---

en/winelib-porting.sgml | 38 +-------------------------------------
 1 file changed, 1 insertion(+), 37 deletions(-)

diff --git a/en/winelib-porting.sgml b/en/winelib-porting.sgml
index d7a6124..bd7731d 100644
--- a/en/winelib-porting.sgml
+++ b/en/winelib-porting.sgml
@@ -76,43 +76,7 @@
       <para>
         Add <option>-mno-cygwin</option> to your compiler flags. This
         will cause <command>winebuild</command> to resolve your C
-        library calls to <filename class="libraryfile">msvcrt.dll</filename>. Many simple
-        calls which behave the same have been specified as
-        non-importable from msvcrt; in these cases
-        <command>winebuild</command> will not resolve them and the
-        standard linker <command>ld</command> will link to the glibc
-        version instead.
-      </para>
-      <para>
-        In order to avoid warnings in C (and potential errors in C++)
-        from not having prototypes, you may need to use a set of MS
-        compatible header files. These are scheduled for inclusion
-        into Wine but at the time of writing are not available. Until
-        they are, you can try prototyping the functions you need, or
-        just live with the warnings.
-      </para>
-      <para>
-        If you have a set of include files (or when they are available
-        in Wine), you need to use the <parameter>-isystem
-        <replaceable>include_path</replaceable></parameter> flag to gcc to tell it to use your
-        headers in preference to the local system headers.
-      </para>
-      <para>
-        To use option 3, add the names of any symbols that you don't
-        want to use from msvcrt into your applications
-        <filename class="extension">.spec</filename> file. For example, if you wanted
-        the MS specific functions, but not file I/O, you could have a
-        list like:
-      </para>
-
-      <programlisting>@ignore = ( fopen fclose fwrite fread fputs fgets )</programlisting>
-      <para>
-        Obviously, the complete list would be much longer. Remember
-        too that some functions are implemented with an underscore in
-        their name and <function>#define</function>d to that name in
-        the MS headers. So you may need to find out the name by
-        examining <filename>dlls/msvcrt/msvcrt.spec</filename> to get
-        the correct name for your <function>@ignore</function> entry.
+        library calls to <filename class="libraryfile">msvcrt.dll</filename>.
       </para>
     </sect1>