mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alex Raimondi <raimondi@miromico.ch>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Integration of node.js
Date: Fri, 21 Nov 2014 08:27:54 +0100	[thread overview]
Message-ID: <546EE97A.40102@miromico.ch> (raw)

Hi

I am working on adding nodejs to ptxdist. I use ptxdist to crosscompile 
my ARM based linux.

I already succeeded in crosscompiling the nodejs base package and it 
works on the target.

Node.js is special in some kind. To add extra modules it uses its own 
packet manager "npm". Some packages will build some binaries right on 
the target system upon installing. This will not work on a cross 
compiled target (with no compilers installed)

So my approach is to allow the user to select additional modules and 
cross compile these modules on the host.

So I guess I also need to build nodejs for the host to get my hands on 
the npm package manager. I created a host-node package and it 
successfully compiles.

About the next steps I am unsure how to do that:

- My host-node package currently does fetch/prepare/compile. What do I 
need to do in install or targetinstall? Currently my host-node gets 
installed into platform-XXX/sysroot-host

- I need to use host built npm in (target) node to fetch modules. How do 
I correctly access the npm package manager?

Is there any documentation about host tools usage? What is the meaning 
of cross tools?

Thanks for any hint

Best regards
Alex Raimondi


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2014-11-21  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  7:27 Alex Raimondi [this message]
2014-11-24  8:08 ` Juergen Borleis
2014-12-09 10:04 ` Jean-Claude Monnin
2014-12-10  8:38   ` Alexander Raimondi
2014-12-10 14:15     ` Alexander Stein

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=546EE97A.40102@miromico.ch \
    --to=raimondi@miromico.ch \
    --cc=ptxdist@pengutronix.de \
    /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