Skip to content
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

Can't suppress the cache for rerunning a failed installation #41

Closed
vdegenne opened this issue Jun 22, 2024 · 4 comments
Closed

Can't suppress the cache for rerunning a failed installation #41

vdegenne opened this issue Jun 22, 2024 · 4 comments

Comments

@vdegenne
Copy link

I try to build wayfire from the master branch using this convenient script however during the first run I got this error:
image
From the error I understand I need wayland-protocols >= 1.32 but It seems I'm on 1.24 only, so I installed wayland-protocols 1.34 on my system and tried to run the script again, but as you can see from the capture everything is cache and the installation process still think I am using wayland-protocols 1.24 which now I know is not true. I can't find a way to reset the cache, I tried to delete the repository and clone again but the error is there again.
I'm not familiar with meson, wlroots or whatever cause this error to persist.
I'm looking for your help, thanks

@ammen99
Copy link
Member

ammen99 commented Jun 22, 2024

Try adding the -c flag when running wf-install, it will remove everything from previous build attempts.

@ammen99
Copy link
Member

ammen99 commented Jun 22, 2024

Also it is possible that the caching happens because wayfire first checked for wayland-protocols and then the subproject wlroots also does the same ...

@vdegenne
Copy link
Author

Try adding the -c flag when running wf-install, it will remove everything from previous build attempts.

Yes I tried the -c flag before but it doesn't change anything.
I found out the reason I had a pkgconfig file at /usr/local/share/pkgconfig/wayland-protocols.pc which was seen as a cache file. I temporarily renamed this file and could advance to the next error of the build.

@ammen99
Copy link
Member

ammen99 commented Jun 22, 2024

Alright, I hope you figure it out :) I will close this issue for now since I don't think there is anything wf-install can do.

@ammen99 ammen99 closed this as completed Jun 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants