Jump to content

Tauri: Difference between revisions

From Official NixOS Wiki
Mrid22 (talk | contribs)
m i added rustc as a package in the devshell, as its needed to run the dev server that tauri provides
A section is added for crane-tauri.
 
Line 36: Line 36:
A distribution mechanism has been implemented for Tauri applications within Nixpkgs. Refer to the Nixpkgs documentation for implementation details. [https://nixos.org/manual/nixpkgs/unstable/#tauri-hook here]
A distribution mechanism has been implemented for Tauri applications within Nixpkgs. Refer to the Nixpkgs documentation for implementation details. [https://nixos.org/manual/nixpkgs/unstable/#tauri-hook here]


== Building a Tauri app with crane ==
The [https://github.com/JPHutchins/crane-tauri crane-tauri] flake uses [https://github.com/ipetkov/crane crane] to cache <code>cargoArtifacts</code>, so changes to your app source rebuild at near-incremental speed. Refer to the [https://github.com/JPHutchins/crane-tauri source code repository] for implementation details and documentation.
[[Category:Development]]
[[Category:Development]]

Latest revision as of 22:57, 6 June 2026

⚠︎
Warning: Work in Progress

Development environment with nix-shell

References

# Run with `nix-shell shell.nix`
let
  pkgs = import <nixpkgs> { };
in
pkgs.mkShell {
  nativeBuildInputs = with pkgs; [
    pkg-config
    wrapGAppsHook4
    cargo 
    cargo-tauri # Optional, Only needed if Tauri doesn't work through the traditional way.
    nodejs # Optional, this is for if you have a js frontend
    rustc # Needed for dev server (npm tauri dev)
  ];

  buildInputs = with pkgs; [
    librsvg
    webkitgtk_4_1
  ];

  shellHook = ''
    export XDG_DATA_DIRS="$GSETTINGS_SCHEMAS_PATH" # Needed on Wayland to report the correct display scale
  '';
}

Building a Tauri app on nixpkgs?

A distribution mechanism has been implemented for Tauri applications within Nixpkgs. Refer to the Nixpkgs documentation for implementation details. here

Building a Tauri app with crane

The crane-tauri flake uses crane to cache cargoArtifacts, so changes to your app source rebuild at near-incremental speed. Refer to the source code repository for implementation details and documentation.