From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Adrian Freihofer" <adrian.freihofer@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Adrian Freihofer <adrian.freihofer@siemens.com>
Subject: Re: [OE-core] [PATCH v2 00/13] devtool ide plugin
Date: Thu, 24 Aug 2023 09:58:01 +0200 [thread overview]
Message-ID: <20230824095801.5a3ca2f4@booty> (raw)
In-Reply-To: <20230822192300.3235896-1-adrian.freihofer@siemens.com>
Hello Adrian,
On Tue, 22 Aug 2023 21:20:06 +0200
"Adrian Freihofer" <adrian.freihofer@gmail.com> wrote:
> Changes in comparison to v1:
> - Replace the .vscode config commit by something wich can be merged
> - Improve the commit messages
> - Add missing signed off
>
>
>
> According to https://www.yoctoproject.org/community/yocto-project-engineering-request-for-quotation/
> one of the proposed areas for development of the Yocto project is "VSCode IDE Integration - New developer tooling".
> One aspect of this larger topic is helping application developers configure the IDE to work on a recipe's source code using Yocto's eSDK. This patchset provides a new devtool plugin (devtool ide) that does this fully automatically for recipes inheriting the cmake or the meson bbclass. Support for more programming languages and build tools may be added in the future.
Testing with this series showed some errors on the autobuilders in the
devtool.DevtoolIdeTests.test_devtool_ide_recipe_* tests:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/devtoolqa4gzuj7fk/.vscode/tasks.json'
Some logs:
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1954/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5592/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5668/steps/14/logs/stdio
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-08-24 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 19:20 [PATCH v2 00/13] devtool ide plugin Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 01/13] vscode: add minimal configuration Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 02/13] cmake.bbclass: refactor cmake args Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 03/13] cmake.bbclass: cleanup spaces and tabs Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 04/13] cmake.bbclass: support qemu Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 05/13] devtool: new ide plugin Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 06/13] tests: add a C++ example recipe Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 07/13] cmake-example: workaround for pseudo breakeage Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 08/13] refactor: make multiprocess_launch callable without d Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 09/13] refactor: make strip_execs " Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 10/13] devtool: refactor deploy-target Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 11/13] devtool: ide make deploy-target quicker Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 12/13] oe-selftest devtool: ide tests Adrian Freihofer
2023-08-22 19:20 ` [PATCH v2 13/13] docs: cover devtool ide Adrian Freihofer
2023-08-23 8:41 ` [OE-core] " Luca Ceresoli
2023-08-24 7:58 ` Luca Ceresoli [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=20230824095801.5a3ca2f4@booty \
--to=luca.ceresoli@bootlin.com \
--cc=adrian.freihofer@gmail.com \
--cc=adrian.freihofer@siemens.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