Then make dep worked. Apparently 1 string function warning.
Now doing make.
EDIT: VCV - Google Drive some built plugins. I think distributing the Rack build itself is not allowed. The plugins thus are all open source and free so that the licence is satisfied by the source from the repository (usually on github, found by the link to the source from the VCV library). DON’T use any other repository (beware name supply chain hacking). Some repositories are not named after the plugin slug. Some are but need some capitalization, and some are verbatim slug named.
Minor issue of cursor turning into white square solved with click.
No library, as developer mode only. Must build modules from source.
What to do after fundamental besides own? That’s maybe tomorrow. Now beer
EDIT: VCV Manual - Building follow Ubuntu instructions. When the make error happens place file in libsamplerate-1.9/Cfg folder. make again. … yes that console clears up where the Fundemental git repo is placed.
Happy Crimbo and New Year '23
PS: perhaps an important edit. The cursor changing into a white square might be a ChromeOS/Wayland issue, but could indicate an assignment blit order race or sequence wrong in rack. ie, at set draw before fill, and a container interaction of set draw to export container, hence fill fail until check shape change on click?
NB: I can only debug to some extent kappaChrome OS Updates and the rest is pricey of chromebook count and accommodation space and time. Also I haven’t read the chromebook source so there is that …
She works armv8-a+fp+simd as the compiler options which flew by said with an aarch64/arm64. So I assume it builds using NEON and or other ARM core FPU vector stuff.
The gate from the QWERTY keyboard always seems to be active. Timer clocking internally works. CV note from QWERTY works. Compile of my own KRTPluginA module works, and so works with at least one arm64 architecture. I can therefore keep up development.