Yup. It means making a
The makefile should serve as a good base for what settings need to be filled with what though.
It should at least give a clue as to what the compiler settings should be.
Otherwise it’s going to just be a matter of knucking down and fighting the documentation.
On the other hand, aparently Code::Blocks can use custom makefiles to build.
We’re already recommending Code::Blocks for the simulator, so maybe that would be a good stepping stone?
(Also EmBitz is a fork of Code::Blocks, so the UI is quite similar - shouldn’t be a major leap for those who are used to EmBitz.)
That was a fast reply.
I was thinking more about how far you had gotten.
If you had a half-built
platformio.ini, that could possibly serve as a starting point.
Can’t get mbed online or EmBitz working?
Or just don’t want to use either?
While I’m thinking of library things.
I cannot deny how useful
I find myself using
Buttons::held in an attempt to simulate it, so a future buttons API would do well to accomodate both the current ‘timed’ functions and something more like
Come to think of it, if the buttons are updated via interrupt, what metric/time interval is used for defining the
timeHeld (and related functions)?
Is it the number of calls to