Oops. Sorry that I left the subject off.
On Sun, 21 Dec 2003, Kevin Atkinson wrote:
>
> I am having a problem compiling a simple winelib program which relies on
> a dll which uses the stdcall calling convention. I used pexports on the
> dll avisynth_c.dll to created the spec and then edited
I am having a problem compiling a simple winelib program which relies on
a dll which uses the stdcall calling convention. I used pexports on the
dll avisynth_c.dll to created the spec and then edited the file to removed
the leading underscore in the names (without that it would not link).
Tha
I just did a cvs update on the wine tree, and tried to build it. The build
failed when trying to link winealsa.drv.spec, with ALSA_widMessage reference
undefined.
The issue was that the majority of the code in audio.c, including one
definition of the function ALSA_widMessage, is conditioned up
This is an intresting way of looking at it. The
question is, do we have an active inventory of what
constitutes as a "Base DLL" I remeber some infighting
a while back about if the MFC DLLs counted or not.
I think I might be rasing a dead issue though.
-Joshua
--- "Dimitrie O. Paun" <[EMAIL PROT
On December 16, 2003 08:49 pm, Tom wrote:
> Here is the current DLL's Status Page.
Tom, it looks good, but I think it's getting too big.
Why don't we break it in 3 pages:
-- Base DLLs
-- DirectX DLLs
-- Multimedia DLLs
This also makes sense as some people don't care about
DirectX/Multimedia
