Closed JohnDoeAntler closed 1 year ago
Do I missing something here?
Nope. You have included all the proper logs I could think of.
Meson found your headers, but gcc
didn't, odd.
Have you tried manually cloning and compiling the project?
Sorry for the late response.
Have you tried manually cloning and compiling the project? Yes, I have cloned it manually, executed the lines from the readme build section, but have the same errors like I installed it from AUR.
Before the ninja build command executed, everything seems to work fine, the line meson build --prefix=/usr/local
is executed without poping up any errorsp.
I got the same errors during the execution of the command ninja -C build
.
You could try manaully pointing to the Wayland directory by adding this to meson.build at around line 3:
add_project_arguments( '-I/usr/include/wayland', language : 'c')
Edit: Never mind this was a separate issue I saw online.
I wonder if this is a system issue.
Are you able to compile other Wayland projects such as sway
?
Are you able to compile other Wayland projects such as
sway
?
No, same errors like building this project.
I wonder if this is a system issue.
Mostly I guess, sorry for bothering your time, I will close this issue.
No problem. I knew something was off from the start, but wanted to try to help anyway. But I'm at a loss with this issue. Best of luck to you.
Yep, just found out a few days ago, my gcc and some other C build tools were overwritten by the miniconda binary path, and that explains why I failed the build even though I could find those header files in /usr/include. Anyways, thanks for your help.
The meson build logs:
And my
/usr/include
directory:However during the building process seems like it could not find the Wayland header files:
Do I missing something here?
Full build logs: