## Issue Addressed Resolves #2406 ## Proposed Changes Add windows release binaries to our CI ## Additional Info Co-authored-by: realbigsean <seananderson33@gmail.com>
2.4 KiB
Pre-built Binaries
Each Lighthouse release contains several downloadable binaries in the "Assets" section of the release. You can find the releases on Github.
Note: binaries are provided for Windows native, but Windows Lighthouse support is still in beta testing.
Platforms
Binaries are supplied for four platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64-bit ARM processors (Raspberry Pi 4)x86_64-apple-darwin
: macOS with Intel chipsx86_64-windows
: Windows with 64-bit processors (Beta)
Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
- Without
portable
: uses modern CPU instructions to provide the fastest signature verification times (may causeIllegal instruction
error on older CPUs) - With
portable
: approx. 20% slower, but should work on all modern 64-bit processors.
Usage
Each binary is contained in a .tar.gz
archive. For this example, lets assume the user needs
a portable x86_64
binary.
Whilst this example uses
v0.2.13
we recommend always using the latest release.
Steps
- Go to the Releases page and select the latest release.
- Download the
lighthouse-${VERSION}-x86_64-unknown-linux-gnu-portable.tar.gz
binary. - Extract the archive:
cd Downloads
tar -xvf lighthouse-${VERSION}-x86_64-unknown-linux-gnu.tar.gz
- Test the binary with
./lighthouse --version
(it should print the version). - (Optional) Move the
lighthouse
binary to a location in yourPATH
, so thelighthouse
command can be called from anywhere.- E.g.,
cp lighthouse /usr/bin
- E.g.,
Windows users will need to execute the commands in Step 3 from PowerShell.
Troubleshooting
If you get a SIGILL (exit code 132), then your CPU is incompatible with the optimized build
of Lighthouse and you should switch to the -portable
build. In this case, you will see a
warning like this on start-up:
WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
On some VPS providers, the virtualization can make it appear as if CPU features are not available, even when they are. In this case you might see the warning above, but so long as the client continues to function it's nothing to worry about.