CMake Support [breaking change Ctor API]

[joerossrobotics]

This pull request introduces CMake support to the project. This enables use of the library outside of the Arduino ecosystem, just as with the cyphal library. This would be beneficial to many who want to make use of the robustness of 107 systems work, but that operate in frameworks other than Arduino.

[github-actions]

Memory usage change @ 28f719d

Board	flash	%	RAM for global variables	%
arduino:renesas_portenta:portenta_c33	🔺 +176 - +176	+0.01 - +0.01	🔺 +32 - +32	+0.01 - +0.01
arduino:renesas_uno:minima	🔺 +176 - +176	+0.07 - +0.07	🔺 +32 - +32	+0.1 - +0.1
arduino:samd:mkrzero	🔺 +180 - +184	+0.07 - +0.07	🔺 +32 - +32	+0.1 - +0.1
rp2040:rp2040:rpipico	🔺 +160 - +168	+0.01 - +0.01	🔺 +32 - +32	+0.01 - +0.01

Click for full report table

Board	examples/MCP2515-CAN-Sniffer flash	%	examples/MCP2515-CAN-Sniffer RAM for global variables	%	examples/MCP2515-Filter flash	%	examples/MCP2515-Filter RAM for global variables	%	examples/MCP2515-Loopback flash	%	examples/MCP2515-Loopback RAM for global variables	%
arduino:renesas_portenta:portenta_c33	176	0.01	32	0.01	176	0.01	32	0.01	176	0.01	32	0.01
arduino:renesas_uno:minima	176	0.07	32	0.1	176	0.07	32	0.1	176	0.07	32	0.1
arduino:samd:mkrzero	180	0.07	32	0.1	184	0.07	32	0.1	184	0.07	32	0.1
rp2040:rp2040:rpipico	168	0.01	32	0.01	160	0.01	32	0.01	168	0.01	32	0.01

Click for full report CSV

Board,examples/MCP2515-CAN-Sniffer<br>flash,%,examples/MCP2515-CAN-Sniffer<br>RAM for global variables,%,examples/MCP2515-Filter<br>flash,%,examples/MCP2515-Filter<br>RAM for global variables,%,examples/MCP2515-Loopback<br>flash,%,examples/MCP2515-Loopback<br>RAM for global variables,%
arduino:renesas_portenta:portenta_c33,176,0.01,32,0.01,176,0.01,32,0.01,176,0.01,32,0.01
arduino:renesas_uno:minima,176,0.07,32,0.1,176,0.07,32,0.1,176,0.07,32,0.1
arduino:samd:mkrzero,180,0.07,32,0.1,184,0.07,32,0.1,184,0.07,32,0.1
rp2040:rp2040:rpipico,168,0.01,32,0.01,160,0.01,32,0.01,168,0.01,32,0.01

[aentinger]

Define MilliSecondFunc, use instead of MicroSecondFunc.

[github-actions]

Memory usage change @ 577a29d

Board	flash	%	RAM for global variables	%
arduino:renesas_portenta:portenta_c33	🔺 +176 - +176	+0.01 - +0.01	🔺 +32 - +32	+0.01 - +0.01
arduino:renesas_uno:minima	🔺 +176 - +176	+0.07 - +0.07	🔺 +32 - +32	+0.1 - +0.1
arduino:samd:mkrzero	🔺 +180 - +184	+0.07 - +0.07	🔺 +32 - +32	+0.1 - +0.1
rp2040:rp2040:rpipico	🔺 +160 - +168	+0.01 - +0.01	🔺 +32 - +32	+0.01 - +0.01

Click for full report table

Board	examples/MCP2515-CAN-Sniffer flash	%	examples/MCP2515-CAN-Sniffer RAM for global variables	%	examples/MCP2515-Filter flash	%	examples/MCP2515-Filter RAM for global variables	%	examples/MCP2515-Loopback flash	%	examples/MCP2515-Loopback RAM for global variables	%
arduino:renesas_portenta:portenta_c33	176	0.01	32	0.01	176	0.01	32	0.01	176	0.01	32	0.01
arduino:renesas_uno:minima	176	0.07	32	0.1	176	0.07	32	0.1	176	0.07	32	0.1
arduino:samd:mkrzero	180	0.07	32	0.1	184	0.07	32	0.1	184	0.07	32	0.1
rp2040:rp2040:rpipico	168	0.01	32	0.01	160	0.01	32	0.01	168	0.01	32	0.01

Click for full report CSV

Board,examples/MCP2515-CAN-Sniffer<br>flash,%,examples/MCP2515-CAN-Sniffer<br>RAM for global variables,%,examples/MCP2515-Filter<br>flash,%,examples/MCP2515-Filter<br>RAM for global variables,%,examples/MCP2515-Loopback<br>flash,%,examples/MCP2515-Loopback<br>RAM for global variables,%
arduino:renesas_portenta:portenta_c33,176,0.01,32,0.01,176,0.01,32,0.01,176,0.01,32,0.01
arduino:renesas_uno:minima,176,0.07,32,0.1,176,0.07,32,0.1,176,0.07,32,0.1
arduino:samd:mkrzero,180,0.07,32,0.1,184,0.07,32,0.1,184,0.07,32,0.1
rp2040:rp2040:rpipico,168,0.01,32,0.01,160,0.01,32,0.01,168,0.01,32,0.01

[aentinger]

I suggest that you add typedef std::function<unsigned long()> MilliSecondFunc; to MCP2515_Types.h and pass through to the various functions.

[joerossrobotics]

@aentinger I have made that change. This does end up modifying the constructor, are we not concerned about this breaking change?

[aentinger]

You could mitigate it with an default argument, although on second check you can't. Well, I'm okay with a breaking change now and then. This one is allright.

[aentinger]

You'll need to fix the breaking changes in the examples though ...