From: "Jade" <jade6@kolumbus.fi>
To: <gcc@gnu.org>
Subject: installation
Date: Thu, 06 Dec 2001 12:00:00 -0000 [thread overview]
Message-ID: <000801c17e8f$f06d42c0$da1e36d4@elisa.omakaista.fi> (raw)
Hi,
I would like to use GCC for compiling my C++ programs, but basically, you
guys really aren't making it easy to install the thing. I've come to the
conclusion that there are only 2 difficult things in C++ (which I already
know, after using it at school for a year); these things are:
1.) installing the compiler and figuring out how it works
2.) finding documentation that a human being can read
Why couldn't people simply do what Sun has done with Java: just a single,
no-extra-crap-distribution and simple instructions on how to get started,
plus easy-to-read API documentation on the most important classes. Java
would never have gained as much popularity as it has if only somebody had
figured this out, and done something about it. It's by far the most vital
problem to solve for the C++ community. New users turn to Java simply
because it doesn't take a year to figure out how to get started with it.
So, please answer just one question:
"Where can I find a normal command-line version of GCC which can be hooked
up with the Win API / MFC easily?"
That is, no UNIX emulator crap, just standard MS-DOS. As far as I know,
DJGPP can't be used with the Win API very easily, and its documentation
sucks bad, not to mention that the error messages are mostly useless and it
seems kinda unstable anyway. Sorry about the tone, but this thing has been
bothering me for a long time. Why isn't something being done? It's been 3
decades.
- Janne Kuusela
next reply other threads:[~2001-12-06 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 12:00 Jade [this message]
2001-12-06 12:14 ` installation DJ Delorie
2002-04-26 8:37 installation Vu Khuong
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='000801c17e8f$f06d42c0$da1e36d4@elisa.omakaista.fi' \
--to=jade6@kolumbus.fi \
--cc=gcc@gnu.org \
/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).