public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Adrian Freihofer" <adrian.freihofer@gmail.com>,
	<docs@lists.yoctoproject.org>
Cc: "Adrian Freihofer" <adrian.freihofer@siemens.com>
Subject: Re: [PATCH v3] sdk-manual: extensible.rst: devtool ide-sdk improve
Date: Mon, 20 Jan 2025 09:30:35 +0100	[thread overview]
Message-ID: <D76RDCSD5GRB.27GJNWE79OPLB@bootlin.com> (raw)
In-Reply-To: <20250120071619.2005696-1-adrian.freihofer@siemens.com>

Hi Adrian,

On Mon Jan 20, 2025 at 8:16 AM CET, Adrian Freihofer wrote:
> The devtool ide-sdk section is reformulated to be independent of the
> eSDK installer. In fact, ide-sdk does not even support the execution
> of an installer-based setup.
> This reformulation is also a preparation for moving the devtool
> documentation to a dedicated devtool section which is independent from
> the eSDK documentation.
> It should be clarified that devtool ide-sdk starts the SDK directly
> from the bitbake environment. It is therefore an alternative to
> bitbake -c populate_sdk_ext and installing an SDK installer.
>
> A warning is added that explains some workarounds for some nasty
> behavior of VSCode when running it in a bitbake environment.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
> Cc: Antonin Godard <antonin.godard@bootlin.com>
> ---
> v3: findings from https://lists.yoctoproject.org/g/docs/message/6144
> ---

Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>

Thanks for the patches. I will rebase my devtool patches on yours, and resend
this week.

Cheers
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2025-01-20  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  7:16 [PATCH v3] sdk-manual: extensible.rst: devtool ide-sdk improve Adrian Freihofer
2025-01-20  8:30 ` Antonin Godard [this message]
2025-01-31  9:38 ` Antonin Godard

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=D76RDCSD5GRB.27GJNWE79OPLB@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=adrian.freihofer@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=docs@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