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

Re: Problems converting DLL to unix SO with winelib
by List vmn June 12, 2002

June 12, 2002

Hi Martin, I finaly got the patch to work. The problem was with my mail client. I am now at the office and using eudora and things worked... A question, When I use the patched winemaker , I get a spec file with out any imports at all, even the ones specified on the command line. When I compile/link I get unresolved symbols. I then dont know what to do so I add the import lines back to the spec file and it links/compiles.... What am I missing here? What is your patch doing ? Thanks, Miguel At 17:17 7/6/2002 +0200, you wrote: >Am Fre, 2002-06-07 um 16.59 schrieb mfeitosa(a)vmn.com.br: > > > Here is the output... > >And here is mine: > >[martin(a)biker tools]$ cvs diff -u -r 1.39 winemaker >[martin(a)biker tools]$ cd .. >[martin(a)biker wine]$ patch -p0 --dry-run </tmp/winemaker.diff >patching file tools/winemaker >patching file documentation/winemaker.man >[martin(a)biker wine]$ > >Perhaps you have the wrong patch. I attach it. >Martin > >-- >Martin Wilck Phone: +49 5251 8 15113 >Fujitsu Siemens Computers Fax: +49 5251 8 20409 >Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com >D-33106 Paderborn http://www.fujitsu-siemens.com/primergy > > > >

3 2

winespy - a wine gui front-end for --debugmsg output
by max June 12, 2002

June 12, 2002

I got the first (... very first) winespy wine front-end running. You can download at www.veneto.com/winespy/winespy.tar.gz In INSTALL and README files you'll find shorts description of usage and, of course, bugs :) Any suggestion/help appreciated ! Regards Max

1 0

gdi functions as undefined symbol in libwine.so
by Sylvain Petreolle June 11, 2002

June 11, 2002

Hi, Marcus showed I probably have install problems. All symbols that are in gdi.exe dll are reported as undefined symbols in libwine.so fixme:win32:ELF_FindExportedFunction function AbortDoc not found: /usr/local/lib/libwine.so: undefined symbol: AbortDoc fixme:win32:ELF_FindExportedFunction function AbortPath not found: /usr/local/lib/libwine.so: undefined symbol: AbortPath Download CVS version from scratch and reinstall didn't fix the problem. Did someone else got the problem ? I actually don't see a way to fix it. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

RE: driver question
by Patrik Stridvall June 11, 2002

June 11, 2002

> On Tue, Jun 11, 2002 at 11:23:06PM +0300, Hetz Ben Hamo wrote: > > > I'm not an expert on licensing, and I thought to ask this > question here - I'm > > not trying to make any emails flame war - just need a > simple answer... > > > A friend of mine is toying with an idea to write a frame > buffer driver instead > > of the x11drv on wine, but he doesn't think his boss will > allow to release > > the code.. > > > Can he (legally) write the driver, bundle it with the > lgpl'd wine and sell > > it? or is this illegal? > > If the driver interfaces with the rest of Wine through a > clearly defined > library API, and his proprietary code is distributed as > separate object > code that can be relinked with Wine at runtime or at build time (i.e., > made available as either .o files or as a .so shared lib), > then this is > unquestionably permitted by the LGPL. True in general but unfortunately the Wine display driver API wouldn't IMHO be classified as a clearly defined API... So whether this is allowed is a little unclear to say the least.

2 1

self-registerable standard DLLs
by John K. Hohm June 11, 2002

June 11, 2002

I noticed that the attempt to test comcat.dll on Win98 failed because DllRegisterServer is a stub returning E_NOTIMPL. I have added the registry entries for the component categories manager to winedefault.reg, which should suffice for normal Wine installations. Despite this, is it generally acceptable to have actual code to register/unregister a standard COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.

4 5

driver question
by Hetz Ben Hamo June 11, 2002

June 11, 2002

Hi, I'm not an expert on licensing, and I thought to ask this question here - I'm not trying to make any emails flame war - just need a simple answer... A friend of mine is toying with an idea to write a frame buffer driver instead of the x11drv on wine, but he doesn't think his boss will allow to release the code.. Can he (legally) write the driver, bundle it with the lgpl'd wine and sell it? or is this illegal? Thanks, Hetz

2 1

Re: null midi device
by Eric Pouech June 11, 2002

June 11, 2002

> I was thinking: Couldn't one use timidity to make a fake midi device > that actually produces sound? That would be something. I thought about it. you need to use timidity 0.20i (the last one from the original author released under LGPL, the next ones are released under GPL). Then, to make it a real midi driver (in terms of Win32 API) which isn't a trivial task (for example, timidity pre-processes the full content of the MIDI file to be played, whilst a standard MIDI driver has to play midi notes on the fly...). I did start looking at that a long time ago, but without real results in so far. A+ --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) The future will be better tomorrow, Vice President Dan Quayle ____________________________________________________________ Faites un voeu et puis Voila ! www.voila.fr Avec Voila Mail, consultez vos e-mails sur votre mobile Wap.

6 9

builtin oleaut32
by Ann and Jason Edmeades June 11, 2002

June 11, 2002

Hello, I have been doing some playing with builtin oleaut32 and a Visual Basic program I am trying to get working under wine with no-windows (well, as little as possible anyway). I noticed after copying some ocx files from windows, I was starting to trap due to unimplemented stubs inside oleaut32, and have started coding up just enough to get my application working. Every time I fix one issue, I find 2 others, so before I dive in too far has anyone else done any work in improving this area which hasnt been submitted, or is anyone actively working on this - or should I just continue? Currently I have: VarCmp support for BSTR and Integer variants VarAnd support for boolean variants only VarNot support for boolean variants only VarParseNumFromStr support for negative numbers VarNumFromParseNum support shorts VarDateFromUDate return value is incorrect VarNot support for boolean variants only Two other questions as I am still fairly new at Unix in general, let alone wine.... 1. What is the policy on patches - Is one big one with all changes for the same module ok? 2. What about tracing - While writing them I have added trace to show the parms and return values (relay just shows the rc whereas the actual return value is normally a third varient). Should I leave these in? Thanks Jason

2 1

RE: builtin oleaut32
by Medland, Bill June 11, 2002

June 11, 2002

> -----Original Message----- > From: Ann and Jason Edmeades [mailto:us(a)the-edmeades.demon.co.uk] > Sent: Tuesday, June 11, 2002 10:20 AM > To: wine devel > Subject: builtin oleaut32 > > > Hello, > > I have been doing some playing with builtin oleaut32 and a > Visual Basic > program I am trying to get working under wine with no-windows > (well, as > little as possible anyway). > > I noticed after copying some ocx files from windows, I was > starting to trap > due to unimplemented stubs inside oleaut32, and have started > coding up just > enough to get my application working. Every time I fix one > issue, I find 2 > others, so before I dive in too far has anyone else done any work in > improving this area which hasnt been submitted, or is anyone actively > working on this - or should I just continue? Basically that's what I noted too. I am sort of working in the area but I haven't even got everything working natively yet (since I started from a non-windows installation and it's hard to figure out what needs to be put in). I would suggest that the best solution is to submit small packages at regular intervals. > > Currently I have: > VarCmp support for BSTR and Integer variants > VarAnd support for boolean variants only > VarNot support for boolean variants only > VarParseNumFromStr support for negative numbers > VarNumFromParseNum support shorts > VarDateFromUDate return value is incorrect > VarNot support for boolean variants only > > Two other questions as I am still fairly new at Unix in > general, let alone > wine.... > 1. What is the policy on patches - Is one big one with all > changes for the > same module ok? > 2. What about tracing - While writing them I have added trace > to show the > parms and return values (relay just shows the rc whereas the > actual return > value is normally a third varient). Should I leave these in? Sounds a good idea. Presumably they are under the ole debug channel. If it gets ridiculous it might be worth adding a new debug channel. > > Thanks > Jason > > > Bill

1 0

Re: Linux patch for supporting shortcuts and symlinks on VFAT
by Brian Vincent June 11, 2002

June 11, 2002

> It seem that at least some people are against it inclusion so I > wonder whether we should support inclusion of the patch or not. I'd agree that doing it at the kernel level isn't the answer. You don't want to abstract that information away from the user. Plus, like Francois mentioned there's a bunch of cases where it's just not going to work. However, what would be interesting (if you're going to parse the .lnk file anyway) is to display it as a symlink, but not actually have it operate as a link. For instance: -rw-r--r-- 1 vinn power 22 Jun 11 09:16 junk -> c:\Program Files\bar At that point it becomes useful to parse large directories of .lnk files by simply reading the directory. Leave it up to the application (Wine, etc) to figure out how to translate the path. With proper error handling you could probably add it as a "feature" to every filesystem. </$.02> -brian

1 0