Re: [OE-core] [PATCH v2 5/5] devtool: code: Provide a generic C++ configuration

2024-02-20 Thread Enguerrand de Ribaucourt
Hi Adrian, Thanks for your review. Yes it doesn't makes a lot of sense to keep this patch compared to the specific support you are working on. It was especially useful for recipes using plain oe_runmake or CC/CXX outside of a class. But we can't distinguish these recipes from others classes

Re: [OE-core] [PATCH v2 5/5] devtool: code: Provide a generic C++ configuration

2024-02-20 Thread Adrian Freihofer
Hi Enguerrand I would really like to stay on the path with tests. This patch changes code which is covered by tests without tests. Lets develop the autotools support as a separate patch series. There are three parts needed: - Extend the cpp-example with autotools support (already on my branch)

[OE-core] [PATCH v2 5/5] devtool: code: Provide a generic C++ configuration

2024-02-19 Thread Enguerrand de Ribaucourt
By default, the cpptools VSCode extension will use the host's headers and flags for linting. This results in a lot of include errors and misleading definitions. Even though this generic configuration doesn't include all the depenendencies, it is a proper fallback for recipe classes we do not