Compiled using WinAVR. A few messages, but nothing scary so far.
Hmm. What if I tried to make the footprint smaller to see if it would fit in another device? (I won't bother readers by explaining why unless you want to know. Ask if you do.)
Why ? Which device ?
I have a 1951 Fergie that I use around the house. It runs crappy and is more thirsty than a 1970's popstar. I thought it might be a nice 1'st project to play around with a DIY ignjection system. There would be no space (or environment) for an LCD. It would have to be a bit more compact and resistant to harsh environment. I was hoping to use a PCB I have a number of from a project I've done at work and just solder on the missing components dead-bug style. It uses ATmega16/32. I would like to see if I could get the footprint down to match it by removing the modules not needed. And I could play with it between Christmas/New Year as I have a week off. I would not get the V3 board in time. BTW. My compliments on the project. It took me less than 15min from start of download to first .hex code. It fit straight into my existing environment. Looks very clean. I don't expect anyone to take much interest in such a low perf. app, but even if it does not go well, it will let me get a feel for how the code is built up.
Commenting out "# MY_CONF += -D LCD" makes it barf on missing functions. Someone forgot to #ENDIF <stub code>. I suggest either taking out the indication in my_make it can be done, or correcting code so it can.
Obviously, it is possible to fix it to compile without LCD, and magicstr.h and varstr.h and lcd_display.c would free much space. Also, much inlining eats space. 64 kbyte flash would be possible, but 32kbyte would mean serious compromise.
I'll better go have a sightseeing in the code and see if it may be too much other stuff making it difficult to fit in another device.
I think (even if it's possible), it's a waste of time to fit in a smaller device. Also note that the code is covered by copyright (open != freeware).
If you want to help making the code (more) portable, it's possible that you get SubVersionSvn access for the trunk (codetree that has been started to be ported for ARM), but signing a lightish NDA is necessary, and firmware developers must see your intentions clearly.