[ANNOUNCEMENT] VS Code Yocto Project extension v2.8.0 is released

[ANNOUNCEMENT] VS Code Yocto Project extension v2.8.0 is released

[Enguerrand de Ribaucourt]

Hello,

We are thrilled to announce the release of v2.8.0 of the official VS 
Code Yocto Project's extension.

Download is available through the VSCode marketplace at:
  - 
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake

Check out our blog post showcasing the latest features at:
  - 
https://blog.savoirfairelinux.com/en-ca/2025/introducing-the-v2-8-release-of-the-yocto-project-extension-for-vs-code

Happy coding,

Enguerrand de Ribaucourt
Savoir-faire Linux

-------------------------------
Changelog for v2.8.0:
-------------------------------

  - Renamed command "Pick configuration" to "Change active 
buildConfiguration"
  - Automatically re-scan when changing buildConfiguration
  - Cache per-buildConfiguration scan results
  - Make the recipes view appear as "loading" while a scan is ongoing
  - Add "Change active buildConfiguration" to the main contextual menus
  - Update dependencies and make according changes
  - Verify Open VSX publisher for "The Yocto Project"
  - Rate-limit loading bars in the debug logs
  - Add support for the new `devtool modify --debug-build` option
  - Add the "bitbake.disableDevtoolDebugBuild" setting to disable this 
new default behavior
  - Fix an issue with the highlighting of the word "python"
  - Improve compatibility and documentation around kas-container's 
ssh-agent option

Re: [yocto] [ANNOUNCEMENT] VS Code Yocto Project extension v2.8.0 is released

[Marco Cavallini]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Hi Enguerrand,
thank you for updating the extension.

However the most struggling part of this VScode extension is to learn how to setup it with an existing project.
Most of the videos and presentations are showing features like syntax highlighting and so on.

I haven't been able to find any valid document nor video showing how to setup it using a recent VScode YP extension.
Let's suppose one starts from the beginning cloning poky and setting the default 'oe-init-build-env'.
Is the VScode YP extension able to detect the default setting like a build directory and local.conf and bblayers.conf.

Would you mind to point me out to any resource showing that?
Just my two cents ;-)
--
Marco

[-- Attachment #2: Type: text/html, Size: 878 bytes --]

Re: [yocto] [ANNOUNCEMENT] VS Code Yocto Project extension v2.8.0 is released

[Enguerrand de Ribaucourt]

Hello Marco,

The main configuration guide is the README that you will find on the 
extension's marketplace page and github repository [1]. It lists the 
settings which also have their documentation brought up when you write 
your .vscode/settings.json. You'll also find an example for a basic 
oe-init-build-env configuration in the first few lines.

There is also poky/scripts/oe-setup-vscode which will generate a simple 
.vscode/settings.json automatically through oe-init-build-env. You need 
a recent version of poky, and no existing .vscode for it to activate.

We have identified that setting up the extension is currently a bit 
un-intuitive for beginners. This is why we are planning to add a 
"walkthrough" view [2].

Let me know if you need any additional help. You can also submit an 
issue on our github.

Best Regards,

  - [1] github README: https://github.com/yoctoproject/vscode-bitbake
  - [2] walkthrough issue: 
https://github.com/yoctoproject/vscode-bitbake/issues/360

On 11/01/2025 11:43, Marco Cavallini via lists.yoctoproject.org wrote:
> Hi Enguerrand,
> thank you for updating the extension.
> However the most struggling part of this VScode extension is to learn 
> how to setup it with an existing project.
> Most of the videos and presentations are showing features like syntax 
> highlighting and so on.
> I haven't been able to find any valid document nor video showing how to 
> setup it using a recent VScode YP extension.
> Let's suppose one starts from the beginning cloning poky and setting the 
> default 'oe-init-build-env'.
> Is the VScode YP extension able to detect the default setting like a 
> build directory and local.conf and bblayers.conf.
> Would you mind to point me out to any resource showing that?
> Just my two cents ;-)
> --
> Marco

-- 
Savoir-faire Linux
Enguerrand de Ribaucourt

Re: [yocto] [ANNOUNCEMENT] VS Code Yocto Project extension v2.8.0 is released

[Adrian Freihofer]

[-- Attachment #1: Type: text/plain, Size: 3389 bytes --]

Hi Marco,

Here is the commit (and the commit message) which probably explains some
details:
https://git.yoctoproject.org/poky/commit/?id=dfe98713729ceb329813ac00f6035dcfb470b469

I use it like this when I start vscode for the first time in a build
environment:

# Close all VSCode instances
cd poky
rm -rf .vscode  # Make sure .vscode gets generated by oe-init-build-env
. oe-init-build-env
code .

This generates a valid initial configuration for VSCode. Then everything
works as expected.


Using projects with multiple build directories is possible as well. We have
projects where the oe-init-build-env is provided by a layer. It contains
something like this:

# Generate an initial configuration for VSCode and the yocto-bitbake plugin.
OEINIT=$(dirname "$THIS_SCRIPT")
OEINIT=$(readlink -f "$OEINIT")
if command -v code > /dev/null && [ ! -d "$OEINIT/.vscode" ]; then
"$OEINIT"/scripts/oe-setup-vscode "$OEINIT" "$BUILDDIR" "$OEINIT"/build*
fi
unset OEINIT
unset THIS_SCRIPT

This generates a settings.json with

"bitbake.buildConfigurations": [
{ "name": "ccp-sd", "pathToBuildFolder": "${workspaceFolder}/build-1" },
{ "name": "ccp", "pathToBuildFolder": "${workspaceFolder}/build-2" },

which allows you to switch the active build folder from the UI in the right
bottom corner.

Unfortunately it's not 100% self explaining, I agree.

Regards,
Adrian



Am Mo., 13. Jan. 2025 um 09:37 Uhr schrieb Enguerrand de Ribaucourt <
enguerrand.de-ribaucourt@savoirfairelinux.com>:

> Hello Marco,
>
> The main configuration guide is the README that you will find on the
> extension's marketplace page and github repository [1]. It lists the
> settings which also have their documentation brought up when you write
> your .vscode/settings.json. You'll also find an example for a basic
> oe-init-build-env configuration in the first few lines.
>
> There is also poky/scripts/oe-setup-vscode which will generate a simple
> .vscode/settings.json automatically through oe-init-build-env. You need
> a recent version of poky, and no existing .vscode for it to activate.
>
> We have identified that setting up the extension is currently a bit
> un-intuitive for beginners. This is why we are planning to add a
> "walkthrough" view [2].
>
> Let me know if you need any additional help. You can also submit an
> issue on our github.
>
> Best Regards,
>
>   - [1] github README: https://github.com/yoctoproject/vscode-bitbake
>   - [2] walkthrough issue:
> https://github.com/yoctoproject/vscode-bitbake/issues/360
>
> On 11/01/2025 11:43, Marco Cavallini via lists.yoctoproject.org wrote:
> > Hi Enguerrand,
> > thank you for updating the extension.
> > However the most struggling part of this VScode extension is to learn
> > how to setup it with an existing project.
> > Most of the videos and presentations are showing features like syntax
> > highlighting and so on.
> > I haven't been able to find any valid document nor video showing how to
> > setup it using a recent VScode YP extension.
> > Let's suppose one starts from the beginning cloning poky and setting the
> > default 'oe-init-build-env'.
> > Is the VScode YP extension able to detect the default setting like a
> > build directory and local.conf and bblayers.conf.
> > Would you mind to point me out to any resource showing that?
> > Just my two cents ;-)
> > --
> > Marco
>
> --
> Savoir-faire Linux
> Enguerrand de Ribaucourt
>

[-- Attachment #2: Type: text/html, Size: 9332 bytes --]