Some structure...

[Jop... (Jonas F. Jensen).]

Hi,

I turned in my final project a few days ago, so I'm back with more
time for this project... :)
unfortunately, my project was also my development board... But I've
got a few atmega644 so I'll be building a new soon... Right now I'm
stuck with a simple atmega168 board from TuxGraphics, but it works...

I don't know if anybody else was working on the current revision...
However, as it's mostly my mess (e.g. my code)... I figured I'd clean
it up and add some structure to it...

I've just restructured the directory layout and written a new build
system using make... It should be in SVN by now...

I've written a small doc about how it's to be used, see: structure.txt
in trunk
http://code.google.com/p/avr-uip/source/browse/trunk/structure.txt#
(I guess we could move this file into the wiki and/or docs directory).

Well, what do you think... If it's all bad we can always go a revision
back :)

Note: instead of creating different branches for different boards... I
suggest we make different subdirectories in the directory called
projects (it would sound wrong if I suggested making different
projects, perhaps a better terminology is required :) )...
By doing this we'd be able to run and update/modify the same generic
code for drivers, libraries and uip... Since driver configuration etc.
is placed in the project specific directory...
This would also make upgrades from one avr-uip version to the next far
less painful...

Right now I've created a project directory called TuxGraphics... To
support the board from:
http://tuxgraphics.org/electronics/200611/embedded-webserver.shtml

Anyway let me know what you think... we can't let this project die
already :)
Also, I still can't decide if drivers should be able to depend on
libraries or if libraries should be able to depend on drivers... See
the last section in structure.txt, this is a restriction because
makefiles from apps, drivers and libraries are included using 3
loops... So I've got to include either the makefiles from libs or
drivers first... The last one of the included makefiles won't be able
to modify the other include variable, hence LIBS or DEVS.

//Regards Jonas Finnemann Jensen.