This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: using MFC with cygwin

Hm, someone's been digging around in the email archives! ;-)
Actually, that's good to see.

While I won't argue the slight semantic differences pointed out
here between what I said and this response, I believe we both agree 
it makes the same point, at least in the context of Cygwin.  Anyone
that wants to can try to port MFC to any Win32-based compiler they
want but they will end up with something restricted by the Microsoft


Original Message:
From: Samuel
Date: Wed, 11 Dec 2002 20:13:52 -0800
Subject: Re: using MFC with cygwin

----- Original Message -----
From: <>
To: <>; <>
Sent: Thursday, August 22, 2002 6:59 AM
Subject: RE: using MFC with cygwin

> No one has ported MFC to any compiler besides VC++.  And while
> it could be done, the benefits are minimal since the Microsoft
> license would prevent you from distributing the result.

MFC was not ported to VC; it did not exist prior to VC.

I am 95% sure that (some) Borland compilers license (include) MFC. You might
be correct that it has not been ported, but Microsoft licenses it. The VC
compiler includes the MFC source code so it would not be too much work to
port (unlicensed). I assume that if source code existed that did the same
thing as MFC then it could be entirely legal.

I think the original question was about a console program that used MFC and
I would probably suggest not using MFC for that.

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/14/2002

Unsubscribe info:
Bug reporting:

mail2web - Check your email from the web at .

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]