mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] harfbuzz: Version bump. 5.3.1 -> 8.3.0
Date: Mon, 29 Jan 2024 16:40:34 +0100	[thread overview]
Message-ID: <ZbfG8pMF6P8prg6L@pengutronix.de> (raw)
In-Reply-To: <20240126194146.2385164-1-christian.melki@t2data.com>

On Fri, Jan 26, 2024 at 08:41:46PM +0100, Christian Melki wrote:
> Major version bumps.
> A lot of work went into the releases.
> Harfbuzz is a victim bump for sdl2-ttf.
> sdl2-ttf in ptxdist uses freetype and harfbuzz externally
> and now requires newer versions.
> Luckily the build changes seem rather small.
> 
> Major speedups, new interfaces, new unicode support,
> new wasm shaper, etc.
> 
> https://github.com/harfbuzz/harfbuzz/releases/tag/6.0.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/7.0.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/7.0.1
> https://github.com/harfbuzz/harfbuzz/releases/tag/7.1.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/7.2.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/7.3.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.0.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.0.1
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.1.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.1.1
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.2.0
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.2.1
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.2.2
> https://github.com/harfbuzz/harfbuzz/releases/tag/8.3.0
> 
> * License file changed. Contributor copyright changes.
> 
> * Disable the new wasm engine.
> 

This generates a broken harfbuzz-config.cmake. From a quick lock, it seems
that just the autotools version is broken. Try switching to meson. That's
the build-system suggested by BUILD.md.

Michael

> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
>  rules/harfbuzz.make | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/rules/harfbuzz.make b/rules/harfbuzz.make
> index 6726fd196..95459c038 100644
> --- a/rules/harfbuzz.make
> +++ b/rules/harfbuzz.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_HARFBUZZ) += harfbuzz
>  #
>  # Paths and names
>  #
> -HARFBUZZ_VERSION	:= 5.3.1
> -HARFBUZZ_MD5		:= 74dd89b7f394aabb0e318e36d169b77e
> +HARFBUZZ_VERSION	:= 8.3.0
> +HARFBUZZ_MD5		:= 7bf11a21c51a4f3ce0728decc4c557d4
>  HARFBUZZ		:= harfbuzz-$(HARFBUZZ_VERSION)
>  HARFBUZZ_SUFFIX		:= tar.xz
>  HARFBUZZ_URL		:= https://github.com/harfbuzz/harfbuzz/releases/download/$(HARFBUZZ_VERSION)/$(HARFBUZZ).$(HARFBUZZ_SUFFIX)
> @@ -23,7 +23,7 @@ HARFBUZZ_SOURCE		:= $(SRCDIR)/$(HARFBUZZ).$(HARFBUZZ_SUFFIX)
>  HARFBUZZ_DIR		:= $(BUILDDIR)/$(HARFBUZZ)
>  HARFBUZZ_LICENSE	:= MIT
>  HARFBUZZ_LICENSE_FILES	:= \
> -	file://COPYING;md5=6ee0f16281694fb6aa689cca1e0fb3da
> +	file://COPYING;md5=b98429b8e8e3c2a67cfef01e99e4893d
>  
>  # ----------------------------------------------------------------------------
>  # Prepare
> @@ -50,7 +50,8 @@ HARFBUZZ_CONF_OPT	:= \
>  	--without-uniscribe \
>  	--without-gdi \
>  	--without-directwrite \
> -	--without-coretext
> +	--without-coretext \
> +	--without-wasm
>  
>  # ----------------------------------------------------------------------------
>  # Target-Install
> -- 
> 2.34.1
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2024-01-29 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 19:41 Christian Melki
2024-01-29 15:40 ` Michael Olbrich [this message]
2024-01-29 18:19   ` Christian Melki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZbfG8pMF6P8prg6L@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox