Without the change `yambar` fails to build on `gcc-13` as:
yambar> ../plugin.c: In function 'plugin_load':
yambar> ../plugin.c:279:35: warning: '%s' directive argument is null [-Wformat-truncation=]
yambar> 279 | snprintf(path, sizeof(path), "%s_%s.so", type2str(type), name);
yambar> | ^~
Co-authored-by: Anderson Torres <torres.anderson.85@protonmail.com>
Yambar uses meson as build system. Its `dependency` function uses pkg-config as
default method for finding the required dependencies.
However, as seen in their code[^1], scdoc is searched with `native` set to
true. According to Meson specs[^2], it directs the search to the _build_ machine
instead of the _host_ one. This parameter is usually needed only when finding a
tool to be used during compilation.
Because of this, `pkg-config` needs to be included at `depsBuildBuild`.
Why? Magic! Sorry, I am not so proficient in cross-compilation issues yet.
[^1] 78f7b60e13/doc/meson.build (L3)
[^2] https://mesonbuild.com/Reference-manual_functions.html#dependency_native
* Use fetchFromGitea instead of fetchgit, submodules are unnecessary
as we wlr-protocols are vendored.
* Split into xorg and wayland backends based on an option flag, (By
default, the xorg backend is used, this might be a breaking change)
* Adhere to syntax style guide for long lists.
