"Wilbur N. Dale" wrote:
[snip]
> 1. Compile MFC. Several years ago we (Lumin Software) tried to compile MFC.
> The attempt failed and we found another way to do what we wanted. MS
> documentation states that compiling MFC was deliberately made difficult.
> Considering my experience with stuff they call "easy" I am not looking forward
> to compiling MFC. We are currently using Visual Studio 5 for windows
> development.
Wilbur, I personally think that this is the 'right' approach, although
approach #2 may prove faster.
Despite your previous experience, and despite my earlier incorrect
statements,
I think that this is simpler than you fear. It's one of those tasks
that's
darkest before the storm - you spend all of your energy getting all the
include files to work. Once you have *one* object file, the rest go
much more quickly (alright, getting it to link is also a hairball of a
job,
but it's tractable <g>).
If you're not in a hurry, getting MFC to compile, and having a
documented
procedure for compiling it is on our agenda for the relatively near
future (see the Wine 1.0 task list).
Jer
p.s. Stick with Visi C++ 5. IMHO its MFC license is cleaner than that
of VC 6.
