main
yume4kde
Yume Nikki desktop pet ported for Wayland KDE
Credits
Sierpinski Simon, Yume Nikki Desktop Pet for Windows
Install
-
Download
yume4kde.flatpakfrom the releases page. -
Install:
flatpak install --user ./yume4kde.flatpak flatpak run jp.angeltech.yume4kde
Native build
You need:
- Rust and Cargo >=1.88
- gcc, cmake, pkg-config
- Qt 6.10 or later. We use Qt Bridge
- LayerShellQt-dev and the Qt build tools
qmake,moc,rcc.
On Fedora:
sudo dnf install gcc-c++ cmake pkgconf-pkg-config \
qt6-qtbase-devel qt6-qtbase-private-devel qt6-qtdeclarative-devel \
qt6-qtmultimedia-devel qt6-qtwayland layer-shell-qt-devel
On Debian:
sudo apt install build-essential cmake pkg-config \
qt6-base-dev qt6-base-private-dev \
qt6-declarative-dev qt6-declarative-private-dev \
qt6-multimedia-dev qt6-wayland liblayershellqtinterface-dev \
qml6-module-qtquick qml6-module-qtquick-controls \
qml6-module-qtqml-workerscript qml6-module-qtmultimedia
On Arch:
sudo pacman -S base-devel cmake pkgconf qt6-base qt6-declarative qt6-multimedia qt6-wayland layer-shell-qt
-
Install Rust and Cargo: rustup.
-
Build:
cargo build --release --locked ./target/release/yume4kde
If you have multiple Qt installs, set QMAKE env:
QMAKE=qmake6 cargo build --release --locked ./target/release/yume4kde
Build and install locally
For Flatpak builds, install Flatpak, flatpak-builder, the KDE 6.10 SDK and
platform, and the matching Rust SDK.
flatpak install --user flathub org.kde.Platform//6.10 org.kde.Sdk//6.10 \
org.freedesktop.Sdk.Extension.rust-stable//25.08
Build from the local source tree and install for the current user:
flatpak-builder --force-clean --user --install .flatpak-build dev.jp.angeltech.yume4kde.json
flatpak run jp.angeltech.yume4kde
Creating a distributable package
flatpak-builder --force-clean --repo=flatpak-repository .flatpak-build jp.angeltech.yume4kde.json
flatpak build-bundle flatpak-repository yume4kde.flatpak jp.angeltech.yume4kde
Local manifest
If you want to test local changes to the source code, you should build with dev.jp.angeltech.yume4kde.json manifest instead, as main manifest pulls a tarball from the remote source.
