Wine Traffic #169 For 5/09/2003

WHAT'S NEW with Wine-20030508: (see ChangeLog for details)

• Some more reorganizations of the source tree.
• A few more steps towards kernel/ntdll separation.
• Many Direct3D improvements.
• More compatible COM interfaces definitions.
• Lots of bug fixes.

Breaking down one of the barrriers to widespread adoption of Desktop/LX as a mainstream operating system, Lycoris and TransGaming unleash the GamePak. A powerful package of five (5) native Desktop/LX games, the GamePak comes bundled with access to one free month of WineX which allows Desktop/LX users to play over 250 Windows games on their Desktop/LX PC. At the low price of $34.95, the GamePak gives Desktop/LX users value, action and compatibility in a single, simple to install package. The GamePak is immediately available from The Lycoris Store.

Anyone see the release info for Mozilla 1.4 Beta? It says:

"As of Mozilla 1.4b, it is possible to build Mozilla for Win32 using GCC."

Here's the specific build instructions for Windows:

http://www.mozilla.org/build/win32.html

It notes:

"GCC for Win32 is available as part of the MinGW project. The following mingw packages are required for building:
• gcc >= 3.2.2 (20030208)
• binutils >= 2.13.90 (20030104)
• w32api >= 2.3
• mingw-runtime >= 2.4"

Yes, the 1.4 release will build on MinGW/Cygwin. With a bit of luck, we'll have a binutils release in a week or two, so we can remove some of the ugly, ugly hacks that were put it to work around windres problems that have since been fixed.

Some of this fixes will help a little with an eventual Wine port, but this one will be tough. We still need a lot of work on winegcc/winewrap to get this to work, let alone possible enhancements to gcc for -mthread support.

We are currently failing on simple things with winegcc. For example:

1. It seems that MinGW's gcc support both main() and WinMain() as entry points irregardless of the -mwindows flags. We don't. This results in configure tests. For example, we can't currently build wxWindows using their configure script because configure invokes winegcc with the -mwindows flag even though it builds simple console apps that have a simple main() function. This obviously works under MinGW. I have little knowledge about linking issues like this, how can we support that in wingcc/winewrap?
2. We need to add support for the -shared flag to winegcc. This is a big task, and we haven't even started to look at these issues.
3. I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?

what is the status of WINE development for solaris x86?

i'm running into some fairly fundamental build bugs & would like to know if anyone has got it working.

Wine can be made to work on Solaris X86 with a few patches. To compile you will need the patch kit and a copy of gcc that uses gas rather than AS. the Solaris assembler expect intel assembly while gas expects AT&T.

I sent diffs last week but I don't know how long it will take for them to reach cvs or if they will ever get there.

• Debian Sid x86
• kernel: 2.4.20
• flex version: 2.5.31-4
• bison: 1.875a-1
• gcc: 3.2.3
• binutils: 2.13.90.0.18-1

gcc -c -I. -I. -I../../include -I../../include -Wall -mpreferred-stack-boundary=2 -gstabs+ -Wpointer-arith -g -O2 -o lex.yy.o lex.yy.c
./ppl.l:97:1: warning: "/*/index.html" within comment
./ppl.l: In function `pplex':
./ppl.l:309: `pp_incl_state' undeclared (first use in this function)
./ppl.l:309: (Each undeclared identifier is reported only once
./ppl.l:309: for each function it appears in.)
./ppl.l:309: `pp_pp' undeclared (first use in this function)
[....] /usr/include/stdlib.h: At top level:
lex.yy.c:15493: warning: `yyunput' defined but not used
make[2]: *** [lex.yy.o] Error 1
make[2]: Leaving directory `/root/cvs/wine/libs/wpp'

The script which dumps dll imports and exports now seems to parse everything correctly and organize it nicely in a text file. We need the script run against various windows versions. The output can be sent directly to me, but please verify I do not already have the data for that particular version of windows. I don't need 10 copies of win2k SP3 for example. :)

The script is available at http://home.ptd.net/~compsol. Please make sure you get createdb.pl. There is another script, createwinedb.pl which will ONLY parse the wine spec files.

To run this you will need winedump, perl, and access to your windows directory from within Linux. The cleaner the windows install the better. We don't want to clutter the database with info from dlls not provided with windows. Usage is as follows:

createdb.pl -d -p <path to windows dir> -o <winver> (ex. win98)

This will save the imports and exports and also create winver.ref, where winver is specified on the command line with -o. The .ref file is the one which will contain all the info we need. This will be a large file, so I recommend compressing with gzip if you are going to email it to me. It may be large enough to bounce back into your mailbox if you do not. :)

Attachment is a windows registry file.

Integration of this file directs WinZip to not use the Rich Edit control when displaying comments in Zip files by changing a flag that WinZip read from the registry. This means that it will work with all zip files rather than crashing out on zip files with comments.

Should I post this anywhere else? eg the wine-patch list? Any comments would be appreciated.