hyprland-plugin-template | A `` convenient '' Hyprland plugin template

This is a github template repository. To use it, use the green Use this template button at the top of the repository file view.
For a code editor, I recommend VS Code or Neovim, but anything that can use Clangd will work If you use Clangd, make clangd will generate a simple compile_flags.txt file with the proper include paths and flags, which will make Clangd recognize the includes etc. Warning: Compiling the plugin should still be done using GCC 12+. Clang does not properly build Hyprland, and is very fussy about the hook system. You will most likely encounter errors like cannot cast from type 'void (CCompositor::*)(CWindow *, wlr_surface *)' to pointer type 'void *' This won't happen when building with GCC and can be ignored. The most important part of setting up plugin builds is the HYPRLAND_HEADERS variable. Plugins can hook directly into Hyprland's C++ code, which is what makes them so powerful. Because of that, they need to be able to see the Hyprland source. HYPRLAND_HEADERS ensures that. When building your own plugins for testing, you will need to manually define it using export HYPRLAND_HEADERS=(PATH_TO_HYPRLAND_SOURCE_ROOT) before running make commands. You can use a local path if you keep Hyprland source anyway, but I'd definitely recomment using hyprload. If you use your local source different from the hyprload one, make sure to run make pluginenv in the Hyprland folder.
main.cpp: The PLUGIN_INIT function returns a struct with the plugin name, description, author and version. Change those.
Makefile: At the top of the file, the variable PLUGIN_NAME contains the name of the plugin .so that will be built. This should generally match your plugin name.
hyprload.toml: The [examplePlugin] and [examplePlugin.build] should be changed to match the name of your plugin. hyprload will look at these dictionaries for info about the plugin. For more info, see hyprload docs