André Hentschel : winelib: Update Test Drive.

Alexandre Julliard julliard at winehq.org
Sun May 16 10:50:07 CDT 2010


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

Author: André Hentschel <nerv at dawncrow.de>
Date:   Fri May 14 18:42:55 2010 +0200

winelib: Update Test Drive.

---

 en/winelib-intro.sgml |   38 +++++++++++++++-----------------------
 1 files changed, 15 insertions(+), 23 deletions(-)

diff --git a/en/winelib-intro.sgml b/en/winelib-intro.sgml
index 6af563f..9d92fcf 100644
--- a/en/winelib-intro.sgml
+++ b/en/winelib-intro.sgml
@@ -163,31 +163,23 @@
         </programlisting>
 
         <para>
-          Notice how the build fails in a resource file
-          (<filename>Da.rc</filename> at the time this was written).
-          This is because for the time being, the Wine resource compiler
-          (<command>windres</command>) can't cope with more than one
-          resource file ending up in a given executable. To get around
-          that limitation, the Wine developers have chosen to only have
-          one master resource file per application, and include the
-          other ones via <literal>#include</literal> statements in the
-          master one. The included files do not
-          <literal>#include</literal> the necessary files to be
-          compilable on their own. You will need to do the same thing
-          for now in your own Winelib port projects.
+          Notice how it fails linking, because of undefined reference to
+          wnsprintfW. This is because we didn't specify the libraries we need
+          to link to. Normally you know which libraries you need or you can find
+          a list in your old Makefile or project file.
         </para>
         <para>
-          To fix that problem, you will need to edit the list of
-          resource files winemaker thought notepad used, and only keep
-          the master resource file. To do so, open
-          <filename>notepad2/Makefile</filename> in a text editor and
-          search for an assignment to a variable with
-          <literal>RC_SRCS</literal> as part of its name. It will likely
-          be named <literal>notepad2_exe_RC_SRCS</literal>. There will
-          be a list of resource files starting on the same line. Remove
-          them all except <filename>rsrc.rc</filename> (this is the
-          master one for notepad). Save your work.
+          To fix that problem, open <filename>notepad2/Makefile.in</filename>
+          in a text editor and search for an assignment to a variable with
+          <literal>IMPORTS</literal> as part of its name. There will
+          be a list of import libraries. Now run winemaker again, but with
+          these libraries prefixed by <literal>-i</literal>:
         </para>
+        <programlisting>
+          $ winemaker --lower-uppercase -icomdlg32 -ishell32 -ishlwapi -iuser32 -igdi32 -iadvapi32 -ikernel32 .
+          $ make
+        </programlisting>
+
         <para>
           Now you're ready to continue at the same point the first
           <command>make</command> failed. Return to the notepad2
@@ -199,7 +191,7 @@
 
         <para>
           You are done! Now you can start the application as
-          <command>./notepad2</command>.
+          <command>wine notepad2.exe.so</command>.
         </para>
         <para>
           If you come across problems preparing and building this application




More information about the wine-cvs mailing list