All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alessandro Tagliapietra" <tagliapietra.alessandro@gmail.com>
To: Nicolas Jeker <n.jeker@delisys.ch>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] Improving NPM recipe build speed
Date: Tue, 11 May 2021 12:25:25 -0700	[thread overview]
Message-ID: <CAKKtPp-RGDcs3-tJ8SYyfL8qMySYhuOhyB8iUpaM6uUJ-wS0kA@mail.gmail.com> (raw)
In-Reply-To: <003b4d91f0f044ffdc2a88c8cee34099878a8a05.camel@delisys.ch>

[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]

Hi Nicolas,

Thank you for the advice, that would work for files outside the npm
packages!

Hopefully there's a way to improve npm install speed too, I was hoping
there was a way to just run npm install instead of going through the yocto
npm process (which takes 30 mins vs < 1 min that npm takesi

--
Alessandro Tagliapietra


On Mon, May 10, 2021 at 2:18 AM Nicolas Jeker <n.jeker@delisys.ch> wrote:

> On Mon, 2021-04-26 at 16:29 -0700, Alessandro Tagliapietra wrote:
> > Hi everyone,
>
> Hi Alessandro,
>
> > I'm making an image that includes the node-red recipe from meta-iot-
> > cloud.
> > The whole process takes about 30+ minutes for that recipe alone (most
> > of the time spent in do_configure).
> > Now I want to override the recipe systemd service file and create a
> > nodered user. Every time I change my bbappend file I have to wait 30+
> > minutes to have the result even for a small systemd file change.
> >
> > Is it possible to speed up the process somehow?
> >
>
> I never worked with node-red in yocto, so I can't speak specifically
> for that, but I encountered similar situations before. Here is what I
> usually do when I need to change a file in a recipe that takes a really
> long time to compile or triggers a rebuild of a ton of other recipes.
>
> This only works for files that don't need to be compiled, like
> configuration files, systemd service files, udev rules etc. I usually
> replace the file in the rootfs directly on the device (or boot from NFS
> and edit the file in the NFS export). For example if I need to change a
> systemd service file, I change the file on my host, copy it with scp to
> the device and check if everything is working as expected. When I'm
> finished, I reintegrate my edits with a bbappend file and check again
> if it works.
>
> > Thanks in advance
>
>

[-- Attachment #2: Type: text/html, Size: 2477 bytes --]

      reply	other threads:[~2021-05-11 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 23:29 Improving NPM recipe build speed Alessandro Tagliapietra
2021-05-07 13:53 ` Alessandro Tagliapietra
2021-05-10  9:18 ` [yocto] " Nicolas Jeker
2021-05-11 19:25   ` Alessandro Tagliapietra [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKKtPp-RGDcs3-tJ8SYyfL8qMySYhuOhyB8iUpaM6uUJ-wS0kA@mail.gmail.com \
    --to=tagliapietra.alessandro@gmail.com \
    --cc=n.jeker@delisys.ch \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.