[yocto] SRTool usage for CVE management at YP

Hello all, There' a discussion pending on the usage of SRTool and CVE management for the Yocto project in general. It is related to the need of having a list of CVEs the project is affected by, those fixed and those that we know we are not affected. In the previous episode, we have had a demo of

[yocto] [meta-anaconda][PATCH] anaconda_oe.py: correct image name

From: Changqing Li Since oe-core commit 26d97acc713 [image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME}], image name has changed to core-image-minimal-qemux86.rootfs.ext4, change accordingly to fix error: INSTALLER_TARGET_BUILD does not exist

[yocto] [yocto-autobuilder-helper][dunfell] config.json: update to latest buildtools tarball

Signed-off-by: Steve Sakoman --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json b/config.json index 03ea262..7ed8259 100644 --- a/config.json +++ b/config.json @@ -10,7 +10,7 @@ "BUILDTOOLS_URL_TEMPLOCAL" :

Re: [yocto] CDN for sstate.yoctoproject.org

Thanks for working on this! I finally got to playing with CDN mirror a bit, and it seems to basically work ok, so next I'm going to write AB tests that check that it remains useful. Specifically: 1. What should the test be? I tried 'bitbake -S printdiff core-image-sato' on a blank build

Re: [yocto] Using cmake... how?

Yeah, it is indeed, hence the changing the git address  From: Ross Burton Sent: 17 October 2023 15:32 To: Dave Hitchman Cc: Mikko Rapeli ; yocto@lists.yoctoproject.org Subject: Re: [yocto] Using cmake... how? On 17 Oct 2023, at 12:58, Dave Hitchman via

[yocto] Yocto Project Status 17 October 2023 (WW42)

Current Dev Position: YP 4.3 M4 (Feature Freeze) Next Deadline: 2nd October 2023 YP 4.3 M4 build date Next Team Meetings: - Bug Triage meeting Thursday October 19th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) - Weekly Project Engineering Sync

Re: [yocto] example where "RDEPENDS" is including a "virtual/" run-time dependency

On 17 Oct 2023, at 12:56, Robert P. J. Day via lists.yoctoproject.org wrote: > > > while the dev manual insists that "virtual/" dependencies are only > for build-time deps and not run-time deps, i ran across this example > on the meta-intel master branch, under >

Re: [yocto] Using cmake... how?

On 17 Oct 2023, at 12:58, Dave Hitchman via lists.yoctoproject.org wrote: > > > I understand that, and the compiler the rest of the recipe uses does cope so > I am trying to understand why this bit of the whole thing is using a > different compiler. Maybe it is somewhere in the cmake of the

Re: [yocto] Using cmake... how?

Hi, On Tue, Oct 17, 2023 at 11:58:23AM +, Dave Hitchman wrote: > I understand that, and the compiler the rest of the recipe uses does cope so > I am trying to understand why this bit of the whole thing is using a > different compiler. Maybe it is somewhere in the cmake of the library, but

Re: [yocto] Using cmake... how?

I understand that, and the compiler the rest of the recipe uses does cope so I am trying to understand why this bit of the whole thing is using a different compiler. Maybe it is somewhere in the cmake of the library, but it certainly isnt obvious. Thats where I am digging for the moment.

[yocto] example where "RDEPENDS" is including a "virtual/" run-time dependency

while the dev manual insists that "virtual/" dependencies are only for build-time deps and not run-time deps, i ran across this example on the meta-intel master branch, under dynamic-layers/openembedded-layer/recipes-oneapi/ (blank lines added for clarity): $ grep -r "RDEPENDS.*virtual/" *

Re: [yocto] Using cmake... how?

Hi, On Tue, Oct 17, 2023 at 11:35:13AM +, Dave Hitchman wrote: > | /usr/bin/g++ -O2 -pipe -g -feliminate-unused-debug-types > -fmacro-prefix-map=/home/dave/Documents/Kymati/yocto/build/tmp/work/cortexa53-crypto-phytec-linux/libkymati/1.0-r0=/usr/src/debug/libkymati/1.0-r0 >

Re: [yocto] Using cmake... how?

Hi, On Tue, Oct 17, 2023 at 11:35:13AM +, Dave Hitchman wrote: > Thanks, but without the CXX settings there is no difference either, it still > uses the wrong toolchain (or rather tries to and fails in the same way) . I > have now removed the two export CXX type lines... Check the

Re: [yocto] Using cmake... how?

Thanks, but without the CXX settings there is no difference either, it still uses the wrong toolchain (or rather tries to and fails in the same way) . I have now removed the two export CXX type lines... bitbake -c configure custom-image-mpet Loading cache: 100%

Re: [yocto] Using cmake... how?

Hi, On Tue, Oct 17, 2023 at 10:09:42AM +, Dave Hitchman wrote: > Thanks > > So, first, I thought - as I had seen examples that I had to put these flags > etc. in the configuration function but it appears that was a wrong thing. > Now my recipe looks like: > SUMMARY = "mylib" > DESCRIPTION =

Re: [yocto] Using cmake... how?

Thanks So, first, I thought - as I had seen examples that I had to put these flags etc. in the configuration function but it appears that was a wrong thing. Now my recipe looks like: SUMMARY = "mylib" DESCRIPTION = "Fetch and build mylibi" LICENSE = "CLOSED" LIC_FILES_CHKSUM = ""

Re: [yocto] Using cmake... how?

Hi, On Tue, Oct 17, 2023 at 09:21:27AM +, Dave Hitchman wrote: > Oh I dont know. This is getting to be a bit annoying. > I had already included the inherit cmake line but now it seems maybe that you > dont need to put any cmake commands in... not 100% sure, no one seems to > explain this, I

Re: [yocto] Using cmake... how?

Oh I dont know. This is getting to be a bit annoying. I had already included the inherit cmake line but now it seems maybe that you dont need to put any cmake commands in... not 100% sure, no one seems to explain this, I am not convinced. However I want some extra flags and I have read that you