Troubleshooting and remaining scope¶
- Cargo missing/linker failure: put Rust and the platform compiler on PATH; on Windows use x64 Developer PowerShell and matching MSVC Rust.
- Windows blank/editor creation failure: check the installed WebView2 Runtime and loader beside the executable, not just the SDK headers.
- Linux display failure: use X11/XWayland and check DISPLAY; install the 4.1 development packages rather than a different WebKitGTK API version.
- Offline resolution failure: populate the Cargo cache with an ordinary build before selecting Offline. Foundry does not install toolchains or SDKs.
- Regeneration conflict: preserve and reconcile the named managed-file edit; DSP/editor changes do not cause this conflict.
Next work includes component/dependency/MPE selection, platform matrices, additional instrument adapters, richer source/resource navigation and file selection, application packaging, and target-platform UI validation. VST2 is excluded. Proprietary consumers remain separate private workspaces. Validate the generator in disposable external workspaces:
cargo test -p ravet-foundry --locked
python3 scripts/check-foundry.py
python3 scripts/check-foundry.py --build
# Optional native builds/probes with externally installed SDKs:
python3 scripts/check-foundry.py --build --vst3-sdk /path/to/vst3 --audio-unit-sdk /path/to/AudioUnitSDK --aax-sdk /path/to/AAX --lv2-sdk /path/to/lv2 --auv3 --vst3-validator /path/to/validator
Build the debug Foundry executable first. --build adds offline consumer builds,
the offline runnable fixture, effect/instrument CLAP packages and the macOS
standalone hidden UI/audio fixture.
It opens no devices and installs no plug-in. Use --executable /path/to/ravet-foundry
for a separate Cargo target directory.
See decision 0194.