10 Replies Latest reply on Aug 2, 2016 3:07 PM by mgiuncato

    Edison BSP (1.0 ... 2.1 ... 3.0 ..  3.5) and Nodejs, the never ending story.... AKA Where in the World Is Carmen Sandiego?

    mgiuncato

      Intel Edison from node 0.10.38 to 0.12 ... aiming to 4.x .. a long story passed... but finally in Jun 6 , 2016 ..

      Wai Lun Poon (Intel)

      in the Release note of INTEL® IOT DEVELOPER KIT 3.5 RELEASE ANNOUNCEMENT ( https://software.intel.com/en-us/blogs/2016/06/06/intel-iot-dev-kit-35-release-announcement ) announce the presence of nodejs 4.4.3 in Intel BSP.

       

      but, taking a deep look : in the main page of BS ( https://software.intel.com/en-us/iot/hardware/edison/downloads  ) the binary image release ( https://software.intel.com/edison-image/latest  ) contais nodejs 4.4.3....

       

      BUT.....

       

      the source code (     http://iotdk.intel.com/src/3.5/edison/     )         that developers MUST use to rebuild image without Library, develop kit, usefull for remote upgrade etc etc ... ) misses the nodejs 4.4.3 and... after years.. sadly contains ... nodejs 0.10.38 (     .. )

       

      #-------------------------------------------------------------------------------------------

      ./build/tmp/work/x86_64-linux/nodejs-native

      ./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/sysroot-destdir/home/mgiuncato/e/i3.5/poky/out/linux64/build/tmp/sysroots/x86_64-linux/sysroot-providers/nodejs-native

      ./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/license-destdir/nodejs-native

      ./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/node-v0.10.38/out/Release/.deps/home/mgiuncato/e/i3.5/poky/out/linux64/build/tmp/work/x86_64-linux/nodejs-native

      ./build/tmp/buildstats/edison-image-edison/Custom Edison build by mgiuncato@ubu14v 2016-07-22 10:08:50 CEST/nodejs-native-0.10.38-r0

      ./build/tmp/buildstats/edison-image-edison/Custom Edison build by mgiuncato@ubu14v 2016-07-22 10:08:50 CEST/nodejs-0.10.38-r0

      mgiuncato@ubu14v:~/e/i3.5/poky/out/linux64$ bitbake -s | grep nodejs

      #-----------------------------------------------------------------------------------------------

       

      anyone in Intel may correct ?

       

      ( or indicate how to do it  :-) )

       

      to be continue...