Mailing list archives : pcb-rnd

ID:5979
From:rn...@igor2.repo.hu
Date:Mon, 6 Mar 2023 08:05:42 +0100 (CET)
Subject:Re: [pcb-rnd] Issue finding freetype when it is in non-standard
in-reply-to:5976 from Henner Zeller <h....@acm.org>
Hello Henner,
 
On Sun, 5 Mar 2023, Henner Zeller wrote:
 
>Hi,
>
>When configuring pcb-rnd, the configure script does not find the
>freetype library
>...
> import ttf glyphs               no              [import_ttf]
>...
>
>This is what I used to configure
>./configure $(cat doc/developer/packaging/auto/Configure.args)
>--prefix=`pwd`/testroot
>
>Looking scconfig/config.log log (attached gzipped), it looks like it
>looks at the 'usual' places, such as /usr/include ... but that
>assumption does not hold on nixos.
>
>There, more 'meta' methods to find packages are advised. Using
>pkg-config, it will find the necessary library; and this is how it
>looks like ... you can tell that this is not necessarily a
>super-guessable place :)
>
>$ pkg-config --cflags --libs freetype2
>-I/nix/store/ybd7brnb5kavanvz40mg2p5pmgnczi85-freetype-2.12.1-dev/include/freetype2
>-L/nix/store/2jq0rdhc7wb8fj0q82whsj9p50sdmvcv-freetype-2.12.1/lib
>-lfreetype
>
>So I suggest to use pkg-config as fallback to find freetype.
 
 
(meanwhile we had a discussion on IRC, and this mail is only to inform the 
rest of the mailing list about the conclusions.)
 
I think this can affect any dependency on that distro, which means we 
would need to have a pkg-config fallback for pretty much every external 
lib dep to make this work reliably. And I really dislike that idea.
 
So I think on distros that use such highly-non-standard installation 
paths, the way to go is using a longer ./configure line that specify the 
-L and -I flags (which in turn you can obtain with pkg-config).
 
Best regards,
 
Igor2
 
 

Reply subtree:
5979 Re: [pcb-rnd] Issue finding freetype when it is in non-standard from rn...@igor2.repo.hu