[sword-devel] [PATCH] Fix ICU checking without icu-config

[Adrian Bunk]

On Sat, Jun 20, 2020 at 03:47:13PM -0400, Karl Kleinpaste wrote:
>...
> Fedora handles this problem /just fine/:
> 
> $ grep libicu-devel /var/log/rpmpkgs
> libicu-devel-63.2-3.fc31.i686.rpm
> libicu-devel-63.2-3.fc31.x86_64.rpm
> $ ls -l /usr/bin/icu-config*
> -rwxr-xr-x 1 root root   205 May 28  2018 /usr/bin/icu-config
> -rwxr-xr-x 1 root root 22011 Jul 25  2019 /usr/bin/icu-config-32
> -rwxr-xr-x 1 root root 22019 Jul 25  2019 /usr/bin/icu-config-64
> $ rpm -qf /usr/bin/icu-config*
> libicu-devel-63.2-3.fc31.x86_64
> libicu-devel-63.2-3.fc31.i686
> libicu-devel-63.2-3.fc31.i686
> libicu-devel-63.2-3.fc31.x86_64
> 
> The main script is a 32/64-bit selector script which then calls the
> right arch-specific binary, and the relevant symlinks are all correct in
> /usr/lib{,64}.
>...

What is "the right arch-specific binary" when I am building on x86_64?
icu-config automatically using icu-config-64 is right most of the time,
but not when building on x86_64 for i686.

On Debian/Ubuntu I can just install the i686 version of pkg-config,
and this will then give the correct i686 output.

Nowadays pkg-config is the standard tool for this kind of information,
the Fedora libicu-devel package is shipping a pkg-config file since 2006.

cu
Adrian