January 2003 - Wine-Devel - list.winehq.org

Re: winemaker problem

by Jeff Smith

Yes there should be. Currently execname.so is being created rather than execname.exe.so. The patch I submitted a few hours ago (don't know if it has made it through yet) includes a fix for this. Copying the file is actually what I did for several weeks, rather than dig in to winemaker to fix the problem. But I get fed up and started putting together a patch for this several days ago. So now it is ready to roll. Good timing, yes? -- Jeff S >From: Shachar Shemesh <wine-devel(a)sun.consumer.org.il> > >Shouldn't there be a winemine-hcs.exe.so file there? >If you rename winemine-hcs.so to winemine-hcs.exe.so, what happens? > > Shachar > >Hans Christian Studt wrote: > >>It still cannot find 'winemine-hcs.exe'. >>What seems to comes nearest is >>-rwxr-xr-x 969 jan 1 21:00 winemine-hcs >>-rwxrwxr-x 793446 jan 1 21:00 winemine-hcs.so >>-rw-rw-r-- 44160 jan 1 21:00 winemine-hcs.spec.c >>-rw-rw-r-- 92648 jan 1 21:00 winemine-hcs.spec.o >>-rw-rw-r-- 173 jan 1 20:59 winemine.exe.dbg.c >>-rw-rw-r-- 2040 jan 1 21:00 winemine.exe.dbg.o >>-rw-rw-r-- 43665 jan 1 15:39 winemine.exe.spec.c >> >>I sure hope someone can help out - because I plan to try to see if I can >>make some of those 7.000 win32 applications over at sourceforge.net >>compile under winelib. _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus

Jan. 2, 2003

Re: winemaker problem

by Shachar Shemesh

Shouldn't there be a winemine-hcs.exe.so file there? If you rename winemine-hcs.so to winemine-hcs.exe.so, what happens? Shachar Hans Christian Studt wrote: > It still cannot find 'winemine-hcs.exe'. > What seems to comes nearest is > -rwxr-xr-x 969 jan 1 21:00 winemine-hcs > -rwxrwxr-x 793446 jan 1 21:00 winemine-hcs.so > -rw-rw-r-- 44160 jan 1 21:00 winemine-hcs.spec.c > -rw-rw-r-- 92648 jan 1 21:00 winemine-hcs.spec.o > -rw-rw-r-- 173 jan 1 20:59 winemine.exe.dbg.c > -rw-rw-r-- 2040 jan 1 21:00 winemine.exe.dbg.o > -rw-rw-r-- 43665 jan 1 15:39 winemine.exe.spec.c > > I sure hope someone can help out - because I plan to try to see if I > can make some of those 7.000 win32 applications over at > sourceforge.net compile under winelib.

Jan. 2, 2003

Re: Alexandre?

by Shachar Shemesh

Just make sure to read your mail ordered latest to earliest, in case someone sent a patch and then changed their mind. Also, please ignore my wineboot patch. I'll resend later today (my timezone). Shachar Alexandre Julliard wrote: >"Jeff Smith" <whydoubt(a)hotmail.com> writes: > > > >>I've seen no activity on wine-cvs for a week (Dec 23). >>What's up? Holiday vacation? >> >> > >Yep, I'm just back from one week without email access; there should be >plenty of traffic on wine-cvs soon judging from my mailbox ;-) > >Happy New Year to everybody! > > >

Jan. 2, 2003

Re: wineboot - initial version

by Shachar Shemesh

Dimitrie O. Paun wrote: >On January 1, 2003 12:48 pm, Shachar Shemesh wrote: > > >> * _stricmp is not defined, and is called directly instead of as >>stricmp. * As a result of the above, there is a compilation warning when >>compiling. >> >> > >There's no point in importing msvcrt just for this function. >Just use lstrcmpiA (exported by kernel32 and defined in winbase.h) >as suggested by Francois. > The only reason I had for using msvcrt was that I was aiming at having all of the winelib apps shipping with Wine compile on windows (even if that makes no sense, as is the case with wineboot). I will use lstrcmpiA, thanks. >As for the patch, please include even new files in the patch >(as I explained in the message "Re: Tests for URL functions in shlwapi") >by diffing against /dev/null. > > I tried that at first, but diff -u produced slightly different output than cvs diff -u, and I was worried that the two could not coexist. I'll make sure I can run patch on the result, and run the diff together (along with the fix for the stricmp stuff). Shachar

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Tom Wickline

Dan Kegel wrote: > http://www.wheaty.net/FAQ.htm#APISPY32 says that the best tool out there is > http://www.internals.com/utilities_main.htm > (Supposedly the author will send source to you on request, too.) > That program requires a text file containing the prototype for > each API you want to spy on, though, and it only comes with 3 APIs > as an example. Does anyone have a full version of that file, or > a perl script to create it from the wine tree? Hi, You could look at : http://www.dxspy.com/ For hooks : http://www.codeproject.com/system/hooksys.asp Tom

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Dmitry Timoshkov

"Jeremy White" <jwhite(a)codeweavers.com> wrote: > We've looked into this extensively; looking at both flavors > of apispy (yes, there are two of them, with very similar names), > and a lot of other variations. > > However, I've got a half baked W2K based solution similar to > the Detours library from Microsoft. The advantage to my approach > is that it generates a relay log identical to that of Wine, > which then allows for diffing the log files. Debugging Tools for Windows http://www.microsoft.com/ddk/debugging has logger.exe/logviewer.exe which help a lot in investigating what actually windows applications do. Logger creates binary log files which logviewer is able to parse/view. Even there is a mechanism to extend the logging facility by simply editing a .h like files. Logviewer is able to show all the API arguments, various data structures, API results and more. It can export log into the plain text file, which could be diffed against another one. I would say that log file is *very* similar to the Wine relay log. Just give it a try. -- Dmitry.

Jan. 2, 2003

Re: __WINE__ vs. __WINESRC__

by Dimitrie O. Paun

On January 1, 2003 07:40 pm, Alexandre Julliard wrote: > I think __WINE__ is best, let's just rename the internal one. BTW this Cool, but to what? __WINESRC__? __WINEBUILD__? __WINEINTERNAL__? > may be the occasion to clean things up a bit, we have way too many of > these ifdefs in our headers, and many of them could be removed IMO. Indeed. How do you want to do this? Can we do the rename, and then eliminate some of them? This would be best for me, since I can complete the work on wxWindows. There are many things of this form: include/mediaobj.h:#ifndef __WINE__ include/mediaobj.h-#include "rpc.h" include/mediaobj.h-#include "rpcndr.h" include/mediaobj.h-#ifndef COM_NO_WINDOWS_H include/mediaobj.h-#include "windows.h" include/mediaobj.h-#include "ole2.h" include/mediaobj.h-#endif include/mediaobj.h-#endif Do you want to keep them? -- Dimi.

Jan. 2, 2003

argv[0] needs to be an absolute path

by Dan Kegel

The C program main(int argc, char **argv) { puts(argv[0]); } outputs an absolute path on Windows, but sometimes outputs a relative path on Wine. This causes the commandline $ wine d:setup to fail to find its files properly if it uses the basename of argv[0]. One example of this is msvc4.0 (although it only tries this if an earlier method fails, so there's another bug lurking). I am about to submit a one-line patch to fix this to wine-patches. (If I weren't a wimp, I'd figure out a way to submit a regression test, too, although it'd be a strange one; most of our tests don't need to invoke Wine itself from the Unix commandline!) The same problem exists for programs launched from other wine programs, e.g. from inside wcmd. That's another code path, and I couldn't find a one-line fix for that one. - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com

Jan. 2, 2003

Re: winemaker problem

by Sylvain Petreolle

Don't know mny things on winelib compilation, but look under other programs/ examples. It seems you have incorrect extension for your files. You're missing the .exe before the .so (wine looks for winemine-hcs.exe.so if I remember correct) Last thing I can say : check your winemaker options. > (/user/usr/local/wine/programs/winemine-hcs) #./winemine-hcs > /usr/local/bin/wine: cannot find 'winemine-hcs.exe' > > It still cannot file 'winemine-hcs.exe'. > What comes nearest is > -rwxr-xr-x 969 jan 1 21:00 winemine-hcs > -rwxrwxr-x 793446 jan 1 21:00 winemine-hcs.so > -rw-rw-r-- 44160 jan 1 21:00 winemine-hcs.spec.c > -rw-rw-r-- 92648 jan 1 21:00 winemine-hcs.spec.o > -rw-rw-r-- 173 jan 1 20:59 winemine.exe.dbg.c > -rw-rw-r-- 2040 jan 1 21:00 winemine.exe.dbg.o > -rw-rw-r-- 43665 jan 1 15:39 winemine.exe.spec.c > > -- > Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk > .dk og W3C standarder : http://w3c.studt.dk > ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Dan Kegel

Duane Clark wrote: > Dan Kegel wrote: >> I'm trying to figure out why an app works on Windows but not Wine, >> and it'd sure be nice to be able to log all the api calls the >> app makes under each of the two environments; then perhaps >> I could compare the logs to see where Wine differed from Windows. >> >> Does anyone else do stuff like that? If so, what tools do you use? > > You had previously mentioned having a copy of msvc. Did you check in it > for SPY++? I would have to say that it seems to work quite well under Wine. The SPYXX.EXE in my copy of msvc4.0 appears to only let you log windows messages, not api calls. Then again, since help doesn't work under Wine, I can't tell if I'm missing something... -- Dan Kegel Linux User #78045 http://www.kegel.com

Jan. 2, 2003