Starting with build automation

When starting an open source project you want to have a proper build setup that can be automatically building the sources on each commit. This is where Travis-CI comes in. All it needs is a file that tells it what the environment looks like and off we go. So here's the config file for it.
Link the build status

The markdown file in the repo root is displaying the last build status of the master branch now
More ado about the Readme

Getting some structure in
Set up autotools

I chose autotools to build this project, so here are the files that it needs. The autotools should be pretty standard for C projects and they are assumed by Travis-CI, so they seemed fitting best.
Fixing the build

Travis has autotools installed, but noone was telling it to set them up before the build starts. That is done in the "before-build" section in the travix config file.

The changes to the gitignore file keep *.in files out of the repo because they are automatically generated with autoreconf.
Fixing typo

The before-script section has to be a before_script section
Merge pull request #1 from HaMster21/master

Setting up the project a little