- wine-devel - winehq.org

Re: Mach-O Support in WineLib Loader
by Mike Hearn 21 Jul '03

21 Jul '03

Out of curiousity, how do you get around the linkage requirements of Mach-O, ie the fact that you can't both dlopen and runtime link to the same module? On Mon, 2003-07-21 at 13:08, Pierre d'Herbemont wrote: > Hi! > > This patch enables Mach-O (Darwin linker file format) support in > WineLib. > > Thanks, > > Pierre > > ModifiedFiles: > - loader/module.c > > ChangeLog: > - Add Mach-O (Darwin file format) support. >

2 1

Typelib marshalling BSTRs
by Mike Hearn 21 Jul '03

21 Jul '03

Hi, Well, I've made pretty good progress, but am a bit stuck with this problem. Basically: 003d:trace:ole:TL_Marshal parameter 1 003d:trace:ole:TL_Marshal name : L"rgszNames" 003d:trace:ole:TL_Marshal type : 26 003d:trace:ole:TL_Marshal flags : 01 003d:trace:ole:TL_MarshalType dereferencing PTR 0x52edf7d0 => 0x54331260 003d:trace:ole:TL_MarshalType dereferencing PTR 0x54331260 => 0x54331270 003d:trace:ole:TL_MarshalType marshaling byte 100 As you can see, it's marshalling IDispatch across apartment boundaries, but it gets this parameter wrong. The double dereference seems correct, but marshalling a byte is not - I think it should be a BSTR. rgszNames is a parameter of IDispatch::GetIDsFromNames, which is defined as an OLECHAR FAR* FAR* I can't figure out where the typeinfo data for IDispatch is coming from though, hence my stuckness. BTW, is this line really correct: TL_Unmarshal(pStm, pInfo, pDesc, PARAMFLAG_FIN, args, &argc, pChannel, &is_iid); shouldn't it be: TL_Unmarshal(pStm, pInfo, pDesc, PARAMFLAG_FIN, (DWORD*)&args[0], &argc, pChannel, &is_iid); as args[] is a local array declared on the stack which is then passed to the function to be invoked - otherwise how does TL_Unmarshal set the arguments? Well I tried changing it, and it made no obvious difference to my bug, but I thought I'd ask anyway. thanks -mike

4 8

question about non-standard language IDs
by Jonathan Wilson 21 Jul '03

21 Jul '03

i.e. LANG_ESPERANTO, LANG_WALON, LANG_CORNISH, LANG_WELSH, LANG_BRETON Where are these comming from? Are these Wine only or does some variant of windows (or some language list somewhere) define these? If they are Wine only (I cant find them in any MS headers), then something should be added in the places they are used to say: #ifdef LANG_WALON #include "wa.rc" #endif This will enable wine stuff (such as notepad) to compile under win32 using the MS or W32API headers.

2 2

Debugging with native DLLs
by E Lea 21 Jul '03

21 Jul '03

I'm trying to see which OLE calls a program makes under WINE when using oleaut32 natively. Obviously this native DLL doesn't have any debugging information. wine --debugmsg +ole app.exe doesn't seem to show the calls made to oleaut32. Is there are way I can get this information?

2 1

Re: Misc FAQ improvements
by Tom 21 Jul '03

21 Jul '03

Mike Hearn wrote: > > Wine is a program which allows the operation of DOS and MS >- Windows programs (Windows 3.x and Win32 executables) on UNIX. >+ Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux. > Why not just : Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems. Wine runs on BSD, Solaris, OSX as well. >@@ -440,7 +448,12 @@ > taken place. That said, the documentation is often bad, nonexistent, > and even misleading where it exists, so a fair amount of reverse > engineering has been necessary, particularly in the shell (Explorer) >- interface. >+ interface. The biggest problem facing Wine though is simply lack of >+ manpower. At one point, over 5000 people were working on Windows 2000. >+ While Wine doesn't need to replicate all of Windows (we only cover the >+ parts needed to make Windows programs work), that's still nearly 10 times >+ more people working simply on one release than have <emphasis>ever</emphasis> >+ worked on Wine, in the history of the project. > should you note at one given time ? > >@@ -1142,7 +1161,7 @@ > <answer> > <para> > Make sure you have all the VB runtime libraries installed. You may >- need to use the native DLL vbrun60.dll >+ need to use the native DLL vbrun60.dll. You can get some from dll-files.com. > some or them or just "it" if you only need the one dll ? Tom

2 2

Still Questions about building wine dll using winedump or winemaker
by dd jj 20 Jul '03

20 Jul '03

Hello, After reading winedump/README, I am still confused about how to generate a wine dll since there's no example described. Originally I followed the example described by "spec mode: Generating stub DLLs", later I found what I need is to "reimplement a Win32 DLL for Unix", I am wondering whether anyone can give a detailed sample to show how to do that... Now I have 'pingdll.dll'(generated by MS visual studio), and source code 'pingdll.h','pingdll.c'... So my final goal is to generate a wine dll - pingdll.dll.so taking place of native dll(ping.dll) completly which can be called when I run:( I also need to change the wine's config to anounce 'Dlloveride: "pingdll" = "builtin,native") % wine ./ping.exe In such a way, I can implement some functionality through linux shared library without the restriction of WINE spave if using native dll under WINE). Could you please help me out of this? Thanks a lot. -Lechun Steven Edwards <steven_ed4153(a)yahoo.com> wrote: > Now I am trying to use winemaker to build a winelib dll from windows source code, > Could anyone give some instructions about the implementation details? Or any useful info and > samples there? It seems to me the easy way to build a WINElib dll ATM is not to use Winemaker but to use winedump to create the spec and add the dll to wine/dlls/newdllname. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Re: Problam compiling wine rpm with icu support
by Shachar Shemesh 20 Jul '03

20 Jul '03

puoti wrote: >I've just installed icu 2.6 on a fresh install of Mandrake Linux 9.1, and was >compiling wine-20030709 when I noticed a configure message saying >checking if we can staticly link icu... no >and I'm wondering what I've done wrong. Should I try with icu 2.4, or must I >compile icu with some special option? Please help, for various reasons this >month's wine rpm for mandrake is already very late. > > > Sorry for the late reply. I'm CCing the mailing list, in case someone there has a better clue as to the problem. Can you please send me the config.log file? Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

1 0

something I intend working on that will help make wine "more complete"
by Jonathan Wilson 20 Jul '03

20 Jul '03

Basicly, I am going to compare what functions WINE exports from different dlls, say, kernel32.dll or whatever with what Windows XP SP1 exports from the same dll. If there is anything "missing" from the WINE version, then it needs to be added (even if its just a "fixme" stub) Would such work be any use? Has this work already been dome by someone?

5 7

Re: Typelib marshalling BSTRs
by Mike Hearn 20 Jul '03

20 Jul '03

On Sun, 2003-07-20 at 12:56, Ove Kaaven wrote: > I've mentioned before the InstallShield hack in typelib.c (the "if (1 || > ...)"), right? I suspect that you *must* disable it. or it'll probably > keep reinstalling the wrong marshaller into the registry every time you > run it. Eek, I didn't realise that hack would actually modify the registry on each run, I thought it just diverted something onto a different codepath. I'll try disabling that as well. thanks -mike

1 0

Warning on Alpha Linux
by Steven Edwards 20 Jul '03

20 Jul '03

Hello, On just about every file that is built we are getting this warrning. This is the most minor problem we have with the alpha build but I couldnt figure it out. ../../include/wine/debug.h: In function `wine_dbgstr_guid': ../../include/wine/debug.h:152: warning: cast from pointer to integer of different size ../../include/wine/debug.h:152: warning: cast from pointer to integer of different size This system is a Alpha AXP 21164. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

6 11

SMP on RedHat 9
by Vitaliy Margolen 20 Jul '03

20 Jul '03

I'm having major problems running some apps since upgrading from 7.3 to RedHat 9. I think the problem could be that my PC is dual CPU. Compiling wine with --with-ntpl does not help. Most of the time I'm getting "Access violation" or "Page fault" errors. Some time it's thread deadlocks. The worst app so far is "The Bat!". It starts on 5th 10th attempt only. But only if I'm running wine in "win98" mode. Running as "win2k" doesn't work at all. One time I tried to start The Bat! 20 times. And it failed every time in different places. Also running in limited desktop window 'Desktop="1024x768"' fails every time as well. Any suggestions? -- Best regards, Vitaliy

2 2

Re: Sync(20): ntdll/tests/rtlstr.c
by Alexandre Julliard 20 Jul '03

20 Jul '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > +/* Define the undocumented types we need here as there is no native header */ > +typedef struct _STRING { > + USHORT Length; > + USHORT MaximumLength; > + PCHAR Buffer; > +} STRING, *PSTRING; > +typedef const STRING *PCANSI_STRING; Actually there is a native winternl.h that defines these. You may need to upgrade your headers. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: just a suggestion (richedit.dll)
by Jonathan Wilson 20 Jul '03

20 Jul '03

Tom wrote: > Hello, > > You could look into riched20.dll and riched32.dll > as wine is in need of these in a bad way :) Unfortunatly, I have never programmed richedit stuff. But, if someone can provide 4 things, I might actually give it a go: 1.an existing control or library that can do the actual rendering of the text (with the colors, fonts, bold and so on) 2.an example program that shows the usage of RichEdit (something that has source code) and that will work just fine using MS richedit.dll under Wine that I can use as a test subject (something that uses straight C code and calls richedit directly, i.e. doesnt use libraries like MFC) 3.documentation on the programming interface of this dll. Having a working clone header and library file (perhaps the one from MingW32 if the licence of that file is ok) would be ideal as it would give me a place to start. and 4.details on anything I am not allowed to do to the MS dll in the corse of making this new one (I know copying stuff is forbidden because its a copyright violation but am I allowed to for example disassemble richedit.dll or step through it in a debugger to get a better idea of how it works or is that considered too legally risky?)

3 3

WINE programs question...
by Jonathan Wilson 20 Jul '03

20 Jul '03

Some of the WINE programs (for example, notepad) use resources for languages that arent present in the MingW headers, the Windows SDK or the visual C++ 6 header files (like LANG_WALON). Where did these definitions come from? Does windows actually use these definitions somehow? (Given that WINE is supposed to be a clone of the windows API, defining and using things that windows itself doesnt provide doesnt make sense) IANACWD (I Am Not A Core Wine Developer) but I would think that being able to compile the standard Wine programs and some of the non-core dlls under MingW with w32api would be a usefull test. Being able to replace e.g. comctl32.dll from MS with the wine version and seeing what breaks would be a good way to track down bugs (IMHO) Same for Wine programs (like notepad), being able to build & use em on win32 would help with bug tracking. (i.e. is this bug in WINE or in the app)

3 2

something I could work on, can someone tell me if this is something usefull or not?
by Jonathan Wilson 20 Jul '03

20 Jul '03

I could take the WINE implementation of notepad.exe (which is clearly a "clone" of an older version of notepad, probobly from Windows 98 or ME or 2000 or something) and add to it so it does the same things or similar things as the windows XP notepad. Some of the differences between XP notepad and Wine notepad: the file size limit is gone (because microsoft re-wrote the edit control to not have a size limit I guess) the "page setup" and "print setup" dialogs are combined into one dialog now with new code to handle that. A few slight differences between the UI of both (for example the Cut and Copy items are disabled if there is nothing selected, something wine notepad doesnt do) Wrap Ling Lines (in Wine notepad) is moved to a new Format menu in Windows XP notepad and is called Word Wrap. Also, the Font menu item is moved for the Format menu. Find and Find Next are moved to the Edit menu and renamed from Search and Search Next. Also, a Replace option and a Go To option (goes to a specific line) have been added. And, the Save and Save As dialogs have an "encoding" selection box that lets you select And, the print function has a "now printing" dialog. Also (obviously), the help system is better in Windows XP notepad. Basicly, I plan to implement some of these things (but I wont do the help system since thats something I know nothing about) to make wine notepad more like windows XP notepad (in particular, adding the Replace and Go To features) I am taking this on because I want to improve my skills at working with the Win32 API. Basicly, I want to know: 1.is this something usefull to the Wine project? and 2.is there anything I should avoid doing for whatever reason? (for example, are there things I cant do because they would violate MS IP or something)

4 3

RE: Web: Fix the WWN intros
by Brian Vincent (C) 19 Jul '03

19 Jul '03

> So why do we still say (the Un*x Windows emulator). ? If it's > *not* a emulator ? The only reason I ever left that in there is because that's the way Eric had it. (And he can always just blame it on being a native .fr speaker.) Maybe I'll change it this week to something more appropriate. I've always hated saying something like "an implementation of the Win32 API for Un*x", it sounds too technical. Emulator, while wrong in a technical sense, does get the point across. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

3 2

DirectSound problems
by Mike Hearn 19 Jul '03

19 Jul '03

Hi, Just trying out EV Nova (a game), I get lots and lots of errors like this: err:dsound:DSOUND_MixOne underrun on sound buffer 0x5579a110 fixme:dsound:DSOUND_MixOne problem with underrun detection (mixlen=15872 < primary_done=21168) fixme:dsound:DSOUND_MixOne problem with underrun detection (mixlen=15872 < primary_done=17640) fixme:dsound:DSOUND_MixOne problem with underrun detection (mixlen=15872 < primary_done=17640) fixme:dsound:DSOUND_MixOne problem with underrun detection (mixlen=15872 < primary_done=21168) err:dsound:DSOUND_MixOne underrun on sound buffer 0x5579a110 and the soundy is choppy, drops out and is distorted. Yes, I am forcing HEL emulation. What sort of thing causes these errors? Any idea what I can do to fix it? thanks -mike

1 0

Re: just a suggestion (richedit.dll)
by Robert Shearman 19 Jul '03

19 Jul '03

> > You could look into riched20.dll and riched32.dll > > as wine is in need of these in a bad way :) I submitted a patch to enhance the functionality of richedit a while ago, although it wasn't accepted (probably because I hadn't finished it). I have abandoned it for the moment so feel free to continue with the work. If richedit doesn't appeal to you, maybe you could implement a few Var* functions in oleaut32. These are particularly important to VB users, and can be tested very easily since the functions have no side effects. Rob

1 0

2 questions about the WINE multi-line edit control
by Jonathan Wilson 19 Jul '03

19 Jul '03

1.does it handle UNICODE yet? and 2.is there any limit to the size of the data that can be stored in one?

1 0

Re: Locales with the same language
by Dmitry Timoshkov 19 Jul '03

19 Jul '03

"Marcelo Duarte" <wine-devel(a)bol.com.br> wrote: > If I understanded, people that have LANG=fr_CA or pt_PT, etc (non-default > SUBLANG), will have to use English? If there are no resources with SUBLANGE_DEFAULT, then yes. > Then the correct will be change all resources with SUBLANGE_DEFAULT to > SUBLANG_NEUTRAL until someone localize them? > I can modify this if is the correct. Actually there was a completely opposite patch committed recently: 2003-01-05 Shachar Shemesh <winecode(a)sun.consumer.org.il> Change the SUBLANG_NEUTRAL clause in all winelib applications to SUBLANG_DEFAULT, as they should be. I vote to revert that patch. -- Dmitry.

3 10

Re: Sync (32): winbuild msvcrt
by Alexandre Julliard 19 Jul '03

19 Jul '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > - Functions exported by name only should not be given ordinal numbers > in the .def output, so that link.exe can fill up empy ordinal slots > and create a valid export table. Not doing this leads to an incorrect > export table without any warnings or errors during the build. We use the ordinal to generate the proper hint in the import table, so this is not a good idea. > - We need the stub functions to be present in the final dll file, or > our ordinal functions cannot be accessed. This is because link.exe > requires that all ordinals be present in order to generate a correct > ordinal export table. > This in turn requires that the .spec.c files compile correctly under > msvc, in order to get the stub functions included in the link. > However, we obviously don't need the pe header or export tables that > winebuild generates, since link.exe (and any other PE linker, for > that matter) does this work for us. The .spec.c file must not be used on Windows IMO. If the MS linker is really that brain damaged then you'll need to make sure you have valid functions for all entry points, or use a better linker (mingw should work AFAIK). > - Several symbols are expected to be exported as private and by name > only, or they generate warnings when creating the .lib and .exp files > for the dll. This requires identifying said symbols, and correctly > generating and parsing the PRIVATE flag in .def files. I'd suggest specifying that in the spec file instead of hard-coding the symbols in winebuild. Also please try to split your patch, there are clearly different changes in there, it would be a lot easier to analyze them independently. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Sync (32): winbuild msvcrt
by Steven Edwards 19 Jul '03

19 Jul '03

--- Jon Griffiths <jon_p_griffiths(a)yahoo.com> wrote: > > +tools/winebuild/build.h tools/winebuild/import.c > tools/winebuild/parser.ctools/winebuild/spec16.c > tools/winebuild/spec32.c > Export '@'-functions and forwards > Support PRIVATE and optional ordinal numbers in .def files > Allow generated files to build correct dlls under msvc > Clean up the generated output Using your patch I am now getting the following errors in linking of shlwapi.dll dllwrap -k --def shlwapi.spec.def -o shlwapi.dll assoc.o clist.o istream.o ordi nal.o path.o reg.o regstream.o shlwapi_main.o string.o thread.o url.o wsprintf.o shlwapi.dll.dbg.o -L../../dlls -lole32 -luser32 -lgdi32 -ladvapi32 -lkernel3 2 -L../../libs/wine -lwine -L../../libs/uuid -lwine_uuid -L../../libs/unicode -l wine_unicode -L../../libs/port -lwine_port -lm shlwapi.exp(.edata+0xc4):fake: undefined reference to `f1' shlwapi.exp(.edata+0xc8):fake: undefined reference to `f2' shlwapi.exp(.edata+0xcc):fake: undefined reference to `f3' shlwapi.exp(.edata+0xd0):fake: undefined reference to `f4' shlwapi.exp(.edata+0xd4):fake: undefined reference to `f5' shlwapi.exp(.edata+0xd8):fake: undefined reference to `__wine_stub_shlwapi_dll_4 2' shlwapi.exp(.edata+0xdc):fake: undefined reference to `f6' shlwapi.exp(.edata+0xe0):fake: undefined reference to `f7' shlwapi.exp(.edata+0xe4):fake: undefined reference to `f8' shlwapi.exp(.edata+0xe8):fake: undefined reference to `f9' shlwapi.exp(.edata+0xec):fake: undefined reference to `f10' shlwapi.exp(.edata+0xf0):fake: undefined reference to `f11' shlwapi.exp(.edata+0xf4):fake: undefined reference to `f12' shlwapi.exp(.edata+0xf8):fake: undefined reference to `f13' shlwapi.exp(.edata+0xfc):fake: undefined reference to `f14' shlwapi.exp(.edata+0x100):fake: undefined reference to `f15' shlwapi.exp(.edata+0x104):fake: undefined reference to `f16' shlwapi.exp(.edata+0x108):fake: undefined reference to `f17' shlwapi.exp(.edata+0x10c):fake: undefined reference to `f18' shlwapi.exp(.edata+0x110):fake: undefined reference to `f19' shlwapi.exp(.edata+0x114):fake: undefined reference to `f20' shlwapi.exp(.edata+0x118):fake: undefined reference to `__wine_stub_shlwapi_dll_ 58' shlwapi.exp(.edata+0x11c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 59' shlwapi.exp(.edata+0x120):fake: undefined reference to `f21' shlwapi.exp(.edata+0x124):fake: undefined reference to `f22' shlwapi.exp(.edata+0x128):fake: undefined reference to `f23' shlwapi.exp(.edata+0x12c):fake: undefined reference to `f24' shlwapi.exp(.edata+0x130):fake: undefined reference to `f25' shlwapi.exp(.edata+0x134):fake: undefined reference to `f26' shlwapi.exp(.edata+0x138):fake: undefined reference to `f27' shlwapi.exp(.edata+0x13c):fake: undefined reference to `f28' shlwapi.exp(.edata+0x140):fake: undefined reference to `f29' shlwapi.exp(.edata+0x144):fake: undefined reference to `f30' shlwapi.exp(.edata+0x148):fake: undefined reference to `f31' shlwapi.exp(.edata+0x14c):fake: undefined reference to `f32' shlwapi.exp(.edata+0x150):fake: undefined reference to `f33' shlwapi.exp(.edata+0x154):fake: undefined reference to `f34' shlwapi.exp(.edata+0x15c):fake: undefined reference to `f35' shlwapi.exp(.edata+0x160):fake: undefined reference to `f36' shlwapi.exp(.edata+0x164):fake: undefined reference to `f37' shlwapi.exp(.edata+0x168):fake: undefined reference to `f38' shlwapi.exp(.edata+0x16c):fake: undefined reference to `f39' shlwapi.exp(.edata+0x170):fake: undefined reference to `f40' shlwapi.exp(.edata+0x174):fake: undefined reference to `f41' shlwapi.exp(.edata+0x178):fake: undefined reference to `f42' shlwapi.exp(.edata+0x17c):fake: undefined reference to `f43' shlwapi.exp(.edata+0x180):fake: undefined reference to `f44' shlwapi.exp(.edata+0x184):fake: undefined reference to `f45' shlwapi.exp(.edata+0x188):fake: undefined reference to `f46' shlwapi.exp(.edata+0x18c):fake: undefined reference to `f47' shlwapi.exp(.edata+0x190):fake: undefined reference to `f48' shlwapi.exp(.edata+0x194):fake: undefined reference to `f49' shlwapi.exp(.edata+0x198):fake: undefined reference to `f50' shlwapi.exp(.edata+0x19c):fake: undefined reference to `f51' shlwapi.exp(.edata+0x1a0):fake: undefined reference to `f52' shlwapi.exp(.edata+0x1a4):fake: undefined reference to `f53' shlwapi.exp(.edata+0x1a8):fake: undefined reference to `f54' shlwapi.exp(.edata+0x1ac):fake: undefined reference to `f55' shlwapi.exp(.edata+0x1b0):fake: undefined reference to `f56' shlwapi.exp(.edata+0x1b4):fake: undefined reference to `f57' shlwapi.exp(.edata+0x1b8):fake: undefined reference to `f58' shlwapi.exp(.edata+0x1bc):fake: undefined reference to `f59' shlwapi.exp(.edata+0x1c0):fake: undefined reference to `f60' shlwapi.exp(.edata+0x1c4):fake: undefined reference to `f61' shlwapi.exp(.edata+0x1c8):fake: undefined reference to `f62' shlwapi.exp(.edata+0x1cc):fake: undefined reference to `f63' shlwapi.exp(.edata+0x1d0):fake: undefined reference to `f64' shlwapi.exp(.edata+0x1d4):fake: undefined reference to `f65' shlwapi.exp(.edata+0x1d8):fake: undefined reference to `f66' shlwapi.exp(.edata+0x1dc):fake: undefined reference to `f67' shlwapi.exp(.edata+0x1e0):fake: undefined reference to `f68' shlwapi.exp(.edata+0x1e4):fake: undefined reference to `f69' shlwapi.exp(.edata+0x1e8):fake: undefined reference to `f70' shlwapi.exp(.edata+0x1ec):fake: undefined reference to `f71' shlwapi.exp(.edata+0x1f0):fake: undefined reference to `f72' shlwapi.exp(.edata+0x1f4):fake: undefined reference to `f73' shlwapi.exp(.edata+0x1f8):fake: undefined reference to `f74' shlwapi.exp(.edata+0x1fc):fake: undefined reference to `f75' shlwapi.exp(.edata+0x200):fake: undefined reference to `f76' shlwapi.exp(.edata+0x204):fake: undefined reference to `f77' shlwapi.exp(.edata+0x208):fake: undefined reference to `f78' shlwapi.exp(.edata+0x20c):fake: undefined reference to `f79' shlwapi.exp(.edata+0x210):fake: undefined reference to `f80' shlwapi.exp(.edata+0x214):fake: undefined reference to `f81' shlwapi.exp(.edata+0x218):fake: undefined reference to `f82' shlwapi.exp(.edata+0x21c):fake: undefined reference to `f83' shlwapi.exp(.edata+0x220):fake: undefined reference to `f84' shlwapi.exp(.edata+0x224):fake: undefined reference to `f85' shlwapi.exp(.edata+0x228):fake: undefined reference to `f86' shlwapi.exp(.edata+0x22c):fake: undefined reference to `f87' shlwapi.exp(.edata+0x230):fake: undefined reference to `f88' shlwapi.exp(.edata+0x234):fake: undefined reference to `f89' shlwapi.exp(.edata+0x238):fake: undefined reference to `f90' shlwapi.exp(.edata+0x23c):fake: undefined reference to `f91' shlwapi.exp(.edata+0x240):fake: undefined reference to `f92' shlwapi.exp(.edata+0x244):fake: undefined reference to `f93' shlwapi.exp(.edata+0x248):fake: undefined reference to `f94' shlwapi.exp(.edata+0x24c):fake: undefined reference to `f95' shlwapi.exp(.edata+0x250):fake: undefined reference to `f96' shlwapi.exp(.edata+0x254):fake: undefined reference to `f97' shlwapi.exp(.edata+0x25c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 139' shlwapi.exp(.edata+0x260):fake: undefined reference to `f98' shlwapi.exp(.edata+0x264):fake: undefined reference to `f99' shlwapi.exp(.edata+0x268):fake: undefined reference to `f100' shlwapi.exp(.edata+0x26c):fake: undefined reference to `f101' shlwapi.exp(.edata+0x270):fake: undefined reference to `f102' shlwapi.exp(.edata+0x274):fake: undefined reference to `f103' shlwapi.exp(.edata+0x278):fake: undefined reference to `f104' shlwapi.exp(.edata+0x27c):fake: undefined reference to `f105' shlwapi.exp(.edata+0x280):fake: undefined reference to `f106' shlwapi.exp(.edata+0x284):fake: undefined reference to `f107' shlwapi.exp(.edata+0x288):fake: undefined reference to `f108' shlwapi.exp(.edata+0x2ac):fake: undefined reference to `f109' shlwapi.exp(.edata+0x2b0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 160' shlwapi.exp(.edata+0x2b4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 161' shlwapi.exp(.edata+0x2e4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 173' shlwapi.exp(.edata+0x2f4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 177' shlwapi.exp(.edata+0x2f8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 178' shlwapi.exp(.edata+0x2fc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 179' shlwapi.exp(.edata+0x314):fake: undefined reference to `__wine_stub_shlwapi_dll_ 185' shlwapi.exp(.edata+0x318):fake: undefined reference to `__wine_stub_shlwapi_dll_ 186' shlwapi.exp(.edata+0x320):fake: undefined reference to `__wine_stub_shlwapi_dll_ 188' shlwapi.exp(.edata+0x328):fake: undefined reference to `__wine_stub_shlwapi_dll_ 190' shlwapi.exp(.edata+0x32c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 191' shlwapi.exp(.edata+0x330):fake: undefined reference to `__wine_stub_shlwapi_dll_ 192' shlwapi.exp(.edata+0x338):fake: undefined reference to `__wine_stub_shlwapi_dll_ 194' shlwapi.exp(.edata+0x33c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 195' shlwapi.exp(.edata+0x340):fake: undefined reference to `__wine_stub_shlwapi_dll_ 196' shlwapi.exp(.edata+0x348):fake: undefined reference to `__wine_stub_shlwapi_dll_ 198' shlwapi.exp(.edata+0x350):fake: undefined reference to `__wine_stub_shlwapi_dll_ 200' shlwapi.exp(.edata+0x36c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 207' shlwapi.exp(.edata+0x390):fake: undefined reference to `__wine_stub_shlwapi_dll_ 216' shlwapi.exp(.edata+0x3a0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 220' shlwapi.exp(.edata+0x3a4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 221' shlwapi.exp(.edata+0x3b4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 225' shlwapi.exp(.edata+0x3b8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 226' shlwapi.exp(.edata+0x3bc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 227' shlwapi.exp(.edata+0x3c0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 228' shlwapi.exp(.edata+0x3c4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 229' shlwapi.exp(.edata+0x3c8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 230' shlwapi.exp(.edata+0x3cc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 231' shlwapi.exp(.edata+0x3d0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 232' shlwapi.exp(.edata+0x3d4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 233' shlwapi.exp(.edata+0x3d8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 234' shlwapi.exp(.edata+0x3dc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 235' shlwapi.exp(.edata+0x3e8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 238' shlwapi.exp(.edata+0x3f8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 242' shlwapi.exp(.edata+0x3fc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 243' shlwapi.exp(.edata+0x400):fake: undefined reference to `__wine_stub_shlwapi_dll_ 244' shlwapi.exp(.edata+0x404):fake: undefined reference to `__wine_stub_shlwapi_dll_ 245' shlwapi.exp(.edata+0x408):fake: undefined reference to `__wine_stub_shlwapi_dll_ 246' shlwapi.exp(.edata+0x40c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 247' shlwapi.exp(.edata+0x410):fake: undefined reference to `__wine_stub_shlwapi_dll_ 248' shlwapi.exp(.edata+0x414):fake: undefined reference to `__wine_stub_shlwapi_dll_ 249' shlwapi.exp(.edata+0x418):fake: undefined reference to `__wine_stub_shlwapi_dll_ 250' shlwapi.exp(.edata+0x41c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 251' shlwapi.exp(.edata+0x420):fake: undefined reference to `__wine_stub_shlwapi_dll_ 252' shlwapi.exp(.edata+0x430):fake: undefined reference to `__wine_stub_shlwapi_dll_ 256' shlwapi.exp(.edata+0x434):fake: undefined reference to `__wine_stub_shlwapi_dll_ 257' shlwapi.exp(.edata+0x438):fake: undefined reference to `__wine_stub_shlwapi_dll_ 258' shlwapi.exp(.edata+0x43c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 259' shlwapi.exp(.edata+0x440):fake: undefined reference to `__wine_stub_shlwapi_dll_ 260' shlwapi.exp(.edata+0x444):fake: undefined reference to `__wine_stub_shlwapi_dll_ 261' shlwapi.exp(.edata+0x448):fake: undefined reference to `__wine_stub_shlwapi_dll_ 262' shlwapi.exp(.edata+0x44c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 263' shlwapi.exp(.edata+0x450):fake: undefined reference to `__wine_stub_shlwapi_dll_ 264' shlwapi.exp(.edata+0x454):fake: undefined reference to `__wine_stub_shlwapi_dll_ 265' shlwapi.exp(.edata+0x470):fake: undefined reference to `__wine_stub_shlwapi_dll_ 272' shlwapi.exp(.edata+0x474):fake: undefined reference to `__wine_stub_shlwapi_dll_ 273' shlwapi.exp(.edata+0x478):fake: undefined reference to `__wine_stub_shlwapi_dll_ 274' shlwapi.exp(.edata+0x47c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 275' shlwapi.exp(.edata+0x484):fake: undefined reference to `__wine_stub_shlwapi_dll_ 277' shlwapi.exp(.edata+0x48c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 279' shlwapi.exp(.edata+0x490):fake: undefined reference to `__wine_stub_shlwapi_dll_ 280' shlwapi.exp(.edata+0x49c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 283' shlwapi.exp(.edata+0x4a4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 285' shlwapi.exp(.edata+0x4a8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 286' shlwapi.exp(.edata+0x4b0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 288' shlwapi.exp(.edata+0x4b8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 290' shlwapi.exp(.edata+0x4bc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 291' shlwapi.exp(.edata+0x4c0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 292' shlwapi.exp(.edata+0x4c4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 293' shlwapi.exp(.edata+0x4d0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 296' shlwapi.exp(.edata+0x4d4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 297' shlwapi.exp(.edata+0x4d8):fake: undefined reference to `f110' shlwapi.exp(.edata+0x4e0):fake: undefined reference to `f111' shlwapi.exp(.edata+0x4e4):fake: undefined reference to `f112' shlwapi.exp(.edata+0x4e8):fake: undefined reference to `f113' shlwapi.exp(.edata+0x4ec):fake: undefined reference to `f114' shlwapi.exp(.edata+0x4f0):fake: undefined reference to `f115' shlwapi.exp(.edata+0x4f4):fake: undefined reference to `f116' shlwapi.exp(.edata+0x4f8):fake: undefined reference to `f117' shlwapi.exp(.edata+0x4fc):fake: undefined reference to `f118' shlwapi.exp(.edata+0x500):fake: undefined reference to `f119' shlwapi.exp(.edata+0x504):fake: undefined reference to `f120' shlwapi.exp(.edata+0x508):fake: undefined reference to `f121' shlwapi.exp(.edata+0x50c):fake: undefined reference to `f122' shlwapi.exp(.edata+0x510):fake: undefined reference to `f123' shlwapi.exp(.edata+0x518):fake: undefined reference to `f124' shlwapi.exp(.edata+0x51c):fake: undefined reference to `f125' shlwapi.exp(.edata+0x520):fake: undefined reference to `__wine_stub_shlwapi_dll_ 316' shlwapi.exp(.edata+0x524):fake: undefined reference to `__wine_stub_shlwapi_dll_ 317' shlwapi.exp(.edata+0x52c):fake: undefined reference to `f126' shlwapi.exp(.edata+0x558):fake: undefined reference to `__wine_stub_shlwapi_dll_ 330' shlwapi.exp(.edata+0x55c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 331' shlwapi.exp(.edata+0x560):fake: undefined reference to `f127' shlwapi.exp(.edata+0x578):fake: undefined reference to `f128' shlwapi.exp(.edata+0x57c):fake: undefined reference to `f129' shlwapi.exp(.edata+0x580):fake: undefined reference to `f130' shlwapi.exp(.edata+0x584):fake: undefined reference to `f131' shlwapi.exp(.edata+0x58c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 343' shlwapi.exp(.edata+0x590):fake: undefined reference to `__wine_stub_shlwapi_dll_ 344' shlwapi.exp(.edata+0x594):fake: undefined reference to `__wine_stub_shlwapi_dll_ 345' shlwapi.exp(.edata+0x59c):fake: undefined reference to `f132' shlwapi.exp(.edata+0x5a0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 348' shlwapi.exp(.edata+0x5a4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 349' shlwapi.exp(.edata+0x5b4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 353' shlwapi.exp(.edata+0x5b8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 354' shlwapi.exp(.edata+0x5bc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 355' shlwapi.exp(.edata+0x5cc):fake: undefined reference to `f133' shlwapi.exp(.edata+0x5d0):fake: undefined reference to `f134' shlwapi.exp(.edata+0x5d4):fake: undefined reference to `f135' shlwapi.exp(.edata+0x5d8):fake: undefined reference to `f136' shlwapi.exp(.edata+0x5dc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 363' shlwapi.exp(.edata+0x5e4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 365' shlwapi.exp(.edata+0x5e8):fake: undefined reference to `f137' shlwapi.exp(.edata+0x5ec):fake: undefined reference to `f138' shlwapi.exp(.edata+0x5f0):fake: undefined reference to `f139' shlwapi.exp(.edata+0x5f4):fake: undefined reference to `f140' shlwapi.exp(.edata+0x5fc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 371' shlwapi.exp(.edata+0x600):fake: undefined reference to `__wine_stub_shlwapi_dll_ 372' shlwapi.exp(.edata+0x604):fake: undefined reference to `__wine_stub_shlwapi_dll_ 373' shlwapi.exp(.edata+0x608):fake: undefined reference to `__wine_stub_shlwapi_dll_ 374' shlwapi.exp(.edata+0x60c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 375' shlwapi.exp(.edata+0x61c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 379' shlwapi.exp(.edata+0x620):fake: undefined reference to `__wine_stub_shlwapi_dll_ 380' shlwapi.exp(.edata+0x63c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 387' shlwapi.exp(.edata+0x640):fake: undefined reference to `__wine_stub_shlwapi_dll_ 388' shlwapi.exp(.edata+0x650):fake: undefined reference to `__wine_stub_shlwapi_dll_ 392' shlwapi.exp(.edata+0x654):fake: undefined reference to `f141' shlwapi.exp(.edata+0x658):fake: undefined reference to `f142' shlwapi.exp(.edata+0x65c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 395' shlwapi.exp(.edata+0x660):fake: undefined reference to `__wine_stub_shlwapi_dll_ 396' shlwapi.exp(.edata+0x664):fake: undefined reference to `__wine_stub_shlwapi_dll_ 397' shlwapi.exp(.edata+0x668):fake: undefined reference to `__wine_stub_shlwapi_dll_ 398' shlwapi.exp(.edata+0x684):fake: undefined reference to `__wine_stub_shlwapi_dll_ 405' shlwapi.exp(.edata+0x68c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 407' shlwapi.exp(.edata+0x690):fake: undefined reference to `__wine_stub_shlwapi_dll_ 408' shlwapi.exp(.edata+0x694):fake: undefined reference to `__wine_stub_shlwapi_dll_ 409' shlwapi.exp(.edata+0x698):fake: undefined reference to `__wine_stub_shlwapi_dll_ 410' shlwapi.exp(.edata+0x69c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 411' shlwapi.exp(.edata+0x6a0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 412' shlwapi.exp(.edata+0x6a8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 414' shlwapi.exp(.edata+0x6ac):fake: undefined reference to `__wine_stub_shlwapi_dll_ 415' shlwapi.exp(.edata+0x6b0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 416' shlwapi.exp(.edata+0x6b4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 417' shlwapi.exp(.edata+0x6bc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 419' shlwapi.exp(.edata+0x6c0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 420' shlwapi.exp(.edata+0x6c4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 421' shlwapi.exp(.edata+0x6d4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 425' shlwapi.exp(.edata+0x6d8):fake: undefined reference to `__wine_stub_shlwapi_dll_ 426' shlwapi.exp(.edata+0x6dc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 427' shlwapi.exp(.edata+0x6e0):fake: undefined reference to `f143' shlwapi.exp(.edata+0x6e4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 429' shlwapi.exp(.edata+0x6f0):fake: undefined reference to `__wine_stub_shlwapi_dll_ 432' shlwapi.exp(.edata+0x6f4):fake: undefined reference to `__wine_stub_shlwapi_dll_ 433' shlwapi.exp(.edata+0x6f8):fake: undefined reference to `f144' shlwapi.exp(.edata+0x6fc):fake: undefined reference to `__wine_stub_shlwapi_dll_ 435' shlwapi.exp(.edata+0x708):fake: undefined reference to `__wine_stub_shlwapi_dll_ 438' shlwapi.exp(.edata+0x70c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 439' shlwapi.exp(.edata+0x710):fake: undefined reference to `__wine_stub_shlwapi_dll_ 440' shlwapi.exp(.edata+0x714):fake: undefined reference to `__wine_stub_shlwapi_dll_ 441' shlwapi.exp(.edata+0x718):fake: undefined reference to `f145' shlwapi.exp(.edata+0x71c):fake: undefined reference to `f146' shlwapi.exp(.edata+0x720):fake: undefined reference to `f147' shlwapi.exp(.edata+0x728):fake: undefined reference to `__wine_stub_shlwapi_dll_ 446' shlwapi.exp(.edata+0xb28):fake: undefined reference to `__wine_stub_shlwapi_dll_ 450' shlwapi.exp(.edata+0xb2c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 451' shlwapi.exp(.edata+0xb30):fake: undefined reference to `__wine_stub_shlwapi_dll_ 452' shlwapi.exp(.edata+0xb34):fake: undefined reference to `__wine_stub_shlwapi_dll_ 453' shlwapi.exp(.edata+0xb38):fake: undefined reference to `__wine_stub_shlwapi_dll_ 556' shlwapi.exp(.edata+0xb3c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 557' shlwapi.exp(.edata+0xb48):fake: undefined reference to `__wine_stub_shlwapi_dll_ 598' shlwapi.exp(.edata+0xb4c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 599' shlwapi.exp(.edata+0xb50):fake: undefined reference to `__wine_stub_shlwapi_dll_ 600' shlwapi.exp(.edata+0xb54):fake: undefined reference to `__wine_stub_shlwapi_dll_ 601' shlwapi.exp(.edata+0xb58):fake: undefined reference to `__wine_stub_shlwapi_dll_ 602' shlwapi.exp(.edata+0xb5c):fake: undefined reference to `__wine_stub_shlwapi_dll_ 603' shlwapi.exp(.edata+0xb60):fake: undefined reference to `__wine_stub_shlwapi_dll_ 607' shlwapi.exp(.edata+0xb64):fake: undefined reference to `__wine_stub_shlwapi_dll_ 608' shlwapi.exp(.edata+0xb68):fake: undefined reference to `__wine_stub_shlwapi_dll_ 627' C:\mingw\bin\dllwrap.exe: C:\mingw\bin\gcc exited with status 1 make: *** [shlwapi.dll] Error 1 isolation@PH33R /g/src/wine-dev/wine/dlls/shlwapi $ __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

1 0

Re: Sync (32): winbuild msvcrt
by Steven Edwards 19 Jul '03

19 Jul '03

--- Jon Griffiths <jon_p_griffiths(a)yahoo.com> wrote: > This patch addresses most of the existing issues building Wines dlls > as native win32 dlls using msvc, namely: > > - We need to export forwards from the .def file. > > - We need to export any implemented ordinal functions and mark them > as NONAME. > > - Functions exported by name only should not be given ordinal numbers > in the .def output, so that link.exe can fill up empy ordinal slots > and create a valid export table. Not doing this leads to an incorrect > export table without any warnings or errors during the build. > > - This means that parsing the .def files has to treat ordinal numbers > as optional for named functions (just as link.exe/lib.exe do). This > concurs with the MSDN documentation for the .def file syntax. > > - We need the stub functions to be present in the final dll file, or > our ordinal functions cannot be accessed. This is because link.exe > requires that all ordinals be present in order to generate a correct > ordinal export table. > This in turn requires that the .spec.c files compile correctly under > msvc, in order to get the stub functions included in the link. > However, we obviously don't need the pe header or export tables that > winebuild generates, since link.exe (and any other PE linker, for > that matter) does this work for us. > > - Fixing the .spec.c file requires that we use RaiseException from > kernel32 instead of RtlRaiseException from ntdll, since no import > library is provided for ntdll by default. This can be fixed later but > requires large changes to the build environment to get dependencies > correct (we should generate our .def files from our .spec files when > building with msvc, just as we do under unix; we would then use our > own ntdll.def to link to ntdll functions). > > - Several symbols are expected to be exported as private and by name > only, or they generate warnings when creating the .lib and .exp files > for the dll. This requires identifying said symbols, and correctly > generating and parsing the PRIVATE flag in .def files. > > - Debug channels should be registered, this is accomplished using the > CRT static constructor data segment. This allows linking to proceed > by finding the debug channels, and (with upcoming patches) will allow > debug msgs to be printed. > > - The added #ifdefs required for msvc made the output look more crufy > than it was, so I reduced the number of these with some macros at the > start of the generated output files. > > Using this patch I can build a correctly functioning native > shlwapi.dll which will load and run under Windows, and as a native > dll under Wine. This includes being able to GetProcAddress() the > ordinal functions and call them. It should now be possible to create > distributable native trace dlls that can be installed under windows, > giving us non-instrusive monitoring of the internals of calls between > applications and native dlls. > > Two remaining issues are what to do with register functions and 16 > bit dlls. > > Please comment if there are any issues with respect to cygwin that > occur after applying this patch. I imagine the ReactOS folks might be > interested as well; does anyone know how they build their dlls at > present? This is great. I have not had a chance to test this patch as the ReactOS build system differs from the standard WINE + Mingw and MSYS build. I am currently having a problem with using WINE dlls we build with ReactOS due to the fact the ReactOS build system is stupid and cannot properly use gcc or binutils to generate a dll with the .def file winebuild already creates. Using MSYS+Mingw I have been able to use shlwapi and others from WINE already but dllwrap takes care of some of the short commings in our autogenerated def's. I will attempt to test tonight with the current Winehq CVS and Msys. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

1 0

Re: Typelib marshalling BSTRs
by Robert Shearman 19 Jul '03

19 Jul '03

> Subject: Re: Typelib marshalling BSTRs > From: Mike Hearn <mike(a)theoretic.com> > To: Kelly Leahy <kellyleahy(a)swbell.net> > Cc: wine-devel(a)winehq.com > Date: 18 Jul 2003 17:24:07 +0100 > > On Fri, 2003-07-18 at 17:08, Kelly Leahy wrote: > > weird. are the "type" and "flags" correct? > > They appear to be. Type 26 is VT_PTR, flags 1 == in param > > > bstr isn't right, since it's an array of bstr (or more > precisely array of > > OLECHAR FAR* - which may also be causing problems) - though I > may be wrong > > if it marshals them one by one. > > Yeah, I had a thinko. It's supposed to be an array of bstr, but even > simply marshalling the first element correctly would be good :) No, it is supposed to be OLECHAR which is different (in terms of VARIANT types) to BSTR. BSTR implies a size field at the start of the array. > HRESULT GetIDsOfNames( > [in] REFIID riid, > [in, size_is(cNames)] LPOLESTR *rgszNames, > [in] UINT cNames, > [in] LCID lcid, > [out, size_is(cNames)] DISPID *rgDispId); > > Maybe the size_is() field should be noticed somewhere in the marshalling > code. I don't know where such information would surface though, it's not > in the flags, there is no PARAMFLAG constant for it. There is no way of expressing size_of once the IDL is in TypeLib form. It is effectively ignored. However, it is used in the proxy and stub functions generated. I'm not sure what interface it is marshalling here, but your error would appear to be elsewhere. Using a test program which dumps type libraries, I can confirm that LPOLESTR * is compiled to CHAR** on Windows. I can't quite seem why, but it appears that the marshalling that is being done is correct, at least for the information available to it. Rob

3 3

Re: [ros-kernel] wine/dlls/ole32/compobj.c
by Steven Edwards 18 Jul '03

18 Jul '03

> wine/dlls/ole32/compobj.c > I'm reading through this file and came across this function: > > COMPOBJ_DllList_FreeUnused > > In particular I noticed this: > > DllCanUnloadNow = (DllCanUnloadNowFunc) GetProcAddress(curr->hLibrary, "DllCanUnloadNow"); > > Every time WINE is checking for DLLs to unload, it's > loading the DLL's CanUnloadNow function again. I don't yet > know how often this is done, but wouldn't it be better to > go ahead and store the DllCanUnloadNow function pointer in > the OpenDll struct? We can do this. I have CC'd this to ask wine-devel why this is done. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

1 0

Re: Sync(18): msvcrt cpp exceptions
by Alexandre Julliard 18 Jul '03

18 Jul '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > +dlls/msvcrt/cppexcept.c > strip dump code when NO_TRACE_MSGS is defined The compiler should optimize this out, and even if it doesn't that's no big deal. It certainly doesn't justify adding #ifdefs. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: WWN: wn20030718_179.xml
by Dimitrie O. Paun 18 Jul '03

18 Jul '03

On July 17, 2003 07:24 pm, Brian Vincent wrote: > <intro> <p>This is the 179th release of the weekly Wine Weekly News > publication. It's main goal is to ponder why I never knew I there was a ^^^^^^^^ Eh? > real gold mine down the street from where I live. It also serves inform you ^^^^^^^^^^^ Ditto :) > of what's going on around Wine. -- Dimi.

1 0

Question about Own generated winelib dll using winedump
by dd jj 18 Jul '03

18 Jul '03

Hello everyone, I followed instructions from winedump/README: ./pingdll_install <wine-path> cd <wine-path> autoconf ./configure make depend && make make install But didn't execute the last command make install, (It seems I crashed WINE after that) I still get my own generated winelib dll - ping.dll.so :) But when I try to run my application, it shows the error: err:module:imort_dll No implementation for pingdll.dll._quicktest@4 imported from C:\ping\ping_slave.exe, setting to Oxdeadbeef. The window native dll works fine under wine, but now it seems I didn't generate the winelib dll corretly? or any trick to make it work? Do I must run make install... ? Thanks a lot! -Lechun --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Re: Sync (37): shlwapi regstream
by Alexandre Julliard 18 Jul '03

18 Jul '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > +#ifdef __WINE_USE_MSVCRT > +#define FS_I64 "%I64d" > +#define FS_UI64 "%I64u" > +#else > +#define FS_I64 "%lld" > +#define FS_UI64 "%llu" > +#endif Please don't do that, it's not portable anyway. Simply print high and low part separately with something like "%lx%08lx". -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Sync (31): winbuild relay
by Alexandre Julliard 18 Jul '03

18 Jul '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > +tools/winebuild/relay.c > Remove redundant multiple calls to fprintf() There's no reason to do that. The existing code is just fine, and much easier to modify. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Sync (44): documentation/Makefile.in
by Vincent Béron 18 Jul '03

18 Jul '03

Le jeu 17/07/2003 à 14:22, Jon Griffiths a écrit : > Hi, > > I've never had any luck with the default make rules for the html > books. I'm running (more or less) Mandrake 8, and it seems that > db2html from that distribution doesn't respect the current directory > when computing relative paths, so it always fails to find the .dsl > file and bombs. The following patch fixes this for me, and hopefully > should work for everyone else too. Yea, I know. You're not the only one. > - $(DB2HTML) -d $(SRCDIR)/default.dsl -o $* $< > + $(DB2HTML) -d `pwd $(SRCDIR)`/default.dsl $< Why do you keep $(SRCDIR) after pwd? man bash and man pwd both say nothing about giving pwd a path... What's really needed is either use our own db2html (but that was struck down already in the past), or test in configure the behaviour of the system's db2html and act accordingly. Also, ideally there'd be only one standard for db2htmls... Vincent

3 2

Re: [RESENT]: Fixed winedbg example configuration
by Alexandre Julliard 18 Jul '03

18 Jul '03

"BiGgUn" <fbiggun(a)hotmail.com> writes: > Changelog: > Reorder lines for a typical winedbg configuration. Your patch is wrapped; but anyway I don't see any reason to change that, keys are sorted when registry files are saved so the order doesn't matter. -- Alexandre Julliard julliard(a)winehq.com

8 22

Serial comm overlapped IO problem
by Rein Klazes 18 Jul '03

18 Jul '03

Hi, Recent commits http://www.winehq.com/hypermail/wine-cvs/2003/06/0232.html and http://www.winehq.com/hypermail/wine-cvs/2003/07/0090.html broke communication with my online banking program girotel. Part of the +relay,+comm,+file,+server trace: | 0009:Call kernel32.ClearCommError(000000bc,40721064,4072106c) ret=6005312f | 0009: get_handle_fd( handle=0xbc, access=80000000 ) | 0009: get_handle_fd() = 0 { fd=16, type=1, flags=1 } | trace:comm:ClearCommError handle 0xbc cbInQue = 375 cbOutQue = 0 ClearCommError indicates 375 bytes available. | 0009: get_serial_info( handle=0xbc ) | 0009: get_serial_info() = 0 { readinterval=ffffffff, readconst=00000000, readmult=00000000, writeconst=00000000, writemult=00000000, eventmask=0000003d, commerror=00000000 } | 0009: set_serial_info( handle=0xbc, flags=4, readinterval=00000000, readconst=00000000, readmult=00000000, writeconst=00000000, writemult=00000000, eventmask=00000000, commerror=00000000 ) | 0009: set_serial_info() = 0 | 0009:Ret kernel32.ClearCommError() retval=00000001 ret=6005312f | 0009:Call kernel32.ReadFile(000000bc,407210ac,00000177,40721060,4050358c) ret=60053164 | trace:file:ReadFile 0xbc 0x407210ac 375 0x40721060 0x4050358c App. requests those 375 bytes. | 0009: get_handle_fd( handle=0xbc, access=80000000 ) | 0009: get_handle_fd() = 0 { fd=16, type=1, flags=1 } | 0009: register_async( handle=0xbc, type=1, overlapped=0x40503708, count=375, status=00000103 ) | 0009: register_async() = 0 | 0009:Ret kernel32.ReadFile() retval=00000000 ret=60053164 | 0009:Call kernel32.GetLastError() ret=60053172 | 0009:Ret kernel32.GetLastError() retval=000003e5 ret=60053172 Read returns failure with GLE() == ERROR_IO_PENDING, leading to an error messagbox in the program. With only the first commit, the ReadFile returns 1 (success) but no data. Nowthe situations seems reversed, since accepting the error message the program proceeds to the next read and a new error messagebox. Any suggestions? Rein. -- Rein Klazes rklazes(a)xs4all.nl

4 4

Re:Eorr message when using winedump
by dd jj 17 Jul '03

17 Jul '03

Gosh, I found there's a "\" missing in wine-path\dlls\Makefile.in before pingdll setting. Maybe it's a bug there? Anyway, thanks -Lechun --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Eorr message when using winedump
by dd jj 17 Jul '03

17 Jul '03

Hello I got error message as following when I try to use winedump to build a winelib described as "generating stub DLLs", I follow the instructions provided by winedump/README: ./pingdll_install <wine-path> cd <wine-path> autoconf ./configure make depend && make make install It shows Ok until make depend && make, I got these error message: pingdll.dll.so \ make[1]: pingdll.dll.so Command not found make[1]: *** [all] Error 127 make[1]: Leaving directory '/home/lechun/wine-20030618/dlls' make: *** [dlls] Error 2 Could anyone give me some hints to fix it? Thanks a lot. p.s I used Redhat 9.0, wine-20030618. -Lechun --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

RE: Sync(2): oleaut32 I1 funcs
by Robert Shearman 17 Jul '03

17 Jul '03

> -----Original Message----- > Message: 1 > Date: Thu, 17 Jul 2003 08:37:08 -0700 (PDT) > From: Jon Griffiths <jon_p_griffiths(a)yahoo.com> > Subject: Sync(2): oleaut32 I1 funcs > To: wine-patches(a)winehq.com, julliard(a)winehq.com > Reply-To: wine-devel(a)winehq.com > -HRESULT WINAPI SetErrorInfo(ULONG dwReserved, IErrorInfo *perrinfo); > -HRESULT WINAPI GetErrorInfo(ULONG dwReserved, IErrorInfo **pperrinfo); > -HRESULT WINAPI CreateErrorInfo(ICreateErrorInfo **pperrinfo); > +HRESULT WINAPI SetErrorInfo(ULONG,IErrorInfo*); > +HRESULT WINAPI GetErrorInfo(ULONG,IErrorInfo**); > +HRESULT WINAPI CreateErrorInfo(ICreateErrorInfo**); Is there any reason for stripping out the parameter names from this file? They can be quite useful as a reminder for what each parameter is. P.S. In other parts of your patch you replaced char with signed char. Is signed char != char? Rob

3 2

Re: Question using winemaker to build a Winelib dll
by dd jj 17 Jul '03

17 Jul '03

Yeah, I saw there is a README file under winedump directory. I will read it through... Thanks -Lechun Steven Edwards <steven_ed4153(a)yahoo.com> wrote: > Now I am trying to use winemaker to build a winelib dll from windows source code, > Could anyone give some instructions about the implementation details? Or any useful info and > samples there? It seems to me the easy way to build a WINElib dll ATM is not to use Winemaker but to use winedump to create the spec and add the dll to wine/dlls/newdllname. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Re: Question using winemaker to build a Winelib dll
by dd jj 17 Jul '03

17 Jul '03

Hello Steven, Thank you for your answering. Honestly, I am a beginner to use WINE, could you please give me some implementation details about how to use winedump to create the spec? I am sorry to bother experts like you so much, but that's what I can only count on... Thanks. All the best. -Lechun Steven Edwards <steven_ed4153(a)yahoo.com> wrote: > Now I am trying to use winemaker to build a winelib dll from windows source code, > Could anyone give some instructions about the implementation details? Or any useful info and > samples there? It seems to me the easy way to build a WINElib dll ATM is not to use Winemaker but to use winedump to create the spec and add the dll to wine/dlls/newdllname. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Some dmusic questions
by Rok Mandeljc 17 Jul '03

17 Jul '03

Today I did some "tests" with dmusic; I've tried to run dxdiag with mixture of builtin and native dm*.dll and I have some questions based on observations: 1. dm*.dlls don't share DllGetClassObject function like I did in wine's implementations (dm*.dlls other than dmusic.dll have their functions forwarded to dmusic.dll). Shall we implement such separation or shall we leave it as it is? (personally, I'd choose separation because then mixing dlls would be more efficient; at the moment, all dm*.dlls call dmusic.DllGetClassObject, which mean I must replace all of them with native equivalents if I want to replace dmusic.dll; besides, dxdiag crashes in a mysterious way with builtin dlls and I expect the problem lies here). 2. when listing dmusic ports, dmusic calls EnumLegacyDevice, which is stub, because I can't find any info about it's parameters... It calls some winemm stuff and lists Wine midi out mapper, although it can't be used. It is obvious that it lists devices that could be used as ports, except Microsoft Software Synthesizer, which is available only if native dmsynth.dll is used (i used native dmusic.dll). Any ideas where I could get more detailed info about what does this funct. do and what parameters it takes? 3. this one concerns RIFF loading stuff I've been working on recently. MSDN states that IStream and IPersistStream insterfaces should be used in parsing data, which means all functs. in helper.c are wrong. I'll look deeper into docs and try to find out how it's supposed to go (just expect that all functs. will be replaced so do not modify them ;=) ). -- 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

2 1

Internet Explorer related trivia
by Mike Hearn 17 Jul '03

17 Jul '03

Well, I thought this statistic might counterpoint the news of Netscapes final death, and I'm in an odd mood at the moment. As we might end up cloning large parts of the Internet Explorer infrastructure someday, it's worth knowing roughly how much Microsoft invested/lost on it: $1.25 billion dollars This is according to Robert Scoble, who is an "evangelist" for Longhorn/Windows, so I expect it's mostly accurate. The figure sounds somewhat stupid, a pinky-to-the-mouth Dr. Evil moment. If you consider a large team of programmers working on the product for many years however, it becomes quite believable. Consider that IE encompasses not only MSHTML, but also things like MLANG, shell integration, ActiveX, probably elements of WSH and so on. I hope somebody finds web browsers interesting around here ;)

2 1

XEMBED implementation
by olivier 17 Jul '03

17 Jul '03

Hello, I would like to know how to use the XEMBED specification for inter-application GUI. Is there someone with a library which implement the specs? I would like to create a win32 window on a gtk (or X11) child panel. Regards, Olivier

2 1

more 3d ...
by Lars Segerlund 17 Jul '03

17 Jul '03

I am having some trouble running the MotoGP2 demo on wine ( Wine 20030709 ). ( It can be found on www.thq.com ) I know it uses direct X 9 and this is a bit experimental, but the game segfaults .... In any case I thought that this would be a good test case, and since it's easily downloaded. As a comment, the game will only run with the lates drivers from nVidia ... on win. ( btw. I'm trying to look a bit more in detail on what happens at the moment ) / Lars Segerlund.

2 2

Re: [dx69+70] FPS + SetTransform transformation
by Steven Edwards 17 Jul '03

17 Jul '03

> Note: I had a concern about calling gettimeofday, but I saw it was > already used in dlls\ntdll\time.c and I think I have done the right > includes. If you can avoid gettimeofday please try to. I have a patch to add gettimeofday to wine_port in the ReactOS tree but the dlls really should avoid calling *nix only functions if you can. Not that it really matters as most of WINEs directX stuff wont work on ReactOS for years++ anyway. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

3 2

Re: shell namespace in Winefile
by Rolf Kalbermatter 17 Jul '03

17 Jul '03

Hi Martin, I saw your patch to shell32, and noticed that you added ole32 to the dependicies of shell32. I believe in the interest of DLL seperation and avoiding circular DLL references it is the intention to prevent such hard dependencies on ole32 in most DLLs including shell32. If I'm not mistaken shell32 used to import ole32 some time ago but it was stated that this should go away which it seems to have done. The solution is to dynamically link to the functions of such DLLs on first execution as done in several places in clipboard.c. Rolf Kalbermatter

2 1

AAAUUGH!
by Gregory M. Turner 17 Jul '03

17 Jul '03

I swear, fdi.c is the worst code I ever wrote, period. It's just an absolute graveyard of abandoned code-paths and unused variables... it's downright embarassing... and of course all the stuff I carelessly brushed over is coming back to haunt me for split cabs... it doesn't help that this is really boring stuff, absolutely no real challenge to keep it interesting except the pure tediousness of it... Stuart Caie did all the real work already, of course, this is just some kind of insane-asylum housekeeping chore... Seriously, why are you people letting me infect your beautiful non-emulator with such crap? You should have taken me out to the abandoned nether regions of the code mines and shot me several patches ago ;) I'm really tempted to just pitch the whole mess and start over. I should have been editing cabextract.c all along, instead of employing this cut-and-paste bloatware approach... Bet I'd be done by now, if I'd just maintained some pretense of orthogonality. Well, in such situations I am at least stubborn, if not effective. Either I will beat the infestation into remission, or I will fix it the hard (and right) way. Be advised, however, that previous "I'm really, really almost done this time" predictions may have been overly optimistic. -- "We must stop thinking of the individual and start thinking about what is best for society." -Hillary Clinton, 1993 gmt

1 0

Question using winemaker to build a Winelib dll
by dd jj 17 Jul '03

17 Jul '03

Hello everyone, Now I am trying to use winemaker to build a winelib dll from windows source code, Could anyone give some instructions about the implementation details? Or any useful info and samples there? Thank you. All the best. -Lechun --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

Re: dmusic.dll DllRegisterServer et. al.
by Sylvain Petreolle 16 Jul '03

16 Jul '03

Wine doesnt compile with your patch applied, at least for me. In regsvr.c, you should include <string.h> instead of "string.h". Perhaps are you using a custom include path ? ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Question about docs of winegcc/wineg++
by dd jj 16 Jul '03

16 Jul '03

Hello everyone, Thank you all for your original help. Now I need to use winegcc/wineg++ to build winelib dlls, but I couldn't find any documents ans samples about such tasks. As a beginner in this field, I am eagerly hoping some clues or comments on these... Best wishes. -Lechun --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

4 7

"No App Selected"
by Robin Connelly 16 Jul '03

16 Jul '03

How do I select an App for voting -- I clicked on my favorite programming tool "Visual Foxpro" -- but although I see the 3 voting slots on the left, each slot is labelled: No App Selected I looked at the HELP screen ( http://appdb.winehq.com/help/?topic=voting ) but still do not understand how to select an app for voting. Specifically, what I did was: 1) Logged in as "Foxpro since 1987" 2) Navigated to the applications page ( http://appdb.winehq.com/votestats.php ) 3) clicked on the top item: Visual Foxpro 4) The attached page ( http://appdb.winehq.com/appview.php?appId=296 ) is what I see: << C E N S O R E D >> I would like to vote for the support of VFP ( Visual Foxpro, especially its most current versions 7 and 8 ).

1 0

question about WINE MSVCRT
by Jonathan Wilson 16 Jul '03

16 Jul '03

I notice that WINE has a clone of MSVCRT. I also know that MSVCRT exports some C++ symbols. How does WINE and its clone of MSVCRT and its build system handle the differences in name mangling between MSVCRT and GCC? Also, how does it handle the differences between the different class formats? Also, is the MSVCRT provided by WINE portable to all platforms and/or useable with winelib? I looked at the source code for WINE MSVCRT and I couldnt see how it all works.

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel