From: adrian.freihofer@gmail.com
To: Enguerrand de Ribaucourt
<enguerrand.de-ribaucourt@savoirfairelinux.com>,
openembedded-core@lists.openembedded.org
Cc: Ross.Burton@arm.com, mohammed.raza@savoirfairelinux.com
Subject: Re: [PATCH v2 2/5] devtool: code: Add source mapping for debug source files
Date: Tue, 20 Feb 2024 10:01:47 +0100 [thread overview]
Message-ID: <4a89e1327bf1595361c98d200f15a36daefca0a6.camel@gmail.com> (raw)
In-Reply-To: <20240219165525.714512-3-enguerrand.de-ribaucourt@savoirfairelinux.com>
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 properly map them to the file being developed
> and
> compiled by the IDE integration. This also more closely matches what
> the
> user would expect compared to native development.
>
> This is also true for the devtool fallback mode.
This looks still wrong to me. If files from the rootfs are openend for
a recipe which is in the workspace, the SDK is broken and we need to
understand and fix that. This patch does not solve that, but will make
it much harder to find the right solution for this issue.
Adrian
>
> Signed-off-by: Enguerrand de Ribaucourt
> <enguerrand.de-ribaucourt@savoirfairelinux.com>
> ---
> 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/lib/devtool/ide_plugins/ide_code.py
> b/scripts/lib/devtool/ide_plugins/ide_code.py
> index b2193130d2e..c063b7d0590 100644
> --- a/scripts/lib/devtool/ide_plugins/ide_code.py
> +++ b/scripts/lib/devtool/ide_plugins/ide_code.py
> @@ -234,6 +234,7 @@ class IdeVSCode(IdeBase):
> if gdb_cross_config.image_recipe.rootfs_dbg:
> launch_config['additionalSOLibSearchPath'] =
> modified_recipe.solib_search_path_str(
> gdb_cross_config.image_recipe)
> + src_file_map[os.path.join("/usr/src/debug",
> modified_recipe.pn, modified_recipe.pv)] = "${workspaceFolder}"
> src_file_map["/usr/src/debug"] = os.path.join(
> gdb_cross_config.image_recipe.rootfs_dbg, "usr",
> "src", "debug")
> else:
> diff --git a/scripts/lib/devtool/ide_sdk.py
> b/scripts/lib/devtool/ide_sdk.py
> index 14679744807..f292edbe25c 100755
> --- a/scripts/lib/devtool/ide_sdk.py
> +++ b/scripts/lib/devtool/ide_sdk.py
> @@ -356,6 +356,7 @@ class RecipeModified:
> 'PACKAGE_DEBUG_SPLIT_STYLE')
> self.path = recipe_d.getVar('PATH')
> self.pn = recipe_d.getVar('PN')
> + self.pv = recipe_d.getVar('PV')
> self.recipe_sysroot = os.path.realpath(
> recipe_d.getVar('RECIPE_SYSROOT'))
> self.recipe_sysroot_native = os.path.realpath(
next prev parent reply other threads:[~2024-02-20 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:55 [PATCH v2 0/5] devtool: ide: Improve VSCode support Enguerrand de Ribaucourt
2024-02-19 16:55 ` [PATCH v2 1/5] devtool: ide_sdk: Use bitbake's python3 for generated scripts Enguerrand de Ribaucourt
2024-02-20 9:03 ` adrian.freihofer
2024-02-19 16:55 ` [PATCH v2 2/5] devtool: code: Add source mapping for debug source files Enguerrand de Ribaucourt
2024-02-20 9:01 ` adrian.freihofer [this message]
2024-02-21 14:12 ` Enguerrand de Ribaucourt
2024-02-21 14:56 ` Enguerrand de Ribaucourt
2024-02-22 13:00 ` adrian.freihofer
2024-02-22 15:51 ` Enguerrand de Ribaucourt
2024-02-25 20:52 ` adrian.freihofer
2024-02-19 16:55 ` [PATCH v2 3/5] devtool: ide: vscode: Configure read-only files Enguerrand de Ribaucourt
2024-02-20 9:05 ` adrian.freihofer
2024-02-19 16:55 ` [PATCH v2 4/5] meson: use absolute cross-compiler paths Enguerrand de Ribaucourt
2024-02-20 12:54 ` [OE-core] " Richard Purdie
2024-02-19 16:55 ` [PATCH v2 5/5] devtool: code: Provide a generic C++ configuration Enguerrand de Ribaucourt
2024-02-20 9:20 ` adrian.freihofer
2024-02-20 9:27 ` Enguerrand de Ribaucourt
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=4a89e1327bf1595361c98d200f15a36daefca0a6.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=enguerrand.de-ribaucourt@savoirfairelinux.com \
--cc=mohammed.raza@savoirfairelinux.com \
--cc=openembedded-core@lists.openembedded.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