From: adrian.freihofer@gmail.com
To: Enguerrand de Ribaucourt
<enguerrand.de-ribaucourt@savoirfairelinux.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] devtool: ide: Fix topdir exception for fallback mode
Date: Fri, 16 Feb 2024 00:02:35 +0100 [thread overview]
Message-ID: <be56443580c80e21a38635e8b2316e8d22445726.camel@gmail.com> (raw)
In-Reply-To: <20240215170422.659073-2-enguerrand.de-ribaucourt@savoirfairelinux.com>
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> 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.py
> b/scripts/lib/devtool/ide_sdk.py
> index 3986dc1436a..db2e95616be 100755
> --- a/scripts/lib/devtool/ide_sdk.py
> +++ b/scripts/lib/devtool/ide_sdk.py
> @@ -366,6 +366,7 @@ class RecipeModified:
> self.target_arch = recipe_d.getVar('TARGET_ARCH')
> self.topdir = recipe_d.getVar('TOPDIR')
> self.workdir = os.path.realpath(recipe_d.getVar('WORKDIR'))
> + self.topdir = os.path.realpath(recipe_d.getVar('TOPDIR'))
I think this patch is not needed. Two lines above the variable is
already initialized.
Some time ago there was an exception but it is fixes on master-next
already.
>
> self.__init_exported_variables(recipe_d)
>
next prev parent reply other threads:[~2024-02-15 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 17:04 [PATCH 0/6] devtool: ide: Improve VSCode support Enguerrand de Ribaucourt
2024-02-15 17:04 ` [PATCH 1/6] devtool: ide: Fix topdir exception for fallback mode Enguerrand de Ribaucourt
2024-02-15 23:02 ` adrian.freihofer [this message]
2024-02-15 17:04 ` [PATCH 2/6] devtool: ide_sdk: Use bitbake's python3 for generated scripts Enguerrand de Ribaucourt
2024-02-15 17:04 ` [PATCH 3/6] devtool: code: Add source mapping for debug source files Enguerrand de Ribaucourt
2024-02-15 23:21 ` adrian.freihofer
2024-02-15 17:04 ` [PATCH 4/6] devtool: ide: vscode: Configure read-only files Enguerrand de Ribaucourt
2024-02-15 17:04 ` [PATCH 5/6] meson: use absolute cross-compiler paths Enguerrand de Ribaucourt
2024-02-15 17:04 ` [PATCH 6/6] devtool: code: Provide a generic C++ configuration Enguerrand de Ribaucourt
2024-02-15 23:15 ` adrian.freihofer
2024-02-15 17:11 ` [OE-core] [PATCH 0/6] devtool: ide: Improve VSCode support Richard Purdie
2024-02-15 22:38 ` Peter Kjellerstedt
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=be56443580c80e21a38635e8b2316e8d22445726.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=enguerrand.de-ribaucourt@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