Re: [avr-gcc-list] makefile for ubuntu

[Patrick Blanchard]

On Thu, 2005-10-13 at 20:10 -0500, David Kelly wrote:
> On Thu, Oct 13, 2005 at 10:33:45AM -0500, Patrick Blanchard wrote:
> 
> > I would shy away from the makefile approach until you are capable of
> > understanding the linux tooling process from start to finish. The
> > WinAVR makefile is bloated for microsofties, so it takes a lot of
> > wading thru the makefile to set what you require for linux.
> 
> You lost me in "linux tooling process".

I have yet to find 2 linux boxes 'tooled' the same way. I have for
example, one box 'tooled' as a fax server w/ hylafax. another is
'tooled' for an internal web server for my company forum and email.
Another is my personal box, and yet 2 others reside in our lab for
electronics.

"tooling up" is slang often used in machine shops. It means getting
ready to make something with a lath or mill or welding jig.

IIRC, the OP wanted a dev environment, or a set of tools to produce
something w/ AVR. 

http://tinyurl.com/8p9qq 
tool·ing   
     1. Work or ornamentation done with tools, especially stamped or
        gilded designs on leather.
     2. The process of providing a factory with machinery in preparation
        for production.

I have 10+ years dabbling w/ precision lathes and mills and <1 year w/
linux. but 'tooling up' fits both disciplines. Linux is a lot cleaner
than lathe and mill work though. :)

>  The Makefile I sent to Vincent
> which was reposted here yesterday works unchanged on WinAVR, FreeBSD,
> and undoubtedly on Vincent's Linux.

It will probably work, but only until Vincent tries it on his own linux
box (which is different from my linux box(es)) will he be undoubtedly
certain that it works or not. And if it doesn't work, it might get him
so frustrated that he gives up linux for good.

> 
> Once past the bloat of WinAVR's generic Makefile the workings of Make
> becomes simple and beautiful. No matter the one I provided has some
> "advanced" features such as a generated depend list. One of Joerg's demo
> project Makefiles, IIRC the twi demo, got me over the hump as to what
> avr-gcc needed.

I couldn't write an advanced makefile like you did. But I think we agree
on this issue of a lot of stuff in the makefile - bloat doesn't make it
a bad thing always, just sometimes later on when you don't want to wade
through a large makefile to change one line, and sometimes early on when
you just need to know your toolchain works.