[harfbuzz] Use meson and update to 2.7.0

[vejmartin]

Switches from CMake to meson for the build system and updates to 2.7.0.
Drops glib dependency for harfbuzz with a patch for pango based on https://gitlab.gnome.org/GNOME/pango/-/commit/d7c66dd4387fb6c3e79d87a35264b99e7f21a477 and https://gitlab.gnome.org/GNOME/pango/-/commit/5ec478dac9146175de7ba4a1f88ebbab963f4c0f.

• What does your PR fix? Fixes [harfbuzz] Use meson and update to 2.7.0 #12572

• Which triplets are supported/not supported? Same as before.

• Have you updated the CI baseline? No

• Does your PR follow the maintainer guide? Yes

[JackBoosY]

@Neumann-A Could you please review this PR?

Thanks.

[Neumann-A]

@JackBoosY: Not reviewing... will be superseded by #13100. I would also not merge this one until #12945 is merged and user compile flags get forwarded to meson. Otherwise the users cmake toolchains might be ignored.

[LilyWangL]

@vejmartin Thanks for your PR. Could you resolve the conflicts?

[vejmartin]

Could you resolve the conflicts?

@LilyWangL, Yes, I'll resolve them :)

[Neumann-A]

@vejmartin I needed it to get CI to build gtk for x64-linux in that PR. Meson is not clever enough to extract the correct link info out of CMake and I already new that switching harfbuzz to meson would automatically install correct pkg-config files which would be used instead of the cmake configs and lead to a successful CI run. I don't mind if this gets merged before my PR.

[vejmartin]

@Neumann-A, that makes sense. Thanks for the clarification.

[JackBoosY]

One last question: I found that ragel is not on the harfbuzz dependency list. Is this expected?

[vejmartin]

One last question: I found that ragel is not on the harfbuzz dependency list. Is this expected?

@JackBoosY, it looks like ragel isn't required for building the library, src:

ragel = find_program('ragel', required: false)
if not ragel.found()
  warning('You have to install ragel if you are going to develop HarfBuzz itself')

[ebraminio]

Nice work, thanks! :)

[cenit]

One last question: I found that ragel is not on the harfbuzz dependency list. Is this expected?

@JackBoosY, it looks like ragel isn't required for building the library, src:

ragel = find_program('ragel', required: false)
if not ragel.found()
  warning('You have to install ragel if you are going to develop HarfBuzz itself')

But this will make the build different if found or not already on the system...

[cenit]

Anyway since this pr, I cannot build harfbuzz anymore. Curious to understand how on ci it works

edit: analysed build logs and our problem is due to an untested config in CI

[ebraminio]

But this will make the build different if found or not already on the system...

Not much or any really, input of that task is hardly changes, its output is stored on the repo and that is what is used in Chromium checkout of the library.

[Neumann-A]

@cenit Same error as: #15916?

[cenit]

Nope. It's related to the fact that in our CI we specify the config in the triplet, and the port has become incompatible with single-config build.
Again, I'd push @BillyONeal to create a CI pipeline to test "Release-only" builds for ports, maybe a x64-windows-release pipeline. It's a very common config, and it should be tested. At least, it should not regress!

[Neumann-A]

@cenit ah i see it is an error in vcpkg_install_meson not checking for the build type. I was wondering where the error was since I did not observe anything in the changes forbidding that.

[cenit]

yes, exactly.
I will open a PR now and hope for a quick merge

[BillyONeal]

Again, I'd push @BillyONeal to create a CI pipeline to test "Release-only" builds for ports, maybe a x64-windows-release pipeline. It's a very common config, and it should be tested. At least, it should not regress!

I don't believe we have enough hardware available to double the test matrix like that.