IssueNo:https://gitee.com/openharmony/third_party_harfbuzz/issues/I4X5GU
Feature or Bugfix: Feature
Binary Source:harfbuzz resources
Signed-off-by: Nlancer <haoshuo@huawei.com>

Description:harfbuzz版本降低到2.7.2
Sig:harfbuzz
Feature or Bugfix:Feature
Binary Source:No
Signed-off-by: Nlancer <haoshuo@huawei.com>

IssueNo: https://gitee.com/openharmony/third_party_harfbuzz/issues/I4H06M
Feature or Bugfix: Feature
Binary Source:No
Signed-off-by: Nlizhiqi <lizhiqi1@huawei.com>

This reverts commit 2e86d509.

I think the setup that caused me to do this is faulty and not hiding inlines.

Exposed by:

$ make -j5 CPPFLAGS="-O0" CXXFLAGS=-flto=thin LDFLAGS=-lc++ && ./check-symbols.sh

We'll see if bots like.

This makes more of the gcc spurious warning:

../../src/hb-null.hh:53:39: warning: enum constant in boolean context [-Wint-in-bool-context]

But not going to let that defeat correct code.  Type to switch to clang
as my main compiler...

Fix hb_blob_ptr_t::get_length () as well.

Use in a couple of places.  Push to bots to see how many unhappy before
I convert the rest.

Saves 4 or 8 bytes per object on 64bit archs.

It's true that blob->as<> should only be called on null or sanitized
data.  But this change is safe, so keep it.

Newer compilers / language allows structs with constructor in union.
So, this was not actually testing anything.  Indeed, the recent
change in DISALLOW_COPY *is* making some of our types non-POD.
That broke some bots.

Just remove this since it wasn't doing much, and I'd rather have
DISALLOW_COPY.

Sorry for the noise, downstream custom builders.  Please adjust.

Finally, unified!

Fixes https://github.com/harfbuzz/harfbuzz/issues/1023

It is desirable to be able to build against older versions of glib.

fd7a245d changed the configure check to require glib > 2.38 for
G_TEST_DIST. Before that, version 2.16 was required, but in fact,
since aafe395a, G_PASTE is being used, which was introduced in 2.19.1.
And since 0ef179e2, hb-glib uses GBytes, which were introduced in
2.31.10.

2.19.1 is rather old, but 2.38 is rather new. For Firefox, building
against 2.22 is still supported, although we could probably get away
with bumping that to 2.28. Either way, GBytes is not available.

Arguably, if you build against a glib that doesn't support GBytes,
you're not going to use the hb_glib_blob_create function, so we hide
the function when building against such a glib.

As for G_TEST_DIST, when building against versions of glib that don't
support it, we can fallback to the previous behavior, which, AIUI, was
just making the test not work when building in a separate directory.

This prepares the headers for exporting symbols using visibility
attributes or __declspec(dllexport), so that we do not need to maintain
symbols listing files, as this is what was and is done in GLib and GTK+.

Users should #include <hb.h> (or hb-ft.h, hb-glib.h, etc), but
never things like hb-shape.h directly.  This makes it easier to
refactor headers later on without breaking compatibility.

Also optimizes the common-direction script lookup to be an array lookup.