linux/meta-openembedded.git/meta-oe/recipes-devtools/nodejs/nodejs4_0.4.12.bb, branch morty

nodejs: cleanup and update

2016-01-04T13:56:23+00:00

Remove old nodejs4_0.4.12 and update nodejs_0.12.7 to the latest stable nodejs_4.2.3. Nodejs is picky about which architectures it supports. The supported arch mapping required some updating to bring it up to date with the current nodejs code. Add COMPATIBLE_MACHINE entries so it only builds for the supported architectures. ARM cores that don't support at least VFP2 have been dropped: https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk "Due the increasing cost of the keeping the "no-VFPv2" port of V8 working on ARM, we are planning on making 3.17 the last V8 release that that supports ARM chips without VFPv2. Starting with the 3.18 release, the minimal V8 requirements will increase to ARMv6 + VFPv2. In order to simplify maintenance, we will also remove the "pre-VFP2" ARM code from the V8 code base." Additionally, gcc no longer supports a VFPv2 option: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-mfpu-1460 Signed-off-by: Trevor Woerner Signed-off-by: Martin Jansa

nodejs4, liblinebreak: use "Zlib" instead of "zlib" for LICENSE

2015-04-13T10:55:52+00:00

* otherwise zlib license text provider isn't found: WARNING: The license listed zlib was not in the licenses collected for liblinebreak WARNING: liblinebreak: No generic license file exists for: zlib in any provider [YOCTO #7584] Signed-off-by: Martin Jansa

cloud9, nodejs4: blacklist

2015-03-10T13:19:36+00:00

Signed-off-by: Martin Jansa

recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues

2014-02-23T22:20:02+00:00

Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa Acked-by: Koen Kooi

nodejs4: fix build with dash

2013-04-15T14:17:22+00:00

Signed-off-by: Martin Jansa

nodejs4: reinstate installing all the files

2013-04-15T14:16:52+00:00

Cloud9 needs the headers to build the o3-xml binary, using 0.8.x headers makes it crash. This installs everything namespaced as 'node4' to avoid collisions. Signed-off-by: Koen Kooi Signed-off-by: Martin Jansa

nodejs 0.4.12: rename to node4 to make it parallel installable with 0.6.x

2012-04-08T19:48:57+00:00

This is done to support running cloud9 using node 0.4.x but all other node apps with 0.6.x Signed-off-by: Koen Kooi