Skip to content

Add zephyr sdk 1.0 - #26

Merged
jaredwolff merged 15 commits into
mainfrom
add-zephyr-sdk-1.0
Jun 20, 2026
Merged

jaredwolff merged 15 commits into
mainfrom
add-zephyr-sdk-1.0

Conversation

@jaredwolff

Copy link
Copy Markdown
Contributor

No description provided.

jaredwolff and others added 15 commits May 14, 2026 17:41
Add log_dictionary.json as a build asset shown in the sidebar. Replace
the brittle extractChipName path computation with a file search that
handles sysbuild, non-sysbuild, and chip-qualified build directories.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Upgrade in place with --upgrade when the venv is healthy; only remove
and recreate if the Python binary is missing or the upgrade fails.
…ectron

- Bump @types/node, @types/vscode, esbuild, eslint, typescript, and others
- Replace deprecated vscode-test with @vscode/test-electron
- Fix mocha import for updated typings
- Add qs override; ignore local agent state (.claude/, .codex)
- Switch download verification from md5 to sha256
- Drop unused validateMd5 helper
- Update manifest entries with sha256 checksums and zephyr-sdk-1.0.0 toolchains
…to-selection

Separate SDK/toolchain management from the host-tools Setup so multiple SDK
versions can coexist and each workspace uses the one its Zephyr tree requires.

- Setup now installs host tooling only; SDKs are managed separately
- Add 'Install SDK' command and on-demand install prompt before builds
- Add 'Manage SDKs' command to list/activate/uninstall installed SDKs
- Make ZEPHYR_SDK_INSTALL_DIR workspace-scoped (paths.sdkInstallDir)
- Auto-switch to a compatible installed SDK based on the Zephyr tree's
  required version, accounting for the SDK's minimum-compatible floor
- Resync the environment variable collection before builds so tasks use the
  active SDK instead of a stale value
- Extract shared download engine into download-processor.ts
- Surface SDK state and a Manage SDKs action in the sidebar
…rements command

Keep the venv in sync when a Zephyr version bump changes dependencies, instead
of requiring a full re-init.

- Update now runs west update -> re-resolve SDK -> reinstall Python requirements
- Prefer "west packages pip --install" (collects requirements across all west
  modules) with a fallback to zephyr/scripts/requirements.txt on older trees
- Add standalone "Zephyr Tools: Install Python Requirements" command
- Refresh the sidebar after update so SDK state reflects the updated tree
SDK 1.0 moved GNU toolchains under <sdk>/gnu/<triple>, which broke installs and
conflated SDK state with the host-tools setup flag.

- Extract the SDK 1.0 GNU toolchain into gnu/ and fix its PATH suffix (linux/win/mac)
- Resolve the SDK ARM toolchain bin path layout-aware (gnu/ for 1.0+, root for 0.x)
- Verify the toolchain payload is actually present (not just the version) when
  judging SDK compatibility; report incomplete installs distinctly
- Stop SDK problems from clearing the host-setup flag, and self-heal isSetup when
  host tooling is present
- Surface SDK readiness in the sidebar independently and refresh on sdkInstallDir change
- Split clear-target path on both separators so Windows clears the right directory
Make the SDK install automatic and keep the host-setup/project state from
drifting, so a fresh Setup -> Init Repo reaches a build-ready state with no
extra prompts or dead-ends.

- Install the required SDK automatically (no version prompt); Init Repo now
  installs it as its final step, and build/update do so as a silent safety net
- Setup installs host tooling only; the SDK is handled once the tree is known
- Persist ZEPHYR_BASE during init and resolve it robustly in checkSdkCompatibility
  (detect + persist) so the SDK check never silently skips
- Keep the in-memory global config in sync after self-heal, and reload it in the
  init-repo guard, so Resume no longer wrongly reports "Run setup first"
- Self-heal isInit when .west and a fetched Zephyr tree are present, so a
  complete-on-disk project is not mislabeled "incomplete"
Two correctness fixes for the multi-SDK/workspace selection flow:

- installSdkCommand now fails when checkSdkCompatibility still reports an
  error after extraction, instead of returning true and letting build/update
  proceed into CMake with an unusable SDK.

- Make the workspace-scoped paths.sdkInstallDir the single source of truth.
  Stop persisting ZEPHYR_SDK_INSTALL_DIR through the generic global env path,
  remove the global env-var fallback in getSdkInstallDir, and migrate any
  legacy global value into the workspace setting once on activation. Rebuild
  the PATH/ZEPHYR_SDK_INSTALL_DIR env-collection mutators in
  setupEnvironmentPaths, explicitly deleting them when no SDK is selected, so
  an uninstalled or switched-away SDK can no longer linger.
…arm64

- Unit tests for version compatibility (minimum-compatible floor, >= check) and
  SDK recommendation
- Fixture-based tests for required/installed/min-compat parsing, the gnu/ vs root
  toolchain layout, and compatible-SDK selection (incl. skipping incomplete SDKs)
- GitHub Actions workflow running tests + lint + compile on ubuntu, windows, and
  macos-14 (arm64)
- Changelog entry and version bump for SDK 1.0 support
- Clear dependency advisories: esbuild 0.28.1, js-yaml override >=4.2.0
  (qs already pinned to patched 6.15.2 via override)
…ntents

- Pin @types/vscode to ~1.101.0 so it matches engines.vscode ^1.101.0 (vsce
  rejects types newer than the declared minimum); regression from the dep bump
- Exclude local agent state (.claude/, .codex) and the flat eslint config from
  the packaged VSIX
A space anywhere in the Zephyr SDK install path breaks GNU-toolchain
linking on Windows: GCC emits its built-in library search paths
unquoted, so ld splits the -L flag at the space and fails. This is a
hard toolchain limitation, not fixable by quoting our own commands.

- Default install location falls back to a space-free path at the root
  of the home drive (e.g. C:\.zephyrtools) when the home directory
  contains a space
- Setup refuses a spaced install path on Windows with a clear message
  instead of failing cryptically deep in the build
- Add deterministic cross-platform tests for both behaviors

Release 0.6.1.
@jaredwolff

Copy link
Copy Markdown
Contributor Author

Merging — Zephyr SDK 1.0 support landed, shipped as 0.6.1.

Highlights:

  • SDK 1.0 gnu/<triple> toolchain layout + per-workspace SDK management (Install SDK / Manage SDKs, auto-selection against each tree's required version)
  • Setup decoupled from SDK install; Init Repo installs the required SDK automatically
  • Final fix (0.6.1): on Windows the SDK no longer installs under a path containing a space (e.g. C:\Users\Jared Wolff\.zephyrtools), which broke linking — GCC emits its built-in -L search paths unquoted, so ld split at the space. Defaults to a space-free location (C:\.zephyrtools) and Setup now refuses a spaced path with a clear message.

CI green across Linux, Windows, and macOS.

@jaredwolff
jaredwolff merged commit 855b7e4 into main Jun 20, 2026
6 checks passed
@jaredwolff
jaredwolff deleted the add-zephyr-sdk-1.0 branch June 20, 2026 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant