DunneNote documentation
DocsDunneNoteStart here

Installing and building

In progress

What you need to build DunneNote on each platform, and why there is no installer yet.

There is no download. DunneNote has not been packaged for distribution, and the source repository is not public yet, so this page cannot be followed end to end by a general reader today. It documents the real build so that the prerequisites are known, and so that the moment access opens the process is already written down.

What the build needs

DunneNote is a Tauri 2 application: a Rust core with a Svelte front end rendered in the platform’s own web view. That means the build needs a Rust toolchain and a Node toolchain, plus whatever web view the operating system provides.

Common to every platform:

  • A Rust stable toolchain, managed by rustup
  • Node 20+ — 24 or newer recommended
  • pnpm 9+ — 10 or newer recommended

macOS

xcode-select --install
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
brew install node pnpm

Nothing further is needed. The Command Line Tools supply WebKit, the linker and the code-signing utilities.

Windows

  1. Visual Studio Build Tools 2022 with the Desktop development with C++ workload — this provides the MSVC linker and the Windows SDK.
  2. WebView2 Runtime. Recent Windows 10 and 11 installations already have it.
  3. Rust stable, via the rustup-init.exe installer.
  4. Node 20+, from nodejs.org or winget install OpenJS.NodeJS.
  5. pnpm: npm install -g pnpm.

Linux (Ubuntu 22.04+ / Debian 12+)

sudo apt update
sudo apt install -y \
    libwebkit2gtk-4.1-dev build-essential curl wget file \
    libxdo-dev libssl-dev libayatana-appindicator3-dev librsvg2-dev

On other distributions, install the equivalents of webkit2gtk-4.1-dev, libayatana-appindicator3-dev and librsvg2-dev.

Building

pnpm install
pnpm tauri dev

The first build compiles a large Rust dependency tree and takes several minutes. Subsequent builds are incremental and fast.

pnpm tauri info is a useful diagnostic if something is missing — it reports every toolchain component it can see.

Platform support is tiered

Windows and macOS are tier one: both must be green for a phase to close. Linux is tier two — supported and tested, but WebKit2GTK stability is a known risk that the project does not control, so a Linux-only regression is recorded rather than treated as a release blocker.

Every acceptance sweep runs on physical hardware of all three kinds rather than on one developer’s machine.

What about iPad?

An iPad build has been proven to compile, install, launch and round-trip data on real iOS. It is not shipped: distribution, signing for release and on-device acceptance testing are deliberately deferred. Development continues desktop-first.