Re: msftedit.dll

2006-02-04 Thread Stefan Leichter
ls/winegcc/winegcc -B../../tools/winebuild -shared ./msftedit.spec -o msftedit.dll.so -L../../dlls -L../../dlls/kernel32 -L../../dlls/riched20 -lkernel32 -lriched20 -L../../libs/wine -lwine -luuid -L../../libs/port -lwine_port msftedit.dll-FZrkTh.spec.o(.data+0x3f0): In function `__wine_spec_n

Re: msftedit.dll

2006-02-03 Thread Dmitry Timoshkov
On Sat, 2006-02-04 at 02:26 +0300, Phil Krylov wrote: > Could this be done another way? E.g., symlink msftedit.dll.so to > riched20.dll.so? Or copy riched20.dll.so as msftedit.dll.so, which would > resemble MS approach more. I'd suggest #3: forward msftedit entry points to the riched20 ones. --

Re: msftedit.dll

2006-02-03 Thread Phil Krylov
On Sat, 4 Feb 2006 00:07:24 +0100 Stefan Leichter <[EMAIL PROTECTED]> wrote: > +2 stub IID_IRichEditOle > +3 stub IID_IRichEditOleCallback > +4 stub CreateTextServices > +5 stub IID_ITextServices > +6 stub IID_ITextHost > +7 stub IID_ITextHost2 > +8 stub REExtendedRegisterClass > +9 stub RichEditA