LibreTranslate / LibreTranslate/LTEngine

cargo binstall suport

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
197
Forks
32
Avg merge
15h 37m
Merged PRs (30d)
1

Description

https://github.com/cargo-bins/cargo-binstall

A point cargo toml binpkgs..
Else it falls back to cargo build install etc...

https://github.com/marketplace/actions/install-cargo-binstall

Ubuntu docker n rustup multiarch targets
Llvm-mingw64 could autobake for all...

# Simplified logic for your GitHub Release Action
jobs:
  release:
    strategy:
      matrix:
        target: [x86_64-unknown-linux-gnu, x86_64-pc-windows-msvc, aarch64-apple-darwin]
        include:
          - target: x86_64-unknown-linux-gnu
            features: "cuda,vulkan"
          - target: aarch64-apple-darwin
            features: "metal"
    steps:
      - uses: actions/checkout@v4
      - name: Install Toolchain
        run: rustup target add ${{ matrix.target }}
run cargo install xargo binstall # cargo-deb cargo-rpm if want pkgs etc... 
      - name: Build with Xargo
        run: xargo build --release --features ${{ matrix.features }} --target ${{ matrix.target }}
      - name: Upload to Release
        uses: softprops/action-gh-release@v1
        with:
          files: target/${{ matrix.target }}/release/ltengine*

services:
  ltengine-builder:
    image: debian:bookworm-slim
    environment:
      - CUDA_VERSION=12.x
      - LLVM_MINGW_VERSION=20240321
    volumes:
      - .:/src
    command: >
      sh -c "
        apt update && apt install -y curl cmake clang llvm lld git;
        # Download llvm-mingw for the Windows side
        curl -L https://github.com/mstorsjo/llvm-mingw/releases/download/... -o mingw.tar.xz;
        tar -xf mingw.tar.xz;
        export PATH=$PATH:$(pwd)/llvm-mingw/bin;
        # Build LTEngine
        cd /src && cargo build --release --target x86_64-pc-windows-gnullvm --features cuda,vulkan
      "

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the repository's current GitHub Release Action and Docker/build configuration; the issue names no specific file or test entry point. Clarify whether the scope is cargo-binstall package metadata, fallback installation, or the proposed multi-target release build. Done should be a reproducible release workflow covering the agreed targets and installation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions, rust
Domain
build-system, ci-cd, devops, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.