add arc intensity

[tehn]

note this requires a libmonome update (which I can bundle in the next norns update) and also arc firmware update (to be released formally).

there are no plans to add intensity to older edition arcs as they are already super dim.

[tehn]

Ok, this is failing the CI because the testing image doesn't have an updated libmonome.

Which brings me to another point--- the update would be easier-ish if we just included libmonome as a submodule of norns instead of expecting it to be present system-wide (serialosc does this).

I would welcome any strong opinions about this. @artfwo @Dewb

ps. this PR tested with hardware, working well.

[artfwo]

it shouldn't be a big problem, libmonome has a wscript that can be included from norns wscript to build a (static) libmonome to link to.

but given that libmonome is updated not so frequently, how likely we're going to need to change that once the image is up to date?

that said, there may be other reasons to include it as submodule, e.g. dropping a dependency on a package, but not sure if that's still relevant. is libmonome built from source for the image or installed from a .deb?

[Dewb]

For now, changing the version number here should be sufficient to satisfy CI:

norns/Dockerfile

Line 40 in d5bdf1d

LIBMONOME_VERSION=1.4.7 \

This is the CI working as intended by failing until the new dependency is documented. Hooray!

The medium term issue IMO is that the efforts to update CI, developer environment instructions (if people aren’t using the CI image as a devcontainer), and the release image are still three separate things. Moving the libmonome build from Dockerfile to wscript avoids that issue for one dependency, but I think iterating towards a general solution to the bigger issue would pay off across the board.

[Dewb]

Ah @robbielyman and I have one last step to perform to auto-update the image when the Dockerfile changes.

[tehn]

thanks for the tip! corrected the Dockerfile but it seems the CI container needs to be recompiled.

libmonome on the actual disk image is manually compiled from source. the entire process is very by-hand. https://github.com/monome/norns-image/blob/main/build-dev-image.md?plain=1#L88

for the next update I'll simply include the source tree and add that step to modify the disk image.

[Dewb]

one last step to perform to auto-update the image when the Dockerfile changes.

A possible approach for this last step is described in #1853:

Breadcrumbs for next steps on build automation: this config file may also become useful in setting up future Actions workflows such as the ones mentioned in #1842 and #1838.

[Dewb]

The compile check Action will now use the Dockerfile in the PR to run the compilation step, and results will be cached in the container registry. Hooray!

[tehn]

thank you @Dewb !