Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

2025-01-15 Thread Antonin Godard via lists.openembedded.org
Hi Randy, On Mon Jan 13, 2025 at 11:02 PM CET, Randy MacLeod wrote: [...] >> + >> +output_binary = cpp_file_name + ".out" >> +compile_command = ['g++', '-std=c++17', cpp_file_name, '-o', >> output_binary] > > Maybe use BUILD_CC here? > > Oddly, that variable isn't in the docs but

Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

2025-01-13 Thread Yoann Congal via lists.openembedded.org
Hello Christos! I agree with Randy, this is a good start :) Le 13/01/2025 à 21:44, Christos Gavros via lists.openembedded.org a écrit : > Some users have reported issues which were caused because they were missing > the right libstdc++-version-dev in their system. > A new function with the name

Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

2025-01-13 Thread Randy MacLeod via lists.openembedded.org
On 2025-01-13 3:44 p.m., Christos Gavros via lists.openembedded.org wrote: Some users have reported issues which were caused because they were missing the right libstdc++-version-dev in their system. A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass in order to ver

[OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

2025-01-13 Thread Christos Gavros via lists.openembedded.org
Some users have reported issues which were caused because they were missing the right libstdc++-version-dev in their system. A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass in order to verify that the host system can compile and link successfully a 'hello world' c