{"id":185,"date":"2019-01-07T11:30:07","date_gmt":"2019-01-07T11:30:07","guid":{"rendered":"http:\/\/joanalbamaldonado.com\/blog\/?p=185"},"modified":"2019-01-07T11:49:06","modified_gmt":"2019-01-07T11:49:06","slug":"nw-js-port-for-raspberry-pi","status":"publish","type":"post","link":"https:\/\/joanalbamaldonado.com\/blog\/2019\/01\/07\/nw-js-port-for-raspberry-pi\/","title":{"rendered":"NW.js port for Raspberry Pi"},"content":{"rendered":"

There is a NW.js (formerly node-webkit)<\/a> binary compiled for the ARMv6<\/strong> used by Raspberry Pi. It also runs on Raspberry Pi 2 and Raspberry Pi 3 since they are backward compatible with ARMv6. Other compatible hardware should also be able to run this binary.<\/p>\n

It can be found on GitHub: https:\/\/github.com\/jalbam\/nwjs_rpi<\/a><\/p>\n

Instructions<\/h2>\n
    \n
  1. You need a package.nw<\/em><\/strong> which is just a .zip<\/em> file with .nw<\/em> extension that contains your project (at least, it needs an index.html<\/em> and a package.json<\/em> inside). The included package.nw<\/em> is just an example using the Yasminoku<\/a> game. Since this is only a port, if you need it you can go to the official web site of NW.js<\/a> and read the documentation to know more about package.nw<\/em>, package.json<\/em>, etc.<\/li>\n
  2. Optional: merge nw<\/em> and package.nw<\/em><\/strong> into a single file with the following command:<\/li>\n<\/ol>\n
    cat nw package.nw > Your_new_binary_file\n<\/code><\/pre>\n
      \n
    1. Edit fix_libudev.so.0<\/em> and fix_libudev.so.1<\/em><\/strong> and replace Your_new_binary_file<\/em> found in their code by the real name of your binary file (if you did not merge nw<\/em> and package.nw<\/em> together, then replace it by just nw<\/em>).<\/li>\n
    2. If you need it, give executable permissions<\/strong> (and other desired permissions) to Your_new_binary_file<\/em> (or nw<\/em>) using the chmod<\/em><\/strong> command (as root).<\/li>\n
    3. Try to run the binary<\/strong>:<\/li>\n<\/ol>\n
      .\/Your_new_binary_file\n<\/code><\/pre>\n
      If you did not merge the nw<\/em> and package.nw<\/em> files in one single file (as explained in step 2<\/em>), you should run this command instead:<\/p>\n
      .\/nw\n<\/code><\/pre>\n
        \n
      1. In the case the system complains about libudev.so.0<\/em><\/strong> when you try to run the binary, just type the following command:<\/li>\n<\/ol>\n
        .\/fix_libudev.so.0\n<\/code><\/pre>\n
        Likewise, if needed, do the same for libudev.so.1<\/em><\/strong> running this:<\/p>\n
        .\/fix_libudev.so.1\n<\/code><\/pre>\n
        Note: these two commands above will only work if you have followed the step 3<\/em> properly before. Each of them only needs to be executed once and never again.<\/p>\n
          \n
        1. If all works well, you can distribute your project<\/strong>. You will need these files at least (in the same folder): libffmpegsumo.so<\/em>, nw.pak<\/em> and Your_new_binary_file<\/em> (or nw<\/em> and package.nw<\/em> instead). I would recommend including fix_libudev.so.0<\/em> and fix_libudev.so.1<\/em> optionally (modified as explained in step 3<\/em>) if you think others might need them.<\/li>\n<\/ol>\n
          Versions<\/h2>\n
          node-webkit (now called NW.js) version: v.0.7.0-pre<\/p>\n
          Node.js version: v0.10.12<\/p>\n
          Tested on<\/h2>\n