As with the other pages, my version is now officially retired. I'll be maintaining the WineHQ one directly. ChangeLog Update the Winelib page to version 0.3. -- Dimi.
Index: templates/en/winelib.template =================================================================== RCS file: /home/wine/lostwages/templates/en/winelib.template,v retrieving revision 1.3 diff -u -r1.3 winelib.template --- templates/en/winelib.template 3 Jul 2003 17:33:59 -0000 1.3 +++ templates/en/winelib.template 1 Sep 2003 06:21:40 -0000 @@ -22,20 +22,21 @@ <p><i>Motto: The journey of a thousand miles starts with a single step.</i></p> - <p>Theoretically, any Win32 app should be compilable out of the box under Wine. + <h2>Introduction</h2> + <p> + Theoretically, any Win32 app should be compilable out of the box under Wine. This, of course, is not the case. We have incompatible headers, and a bunch of other problems described in - <a href="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</a>. + <a href="http://www.winehq.org/docs/winelib-user/">Winelib User's Guide</a>. A good way to fix these is to try to compile applications for which we - have the source under Winelib.</p> + have the source under Winelib. <h3>Why</h3> <p>But what do we hope to achieve? Well, the purpose of this project is four-fold: <ul> - <li>Document our experience on porting these applications to Winelib <li>Improve Winelib based on the above such that the porting process becomes very simple - <li>Update the <a href="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</a> + <li>Update the <a href="http://www.winehq.org/docs/winelib-user/">Winelib User's Guide</a> to the latest porting process <li>Fixing header & library problems in the process. </ul> @@ -44,7 +45,6 @@ <p>There are many such apps around, and a lot of them are hosted at <a href="http://sourceforge.net">SourceForge</a>. There are over <a href="http://sourceforge.net/softwaremap/trove_list.php?form_cat=216">10,000 apps</a> - listed as running under Windows OS, and over <a href="http://sourceforge.net/softwaremap/trove_list.php?form_cat=230">7,000</a> of them are listed as running under the Win32 environment. @@ -71,8 +71,7 @@ <dd>For these, <tt>winemaker</tt> does a decent job of generating a build system. I will not cover this type of applications here, for the time being. Please refer to the <tt>winemaker</tt> - <a href="http://www.winehq.org/Docs/winelib-user/winelib-getting-started.shtml#WINEMAKER-INTRODUCTION">documentation</a> - + <a href="http://www.winehq.org/docs/winelib-user/winelib-getting-started.html#WINEMAKER-INTRODUCTION">documentation</a> for more information.</dd> <dt>GNU tools based build process</dt> <dd>Fortunately, most OSS applications have a build system based around the @@ -82,23 +81,25 @@ </dl> <h3>What</h3> - If you know of applications that should be listed here, please send your suggestion + If you know of applications that should be listed here, please send your suggestions to <a href="mailto:dpaun@rogers.com">Dimi</a>. Currently, we have: <ul> - + <li><a href="#texniccenter">TeXnicCenter</a> + <li><a href="#cdex">CDex</a> + <li><a href="#xtractor">CD-DA X-Tractor</a> + <li><a href="#dxsdk">DXSDK's Examples</a> <li><a href="#petzold">Petzold's Examples</a> + <li><a href="#winboard">GNU Winboard</a> <li><a href="#coolplayer">CoolPlayer</a> <li><a href="#mozilla">Mozilla</a> <li><a href="#visual-mingw">Visual MinGW</a> <li><a href="#putty">PuTTY</a> <li><a href="#devcpp">Dev-C++</a> - <li><a href="#gimp">Gimp</a> <li><a href="#virtualdub">VirtualDub</a> </ul> <h2>Applications</h2> - Legend: <ul> <li> <span class=todo>TODO</span>: the project is waiting in the queue for someone to pick it up, and run with it @@ -107,9 +108,46 @@ <li> <span class=done>DONE</span>: the Winelib platform has been included in the official application build system <li> <span class=abandoned>ABANDONED</span>: the application has been deem unsuitable for porting using Winelib </ul> - - <h3 class=done><a name="petzold" href="http://www.computersciencelab.com/Petzold.htm">Petzold's Examples</a></h3> + <a name="texniccenter"></a><h3 class=inprogress>TeXnicCenter</h3> + <p>Suggested by <a href="mailto:jahn.matthias@freenet.de">Matthias Jahn</a>: + <i>It is a tex-shell like kde's "kile".</i> + <ul> + <li>worker: <a href="mailto:jahn.matthias@freenet.de">Matthias Jahn</a> + <li>status: runs with wine, now i try to port it with Winelib + <li>updated: Apr 20, 2003 + <li>homepage: <a href="http://www.toolscenter.org/products/texniccenter/">www.toolscenter.org/products/texniccenter</a> + </ul> + + <a name="cdex"></a><h3 class=todo>CDex</h3> + <p>Suggested by <a href="mailto:stuart.rowan@strr.org">Stuart Rowan</a>: + <i>cdex is a great ripper tool used by many to make mp3s and oggs under windows. [...] + If this could be ported to winelib that would be super then I can enjoy it on linux (finally).</i> + <ul> + <li>worker: wanted + <li>status: wishlist + <li>updated: Apr 14, 2003 + <li>homepage: <a href="http://cdexos.sourceforge.net/">cdexos.sourceforge.net</a> + </ul> + + <a name="xtractor"></a><h3 class=todo>CD-DA X-Tractor</h3> + <ul> + <li>worker: wanted + <li>status: it has a MinGW build system... + <li>updated: Mar 30, 2003 + <li>homepage: <a href="http://xtractor.sourceforge.net/">xtractor.sourceforge.net</a> + </ul> + + <a name="dxsdk"></a><h3 class=todo>DXSDK's Examples</h3> + <p>Suggested by <a href="mailto:reif@earthlink.net">Robert Reif</a>. + <ul> + <li>worker: wanted + <li>status: it's a cool idea + <li>updated: Mar 26, 2003 + <li>homepage: <a href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/directx.asp">msdn.microsoft.com/library</a> + </ul> + + <a name="petzold"></a><h3 class=done>Petzold's Examples</h3> <p>Suggested by <a href="mailto:j_kopplin@hotmail.com">John Kopplin</a>. <ul> <li>worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> @@ -117,7 +155,6 @@ <li>updated: Mar 24, 2003 <li>homepage: <a href="http://www.computersciencelab.com/Petzold.htm">www.computersciencelab.com/Petzold.htm</a> </ul> - <p>It took some work, but we've done it. The good news is that all (but 3) examples compile just fine. This has been accomplished while making absolutely <i>no</i> changes to the original source, and @@ -157,35 +194,47 @@ are the instructions on how to try the sample under Wine: <br> <i>(place the Petzold CD in the CDROM drive)</i> -<pre> - $ mount /mnt/cdrom - $ mkdir petzold - $ cd petzold - $ cp -r /mnt/cdrom/* . - $ wget http://www.computersciencelab.com/Petzold.zip - $ unzip -a Petzold.zip - $ bash Wine/install.sh - $ make -</pre> + <table width="500" border=0 cellpadding=10><tr><td class=black> + <span class=inverse> +mount /mnt/cdrom<br> +mkdir petzold<br> +cd petzold<br> +cp -r /mnt/cdrom/* .<br> +wget http://www.computersciencelab.com/Petzold.zip<br> +unzip -a Petzold.zip<br> +bash Wine/install.sh<br> +make<br> +</span> + </td></tr> + </table> + <p>Enjoy! - <h3 class=inprogress><a name="coolplayer" href="http://coolplayer.sourceforge.net/">CoolPlayer</a></h3> - <p>Suggested by <a href="mailto:henrik.uggla@hem.utfors.se">Henrik Uggla</a>. + <a name="winboard"></a><h3 class=works>GNU Winboard</h3> + <p>Suggested by <a href="erwinwolffnl@microformatica.com">Erwin Wolff</a>. <ul> + <li>worker: <a href="mailto:erwinwolffnl@microformatica.com">E. C. F. Wolff</a>, + <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a>. + <li>status: Non-computer opponent playing only so far. + <li>updated: Aug 18, 2003 + <li>homepage: <a href="http://www.tim-mann.org/xboard.html">www.tim-mann.org/xboard.html</a> + </ul> + Intresting and simple chess game because it depends on email and network (TCP/IP) code to function. - <li>worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a>, help wanted. - <li>status: Initial review, see below for my notes. - <li>updated: Dec 6, 2002 + <a name="coolplayer"></a><h3 class=works>CoolPlayer</h3> + <p>Suggested by <a href="mailto:henrik.uggla@hem.utfors.se">Henrik Uggla</a>. + <ul> + <li>worker: <a href="mailto:vberon@mecano.gme.usherb.ca">Vincent Béron</a>. + <li>status: Trying to submit the <a href="http://www.winehq.com/hypermail/wine-patches/2003/04/0237.html">changes</a> to the official CVS + <li>updated: Apr 22, 2003 <li>homepage: <a href="http://coolplayer.sourceforge.net/">coolplayer.sourceforge.net</a> </ul> - I have tried to run the Win32 binary under Wine, it runs just fine. Therefore, it should - run as a Winelib application just fine. As for the build system, it only has a MSVC++ - .dsp-based build system. It is probably better to port the application first to MinGW, - and then compile it as a Winelib app. - <strong>We need a volunteer for the MinGW port.</strong> + <strong>Update:</strong> (from Vincent) <i>Ok, so I got it running under Winelib. + I'm listening to /usr/share/redhat-credits.ogg (only thing I could find quickly on my + computer :). It's so good to listen to something through it :P + I'll try to get it all under small bits for both projects.</i> - <h3 class=inprogress><a name="mozilla" href="http://www.mozilla.org">Mozilla</a></h3> - + <a name="mozilla"></a><h3 class=inprogress>Mozilla</h3> <p>One of the largest free software projects that we can support with Winelib. Having this one compile, and run under Winelib would be a real <i>tour de force</i>. <ul> @@ -194,13 +243,12 @@ <li>updated: Dec 31, 2002 <li>homepage: <a href="http://www.mozilla.org">www.mozilla.org</a> </ul> - <p><strong>Update:</strong> Mozilla currently requires MS tools to build on Win32. To be ported to Wine, Mozilla must first be ported over to MinGW. There is an ongoing effort to do so that is tracked in bug <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=134113">134113</a>. - <h3 class=works><a name="visual-mingw" href="http://visual-mingw.sourceforge.net/">Visual MinGW</a></h3> + <a name="visual-mingw"></a><h3 class=works>Visual MinGW</h3> <p>Rational provided by <a href="mailto:steven_ed4153@yahoo.com">Steven Edwards</a>: <p><i>[...] WINE might gain more of a market share if there was a easy way for people that are writing Windows apps on Windows if they had a IDE for GCC @@ -210,7 +258,6 @@ Mingw and ReactOS have by finding areas where we are not in sync.</i> <ul> <li>worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> - <li>status: compiles, links, and runs! <a href="http://www.winehq.com/hypermail/wine-devel/2002/12/1001.html">Patch</a> sent to the maintainer. <li>updated: Dec 31, 2002 @@ -218,10 +265,9 @@ </ul> - <h3 class=done><a name="putty" href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a></h3> + <a name="putty"></a><h3 class=done>PuTTY</h3> <p>A most loved Windows tool. <ul> - <li>worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> <li>status: compiles, links, and runs! The <a href="http://www.winehq.com/hypermail/wine-devel/2002/12/1002.html">patch</a> @@ -230,14 +276,13 @@ <li>homepage: <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">www.chiark.greenend.org.uk/~sgtatham/putty</a> </ul> - <h3 class=abandoned><a name="devcpp" href="http://www.bloodshed.net/dev/devcpp.html">Dev-C++</a></h3> + <a name="devcpp"></a><h3 class=abandoned>Dev-C++</h3> <a href="mailto:lynchaj@yahoo.com">Andrew Lynch</a> writes:<br> <i>Visual-Mingw sounds almost identical to DevEx found at <a href="http://sourceforge.net/projects/wingtk">http://sourceforge.net/projects/wingtk</a> and <a href="http://www.bloodshed.net">http://www.bloodshed.net</a>. <br>I am using their wGLADE tool for cygwin/GTK+ development presently and it works great under Win98.</i> - <ul> <li>worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> <li>status: abandoned @@ -248,8 +293,7 @@ as it is written in Pascal/Delphi. It should be possible to port it to Linux using Kylix relatively easily. - <h3 class=inprogress><a name="atlmfc" href="http://support.microsoft.com/default.aspx?scid=/support/visualc/atlmfc/atlmfc.asp">ATL & MFC</a></h3> - + <a name="atlmfc"></a><h3 class=inprogress>ATL & MFC</h3> <p>This is a very common request. And due to its widespread usage, a very important project as well. <ul> @@ -260,36 +304,32 @@ </ul> From Ronald, on what it took to compile MFC: <ul> - <li> I had to uncomment <tt>PSH_WIZARD97</tt> in <tt>/wine/prsht.h</tt> (fixed by Francois) <li> The packing pragmas looks handled by gcc-3.2.1, so we may remove all modifications made by winemaker <li> I had to force winnt.h to use nameless struct and unions (fixed by Dimi) <li> I added </tt>#define EDEADLOCK EDEADLK</tt> in <tt>/wine/msvcrt/errno.h</tt> (fixed by Francois) - <li> I linked _alloca() to alloca() function + <li> I linked _alloca() to alloca() function (fixed by Alexandre) <li> There was a conflict on HKEY type between <tt>afxres.h</tt> and <tt>wine/windef.h</tt> - <li> Some little others syntax issues like: <tt>__try __expect, asm {}, unsigned short(x), (LPCTSTR)CString</tt> </ul> - <h3 class=todo><a name="gimp" href="http://www.gimp.org/~tml/gimp/win32/">Gimp</a></h3> + <a name="gimp"></a><h3 class=todo>Gimp</h3> <p>This one's a very strange case. <a href="http://www.gimp.org/">The Gimp</a> is a native Linux application built around the <a href="http://www.gtk.org/">GTK+</a> toolkit. It became a native Windows application by porting over the entire GTK+ toolkit, and other supporting libraries. It would thus be quite interesting to see how it can be ported back to Linux, via Winelib. <ul> - <li>worker: wanted <li>status: todo <li>updated: Nov 27, 2002 <li>homepage: <a href="http://www.gimp.org/~tml/gimp/win32/">www.gimp.org/~tml/gimp/win32</a> </ul> - <h3 class=todo><a name="virtualdub" href="http://www.virtualdub.org/">VirtualDub</a></h3> + <a name="virtualdub"></a><h3 class=todo>VirtualDub</h3> <p>Suggested by <a href="mailto:nerijus@users.sourceforge.net">Nerijus Baliunas</a> since <i>it is often requested</i>. <ul> - <li>worker: wanted <li>status: todo <li>updated: Nov 27, 2002 @@ -300,7 +340,6 @@ As explained in the introduction, the primary motivation for this effort is to discover, and fix Winelib shortcomings. These are the fixes that have been <a href="http://www.winehq.com/hypermail/wine-devel/2002/11/1518.html">suggested and discussed</a> - thus far: <dl> <dt>Configuration</dt> @@ -310,7 +349,6 @@ <li> status: not started <li> updated: Nov 28, 2002 </ul> - </dd> <dt>Compilation</dt> <dd>Write a small wrapper that makes gcc on Linux behave like mingw. <span class=done>[DONE]</span> @@ -320,19 +358,16 @@ and <a href="http://cvs.winehq.com/patch.py?id=6503">committed</a>. <li> updated: Dec 5, 2002 </ul> - </dd> <dt>Resources</dt> <dd>Make <tt>wrc</tt> compatible with <tt>windres</tt> at command line level. <span class=done>[DONE]</span> <ul> - <li> worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> <li> status: working on <a href="http://www.winehq.com/hypermail/wine-devel/2002/12/0185.html">this</a> solution, patch <a href="http://www.winehq.com/hypermail/wine-patches/2002/12/0048.html">submitted</a>, and <a href="http://cvs.winehq.com/patch.py?id=6519">committed</a>. <li> updated: Dec 6, 2002 </ul> - </dd> <dt>Linking</dt> <dd>Write wrapper script that takes care of generating <tt>.spec</tt> files, etc. <span class=done>[DONE]</span> @@ -340,7 +375,6 @@ <i>Yes, I think we want a wrapper like dllwrap to do all that. I'm not sure a script would be enough, we may want a full-fledged C program. The idea would be that you do something like:</i> - <pre> winewrap *.o *.res -o foo -lwhatever </pre> @@ -350,20 +384,17 @@ you still have a <tt>.exe.so</tt> file, but you don't really need to worry about it. You simply run "foo" and everything works.</i> <ul> - <li> worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> <li> status: first cut <a href="http://www.winehq.com/hypermail/wine-devel/2002/12/0194.html">submitted</a> for review, patch <a href="http://cvs.winehq.com/patch.py?id=6616">committed</a>. <li> updated: Dec 16, 2002 </ul> </dd> - <dt>Running</dt> <dd>Arrange so that a regular Unix executable is generated. <span class=done>[DONE]</span> <p>Improve the <tt>wineapploader</tt> so it can be used directly by the step above. <ul> <li> worker: <a href="mailto:dpaun@rogers.com">Dimitrie O. Paun</a> - <li> status: patch <a href="http://cvs.winehq.com/patch.py?id=6616">committed</a>. <li> updated: Dec 16, 2002 </ul>