- Wine-Devel - list.winehq.org

Re: spec file syntax and automated generation
by Jon Griffiths Aug. 20, 2003

Aug. 20, 2003

Hi, <disclaimer> I havent read the wine-user posts.... >1. The winebuild manpage only mentions ptr, str, wstr, long and double >as valid Win32 function argument size information - is the amount and >kind of symbols really important, or is it just the amount of used stack >space? the type is used for dumping of parameters so its good to have it right. >I am not too familiar with assembler, but I would assume the first is >right, since two arguments are pushed on the stack, each using 32bit. Correct. Logical types are irrelevant, only the physical size matters. % __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

is anyone running windows 95, windows 98, windows ME or windows 2003?
by Jonathan Wilson Aug. 20, 2003

Aug. 20, 2003

If so, I need you to run some kind of PE dumper that can dump exports (such as dumpbin from MS with the /exports switch on user32.dll and gdi32.dll from your version and send me the results, along with details of which version of windows you are running. I want this info because I am compiling a list of the different versions of windows and which functions are exported by user32.dll and gdi32.dll in each version.

4 3

Re: [Foxgui-users]Re: Wine fixes (1)
by Dimitrie O. Paun Aug. 20, 2003

Aug. 20, 2003

On 20 Aug 2003, Doug Henry wrote: > > Added this one too. [As to why you'd want to run FOX under Wine while it > > runs natively under X11, I don't know....] > > > > If you cross-compile for windows under linux, it is useful to test under > wine. Its more convenient than rebooting or going to another machine > just for simple testing. Top 10 reasons you want Fox ported to Wine: 10. Windows sux 9. Microsoft is evil 8. Test windows features without rebooting (as Doug mentioned) 7. Keep development on Linux 6. Run valgrind on the Windows port 5. Make sure the Win32 part is portable to multiple implementations 4. Help find missing features/problems/etc. in Wine 3. Some people may prefer the Wine widgets to the GTK+ ones 2. wxWindows is already ported to Wine, Fox needs that too! ;) and the number one reason is: 1. It is just cool!!! (what geek can resist this sort of virtualization? :)) -- Dimi.

1 0

Re: winegcc
by puoti＠inwind.it Aug. 20, 2003

Aug. 20, 2003

I've just updated via cvs, and I get this [ivan(a)my Wine]$ winegcc -mwindows 01-biditest.c /tmp/wappZjLo5B.spec.o(.text+0x1010a): In function `__wine_exe_main': : undefined reference to `WinMain' collect2: ld returned 1 exit status Error: gcc failed. Error: winewrap failed. [ivan(a)my Wine]$ winewrap returns a seg fault.

3 2

LPT1 support in DOSFS_OpenDevice
by E Lea Aug. 20, 2003

Aug. 20, 2003

I'm trying to add LPT1 support to DOSFS_OpenDevice. The software that requires this functionality controls a parallel port plotter by sending LOGO-style ASCII commands. I have based my attempts heavily on the serial port support, although I don't think I really know what I'm doing. Can anyone explain to me what's required? I have tried to implement a server call to create a file descriptor to /dev/lp0 (read from ~/.wine/config) and return a handle to it, but after that (perhaps when wine starts using the handle) both the wine and wineserver processes die. I don't really understand handles and how they are used. Are more functions required other than a simple create_parallel()? How do handles work?

1 0

anyone here got the format of icons & cursors?
by Jonathan Wilson Aug. 20, 2003

Aug. 20, 2003

I am asking this since WINE appears to support icons and cursors but I cant find the code or the info. What I am looking for is: 1.the format of *.cur files 2.the format of *.ico files 3.the format of RT_CURSOR resources 4.the format of RT_ICON resources 5.the format of RT_CURSOR_GROUP resources and 6.the format of RT_ICON_GROUP resources

1 0

Re: PATCH - build libwine_unicode with w32api headers
by Steven Edwards Aug. 20, 2003

Aug. 20, 2003

Nevermind. Send this patch and email to /dev/null. My w32api headers were hosed. Sorry for the noise. Thanks Steven --- Steven Edwards <steven_ed4153(a)yahoo.com> wrote: > You can now rm -fr *.h in wine/include (exclude config.h) and then do > configure. This patch fixes unicode.dll. I didnt know if you had a problem with > defining the WINVER but a define the winnls.h is not included in mingw without this. Should > wines > winnls be changed also? here is what we get without the patch. I am not near a MS_VC install to > check how it is done with the headers there. > > gcc -c -I. -I. -I../../include -I../../include -D_REENTRANT -D__WINESRC__ -DNO_ > LIBWINE_PORT -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ - > Wpointer-arith -g -O2 -o wctomb.o wctomb.c > wctomb.c: In function `is_valid_sbcs_mapping': > wctomb.c:73: `WC_NO_BEST_FIT_CHARS' undeclared (first use in this function) > wctomb.c:73: (Each undeclared identifier is reported only once > wctomb.c:73: for each function it appears in.) > wctomb.c: In function `is_valid_dbcs_mapping': > wctomb.c:256: `WC_NO_BEST_FIT_CHARS' undeclared (first use in this function) > make: *** [wctomb.o] Error 1 > > Changelog: Fix building libwine_unicode with w32api headers. > > Index: Makefile.in > =================================================================== > RCS file: /home/wine/wine/libs/unicode/Makefile.in,v > retrieving revision 1.5 > diff -u -r1.5 Makefile.in > --- Makefile.in 27 Jun 2003 19:02:23 -0000 1.5 > +++ Makefile.in 20 Aug 2003 06:13:25 -0000 > @@ -4,7 +4,7 @@ > VPATH = @srcdir@ > LIBRARY = wine_unicode > SOVERSION = 1 > -EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT > +EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT -DWINVER=0x0500 > > CODEPAGES = \ > 037 \ > > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

rpcrt4.dll from WINE in ReactOS
by Steven Edwards Aug. 20, 2003

Aug. 20, 2003

Hello, Are we going to be able to make use of WINEs rpcrt4.dll on ReactOS? I can build 99% of the dll with Mingw but am having trouble because of WINEs exception handler and a few calls to gettimeofday. If we should be able to use it then I will work on porting it when I get back from vacation on the 8th. We need a semi functioning rpcrt4 to be able to port ole32 and shell32. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 2

winegcc
by puoti＠inwind.it Aug. 20, 2003

Aug. 20, 2003

Hi list, I was compiling the bidi test to try the ICU libs, and got this error ivan(a)my Wine]$ winegcc 01-biditest.c wgcc.ygvnee.o(.text+0x91): In function `main': : undefined reference to `GetCharacterPlacementW' collect2: ld returned 1 exit status Error: gcc failed. Error: /usr/local/bin/winewrap failed. [ivan(a)my Wine]$ so I tried winewrap and got a segmentation fault I'm running wine cvs current, compiled on Mandrake 9.1 with gcc 3.2.2, and glibc 2.3, any help would be gratly appreciated, Ivan.

2 1

problem with apps in desktop mode
by Rok Mandeljc Aug. 19, 2003

Aug. 19, 2003

When I try running InstallShield in windowed mode ("Desktop" = "640x480" as per default in config), window appears for a second and then dissapears printing this message: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 12 (X_ConfigureWindow) Serial number of failed request: 93 Current serial number in output stream: 98 Did latest modifications of x11drv break anything? -- Rok Mandeljc <rok.mandeljc(a)gimb.org> "All that is gold does not glitter, Not all those who wander are lost; The old that is strong does not wither, Deep roots are not reached by the frost. >From the ashes a fire shall be woken, A light from the shadows shall spring; Renewed shall be blade that was broken, The crownless again shall be king." -- J.R.R. Tolkien

4 3