BlackMark
52faaf9920
The pin moves to libavr's USI I2C rate fix and to the two override surfaces the fan-controller port filed - a PWM solve that can be pinned, and a capture edge that is a value rather than a template argument. Nothing here names any of them; four presets green and no image moved. `tools/check.sh` is new, and its absence was the defect: this repository had no committed gate at all, so "run the suite" was a snippet somebody remembered - and the order in a snippet is the one thing nobody re-derives. Every preset built before any is tested is subtle and load-bearing, because the mode-identity check reads the sibling mode's tree and a build-then-test-per- preset run holds a fresh image against a stale sibling. The loop is libavr's `tools/check-presets.sh`; nothing is written after the call, there being nothing beyond the presets this repository knows to ask. And `.vscode/settings.json` stops naming a toolchain prefix. It named `D:/dev/libavr/local/toolchain/avr-gcc-16.1.0-mingw`: a path true of one machine (libavr guidance rule 50) and, since the in-repo toolchain copies went, true of none. `local/machine.cmake` is where a checkout says that, and it already did. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
37 lines
1.3 KiB
JSON
37 lines
1.3 KiB
JSON
{
|
|
// clangd is the language server; the cpptools engine would parse every file
|
|
// a second time and disagree, since nothing tells it about a cross
|
|
// compiler.
|
|
"C_Cpp.intelliSenseEngine": "disabled",
|
|
|
|
// --query-driver lets clangd ask the cross compiler for its own system
|
|
// includes and target. The database is named here rather than in .clangd
|
|
// because that file travels with the driver into a consumer's submodule,
|
|
// where a build tree of this repo's own need not exist.
|
|
"clangd.arguments": [
|
|
"--compile-commands-dir=${workspaceFolder}/build/atmega328p-generated",
|
|
"--query-driver=**avr-g++*",
|
|
"--header-insertion=never"
|
|
],
|
|
|
|
// The presets are the build interface, and the toolchain file inside the
|
|
// libavr submodule is the one place the compiler is chosen. **No prefix is
|
|
// named here**: a committed file may not name a path that is true of one
|
|
// machine (libavr guidance rule 50), so the gitignored local/machine.cmake
|
|
// at this repository's root is where a checkout says where its toolchain
|
|
// is - one file, and it answers for both hosts.
|
|
"cmake.useCMakePresets": "always",
|
|
"cmake.configureOnOpen": true,
|
|
"cmake.options.statusBarVisibility": "compact",
|
|
|
|
"files.watcherExclude": {
|
|
"**/build/**": true,
|
|
"**/libavr/**": true
|
|
},
|
|
|
|
"files.associations": {
|
|
".clangd": "yaml",
|
|
".clang-format": "yaml"
|
|
}
|
|
}
|