Eclipse Install Instructions

Don't skip this part! How to follow instructions

Too many students have hopelessly messed up their computers by incorrectly or incompletely following my instructions.

Yes, I've made those same mistakes too.

These are detailed instructions, and you must be diligent about following them if you want to maximize your chances of success. I've spent upwards of 5 hours on these instructions, and nothing is more frustrating than fixing a student's computer because s/he didn't read what I've written. Don't be afraid to ask me questions and come to me with problems, but please carefully read my instructions first.

Whenever I'm working through complex instructions, I read them four(!) times.

  1. First I just read the instructions all of the way through once. I don't do anything. I don't run anything. I just read the instructions and get a feel for how this process will work, as well as the writer's style.
  2. I then read all of the way through the first section again to remind myself of what that set of steps is like.
  3. Having read through the first section, I then read the entire first paragraph again, since people who write technical instructions usually use paragraphs to block related steps together. By reading the first paragraph, I'll know how the first set of steps works together.
  4. Having read through the first paragraph, I then go through it again and actually do the steps that it is telling me to do. Since this is my 4th time through that material, I am less likely to miss an instruction or partially complete it.
  5. I then move on to the second paragraph, reading it all of the way through first and then doing the steps. I repeat this until I reach the end of the section
  6. At the start of the next section, I read it through again, and then start working through the paragraphs one by one just as I did before. I repeat this process until I'm at the end of the document.

This is how I, Mr. Kozee computer teacher and techy geek-head work through instructions, so I highly recommend that all of my students do the same with these.

Disclaimer

If you're running Vista, you're on your own. I may be able to provide some help, but Vista (especially 64-bit Vista) is just a mess. Sorry!

Ditto if you're running a Windows 7 beta.

Obtaining the needed files

There are many ways you can obtain the files. The installer application is in my handouts folder, so people with broadband can use the school's home access service to download the application (named "Programming Installer.exe"). Likewise, students with a USB pen drive can copy the application to their pen drive during class (you'll need 140 mb free).

I also offer CDs containing the install software. CDs cost $1 a piece, or you can bring in a blank CD for me to use instead.

These instructions are aimed at Windows users. If you run Linux or Mac OS X, contact me for help (though I will only provide limited assistance).

Installing Eclipse and MinGW

This year is different in that I've packaged Eclipse and MinGW together into a single install application, named "Programming Installer.exe". Simply double click the installer, and let it work. Be sure to read the message that comes up when you first run the installer, or else you may goof something up.

It is very important that you do not change the program's install location. The default location is C:\, and should stay that way. Under no circumstances should you change it. You will need about 300 megabytes free on your C drive to install both Eclipse and MinGW.

When the installation is done, you can move the Eclipse folder if you like, but I really don't recommend it (you'll find it in the "Program Files" folder on your C drive). You'll also see a shortcut to Eclipse on your desktop, but don't double click it yet.

Testing MinGW

To test your MinGW, go to Start->Run-> and type "cmd" into the box. Hit enter and a DOS window will appear. Type in "g++" (without quotes) and hit enter. You should get "G++: no input files" as the response. If you don't, let me know.

Configuring Eclipse

Run Eclipse. The first time you run it, you'll get a warning asking you to choose the location of your workspace. In general, just accept Eclipse's suggestion and click okay. If you don't want to see this warning ever again, simply tick off the check box at the buttom of the window before clicking ok.

Soon the Eclipse window will appear. Go to Windows->Open Perspective->Other and select "CVS Repository Exploring" to activate the CVS perspective. Repeat this process and select "C/C++" instead. This will activate the C/C++ perspective.

Remember that in the upper-right corner of your screen is a little icon palette that you can use to quickly switch between perspectives. Resize that palette so that you see the CVS and C++ icons at the same time.

Finally, in the Project menu, make sure that "Build Automatically" is unchecked. If it is checked, you can uncheck it by selecting it in the Project menu. This will prevent Eclipse from compiling your projects before you are ready.

You are now ready to configure CVS.

Configuring CVS

Let's set up your class and personal repositories, pull down some files and make sure that everything works. We'll set up your class repository first.

Get into the CVS perspective and right-click in the white space on the left side of the screen and select New->Repository Location. Enter the following data into the perspective configuration window:

  • I will provide you with the correct host to use in class.
  • The path is
    • /cvs.prog for Programming I and II students
    • /cvs.approg for AP students
  • The username the same username you use for the school's network. If you have a 5-digit username, add a zero to the beginning (ex. 91231 becomes 091231)
  • The password is the password I provided earlier in the year
  • The connection type is extssh
  • Use port 6181
  • Check (turn on) the Save Password box

Click finish and after some churning, a new entry should appear in your repository list. Expand that entry and expand the HEAD, and you should see everything in the class repository.

To help you better tell this class repository from the other repository you're about to set up, right click on the repository's entry (the one with the orange cylinder beside it) and go to properties. At the top of that window, select the "Use Custom Label" option and type "Class Repository" into the text box to the right. Make sure that the "Save Password" box is still checked, click ok, and the name of the repository should change to something easily understandable.

Now let's set up your personal repository.

Right-click in the white space on the left side of the screen and select New->Repository Location. Enter the following data into the perspective configuration window:

  • The host the same as for the class repository
  • The path is /home/YOUR_USER_NAME/cvs (don't actually write the words YOUR_USER_NAME in the path. Instead, write in the same user name you used to set up the class repository. For example: if your username was bob, your path is /home/bob/cvs)
  • The username is the same one you used to set up the class repository.
  • The password is the password I provided earlier in the year
  • The connection type is extssh
  • Use port 6181
  • Check off (turn on) the Save Password box

Click finish and after some churning, a new entry should appear in your repository list. Expand that entry and expand the HEAD, and you should see everything in your repository. You may want to change the name of this repository too, much like you did the class repository. Follow the same steps and give your repository some appropriate name. Be sure that the Save Password box is still checked off (turned on) before hitting ok.

Your repositories are now set up.

Hello World!

Enter Eclipse and open the now-available C++ Perspective.

Make an empty C++ project, just like we've been doing in class. Be sure that you select the MinGW compiler when you make your project. You may get a warning about switching to the C++ perspective. Hit ok. In this new project, make a new C++ source file called "main.cpp".

Type the following code in main.cpp

#include <iostream>
using namespace std;
int main (void)
{
 	cout << "Hello World!" << endl;
	return 0;
}

Save, build and run it like we did in class. It should behave predictably.

If something goes wrong

If something goes wrong, create a detailed description of what is not working and any errors that you see, then send me an email. I will try to solve the problem as best I can, even controlling your computer remotely to get it to work.