[shaderc] Fix pkgconfig file generation

[nikitalita]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

In our port, we apply a patch to the build to link against the glslang and SPIRV-Tools libraries. While the generated cmake config files reflect this change, the generated pkgconfig file did not, resulting in errors when linking against this library with pkgconfig. This change fixes that.

Additionally, I also added in creation of a shaderc pkgconfig file in addition to the shaderc_static pkgconfig file when building statically. This change brings it in-line with how pkgconfig files are generated for other libraries: the static library has the same name as the shared library, and there is no pc generated for the DLL. This fixes scenarios where we may be building a static shaderc library but dynamic other libraries that depend on it and won't pass in --static to pkgconfig (which is likely to happen, since shaderc is only built statically).

[dg0yt]

Additionally, I also added in creation of a shaderc pkgconfig file in addition to the shaderc_static pkgconfig file when building statically. This change brings it in-line with how pkgconfig files are generated for other libraries: the static library has the same name as the shared library, and there is no pc generated for the DLL. This fixes scenarios where we may be building a static shaderc library but dynamic other libraries that depend on it and won't pass in --static to pkgconfig (which is likely to happen, since shaderc is only built statically).

IMO this sound quite confusing. At least in vcpkg, there should be one pkgconfig module name, regardless of triplet. vcpkg_fixup_pkgconfig merges private properties into the regular properties for ports with static library linkage, so that --static isn't needed. (--static doesn't really work for mixed configurations.)

[nikitalita]

IMO this sound quite confusing. At least in vcpkg, there should be one pkgconfig module name, regardless of triplet. vcpkg_fixup_pkgconfig merges private properties into the regular properties for ports with static library linkage, so that --static isn't needed. (--static doesn't really work for mixed configurations.)

To be clear, this is for an upcoming patch to ffmpeg to add in shaderc support; If we're building ffmpeg dynamically (and since shaderc is only built statically), it fails to find the library with pkgconfig due to it not being named shaderc.

One solution is that I can just remove the shaderc_static package config, I was only keeping that in the off chance of breaking something.

[BillyONeal]

One solution is that I can just remove the shaderc_static package config, I was only keeping that in the off chance of breaking something.

I think @dg0yt 's observation is exactly that there shouldn't be a _static .pc.

[BillyONeal]

Sorry for the nitpick :/

Thanks!

[BillyONeal]

Suggested change

	if(NOT DEFINED VCPKG_BUILD_TYPE OR VCPKG_BUILD_TYPE STREQUAL "debug")
	if(NOT VCPKG_BUILD_TYPE)