public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Enguerrand de Ribaucourt" <enguerrand.de-ribaucourt@savoirfairelinux.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 2/2] oe-init-build-env: generate .vscode from template
Date: Thu, 15 Feb 2024 00:31:14 -0800	[thread overview]
Message-ID: <29120.1707985874540656814@lists.openembedded.org> (raw)
In-Reply-To: <20240214173914.136799-3-adrian.freihofer@siemens.com>

Hello Adrian,

I recommend to keep expliciting other vscode-bitbake parameters. In addition to the default config, the user may have overridden the configuration in their global setting. In which case, the unspecified settings in your template will take that value and probably break.

```
    "bitbake.pathToBitbakeFolder": "${workspaceFolder}/bitbake",
    "bitbake.pathToEnvScript": "${workspaceFolder}/oe-init-build-env",
    "bitbake.pathToBuildFolder": "${workspaceFolder}/build",
    "bitbake.commandWrapper": "",
    "bitbake.workingDirectory": "${workspaceFolder}",
```

Thanks for this new feature which is a great way to share the VSCode configs!


      parent reply	other threads:[~2024-02-15  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 17:36 [PATCH v3 0/2] oe-init-build-env: generate .vscode from template Adrian Freihofer
2024-02-14 17:36 ` [PATCH v3 1/2] vscode: drop .vscode folder Adrian Freihofer
2024-02-14 17:36 ` [PATCH v3 2/2] oe-init-build-env: generate .vscode from template Adrian Freihofer
2024-02-14 17:49   ` [OE-core] " Alexander Kanavin
2024-02-14 17:59     ` adrian.freihofer
2024-02-15  8:31   ` Enguerrand de Ribaucourt [this message]

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=29120.1707985874540656814@lists.openembedded.org \
    --to=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