Test: Minor Winemaker documentation update

Francois Gouget fgouget at free.fr
Mon Sep 16 06:13:06 CDT 2002



Changelog:

 * documentation/winelib-toolkit.sgml

   Update the section concerning winemaker's options
   Add a couple of warnings about out-of-date sections


Index: documentation/winelib-toolkit.sgml
===================================================================
RCS file: /home/wine/wine/documentation/winelib-toolkit.sgml,v
retrieving revision 1.3
diff -u -r1.3 winelib-toolkit.sgml
--- documentation/winelib-toolkit.sgml	12 Sep 2002 17:53:22 -0000	1.3
+++ documentation/winelib-toolkit.sgml	16 Sep 2002 10:16:16 -0000
@@ -156,10 +156,11 @@
           <filename>configure.in</filename>,
           <filename>Make.rules.in</filename>). From the above description
           you can guess at the items that winemaker may get wrong in
-          this phase: macro definitions, include path, library path,
-          list of libraries to import. You can deal with these issues by
-          using winemaker's <option>-D</option>, <option>-I</option>,
-          <option>-L</option> and <option>-i</option> options if they are
+          this phase: macro definitions, include path, dll path, dlls to
+          import, library path, libraries to link with. You can deal with
+          these issues by using winemaker's <option>-D</>, <option>-P</>,
+          <option>-i</>, <option>-I</>, <option>-L</> and <option>-l</>
+          options if they are
           homogeneous enough between all your targets. Otherwise you may
           want to use winemaker's <link linkend="interactive">interactive
           mode</link> so that you can specify different settings for each
@@ -181,10 +182,11 @@
         <itemizedlist>
           <listitem>
             <para>
-              The target is not being linked with the right set of libraries.
-              You can avoid this by using winemaker's <option>-L</option> and
-              <option>-i</option> options or adding these libraries to the
-              <filename>Makefile.in</filename> file.
+              The target is not importing the right set of dlls, or is not
+              being linked with the right set of libraries. You can avoid
+              this by using winemaker's <option>-P</>, <option>-i</>,
+              <option>-L</option> and <option>-l</> options or adding these
+              dlls and libraries to the <filename>Makefile.in</> file.
             </para>
           </listitem>
           <listitem>
@@ -642,6 +644,13 @@

       <sect2 id="spec-compiling">
         <title id="spec-compiling.title">Compiling it</title>
+          <note><para>
+            FIXME: This section is very outdated and does not correctly
+            describe the current use of winebuild and spec files. In
+            particular, with recent versions of winebuild most of the
+            information that used to be in the spec files is now specified on
+            the command line.
+          </para></note>
           <para>
             Compiling a spec file is a two step process. It is first
             converted into a C file by winebuild, and then compiled into an
@@ -671,7 +680,6 @@
         <title id="spec-reference.title">More details</title>
         <para>
           (Extracted from tools/winebuild/README)
-          <!-- FIXME: this seems to be rather outdated and sometimes even incorrect, check with the source! -->
         </para>

         <para>


-- 
Francois Gouget         fgouget at free.fr        http://fgouget.free.fr/
      Broadcast message : fin du monde dans cinq minutes, repentez vous !




More information about the wine-patches mailing list