Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <033a01c2a194$e3f87d60$a352a518@samsystem> From: "Samuel" To: References: <170350-220028422145914150 AT M2W085 DOT mail2web DOT com> Subject: Re: using MFC with cygwin Date: Wed, 11 Dec 2002 20:13:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 ----- 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 (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/14/2002 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/