-
-
Notifications
You must be signed in to change notification settings - Fork 719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot build hyprland with latest wlroots #1134
Comments
hyprland & wlroots ver mismatch. make sure to always |
i cannot do this without using direct git cloning, which is related to #1133 |
the source and binaries provided in the tarball should work. Otherwise, git cloning is your only option (unless your distro packages hyprland) I can also see you're using meson - tried CMake? |
|
#1133 like i said, as i am trying to
myself. |
I meant building with cmake. You're using meson in the above screenshot.
|
well that wont work because of #1133 and not using the meson subprojects feature.
after installing wlroots 0.16.0:
|
that is really odd, you're doing something not right. Hyprland should never try to use system wlroots. The dep in CMakeLists is the subproject, not a system dep |
so... can you fix #1133 so this can be solved? or do i have to fork wlroots as a package for this? |
how is that related to 1133? Yes I could rename it and fix the tarbomb with the next release, but what would that change in this sense? It seems like you're trying to force build Hyprland against a tagged wlroots, which will never work. See #302 You do not need to package wlroots separately. You can keep it as a part of Hyprland and install the separate .so in /usr/lib. (or wherever your distro puts shared objects) The so has a different name than any packaged wlroots, so it will not create a conflict. Although I understand the situation with the tarballs, I fail to see a problem. You are not supposed to use the GitHub generated sources. There is an attached It is a tarbomb. Yes, oops. The problem with changing that now is we are breaking already existing packages if we change that. (e.g. AUR) Although the AUR can be updated easily by me, I have no clue what else may break. Can't you The name of the binaries' tarball is the same as the github sources. Yes, but it doesn't matter. The links are different, and you're not supposed to use the GH sources anyways. |
Which is why i want to use them. but i cannot because of the tarball scheme. |
I will sort it out with the next release. |
i still can't compile hyprland, latest wlroots and latest hyprland with git sources.
to preproduce:
|
Yes, i face this an a previous issue with latest wlroots,
some hyprland code should be changed for the latest wlroots? |
Hyprland does NOT use the latest wlroots. It uses a pinned commit that is updated by me manually every week or two. |
.gitmodules says otherwise. What is the specified commit? |
.gitmodules is not where a commit lock is located. That would be in You can view the tree at any point and see the commit's abbrev-ref if you go into submodules/ |
this wlroots commit: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/4ff46e6cf9463e594605928feeb7c55cf323b5e7 ,...hyprland still fails with the same error. |
... that's the HEAD's lock. Did you even read what I said? You are compiling a release. You need to go back to the release's tree. |
i still don't know exactly how to retrieve the commit. |
IT STILL FAILS. |
i wanted to go on the discord for easy communication, however the discord server requires a phone number, and I'd rather not give that away to a company like Discord, when many FOSS discord servers don't have this in place. |
so, using the native Makefile method, which calls meson and then Cmake, makes hyprland fail. but using native meson makes it have a linking error. |
i got it to work with installation of it was weird that it wouldn't work, but as of right now i am not using cmake, only native meson. |
wlroots commit 0611c10, hyprland fails to compile.
The text was updated successfully, but these errors were encountered: