August 2002 - Wine-Devel - list.winehq.org

right way to compile wine with a "buildroot" DESTDIR is missing
by Raul Dias Aug. 16, 2002

Aug. 16, 2002

Hi, I have been building wine RPMs for some time now. The way I do is to specify the correct paths to ./configure script (like prefix, mandir, bindir, ...). After building I have to use an ugly make install in orther to install it into another dir that is different from the one. However, talking to some wine developers on #winehq in openprojects network. They state that a ./configure --prefix=<you buildroot>/prefix was enough. That's because wine does not hardcode any %prefix related path. This would simplify a lot the process. However I just checked that wine does hardcode the %prefix dir in the binaries. This is done in dlls/ntdll/ntdll.dll.so and possible at miscemu/wine . AFAIU, this is done to keep the path to the global registries which is the Right Thing to do. So what I really would like to know is which way is the right way to install wine in a dir different than %prefix or /usr/local (default %prefix)? Is there any chance to get a DESTDIR implemented in the Makefiles? []'s Raul Dias

4 12

microsoft CFileDialog problem
by mayonaise＠beer.com Aug. 16, 2002

Aug. 16, 2002

hi everybody, i am currently working on making a windows program function in wine. it works for the most part, so i'm trying to iron out a few critical bugs. first off... i'm looking at microsoft's CFileDialog class - it is what the standard windows 'open file' and 'save file' dialog windows use. the problem is this: CFileDialog has a built in function called OnFolderChange, that is used to determine whether the user has changed folders in the dialog, whether by double click or what not.. the program i'm working on overrides the CFileDialog class, and includes more code for the OnFolderChange function (and for other functions) for its own purposes. the new OnFolderChange function works perfectly fine in windows, but is completely ignored when using wine - it never even gets called, while the rest of the dialog window retains all of its intended functionality. as a reference, the built in functions OnFileNameChange, GetFolderPath, and others gets overridden successfully. as far as i can tell, the only function that is not working properly is the OnFolderChange function. the overriding of CFileDialog was accomplished by using a hooking procedure provided in the MSDN library. i hope this is enough information, however i don't expect anyone to fully be able to address this issue without seeing the code i'm working on first.thank you for your time! -kyle

2 1

note to packagers (new optional dependancy)
by Shachar Shemesh Aug. 16, 2002

Aug. 16, 2002

Hi all, A patch just submitted to wine-patches changes the rules when building binary packages of WINE for distributions. This is an optional change, so ignoring this email will not break anything, but will result in decreased functionality. During the configure phase ./configure will now check for the availability of the libfribidi header files. These are typically distributed in a package called "libfribidi-dev". I would highly recommend installing this library on the machine you compile the package on, so as to include the option for BiDi support in the resulting binary. If the headers are found during compile time, a run time check is performed whether the libfribidi library is available. If it is not, Wine will continue without BiDi support. If it is, BiDi support will (at some future date, admitably) be enabled. In .deb speak, libfribidi-dev is build recommended for wine src. libfribidi is suggested for wine. Shachar

2 1

RE: New user/developer has questions ...
by Medland, Bill Aug. 16, 2002

Aug. 16, 2002

> -----Original Message----- > From: Crispen Scott [mailto:C.Scott(a)astronautics.com] > Sent: Friday, August 16, 2002 6:56 AM > To: wine-devel(a)winehq.com > Subject: New user/developer has questions ... > > > I have just RPMed wine-20020512-1.i386.rpm and attempted to > run several WIN > programs (to wit: sol.exe and a proprietary package). > Both fail. I am including the entire run/error message from > my attempt to run > sol.exe below. Being new to WINE, I have no idea where > to begin to find the problem. I have annotated the error > message with notes. > All notes are separated by a > > <NOTE - TEXT> then a CR and follows the line(s) that the NOTE > applies to. > > [root(a)localhost root]# wine /mnt/windows/windows/system32/sol.exe > <NOTE - This is the command line entry > > > err:reg:_convert_win95_registry_to_wine_format unable to load > native win95 > registry file C:\WINDOWS\system.dat: unknown signature. > err:reg:_convert_win95_registry_to_wine_format Unable to load > native win95 > registry file C:\WINDOWS\system.dat. > err:reg:_convert_win95_registry_to_wine_format Please report to > a.mohr(a)mailto.de. > err:reg:_convert_win95_registry_to_wine_format Make a backup > of the file, run > a good reg cleaner program and try again! > <NOTE - The SYSTEM.DAT file located in the windows SUBDIR was > exported from > regedit.exe. This is from a WIN2K OS > That's your mistake. You shouldn't export it. reg_convert_win95_registry_to_wine_format actually reads the files that store a Win95 registry (the actual files, not exports). > > fixme:win32:PE_CreateModule Security directory ignored > <NOTE - I assume this is a FIXME in the SRC> True > > err:font:AddFontFileToList Unable to load font file > "/mnt/windows/windows/Fonts/desktop.ini" err = 55 > <NOTE - This file exists in the proper location so what is the error?> I don't know the font stuff; someone else maybe will help here. > > err:font:AddFontFileToList Already loaded font L"Garamond" L"Bold" > err:font:AddFontFileToList Already loaded font L"Garamond" L"Italic" > err:font:AddFontFileToList Already loaded font L"Garamond" L"Regular" > > err:font:AddFontFileToList Unable to load font file > "/mnt/windows/windows/Fonts/modern.fon" err = 2 > err:font:AddFontFileToList Unable to load font file > "/mnt/windows/windows/Fonts/mtsorts.ttf" err = 2 > err:font:AddFontFileToList Unable to load font file > "/mnt/windows/windows/Fonts/roman.fon" err = 2 > err:font:AddFontFileToList Unable to load font file > "/mnt/windows/windows/Fonts/script.fon" err = 2 > <NOTE - These files exist so why are they able to be loaded?> > > X Error of failed request: XF86DGANoDirectVideoMode > Major opcode of failed request: 136 (XFree86-DGA) > Minor opcode of failed request: 22 (XDGAOpenFramebuffer) > Serial number of failed request: 181 > Current serial number in output stream: 181 > <NOTE - What does this indicate?> > > I am trying to come up to speed on the use of WINE but, as > everyone knows, > the documentation is a little light > as is the commenting of the source code. If someone could > please head me in > the right direction, I would greatly appreciate it. > > Once I have gained some additional expertise in WINE I will > use my 15+ years > of Windows development experience and knowledge > to try and resolve some of the issues and bugs that are > reported. This may > take me several more weeks. > > I am also intending to write a technical book on WINE so will > submit chapters > for review to the community as the become available. > Much of the information will deal with the issues the I, as a > newbie, am > encountering. > > I await the response. > > Crispen Scott > > BTW: I downloaded the source for 20020804 and, after fixing > several build > related problems (incorrect build order, root objections, & > eliminating > programs with build problems I couldn't readily resolve, i.e. > widl), I had > even worse problems with trying to get that version of wine > to run. That is > why I reverted to the latest RPM version. Some of the > problems with the > 20020804 build might be resolved after I see the answers to > the problems I > stated above. > > I am excited about becoming an integral part of this > community but need some > start-up help! > Thanks! > > -- > Crispen Scott > Engineer - Software > Astronautics.com > 4115 Teutonia Road > Milwaukee, WI 53209 > Tel: 414-447-8200 x4434 > C.Scott(a)Astronautics.com > What is your environment; you shouldn't have had all those build problems. Bill

4 3

RFC: winedefault.reg
by lawson_whitney＠juno.com Aug. 16, 2002

Aug. 16, 2002

Good day! Should we maybe install it somewhere in --prefix so it has a chance to get included in binary packages? I have one in /usr/local, but it is from April 19, 2001 and not much use... Lawson ---oops---

2 1

RE: window parent/owner handling
by Medland, Bill Aug. 16, 2002

Aug. 16, 2002

> -----Original Message----- > From: Dmitry Timoshkov [mailto:dmitry(a)baikal.ru] > Sent: Thursday, August 15, 2002 8:22 PM > To: Medland, Bill > Cc: wine-devel(a)winehq.com > Subject: Re: window parent/owner handling > > > "Medland, Bill" <Bill.Medland(a)accpac.com> wrote: > > > Includes my previous patch for SetWindowLong (for Bug 825) > > Seems that your investigations are correct, at least test succeeds > under win2000. I would suggest to apply tiny patch (attached) to catch > some additional problems. Thanks Dmitry; for all your help on this. p.s. I suddenly realised I'd put only my name on the copyright in the test. It's based on your code; You want to be mentioned? (Or is this sufficient ackowledgement?). > > -- > Dmitry. > Bill

2 1

FW: what's with WS_OVERLAPPED?
by Medland, Bill Aug. 16, 2002

Aug. 16, 2002

(Damn; Outlook bugs me) -----Original Message----- From: Medland, Bill Sent: Friday, August 16, 2002 8:19 AM To: 'rolf.kalbermatter(a)citeng.com' Subject: RE: what's with WS_OVERLAPPED? > -----Original Message----- > From: Rolf Kalbermatter [mailto:r.kalbermatter(a)hccnet.nl] > Sent: Thursday, August 15, 2002 11:31 PM > To: Bill.Medland(a)accpac.com > Cc: wine-devel(a)winehq.com > Subject: RE: what's with WS_OVERLAPPED? > > > On Thu, 15 Aug 2002 "Medland, Bill" <Bill.Medland(a)accpac.com> wrote > > > >> On Wednesday, August 14, 2002 Ove Kaaven [mailto:ovehk(a)ping.uio.no] > wrote: > > <snip> > > >> WS_OVERLAPPED is in practice considered the absence of the > >> WS_POPUP and > >> WS_CHILD flags, I believe. > > > >Thanks Ove; that'll do for a working hypothesis. (I wish > Microsoft would > be > >consistant) > > > >Just for the record it is clearly more complex than that. I > guess since > >Microsoft wrote it we can trust Spy++ a little. I have seen > spy++ declare > >that a "tooltips" class window (style 0x84800000/00000088) has style > >WS_OVERLAPPED whereas a "tooltips_class32" class window (style > >0x84800003/00000088) doesn't. > > Hmm, this is just a wild guess but couldn't it be that the > WS_OVERLAPPED > style applies only to the lower word of the windows style. > Windows coming > from 16bit DOS it wouldn't be surprising if the original > windows style was > 16 bit only as well. Either that or Spy++ has a bug, even > though you trust > it so much ;-). Except all the general style stuff is in the top word; the only difference between the two styles, the 3, is two TTS_* toolbar style; generally the stuff in the low word is, I believe, control-specific. I honestly think that it is not so much that Spy++ has a bug as that it is based on some knowledge within Microsoft that describes how they have worked around the mess they have generated over the years. > > Rolf Kalbermatter > mailto:rolf.kalbermatter(a)citeng.com > > Bill

1 0

New user/developer has questions ...
by Crispen Scott Aug. 16, 2002

Aug. 16, 2002

I have just RPMed wine-20020512-1.i386.rpm and attempted to run several WIN programs (to wit: sol.exe and a proprietary package). Both fail. I am including the entire run/error message from my attempt to run sol.exe below. Being new to WINE, I have no idea where to begin to find the problem. I have annotated the error message with notes. All notes are separated by a <NOTE - TEXT> then a CR and follows the line(s) that the NOTE applies to. [root(a)localhost root]# wine /mnt/windows/windows/system32/sol.exe <NOTE - This is the command line entry > err:reg:_convert_win95_registry_to_wine_format unable to load native win95 registry file C:\WINDOWS\system.dat: unknown signature. err:reg:_convert_win95_registry_to_wine_format Unable to load native win95 registry file C:\WINDOWS\system.dat. err:reg:_convert_win95_registry_to_wine_format Please report to a.mohr(a)mailto.de. err:reg:_convert_win95_registry_to_wine_format Make a backup of the file, run a good reg cleaner program and try again! <NOTE - The SYSTEM.DAT file located in the windows SUBDIR was exported from regedit.exe. This is from a WIN2K OS > fixme:win32:PE_CreateModule Security directory ignored <NOTE - I assume this is a FIXME in the SRC> err:font:AddFontFileToList Unable to load font file "/mnt/windows/windows/Fonts/desktop.ini" err = 55 <NOTE - This file exists in the proper location so what is the error?> err:font:AddFontFileToList Already loaded font L"Garamond" L"Bold" err:font:AddFontFileToList Already loaded font L"Garamond" L"Italic" err:font:AddFontFileToList Already loaded font L"Garamond" L"Regular" err:font:AddFontFileToList Unable to load font file "/mnt/windows/windows/Fonts/modern.fon" err = 2 err:font:AddFontFileToList Unable to load font file "/mnt/windows/windows/Fonts/mtsorts.ttf" err = 2 err:font:AddFontFileToList Unable to load font file "/mnt/windows/windows/Fonts/roman.fon" err = 2 err:font:AddFontFileToList Unable to load font file "/mnt/windows/windows/Fonts/script.fon" err = 2 <NOTE - These files exist so why are they able to be loaded?> X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 22 (XDGAOpenFramebuffer) Serial number of failed request: 181 Current serial number in output stream: 181 <NOTE - What does this indicate?> I am trying to come up to speed on the use of WINE but, as everyone knows, the documentation is a little light as is the commenting of the source code. If someone could please head me in the right direction, I would greatly appreciate it. Once I have gained some additional expertise in WINE I will use my 15+ years of Windows development experience and knowledge to try and resolve some of the issues and bugs that are reported. This may take me several more weeks. I am also intending to write a technical book on WINE so will submit chapters for review to the community as the become available. Much of the information will deal with the issues the I, as a newbie, am encountering. I await the response. Crispen Scott BTW: I downloaded the source for 20020804 and, after fixing several build related problems (incorrect build order, root objections, & eliminating programs with build problems I couldn't readily resolve, i.e. widl), I had even worse problems with trying to get that version of wine to run. That is why I reverted to the latest RPM version. Some of the problems with the 20020804 build might be resolved after I see the answers to the problems I stated above. I am excited about becoming an integral part of this community but need some start-up help! Thanks! -- Crispen Scott Engineer - Software Astronautics.com 4115 Teutonia Road Milwaukee, WI 53209 Tel: 414-447-8200 x4434 C.Scott(a)Astronautics.com

2 1

RE: what's with WS_OVERLAPPED?
by Rolf Kalbermatter Aug. 16, 2002

Aug. 16, 2002

On Thu, 15 Aug 2002 "Medland, Bill" <Bill.Medland(a)accpac.com> wrote > >> On Wednesday, August 14, 2002 Ove Kaaven [mailto:ovehk(a)ping.uio.no] wrote: <snip> >> WS_OVERLAPPED is in practice considered the absence of the >> WS_POPUP and >> WS_CHILD flags, I believe. > >Thanks Ove; that'll do for a working hypothesis. (I wish Microsoft would be >consistant) > >Just for the record it is clearly more complex than that. I guess since >Microsoft wrote it we can trust Spy++ a little. I have seen spy++ declare >that a "tooltips" class window (style 0x84800000/00000088) has style >WS_OVERLAPPED whereas a "tooltips_class32" class window (style >0x84800003/00000088) doesn't. Hmm, this is just a wild guess but couldn't it be that the WS_OVERLAPPED style applies only to the lower word of the windows style. Windows coming from 16bit DOS it wouldn't be surprising if the original windows style was 16 bit only as well. Either that or Spy++ has a bug, even though you trust it so much ;-). Rolf Kalbermatter mailto:rolf.kalbermatter(a)citeng.com

1 0

Re: wine/ dlls/gdi/Makefile.in dlls/gdi/bidi16.c d ...
by Dimitrie O. Paun Aug. 16, 2002

Aug. 16, 2002

On August 15, 2002 08:42 pm, Alexandre Julliard wrote: [...] > Log message: > Moved a large number of 16-bit functions to a separate gdi16.c file. This is a great idea that I've been advocating for a loooong time now <g>. I think moving 16 bit code into separate files is cool: -- runtime efficiency: If 16 bit code is not invoked, it's not going to be paged in during execution -- code neatness: developers working on the 32-bit code (which is _the_ code in Wine) will not get distracted by silly 16-to-32-to-16 bit conversions. -- helps correctness: 16-bit code is in general a simple: 16-to-32 bit conversion call the 32-bit equivalent function 32-to-16 bit conversion Which means there is a lot of repetition, template-like coding. Any departure from the usual pattern is a *lot* more easily spotted by the naked eye if it's present in a file that does just that. -- 16-to-32 bit: we can more easily see (and fix) cases where 32 bit code calls 16 bit code. For all these reasons, I think we should have _all_ 16-bit code into separate files. Always. Who knows, maybe we can have makefiles done such a way that we can avoid compiling 16 bit code altogether! :) Even if only as a simple check that no 32 bit code calls down to 16 bit... And again, the _same_ rationale applies to xxxW & xxxA functions, but I'll not pursue this point for now ;). -- Dimi.

1 0