/pkg-binaries

Collection of pkg nodejs binaries that are not supported by pkg

Primary LanguageShellMIT LicenseMIT

Pkg Binaries

PRs Welcome

Buy Me A Coffee

Collection of NodeJS precompiled binaries to use with pkg. Please submit a pull request if you have others that are not present in pkg resources.

Usage

Just download the desired binary and copy it into .pkg-cache folder or (if present) to any subfolders inside that (depends on your version of pkg, in my case I have to copy it inside ~/.pkg-cache/v2.5). After this run your pkg command and now it will find the desired binary in cache.

Example with arm64 node v8.11.3 linux:

# Must set -O to preserve the correct file metadata
wget https://github.com/robertsLando/pkg-binaries/raw/master/arm64/fetched-v8.11.3-linux-arm64 -O fetched-v8.11.3-linux-arm64
sudo mv fetched-v8.11.3-linux-arm64 ~/.pkg-cache/

ATTENTION

Once you have placed the file in .pkg-cache folder check that the output of file command gives you the correct interpreter:

pi@NanoPi-NEO-Plus2:~/.pkg-cache/v2.5$ file fetched-v8.11.3-linux-arm64
fetched-v8.11.3-linux-arm64: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-, for GNU/Linux 3.7.0, BuildID[sha1]=02bf3444ecc520c4da40e89cbfbf6831e3a205ea, not stripped

SOmetimes when using wget it could be donwloaded as HTML text file and it wouldn't work.

Utils

In utils folder you will find a bash script package.sh that I have created to package my nodejs application.

Copy the script in your app directory and edit it with your appName and the destination folder of the pkg compiled output.

# EDIT THIS WITH YOUR VALUES
APP="appName"
PKG_FOLDER="pkg"

It also automatically scan node_modules folder and adds required .node files that pkg is not able to package.

You will find all your files inside the destination folder and they will be also packaged inside a .zip file with appName and version choosed.

If you want to make things more easy add a script in your package.json file:

"scripts": {
  "start": "sudo node ./bin/www", //default to start the application
  "package": "sudo chmod +x package.sh && ./package.sh"
}

Than simply run npm run package to start the script

Compilation guide

Using Docker

This allows to compile nodejs pkg binary for arm32 (armv7l, armv6) and arm64 archs from a x86_64.

Steps

# Clone this repo
git clone https://github.com/robertsLando/pkg-binaries.git
cd pkg-binaries
# Get qemu bianaries
cd bin
chmod +x get_qemu.sh
./get_qemu.sh
cd ..
# Build the required binary inside the container. Example for arm32v6
chmod +x build.sh
./build.sh
# Follow build steps and wait for nodejs to be compiled (CAN TAKE MORE THAN 10 HOURS)

Manually

This requires to run commands in a CPU with the required build ARCH

Here is a guide to manually compile a nodejs binary from source. Usually pkg automatically compiles this binary if it doesn't find them in his resources but this process may fail and this is how to do it by your self. In this example I'm compiling nodejs 8 LTS using a device with Linux with architecture arm64 (to check the information about your device run the comand uname -a).

  1. Install required build tools:

    sudo apt-get install build-essential

  2. Than clone node:

    git clone https://github.com/nodejs/node.git

  3. Checkout to the desired version:

    cd node git checkout v8.11.3

  4. Create the patch file inside the node dir and paste the content from the patch file you find on pkg-fetch github inside patch directory (https://raw.githubusercontent.com/zeit/pkg-fetch/master/patches/node.v8.11.3.cpp.patch)

    sudo nano node.v8.11.3.cpp.patch (Ctrl+Maiusc+V - Ctrl+X - Y)

    git apply node.v8.11.3.cpp.patch

    ./configure

    make (this takes many minutes, even hours in some devices)

  5. Finally copy the binary:

    cp node ~/.pkg-cache/v2.5/fetched-v8.11.3-linux-arm64