Package Details: hyprland-git 0.46.0.r115.ga6b26371-1

Git Clone URL: https://aur.archlinux.org/hyprland-git.git (read-only, click to copy)
Package Base: hyprland-git
Description: Hyprland is an independent, highly customizable, dynamic tiling Wayland compositor that doesn't sacrifice on its looks
Upstream URL: https://github.com/hyprwm/Hyprland
Licenses: BSD-3-Clause, BSD-2-Clause
Conflicts: hyprland
Provides: hyprland, wayland-compositor
Submitter: hertog
Maintainer: Vaxry (zjeffer, alba4k)
Last Packager: alba4k
Votes: 94
Popularity: 1.58
First Submitted: 2022-04-12 20:26 (UTC)
Last Updated: 2025-01-15 20:42 (UTC)

Required by (64)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 39 Next › Last »

<deleted-account> commented on 2023-11-25 00:40 (UTC)

@akshettrj

Thank you for your work. However, I suggest you report this issue upstream, as the patch file subprojects/packagefiles/wlroots-meson-build.patch needs to be fixed.

akshettrj commented on 2023-11-24 13:11 (UTC) (edited on 2023-11-24 13:14 (UTC) by akshettrj)

The package fails to build because the Hyprland upstream has changed the wlroots sover from 12032 to 13032 in this commit: https://github.com/hyprwm/Hyprland/commit/af5d06593f83344e20537ad5ec7a780eda4fce87

suggested changes: https://aur.archlinux.org/packages/hyprland-nvidia-git#comment-945045

D3vil0p3r commented on 2023-11-21 11:04 (UTC) (edited on 2023-11-21 12:57 (UTC) by D3vil0p3r)

Is this package compatible with NVIDIA GPUs? I see that AUR has hyprland-nvidia and hyprland-nvidia-git packages but someone told me that hyprland and hyprland-git packages should work with NVIDIA GPUs. Is it correct? If so, what is the difference between hyprland{-git} package and hyprland-nvidia{-git} package?

<deleted-account> commented on 2023-11-11 00:30 (UTC)

This is a git package that always tracks the latest HEAD on the main branch. Please do not flag it as outdated because of the version number on the AUR web is low.

thatoneguy commented on 2023-11-02 03:37 (UTC)

@memchr yup. That worked. Thanks!

<deleted-account> commented on 2023-11-02 03:27 (UTC)

@thatoneguy Please update your local git clone of this PKGBUILD, which doesn't use the upstream makefile at all.

thatoneguy commented on 2023-11-02 03:25 (UTC) (edited on 2023-11-02 03:27 (UTC) by thatoneguy)

Build/install fails with the following error because the fixwlr make rule was removed in commit d4e4931 upstream. Please update the PKGBUILD.

Submodule path 'subprojects/hyprland-protocols': checked out '0c2ce70625cb30aef199cb388f99e19a61a6ce03'
Submodule path 'subprojects/tracy': checked out '897aec5b062664d2485f4f9a213715d2e527e0ca'
Submodule path 'subprojects/udis86': checked out '5336633af70f3917760a6d441ff02d93477b0c86'
Submodule path 'subprojects/wlroots': checked out '3406c1b17a4a7e6d4e2a7d9c1176affa72bce1bc'
make: *** No rule to make target 'fixwlr'.  Stop.
==> ERROR: A failure occurred in prepare().
    Aborting...

xiota commented on 2023-10-22 11:47 (UTC) (edited on 2023-10-22 11:49 (UTC) by xiota)

@memchr patch should not be in makedepends. It is installed with base-devel, which is an implied make dependency for all packages.

<deleted-account> commented on 2023-10-22 11:09 (UTC)

See comment https://aur.archlinux.org/packages/hyprland-git?O=30#comment-937055

Sorry, won't fix, as stated upstream, gcc >= 13 must be used.

MarcusE1W commented on 2023-10-22 11:00 (UTC)

On ArchlinuxARM is still only gcc12, but it has clang16, so I tried to use that. I used: export CC=clang and export CXX=clang++. However I get this error now right at the start:

Project version: 0.31.0
C compiler for the host machine: clang (clang 16.0.6 "clang version 16.0.6")
C linker for the host machine: clang ld.bfd 2.38
C++ compiler for the host machine: clang++ (clang 16.0.6 "clang version 16.0.6")
C++ linker for the host machine: clang++ ld.bfd 2.38
Host machine cpu family: aarch64
Host machine cpu: aarch64
Compiler for C++ supports arguments -std=c++23: NO 
Compiler for C++ supports arguments -std=c++2b: NO 

meson.build:20:2: ERROR: Problem encountered: Could not configure current C++ compiler (clang 16.0.6) with required C++ standard (C++23)

What would be the correct setup to use clang16 ?

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 39 Next › Last »