Compiling .ino files

[laupow]

Story details: https://app.shortcut.com/particle/story/117875

I embedded code from https://github.com/particle-iot/buildpack-wiring-preprocessor to mirror the cloud compiler's preprocessing step.

Do we have any other places that use this code @suda? I'm ok embedding the cparser code this way.

depends on #10

[keeramis]

@laupow thanks for the changes. Overall as I scanned through, the PR looks good to me. Does it make sense for me to test this locally and if yes, could you please point me to any testing instructions that I can try to use?

[laupow]

@keeramis Yeah, it's likely a good idea to test a ino firmware. I tested two different apps myself.

To test these changes locally, you can checkout this branch and then run the steps over here:

https://github.com/particle-iot/compile-action/blob/main/DEVELOPMENT.md

For the npm start command, replace the sources path in INPUT_SOURCES-FOLDER=test/fixtures/single-file-firmware with a path to some firmware on your computer that is ino files (not cpp files). You'll need Docker running on your machine to successfully compile.

I added a copy of Tinker and this PR adds some checks to make sure Tinker (in an ino file) compiles

[keeramis]

Works as expected. 👍

• INPUT_DEVICE-OS-VERSION=default gives the default/most relevant device-os version for that platform (ex: electron points to 2.3.1, tracker points to 4.0.2, p2 points to 5.3.1)
• INPUT_DEVICE-OS-VERSION=latest_lts gives it's LTS version is available (ex: electron points to 2.3.1, tracker points to 4.0.2, p2 gives an error)
• INPUT_DEVICE-OS-VERSION=latest gives the latest (ex: electron points to 3.3.1, tracker points to 5.3.1)