hyprland-plugins: New plugin hyprexpo fails to build
As a follow up to #105, hyprexpo is now in the manifest, but it doesn’t build. All the other plugins in the manifest seem to have built, and no logs or useful errors are output:
$ hyprpm add https://github.com/hyprwm/hyprland-plugins.git
✔ adding a new plugin repository from https://github.com/hyprwm/hyprland-plugins.git
MAKE SURE that you trust the authors. DO NOT install random plugins without verifying the code and author.
Are you sure? [Y/n] y
! old plugin repo build files found in temp directory, removing.
→ Cloning https://github.com/hyprwm/hyprland-plugins.git
✔ cloned
✔ found hyprpm manifest
✔ parsed manifest, found 6 plugins:
→ borders-plus-plus by Vaxry version
→ csgo-vulkan-fix by Vaxry version
→ hyprbars by Vaxry version
→ hyprexpo by Vaxry version
→ hyprtrails by Vaxry version
→ hyprwinwrap by Vaxry version
→ Manifest has 8 pins, checking
✔ commit pin e45066d0741a1a4b9298a4c5ec43a5e57b059a4e matched hl, resetting
✔ Hyprland headers OK
→ Building borders-plus-plus
✔ built borders-plus-plus into borders-plus-plus/borders-plus-plus.so
→ Building csgo-vulkan-fix
✔ built csgo-vulkan-fix into csgo-vulkan-fix/csgo-vulkan-fix.so
→ Building hyprbars
✔ built hyprbars into hyprbars/hyprbars.so
→ Building hyprexpo
✖ Plugin hyprexpo failed to build.
→ Building hyprtrails
✔ built hyprtrails into hyprtrails/hyprtrails.so
→ Building hyprwinwrap
✔ built hyprwinwrap into hyprwinwrap/hyprwinwrap.so
✔ all plugins built
✔ installed repository
✔ you can now enable the plugin(s) with hyprpm enable
Perhaps a user hint for what to do next when a build fails would be a good thing to add to the output. Is there a place to find build logs even?
About this issue
- Original URL
- State: open
- Created 3 months ago
- Reactions: 4
- Comments: 25 (10 by maintainers)
I’ve added some stuff so that it’s like this now:
worth noting it won’t work retroactively, it’s available in git now. Is that enough?
Ignore the duplicate bars its me being a bit goof
makes sense. I’ll try to do something about the UX tomorrow.
Okay several issues:
Tag: v0.38.0-21-g36a8ae9bworks (to build at least, haven’t tried using it) given those other points.This brings us back to UX. The experience of trying to build plugins is quite opaque and the errors point nowhere useful for any of this. The running sessions vs. downloaded vendored copy of hyprland source code needs to be explained, as does the issue wind needing to be in a running copy, and of course plugins should clearly identify a minimum version and that should produce a different error than any of the above.
also about the “it only builds for the newest version”, shouldn’t hyprpm skip the plugin then if it isn’t for the version?
expo needs today’s git. Add
-vto your hyprpm command to see what went wrong