On 2016-07-13 16:41, Davis, Michael wrote:
I am building for intel core2-32 with an nginx backend.
I believe the layer exists to keep packages more closely aligned with the
upstream project.  I personally use it for the current 6.x releases of nodejs.


Fair enough (although I believe that this should be only in one place).

That said, I'm having issues with very simple angularjs application.  Any
ideas how I might debug it?  My target is ARM i.MX6Q (armv7-hardfp)?

On Wednesday, July 13, 2016 04:24:52 PM Gary Thomas wrote:
On 2016-07-13 15:29, Davis, Michael wrote:
I am currently using angular from a different meta layer.
https://github.com/imyller/meta-nodejs
It maintains newer versions of nodejs.
It might be something you want to try.

I have tried this and yes, the versions are newer, but my simple example
still does not work :-(

What target/platform are you using?
Any idea why there is a separate layer for something that is in a
more mainstream (meta-oe) layer for the same things?

On Wednesday, July 13, 2016 10:11:05 AM Gary Thomas wrote:
On 2016-07-13 09:39, Gary Thomas wrote:
The current (at least 4.4.4) nodejs recipe also creates nodejs-npm
which is npm version 2.15.1.  I'm trying to run angularjs that needs
npm >= 3.3.x.  I've not yet tried the update to 4.4.5, so if this
fixes the issue just let me know.

What needs to be done to get a newer npm?

BTW, the current one segfaults when trying to install the
attached package file.

I have now tried nodejs-4.4.5 which has npm-2.15.5  It no longer
segfaults on the install step, but it doesn't really work :-(
Any access just returns 'Cannot GET /'

Anyone have suggestions on how I might debug this?  It's a known
working (simple) application I got from
https://angular.io/docs/ts/latest/quickstart.html


--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to