Re: [yocto] nodejs do_compile eats all resources

> Am Dienstag, 27. September 2022 10:50 schrieb Alexander Kanavin > : > > Do keep in mind that PARALLEL_MAKE can and should be set per recipe, so you > can make-limit only the worst items. > > Alex Yeah, I'm currently using PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}" In a

Re: [yocto] nodejs do_compile eats all resources

> Am Montag, 26. September 2022 19:33 schrieb Alexander Kanavin > > > Anything written in C++ tends to consume 1-2 Gb of ram per compiler process. > If that lands you in OOM, you probably should limit that with > PARALLEL_MAKE:pn-nodejs, but otherwise that is the sad reality of C++ builds.

[yocto] nodejs do_compile eats all resources

Hey, We recently added nodejs to our images and noticed that it's do compile process is a real memory hog. Since we planned to update the recipe anyway we didn't pay much attention, but today we updated the recipe to the current version from openembedded-core (16.14.2). Still I see that it

[yocto] Automate updating of SRCREV

Hey, maybe somebody already has something for this before I reinvent the wheel ;-) We've several internal tools that mostly have their own CI and are referenced in our yocto layers to be picked up by the nightly build. Usually we manually update the SRCREV and add a `git log --oneline

Re: [yocto] NPM Fetcher & License collection in Yocto Zeus

XetPz%2BamYSoE%3D=0> Is it possible to test if you have the same issue with dunfell ? Best Regards, Jean-Marie On Fri, Jan 22, 2021 at 10:00 AM Oliver Westermann mailto:oliver.westerm...@cognex.com>> wrote: Hey, We’ve upgraded to zeus some time ago and also updated some of our recipes ar

[yocto] NPM Fetcher & License collection in Yocto Zeus

Hey, We’ve upgraded to zeus some time ago and also updated some of our recipes around node-red and it’s nodes. Before I created my own class to easily fetch several nodes, now we used devtool to create those recipes. In zeus, this happens using the npm:// fetcher. This worked fine, but we

[yocto] Yocto uses older PV instead of newest - how to figure out why?

Hey, we're porting our yocto from an older NXP iMX release to their newest BSP, upgrading yocto in the process from sumo to zeus. Using their current setup, the layers provide one recipe in two versions - 0.2 and 1.0. imx-boot to be precise. I assumed yocto would use the newer version, but it

Re: [yocto] Autoupdate of versions in specific recipes #yocto

Thanks for the link, I will check it out. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49351): https://lists.yoctoproject.org/g/yocto/message/49351 Mute This Topic: https://lists.yoctoproject.org/mt/74029332/21656 Mute #yocto:

[yocto] Autoupdate of versions in specific recipes #yocto

Hey, Is there a feature in yocto, similar to ${AUTOREV}, which allows to check for updates and modify a recipe? Background: We've a setup which is build upon the yocto project. We've a base git project containing various layers (like basic poky, bsp layers as well as our own layers with our

Re: [yocto] Fw: Reducing rootfs size in yocto

Do you need the -dev version of boost on the device? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48975): https://lists.yoctoproject.org/g/yocto/message/48975 Mute This Topic: https://lists.yoctoproject.org/mt/72609037/21656 Group Owner:

Re: [yocto] What are the key factors for yocto build speed?

On Wed, Mar 18, 2020 at 08:09 AM, Mike Looijmans wrote: > > Of course he's on a tight budget. He wouldn't need to ask for advice > otherwise... When has a company ever given you a card blanche for equipment? :D There is a budget and I just need to write down a good argument to spend it on

Re: [yocto] What are the key factors for yocto build speed?

On Wed, Mar 18, 2020 at 08:38 AM, Martin Jansa wrote: > > > If you want to compare how terrible your current VM compares with some > other builders, you can use: > https://github.com/shr-project/test-oe-build-time Thanks for all the replies here, had some long days so no earlier answers. I did

[yocto] What are the key factors for yocto build speed?

Hey, We're currently using a VM on Windows and it's a lot slower than the native linux build (which is expected). We're looking into getting a dedicated build server for our team (basically a self-build tower PC). Any suggestions what to put in that build to get the most out of it? Currently

[yocto] How to figure out what triggers the rebuild of a certain task/recipe

Hey, I'm debugging a issue in the sdcard generation recipe of a NXP provided class (image_types_fsl). So I'm only interested in their workings of the do_image_sdcard step, however yocto rebuilds the complete rootfs on every call. I already tried limiting the tasks/commands by going to to run

Re: [EXTERNAL] Re: [yocto] Clarifying install vs deploy

On Mon, Feb 10, 2020 at 11:22 AM Nicolas Dechesne wrote: > you use do_install() to install any content that you need to be added to your > rootfs/image, as you said. the content of $D will end up in a binary package > (rpm, deb, or ipk), and that package might eventually be installed into an

[yocto] Clarifying install vs deploy

I was asked by a colleague for the difference between do_deploy and do_install, which I both used mostly by checking similar recipes and copying their methods, but now I'm having some questions as well. The Yocto dev manual doesn't list deploy at all, so my assumption is that why do_install is