you can add a HEADER file , and you can see in include axo_push.h , which then just 'includes' the source files.
this is perfectly valid in C, just not a common thing to do, as you normally want separate compilation units.
there are a few issues with this approach, the main one I stumbled over was that functions defined (i.e. with code block) in a header file default to being inlined - this causes major code bloat, and was unnecessary for my needs.
this is why you can see I forward declare functions , and explicitly tell them not to be inlined using
(if you need to do this, depends on complexity of your project, if its trivial is unnecessary)
workflow - hmm, was a while ago....
Its unlikely I used an IDE, its more likely a coding editor, possibly SublimeText as Ive been using it for a while, but mostly just to be able to get indentation etc.
I then would have likely been compiling in Axoloti...
if you use 'expert mode' , you can just compile , rather than going live, you can even stop it generating the code.
so process would have been something like
- keep code editor open
- make changes
- use editor to fix code errors,
- go live, to test new functionality
it's possible i might have been compiling the patch from the command line too, you'll find some scripts in the axoloti release if you dig a bit ... but they doesn't really save you much effort.