rust-cross
rust-blog
Our great sponsors
rust-cross | rust-blog | |
---|---|---|
5 | 63 | |
2,475 | 6,600 | |
- | - | |
0.0 | 5.0 | |
almost 2 years ago | about 1 month ago | |
Shell | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-cross
-
Anything C can do Rust can do Better
rust-cross, Everything you need to know about cross compiling Rust programs! - Jorge Aparicio
-
GitHub Actions can't find built binaries to put them to a release
on: push: tags: - 'v*' name: Cross-compile and release jobs: build: name: Build runs-on: ubuntu-latest strategy: matrix: target: # https://github.com/japaric/rust-cross#the-target-triple - x86_64-unknown-linux-gnu - x86_64-pc-windows-gnu - wasm32-unknown-emscripten steps: - uses: actions/checkout@v2 - uses: actions-rs/toolchain@v1 with: toolchain: stable target: ${{ matrix.target }} override: true - uses: actions-rs/cargo@v1 with: use-cross: true command: build args: --release --target=${{ matrix.target }} release: name: Release needs: [ build ] runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 with: clean: false - uses: nowsprinting/check-version-format-action@v3 id: version with: prefix: 'v' - name: Create release id: new_release uses: actions/create-release@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: tag_name: ${{ github.ref }} release_name: Release ${{ github.ref }} body: | Changes in this release: - First change - Second change draft: false prerelease: false - name: Upload 64-bit Windows build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client.exe asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }}.exe asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }} - name: Upload 64-bit Linux build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }} asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }} - name: Upload 32-bit WebAssembly build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client.wasm asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }}.wasm asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }}
-
In support of single binary executable packages
Well, at least that's that easy if what you try to compile don't have C dependencies. For C dependencies, there is cross <https://github.com/japaric/rust-cross> which I had good experiences with.
-
Hey Rustaceans! Got an easy question? Ask here (15/2021)!
Oh, this was the first thing that came up: https://github.com/japaric/rust-cross
rust-blog
- Common Rust Lifetime Misconceptions
-
What are some good resources for experienced programmers new to Rust to learn about lifetimes?
Hands down the best resource (after you've had sufficient experience with Rust, especially so) - https://github.com/pretzelhammer/rust-blog/blob/master/posts/common-rust-lifetime-misconceptions.md
-
How can a parameter type `T` be not long living enough?
I really really recommend reading this to understand lifetimes and generics in Rust better.
- What learning resource has had the greatest impact in elevating your understanding and knowledge of Rust?
- I do not understand why Sized bound prevents a trait from being used as a trait object.
-
Lifetime annotations: why doesn't Rust?
It's already now that the elided lifetimes are not always correct, as pointed out in Common Rust Lifetime Misconceptions (No 5) by pretzelhammer.
-
Anything C can do Rust can do Better
Common Rust Lifetime Misconceptions - kirill
-
Resources on Lifetimes
Probably a bit more advanced than what you asked about, but still possibly useful: Common Rust Lifetime Misconceptions by /u/pretzelhammer.
-
Borrow checker puzzles
This helped me a lot understanding Rust ownership rules and lifetimes: https://github.com/pretzelhammer/rust-blog/blob/master/posts/common-rust-lifetime-misconceptions.md
What are some alternatives?
xargo - The sysroot manager that lets you build and customize `std`
zero-to-production - Code for "Zero To Production In Rust", a book on API development using Rust.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
fluvio - Lean and mean distributed stream processing system written in rust and web assembly.
Module Linker - browse modules by clicking directly on "import" statements on GitHub
static-analysis - ⚙️ A curated list of static analysis (SAST) tools and linters for all programming languages, config files, build tools, and more. The focus is on tools which improve code quality.
just - 🤖 Just a command runner
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
cargo-linked - Display linked packages for compiled rust binaries
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
iced - A cross-platform GUI library for Rust, inspired by Elm
polonius - Defines the Rust borrow checker.