Replies: 76 comments 165 replies
|
thank you for the guide! |
|
Maybe you could setup a Fedora Copr to build and publish the releases |
|
Can't get it to compile. I followed the above instructions - this is Fedora 36. libwayland-server is installed.
|
|
i installed it via copper, then uninstalled it without its dependencies and then the build worked for me (Nobara) |
|
copr* |
How can i update pixman ? |
|
for the pixman-1 error i had to compile it https://www.linuxfromscratch.org/blfs/view/svn/general/pixman.html |
|
It worked tnx |
|
That's strange - I just pulled the latest version of Hyprland and was able to build it successfully. Maybe delete your Hyprland repo and re-clone - perhaps you cloned at a bad time or something (pretty unlikely). Otherwise I'm afraid I don't have any insight into your issue. You could check out the wiki and see if you can get it to compile using cmake instead of ninja. Edit to add: I ran xorg-x11-server-Xwayland-21.1.4-1.fc35.x86_64 Edit once more: I looked at the meson.build file for wlroots - it specifies a wayland-server version >= 1.20. You said you're running F36 so you're probably up to date, but you may want to check your package version. |
|
same here hyperland has a wayland server requirement of 1.21 and fedora repos only have 1.20.what could have changed in such a short time. |
|
I encountered this on arch not long ago. The "problem" is that Hyprland follows the current git development of wlroots fairly closely. The bundled wlroots version is never more than a couple of weeks behind the latest git commits, and wlroots recently bumped their Wayland server requirements to 1.21. I don't know how feasible it is to downgrade the bundled wlroots submodule, but that might be the best bet if upgrading the wayland-server isn't an option. |
|
You can always use the precompiled releases, I guess. |
|
That's also the reason I didn't update the COPR packages. I might try to play with some packages over the weekend and see what I can get. |
|
I am no Fedora expert, but you should use |
|
You're absolutely right. We use podman instead of mock at work for repeatable non-contaminated builds. However for personal use, I'm OK with a quick build using the system packages. |
|
I'm no longer able to build Hyprland due to compiler errors. The reason is the recent switch to the C++23 standard and the use of I guess I've put off upgrading long enough, it may finally be time to do so. |
|
cant install it when i try to sudo make install i get this error [riot@localhost-live Hyprland]$ sudo make install |
|
Try using meson / ninja instead of make. If you have wlroots installed on your system, running |
|
for some reason when i use mason i get wayland-server missing even though am ruing the latest fedora update |
|
This is very strange - I have F35 on my laptop and F36 in a test VM, and I can compile Hyprland with ninja in both places. I looked through the meson.build file in the subprojects/wlroots repo for the wayland-server requirement - you might want to do the same to see if what's there matches your system. It looks to me like the method for determining whether the requirement for wayland-server is met might be internal to meson - when I have a bit of time I'll dig around and see if I can turn something up, because you're certainly not the only person who's run into this problem. Edit to add: it looks like people are having the same issue with some of the other Wayland compositors that use wlroots (newm, wayfire). @SteveHNH above looks like he was able to get meson to run by adding some more packages - you might see if that will work for you. |
|
Filling in: the following works in Fedora 36 for me. Using the command above from @bceric7 : and installing dev dependencies: Builds for me. |
|
Since xcb-errors isn't available in the fedora repos AFAIK, I built and installed via: I also built vulkan-renderer in a docker container, so it is untested. Use at your own risk: Click to expand |
|
I had to build vulcan-renderer from source. Here's the docs. |
|
... or you can install https://opensuse.pkgs.org/tumbleweed/opensuse-oss-x86_64/libxcb-errors0-1.0.1-1.1.x86_64.rpm.html RPM (work for me on F37) |
|
looks like it also worked on fedora 38 let me restart my system |
|
Hey folks, I took a look at packaging hyprland to try it out on Fedora. It's available in this COPR repo. https://copr.fedorainfracloud.org/coprs/carlwgeorge/hyprland/ I'm not sure that I'll stick with it, but I'd like to avoid this packaging work going to waste. Would any of the hyprland developers be interested in becoming Fedora packagers to maintain an official Fedora hyprland package? I can see that @vaxerski co-maintains the AUR package, this would be a similar set up to that. The spec file I wrote already complies with the Fedora packaging guidelines. I can add it to Fedora and sponsor someone to co-maintain it to ensure it stays up to date. |
|
RPM packages created with fpm do not comply with the Fedora packaging guidelines. I suspect similar things are true for other distro package formats. It's not a tool for creating correct packages, it's a tool for creating hacky one-off solutions that are not maintainable long term. It solves the problem of "I want a package file right now that will technically install", and doesn't look past that problem in the slightest. |
|
Aw interesting @carlwgeorge can you elaborate more about complying with Fedora packaging guidelines? Coming from natives mobile apps world we are using similar tools (jenkins/fastlane) to 'package' Android/iOS apps and fpm looks like a lot of fastlane so I am curious if ever I need to package something one day. 🙂 |
|
I don't package for RPM, but I think this applies to every package manager. The action of putting the files in some package format is not the hard part, but getting a build system that builds the package in a system as hermetic as possible, where every dependency is properly declared in the build process and the resulting package. In that sense, fpm doesn't solve much. |
|
fpm doesn't use RPM spec files, so right out of the gate it breaks every rule related to spec files. This includes the general rules about spec files as well as all the other various rules throughout the guidelines that are implemented or enforced as spec file macros and conventions. It also appears to focus on building RPMs from pre-built sources (tarballs, other package formats, etc.), and all packages in Fedora must be built from source code. I honestly don't have time to go through and enumerate every rule in the guidelines that it violates, but those are probably the two biggest show-stoppers. |
|
So I'm teaching myself rpm packaging once I figure out what I'm looking at here I'll see if I can spin up a repo that builds every 24 hours |
|
I get this error on Fedora 36; |
|
That is an error from what? |
|
Using manual releases: https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases |
|
Those are built against Arch, not Fedora |
wget https://ftp.lysator.liu.se/pub/opensuse/tumbleweed/repo/oss/x86_64/libxcb-errors0-1.0.1-1.1.x86_64.rpm
sudo dnf install libxcb-errors0-1.0.1-1.1.x86_64.rpm |
|
Anyone know how to update wayland-server i get |
|
Wait for Fedora 37 |
|
Could annyone be a dear and make/maintain a copr package ? |
|
I don't know because I'm using an outdated version, but recently I saw that v0.15.1beta is a critical update, it says that v0.15.0beta had a problem that made the GPU suffer a lot, also v0.15.2beta fixed a VRAM leak, try updating to the latest version available. |
|
@carlwgeorge added a testing branch https://bodhi.fedoraproject.org/updates/FEDORA-2022-a5f31ced62 this fixes the problem but leaves u with another problem namly even 37 seems to be on v 2.4.112 https://bodhi.fedoraproject.org/updates/?search=libdrm If i try to build it myself i get the following error meson --prefix=$XORG_PREFIX ../meson.build:21:0: ERROR: prefix value '' must be an absolute path A full log can be found at /home/ntanghe/git/libdrm-2.4.113/build/meson-logs/meson-log.txt |
|
Someone did the thing https://copr.fedorainfracloud.org/coprs/kasion/Hyprland-git/ |
I built libdrm-2.4.113 and current Hyprland for 36 and 37. As Hyprland is my daily driver I'll keep it updated with git as the quick releases come. I don't personally use Fedora 36 but most had success with also getting Wayland to 1.21 before installing the build. |
|
I built libdrm-2.4.113 from source https://dri.freedesktop.org/libdrm/libdrm-2.4.113.tar.xz then hyprland got built just fine. tar xf libdrm-2.4.113.tar.xz
cd libdrm-2.4.113
mkdir build
cd build
meson --prefix=/usr/local
ninjaTo check the results, issue ninja install |
|
Hey, I got a compiler error when using a fully up-to-date Fedora 37 install. How would I fix this? I do have libwayland-server installed. |
|
I encountered this exact error today, were you ever able to resolve this @hifinerd and if so how? |
|
Build |
|
same error for me, I'm stucked |
|
sudo dnf install wayland-devel libwayland-client libwayland-server libwayland-cursor libdrm-devel |
|
FWIW until pixman Get the source at https://github.com/hyprwm/Hyprland/releases/tag/v0.17.0beta |
|
You can actually go way further than just Assuming you have all the other dependencies listed in https://wiki.hyprland.org/0.17.0beta/Getting-Started/Installation/#manual-manual-build: sudo dnf install gcc-c++ git meson cmake "pkgconfig(cairo)" "pkgconfig(egl)" "pkgconfig(gbm)" "pkgconfig(gl)" "pkgconfig(glesv2)" "pkgconfig(libdrm)" "pkgconfig(libinput)" "pkgconfig(libseat)" "pkgconfig(libudev)" "pkgconfig(pango)" "pkgconfig(pangocairo)" "pkgconfig(pixman-1)" "pkgconfig(vulkan)" "pkgconfig(wayland-client)" "pkgconfig(wayland-protocols)" "pkgconfig(wayland-scanner)" "pkgconfig(wayland-server)" "pkgconfig(xcb)" "pkgconfig(xcb-icccm)" "pkgconfig(xcb-renderutil)" "pkgconfig(xkbcommon)" "pkgconfig(xwayland)" glslang-develgit clone --recursive https://github.com/hyprwm/Hyprland
cd Hyprland
git checkout be6f5ce
cd subprojects/wlroots
git checkout c2d2773d
cd ../..
sudo make install |
|
The fastest way to get accurate information, is to be wrong on the internet :) <3 Thank you Daxtorim! |
Thank you so much, this was exactly the issue I was having and it fixed it. |
Hi, I'm a noob but I followed your advice, I get the below error... any ideas?[k@nobara-pc ~]$ cd Hyprland wlroots 0.16.0-dev User defined options Found ninja-1.10.2 at /usr/bin/ninja |
|
I tried building the 0.19.1 beta and I am struggling with meson _build I can't find it on the internet to build it myself. |
|
Managed to build it. output: And trying to build Hyprland: |
|
im using fedora 38 kernel version 6.4.15-200.fc38.x86_64 and tring to upgrade to the newest release which is supposedly better compatible with screen capture and routing when used with the new xdg-desktop-portal-hyprland 1.0 release. |
|
I installed libinput-devel and got a successful build |
|
in case you have problems with the wayland-protocols version. check this: compile it and then check for new errors ! GL |
|
Hello, Does anyone have a thought on upgrading to Fedora 39 with hyprland installed? I'm running fedora 38 Mate Compiz-spin, but have more or less given up MATE for hyprland.. I don't want to upgrade and kill hyprland and all it's components. Thanks |
|
IMHO... your issue is that you Hyprland setup is not automated and you are afraid to waste your time to get it working again. So... my advice would be that you should do clean F39 |
|
wrong .... i already have isolated home partition, and backups of my settings for hyprland , my question is simple. is everything working in 39. |
|
I had Hyprland with waybar on Fedora 38 and just today I upgraded to 39, everything works fine so far. |
|
Not exactly Fedora but I got v0.17.0beta working on the latest version of RHEL (Rocky Linux 19.2) Manual build of: |
Fedora 39sudo dnf install hyprlandTo build from sourceDownload hyprland source code from releasesInstall libshwdataDownload hwdata source code from https://github.com/vcrhonek/hwdata/releases/ libdisplay-info
libliftoff
Build hyprlandCopy hyprland.conf to ~/.config/hyprLog out and open hyprland |
|
Very nice. Confirmed to work on Fedora 39 Workstation Edition Gnome. Thx. |
|
Thanks! Working February 2024 |
|
Just to update, it is likely that you need to install |
|
Actually if you are on Fedora 39, you can now just do |
|
there's fedora 39 now?? |
|
@fgclue now there's 40 :D |
|
As of 05/18/24, for anyone still wanting to build from source on Fedora, a current build issue seems to be able to be resolved by first building current release of wayland-protocols from source (Fedora package apparently not yet updated to the version needed to build Hyprland - referencing this issue.) |
|
wayland-protocols-devel helped me |
|
Any one succeed building from source on fedora 40 for latest version 0.42.2 ? |
|
Reminder |
|
Thank guy for the tips |
|
not sure if it'll help, I'm on asahi and this is what i had to install to get to the next ninja -C build command (split into new lines to be read easier) |
|
Could be better if you added backward slashes at the end of every line so that the install command runs if you copy and paste it. sudo dnf copr enable solopasha/hyprland
sudo dnf install \
aquamarine \
aquamarine-devel \
bison \
bison-devel \
cairo-devel \
cmake \
flex \
gcc-c++ \
glaze-devel \
hyprcursor \
hyprcursor-devel \
hyprgraphics \
hyprgraphics-devel \
hyprlang \
hyprlang-devel \
hyprutils \
hyprutils-devel \
hyprwayland-scanner \
hyprwayland-scanner-devel \
libX11-devel \
libXcursor-devel \
libdrm-devel \
libicu-devel \
libinput-devel \
libseat-devel \
libudev-devel \
libwayland-client \
libwayland-cursor \
libwayland-egl \
libwayland-server \
libxcb-devel \
libxkbcommon \
libxkbcommon-devel \
mesa-libEGL-devel \
mesa-libgbm-devel \
meson \
ninja-build \
pango-devel \
pixman-devel \
re2 \
re2-devel \
rust-xkbcommon-devel \
systemd-devel \
tomlplusplus \
tomlplusplus-devel \
wayland-devel \
wayland-protocols-devel \
xcb-util-errors \
xcb-util-errors-devel \
xcb-util-image-devel \
xcb-util-renderutil-devel \
xcb-util-wm \
xcb-util-wm-devel \
xorg-x11-server-Xwayland-devel |
|
solopasha/hyprland copr is dead, we need sb to start cooking |
|
There are plenty of up to date coprs if you look around. |
|
I think, it would probably be better to add, or ask to be added (I think it can be done too), Hyprland to Terra Repositories instead of COPR. |
|
I extracted my scripts which build fedora from source, with minimal dependencies. I am and will be maintaing this. Since I swapped to fedora as my main OS. |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The steps to build Hyprland on Fedora are relatively simple and very similar to the steps described in the wiki. The main difference is in the package names between Arch and Fedora. These steps were tested on Fedora 35 and Fedora 36 Workstation. This was done on a laptop using only an integrated Intel video driver - I don't have an AMD or Nvidia GPU to test with.
To begin, install the necessary packages:
sudo dnf install ninja-build cmake meson gcc-c++ libxcb-devel libX11-devel pixman-devel wayland-protocols-devel cairo-devel pango-develThis base set of packages will pull in all the required dependencies. You may also want to install
gdbif you intend to debug crashes.Then, download the Hyprland source:
git clone --recursive https://github.com/hyprwm/HyprlandThe
--recursiveargument is important - it will clone the required branch of wlroots into the subprojects directory. Note that compiling with the master branch of wlroots will cause compiler errors - you need the branch of wlroots with the modified structures.Now you're ready to build Hyprland. I used ninja for my build:
cd Hyprlandmeson _buildninja -C _buildsudo ninja -C _build installI may have some missing drivers on my system - the wlroots config couldn't enable the vulkan renderer. However, Hyprland seems to be working fine without it. Also, as far as I can tell, Fedora doesn't have an
xcb-errorspackage, so the wlroots config won't be able to find this, either.There were some compiler warnings during the build, but no errors.
You can try building with cmake instead as described in the wiki, but I like ninja myself, so I went for that first.
At this point, Hyprland will be installed. However, on my system at least, I needed to install the Hyprland.desktop session file somewhere that gdm could find it, because it appears gdm doesn't look in /usr/local/share/wayland-sessions:
sudo cp /usr/local/share/wayland-sessions/hyprland.desktop /usr/share/wayland-sessionsFinally, copy the sample config file into place:
mkdir -p ~/.config/hyprcp example/hyprland.conf ~/.config/hyprEdit the config file to match your system, and then log out. Hyprland should show up as a selectable option in gdm - note that it may not if gdm is running in an X session instead of Wayland, so check
/etc/gdm/custom.confand make sure Wayland is enabled. There's a note in the wiki about Hyprland crashing the first time it's launched from gdm, but I didn't see this - Hyprland worked the first time.Thanks to @vaxerski for making such a cool window manager!
All reactions