From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix npm module cross compilation, use up-to-date npm and install modules globally
Date: Wed, 26 Nov 2014 22:42:39 +0100 [thread overview]
Message-ID: <20141126224239.248beb17@free-electrons.com> (raw)
In-Reply-To: <1416775178-13738-2-git-send-email-mwei@cs.ucsd.edu>
Dear Michael Wei,
On Sun, 23 Nov 2014 12:39:38 -0800, Michael Wei wrote:
> diff --git a/package/nodejs/nodejs.mk b/package/nodejs/nodejs.mk
> index 312aaa9..fbcb730 100644
> --- a/package/nodejs/nodejs.mk
> +++ b/package/nodejs/nodejs.mk
> @@ -110,11 +110,13 @@ define NODEJS_INSTALL_MODULES
> # npm install call below and setting npm_config_rollback=false can both
> # help in diagnosing the problem.
> (cd $(TARGET_DIR)/usr/lib && mkdir -p node_modules && \
> + $(HOST_DIR)/usr/bin/npm install -g npm --prefix=$(HOST_DIR) && \
If I understand correctly, this asks npm to update itself, i.e update
the host npm. If that's the case, then I believe this should rather go
in the HOST_NODEJS_INSTALL_CMDS.
Also, could you explain what the "-g" option changes? I understand it
installs modules "globally", but what means "globally" compared to what
was done before? Sorry for the silly questions, but I'm far from being
a NodeJS guy, so I don't really know how npm works.
Thanks a lot,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-26 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 20:39 [Buildroot] [PATCH 0/1] (node.js) fix npm CC, other npm tweaks Michael Wei
2014-11-23 20:39 ` [Buildroot] [PATCH 1/1] Fix npm module cross compilation, use up-to-date npm and install modules globally Michael Wei
2014-11-26 21:42 ` Thomas Petazzoni [this message]
2014-11-27 8:08 ` Michael Wei
2015-07-12 22:09 ` Thomas Petazzoni
[not found] ` <1436858924.2564.14.camel@posteo.de>
2015-07-14 7:44 ` Thomas Petazzoni
2014-11-23 20:46 ` [Buildroot] [PATCH 0/1] (node.js) fix npm CC, other npm tweaks Thomas Petazzoni
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=20141126224239.248beb17@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox