On Wed, 24 Dec 2025 at 16:08, Adrian Freihofer via
lists.openembedded.org
<[email protected]> wrote:
> VSCode is started in the workspace folder where the .vscode directory
> is located. With the new bitbake-setup based build layout, this starts
> VSCode in the openembedded-core directory, which means only files in
> that layer are visible. This is not usable for most projects which
> span multiple layers.
...
>  # Generate an initial configuration for VSCode and the yocto-bitbake plugin.
> -if command -v code > /dev/null && [ ! -d "$OEROOT/.vscode" ]; then
> -    oe-setup-vscode "$OEROOT" "$BUILDDIR"

I'm not sure I understand how 'seeing multiple layers' worked before,
or did it? If .vscode is placed into $OEROOT, then only $OEROOT is
visible, e.g. only the former integrated poky repo, but not other
layers.

Otherwise I guess this should be held until we figure out the changes
to bitbake-setup?

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#228551): 
https://lists.openembedded.org/g/openembedded-core/message/228551
Mute This Topic: https://lists.openembedded.org/mt/116929993/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to