Skip to content

vscode: switch S to UNPACKDIR for whinlatter+#3

Merged
EmbeddedAndroid merged 2 commits into
mainfrom
unpackdir-compat
May 14, 2026
Merged

vscode: switch S to UNPACKDIR for whinlatter+#3
EmbeddedAndroid merged 2 commits into
mainfrom
unpackdir-compat

Conversation

@EmbeddedAndroid

Copy link
Copy Markdown
Owner

Whinlatter and wrynose split WORKDIR and UNPACKDIR — do_unpack extracts under UNPACKDIR, while WORKDIR is now reserved for build artefacts. The recipe was setting S to a path under WORKDIR which now produces a fatal error: "S should be set relative to UNPACKDIR".

Caught by the per-release CI sweep on the whinlatter and wrynose branches.

Fix: switch S to ${UNPACKDIR}/VSCode-linux-${VSCODE_ARCH}, with a UNPACKDIR ??= "${WORKDIR}" fallback so kirkstone..walnascar (which don't define UNPACKDIR) keep working.

Whinlatter and wrynose split WORKDIR and UNPACKDIR; do_unpack
extracts under UNPACKDIR while WORKDIR is reserved for build
artefacts. The recipe used to set S = ${WORKDIR}/VSCode-linux-...
which now produces 'S should be set relative to UNPACKDIR' as a
fatal error.

Switch to S = ${UNPACKDIR}/... with a kirkstone..walnascar
fallback via UNPACKDIR ??= ${WORKDIR} so older releases that
don't define UNPACKDIR keep working.
The first cut at this fix set UNPACKDIR ??= ${WORKDIR} so kirkstone /
scarthgap (which don't define UNPACKDIR) would still work, but
bitbake.conf on styhead+ rejects the literal 'UNPACKDIR = ${WORKDIR}'
assignment ('Using UNPACKDIR = ${WORKDIR} is not supported').

Compute the prefix via a Python expression instead: use UNPACKDIR if
the release has set one, fall back to WORKDIR otherwise. Same end
result on every supported release without tripping the assertion.
@EmbeddedAndroid EmbeddedAndroid merged commit 697392e into main May 14, 2026
22 checks passed
@EmbeddedAndroid EmbeddedAndroid deleted the unpackdir-compat branch May 14, 2026 19:41
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