All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Martin Bark <martin@barkynet.com>,
	Linus Kaschulla <linus@cosmos-ink.net>,
	Daniel Price <daniel.price@gmail.com>,
	Adam Duskett <aduskett@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/nodejs: expose capability to compile host library
Date: Tue, 28 Dec 2021 22:58:05 +0100	[thread overview]
Message-ID: <20211228225805.47df3c46@windsurf> (raw)
In-Reply-To: <20211023050119.3293369-1-james.hilliard1@gmail.com>

On Fri, 22 Oct 2021 23:01:19 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> From: Linus Kaschulla <linus@cosmos-ink.net>
> 
> To use nodejs on the host (independant of the actual system)
> to create some static files to place onto the target rootfs
> nodejs can be very helpful.
> 
> The provided nodejs package didn't show the possibility to
> create a host package. But upon further examination I noticed
> that the package does it in fact (in the .mk). It specifies
> dependencies for the package with the host prefix and also
> invokes $(host-generic-package) as well as $(generic-package)
> which is the only one assumed from the config.
> 
> With this change other packages can require BR2_PACKAGE_HOST_NODEJS
> without any problems or the buildsystem not fully knowing about this.
> Seems that someone added the capability (as a step for the cross-
> compiled nodejs) and didn't notice that this is a handy package by itself.
> 
> When installing global npm packages (with -g), the parameter
> `--prefix $(HOST_DIR)` can be used to ensure that nodejs doesn't try
> to install it onto the real host filesystem.
> 
> I already used this change to create static web files from Angular
> and place onto a target that doesn't need nodejs itself.
> 
> This patch contains fixes based on feedback from:
> - Peter Seiderer <ps.report@gmx.net>
> - Yann E. MORIN <yann.morin.1998@free.fr>
> 
> Signed-off-by: Linus Kaschulla <linus@cosmos-ink.net>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> Changes v1 -> v2:
>   - move nodejs 14 dependency selection to host package
> ---
>  package/Config.in.host        |  1 +
>  package/nodejs/Config.in      |  6 +-----
>  package/nodejs/Config.in.host | 13 +++++++++++++
>  3 files changed, 15 insertions(+), 5 deletions(-)
>  create mode 100644 package/nodejs/Config.in.host

I've applied to master, after significantly simplifying the commit log,
which was a bit verbose for no good reason.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-12-28 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23  5:01 [Buildroot] [PATCH v2 1/1] package/nodejs: expose capability to compile host library James Hilliard
2021-12-28 21:58 ` Thomas Petazzoni [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=20211228225805.47df3c46@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=aduskett@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=linus@cosmos-ink.net \
    --cc=martin@barkynet.com \
    /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.