Hi Emily, To find the solution to your issue in a rational and deterministic way we need to start from the error message. What I understand is that while build recipe "opc-ua-server-gfex" you get an

Hi Quentin - That's what I tried originally! DEPENDS on boost and not boost-python gives me the following error when trying to build my original recipe:

Hi Emily, Ok so two things. Yes, I'd say you need python in PACKAGECONFIG for boost. However, it seems it's already part of the default value of PACKAGECONFIG,

Hi all - I'm trying to build an opca recipe (https://github.com/kratsg/meta-l1calo/blob/add/opcServer/recipes-core/opc-ua/opc-ua-server-gfex_git.bb) and it's giving me a build error like: |

Current Dev Position: YP 3.1 M4 - Stabilization Next Deadline: YP 3.1 M4 build date 3/30/2020 Next Team Meetings: Bug Triage meeting Thursday Mar. 19th at 7:30am PDT

Hi! I am building a solution on top of raspberrypi 3a+. I am having problem that around 50% of available memory never gets used by the node applications and instead the kswapd kicks in and after a

On Wed, Mar 11, 2020 at 11:26 AM, Khem Raj wrote: please post your recipeHello Khem Raj, Sorry for the late reply. I was not available during last week. So, I post here my recipe. But before I want to

All, YP M+ or high bugs which moved to a new milestone in WW11 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 13604 [master-next]

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 2 peter.kjellerstedt@... 1 timothy.t.orling@... 1 akuster@... 1 Grand

All, Below is the list as of top 50 developers as of the end of WW11 of who have open medium or higher bugs and enhancements against YP 3.1. There are 28 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Each of the fetcher backends makes some assumptions about what it considers to be "the same". For tarballs from whatever source this is easy and we use the hash of the tarball. For git, we work off

Right, now I see what you mean. The build process does not rely on static metadata in the source tree to determine the version, and is instead poking the git checkout to determine what the version is?

This platform has been removed from master, and is therefore not in M3. cu Adrian

Hi Alexander, thanks for your message. I will try to explain my issue once again, since it still seems not clearly formulated. We build our images on CI (Jenkins). There, we have a shared download

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

From: Aaron Chan <aaron.chun.yew.chan@...> Signed-off-by: Aaron Chan <aaron.chun.yew.chan@...> --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py

From: Aaron Chan <aaron.chun.yew.chan@...> Signed-off-by: Aaron Chan <aaron.chun.yew.chan@...> --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py