Francois Gouget wrote:
>
> Since your application runs well in Wine and does not require any MS
> library you should be able to compile it relatively easily. You said it
> does not depend on any MS dll. I assume this means it's not MFC-based
> which is a good omen (because if it's MFC based you'll have a lot of
> work just recompiling the MFC first).
I'm not sure. I ran with --debugmsg +dll and got this:
trace:dll:NE_DllProcessAttach (KRNL386.EXE) - START
trace:dll:NE_DllProcessAttach (KRNL386.EXE) - END
trace:dll:NE_DllProcessAttach (system.dll) - START
trace:dll:NE_DllProcessAttach (system.dll) - END
trace:dll:NE_DllProcessAttach (wprocs.dll) - START
trace:dll:NE_DllProcessAttach (wprocs.dll) - END
trace:dll:NE_DllProcessAttach (GDI.EXE) - START
trace:dll:NE_DllProcessAttach (GDI.EXE) - END
trace:dll:NE_DllProcessAttach (display.dll) - START
trace:dll:NE_DllProcessAttach (display.dll) - END
trace:dll:NE_DllProcessAttach (USER.EXE) - START
trace:dll:NE_CallDllEntryPoint Calling USER.EXE DllEntryPoint,
cs:ip=0257:18dd
trace:dll:NE_DllProcessAttach (USER.EXE) - END
trace:dll:NE_DllProcessAttach (commdlg.dll) - START
trace:dll:NE_CallDllEntryPoint Calling commdlg.dll DllEntryPoint,
cs:ip=02ef:0171
trace:dll:NE_DllProcessAttach (commdlg.dll) - END
I didn't write it, but it was written using Delphi according to the
help files. Any way to find out what DLLs are being used,
without extra huge amounts of messages?
I'm using the wine RPM from RedHat7.0 right now.
I cannot get to CVS, and haven't grabbed a recent snapshot
yet. wine --version gives 20000716 so it't rather old, but works
well for this app :)
-Thomas
