From: "Samuel" <samuel@socal.rr.com>
To: <cygwin@cygwin.com>
Subject: Re: using MFC with cygwin
Date: Wed, 11 Dec 2002 22:55:00 -0000 [thread overview]
Message-ID: <033a01c2a194$e3f87d60$a352a518@samsystem> (raw)
In-Reply-To: <170350-220028422145914150@M2W085.mail2web.com>
----- Original Message -----
From: <lhall@pop.ma.ultranet.com>
To: <serj@hea.iki.rssi.ru>; <cygwin@cygwin.com>
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/
next prev parent reply other threads:[~2002-12-12 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 11:15 lhall
2002-12-11 22:55 ` Samuel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 8:48 Michael D. Crawford
2002-12-12 7:51 lhall
2002-08-22 9:51 serj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='033a01c2a194$e3f87d60$a352a518@samsystem' \
--to=samuel@socal.rr.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).