From: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>
To: yocto-announce@lists.yoctoproject.org, yocto@lists.yoctoproject.org
Cc: Mohammed Raza <mohammed.raza@savoirfairelinux.com>,
Ross Burton <Ross.Burton@arm.com>
Subject: [ANNOUNCEMENT] VSCode Yocto extension v2.2.0 is released
Date: Mon, 4 Mar 2024 11:00:29 +0100 [thread overview]
Message-ID: <1749a243-7e9e-4163-9240-da4e9c4fda82@savoirfairelinux.com> (raw)
Hello,
We are proud to announce the release of v2.2.0 of the official VSCode
Yocto extension.
Download is available through the VSCode marketplace at:
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
Enguerrand de Ribaucourt
Savoir-faire Linux
- --------------------------
Changelog for v2.2.0:
- --------------------------
- Add a new buildConfigurations settings array and status bar to
manage multiple build configurations
- Add a new command to scan a recipe
- Generate definitions and completions for the variables from the
recipe scan
- Generate hovers with final values for the variables from the
recipe scan
- Automatically start the recipe scan instead of a general parse on
save
- Resolve variable expansions after the recipe scan for symbols
resolution
- Restore packaging for Windows, with a limited, stable feature set
- Add a new command to start an interactive bitbake shell
- Add support for colors, links and progress bars in the bitbake terminal
- Add a reference provider for bitbake variables
- Add new problem matchers for bitbake output
- Suppress some false positives from embedded languages diagnostics
- Automatically detect eSDK mode and deprecate previous option
- Add definitions to overrides files
- Add recipes suggestions for all commands if the project has been scanned
- Add a command to open the WORKDIR of a recipe, allowing to inspect
sources, builds and logs
- Forward Python extension's import quick fixes into bitbake files
- Stop resolving relative settings paths into absolute when invoking
bitbake
- Fix a bug where the settings were not properly updated on the
language server
- Various bug fixes and improvements
reply other threads:[~2024-03-04 10:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1749a243-7e9e-4163-9240-da4e9c4fda82@savoirfairelinux.com \
--to=enguerrand.de-ribaucourt@savoirfairelinux.com \
--cc=Ross.Burton@arm.com \
--cc=mohammed.raza@savoirfairelinux.com \
--cc=yocto-announce@lists.yoctoproject.org \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).