winelib and no mfc

Brandon Kilgore bkilgore at
Fri Jul 13 10:04:39 CDT 2001

Well, if afx.h is included, then the source definitely has to be built 
against the mfc libraries.  I'm not sure if there are other mfc libraries 
that don't include afx.h themselves, but I din't think so.  I know all of 
the afx*.h headers I've seen have all included afx.h, so this is probably a 
good indicator.  I also noticed that in the .dsp visual studio file, 
projects that were designed for mfc have "#PROP Use_MFC #" in them, where 
number indicates the version of MFC being used, I think.  I don't know if 
this could be useful or not.

  - Brandon

At 02:16 PM 7/13/01 +0000, you wrote:
>Hi Francois
>Francois Gouget <fgouget at> wrote in article
><Pine.LNX.4.21.0107121001480.6768-100000 at amboise.dolphin>...
> > On Thu, 12 Jul 2001, Bill Medland wrote:
> > [...]
> > > I have noticed that if ones code comes out of the Visual Studio
> > > (even if it doesn't use MFC and ATL) the current winemaker (and quite
> > > possibly all of them so far) are easily led to believe that it does.
> > > myself (since I'm just playing so far) I simply edit the
> > > to correct that.
> >
> >    I guess this is because the current Winemaker assumes that if a file
> > called 'stdafx.h' is present then the project is an MFC one. Maybe this
> > needs to be fixed, but I'm not really sure then how to detect that a
> > project is an MFC one. Maybe it should look for an atl.h or afx.h when
> > it is parsing the files to fix the include directives. Unfortunately
> > this is done too late in the process...
> >    When does VC6 create this 'stdafx.h' file anyway? I know it's used
> > for precompiled headers but not all projects using these have it. Is it
> > one of the wizards that does this?
>yes.  It seems to me that if the user uses the "Create Project" option,
>which invokes the wizard, and then chooses any option other than an empty
>project, then VC++ will generate a StdAfx.h and StdAfx.c, both of them
>being present to allow it to manage precompiled headers.
>I've just tried making a Win32 console application that supports mfc and it
>creates a "Hello, world" that initialises the MFC.  The obvious
>differentiator is that StdAfx.h includes afx.h and afxwin.h.
>I would suggest that we take the hint from the afx.h (which looks as if it
>only contains stuff required for MFC and is clearly essential for MFC)
>p.s. Winemaker's impressive!
>wine-users mailing list
>wine-users at

More information about the wine-users mailing list