Installing Tools

Now that we have our development Linux system running, it is time to install a few programming tools.

Programmer’s Editor

We need a good programmer’s editor to write our code. Remember, we will not be using an IDE, so you need to learn a professional tool. I am going to use a program that has been popular for over 35 years: Vim

Open up your Terminal program and type this command:

$ sudo apt-get update
# sudo apt-get install -y vim-gtk

The system will ask you for your password on that first line. The “update” just makes sure all of your current programs and the package manager (named “apt”) is ready for work.

The second line actually installs the editor. We will see how to use it later. FOr now, we can confirm that it is installed by typing in this command:

$ vim --version

A lot of text will scroll by. YOu can experiment with your mouse to see how to scroll back and see what all of this said. It justs tells you about all the features compiled into your program.

Build Tools

We will be writing C++ programs for the first part of this course. To do that, we need to make sure the required compiler, and a few additional tools are available. Here is the command to do that:

$ sudo apt-get install -y build-essential

You will not be asked for your password as long as this is the same terminal session as before. You can confirm that you now have a C++ compiler by doing this:

$ g++ --version

This is the Free Software Foundation C/C++ compiler, a very good tool used on many serios projects.

Install Git

We will use a tool named Git to manage project code. This is a free tool, available for all platforms. To install it in Linux, do this:

$ sudo apt-get install -y git-core

Again, we can confirm that Git is ready to use by doing this:

$ git --version

There is one last step, you need to do. Unfortunately, we have a problem doing this on the lab machines. On your personal machine do this:

$ git config --global user.name "ROie Black"
$ git config --global user.email "rblack@austincc.edu"

Obviously, you should use you own credential. This creates a file in your home directory that will “brand” your work with your credentials. That way, when you work on a large project everyone can figure out who did what to the code. Very useful!

Final Note

Believe it or not, we are ready to write code! Obviously, we have a few things to learn yet, like how to use this editor thing, and how to build programs. We will get to that soon enough!

If you are eager to get started, go to this site, and practice a bit:

Then look up how to use the Vim editor at this site:

If you get through those two, you are ready for our next lecture!