Rasbperry 3 (armv7l-unknown-linux-musl)

[Quantium]

Feature Request

Is your feature request related to a problem? Please describe.

Install starship in raspberry pi 3

Describe the solution you'd like

When I run the installation script in a rasbian system based on armv7l-unknown-linux-musl starship should be installed normaly

Describe alternatives you've considered

May be to have an installation script for raspbian

[kakulukia]

With the upcoming OSX ARM version this will probably effect a lot more than just the few Raspberry users out there. :)

[Quantium]

With the upcoming OSX ARM version this will probably effect a lot more than just the few Raspberry users out there. :)

That's true!!!

[crahan]

Took a stab at cross-compiling Starship on macOS for ARM and ended up with working 32-bit and 64-bit binaries for the Raspberry Pi (no expert at cross-compiling so it was a learning experience). Did some minor testing and so far so good.

[theorician]

@crahan Can you post your shell history for cross compiling to ARM? I'm happy to build my own pipeline to generate an ARM binary for my own Pis but I'm not having a lot of luck getting it working. (Though I was trying to get it to compile with the official rust Docker image, rather than on my Mac.)

[davidkna]

@theorician Try this:

cargo install cross
# Make sure podman/docker are installed
cd starship
cross build --release --target armv7l-unknown-linux-musl

[davidkna]

I think you might need to add --features tls-vendored too

[theorician]

Okay, I've had another go at this. I put it in the form of a Gitlab CI job running in a Docker executor. Copying out the script sections and putting them in a Dockerfile for the rust image works just fine as well.

stages:
  - build
build_for_arm: 
  image: rust
  stage: build
  script: 
    - apt-get update
    - apt-get -yq install gcc-arm-linux-gnueabi
    - rustup target add arm-unknown-linux-gnueabi
    - git clone https://github.com/starship/starship starship-repo
    - cd starship-repo
    - git checkout $(git describe --tags --abbrev=0)
    - mkdir .cargo
    - printf '[target.arm-unknown-linux-gnueabi]\nlinker = "arm-linux-gnueabi-gcc"' > .cargo/config
    - cargo build --release --target arm-unknown-linux-gnueabi --features tls-vendored
    - mv ./target/arm-unknown-linux-gnueabi/release/starship ../
  artifacts:
    name: starship
    paths:
      - ./starship

It does not build HEAD but instead looks for the latest release tag and builds that. That's probably safer for 'production' use. I've confirmed that it works on both the Raspberry Pi 3b and a Pi Zero W, though it's possible that the Pi Zero W will show some weird behaviour, since this is compiling for a newer ARM architecture I think.

Thanks everyone!