commonCode (not exclusively for AVRs)

'commonCode' got mentioned on the HaD Blog; Hacklet 31! Awesome! Thanks, y'all!

( http://hackaday.com/2015/01/23/hacklet-31-software-tools/ )

Please comment on, follow, and share this project if it interests you!

Currently, it's in an intermediate state, between:

• Being something I use for dang-near *every* C-based software-project I've made over the past 10+ years (AVR or Desktop)

AND

• Being available to and usable by the public.

I'm all-for making that transition, but there's a lot to be done...

Test-code, comments comments comments, documentation... I need to figure out how to *host* it (a server? Git doesn't seem quite right), and plenty more.

I could really use the support/encouragement.

And if you have ideas of how to make this transition feasible (help pay the bills, etc.), that'd be even better. I can't exactly visualize how to make something like this appeal to an audience like the KickStarter/IndieGoGo/GoFundMe funders... maybe you've ideas to share?

Note that 'commonCode' is a bunch of handy code-snippets/"libraries", but it's more than that... Think 'apt-get' for your microcontroller-project:

• It handles dependencies
• It handles *versions*
• It allows for project-specific configurations without modifying the actual "commonThing's" code
• It creates distributable-packages of projects, containing only the necessary "commonThings"
• Ideally: each "commonThing" will have its own test-code (ala "hello-world") that can easily be the starting-point for--or merged into--your own project...
• It doesn't require anything more than a standard tool-chain (C, preprocessor, make, etc).
• It almost-exclusively runs via "make" commands: 'make fuse' 'make run' 'make localize' 'make delocalize'...
• ...It's also a bunch of useful code.

Was about to post a log saying I could use some beta-testers...

(starting with heartbeat)

Then I realized I forgot to upload the latest version, so started to do that, and realized it's actually quite ugly. There are so many dang files!

Here's the main directory-listing:

comdirEpoxyBlob.mk
_commonCode_localized/
heartbeat_configDesktop.mk
heartbeat_config.mk
heartNoPinStuff.h
main.c
makefile
myMCU.mk
testDesktop.c
__use_Local_CommonCode.mk

Basically, I was attempting two things:

• Combine all tests (both the Desktop-based test-application AND the AVR test-application) into a single package
• Break things up a bit to make the files more intelligible... (e.g. the four .mk files were originally *all* in makefile)

Desktop-Application-Specific files:

• heartbeat_configDesktop.mk
• heartNoPinStuff.h (necessary when not using an AVR)
• testDesktop.c

AVR-Specific:

• heartbeat_config.mk
• myMCU.mk

... Yeah, I think I need to have some directores, e.g.

• configDesktop/
• ...

... yeah I don't have the energy to do it right now. BUT if you want to follow this, that'd be awesome! I could use some followers on this one!