[gentoo-soc] Ebuild Generator week 3 update

This week I've started working on a makefile parser so that I can figure out
additional include paths and which files to scan for includes. And if there
are any extra include paths.

This will hopefully solve some of the problems that I've had so far with
figuring out if includes really are local or global as you can use
#include <file>/"file" to include "local" files that comes with the source
code. Right now "<file>" includes are always treated as global includes and
"file" includes are treated as global ones if the file is not found.

This has it's problems so I'll revisit the local/global include "detection"
when I have more information about the build process.

After the makefile parser is done I should be able to generate a simple
ebuild by looking at makefiles, scan the files that are to be compiled for
includes and link the includes to the appropriate dependecy.
If all goes well I should be able to generate a simple ebuild for the program
"doneyet" (http://code.google.com/p/doneyet/) quite soon.

Other than that I realised that I needed to rework my milestones that I set
up before I started programing.
The problem was that because I haven't done anything like this before I
accidently created milestones that where quite late in the timeline and had
to be done before I could complete the ones before them.
So I have with the help of my mentor rewritten them. These are the new ones:

April 25 - May 23
1: The program is able to parse file structure and file contents of projects.
May 24 - Jun 1
2: Be able to parse .c/.cpp/.h files for includes
Jun 2 - Jun 16
3: Be able to generate a simple ebuild for "make && make install" projects.
If there is extra time work on handeling configure files.
Jun 17 - Jun 27
4: Generate ebuilds for "./configure" projects. If there is extra time work
on autogen/autotool projects
Jun 28 - July 5
5: Add missing features and clean up code.
July 6 - July 13
6: handle autoconf/autogen/autotools
July 14 - July 28
7: Be able to figure out deps that is not installed on the system.
July 29 - Aug 6
9: Bugfixing and code cleanup
Aug 7 - Aug 15
10: Try to support cmake/scons projects

Milestones 1 and 2 are done.
So right now I can "point" the program to a directory and it scan all files
it finds with the supplied filetyp and returns a list with local,global and
ifdef includes.

Now when I've moved on to makefiles I'm really glad that I decided to
"pimp out" my .vimrc file. I'm quite new to all of this (parsing, makefiles)
so it really helped out that my current vim config shows tabs and spaces as
special unicode charaters. That and thanks to the vim highlighting I should
see where I should ignore tabs and when I should not. So even if I didn't
know the makefile syntax I could quite quickly figure out how it worked.

Right now I'm trying to figure out how I should figure out and store the
files that are to be compiled. As you in most cases just type "make" when you
want to build something I'm thinking about just getting the files from the
first make target in the make files. But I'm not sure how I should store the
information. In the end I'm only interested in the dependecies of the *.o
files. Which in most cases is .c/.cpp/.h files.

I were thinking about having it like this:
maketarget → exefile → ofile1 ofile2 ofile3
                            |      |     |
                         cfile1 cfile2 cfile3
                            |      |     |
                         hfile1 hfile2 hfile3

And then when the parser is done take the *.o files and add the sourcefiles
that they depend on them to the list of files to scan for includes so that
files that will not be used doesn't add "ghost" dependecies.