$gcc inputfile.c -o executablename -lstdc++
how do I start using gcc?
$ represents a command prompt. Some people use % instead
There are two popular editors, and a few less popular editors. The two most popular ones are vi and emacs.
How do I activate the editor, what is the name of the editor?
emacs~=Word, but that uses primarily plaintext
"$vi name" creates name if name does not exist. RH7's vi is a symlink to vim, which is slightly different."$emacs name" creates name if name does not exist. Emacs is primarily an X application(read: windows program), whereas vi is more of a console program(read: dos program).
"$gcc inputfilename -o executablename -llibraryname" builds inputfilename into an executable called executablename using the library libraryname, where libraryname is found in /usr/lib/liblibraryname.so, or /lib/liblibraryname.so
And what are the commands to first compile and build my executable?
Just gcc it. Gcc commandlines can get pretty hairy for anything more than a simple test program. To make it easier, make and makefiles were invented. I don't know anything about using makefiles.
What are the steps to creating a program after all the code is written?
No, but for larger programs you will want to eventually.
Do I need to create a make file?
Yes it's all done on the command line if you separate the editor from the compiler, which emacs does not do. There's an emacs mode that gives you a shortcut key to compile the current file, and other such things. It's not a big pain. People do it all the time. The overhead of a makefile is a one-time thing, and really speeds up the project once done. autoconf and automake make the overhead even less per project, but there's a one-time overhead in learning how to use them, which isn't trivial.(You could probably learn it in 24 hours or so if you had some projects for which you need to make some makefiles, but I don't, so learning on a purely abstract basis is rather difficult)
Is this done on the command line? Is the whole process a really big pain?