Great explanation and fix!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196188):
https://lists.openembedded.org/g/openembedded-core/message/196188
Mute This Topic: https://lists.openembedded.org/mt/104570748/21656
Group Owner: openembedded-core+o
On 22/02/2024 14:00, adrian.freiho...@gmail.com wrote:
On Wed, 2024-02-21 at 15:56 +0100, Enguerrand de Ribaucourt wrote:
On 21/02/2024 15:12, Enguerrand de Ribaucourt wrote:
On 20/02/2024 10:01, adrian.freiho...@gmail.com wrote:
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de
a fork from python-progressbar. It hasn't been
refreshed in 8 years. We did only two commits, 5 years ago with minor
modifications. This new change is also not how the upstream project is
behaving.
Signed-off-by: Enguerrand de Ribaucourt
---
bitbake/lib/progressbar/progressbar.py |
the compile_commands.json. The next
commits adds the necessary configuration. We can revert this one and
keep the meson paths as they were.
Signed-off-by: Enguerrand de Ribaucourt
---
meta/classes-recipe/meson-routines.bbclass | 6 --
meta/classes-recipe/meson.bbclass | 7
A feature in vscode-cpptools was just added that allow us to pass the absolute
compiler path through the devtool ide-sdk generated configuration. We can
revert the meson.bbclass modification to avoid any potential issues with using
absolute paths in meson.cross.
-=-=-=-=-=-=-=-=-=-=-=-
Links: Yo
: Enguerrand de Ribaucourt
---
scripts/lib/devtool/ide_plugins/ide_code.py | 1 +
scripts/lib/devtool/ide_sdk.py | 3 +++
2 files changed, 4 insertions(+)
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
b/scripts/lib/devtool/ide_plugins/ide_code.py
index f44665ed872
On 21/02/2024 15:12, Enguerrand de Ribaucourt wrote:
On 20/02/2024 10:01, adrian.freiho...@gmail.com wrote:
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
When launching the debug configuration, the source files from the
debug
rootfs were openened in the editor instead
On 20/02/2024 10:01, adrian.freiho...@gmail.com wrote:
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
When launching the debug configuration, the source files from the
debug
rootfs were openened in the editor instead of the local workspace
files.
We add an exception to
pp-example with autotools support (already on my branch)
- What your patch does
- Extend the oe-selftest suite to cover also the autotools support.
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
By default, the cpptools VSCode extension will use the host's headers
and fla
ned-off-by: Enguerrand de Ribaucourt
---
scripts/lib/devtool/ide_plugins/__init__.py | 3 +++
scripts/lib/devtool/ide_plugins/ide_code.py | 27 +
scripts/lib/devtool/ide_sdk.py | 5
3 files changed, 25 insertions(+), 10 deletions(-)
diff --git a/scripts/l
changes. Meanwhile, we should prevent write access to them.
Signed-off-by: Enguerrand de Ribaucourt
---
scripts/lib/devtool/ide_plugins/ide_code.py | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
b/scripts/lib/devtool
following exception:
AssertionError: SRE module mismatch
We need to match the sys.executable to the sys.path.
Signed-off-by: Enguerrand de Ribaucourt
---
scripts/lib/devtool/ide_sdk.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/ide_sdk.py b
en opened with meson/ninja maintainers to implement
this at their level:
- https://github.com/ninja-build/ninja/issues/2383
- https://github.com/mesonbuild/meson/issues/12834
These tools have even less information on the environment so it makes
sense for Yocto to provide the absolute paths.
Signed-o
would expect compared to native development.
This is also true for the devtool fallback mode.
Signed-off-by: Enguerrand de Ribaucourt
---
scripts/lib/devtool/ide_plugins/ide_code.py | 1 +
scripts/lib/devtool/ide_sdk.py | 1 +
2 files changed, 2 insertions(+)
diff --git a/scripts
These patches improve the VSCode support in devtool ide-sdk from Adrian
Freihofer.
I added a generic C++ configuration for the VScode extension while
awaiting for autotools support.
A refactoring is proposed for the meson class. Without absolute compiler
paths, the linter inside VSCode will not b
By default, the cpptools VSCode extension will use the host's headers
and flags for linting. This results in a lot of include errors and
misleading definitions. Even though this generic configuration doesn't
include all the depenendencies, it is a proper fallback for recipe
classes we do not accura
Among the files generated by meson is compile_commands.json. It is not
used by bitbake during the build. However, if the devtool workspace is
opened inside an IDE, that IDE can use compile_commands.json to
configure linting and code completion. This is notably relied on by the
new devtool ide-sdk c
When debugging or browsing files, the user may fall into external
sources from other packages in the sysroot or dbg-rootfs. Modifying them
will only lead to confusion since they will be overwritten by Yocto. The
user should open them in a separate devtool modify session if they want
to make changes
These patches improve the VSCode support in devtool ide-sdk from
Adrian Freihofer.
I added a generic C++ configuration for the VScode
extension while awaiting for autotools support.
A refactoring is proposed for the meson class. Without absolute compiler
paths, the linter inside VSCode will not b
The generated scripts use the sys.path configuration found inside
bitbake. It can be a different python version than the one used on the
host through the IDE.
For instance, when running the generated script
deploy_target_cmake-example-core2-64 from an eSDK generated on another
machine, I got the f
An exception was raised because we did not have the topdir attribute
which was used in fallback mode (non cmake/meson recipes).
Already in the merge queue in Adrian's latest patches.
---
scripts/lib/devtool/ide_sdk.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/lib/devtool/ide_sdk
When launching the debug configuration, the source files from the debug
rootfs were openened in the editor instead of the local workspace files.
We add an exception to properly map them to the file being developed and
compiled by the IDE integration. This also more closely matches what the
user wou
While the debug-only rootfs is not usable by itself, changing the way it's
currently combined (from the doc) could produce unintended side effects.
Check out this post for explanations:
https://lists.openembedded.org/g/openembedded-core/message/190490
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive a
Hello Adrian,
It's a nice idea to have VSCode settings for users who want to edit poky for
the reasons you mention!
I think it would be nice to have such a configuration as a reference in the
vscode-bitbake documentation as well. You could event contribute it yourself if
you wish
https://githu
On Thu, Oct 12, 2023 at 02:53 PM, Ross Burton wrote:
>
> I’d not noticed image-combined-dbg existed and do wonder if that shoud be
> the behaviour of the debug rootfs. Is there actually a use-case for a tarball
> which is _just_ the symbols?
>
The use for a rootfs containing just the debug tarbal
- Original Message -
> From: "Alexandre Belloni"
> To: "Enguerrand de Ribaucourt"
> Cc: openembedded-core@lists.openembedded.org
> Sent: Wednesday, March 23, 2022 4:35:32 PM
> Subject: Re: [OE-core][PATCH] mobile-broadband-provider-info: update branch
The master branch was renamed main, resulting in do_fetch failure.
This patch updates SRC_URI with the new branch name.
Signed-off-by: Enguerrand de Ribaucourt
---
.../mobile-broadband-provider-info_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
27 matches
Mail list logo
