rust-cross VS iced

rust-cross, Everything you need to know about cross compiling Rust programs! - Jorge Aparicio

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 }}

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.

Oh, this was the first thing that came up: https://github.com/japaric/rust-cross

Based on [1] it looks like System76 does actually think about accessibility, but it's not upstreamed yet.

[1]: https://github.com/iced-rs/iced/issues/552#issuecomment-2180...

AFAICT the "big deal" here is using a rust-native toolkit, iced[0], rather than just slapping together another reskinned gtk-based solution like most similar submissions do.

So this is potentially a really cool thing, not just somebody tinkering with UI elements.

[0] https://github.com/iced-rs/iced

In the last part of the series, we will build a simple UI for Zerocalc. We will use the Iced GUI library as it has a very nice API and very poor documentation which is a great opportunity to dig into its internals...

It's not actually a limitation, the ecosystem is just young:

https://github.com/iced-rs/iced

My general point though is that there's still some ecosystem/legacy reasons to stick with C++, but Rust very much fills the same niches as C++.

Hi all!

Castiron is a super simple podcast player/manager I am building to learn Rust. It uses the iced [https://iced.rs/] GUI library.

Currently the feature set is pretty slim, but you can:

I am building an app using Iced that takes hashes of the files in a directory and assigns them to a profile. The problem is that I can't get the progress bar to update in real time. I've been checking out examples like this https://github.com/iced-rs/iced/tree/master/examples/download_progress. But I just can't get the progress bar to move. Is anyone available to take a look at my code and maybe show me a fix (as long as you're okay with MIT licensing your changes)?

What about Yew and Iced?