Fosstodon

Jons MostovojsI spent four days learning <a href="https://social.doma.dev/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a>-adjacent toolchains (of which there are four, which are doing some things that are the same and some things that are different: <a href="https://social.doma.dev/tags/naersk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#naersk</a>, <a href="https://social.doma.dev/tags/fenix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fenix</a>, <a href="https://social.doma.dev/tags/rustPlatform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustPlatform</a>, <a href="https://social.doma.dev/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>.<a href="https://social.doma.dev/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a>).Throughout these four days I have seen at least a dozen of different error messages. Not a single error message had **anything whatsoever** to do with the error site. Reading traces helped, sometimes, but not always. If you are a company who has excess money and you want to make the world a better place, please have your R&D department pick up <a href="https://social.doma.dev/tags/purenix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#purenix</a>, I urge you.I ended up downgrading my whole *large* codebase to <a href="https://social.doma.dev/tags/rustStable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustStable</a> and simplifying my <a href="https://social.doma.dev/tags/flake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#flake</a> to:```nix { description = "Flake for building rootrunner with standard nixpkgs Rust and OpenSSL support"; inputs = { nixpkgs.url = "github:NixOS/nixpkgs"; flake-utils = { url = "github:numtide/flake-utils"; inputs.nixpkgs.follows = "nixpkgs"; }; }; outputs = { self, nixpkgs, flake-utils, ... }: flake-utils.lib.eachSystem [ "x86_64-linux" ] (system: let pkgs = import nixpkgs { inherit system; }; in { devShells.default = pkgs.mkShell { buildInputs = with pkgs; [ rustc cargo rustfmt clippy rust-analyzer pkg-config sqlx-cli postgresql sqlite nodejs pnpm zip unzip rsync openssl.dev openssl ]; }; devShell = self.devShells.${system}.default; } ); } ```

Simon GollerI really like <a href="https://mastodon.neosam.dev/tags/bevyengine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bevyengine</a> (<a href="https://mastodon.neosam.dev/tags/bevy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bevy</a>) and <a href="https://mastodon.neosam.dev/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> and finally I could create a flake which enables me to install Bevy apps in NixOS.To do this, I've used <a href="https://mastodon.neosam.dev/tags/naersk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#naersk</a> to generate a flake.nix file. From there, I just had to add some build inputs required by some crates like Alsa and had to write a post install script to set environment variables and publish the assets.If somebody is interested on how to set it up in NixOS, here is the code: <a href="https://github.com/neosam/bevy-nix-test/tree/naersk-test" rel="nofollow noopener noreferrer" target="_blank">https://github.com/neosam/bevy-nix-test/tree/naersk-test</a>:ReplyOK: :BoostOK:

Recent searches

Search options

Administered by:

Server stats:

#naersk