#avr Logs

Mar 21 2022

05:00 AM specing_ is now known as specing
05:58 AM ville: close
08:35 AM mikee is now known as saxicola
04:59 PM specing_ is now known as specing
10:34 PM WormFood: Do any of you guys have a preferred makefile template for your AVR projects? I see a few online, but I'm a little slow in evaluating them.
10:34 PM Phantom: I always used the same old one that I found, work for me, dunnot if there is any advantage or not
10:35 PM WormFood: The ones I'n seeing online vary quite a bit. Of course, they all do the same basic thing, but they seem to all do it differently.
10:36 PM WormFood: And then there is the business of linking the right libs if you're using printf and/or floating point calculations...I don't remember all the details, but know if you use some features, you have to link additional stuff.
10:40 PM WormFood: One I find is 100 lines long, and another is 500 lines.
10:40 PM WormFood: I feel 500 lines is rather excessive for a makefile
10:41 PM Phantom: http://dpaste.com/5WC67P75N <=== mine
10:41 PM WormFood: Phantom, thanks
11:16 PM Thrashbarg: 500 lines?!
11:27 PM WormFood: I found another one at over 600 lines
11:28 PM Thrashbarg: "Makefiles for Java Programmers"
11:28 PM WormFood: check this one out https://github.com/embecosm/winavr/blob/master/Mfile/data/makefile_template.winavr
11:29 PM WormFood: It seems that many are based on that...617 lines...now granted, there are a few comments....but, take out those comments, and it is....still pretty big
11:29 PM Thrashbarg: hmm
11:30 PM Thrashbarg: mine's 77 lines and includes facilities to flash the target controller
11:30 PM WormFood: one could have a fully functional make file with just a few lines.
11:30 PM Thrashbarg: yup
11:31 PM WormFood: I imagine if you strip out all the cruft from your makefile, it'd probably be 20-40 lines....I'm guessing, but you know.
11:33 PM WormFood: I really wished I knew about makefiles when I was writing my first real C program, of any real size...and that was a video viewer. It was sooo painful to compile *everything* every time something changed (well, it was a single file, but I would have split it up, had a I know then, what I know now)